From owner-mpls@UU.NET  Sun Sep  1 20:38:27 2002
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 ESMTP id UAA00646
	for <mpls-archive@lists.ietf.org>; Sun, 1 Sep 2002 20:38:27 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnems24391
	for <mpls-archive@lists.ietf.org>; Mon, 2 Sep 2002 00:40:00 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnems23277;
	Mon, 2 Sep 2002 00:39:38 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnems19975
	for mpls-outgoing; Mon, 2 Sep 2002 00:39:11 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQnems19969
	for <mpls@mail-control.ash.ops.us.uu.net>; Mon, 2 Sep 2002 00:39: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 QQnems25090
	for <mpls@UU.NET>; Mon, 2 Sep 2002 00:37:55 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnems22790
	for <mpls@UU.NET>; Mon, 2 Sep 2002 00:37:55 GMT
Received: from wm5.163.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.108.44.230])
	id QQnems22785
	for <mpls@UU.NET>; Mon, 2 Sep 2002 00:37:53 GMT
Received: by wm5.163.com (Postfix, from userid 60001)
	id B1A9E1C682894; Mon,  2 Sep 2002 08:37:49 +0800 (CST)
MIME-Version: 1.0
Message-ID: <3D72B2DD.00005D.05993@bj230.163.com>
Date: Mon, 2 Sep 2002 08:37:49 +0800 (CST)
From: "wang" <to_wl@163.com>
To: mpls@UU.NET
Subject: =?gb2312?B?dW5zdWJzY3JpYmU=?=
X-Priority: 3
X-Originating-IP: [61.50.74.145]
X-Mailer: Coremail2.0 Copyright Tebie Ltd., 2001
Content-Type: Multipart/Alternative; boundary="Boundary-=_frRWswIerIALAiVWKlZACcdBwtGt"
Sender: owner-mpls@UU.NET
Precedence: bulk

--Boundary-=_frRWswIerIALAiVWKlZACcdBwtGt
Content-Type: text/plain
Content-Transfer-Encoding: 8bit


--Boundary-=_frRWswIerIALAiVWKlZACcdBwtGt
Content-Type: text/html
Content-Transfer-Encoding: 8bit

<br><body background="http://images.163.com/images/logo/maillist/vip/background.gif" bgproperties="fixed">
<font style='font-size:9pt'>
<br>
=============================================================<br>

<a target=_blank href='http://popme.163.com/freemail/index.html'><font color=blue>免费邮箱健康杀毒大行动！</a><br>
<a target=_blank href='http://mall.163.com/servlets/productList?name=wgs&category=585009&pageno=1'><font color=blue>飞舞你的精灵 留住你的精彩 精灵全面收费！</a><br>
<a target=_blank href='http://auctions.163.com'><font color=blue>网易拍卖新开张 全部免费 意外惊喜 意外收获！</a><br>

--Boundary-=_frRWswIerIALAiVWKlZACcdBwtGt--


From owner-mpls@UU.NET  Mon Sep  2 09:17:22 2002
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 ESMTP id JAA21679
	for <mpls-archive@lists.ietf.org>; Mon, 2 Sep 2002 09:17:21 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQneor07697
	for <mpls-archive@lists.ietf.org>; Mon, 2 Sep 2002 13:18:53 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQneor04755;
	Mon, 2 Sep 2002 13:17:25 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQneor00841
	for mpls-outgoing; Mon, 2 Sep 2002 13:17:07 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQneor00834
	for <mpls@mail-control.ash.ops.us.uu.net>; Mon, 2 Sep 2002 13:17: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 QQneor12867
	for <mpls@UU.NET>; Mon, 2 Sep 2002 13:16:38 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQneor12236
	for <mpls@UU.NET>; Mon, 2 Sep 2002 13:16:37 GMT
Received: from xover.netplane.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: fwout.maker.com [12.27.183.253] (may be forged))
	id QQneor12223
	for <mpls@UU.NET>; Mon, 2 Sep 2002 13:16:37 GMT
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2653.19)
	id <RQ2V0P81>; Mon, 2 Sep 2002 09:16:36 -0400
Message-ID: <E7E13AAF2F3ED41197C100508BD6A328493990@india_exch.hyderabad.mindspeed.com>
From: "Reddy, Vikram" <vikramr@netplane.com>
To: "'yasukawa.seisho@lab.ntt.co.jp'" <yasukawa.seisho@lab.ntt.co.jp>,
        "'uga.masanori@lab.ntt.co.jp'" <uga.masanori@lab.ntt.co.jp>,
        "'kojima.hisashi@lab.ntt.co.jp'" <kojima.hisashi@lab.ntt.co.jp>,
        "'sugisono.koji@lab.ntt.co.jp'" <sugisono.koji@lab.ntt.co.jp>
Cc: "'mpls@UU.NET'" <mpls@UU.NET>
Subject: Questions/Comments regarding draft-yasukawa-mpls-rsvp-multicast
Date: Mon, 2 Sep 2002 09:18:44 -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 all,

I have a few questions/comments regarding the RSVP multicast draft.

1) Can a mulicast address be a part of the TERO (as a Leaf node address).
    I have in mind a multicast LSP with a sub-tree containing the nodes of
another muticast group.

    If not I would like to know the reason for the following statement in
section 3.7.1.2

  "A loose explicit route allows an external routing algorithm to decide the
route between specified nodes.  
   Multicast routing algorithm such as PIM-SM[8] and MOSPF[9] are examples
of such algorithms. 
   These routes are selected at each link of the tree. "

The above statements seem to imply that if there is a loose hop (i.e
incomplete information at the source),
then there is a need at the intermediate nodes for the existence of
multicast routing capabilities to resolve
it even further. 
My question is, if we use only Unicast address as ER hops in the TERO, what
is the need for the exsitance of 
mulicast information at the intermediate nodes.

2) Typo in Section 4.5.1. Instead of 
   TERO is added to the Resv message. 
  it should be "TERO is added to the Path message. "
3) In section 5.1, regarding the statement.
"This grafting process is initiated not only by the sender node but also by
the NMS. "
What is meant by the above statement. I would think that the NMS cannot
directly signal a grafting
process. What probably is meant is, the NMS can signal the ingress to
initiate a grafting process.
In any case, it is always the ingress which signals a grafting process as
far as RSVP is considered.
NMS can never directly signal a grafting process.

4) In section 5.2 regarding the statement.
"This pruning process is initiated not only by the sender node but also by
the NMS. "
Same argument as above.
5) After a graft notify/join notify/ prune notify/leave notify are received
by the ingress, the ingress should
update the TERO. This is not specified. 

6) Since there are new messages introduced, it would be more helpful if
there is explicit mention of how each 
message is sent i.e with or withiout router alert etc.

Thanks,
Vikram.









From owner-mpls@UU.NET  Mon Sep  2 22:15:21 2002
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 ESMTP id WAA05478
	for <mpls-archive@lists.ietf.org>; Mon, 2 Sep 2002 22:15:20 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQneqr11605
	for <mpls-archive@lists.ietf.org>; Tue, 3 Sep 2002 02:16:53 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQneqr09725;
	Tue, 3 Sep 2002 02:15:56 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQneqr11561
	for mpls-outgoing; Tue, 3 Sep 2002 02:15:27 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQneqr11556
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 3 Sep 2002 02:15: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 QQneqq29057
	for <mpls@UU.NET>; Tue, 3 Sep 2002 02:14:25 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQneqq09066
	for <mpls@UU.NET>; Tue, 3 Sep 2002 02:14:25 GMT
Received: from realname by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [203.254.224.25])
	id QQneqq09060
	for <mpls@UU.NET>; Tue, 3 Sep 2002 02:14:24 GMT
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
 (iPlanet Messaging Server 5.1 (built Sep  5 2001))
 id <0H1U00I01BNUIH@mailout2.samsung.com> for mpls@UU.NET; Tue,
 03 Sep 2002 11:16:42 +0900 (KST)
Received: from ep_mmp1 (localhost [127.0.0.1])
 by mailout2.samsung.com (iPlanet Messaging Server 5.1 (built Sep  5 2001))
 with ESMTP id <0H1U00IAVBNU00@mailout2.samsung.com> for mpls@UU.NET; Tue,
 03 Sep 2002 11:16:42 +0900 (KST)
Received: from jhkim ([165.213.70.25])
 by mmp1.samsung.com (iPlanet Messaging Server 5.1 (built Sep  5 2001))
 with ESMTPA id <0H1U00CJ3BOYPW@mmp1.samsung.com> for mpls@UU.NET; Tue,
 03 Sep 2002 11:17:23 +0900 (KST)
Date: Tue, 03 Sep 2002 11:14:17 +0900
From: Jin-Hyoung Kim <elecrain@chollian.net>
Subject: Question about LDP Receive Label Request
To: mpls@UU.NET
Message-id: <001a01c252ef$9b5d2770$1946d5a5@jhkim>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
Content-type: multipart/alternative;
 boundary="Boundary_(ID_0aSqvS9I6/n2GHm35J6x5A)"
X-Priority: 3
X-MSMail-priority: Normal
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.

--Boundary_(ID_0aSqvS9I6/n2GHm35J6x5A)
Content-type: text/plain; charset=ks_c_5601-1987
Content-Transfer-Encoding: 7BIT

Hi, all.
My name is kim.

I need your help about following question.

At the Appendix of  RFC 3036, LDP Spec., Receive Label Request Procedure is described as below.

I numbered at the position of my doubts.

-----------------------------------------------------------------------------------------
  LRq.9   Perform LSR Label Distribution procedure:

            For Downstream Unsolicited Independent Control OR
            (1)============================================
            For Downstream On Demand Independent Control

               1. Has LSR previously received and retained a label
                  mapping for FEC from Next Hop?.
                  Is so, set Propagating to IsPropagating.
                  If not, set Propagating to NotPropagating.
                  (2) =====================================


               2. Execute procedure
                  Prepare_Label_Mapping_Attributes(MsgSource, FEC,
                  RAttributes, SAttributes, Propagating,
                  StoredHopCount).

               3. Execute procedure Send_Label (MsgSource, FEC,
                  SAttributes).

               4. Is LSR egress for FEC? OR
                  Has LSR previously received and retained a label
                  mapping for FEC from Next Hop?                  (3) ==================================================
                  If so, goto LRq.11.
                  If not, goto LRq.10.

            For Downstream Unsolicited Ordered Control OR
            For Downstream On Demand Ordered Control

               1. Is LSR egress for FEC? OR
                  Has LSR previously received and retained a label
                  mapping for FEC from Next Hop?  (See Note 3.)
                  If not, goto LRq.10.

               2. Execute procedure
                  Prepare_Label_Mapping_Attributes(MsgSource, FEC,
                  RAttributes, SAttributes, IsPropagating,
                  StoredHopCount)

               3. Execute procedure Send_Label (MsgSource, FEC,
                  SAttributes).
                  Goto LRq.11.
-----------------------------------------------------------------------------------------
(1) As I know, "Label Request " is only applicable for DoD. But in this line,            it is mentioned as the message is also applicable for Downstream Unsolicited Independent Control.      Is it right?
(2) What is "Propagating"?      Could you tell me the reason why the algorithm check the state,      "Has LSR previously received and retained a label  mapping for FEC from Next Hop?.",       and set "Propgating" with "IsPropagating" or "NotPropagating"? What does it mean?
(3) As the summary of A.1.1. Recevie Label Request in RFC 3036, the general procedure of Label Request is as follow:      - Transmission of a notification ...........      - Transmission of label mapping .........      - Transmission of label request ..........      - Installation of labels ................
      But, in this procedure, the algorithm checks whether the LSR is egress or the LSR has the labels from the Next Hop.      As far as I think, it looks like that this procedure must be checked before Send_Label procedure or Prepare_Label_Mapping_Attributes.      Why this procedure is performed after Send_Label procedure?      Is is right?
I need your help.!!
Thanks.    


--Boundary_(ID_0aSqvS9I6/n2GHm35J6x5A)
Content-type: text/html; charset=ks_c_5601-1987
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWtzX2NfNTYwMS0xOTg3Ij4NCjxNRVRBIGNvbnRlbnQ9Ik1T
SFRNTCA2LjAwLjI2MDAuMCIgbmFtZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9TVFlMRT4NCjwvSEVB
RD4NCjxCT0RZIGJnQ29sb3I9I2ZmZmZmZj4NCjxESVY+PEZPTlQgc2l6ZT0yPkhpLCBhbGwuPC9G
T05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+TXkgbmFtZSBpcyBraW0uPC9GT05UPjwvRElW
Pg0KPERJVj48Rk9OVCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBzaXpl
PTI+SSBuZWVkIHlvdXIgaGVscCBhYm91dCBmb2xsb3dpbmcgcXVlc3Rpb24uPC9GT05UPjwvRElW
Pg0KPERJVj48Rk9OVCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBzaXpl
PTI+QXQgdGhlIEFwcGVuZGl4IG9mICZuYnNwO1JGQyAzMDM2LCBMRFAgU3BlYy4sIFJlY2VpdmUg
TGFiZWwgDQpSZXF1ZXN0IFByb2NlZHVyZSBpcyBkZXNjcmliZWQgYXMgYmVsb3cuPC9GT05UPjwv
RElWPg0KPERJVj48Rk9OVCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBz
aXplPTI+SSBudW1iZXJlZCBhdCB0aGUgcG9zaXRpb24gb2YgbXkgZG91YnRzLjwvRk9OVD48L0RJ
Vj4NCjxESVY+PEZPTlQgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgDQpz
aXplPTI+LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08L0ZPTlQ+PC9ESVY+DQo8RElW
PjxGT05UIHNpemU9Mj4mbmJzcDsgTFJxLjkmbmJzcDsmbmJzcDsgUGVyZm9ybSBMU1IgTGFiZWwg
RGlzdHJpYnV0aW9uIA0KcHJvY2VkdXJlOjxCUj48QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IA0KRm9yIERvd25zdHJl
YW0gVW5zb2xpY2l0ZWQgSW5kZXBlbmRlbnQgQ29udHJvbCBPUjwvRk9OVD48L0RJVj4NCjxESVY+
PEZPTlQgDQpzaXplPTI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IA0KKDEpPT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT08QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IA0KRm9yIERvd25zdHJlYW0gT24gRGVtYW5k
IEluZGVwZW5kZW50IA0KQ29udHJvbDxCUj48QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
IA0KMS4gSGFzIExTUiBwcmV2aW91c2x5IHJlY2VpdmVkIGFuZCByZXRhaW5lZCBhIA0KbGFiZWw8
QlI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IA0KbWFwcGlu
ZyBmb3IgRkVDIGZyb20gTmV4dCANCkhvcD8uPEJSPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyANCklzIHNvLCBzZXQgUHJvcGFnYXRpbmcgdG8gDQpJc1Byb3Bh
Z2F0aW5nLjxCUj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsg
DQpJZiBub3QsIHNldCBQcm9wYWdhdGluZyB0byBOb3RQcm9wYWdhdGluZy48L0ZPTlQ+PC9ESVY+
DQo8RElWPjxGT05UIA0Kc2l6ZT0yPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOygyKSANCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT08L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIA0Kc2l6ZT0yPjxCUj48QlI+Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7IA0KMi4gRXhlY3V0ZSANCnByb2NlZHVyZTxCUj4mbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgDQpQcmVwYXJlX0xhYmVsX01hcHBpbmdf
QXR0cmlidXRlcyhNc2dTb3VyY2UsIA0KRkVDLDxCUj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsgDQpSQXR0cmlidXRlcywgU0F0dHJpYnV0ZXMsIA0KUHJvcGFn
YXRpbmcsPEJSPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAN
ClN0b3JlZEhvcENvdW50KS48QlI+PEJSPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyANCjMu
IEV4ZWN1dGUgcHJvY2VkdXJlIFNlbmRfTGFiZWwgKE1zZ1NvdXJjZSwgDQpGRUMsPEJSPiZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyANClNBdHRyaWJ1dGVzKS48
QlI+PC9ESVY+PC9GT05UPjxQUkUgc3R5bGU9IlBBR0UtQlJFQUstQUZURVI6IGFsd2F5cyI+PEZP
TlQgZmFjZT2xvLiyIHNpemU9Mj4gICAgICAgICAgICAgICA0LiBJcyBMU1IgZWdyZXNzIGZvciBG
RUM/IE9SDQogICAgICAgICAgICAgICAgICBIYXMgTFNSIHByZXZpb3VzbHkgcmVjZWl2ZWQgYW5k
IHJldGFpbmVkIGEgbGFiZWwNCiAgICAgICAgICAgICAgICAgIG1hcHBpbmcgZm9yIEZFQyBmcm9t
IE5leHQgSG9wPzxCUj4gICAgICAgICAgICAgICAgICAoMykgPT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT08L0ZPTlQ+PC9QUkU+PFBSRSBzdHlsZT0iUEFH
RS1CUkVBSy1BRlRFUjogYWx3YXlzIj48Rk9OVCBmYWNlPbG8uLIgc2l6ZT0yPiAgICAgICAgICAg
ICAgICAgIElmIHNvLCBnb3RvIExScS4xMS4NCiAgICAgICAgICAgICAgICAgIElmIG5vdCwgZ290
byBMUnEuMTAuDQoNCiAgICAgICAgICAgIEZvciBEb3duc3RyZWFtIFVuc29saWNpdGVkIE9yZGVy
ZWQgQ29udHJvbCBPUg0KICAgICAgICAgICAgRm9yIERvd25zdHJlYW0gT24gRGVtYW5kIE9yZGVy
ZWQgQ29udHJvbA0KDQogICAgICAgICAgICAgICAxLiBJcyBMU1IgZWdyZXNzIGZvciBGRUM/IE9S
DQogICAgICAgICAgICAgICAgICBIYXMgTFNSIHByZXZpb3VzbHkgcmVjZWl2ZWQgYW5kIHJldGFp
bmVkIGEgbGFiZWwNCiAgICAgICAgICAgICAgICAgIG1hcHBpbmcgZm9yIEZFQyBmcm9tIE5leHQg
SG9wPyAgKFNlZSBOb3RlIDMuKQ0KICAgICAgICAgICAgICAgICAgSWYgbm90LCBnb3RvIExScS4x
MC4NCg0KICAgICAgICAgICAgICAgMi4gRXhlY3V0ZSBwcm9jZWR1cmUNCiAgICAgICAgICAgICAg
ICAgIFByZXBhcmVfTGFiZWxfTWFwcGluZ19BdHRyaWJ1dGVzKE1zZ1NvdXJjZSwgRkVDLA0KICAg
ICAgICAgICAgICAgICAgUkF0dHJpYnV0ZXMsIFNBdHRyaWJ1dGVzLCBJc1Byb3BhZ2F0aW5nLA0K
ICAgICAgICAgICAgICAgICAgU3RvcmVkSG9wQ291bnQpDQoNCiAgICAgICAgICAgICAgIDMuIEV4
ZWN1dGUgcHJvY2VkdXJlIFNlbmRfTGFiZWwgKE1zZ1NvdXJjZSwgRkVDLA0KICAgICAgICAgICAg
ICAgICAgU0F0dHJpYnV0ZXMpLg0KICAgICAgICAgICAgICAgICAgR290byBMUnEuMTEuPC9GT05U
PjwvUFJFPjxQUkUgc3R5bGU9IlBBR0UtQlJFQUstQUZURVI6IGFsd2F5cyI+PEZPTlQgZmFjZT2x
vLiyIHNpemU9Mj4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTwvRk9OVD48L1BSRT48
UFJFIHN0eWxlPSJQQUdFLUJSRUFLLUFGVEVSOiBhbHdheXMiPjxGT05UIGZhY2U9sby4siBzaXpl
PTI+KDEpIEFzIEkga25vdywgIkxhYmVsIFJlcXVlc3QgIiBpcyBvbmx5IGFwcGxpY2FibGUgZm9y
IERvRC4gQnV0IGluIHRoaXMgbGluZSwgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxC
Uj4gICAgIGl0IGlzIG1lbnRpb25lZCBhcyB0aGUgbWVzc2FnZSBpcyBhbHNvIGFwcGxpY2FibGUg
Zm9yIDwvRk9OVD48Rk9OVCBmYWNlPbG8uLIgc2l6ZT0yPkRvd25zdHJlYW0gVW5zb2xpY2l0ZWQg
SW5kZXBlbmRlbnQgQ29udHJvbC4gPEJSPiAgICAgSXMgaXQgcmlnaHQ/PC9GT05UPjwvUFJFPjxQ
UkUgc3R5bGU9IlBBR0UtQlJFQUstQUZURVI6IGFsd2F5cyI+PEZPTlQgZmFjZT2xvLiyIHNpemU9
Mj4oMikgV2hhdCBpcyAiUHJvcGFnYXRpbmciPzxCUj4mbmJzcDsmbmJzcDsmbmJzcDsgJm5ic3A7
Jm5ic3A7Q291bGQgeW91IHRlbGwgbWUgdGhlIHJlYXNvbiB3aHkgdGhlIGFsZ29yaXRobSBjaGVj
ayB0aGUgc3RhdGUsIDxCUj4gICAgIDwvRk9OVD48Rk9OVCBmYWNlPbG8uLIgc2l6ZT0yPiJIYXMg
TFNSIHByZXZpb3VzbHkgcmVjZWl2ZWQgYW5kIHJldGFpbmVkIGEgbGFiZWwmbmJzcDsgbWFwcGlu
ZyBmb3IgRkVDIGZyb20gTmV4dCBIb3A/LiIsIDxCUj4gICAgICBhbmQgc2V0ICJQcm9wZ2F0aW5n
IiB3aXRoICJJc1Byb3BhZ2F0aW5nIiBvciAiTm90UHJvcGFnYXRpbmciPyBXaGF0IGRvZXMgaXQg
bWVhbj88L0ZPTlQ+PC9QUkU+PFBSRSBzdHlsZT0iUEFHRS1CUkVBSy1BRlRFUjogYWx3YXlzIj48
Rk9OVCBmYWNlPbG8uLI+PEZPTlQgc2l6ZT0yPigzKSBBcyB0aGUgc3VtbWFyeSBvZiBBLjEuMS4g
UmVjZXZpZSBMYWJlbCBSZXF1ZXN0IGluIFJGQyAzMDM2LCB0aGUgZ2VuZXJhbCBwcm9jZWR1cmUg
b2YgTGFiZWwgUmVxdWVzdCBpcyBhcyBmb2xsb3c6PEJSPiAgICAgIC0gVHJhbnNtaXNzaW9uIG9m
IGEgbm90aWZpY2F0aW9uIC4uLi4uLi4uLi4uPEJSPiAgICAgIC0gVHJhbnNtaXNzaW9uIG9mIGxh
YmVsIG1hcHBpbmc8L0ZPTlQ+IC4uLi4uLi4uLjxCUj4gICAgICAtIFRyYW5zbWlzc2lvbiBvZiBs
YWJlbCByZXF1ZXN0IC4uLi4uLi4uLi48QlI+ICAgICAgLSBJbnN0YWxsYXRpb24gb2YgbGFiZWxz
IC4uLi4uLi4uLi4uLi4uLi48L0ZPTlQ+PC9QUkU+PFBSRSBzdHlsZT0iUEFHRS1CUkVBSy1BRlRF
UjogYWx3YXlzIj48Rk9OVCBmYWNlPbG8uLI+ICAgICAgQnV0LCBpbiB0aGlzIHByb2NlZHVyZSwg
dGhlIGFsZ29yaXRobSBjaGVja3Mgd2hldGhlciB0aGUgTFNSIGlzIGVncmVzcyBvciB0aGUgTFNS
IGhhcyB0aGUgbGFiZWxzIGZyb20gdGhlIE5leHQgSG9wLjxCUj4gICAgICBBcyBmYXIgYXMgSSB0
aGluaywgaXQgbG9va3MgbGlrZSB0aGF0IHRoaXMgcHJvY2VkdXJlIG11c3QgYmUgY2hlY2tlZCBi
ZWZvcmUgU2VuZF9MYWJlbCBwcm9jZWR1cmUgb3IgPEZPTlQgc2l6ZT0yPlByZXBhcmVfTGFiZWxf
TWFwcGluZ19BdHRyaWJ1dGVzPC9GT05UPi48QlI+ICAgICAgV2h5IHRoaXMgcHJvY2VkdXJlIGlz
IHBlcmZvcm1lZCBhZnRlciBTZW5kX0xhYmVsIHByb2NlZHVyZT88QlI+ICAgICAgSXMgaXMgcmln
aHQ/PC9GT05UPjwvUFJFPjxQUkUgc3R5bGU9IlBBR0UtQlJFQUstQUZURVI6IGFsd2F5cyI+PEZP
TlQgZmFjZT2xvLiyPkkgbmVlZCB5b3VyIGhlbHAuISE8L0ZPTlQ+PC9QUkU+PFBSRSBzdHlsZT0i
UEFHRS1CUkVBSy1BRlRFUjogYWx3YXlzIj48Rk9OVCBmYWNlPbG8uLI+VGhhbmtzLiZuYnNwOyZu
YnNwOyZuYnNwOyA8L0ZPTlQ+PC9QUkU+PC9CT0RZPjwvSFRNTD4NCg==

--Boundary_(ID_0aSqvS9I6/n2GHm35J6x5A)--


From owner-mpls@UU.NET  Tue Sep  3 06:40:36 2002
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 ESMTP id GAA21064
	for <mpls-archive@lists.ietf.org>; Tue, 3 Sep 2002 06:40:36 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnery00375
	for <mpls-archive@lists.ietf.org>; Tue, 3 Sep 2002 10:42:05 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnery26370;
	Tue, 3 Sep 2002 10:40:03 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnery01643
	for mpls-outgoing; Tue, 3 Sep 2002 10:39:31 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQnery01635
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 3 Sep 2002 10:39: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 QQnery26686
	for <mpls@UU.NET>; Tue, 3 Sep 2002 10:38:20 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnery25080
	for <mpls@UU.NET>; Tue, 3 Sep 2002 10:38:20 GMT
Received: from tama5.ecl.ntt.co.jp by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: tama5.ecl.ntt.co.jp [129.60.39.102])
	id QQnery25075
	for <mpls@UU.NET>; Tue, 3 Sep 2002 10:38:19 GMT
Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110])
	by tama5.ecl.ntt.co.jp (8.9.3+3.2W/3.7W/07/30/02) with ESMTP id TAA04422;
	Tue, 3 Sep 2002 19:38:00 +0900 (JST)
	(envelope-from yasukawa.seisho@lab.ntt.co.jp)
Received: from nttmail3.ecl.ntt.co.jp (localhost [127.0.0.1])
	by vcs3.rdh.ecl.ntt.co.jp (8.12.3/8.12.3) with ESMTP id g83Ac0Rp027030;
	Tue, 3 Sep 2002 19:38:00 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69])
	by nttmail3.ecl.ntt.co.jp (8.12.3/8.12.3) with ESMTP id g83AbxxH027744;
	Tue, 3 Sep 2002 19:37:59 +0900 (JST)
Received: from imc.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.9.3/3.7W) with ESMTP id TAA25824;
	Tue, 3 Sep 2002 19:37:59 +0900 (JST)
Received: from barrister.lab.ntt.co.jp
	by imc.m.ecl.ntt.co.jp (8.9.3/3.7W) with ESMTP id TAA00532;
	Tue, 3 Sep 2002 19:37:56 +0900 (JST)
Message-Id: <5.0.2.5.2.20020903161451.041935e8@imc.m.ecl.ntt.co.jp>
X-Sender: sy003@imc.m.ecl.ntt.co.jp
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2-J
Date: Tue, 03 Sep 2002 19:38:59 +0900
To: "Reddy, Vikram" <vikramr@netplane.com>
From: Seisho Yasukawa <yasukawa.seisho@lab.ntt.co.jp>
Subject: Re: Questions/Comments regarding
  draft-yasukawa-mpls-rsvp-multicast
Cc: "'mpls@UU.NET'" <mpls@UU.NET>
In-Reply-To: <E7E13AAF2F3ED41197C100508BD6A328493990@india_exch.hyderaba
 d.mindspeed.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk

Vikram


>1) Can a mulicast address be a part of the TERO (as a Leaf node address).

A multicast address can be a part of the TERO as a Leaf node address 
theoretically.
But we don't assume this case in the first version of our draft.

>     I have in mind a multicast LSP with a sub-tree containing the nodes of
>another muticast group.

We also think a multicast LSP with a sub-tree containing the nodes of another
multicast group is very attractive when considering backbone usage.
We can convey several multicast group's traffic that splits into several 
different
mulitcast LSP in the peripheral networks, in common within the backbone network.
But we think several new mechanism must be developed to realize this application.
Therefore, we are not targeting to discuss this new technology in our draft.

>     If not I would like to know the reason for the following statement in
>section 3.7.1.2
>   "A loose explicit route allows an external routing algorithm to decide the
>route between specified nodes.
>    Multicast routing algorithm such as PIM-SM[8] and MOSPF[9] are examples
>of such algorithms.
>    These routes are selected at each link of the tree. "
>The above statements seem to imply that if there is a loose hop (i.e
>incomplete information at the source),
>then there is a need at the intermediate nodes for the existence of
>multicast routing capabilities to resolve it even further.

This is typo.
Correct example of external routing algorithm is unicast routing algorithm
such as OSPF and IS-IS.


>My question is, if we use only Unicast address as ER hops in the TERO, what
>is the need for the exsitance of
>mulicast information at the intermediate nodes.

We think using multicast address as ER hops in the TERO can provide another
attractive function.
We can setup multicast LSP automatically using L3 multicast routing information
that is constructed by multicast routing algorithm.
We will discuss this mechanism in our future draft.

>2) Typo in Section 4.5.1. Instead of
>    TERO is added to the Resv message.
>   it should be "TERO is added to the Path message. "

Thank you for your comments.
We would like to modify this error in the next draft.

>3) In section 5.1, regarding the statement.
>"This grafting process is initiated not only by the sender node but also by
>the NMS. "
>What is meant by the above statement. I would think that the NMS cannot
>directly signal a grafting
>process. What probably is meant is, the NMS can signal the ingress to
>initiate a grafting process.
>In any case, it is always the ingress which signals a grafting process as
>far as RSVP is considered.
>NMS can never directly signal a grafting process.

We also don't assume the NMS directly signal a grafting process.
As you mentioned above, the meaning of statement is "the NMS can signal
the ingress to initiate a grafting process".

>4) In section 5.2 regarding the statement.
>"This pruning process is initiated not only by the sender node but also by
>the NMS. "
>Same argument as above.

We would like to modify both statements.

>5) After a graft notify/join notify/ prune notify/leave notify are received
>by the ingress, the ingress should
>update the TERO. This is not specified.

We would like to specify this mechanism in the next draft.

>6) Since there are new messages introduced, it would be more helpful if
>there is explicit mention of how each
>message is sent i.e with or withiout router alert etc.

We would also like to specify above point in the next draft.

Thanks,

Seisho 



From owner-mpls@UU.NET  Tue Sep  3 07:58:25 2002
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 ESMTP id HAA22871
	for <mpls-archive@lists.ietf.org>; Tue, 3 Sep 2002 07:58:25 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnesd13567
	for <mpls-archive@lists.ietf.org>; Tue, 3 Sep 2002 11:59:58 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnesd13406;
	Tue, 3 Sep 2002 11:59:53 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnesd01750
	for mpls-outgoing; Tue, 3 Sep 2002 11:59:34 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQnesd01745
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 3 Sep 2002 11:59: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 QQnesd29155
	for <mpls@UU.NET>; Tue, 3 Sep 2002 11:59:14 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnesd11294
	for <mpls@UU.NET>; Tue, 3 Sep 2002 11:59:14 GMT
Received: from celox-ma1-ems1.celoxnetworks.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: celox-ma1-imap1.celoxnetworks.com [12.40.60.233])
	id QQnesd11290
	for <mpls@UU.NET>; Tue, 3 Sep 2002 11:59:14 GMT
Received: by celox-ma1-ems1.celoxnetworks.com with Internet Mail Service (5.5.2653.19)
	id <RBC1BHAH>; Tue, 3 Sep 2002 07:59:14 -0400
Message-ID: <1117F7D44159934FB116E36F4ABF221B0267EA96@celox-ma1-ems1.celoxnetworks.com>
From: "Gray, Eric" <egray@celoxnetworks.com>
To: "'Jin-Hyoung Kim'" <elecrain@chollian.net>
Cc: mpls@UU.NET
Subject: RE: Question about LDP Receive Label Request
Date: Tue, 3 Sep 2002 07:59:10 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C25341.50290380"
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_01C25341.50290380
Content-Type: text/plain

Kim,

 

            See below...

 

Eric W. Gray

Systems Architect

Celox Networks, Inc.

egray@celoxnetworks.com

508 305 7214

 

...
----------------------------------------------------------------------------
-------------
(1) As I know, "Label Request " is only applicable for DoD. But in this
line,       


     it is mentioned as the message is also applicable for Downstream
Unsolicited Independent Control. 


     Is it right?



Label Request is required for DoD and allowed for DU.  Any implementation 
must support handling of Label Requests for both modes.
 
(2) What is "Propagating"?


      Could you tell me the reason why the algorithm check the state, 


     "Has LSR previously received and retained a label  mapping for FEC from
Next Hop?.", 


      and set "Propgating" with "IsPropagating" or "NotPropagating"? What
does it mean?
 
Propagating state might be thought of as indicating - for independent
control
- whether the Label (about to be given) is bound to a downstream Label.
 
(3) As the summary of A.1.1. Recevie Label Request in RFC 3036, the general
procedure of Label Request is as follow:


      - Transmission of a notification ...........


      - Transmission of label mapping .........


      - Transmission of label request ..........


      - Installation of labels ................
      But, in this procedure, the algorithm checks whether the LSR is egress
or the LSR has the labels from the Next Hop.


      As far as I think, it looks like that this procedure must be checked
before Send_Label procedure or Prepare_Label_Mapping_Attributes.


      Why this procedure is performed after Send_Label procedure?


      Is is right?
I need your help.!!
 
It is not likely that you could summarize the steps without over
simplifying.
 
There are many modes to consider and - if it could have been summarized 
as easily as this - it would have been.  :-)
 
If you consider each combination of modes - one at a time - the procedure
you arrive at for each should make sense.  Even then, you need to cover all
of the possible cases (or states) that might exist at the time of receipt of
a
Label Request. You might also look into RFC 3215. These are things you
need to do for yourself.  If you then come up with more specific questions,
you are much more likely to get help.  As it is, you are asking for a simple
explanation of a complex set of instructions that have already been stated 
as simply as possible.
Thanks.    

------_=_NextPart_001_01C25341.50290380
Content-Type: text/html
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=3DUS-ASCII">


<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Gulim;
	panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:GulimChe;
	panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"\@Gulim";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:Gulim;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:GulimChe;}
span.EmailStyle18
	{font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Kim,</span></font></p>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; See
below...</span></font></p>

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

<div>

<p class=3DMsoAutoSig><font size=3D2 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;color:navy'>Eric W. Gray</span></font></p>

<p class=3DMsoAutoSig><font size=3D2 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;color:navy'>Systems =
Architect</span></font></p>

<p class=3DMsoAutoSig><font size=3D2 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;color:navy'>Celox Networks, =
Inc.</span></font></p>

<p class=3DMsoAutoSig><font size=3D2 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;color:navy'>egray@celoxnetworks.com</span></fo=
nt></p>

<p class=3DMsoAutoSig><font size=3D2 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;color:navy'>508 305 7214</span></font></p>

</div>

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

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'><pre><font
size=3D2 color=3Dnavy face=3DGulim><span =
style=3D'font-size:10.0pt;font-family:Gulim;
color:navy'>..</span></font><font size=3D2 face=3DGulim><span =
style=3D'font-size:
10.0pt;font-family:Gulim'>.</span></font></pre><pre><font size=3D2 =
face=3DGulim><span
style=3D'font-size:10.0pt;font-family:Gulim'>---------------------------=
--------------------------------------------------------------</span></f=
ont></pre><pre><font
size=3D2 face=3DGulim><span =
style=3D'font-size:10.0pt;font-family:Gulim'>(1) As I know, &quot;Label =
Request &quot; is only applicable for DoD. But in this line, =
</span></font><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span></font><font
size=3D2 face=3DGulim><span =
style=3D'font-size:10.0pt;font-family:Gulim'> <br
clear=3Dall style=3D'page-break-before:always'>
&nbsp;&nbsp;&nbsp;&nbsp; it is mentioned as the message is also =
applicable for Downstream Unsolicited Independent Control. <br
clear=3Dall style=3D'page-break-before:always'>
&nbsp;&nbsp;&nbsp;&nbsp; Is it right?</span></font></pre><pre><font =
size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><br>
Label Request is required for DoD and allowed for DU.&nbsp; Any =
implementation </span></font></pre><pre><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>must support handling of Label Requests for both =
modes.</span></font></pre><pre><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>&nbsp;</span></font></pre><pre><font size=3D2 =
face=3DGulim><span
style=3D'font-size:10.0pt;font-family:Gulim'>(2) What is =
&quot;Propagating&quot;?<br
clear=3Dall style=3D'page-break-before:always'>
</span></font><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;</span></font><font =
size=3D2
face=3DGulim><span style=3D'font-size:10.0pt;font-family:Gulim'> =
</span></font><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;</span></font><font
size=3D2 face=3DGulim><span =
style=3D'font-size:10.0pt;font-family:Gulim'>Could you tell me the =
reason why the algorithm check the state, <br
clear=3Dall style=3D'page-break-before:always'>
&nbsp;&nbsp;&nbsp;&nbsp; &quot;Has LSR previously received and retained =
a label</span></font><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span></font><font
size=3D2 face=3DGulim><span =
style=3D'font-size:10.0pt;font-family:Gulim'> mapping for FEC from Next =
Hop?.&quot;, <br
clear=3Dall style=3D'page-break-before:always'>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and set &quot;Propgating&quot; with =
&quot;IsPropagating&quot; or &quot;NotPropagating&quot;? What does it =
mean?</span></font></pre><pre><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>&nbsp;</span></font></pre><pre><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Propagating =
state might be thought of as indicating - for independent =
control</span></font></pre><pre><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>- whether the Label (about to be given) is bound to a =
downstream Label.</span></font></pre><pre><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>&nbsp;</span></font></pre><pre><font size=3D2 =
face=3DGulim><span
style=3D'font-size:10.0pt;font-family:Gulim'>(3) As the summary of =
A.1.1. Recevie Label Request in RFC 3036, the general procedure of =
Label Request is as follow:<br
clear=3Dall style=3D'page-break-before:always'>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Transmission of a notification =
...........<br
clear=3Dall style=3D'page-break-before:always'>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Transmission of label =
mapping</span></font><font
face=3DGulim><span style=3D'font-family:Gulim'> .........<br =
clear=3Dall
style=3D'page-break-before:always'>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Transmission of label request =
..........<br
clear=3Dall style=3D'page-break-before:always'>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Installation of labels =
................</span></font></pre><pre><font
size=3D3 face=3DGulim><span =
style=3D'font-size:12.0pt;font-family:Gulim'>&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; But, in this procedure, the algorithm checks whether the LSR is =
egress or the LSR has the labels from the Next Hop.<br
clear=3Dall style=3D'page-break-before:always'>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; As far as I think, it looks like that =
this procedure must be checked before Send_Label procedure or =
</span></font><font
size=3D2 face=3DGulim><span =
style=3D'font-size:10.0pt;font-family:Gulim'>Prepare_Label_Mapping_Attri=
butes</span></font><font
face=3DGulim><span style=3D'font-family:Gulim'>.<br clear=3Dall =
style=3D'page-break-before:
always'>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Why this procedure is performed after =
Send_Label procedure?<br
clear=3Dall style=3D'page-break-before:always'>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Is is =
right?</span></font></pre><pre><font
size=3D3 face=3DGulim><span =
style=3D'font-size:12.0pt;font-family:Gulim'>I need your =
help.!!</span></font></pre><pre><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>&nbsp;</span></font></pre><pre><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>It is not =
likely that you could summarize the steps without over =
simplifying.</span></font></pre><pre><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>&nbsp;</span></font></pre><pre><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>There are many =
modes to consider and - if it could have been summarized =
</span></font></pre><pre><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>as easily as this - it would have been.&nbsp; =
</span></font><font
size=3D2 color=3Dnavy face=3DWingdings><span =
style=3D'font-size:10.0pt;font-family:
Wingdings;color:navy'>J</span></font></pre><pre><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>&nbsp;</span></f=
ont></pre><pre><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>If you consider each combination of modes - one at a time - =
the procedure</span></font></pre><pre><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>you arrive at for each should make sense.&nbsp; Even then, =
you need to cover all</span></font></pre><pre><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>of the possible cases (or states) that might exist at the =
time of receipt of a</span></font></pre><pre><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>Label Request. You might also look into RFC 3215. These are =
things you</span></font></pre><pre><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>need to do for yourself.&nbsp; If you then come up with =
more specific questions,</span></font></pre><pre><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>you are much more likely to get help.&nbsp; As it is, you =
are asking for a simple</span></font></pre><pre><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>explanation of a complex set of instructions that have =
already been stated </span></font></pre><pre><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'>as simply as possible.</span></font></pre><pre><font =
size=3D3
face=3DGulim><span =
style=3D'font-size:12.0pt;font-family:Gulim'>Thanks.</span></font><font
face=3D"Courier New"><span style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;</span></font><font
face=3DGulim><span style=3D'font-family:Gulim'> =
</span></font></pre></div>

</div>

</body>

</html>

------_=_NextPart_001_01C25341.50290380--


From owner-mpls@UU.NET  Tue Sep  3 09:57:29 2002
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 ESMTP id JAA27292
	for <mpls-archive@lists.ietf.org>; Tue, 3 Sep 2002 09:57:29 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnesl03999
	for <mpls-archive@lists.ietf.org>; Tue, 3 Sep 2002 13:59:02 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnesl03059;
	Tue, 3 Sep 2002 13:58:35 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnesl28176
	for mpls-outgoing; Tue, 3 Sep 2002 13:58:09 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQnesl28171
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 3 Sep 2002 13:58: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 QQnesl22184
	for <mpls@UU.NET>; Tue, 3 Sep 2002 13:57:59 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnesl16770
	for <mpls@UU.NET>; Tue, 3 Sep 2002 13:57:59 GMT
Received: from web21001.mail.yahoo.com by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web21001.mail.yahoo.com [216.136.227.55])
	id QQnesl16765
	for <mpls@UU.NET>; Tue, 3 Sep 2002 13:57:59 GMT
Message-ID: <20020903135758.13741.qmail@web21001.mail.yahoo.com>
Received: from [204.192.44.242] by web21001.mail.yahoo.com via HTTP; Tue, 03 Sep 2002 06:57:58 PDT
Date: Tue, 3 Sep 2002 06:57:58 -0700 (PDT)
From: Carlos Patriawan <carlos_mpls@yahoo.com>
Subject: RE: Question about LDP Receive Label Request
To: "Gray, Eric" <egray@celoxnetworks.com>,
        "'Jin-Hyoung Kim'" <elecrain@chollian.net>
Cc: mpls@UU.NET
In-Reply-To: <1117F7D44159934FB116E36F4ABF221B0267EA96@celox-ma1-ems1.celoxnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk


> (2) What is "Propagating"?
> 
> 
>       Could you tell me the reason why the algorithm
> check the state, 
> 
> 
>      "Has LSR previously received and retained a
> label  mapping for FEC from
> Next Hop?.", 
> 
> 
>       and set "Propgating" with "IsPropagating" or
> "NotPropagating"? What
> does it mean?
>  
> Propagating state might be thought of as indicating
> - for independent
> control
> - whether the Label (about to be given) is bound to
> a down

Yes, Indeed it's needed by the LSR to avoid receiving
another label for the same FEC when it comes from the
same downstream(next-hop) LSR. This condition should
be prohibited when LSR already has a label value for
the same FEC/next-hop LSR. If the condition is allowed
then ILM table may get confused.


Carlos Patriawan

__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com


From owner-mpls@UU.NET  Wed Sep  4 02:02:55 2002
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 ESMTP id CAA26904
	for <mpls-archive@lists.ietf.org>; Wed, 4 Sep 2002 02:02:55 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQneuy22313
	for <mpls-archive@lists.ietf.org>; Wed, 4 Sep 2002 06:04:29 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQneuy22274;
	Wed, 4 Sep 2002 06:04:27 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQneuy04264
	for mpls-outgoing; Wed, 4 Sep 2002 06:03:56 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQneuy04255
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 4 Sep 2002 06:03:40 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 QQneuy06409
	for <mpls@uu.net>; Wed, 4 Sep 2002 06:02:16 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQneuy05198
	for <mpls@uu.net>; Wed, 4 Sep 2002 06:02:15 GMT
Received: from funnel.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQneuy05194
	for <mpls@uu.net>; Wed, 4 Sep 2002 06:02:14 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id CAA28557 for <mpls@uu.net>; Wed, 4 Sep 2002 02:02:14 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8462EI14194 for mpls@uu.net; Wed, 4 Sep 2002 02:02:14 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQneux20936
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 4 Sep 2002 05:58:57 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 QQneux09671
	for <mpls@UU.NET>; Wed, 4 Sep 2002 05:57:53 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQneux17382
	for <mpls@UU.NET>; Wed, 4 Sep 2002 05:57:53 GMT
Received: from mailFA11.rediffmail.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: [203.199.83.246])
	id QQneux17361
	for <mpls@UU.NET>; Wed, 4 Sep 2002 05:57:52 GMT
Received: (qmail 19128 invoked by uid 510); 4 Sep 2002 05:57:32 -0000
Date: 4 Sep 2002 05:57:32 -0000
Message-ID: <20020904055732.19127.qmail@mailFA11.rediffmail.com>
Received: from unknown (203.200.20.226) by rediffmail.com via HTTP; 04 sep 2002 05:57:32 -0000
MIME-Version: 1.0
From: "Harish  Kumtakar" <harishk3@rediffmail.com>
Reply-To: "Harish  Kumtakar" <harishk3@rediffmail.com>
To: rsvp@isi.edu
Cc: schultz@io.iol.unh.edu, mpls@UU.NET
Subject: help
Content-type: text/plain;
	format=flowed
Content-Disposition: inline
Sender: owner-mpls@UU.NET
Precedence: bulk

hi,

    what i understood after reading RFC 2205 and 2209 is that, 
when a node receives a PATH message it will store or update the 
info. contained in the message into corresponding PATH state and 
then forwards the PATH message (the message may be modified) to 
the next hop.

   my question is will that node stores the info that is modified 
by it(in case the PATH message is modified) somewhere (i mean, in 
some state?).



From owner-mpls@UU.NET  Wed Sep  4 02:17:49 2002
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 ESMTP id CAA06063
	for <mpls-archive@lists.ietf.org>; Wed, 4 Sep 2002 02:17:49 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQneuz10476
	for <mpls-archive@lists.ietf.org>; Wed, 4 Sep 2002 06:19:24 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQneuz10425;
	Wed, 4 Sep 2002 06:19:22 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQneuz17258
	for mpls-outgoing; Wed, 4 Sep 2002 06:18:55 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQneuz17249
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 4 Sep 2002 06:18: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 QQneuz15860
	for <mpls@UU.NET>; Wed, 4 Sep 2002 06:17:03 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQneuz18270
	for <mpls@UU.NET>; Wed, 4 Sep 2002 06:17:02 GMT
Received: from mailhost.metro-optix.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [64.219.248.6])
	id QQneuz18264
	for <mpls@UU.NET>; Wed, 4 Sep 2002 06:17:02 GMT
Received: by mailhost.metro-optix.com with Internet Mail Service (5.5.2653.19)
	id <QLW5ZZVX>; Wed, 4 Sep 2002 01:12:50 -0500
Message-ID: <99EC34181384D611BE56000347227B2C01EAE3@MAILHOSTNB>
From: Apratim Mukherjee <apratim.mukherjee@metro-optix.com>
To: "'Harish  Kumtakar'" <harishk3@rediffmail.com>, rsvp@isi.edu
Cc: mpls@UU.NET
Subject: RE: help
Date: Wed, 4 Sep 2002 11:47:59 -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

hi harish,

normally , you would store the incoming and outgoing object separately in
the Path State since you need the incoming object to check for changes in
the incoming refresh message while you need the outgoing object while
buiding the Path Refresh message. Sometimes , the outgoing object can be
calculated every time you send a refresh , but this is implementation
dependant .
e.g OutAdspec could be stored as a separate field or recalculated every time
u send a refresh . 
OutIntegrity could be stored as a separate field which is recalculated evry
time an outgoing object changes or it could be recalculated while sending
each refresh message. 


-----Original Message-----
From: Harish Kumtakar [mailto:harishk3@rediffmail.com]
Sent: Wednesday, September 04, 2002 11:28 AM
To: rsvp@isi.edu
Cc: schultz@io.iol.unh.edu; mpls@UU.NET
Subject: help


hi,

    what i understood after reading RFC 2205 and 2209 is that, 
when a node receives a PATH message it will store or update the 
info. contained in the message into corresponding PATH state and 
then forwards the PATH message (the message may be modified) to 
the next hop.

   my question is will that node stores the info that is modified 
by it(in case the PATH message is modified) somewhere (i mean, in 
some state?).


From owner-mpls@UU.NET  Wed Sep  4 08:25:55 2002
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 ESMTP id IAA24836
	for <mpls-archive@lists.ietf.org>; Wed, 4 Sep 2002 08:25:55 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnevx13070
	for <mpls-archive@lists.ietf.org>; Wed, 4 Sep 2002 12:27:29 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnevx12974;
	Wed, 4 Sep 2002 12:27:26 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnevx08924
	for mpls-outgoing; Wed, 4 Sep 2002 12:27:00 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnevx08918
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 4 Sep 2002 12:26: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 QQnevx03393
	for <mpls@UU.NET>; Wed, 4 Sep 2002 12:25:48 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnevx11811
	for <mpls@UU.NET>; Wed, 4 Sep 2002 12:25:48 GMT
Received: from xover.netplane.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: fwout.maker.com [12.27.183.253] (may be forged))
	id QQnevx11798
	for <mpls@UU.NET>; Wed, 4 Sep 2002 12:25:47 GMT
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2653.19)
	id <S1D0AQL0>; Wed, 4 Sep 2002 08:25:47 -0400
Message-ID: <E7E13AAF2F3ED41197C100508BD6A32849399D@india_exch.hyderabad.mindspeed.com>
From: "Reddy, Vikram" <vikramr@netplane.com>
To: "'Seisho Yasukawa'" <yasukawa.seisho@lab.ntt.co.jp>
Cc: "'mpls@UU.NET'" <mpls@UU.NET>
Subject: RE: Questions/Comments regarding draft-yasukawa-mpls-rsvp-multica
	st
Date: Wed, 4 Sep 2002 08:28:10 -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

Hello Yasukawa-san,

I have one more question regarding the draft. The following is from the
draft.

   Either the intermediate node or the leaf node may calculate the
   multicast tree route in order to decentralize this calculation. So
   all nodes belonging to the same multicast group need to have
   information about the whole multicast tree topology in order to
   prevent intersection of multicast tree.  Each node MUST NOT delete
   the TERO subobjects that specify nodes on the explicitly routed path
   in order to get the whole multicast tree topology information. Each
   node MAY record the whole multicast tree topology from TERO. In this
   way, all nodes can have the same information about the whole
   multicast tree topology.

The above states that all the nodes in the multicast tree have to have 
the full information about the multicast tree. 
I would like to know the technical reasons for this requirement. 
The obvious drawbacks with this requirement is the increase in the
the message sizes with the increase in the number of nodes.

In my opinion, if every node maintains the previous hop and the
next hop(s) information, it should be enough, unless you see some
specific technical reason for the above information. If it is 
only for the NMS show/information/display purpose, I feel it
is better to do it at the source node itself and thus remove this 
requirement.

Thanks,
Vikram.





-----Original Message-----
From: Seisho Yasukawa [mailto:yasukawa.seisho@lab.ntt.co.jp]
Sent: Tuesday, September 03, 2002 4:09 PM
To: Reddy, Vikram
Cc: 'mpls@UU.NET'
Subject: Re: Questions/Comments regarding
draft-yasukawa-mpls-rsvp-multicast


Vikram


>1) Can a mulicast address be a part of the TERO (as a Leaf node address).

A multicast address can be a part of the TERO as a Leaf node address 
theoretically.
But we don't assume this case in the first version of our draft.

>     I have in mind a multicast LSP with a sub-tree containing the nodes of
>another muticast group.

We also think a multicast LSP with a sub-tree containing the nodes of
another
multicast group is very attractive when considering backbone usage.
We can convey several multicast group's traffic that splits into several 
different
mulitcast LSP in the peripheral networks, in common within the backbone
network.
But we think several new mechanism must be developed to realize this
application.
Therefore, we are not targeting to discuss this new technology in our draft.

>     If not I would like to know the reason for the following statement in
>section 3.7.1.2
>   "A loose explicit route allows an external routing algorithm to decide
the
>route between specified nodes.
>    Multicast routing algorithm such as PIM-SM[8] and MOSPF[9] are examples
>of such algorithms.
>    These routes are selected at each link of the tree. "
>The above statements seem to imply that if there is a loose hop (i.e
>incomplete information at the source),
>then there is a need at the intermediate nodes for the existence of
>multicast routing capabilities to resolve it even further.

This is typo.
Correct example of external routing algorithm is unicast routing algorithm
such as OSPF and IS-IS.


>My question is, if we use only Unicast address as ER hops in the TERO, what
>is the need for the exsitance of
>mulicast information at the intermediate nodes.

We think using multicast address as ER hops in the TERO can provide another
attractive function.
We can setup multicast LSP automatically using L3 multicast routing
information
that is constructed by multicast routing algorithm.
We will discuss this mechanism in our future draft.

>2) Typo in Section 4.5.1. Instead of
>    TERO is added to the Resv message.
>   it should be "TERO is added to the Path message. "

Thank you for your comments.
We would like to modify this error in the next draft.

>3) In section 5.1, regarding the statement.
>"This grafting process is initiated not only by the sender node but also by
>the NMS. "
>What is meant by the above statement. I would think that the NMS cannot
>directly signal a grafting
>process. What probably is meant is, the NMS can signal the ingress to
>initiate a grafting process.
>In any case, it is always the ingress which signals a grafting process as
>far as RSVP is considered.
>NMS can never directly signal a grafting process.

We also don't assume the NMS directly signal a grafting process.
As you mentioned above, the meaning of statement is "the NMS can signal
the ingress to initiate a grafting process".

>4) In section 5.2 regarding the statement.
>"This pruning process is initiated not only by the sender node but also by
>the NMS. "
>Same argument as above.

We would like to modify both statements.

>5) After a graft notify/join notify/ prune notify/leave notify are received
>by the ingress, the ingress should
>update the TERO. This is not specified.

We would like to specify this mechanism in the next draft.

>6) Since there are new messages introduced, it would be more helpful if
>there is explicit mention of how each
>message is sent i.e with or withiout router alert etc.

We would also like to specify above point in the next draft.

Thanks,

Seisho 


From owner-mpls@UU.NET  Wed Sep  4 09:04:43 2002
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 ESMTP id JAA26536
	for <mpls-archive@lists.ietf.org>; Wed, 4 Sep 2002 09:04:43 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnewa14553
	for <mpls-archive@lists.ietf.org>; Wed, 4 Sep 2002 13:06:17 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnewa14345;
	Wed, 4 Sep 2002 13:06:11 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnewa04340
	for mpls-outgoing; Wed, 4 Sep 2002 13:05:57 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnewa03600
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 4 Sep 2002 13:05: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 QQnewa08314
	for <mpls@uu.net>; Wed, 4 Sep 2002 13:05:27 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnewa14017
	for <mpls@uu.net>; Wed, 4 Sep 2002 13:05:27 GMT
Received: from mail.san.yahoo.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail.san.yahoo.com [209.132.1.30])
	id QQnewa14013
	for <mpls@uu.net>; Wed, 4 Sep 2002 13:05:26 GMT
Received: from [66.44.48.136] by mail.san.yahoo.com with HTTP; Wed, 4 Sep 2002 06:08:20 -0700
Date: Wed, 4 Sep 2002 09:08:20 -0400
Message-ID: <3D7545D900000682@mta05.san.yahoo.com>
From: "Kavita Khanna" <kkhanna@isocore.com>
Subject: MPLS 2002 Registration - Oct 27-29, Washington, DC
To: mpls@UU.NET
MIME-Version: 1.0
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 JAA26536

                 MPLS2002 International Conference
           5th Annual International Conference on MPLS
                           October 27-29, 2002
               Omni Shoreham Hotel, Washington, DC

     Worldcom, Cable & Wireless, France Telecom and NTT

                        Program Schedule

               Tutorials: Oct 27, 1:00-6:00 pm
         Conference sessions: October 28-29 8:30am-6:00pm
        Exhibits: Oct 28, 8:30am-7:00 & Oct 28, 8:30am-3:00pm
           3rd Public Inter-Op Demo: October 30

 Important Dates:
 - Early Registration Rates Cut-Off Date: Sept 30
 - Hotel Rate Cut-Off Date: Sept 30

You are cordially invited to attend the MPLS 2002 International Conference
to be held in Washington DC, Oct. 27-29. MPLS 2002, the 5th annual International
Conference on MPLS, co-hosted by major service providers is being sponsored
by Agilent Technologies, Alcatel, Avici Systems, Cisco Systems, CoSine Communications,
IXIA, Laurel Networks, NetTest, Nortel Networks, Redback Networks and Spirent
Communications. Sponsors will be exhibiting their products and services
throughout Monday and Tuesday.

We hope you would be able to actively participate in MPLS 2002 International
Conference. The event consists of a two-day highly technical sessions, preceded
by six technical tutorials.

MPLS2002 offers an excellent blend of topics including deployment, application,
and management aspects of MPLS.  The updated tutorials and technical sessions
have been posted at MPLS 2002 web site under "Program" section (http://www.mpls2002.com/sessions.htm).

Registration for the conference is open and you may register for MPLS 2002
either On-line or Off-line by visiting http://www.mpls2002.com/registration.htm
and following the instructions. The early registration fees are extremely
attractive and we hope that you can benefit from the opportunity and pre-register
for MPLS2002 soon. Pre-registration rates are valid till September 30.

If you are planning to attend MPLS 2002, you may want to make your hotel
reservations now as we have blocked limited number of rooms at Omni Shoreham
Hotel (Conference Venue and the designated hotel) at special rates. In order
to benefit from the discounted conference rate, we urge you to make your
reservations immediately. You may visit (http://www.mpls2002.com/hotels.htm)
for more information on hotel reservations.

For any additional information, please visit:
   http://www.mpls2002.com

We look forward to seeing you in the MPLS 2002 International Conference.

Regards,



From owner-mpls@UU.NET  Wed Sep  4 09:21:53 2002
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 ESMTP id JAA27411
	for <mpls-archive@lists.ietf.org>; Wed, 4 Sep 2002 09:21:53 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnewb29912
	for <mpls-archive@lists.ietf.org>; Wed, 4 Sep 2002 13:23:26 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnewb29860;
	Wed, 4 Sep 2002 13:23:25 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnewb07524
	for mpls-outgoing; Wed, 4 Sep 2002 13:23:01 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQnewb07517
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 4 Sep 2002 13:23: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 QQnewb02512
	for <mpls@uu.net>; Wed, 4 Sep 2002 13:22:04 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnewb29037
	for <mpls@uu.net>; Wed, 4 Sep 2002 13:22:04 GMT
Received: from funnel.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnewb29023
	for <mpls@uu.net>; Wed, 4 Sep 2002 13:22:03 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id JAA16455 for <mpls@uu.net>; Wed, 4 Sep 2002 09:22:03 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g84DM3a29025 for mpls@uu.net; Wed, 4 Sep 2002 09:22:03 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnewb07450
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 4 Sep 2002 13:21: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 QQnewb26425
	for <mpls@uu.net>; Wed, 4 Sep 2002 13:20:53 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnewb28501
	for <mpls@uu.net>; Wed, 4 Sep 2002 13:20:53 GMT
Received: from vivacenetworks.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [64.221.212.131])
	id QQnewb28495
	for <mpls@uu.net>; Wed, 4 Sep 2002 13:20:52 GMT
Received: from AMALIS.vivacenetworks.com ([10.120.0.2] RDNS failed) by vivacenetworks.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Wed, 4 Sep 2002 06:20:47 -0700
Message-Id: <5.1.0.14.2.20020904092012.08bdcc90@po1.vivacenetworks.com>
X-Sender: vivacenet\amalis@po1.vivacenetworks.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 04 Sep 2002 09:20:42 -0400
To: "Kavita Khanna" <kkhanna@isocore.com>
From: "Andrew G. Malis" <Andy.Malis@vivacenetworks.com>
Subject: Re: MPLS 2002 Registration - Oct 27-29, Washington, DC
Cc: <mpls@UU.NET>
In-Reply-To: <3D7545D900000682@mta05.san.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 04 Sep 2002 13:20:47.0887 (UTC) FILETIME=[E1C8B9F0:01C25415]
Sender: owner-mpls@UU.NET
Precedence: bulk

Kavita,

I assume speakers are automatically registered?  If not, is there anything 
we need to fill out?

Thanks,
Andy

-------

At 9/4/2002 06:08 AM -0700, Kavita Khanna wrote:

>                  MPLS2002 International Conference
>            5th Annual International Conference on MPLS
>                            October 27-29, 2002
>                Omni Shoreham Hotel, Washington, DC
>
>      Worldcom, Cable & Wireless, France Telecom and NTT
>
>                         Program Schedule
>
>                Tutorials: Oct 27, 1:00-6:00 pm
>          Conference sessions: October 28-29 8:30am-6:00pm
>         Exhibits: Oct 28, 8:30am-7:00 & Oct 28, 8:30am-3:00pm
>            3rd Public Inter-Op Demo: October 30
>
>  Important Dates:
>  - Early Registration Rates Cut-Off Date: Sept 30
>  - Hotel Rate Cut-Off Date: Sept 30
>
>You are cordially invited to attend the MPLS 2002 International Conference
>to be held in Washington DC, Oct. 27-29. MPLS 2002, the 5th annual 
>International
>Conference on MPLS, co-hosted by major service providers is being sponsored
>by Agilent Technologies, Alcatel, Avici Systems, Cisco Systems, CoSine 
>Communications,
>IXIA, Laurel Networks, NetTest, Nortel Networks, Redback Networks and Spirent
>Communications. Sponsors will be exhibiting their products and services
>throughout Monday and Tuesday.
>
>We hope you would be able to actively participate in MPLS 2002 International
>Conference. The event consists of a two-day highly technical sessions, 
>preceded
>by six technical tutorials.
>
>MPLS2002 offers an excellent blend of topics including deployment, 
>application,
>and management aspects of MPLS.  The updated tutorials and technical sessions
>have been posted at MPLS 2002 web site under "Program" section 
>(<http://www.mpls2002.com/sessions.htm>http://www.mpls2002.com/sessions.htm).
>
>Registration for the conference is open and you may register for MPLS 2002
>either On-line or Off-line by visiting 
><http://www.mpls2002.com/registration.htm>http://www.mpls2002.com/registration.htm 
>
>and following the instructions. The early registration fees are extremely
>attractive and we hope that you can benefit from the opportunity and 
>pre-register
>for MPLS2002 soon. Pre-registration rates are valid till September 30.
>
>If you are planning to attend MPLS 2002, you may want to make your hotel
>reservations now as we have blocked limited number of rooms at Omni Shoreham
>Hotel (Conference Venue and the designated hotel) at special rates. In order
>to benefit from the discounted conference rate, we urge you to make your
>reservations immediately. You may visit 
>(<http://www.mpls2002.com/hotels.htm>http://www.mpls2002.com/hotels.htm)
>for more information on hotel reservations.
>
>For any additional information, please visit:
>    <http://www.mpls2002.com>http://www.mpls2002.com
>
>We look forward to seeing you in the MPLS 2002 International Conference.
>
>Regards,



From owner-mpls@UU.NET  Wed Sep  4 09:49:57 2002
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 ESMTP id JAA29412
	for <mpls-archive@lists.ietf.org>; Wed, 4 Sep 2002 09:49:56 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnewd16300
	for <mpls-archive@lists.ietf.org>; Wed, 4 Sep 2002 13:51:31 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnewd16219;
	Wed, 4 Sep 2002 13:51:28 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnewd09495
	for mpls-outgoing; Wed, 4 Sep 2002 13:51:11 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnewd09488
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 4 Sep 2002 13:51:05 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 QQnewd01582
	for <mpls@UU.NET>; Wed, 4 Sep 2002 13:50:56 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnewd19586
	for <mpls@UU.NET>; Wed, 4 Sep 2002 13:50:56 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 QQnewd19582
	for <mpls@UU.NET>; Wed, 4 Sep 2002 13:50:55 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 JAA22901
	for <mpls@UU.NET>; Wed, 4 Sep 2002 09:50:53 -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 JAA20805
	for <mpls@UU.NET>; Wed, 4 Sep 2002 09:50:55 -0400 (EDT)
Message-ID: <3D760FD6.1020500@marconi.com>
Date: Wed, 04 Sep 2002 09:51:18 -0400
From: David Charlap <David.Charlap@marconi.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1b) Gecko/20020826
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: IETF MPLS List <mpls@UU.NET>
Subject: Re: help
References: <20020904055732.19127.qmail@mailFA11.rediffmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Harish Kumtakar wrote:
> 
>    what i understood after reading RFC 2205 and 2209 is that, when a 
> node receives a PATH message it will store or update the info. contained 
> in the message into corresponding PATH state and then forwards the PATH 
> message (the message may be modified) to the next hop.

Actually, the outgoing message will always be different from the 
incoming message.  At the very least, the HOP object will be different.

It's misleading to think that a Path/Resv message is forwarded.  It is 
not.  It is intercepted and processed.  A new Path/Resv message may (or 
may not, depending on circumstances) be generated as a result of that 
processing.

>   my question is will that node stores the info that is modified by 
> it(in case the PATH message is modified) somewhere (i mean, in some 
> state?).

I'm not sure what you're asking here.

Every node must (at minimum) store everything from an incoming Path/Resv 
message.  It must compare subsequent messages with the stored data in 
order to determine if the subsequent message is a modification or a refresh.

What additional information it stores in order to generate and send any 
corresponding outgoing message is an implementation detail and is not 
specified by any standard.

-- David



From owner-mpls@UU.NET  Wed Sep  4 09:54:44 2002
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 ESMTP id JAA29717
	for <mpls-archive@lists.ietf.org>; Wed, 4 Sep 2002 09:54:43 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnewd02244
	for <mpls-archive@lists.ietf.org>; Wed, 4 Sep 2002 13:56:19 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnewd02209;
	Wed, 4 Sep 2002 13:56:17 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnewd09793
	for mpls-outgoing; Wed, 4 Sep 2002 13:55:51 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQnewd09767
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 4 Sep 2002 13:55: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 QQnewd21849
	for <mpls@UU.NET>; Wed, 4 Sep 2002 13:55:22 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnewd24677
	for <mpls@UU.NET>; Wed, 4 Sep 2002 13:55:21 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 QQnewd24657
	for <mpls@UU.NET>; Wed, 4 Sep 2002 13:55:21 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 JAA23288
	for <mpls@UU.NET>; Wed, 4 Sep 2002 09:55:15 -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 JAA21609
	for <mpls@UU.NET>; Wed, 4 Sep 2002 09:55:16 -0400 (EDT)
Message-ID: <3D7610DC.7000004@marconi.com>
Date: Wed, 04 Sep 2002 09:55:40 -0400
From: David Charlap <David.Charlap@marconi.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1b) Gecko/20020826
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: mpls@UU.NET
Subject: Re: help
References: <99EC34181384D611BE56000347227B2C01EAE3@MAILHOSTNB>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Apratim Mukherjee wrote:
> 
> e.g OutAdspec could be stored as a separate field or recalculated every time
> u send a refresh . 
> OutIntegrity could be stored as a separate field which is recalculated evry
> time an outgoing object changes or it could be recalculated while sending
> each refresh message. 

Note that you can not store an INTEGRITY object.  The INTEGRITY sequence 
number must increment for each message sent.  If it doesn't, the 
neighbor is supposed to drop the message.  And that sequence number is 
computed as part of the digest.  Which means you must reconstruct the 
INTEGRITY object for every message sent.

It also means that incoming INTEGRITY objects should not be stored, 
since refresh messages won't have the same INTEGRITY object anyway. 
Once a message is authenticated, there is no further use for the 
INTEGRITY object.

ADSPEC is a good example of an object that may be retained or 
recomputed.  Other good examples include HOP objects, FLOWSPEC objects 
(in Resv messages), and RECORD_ROUTE objects.

-- David



From owner-mpls@UU.NET  Wed Sep  4 12:54:29 2002
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 ESMTP id MAA09907
	for <mpls-archive@lists.ietf.org>; Wed, 4 Sep 2002 12:54:29 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnewp11479
	for <mpls-archive@lists.ietf.org>; Wed, 4 Sep 2002 16:56:01 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnewp11360;
	Wed, 4 Sep 2002 16:55:59 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnewp06065
	for mpls-outgoing; Wed, 4 Sep 2002 16:55:46 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQnewp06049
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 4 Sep 2002 16:55: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 QQnewp08215
	for <mpls@UU.NET>; Wed, 4 Sep 2002 16:54:47 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnewp18539
	for <mpls@UU.NET>; Wed, 4 Sep 2002 16:54:47 GMT
Received: from ariadne.dt.fee.unicamp.br by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: dt.fee.unicamp.br [143.106.8.45])
	id QQnewp18525
	for <mpls@UU.NET>; Wed, 4 Sep 2002 16:54:46 GMT
Received: from calipso.dt.fee.unicamp.br (calipso.dt.fee.unicamp.br [143.106.12.37])
	by ariadne.dt.fee.unicamp.br (8.9.3/8.9.3) with ESMTP id NAA15765;
	Wed, 4 Sep 2002 13:54:27 -0300 (EST)
Date: Wed, 4 Sep 2002 13:53:29 -0300 (EST)
From: Marcos Antonio De Almeida Cora <cora@dt.fee.unicamp.br>
To: mpls@UU.NET, gmpls-ops@mplsrc.com, ccamp@ops.ietf.org
Subject: Doubt on OBGP
Message-ID: <Pine.GSO.4.10.10209041345001.22392-100000@calipso.dt.fee.unicamp.br>
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 all, 

 My name is Marcos, I'm MSc Student of School of
Electrical and Computer Engineering (http://www.fee.unicamp.br) of State
University of Campinas (http://www.unicamp.br), Brazil.

 I have a doubt on OBGP. I'd like to know if GMPLS support OBGP as a
signaling protocol or only CR-LDP and RSVP-TE is used ???

 If yes, where can I find informations about it.

 Thanks, 

        Marcos

_________________________________________________________________

  Marcos Ant鬾io de Almeida Cor�    
  School of Electrical and Computer Engineering
  Departament of Telematics
  State University of Campinas/Brazil - UNICAMP
  Phone: +55 (19) 3788.3711 - Branch: 73723   
  Home Page: www.dt.fee.unicamp.br/~cora
_________________________________________________________________





From owner-mpls@UU.NET  Wed Sep  4 13:05:23 2002
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 ESMTP id NAA10515
	for <mpls-archive@lists.ietf.org>; Wed, 4 Sep 2002 13:05:23 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnewq27255
	for <mpls-archive@lists.ietf.org>; Wed, 4 Sep 2002 17:06:57 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnewq27200;
	Wed, 4 Sep 2002 17:06:55 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnewq29729
	for mpls-outgoing; Wed, 4 Sep 2002 17:06:27 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnewq29704
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 4 Sep 2002 17:06: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 QQnewq24814
	for <mpls@UU.NET>; Wed, 4 Sep 2002 17:05:53 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnewq26332
	for <mpls@UU.NET>; Wed, 4 Sep 2002 17:05:53 GMT
Received: from celox-ma1-ems1.celoxnetworks.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: celox-ma1-imap1.celoxnetworks.com [12.40.60.233])
	id QQnewq26325
	for <mpls@UU.NET>; Wed, 4 Sep 2002 17:05:53 GMT
Received: by celox-ma1-ems1.celoxnetworks.com with Internet Mail Service (5.5.2653.19)
	id <RBC1BM6W>; Wed, 4 Sep 2002 13:05:53 -0400
Message-ID: <1117F7D44159934FB116E36F4ABF221B0267EAA0@celox-ma1-ems1.celoxnetworks.com>
From: "Gray, Eric" <egray@celoxnetworks.com>
To: "'David Charlap'" <David.Charlap@marconi.com>
Cc: IETF MPLS List <mpls@UU.NET>
Subject: RE: help
Date: Wed, 4 Sep 2002 13:05:52 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk


To add to what David has said, there is a predictable
transformation that is performed on a received RSVP
Path message before a corresponding Path messages is
sent downstream.  It is up to the implementation to make
the decision as to which is more optimal - storing a
version of the result of this transformation (with at
least some of the values to be re-transmitted), or 
repeating the entire transformation each time.

Optimizations that apply to your implementation may not
apply to others.  Numerous optimizations are not only
possible, but obvious.

> -----Original Message-----
> From: David Charlap [mailto:David.Charlap@marconi.com]
> Sent: Wednesday, September 04, 2002 9:51 AM
> To: IETF MPLS List
> Subject: Re: help
> 
> Harish Kumtakar wrote:
> >
> >    what i understood after reading RFC 2205 and 2209 is that, when a
> > node receives a PATH message it will store or update the info. contained
> > in the message into corresponding PATH state and then forwards the PATH
> > message (the message may be modified) to the next hop.
> 
> Actually, the outgoing message will always be different from the
> incoming message.  At the very least, the HOP object will be different.
> 
> It's misleading to think that a Path/Resv message is forwarded.  It is
> not.  It is intercepted and processed.  A new Path/Resv message may (or
> may not, depending on circumstances) be generated as a result of that
> processing.
> 
> >   my question is will that node stores the info that is modified by
> > it(in case the PATH message is modified) somewhere (i mean, in some
> > state?).
> 
> I'm not sure what you're asking here.
> 
> Every node must (at minimum) store everything from an incoming Path/Resv
> message.  It must compare subsequent messages with the stored data in
> order to determine if the subsequent message is a modification or a
> refresh.
> 
> What additional information it stores in order to generate and send any
> corresponding outgoing message is an implementation detail and is not
> specified by any standard.
> 
> -- David


Eric W. Gray
Systems Architect
Celox Networks, Inc.
egray@celoxnetworks.com
508 305 7214


From owner-mpls@UU.NET  Wed Sep  4 14:00:45 2002
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 ESMTP id OAA13435
	for <mpls-archive@lists.ietf.org>; Wed, 4 Sep 2002 14:00:45 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnewu05814
	for <mpls-archive@lists.ietf.org>; Wed, 4 Sep 2002 18:02:19 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnewu05698;
	Wed, 4 Sep 2002 18:02:16 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnewu15598
	for mpls-outgoing; Wed, 4 Sep 2002 18:01:54 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQnewu15192
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 4 Sep 2002 18:01:50 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 QQnewu25155
	for <mpls@UU.NET>; Wed, 4 Sep 2002 18:01:02 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnewu02245
	for <mpls@UU.NET>; Wed, 4 Sep 2002 18:01:01 GMT
Received: from c2.ciena.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [63.118.32.25])
	id QQnewu02230
	for <mpls@UU.NET>; Wed, 4 Sep 2002 18:01:01 GMT
Received: by c2.ciena.com (8.8.8+Sun/SMI-SVR4-8.0)
	id OAA19416; Wed, 4 Sep 2002 14:00:52 -0400 (EDT)
Received: from wntcsdexg02.csd.ciena.com(10.128.2.168) by c2.ciena.com via smap (V2.0)
	id xma019212; Wed, 4 Sep 02 14:00:10 -0400
Received: by wntcsdexg02.csd.ciena.com with Internet Mail Service (5.5.2653.19)
	id <PF7ZZYXZ>; Wed, 4 Sep 2002 11:00:09 -0700
Message-ID: <2135200C183FD5119588009027DE5723FD3326@wntcsdexg02.csd.ciena.com>
From: "Ong, Lyndon" <LyOng@ciena.com>
To: "'Marcos Antonio De Almeida Cora'" <cora@dt.fee.unicamp.br>, mpls@UU.NET,
        gmpls-ops@mplsrc.com, ccamp@ops.ietf.org
Subject: RE: Doubt on OBGP
Date: Wed, 4 Sep 2002 11:00: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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA13435

Hi Marcos,

If you mean Optical BGP, this would be for multi-area
routing, not signaling.  I believe ccamp is not yet
chartered to address multi-area routing, or at least
has not seriously taken this issue up at this point.

Also, the status of CR-LDP extensions for GMPLS is not 
clear given that there has been a push to cap work
on CR-LDP.  Is this still going for Proposed Standard,
or will this become Informational?

Cheers,

L. Ong
Ciena

-----Original Message-----
From: Marcos Antonio De Almeida Cora [mailto:cora@dt.fee.unicamp.br]
Sent: Wednesday, September 04, 2002 9:53 AM
To: mpls@UU.NET; gmpls-ops@mplsrc.com; ccamp@ops.ietf.org
Subject: Doubt on OBGP



 Hi all, 

 My name is Marcos, I'm MSc Student of School of
Electrical and Computer Engineering (http://www.fee.unicamp.br) of State
University of Campinas (http://www.unicamp.br), Brazil.

 I have a doubt on OBGP. I'd like to know if GMPLS support OBGP as a
signaling protocol or only CR-LDP and RSVP-TE is used ???

 If yes, where can I find informations about it.

 Thanks, 

        Marcos

_________________________________________________________________

  Marcos Ant鬾io de Almeida Cor�    
  School of Electrical and Computer Engineering
  Departament of Telematics
  State University of Campinas/Brazil - UNICAMP
  Phone: +55 (19) 3788.3711 - Branch: 73723   
  Home Page: www.dt.fee.unicamp.br/~cora
_________________________________________________________________





From owner-mpls@UU.NET  Thu Sep  5 07:21:24 2002
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 ESMTP id HAA15231
	for <mpls-archive@lists.ietf.org>; Thu, 5 Sep 2002 07:21:24 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnezl03476
	for <mpls-archive@lists.ietf.org>; Thu, 5 Sep 2002 11:22:58 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnezl03421;
	Thu, 5 Sep 2002 11:22:57 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnezl08663
	for mpls-outgoing; Thu, 5 Sep 2002 11:22:36 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQnezl08658
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 5 Sep 2002 11:22: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 QQnezl17017
	for <mpls@uu.net>; Thu, 5 Sep 2002 11:22:03 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnezl24268
	for <mpls@uu.net>; Thu, 5 Sep 2002 11:22:03 GMT
Received: from funnel.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnezl24263
	for <mpls@uu.net>; Thu, 5 Sep 2002 11:22:03 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id HAA07228 for <mpls@uu.net>; Thu, 5 Sep 2002 07:22:02 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g85BM2q11397 for mpls@uu.net; Thu, 5 Sep 2002 07:22:02 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQnezl08639
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 5 Sep 2002 11:21:27 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 QQnezl23424
	for <mpls@uu.net>; Thu, 5 Sep 2002 11:21:00 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnezl15444
	for <mpls@uu.net>; Thu, 5 Sep 2002 11:21:00 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 QQnezl15432
	for <mpls@uu.net>; Thu, 5 Sep 2002 11:20:56 GMT
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15141;
	Thu, 5 Sep 2002 07:19:20 -0400 (EDT)
Message-Id: <200209051119.HAA15141@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-kishan-lsp-btrace-03.txt
Date: Thu, 05 Sep 2002 07:19:19 -0400
Sender: owner-mpls@UU.NET
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Backtrace Messages for Label Switched Paths
	Author(s)	: H. Desineni, K. Avasarala
	Filename	: draft-kishan-lsp-btrace-03.txt
	Pages		: 19
	Date		: 2002-9-4
	
Label switched path (LSP) backtrace is a method to backtrack the 
paths followed by packets in a particular forwarding equivalence 
class (FEC). This document describes the encoding and procedures for 
new label distribution protocol (LDP) messages, the backtrace message 
and backtrace reply message used for performing LSP backtrace. The 
backtrace message is sent upstream for an established LSP. The 
backtrace message can be used for LDP LSPs as well as for constraint 
based label switched paths (CR-LSPs). The data requested through a 
backtrace message is encoded into the backtrace reply message. 
Backtrace reply message is sent in downstream direction. It always 
travels towards the tail end of the LSP. Backtrace mechanism 
described in this document can also be used for obtaining additional 
attributes of the LSPs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-kishan-lsp-btrace-03.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-kishan-lsp-btrace-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-kishan-lsp-btrace-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:	<2002-9-4143517.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-kishan-lsp-btrace-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-kishan-lsp-btrace-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--OtherAccess--

--NextPart--




From owner-mpls@UU.NET  Thu Sep  5 09:20:36 2002
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 ESMTP id JAA18307
	for <mpls-archive@lists.ietf.org>; Thu, 5 Sep 2002 09:20:35 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnezt15005
	for <mpls-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:22:09 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnezt14819;
	Thu, 5 Sep 2002 13:22:04 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnezt05916
	for mpls-outgoing; Thu, 5 Sep 2002 13:21:51 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQnezt05911
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 5 Sep 2002 13:21: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 QQnezt17625
	for <mpls@uu.net>; Thu, 5 Sep 2002 13:20:08 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnezt12444
	for <mpls@uu.net>; Thu, 5 Sep 2002 13:20:07 GMT
Received: from funnel.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnezt12426
	for <mpls@uu.net>; Thu, 5 Sep 2002 13:20:07 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id JAA13029 for <mpls@uu.net>; Thu, 5 Sep 2002 09:20:06 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g85DK6j24409 for mpls@uu.net; Thu, 5 Sep 2002 09:20:06 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQneze12408
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 5 Sep 2002 09:39:45 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 QQneze11334
	for <mpls@UU.NET>; Thu, 5 Sep 2002 09:39:30 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQneze29955
	for <mpls@UU.NET>; Thu, 5 Sep 2002 09:39:30 GMT
Received: from mailweb33.rediffmail.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: [203.199.83.245])
	id QQneze29936
	for <mpls@UU.NET>; Thu, 5 Sep 2002 09:39:29 GMT
Received: (qmail 1564 invoked by uid 510); 5 Sep 2002 09:39:03 -0000
Date: 5 Sep 2002 09:39:03 -0000
Message-ID: <20020905093903.1563.qmail@mailweb33.rediffmail.com>
Received: from unknown (203.200.20.226) by rediffmail.com via HTTP; 05 sep 2002 09:39:03 -0000
MIME-Version: 1.0
From: "Harish  Kumtakar" <harishk3@rediffmail.com>
Reply-To: "Harish  Kumtakar" <harishk3@rediffmail.com>
To: rsvp@isi.edu
Cc: mpls@UU.NET, schultz@io.iol.unh.edu
Subject: help
Content-type: text/plain;
	format=flowed
Content-Disposition: inline
Sender: owner-mpls@UU.NET
Precedence: bulk

hi,
    It is given in RFC 2961 that,when a node ,say R, does not 
recognize or does not wish to accept a Bundle message, the 
received Bundle messages will be discarded without further 
analysis.

     If this is the case..then how come the sender (of the Bundle 
Message)will come to know to that R does not support Bundle 
message.

regards,
-harish



From owner-mpls@UU.NET  Thu Sep  5 09:43:47 2002
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 ESMTP id JAA19218
	for <mpls-archive@lists.ietf.org>; Thu, 5 Sep 2002 09:43:47 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnezv01743
	for <mpls-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:45:17 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnezu00489;
	Thu, 5 Sep 2002 13:44:40 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnezu07268
	for mpls-outgoing; Thu, 5 Sep 2002 13:44:14 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQnezu07235
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 5 Sep 2002 13:44: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 QQnezu27350
	for <mpls@UU.NET>; Thu, 5 Sep 2002 13:43:26 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnezu15527
	for <mpls@UU.NET>; Thu, 5 Sep 2002 13:43:26 GMT
Received: from xover.netplane.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: fwout.maker.com [12.27.183.253] (may be forged))
	id QQnezu15516
	for <mpls@UU.NET>; Thu, 5 Sep 2002 13:43:26 GMT
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2653.19)
	id <S1D0AS7K>; Thu, 5 Sep 2002 09:43:25 -0400
Message-ID: <E7E13AAF2F3ED41197C100508BD6A3284939A1@india_exch.hyderabad.mindspeed.com>
From: "Reddy, Vikram" <vikramr@netplane.com>
To: "'Harish  Kumtakar'" <harishk3@rediffmail.com>, rsvp@isi.edu
Cc: mpls@UU.NET, schultz@io.iol.unh.edu
Subject: RE: help
Date: Thu, 5 Sep 2002 09:45:37 -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

From section 3.3 of the same RFC



3.3. Sending RSVP Bundle Messages

   Support for RSVP Bundle messages is optional.  While message bundling
   helps in scaling RSVP, by reducing processing overhead and bandwidth
   consumption, a node is not required to transmit every standard RSVP
   message in a Bundle message.  A node MUST always be ready to receive
   standard RSVP messages.

   RSVP Bundle messages can only be sent to RSVP neighbors that support
   bundling.  Methods for discovering such information include: (1)
   manual configuration and (2) observing the Refresh-Reduction-Capable
   bit (see Section 2) in the received RSVP messages.  RSVP Bundle
   messages MUST NOT be used if the RSVP neighbor does not support RSVP
   Bundle messages.


This means if the 1) configuration on the current node
does not specify that the neighbor is configured to have 
refresh reduction support and 
2) the Flags field of the RSVP common header of the last message received
does not indicate Refresh reduction capability, then 

we have to assume that the neighbor does not support refresh reduction
until one of the above conditions has changed.


Hope this helps.
Vikram.



-----Original Message-----
From: Harish Kumtakar [mailto:harishk3@rediffmail.com]
Sent: Thursday, September 05, 2002 3:09 PM
To: rsvp@isi.edu
Cc: mpls@UU.NET; schultz@io.iol.unh.edu
Subject: help


hi,
    It is given in RFC 2961 that,when a node ,say R, does not 
recognize or does not wish to accept a Bundle message, the 
received Bundle messages will be discarded without further 
analysis.

     If this is the case..then how come the sender (of the Bundle 
Message)will come to know to that R does not support Bundle 
message.

regards,
-harish


From owner-mpls@UU.NET  Thu Sep  5 11:44:48 2002
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 ESMTP id LAA23247
	for <mpls-archive@lists.ietf.org>; Thu, 5 Sep 2002 11:44:47 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfad03471
	for <mpls-archive@lists.ietf.org>; Thu, 5 Sep 2002 15:46:24 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnfad03427;
	Thu, 5 Sep 2002 15:46:22 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnfad05744
	for mpls-outgoing; Thu, 5 Sep 2002 15:45:56 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQnfad05739
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 5 Sep 2002 15:45: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 QQnfac26801
	for <mpls@UU.NET>; Thu, 5 Sep 2002 15:44:40 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfac07600
	for <mpls@UU.NET>; Thu, 5 Sep 2002 15:44:39 GMT
Received: from tama5.ecl.ntt.co.jp by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: tama5.ecl.ntt.co.jp [129.60.39.102])
	id QQnfac07587
	for <mpls@UU.NET>; Thu, 5 Sep 2002 15:44:37 GMT
Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110])
	by tama5.ecl.ntt.co.jp (8.9.3+3.2W/3.7W/07/30/02) with ESMTP id AAA27970;
	Fri, 6 Sep 2002 00:44:18 +0900 (JST)
	(envelope-from yasukawa.seisho@lab.ntt.co.jp)
Received: from nttmail3.ecl.ntt.co.jp (localhost [127.0.0.1])
	by vcs3.rdh.ecl.ntt.co.jp (8.12.3/8.12.3) with ESMTP id g85FiIRp017432;
	Fri, 6 Sep 2002 00:44:18 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69])
	by nttmail3.ecl.ntt.co.jp (8.12.3/8.12.3) with ESMTP id g85FiHxH029499;
	Fri, 6 Sep 2002 00:44:17 +0900 (JST)
Received: from imc.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.9.3/3.7W) with ESMTP id AAA21604;
	Fri, 6 Sep 2002 00:44:17 +0900 (JST)
Received: from barrister.lab.ntt.co.jp
	by imc.m.ecl.ntt.co.jp (8.9.3/3.7W) with ESMTP id AAA15546;
	Fri, 6 Sep 2002 00:44:15 +0900 (JST)
Message-Id: <5.0.2.5.2.20020906001600.00c98df8@imc.m.ecl.ntt.co.jp>
X-Sender: sy003@imc.m.ecl.ntt.co.jp
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2-J
Date: Fri, 06 Sep 2002 00:45:20 +0900
To: "Reddy, Vikram" <vikramr@netplane.com>
From: Seisho Yasukawa <yasukawa.seisho@lab.ntt.co.jp>
Subject: RE: Questions/Comments regarding
  draft-yasukawa-mpls-rsvp-multicast
Cc: "'mpls@UU.NET'" <mpls@UU.NET>
In-Reply-To: <E7E13AAF2F3ED41197C100508BD6A32849399D@india_exch.hyderaba
 d.mindspeed.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk

Hello Vikram

>I have one more question regarding the draft. The following is from the
>draft.
>
>    Either the intermediate node or the leaf node may calculate the
>    multicast tree route in order to decentralize this calculation. So
>    all nodes belonging to the same multicast group need to have
>    information about the whole multicast tree topology in order to
>    prevent intersection of multicast tree.  Each node MUST NOT delete
>    the TERO subobjects that specify nodes on the explicitly routed path
>    in order to get the whole multicast tree topology information. Each
>    node MAY record the whole multicast tree topology from TERO. In this
>    way, all nodes can have the same information about the whole
>    multicast tree topology.
>
>The above states that all the nodes in the multicast tree have to have
>the full information about the multicast tree.
>I would like to know the technical reasons for this requirement.
>The obvious drawbacks with this requirement is the increase in the
>the message sizes with the increase in the number of nodes.

Technically, it is preferable to maintain the full information about the
multicast tree to avoid creating the multicast tree loop.
When considering leaf initiated Join process, the node receiving the
Join message become a leaf LSP setup initiator.
(We call this node as a Graft node)
Therefore the Graft node must be check whole multicast tree topology
when grafting leaf LSP to avoid the creation of multicast loop.

>In my opinion, if every node maintains the previous hop and the
>next hop(s) information, it should be enough, unless you see some
>specific technical reason for the above information. If it is
>only for the NMS show/information/display purpose, I feel it
>is better to do it at the source node itself and thus remove this
>requirement.

We also recognize the drawback of this architecture when considering
system implementation.
To maintain whole topology of multicast tree require huge memory
resource at each node.
This restricts network and system scalability.

Therefore, we want to modify this requirement mandatory to optional
in next version of our draft.

Thanks,

Seisho 



From owner-mpls@UU.NET  Mon Sep  9 10:06:28 2002
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 ESMTP id KAA02439
	for <mpls-archive@lists.ietf.org>; Mon, 9 Sep 2002 10:06:28 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfoq23619
	for <mpls-archive@lists.ietf.org>; Mon, 9 Sep 2002 14:08:07 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnfoq23495;
	Mon, 9 Sep 2002 14:08:03 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnfoq02965
	for mpls-outgoing; Mon, 9 Sep 2002 14:07:34 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnfoq02933
	for <mpls@mail-control.ash.ops.us.uu.net>; Mon, 9 Sep 2002 14:07:19 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 QQnfoq29151
	for <mpls@uu.net>; Mon, 9 Sep 2002 14:07:05 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfoq22961
	for <mpls@uu.net>; Mon, 9 Sep 2002 14:07:04 GMT
Received: from blooper.utfors.se by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail.utfors.se [195.58.103.125])
	id QQnfoq22957
	for <mpls@uu.net>; Mon, 9 Sep 2002 14:07:03 GMT
Received: from utfors.se (nat-sto.utfors.se [212.73.0.237])
	by blooper.utfors.se (8.12.6/8.12.6) with ESMTP id g89E6ZtA013365;
	Mon, 9 Sep 2002 16:06:35 +0200 (MEST)
Message-ID: <3D7CAAEB.7040707@utfors.se>
Date: Mon, 09 Sep 2002 16:06:35 +0200
From: Loa Andersson <loa.andersson@utfors.se>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3
X-Accept-Language: en-us
MIME-Version: 1.0
To: MPLS wg <mpls@UU.NET>
CC: Scott Bradner <sob@harvard.edu>, Bert Wijnen <bwijnen@lucent.com>,
        George Swallow <swallow@cisco.com>
Subject: Consensus on the MPLS signaling protocols
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit

All,

we have found that we have reached a workable consensus in the
discussion on MPLS signaling protocol for traffic engineering
applications.

The consensus is based on the earlier attempted consensus mails
sent by the Working Group chairs to the MPLS mailing list, and
discussion on the list.

Consensus has been reached on:

- that the MPLS WG needs to focus its efforts on RSVP-TE as protocol
   for traffic engineering signaling.

- that the Working Group effort on CR-LDP should be discontinued.

- that the WG charter should be updated to reflect this.

- that CR-LDP (RFC 3212) will remain a proposed standard.

- that RFCs 3213 and 3214, that is closely related to CR-LDP will remain
   proposed standard.

- that existing Working Group drafts related to or updating/changing
   CR-LDP will be progressed through the standards process to
   proposed standard or informational RFCs as appropriate.

- that "the existing cr-ldp working group documents" are:
     draft-ietf-mpls-lsp-query-nn.txt
     draft-ietf-mpls-te-feed-nn.txt
     draft-ietf-mpls-crldp-unnum-nn.txt
     draft-ietf-mpls-ldp-ft-nn.txt
     draft-ietf-mpls-generalized-cr-ldp-nn.txt
     draft-ietf-ccamp-gmpls-sonet-sdh-nn.txt
     draft-ietf-ccamp-gmpls-sonet-sdh-extensions-nn.txt

- that the IETF will take on no new Working Group documents
   related to CR-LDP.

- that the IETF will entertain no efforts to promote CR-LDP beyond
   proposed standard.

- that individual contributions to CR-LDP area are not prohibited, but
   discouraged.

- that a message will be sent to the relevant standards organizations
   notifying them of this change of focus on MPLS signaling protocols.


A more detailed documentation of the consensus, the process through 
which it was reached are found in

http://62.119.0.68/~loa/tally.htm

and

http://62.119.0.68/~loa/draft-andersson-mpls-sig-decision-00.txt

The later is a Internet Draft that will be sent to the IESG to be
published as an Informational RFC as confirmation of the Working
Group consensus.

Comments on this Internet Draft are welcome.

Loa and George

-- 
     Loa Andersson
     Chief Architect,
     Utfors Research, Architecture and Future Lab (URAX)
     Utfors AB
     R錽undav鋑en 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 Sep  9 12:19:03 2002
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 ESMTP id MAA09165
	for <mpls-archive@lists.ietf.org>; Mon, 9 Sep 2002 12:19:03 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfoz09103
	for <mpls-archive@lists.ietf.org>; Mon, 9 Sep 2002 16:20:42 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnfoz09012;
	Mon, 9 Sep 2002 16:20:39 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnfoz14844
	for mpls-outgoing; Mon, 9 Sep 2002 16:20:13 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQnfoz14838
	for <mpls@mail-control.ash.ops.us.uu.net>; Mon, 9 Sep 2002 16:20:07 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 QQnfoz20088
	for <mpls@uu.net>; Mon, 9 Sep 2002 16:19:48 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfoz08336
	for <mpls@uu.net>; Mon, 9 Sep 2002 16:19:47 GMT
Received: from blooper.utfors.se by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail.utfors.se [195.58.103.125])
	id QQnfoz08327
	for <mpls@uu.net>; Mon, 9 Sep 2002 16:19:46 GMT
Received: from utfors.se (nat-sto.utfors.se [212.73.0.237])
	by blooper.utfors.se (8.12.6/8.12.6) with ESMTP id g89GJBtA015969;
	Mon, 9 Sep 2002 18:19:11 +0200 (MEST)
Message-ID: <3D7CC9FF.6010509@utfors.se>
Date: Mon, 09 Sep 2002 18:19:11 +0200
From: Loa Andersson <loa.andersson@utfors.se>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3
X-Accept-Language: en-us
MIME-Version: 1.0
To: ospf wg <OSPF@DISCUSS.MICROSOFT.COM>, isis-wg <isis-wg@ietf.org>
CC: Loa Andersson <loa.andersson@utfors.se>, MPLS wg <mpls@UU.NET>
Subject: Re: LAst Call: draft-ietf-mpls-bundle-04.txt
References: <3D6DBFBE.4050603@utfors.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit

All,

it is my understanding that there has been some hick-ups on
the is-is list, so I'm re-issueing this last call and extending
the time to September 29th. At the same time I would like point out
that there is an acompanying mib draft-ietf-mpls-bundle-mib-03.txt.

Also comments on the mib is welcome.

BTW, thanks to those of you who already sent us comments :)

The wg last call on

  <draft-ietf-mpls-bundle-04.txt>
  <draft-ietf-mpls-bundle-mib-03.txt>

has been extended to September 29.

/Loa

Loa Andersson wrote:

> OSPF and IS-IS working groups, (mpls wg for info)
> 
> the iesg has started the review of the mpls working group draft
> draft-ietf-mpls-bundle-04.txt. The immediate response from the iesg
> is that the draft contains OSPF and ISIS related details (see
> the included mail). After discussing with the wg chairs for ospf
> and is-is working groups, there is a feeling that the two weeks
> the iesg allocated for this last call might not be enough, since the
> draft has not been widely circulated in the routing working groups.
> 
> Therefore:
> 
> This is to initiate a last call for the
> 
> <draft-ietf-mpls-bundle-04.txt>
> 
> by the ospf and is-is working groups.
> The last call ends September 22nd at 12PM CET
> 
> 
> Please include the mpls mailing list (mpls@uu.net) in your responses.
> 
> /Loa (co-chair of the mpls wg)
> 
> -------- Original Message --------
> Subject: draft-ietf-mpls-bundle-04.txt
> Date: Tue, 27 Aug 2002 15:06:48 -0400 (EDT)
> From: Scott Bradner
> To: loa.andersson@utfors.se, swallow@cisco.com
> 
> 
> The IESG discussed this ID last week during its teleconference
> one issue was raised during the discussion
> 
> "the draft contains OSPF & ISIS
> related details and I don't remember it being LC'ed or reviewed
> in the corresponding WGs."
> 
> can you start a 2 week last call on the IS-IS and OSPF mailing
> lists for this document?
> 
> Scott
> 


-- 
     Loa Andersson
     Chief Architect,
     Utfors Research, Architecture and Future Lab (URAX)
     Utfors AB
     R錽undav鋑en 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 Sep 10 10:00:01 2002
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 ESMTP id KAA14510
	for <mpls-archive@lists.ietf.org>; Tue, 10 Sep 2002 10:00:01 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfsi08812
	for <mpls-archive@lists.ietf.org>; Tue, 10 Sep 2002 14:01:40 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnfsi08722;
	Tue, 10 Sep 2002 14:01:38 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnfsi11348
	for mpls-outgoing; Tue, 10 Sep 2002 14:01:18 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQnfsi11058
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 10 Sep 2002 14:01: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 QQnfsi01936
	for <mpls@uu.net>; Tue, 10 Sep 2002 14:01:13 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfsi02526
	for <mpls@uu.net>; Tue, 10 Sep 2002 14:01:13 GMT
Received: from granger.mail.mindspring.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: granger.mail.mindspring.net [207.69.200.148])
	id QQnfsi02521
	for <mpls@uu.net>; Tue, 10 Sep 2002 14:01:12 GMT
Received: from user-uinjmqj.dsl.mindspring.com ([165.121.219.83] helo=METANOIA)
	by granger.mail.mindspring.net with smtp (Exim 3.33 #1)
	id 17olZi-0004m2-00; Tue, 10 Sep 2002 10:01:06 -0400
Reply-To: <v.sharma@ieee.org>
From: "Vishal Sharma" <v.sharma@ieee.org>
To: "Anna Charny" <acharny@cisco.com>,
        "Shahram Davari" <Shahram_Davari@pmc-sierra.com>
Cc: "'mpls@UU.net'" <mpls@UU.NET>
Subject: RE: Comments on Backup-Computation draft
Date: Tue, 10 Sep 2002 10:01:30 -0400
Message-ID: <MMECLKMDFPCEJFECIBCMCEOJCPAA.v.sharma@ieee.org>
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.2910.0)
Importance: Normal
In-Reply-To: <4.3.2.7.2.20020814221708.0402fc18@pilgrim.cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Anna, Shahram,

> -----Original Message-----
> From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Anna
> Charny
> Sent: Thursday, August 15, 2002 5:35 PM
> To: Shahram Davari
> Cc: 'mpls@UU.net'
> Subject: Re: Comments on Backup-Computation draft
>
>
<<snip>


> >8) Section 6.2.1 suggests finding the backup pool, by subtracting the
> >global reservable BW from the link BW. How does a node know the
> link BW to
> >do this computation?
>
> Here is an example with OSPF (link TLV of the TE opaque LSA):
>
> Sub-TLV 6 - Maximum Bandwidth
>
>     The Maximum Bandwidth sub-TLV specifies the maximum bandwidth that
>     can be used on this link in this direction (from the system
>     originating the LSA to its neighbor), in IEEE floating point format.
>     This is the true link capacity.
>
> Sub-TLV 7 - Maximum Reservable Bandwidth
>
>     The Maximum Reservable Bandwidth sub-TLV specifies the maximum
>     bandwidth that may be reserved on this link in this direction, in
>     IEEE floating point format
>
> Maximum bandwidth - Maximum Reservable Bandwidth = Backup bandwidth pool.
>

I seem to recall that the maximum reservable bandwidth can, in fact, be
set to be _larger_ than the link capacity to allow for admitting
traffic/LSPs
whose cumulative b/w exceeds the maximum bandwidth, in those cases where
link oversubscription is allowed or desired.

As a result, the backup bandwidth pool may not be directly derivable from
the simple calculation above, unless there an assumption of a network-wide
policy of
using no oversubscription.

-Vishal




From owner-mpls@UU.NET  Tue Sep 10 10:39:18 2002
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 ESMTP id KAA15934
	for <mpls-archive@lists.ietf.org>; Tue, 10 Sep 2002 10:39:18 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfsk25866
	for <mpls-archive@lists.ietf.org>; Tue, 10 Sep 2002 14:40:57 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnfsk25498;
	Tue, 10 Sep 2002 14:40:44 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnfsk24238
	for mpls-outgoing; Tue, 10 Sep 2002 14:40:17 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQnfsk24227
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 10 Sep 2002 14:39: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 QQnfsk02027
	for <mpls@uu.net>; Tue, 10 Sep 2002 14:39:09 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfsk23266
	for <mpls@uu.net>; Tue, 10 Sep 2002 14:39:09 GMT
Received: from funnel.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnfsk23250
	for <mpls@uu.net>; Tue, 10 Sep 2002 14:39:08 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id KAA18954 for <mpls@uu.net>; Tue, 10 Sep 2002 10:39:08 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8AEd8Z22237 for mpls@uu.net; Tue, 10 Sep 2002 10:39:08 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnfsk24187
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 10 Sep 2002 14:38: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 QQnfsk25356
	for <mpls@UU.NET>; Tue, 10 Sep 2002 14:37:33 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfsk08087
	for <mpls@UU.NET>; Tue, 10 Sep 2002 14:37:33 GMT
Received: from pilgrim.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: pilgrim.cisco.com [161.44.168.94])
	id QQnfsk08083
	for <mpls@UU.NET>; Tue, 10 Sep 2002 14:37:33 GMT
Received: from ACHARNY-W2K1.cisco.com (acharny-frame1.cisco.com [10.84.14.34])
	by pilgrim.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id KAA21805;
	Tue, 10 Sep 2002 10:37:28 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020910102058.023868b8@pilgrim.cisco.com>
X-Sender: acharny@pilgrim.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 10 Sep 2002 10:37:27 -0400
To: <v.sharma@ieee.org>
From: Anna Charny <acharny@cisco.com>
Subject: RE: Comments on Backup-Computation draft
Cc: "Shahram Davari" <Shahram_Davari@pmc-sierra.com>,
        "'mpls@UU.net'" <mpls@UU.NET>
In-Reply-To: <MMECLKMDFPCEJFECIBCMCEOJCPAA.v.sharma@ieee.org>
References: <4.3.2.7.2.20020814221708.0402fc18@pilgrim.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Vishal,

Please see below.

At 10:01 AM 9/10/2002 -0400, Vishal Sharma wrote:
>Anna, Shahram,
>
> > -----Original Message-----
> > From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Anna
> > Charny
> > Sent: Thursday, August 15, 2002 5:35 PM
> > To: Shahram Davari
> > Cc: 'mpls@UU.net'
> > Subject: Re: Comments on Backup-Computation draft
> >
> >
><<snip>
>
>
> > >8) Section 6.2.1 suggests finding the backup pool, by subtracting the
> > >global reservable BW from the link BW. How does a node know the
> > link BW to
> > >do this computation?
> >
> > Here is an example with OSPF (link TLV of the TE opaque LSA):
> >
> > Sub-TLV 6 - Maximum Bandwidth
> >
> >     The Maximum Bandwidth sub-TLV specifies the maximum bandwidth that
> >     can be used on this link in this direction (from the system
> >     originating the LSA to its neighbor), in IEEE floating point format.
> >     This is the true link capacity.
> >
> > Sub-TLV 7 - Maximum Reservable Bandwidth
> >
> >     The Maximum Reservable Bandwidth sub-TLV specifies the maximum
> >     bandwidth that may be reserved on this link in this direction, in
> >     IEEE floating point format
> >
> > Maximum bandwidth - Maximum Reservable Bandwidth = Backup bandwidth pool.
> >
>
>I seem to recall that the maximum reservable bandwidth can, in fact, be
>set to be _larger_ than the link capacity to allow for admitting
>traffic/LSPs
>whose cumulative b/w exceeds the maximum bandwidth, in those cases where
>link oversubscription is allowed or desired.
>
>As a result, the backup bandwidth pool may not be directly derivable from
>the simple calculation above, unless there an assumption of a network-wide
>policy of
>using no oversubscription.

It is correct that the maximum reservable bandwidth may indeed be larger 
than link speed.  However, in the section of the draft that Shahram cites 
we explicitly say that the above computation can be used IF max reservable 
bandwidth is configured to be less than link speed.  This is not an 
entirely unreasonable setting as the context of the discussion is strict 
bandwidth protection.  Here is the quote:

"Also, the backup pools can be implicitly derived from the routing 
information already available. This could be done by configuring max global 
reservable pool to being less than the link speed by the desired value of 
the backup pool. Every node computing its backup tunnels then can by 
default use link speed minus the max global reservable pool as the value of 
the backup pool to use in its computation of the backup tunnels placement. "

However,  if the backup pool is propagated explicitly in the IGP 
extensions, as is really the preferred option for the distributed 
computation, then the backup bandwidth can be set up explicitly, 
independently of the max reservable global.  So under a single failure 
assumption, the effective maximum overbooking  on a given link would be 
essentially defined as the sum of max reservable bandwidth plus explicitly 
defined backup pool divided by the link speed.

Finally, in the case of a centralized server the desired degree of 
overbooking (if any) can be specified in the server.

Does this make sense to you?

Thanks,
Anna

>-Vishal



From owner-mpls@UU.NET  Tue Sep 10 15:21:30 2002
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 ESMTP id PAA24330
	for <mpls-archive@lists.ietf.org>; Tue, 10 Sep 2002 15:21:30 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnftd15293
	for <mpls-archive@lists.ietf.org>; Tue, 10 Sep 2002 19:23:07 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnftd14602;
	Tue, 10 Sep 2002 19:22:45 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnftd07166
	for mpls-outgoing; Tue, 10 Sep 2002 19:22:18 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnftd07159
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 10 Sep 2002 19:22:06 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 QQnftd15435
	for <mpls@uu.net>; Tue, 10 Sep 2002 19:21:21 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnftd13785
	for <mpls@uu.net>; Tue, 10 Sep 2002 19:21:21 GMT
Received: from funnel.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnftd13781
	for <mpls@uu.net>; Tue, 10 Sep 2002 19:21:20 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id PAA13935 for <mpls@uu.net>; Tue, 10 Sep 2002 15:21:20 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8AJLKb24230 for mpls@uu.net; Tue, 10 Sep 2002 15:21:20 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQnftb18715
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 10 Sep 2002 18:58: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 QQnftb19446
	for <mpls@UU.NET>; Tue, 10 Sep 2002 18:57:19 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnftb18833
	for <mpls@UU.NET>; Tue, 10 Sep 2002 18:57:18 GMT
Received: from lennier.cc.vt.edu by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: lennier.cc.vt.edu [198.82.162.213])
	id QQnftb18828
	for <mpls@UU.NET>; Tue, 10 Sep 2002 18:57:18 GMT
Received: from vivi.cc.vt.edu (IDENT:mirapoint@vivi-lb.cc.vt.edu [10.1.1.12])
	by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g8AIvHM338082
	for <mpls@UU.NET>; Tue, 10 Sep 2002 14:57:17 -0400 (EDT)
Received: from zathras (zathras.cc.vt.edu [198.82.162.117])
	by vivi.cc.vt.edu (Mirapoint Messaging Server MOS 3.2.0-GA)
	with ESMTP id AIR66688;
	Tue, 10 Sep 2002 14:57:17 -0400 (EDT)
X-WebMail-UserID:  flaw
Date: Tue, 10 Sep 2002 14:57:17 -0400
From: Raymond Law <flaw@vt.edu>
To: mpls@UU.NET
X-EXP32-SerialNo: 00002964
Subject: RSVP SE reservation style implemented by CR-LDP
Message-ID: <3D851CB8@zathras>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailer: WebMail (Hydra) SMTP v3.62
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Can Shared Explicit reservation style be realized using CR-LDP in an MPLS 
network?  Is it possible to use CR-LDP to allow multiple CR-LSPs to share 
resource reservations.  Thank you.

Ray,




From owner-mpls@UU.NET  Tue Sep 10 16:02:13 2002
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 ESMTP id QAA25497
	for <mpls-archive@lists.ietf.org>; Tue, 10 Sep 2002 16:02:12 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnftg21523
	for <mpls-archive@lists.ietf.org>; Tue, 10 Sep 2002 20:03:52 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnftg21298;
	Tue, 10 Sep 2002 20:03:47 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnftg25060
	for mpls-outgoing; Tue, 10 Sep 2002 20:03:19 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnftg24885
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 10 Sep 2002 20:03: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 QQnftg29058
	for <mpls@uu.net>; Tue, 10 Sep 2002 20:02:42 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnftg20282
	for <mpls@uu.net>; Tue, 10 Sep 2002 20:02:41 GMT
Received: from smtp1.opnet.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: smtp1.opnet.com [141.156.71.6])
	id QQnftg20257
	for <mpls@uu.net>; Tue, 10 Sep 2002 20:02:41 GMT
Received: from wtn10216.opnet.com (unverified) by smtp1.opnet.com
 (Content Technologies SMTPRS 4.2.10) with ESMTP id <T5d40f065fdac10010f360@smtp1.opnet.com> for <mpls@uu.net>;
 Tue, 10 Sep 2002 15:57:35 -0400
Message-Id: <5.0.0.25.2.20020910155145.00aeee40@mail.opnet.com>
X-Sender: skalra@mail.opnet.com
X-Mailer: QUALCOMM Windows Eudora Version 5.0
Date: Tue, 10 Sep 2002 16:02:32 -0400
To: mpls@UU.NET
From: Sachin Kalra <skalra@opnet.com>
Subject: 2547 BGP VPNs
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_512061685==_.ALT"
Sender: owner-mpls@UU.NET
Precedence: bulk

--=====================_512061685==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

Dear MPLS Community:

Please consider the following simple but strange scenario.
Lets say we have two directly connected PEs. Traffic is flowing from CE1 to 
CE2. According to VRF table entry on PE1, for destination CE2 bottom label 
is "X" and top label is "Y". And, we are doing penultimate-hop-popping 
(PHP) for the LSP between PE1 and PE2.


                             LSP
                        ========>
[CE1]------[PE1]-----------------[PE2]------[CE2]


So, my question is who does push and who does pop here? Will top label "Y" 
be ever used in this scenario?

Thanks for your response,
Sachin Kalra

===========================================================
Sachin Kalra
Modeling Engineer
OPNET Technologies, Inc.
(240)-497-3000 x2796
===========================================================
Register for OPNET's Online Technology Workshops
(http://www.opnet.com/TechWorkshops/)
===========================================================

--=====================_512061685==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
Dear MPLS Community:<br>
<br>
Please consider the following simple but strange scenario.<br>
Lets say we have two directly connected PEs. Traffic is flowing from CE1
to CE2. According to VRF table entry on PE1, for destination CE2 bottom
label is &quot;X&quot; and top label is &quot;Y&quot;. And, we are doing
penultimate-hop-popping (PHP) for the LSP between PE1 and PE2.  <br>
<br>
<br>
&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;
LSP<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
========&gt;<br>
[CE1]------[PE1]-----------------[PE2]------[CE2]<br>
<br>
<br>
So, my question is who does push and who does pop here? Will top label
&quot;Y&quot; be ever used in this scenario?<br>
<br>
Thanks for your response,<br>
Sachin Kalra<br>
<x-sigsep><p></x-sigsep>
===========================================================<br>
Sachin Kalra<br>
Modeling Engineer<br>
OPNET Technologies, Inc.<br>
(240)-497-3000 x2796<br>
===========================================================<br>
<b>Register</b> for OPNET's<b> Online Technology Workshops<br>
</b><font color="#0000FF"><u>(<a href="http://www.opnet.com/TechWorkshops/" eudora="autourl">http://www.opnet.com/TechWorkshops/</a>)<br>
</u></font>===========================================================<br>
</html>

--=====================_512061685==_.ALT--



From owner-mpls@UU.NET  Tue Sep 10 16:13:18 2002
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 ESMTP id QAA25677
	for <mpls-archive@lists.ietf.org>; Tue, 10 Sep 2002 16:13:18 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnftg06733
	for <mpls-archive@lists.ietf.org>; Tue, 10 Sep 2002 20:14:57 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnftg06290;
	Tue, 10 Sep 2002 20:14:44 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnftg27289
	for mpls-outgoing; Tue, 10 Sep 2002 20:14:15 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQnftg27284
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 10 Sep 2002 20:14: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 QQnftg18597
	for <mpls@UU.NET>; Tue, 10 Sep 2002 20:13:53 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnftg05456
	for <mpls@UU.NET>; Tue, 10 Sep 2002 20:13:52 GMT
Received: from celox-ma1-ems1.celoxnetworks.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: celox-ma1-imap1.celoxnetworks.com [12.40.60.233])
	id QQnftg05452
	for <mpls@UU.NET>; Tue, 10 Sep 2002 20:13:52 GMT
Received: by celox-ma1-ems1.celoxnetworks.com with Internet Mail Service (5.5.2653.19)
	id <RBC1CF2F>; Tue, 10 Sep 2002 16:13:52 -0400
Message-ID: <1117F7D44159934FB116E36F4ABF221B020B0E91@celox-ma1-ems1.celoxnetworks.com>
From: "Suryanarayana, Ananth" <ananth@celoxnetworks.com>
To: "'Sachin Kalra'" <skalra@opnet.com>, mpls@UU.NET
Subject: RE: 2547 BGP VPNs
Date: Tue, 10 Sep 2002 16:13:51 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C25906.94838BC0"
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_01C25906.94838BC0
Content-Type: text/plain

I think, in any  LSP, the outer-most label corresponding to that LSP will
not be used between PH and the egress lsr and it does apply to this case as
well. and ofcourse, the inner packet has to contain a vpn label.
 
 
Ananth

-----Original Message-----
From: Sachin Kalra [mailto:skalra@opnet.com]
Sent: Tuesday, September 10, 2002 4:03 PM
To: mpls@UU.NET
Subject: 2547 BGP VPNs


Dear MPLS Community:

Please consider the following simple but strange scenario.
Lets say we have two directly connected PEs. Traffic is flowing from CE1 to
CE2. According to VRF table entry on PE1, for destination CE2 bottom label
is "X" and top label is "Y". And, we are doing penultimate-hop-popping (PHP)
for the LSP between PE1 and PE2. 


                            LSP
                       ========>
[CE1]------[PE1]-----------------[PE2]------[CE2]


So, my question is who does push and who does pop here? Will top label "Y"
be ever used in this scenario?

Thanks for your response,
Sachin Kalra


===========================================================
Sachin Kalra
Modeling Engineer
OPNET Technologies, Inc.
(240)-497-3000 x2796
===========================================================
Register for OPNET's Online Technology Workshops
( http://www.opnet.com/TechWorkshops/ <http://www.opnet.com/TechWorkshops/>
)
===========================================================



------_=_NextPart_001_01C25906.94838BC0
Content-Type: text/html
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=3DUS-ASCII">


<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D723400920-10092002><FONT face=3DArial =
color=3D#0000ff size=3D2>I=20
think, in any&nbsp; LSP, the outer-most label corresponding to that LSP =
will not=20
be used between PH and the egress lsr and it does apply to this case as =
well.=20
and ofcourse, the&nbsp;inner packet has to contain a vpn=20
label.</FONT></SPAN></DIV>
<DIV><SPAN class=3D723400920-10092002><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D723400920-10092002><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D723400920-10092002><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Ananth</FONT></SPAN></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> Sachin Kalra=20
  [mailto:skalra@opnet.com]<BR><B>Sent:</B> Tuesday, September 10, 2002 =
4:03=20
  PM<BR><B>To:</B> mpls@UU.NET<BR><B>Subject:</B> 2547 BGP=20
  VPNs<BR><BR></FONT></DIV>Dear MPLS Community:<BR><BR>Please consider =
the=20
  following simple but strange scenario.<BR>Lets say we have two =
directly=20
  connected PEs. Traffic is flowing from CE1 to CE2. According to VRF =
table=20
  entry on PE1, for destination CE2 bottom label is "X" and top label =
is "Y".=20
  And, we are doing penultimate-hop-popping (PHP) for the LSP between =
PE1 and=20
  PE2.=20
  =
<BR><BR><BR>&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
  =
LSP<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
=3D=3D=3D=3D=3D=3D=3D=3D&gt;<BR>[CE1]------[PE1]-----------------[PE2]--=
----[CE2]<BR><BR><BR>So,=20
  my question is who does push and who does pop here? Will top label =
"Y" be ever=20
  used in this scenario?<BR><BR>Thanks for your response,<BR>Sachin=20
  Kalra<BR><X-SIGSEP>
  =
<P></X-SIGSEP>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR>Sachin=20
  Kalra<BR>Modeling Engineer<BR>OPNET Technologies, =
Inc.<BR>(240)-497-3000=20
  =
x2796<BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR><B>Register</B>=20
  for OPNET's<B> Online Technology Workshops<BR></B><FONT =
color=3D#0000ff><U>(<A=20
  href=3D"http://www.opnet.com/TechWorkshops/"=20
  =
eudora=3D"autourl">http://www.opnet.com/TechWorkshops/</A>)<BR></U></FON=
T>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR></P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C25906.94838BC0--


From owner-mpls@UU.NET  Tue Sep 10 16:15:32 2002
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 ESMTP id QAA25754
	for <mpls-archive@lists.ietf.org>; Tue, 10 Sep 2002 16:15:31 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfth09334
	for <mpls-archive@lists.ietf.org>; Tue, 10 Sep 2002 20:17:11 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnfth09165;
	Tue, 10 Sep 2002 20:17:06 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnfth27634
	for mpls-outgoing; Tue, 10 Sep 2002 20:16:39 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQnfth27623
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 10 Sep 2002 20:16:34 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 QQnfth23606
	for <mpls@UU.NET>; Tue, 10 Sep 2002 20:15:25 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfth07602
	for <mpls@UU.NET>; Tue, 10 Sep 2002 20:15:24 GMT
Received: from prattle.redback.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: prattle.redback.com [155.53.12.9])
	id QQnfth07498
	for <mpls@UU.NET>; Tue, 10 Sep 2002 20:15:21 GMT
Received: from malt.redback.com (malt.redback.com [155.53.12.41])
	by prattle.redback.com (Postfix) with ESMTP
	id 82C061DCC77; Tue, 10 Sep 2002 13:14:55 -0700 (PDT)
Received: (from rahul@localhost)
	by malt.redback.com (8.9.3-LCCHA/8.9.3/null redback solaris client) id NAA03913;
	Tue, 10 Sep 2002 13:14:55 -0700 (PDT)
Date: Tue, 10 Sep 2002 13:14:55 -0700
From: Rahul Aggarwal <rahul@redback.com>
To: Sachin Kalra <skalra@opnet.com>
Cc: mpls@UU.NET
Subject: Re: 2547 BGP VPNs
Message-ID: <20020910201455.GG2315@malt.redback.com>
References: <5.0.0.25.2.20020910155145.00aeee40@mail.opnet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5.0.0.25.2.20020910155145.00aeee40@mail.opnet.com>
User-Agent: Mutt/1.4i
Sender: owner-mpls@UU.NET
Precedence: bulk


On Tue, Sep 10, 2002 at 04:02:32PM -0400, Sachin Kalra wrote:
> Dear MPLS Community:
> 
> Please consider the following simple but strange scenario.

Its not all that strange :) 

> Lets say we have two directly connected PEs. Traffic is flowing from CE1 to 
> CE2. According to VRF table entry on PE1, for destination CE2 bottom label 
> is "X" and top label is "Y". And, we are doing penultimate-hop-popping 
> (PHP) for the LSP between PE1 and PE2.
> 
> 
>                             LSP
>                        ========>
> [CE1]------[PE1]-----------------[PE2]------[CE2]
> 
> 
> So, my question is who does push and who does pop here? Will top label "Y" 
> be ever used in this scenario?

The top label Y in this case is an implicit null (value=3) label. PE1 will
send a packet on the wire with only the one label in the label stack : label X.
Label Y is used in the signaling control plane by PE2 to indicate to PE1 to
do PHP for the LSP.

The label actions on PE1 are implemenation dependent. The simplest approach
is to regard this as a push X on PE1 as the encapsulation will be programmed
to push only one label.

> 
> Thanks for your response,
> Sachin Kalra
> 
> ===========================================================
> Sachin Kalra
> Modeling Engineer
> OPNET Technologies, Inc.
> (240)-497-3000 x2796
> ===========================================================
> Register for OPNET's Online Technology Workshops
> (http://www.opnet.com/TechWorkshops/)
> ===========================================================


From owner-mpls@UU.NET  Wed Sep 11 08:20:13 2002
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 ESMTP id IAA05926
	for <mpls-archive@lists.ietf.org>; Wed, 11 Sep 2002 08:20:13 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfvt09756
	for <mpls-archive@lists.ietf.org>; Wed, 11 Sep 2002 12:21:47 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnfvt09601;
	Wed, 11 Sep 2002 12:21:42 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnfvt19260
	for mpls-outgoing; Wed, 11 Sep 2002 12:21:15 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnfvt19253
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 11 Sep 2002 12:21: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 QQnfvt04520
	for <mpls@uu.net>; Wed, 11 Sep 2002 12:20:52 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfvt23594
	for <mpls@uu.net>; Wed, 11 Sep 2002 12:20:51 GMT
Received: from funnel.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnfvt23590
	for <mpls@uu.net>; Wed, 11 Sep 2002 12:20:51 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id IAA05097 for <mpls@uu.net>; Wed, 11 Sep 2002 08:20:51 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8BCKp506787 for mpls@uu.net; Wed, 11 Sep 2002 08:20:51 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQnfvb08902
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 11 Sep 2002 07:59: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 QQnfvb11073
	for <mpls@uu.net>; Wed, 11 Sep 2002 07:59:20 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfvb24069
	for <mpls@uu.net>; Wed, 11 Sep 2002 07:59:20 GMT
Received: from web40413.mail.yahoo.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web40413.mail.yahoo.com [66.218.78.110])
	id QQnfvb24065
	for <mpls@uu.net>; Wed, 11 Sep 2002 07:59:19 GMT
Message-ID: <20020911075919.63269.qmail@web40413.mail.yahoo.com>
Received: from [203.200.20.226] by web40413.mail.yahoo.com via HTTP; Wed, 11 Sep 2002 00:59:19 PDT
Date: Wed, 11 Sep 2002 00:59:19 -0700 (PDT)
From: sumit singh <singhksumit@yahoo.com>
Subject: Help regarding Bidierectional Contention Resolution/ GMPLS-rsvp-te
To: rsvp@isi.edu, mpls@UU.NET
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk

Hello,

I have a doubt in the ietf draft
"draft-ietf-mpls-generalised-rsvp-te-07.txt, Section
3.2, "Contention Resolution"

The draft says :

a consideration related to contention resolution is
that the neighbor's node ID might not be known when
sending an initial path message.  

I am not clear as to why is it that the node ID of the
neighbor would not be known while sending the initial
path message.

I would greatly appreciate any help on this.

-Sumit

__________________________________________________
Yahoo! - We Remember
9-11: A tribute to the more than 3,000 lives lost
http://dir.remember.yahoo.com/tribute



From owner-mpls@UU.NET  Wed Sep 11 13:28:57 2002
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 ESMTP id NAA17736
	for <mpls-archive@lists.ietf.org>; Wed, 11 Sep 2002 13:28:57 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfwo03548
	for <mpls-archive@lists.ietf.org>; Wed, 11 Sep 2002 17:30:32 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnfwn00039;
	Wed, 11 Sep 2002 17:28:54 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnfwn03627
	for mpls-outgoing; Wed, 11 Sep 2002 17:28:36 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnfwn03622
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 11 Sep 2002 17:28:29 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 QQnfwn03650
	for <mpls@uu.net>; Wed, 11 Sep 2002 17:27:35 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfwn00182
	for <mpls@uu.net>; Wed, 11 Sep 2002 17:27:35 GMT
Received: from smtp10.atl.mindspring.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: smtp10.atl.mindspring.net [207.69.200.246])
	id QQnfwn00174
	for <mpls@uu.net>; Wed, 11 Sep 2002 17:27:34 GMT
Received: from user-uinjm1v.dsl.mindspring.com ([165.121.216.63] helo=METANOIA)
	by smtp10.atl.mindspring.net with smtp (Exim 3.33 #1)
	id 17pBGu-0003m3-00; Wed, 11 Sep 2002 13:27:24 -0400
Reply-To: <v.sharma@ieee.org>
From: "Vishal Sharma" <v.sharma@ieee.org>
To: "Anna Charny" <acharny@cisco.com>
Cc: "Shahram Davari" <Shahram_Davari@pmc-sierra.com>,
        "'mpls@UU.net'" <mpls@UU.NET>
Subject: RE: Comments on Backup-Computation draft
Date: Wed, 11 Sep 2002 13:27:30 -0400
Message-ID: <MMECLKMDFPCEJFECIBCMEEPGCPAA.v.sharma@ieee.org>
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.2910.0)
Importance: Normal
In-Reply-To: <4.3.2.7.2.20020910102058.023868b8@pilgrim.cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Anna,

Thanks for your responses. Please see some comments in-line.
(I have some further comments on the draft, which I'm sending
in a separate email.)

-Vishal

> -----Original Message-----
> From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Anna
> Charny
> Sent: Tuesday, September 10, 2002 10:37 AM
> To: v.sharma@ieee.org
> Cc: Shahram Davari; 'mpls@UU.net'
> Subject: RE: Comments on Backup-Computation draft
>
>
> Hi Vishal,
>
> Please see below.
>
> At 10:01 AM 9/10/2002 -0400, Vishal Sharma wrote:
> >Anna, Shahram,
> >
> > > -----Original Message-----
> > > From: owner-mpls@UU.NET [mailto:owner-mpls@UU.NET]On Behalf Of Anna
> > > Charny
> > > Sent: Thursday, August 15, 2002 5:35 PM
> > > To: Shahram Davari
> > > Cc: 'mpls@UU.net'
> > > Subject: Re: Comments on Backup-Computation draft
> > >
> > >
> ><<snip>
> >
> >
> > > >8) Section 6.2.1 suggests finding the backup pool, by subtracting the
> > > >global reservable BW from the link BW. How does a node know the
> > > link BW to
> > > >do this computation?
> > >
> > > Here is an example with OSPF (link TLV of the TE opaque LSA):
> > >
> > > Sub-TLV 6 - Maximum Bandwidth
> > >
> > >     The Maximum Bandwidth sub-TLV specifies the maximum bandwidth that
> > >     can be used on this link in this direction (from the system
> > >     originating the LSA to its neighbor), in IEEE floating
> point format.
> > >     This is the true link capacity.
> > >
> > > Sub-TLV 7 - Maximum Reservable Bandwidth
> > >
> > >     The Maximum Reservable Bandwidth sub-TLV specifies the maximum
> > >     bandwidth that may be reserved on this link in this direction, in
> > >     IEEE floating point format
> > >
> > > Maximum bandwidth - Maximum Reservable Bandwidth = Backup
> bandwidth pool.
> > >
> >
> >I seem to recall that the maximum reservable bandwidth can, in fact, be
> >set to be _larger_ than the link capacity to allow for admitting
> >traffic/LSPs
> >whose cumulative b/w exceeds the maximum bandwidth, in those cases where
> >link oversubscription is allowed or desired.
> >
> >As a result, the backup bandwidth pool may not be directly derivable from
> >the simple calculation above, unless there an assumption of a
> network-wide
> >policy of
> >using no oversubscription.
>
> It is correct that the maximum reservable bandwidth may indeed be larger
> than link speed.  However, in the section of the draft that Shahram cites
> we explicitly say that the above computation can be used IF max
> reservable
> bandwidth is configured to be less than link speed.  This is not an
> entirely unreasonable setting as the context of the discussion is strict
> bandwidth protection.  Here is the quote:
>
> "Also, the backup pools can be implicitly derived from the routing
> information already available. This could be done by configuring
> max global
> reservable pool to being less than the link speed by the desired value of
> the backup pool. Every node computing its backup tunnels then can by
> default use link speed minus the max global reservable pool as
> the value of
> the backup pool to use in its computation of the backup tunnels
> placement. "

I agree that under the assumption of max. reservable b/w being configured
to being less than link speed, things are ok. However, it is not
clear that a SP that has BE and protected traffic in the network
would like to do that, since this does not allow for overbooking
for BE traffic.
(In that case an option might be to use the DiffServ TE extensions
appropriately, but I need to think more about that.)

Or, as you've suggested below, have an IGP extension that advertises
the backup bandwidth pool, which decouples it from max. reservable
bandwidth.

> However,  if the backup pool is propagated explicitly in the IGP
> extensions, as is really the preferred option for the distributed
> computation, then the backup bandwidth can be set up explicitly,
> independently of the max reservable global.  So under a single failure
> assumption, the effective maximum overbooking  on a given link would be
> essentially defined as the sum of max reservable bandwidth plus
> explicitly
> defined backup pool divided by the link speed.

Agreed.

> Finally, in the case of a centralized server the desired degree of
> overbooking (if any) can be specified in the server.
>
> Does this make sense to you?

Yes. In the case of a centralized server, of course there is complete
freedom in what can be configured, which policies can be applied etc.,
so that is a simpler case to talk about, in this sense.




From owner-mpls@UU.NET  Wed Sep 11 13:33:49 2002
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 ESMTP id NAA17982
	for <mpls-archive@lists.ietf.org>; Wed, 11 Sep 2002 13:33:49 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfwo22593
	for <mpls-archive@lists.ietf.org>; Wed, 11 Sep 2002 17:35:19 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnfwo21549;
	Wed, 11 Sep 2002 17:34:51 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnfwo03968
	for mpls-outgoing; Wed, 11 Sep 2002 17:34:36 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnfwo03963
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 11 Sep 2002 17:34: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 QQnfwo22079
	for <mpls@uu.net>; Wed, 11 Sep 2002 17:33:30 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfwo05520
	for <mpls@uu.net>; Wed, 11 Sep 2002 17:33:30 GMT
Received: from smtp10.atl.mindspring.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: smtp10.atl.mindspring.net [207.69.200.246])
	id QQnfwo05516
	for <mpls@uu.net>; Wed, 11 Sep 2002 17:33:30 GMT
Received: from user-uinjm1v.dsl.mindspring.com ([165.121.216.63] helo=METANOIA)
	by smtp10.atl.mindspring.net with smtp (Exim 3.33 #1)
	id 17pBMm-0001rE-00
	for mpls@uu.net; Wed, 11 Sep 2002 13:33:28 -0400
Reply-To: <v.sharma@ieee.org>
From: "Vishal Sharma" <v.sharma@ieee.org>
To: <mpls@UU.NET>
Subject: More comments on the Backup-Computation draft
Date: Wed, 11 Sep 2002 13:33:35 -0400
Message-ID: <MMECLKMDFPCEJFECIBCMIEPGCPAA.v.sharma@ieee.org>
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.50.4133.2400
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Anna,

As a continuation of my previous email, here are a few more comments
on the draft. Some are editorial, some technical.

-Vishal

i) The draft mentions at various points "See Section 11". I think
what is meant is probably Section 10.

ii) References [lakshman] pp. 7 and [MPLS_DIFF] pp. 23 seem to
be missing.

iii) The definition of MP on pp. 4 says "in case of one-to-one
backup, this is where multiple detours converge." Not sure why
this has to be?

iv) In Section 6.2, when discussing the distributed computation
model, the last line on pp. 13 states "But again IGP-TE extensions
is a benefit, not a requirement for this solution to work." If IGP-TE
extensions are not used, is the assumption that the backup bandwidth
pool for all links is explicitly configured at every node?
(since an explicitly defined backup bandwidth pool is one of the
key pieces of this [distributed] model).

v) Section 7, pp. 17, para 3, mentions that "the first case [a downstream
router fails but a link does not] is typically identifiable by means of
RSVP Hellos or some fast IGP Hellos mechanism". How so? If I don't receive
Hellos, I know I cannot reach my neighbor, but cannot say anything about
whether
my neighbor or our intervening link is down. Yes?

vi) Section 12 states that the PCS being stateless is the preferred
approach.
How so?
It seems that for the centralized computation model (with zero b/w
reservations
for backup LSPs) to work, the PCS must keep state on which primary and
backup
LSPs are placed where, on how much b/w each uses, and on the residual
bandwidth
of each network link.




From owner-mpls@UU.NET  Wed Sep 11 14:31:58 2002
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 ESMTP id OAA20490
	for <mpls-archive@lists.ietf.org>; Wed, 11 Sep 2002 14:31:57 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfws04008
	for <mpls-archive@lists.ietf.org>; Wed, 11 Sep 2002 18:33:35 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnfws03663;
	Wed, 11 Sep 2002 18:33:24 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnfws24760
	for mpls-outgoing; Wed, 11 Sep 2002 18:32:56 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnfws24755
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 11 Sep 2002 18:32: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 QQnfws28389
	for <mpls@uu.net>; Wed, 11 Sep 2002 18:31:03 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfws01487
	for <mpls@uu.net>; Wed, 11 Sep 2002 18:31:03 GMT
Received: from funnel.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnfws01475
	for <mpls@uu.net>; Wed, 11 Sep 2002 18:31:03 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id OAA07310 for <mpls@uu.net>; Wed, 11 Sep 2002 14:31:02 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8BIV2J16261 for mpls@uu.net; Wed, 11 Sep 2002 14:31:02 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQnfws24563
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 11 Sep 2002 18:30: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 QQnfws04042
	for <mpls@UU.NET>; Wed, 11 Sep 2002 18:30:20 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfws08279
	for <mpls@UU.NET>; Wed, 11 Sep 2002 18:30:19 GMT
Received: from pilgrim.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: pilgrim.cisco.com [161.44.168.94])
	id QQnfws08269
	for <mpls@UU.NET>; Wed, 11 Sep 2002 18:30:19 GMT
Received: from ACHARNY-W2K1.cisco.com (ch2-dhcp134-194.cisco.com [161.44.134.194])
	by pilgrim.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id OAA25435;
	Wed, 11 Sep 2002 14:30:06 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020911141934.025c54a8@pilgrim.cisco.com>
X-Sender: acharny@pilgrim.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 11 Sep 2002 14:30:05 -0400
To: <v.sharma@ieee.org>
From: Anna Charny <acharny@cisco.com>
Subject: RE: Comments on Backup-Computation draft
Cc: "Shahram Davari" <Shahram_Davari@pmc-sierra.com>,
        "'mpls@UU.net'" <mpls@UU.NET>
In-Reply-To: <MMECLKMDFPCEJFECIBCMEEPGCPAA.v.sharma@ieee.org>
References: <4.3.2.7.2.20020910102058.023868b8@pilgrim.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk

HI Vishal,

Please see  in-line....

<snip>

> > > > >8) Section 6.2.1 suggests finding the backup pool, by subtracting the
> > > > >global reservable BW from the link BW. How does a node know the
> > > > link BW to
> > > > >do this computation?
> > > >
> > > > Here is an example with OSPF (link TLV of the TE opaque LSA):
> > > >
> > > > Sub-TLV 6 - Maximum Bandwidth
> > > >
> > > >     The Maximum Bandwidth sub-TLV specifies the maximum bandwidth that
> > > >     can be used on this link in this direction (from the system
> > > >     originating the LSA to its neighbor), in IEEE floating
> > point format.
> > > >     This is the true link capacity.
> > > >
> > > > Sub-TLV 7 - Maximum Reservable Bandwidth
> > > >
> > > >     The Maximum Reservable Bandwidth sub-TLV specifies the maximum
> > > >     bandwidth that may be reserved on this link in this direction, in
> > > >     IEEE floating point format
> > > >
> > > > Maximum bandwidth - Maximum Reservable Bandwidth = Backup
> > bandwidth pool.
> > > >
> > >
> > >I seem to recall that the maximum reservable bandwidth can, in fact, be
> > >set to be _larger_ than the link capacity to allow for admitting
> > >traffic/LSPs
> > >whose cumulative b/w exceeds the maximum bandwidth, in those cases where
> > >link oversubscription is allowed or desired.
> > >
> > >As a result, the backup bandwidth pool may not be directly derivable from
> > >the simple calculation above, unless there an assumption of a
> > network-wide
> > >policy of
> > >using no oversubscription.
> >
> > It is correct that the maximum reservable bandwidth may indeed be larger
> > than link speed.  However, in the section of the draft that Shahram cites
> > we explicitly say that the above computation can be used IF max
> > reservable
> > bandwidth is configured to be less than link speed.  This is not an
> > entirely unreasonable setting as the context of the discussion is strict
> > bandwidth protection.  Here is the quote:
> >
> > "Also, the backup pools can be implicitly derived from the routing
> > information already available. This could be done by configuring
> > max global
> > reservable pool to being less than the link speed by the desired value of
> > the backup pool. Every node computing its backup tunnels then can by
> > default use link speed minus the max global reservable pool as
> > the value of
> > the backup pool to use in its computation of the backup tunnels
> > placement. "
>
>I agree that under the assumption of max. reservable b/w being configured
>to being less than link speed, things are ok. However, it is not
>clear that a SP that has BE and protected traffic in the network
>would like to do that, since this does not allow for overbooking
>for BE traffic.
>(In that case an option might be to use the DiffServ TE extensions
>appropriately, but I need to think more about that.)

Yes, we assumed that if you only want to protect some traffic but not all, 
then you may want to use DS-TE and specify
max reservable subpool as the primary pool you want to protect.  However, 
in a dynamic setting this would require having a system-wide understanding 
that this is what is being done, which is a risky assumption.

In general, I feel that without IGP extensions our approach has a valid but 
limited use in a dynamic setting, and that the IGP extensions are really 
going to make a difference in flexibility in the choice of how much 
bandwidth available for protection, and what the desired maximum 
overbooking is in case of failure.

>Or, as you've suggested below, have an IGP extension that advertises
>the backup bandwidth pool, which decouples it from max. reservable
>bandwidth.

yes, this seems to be the preferable option

Anna



From owner-mpls@UU.NET  Wed Sep 11 18:36:40 2002
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 ESMTP id SAA26950
	for <mpls-archive@lists.ietf.org>; Wed, 11 Sep 2002 18:36:40 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfxi01841
	for <mpls-archive@lists.ietf.org>; Wed, 11 Sep 2002 22:38:20 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnfxi01452;
	Wed, 11 Sep 2002 22:38:06 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnfxi18356
	for mpls-outgoing; Wed, 11 Sep 2002 22:37:39 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQnfxi18351
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 11 Sep 2002 22:37:29 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 QQnfxi04010
	for <mpls@uu.net>; Wed, 11 Sep 2002 22:37:22 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfxi14303
	for <mpls@uu.net>; Wed, 11 Sep 2002 22:37:21 GMT
Received: from funnel.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnfxi14299
	for <mpls@uu.net>; Wed, 11 Sep 2002 22:37:21 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id SAA26077 for <mpls@uu.net>; Wed, 11 Sep 2002 18:37:20 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8BMbKx11804 for mpls@uu.net; Wed, 11 Sep 2002 18:37:20 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQnfxb08309
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 11 Sep 2002 20:52: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 QQnfxb16620
	for <mpls@uu.net>; Wed, 11 Sep 2002 20:52:03 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfxb03744
	for <mpls@uu.net>; Wed, 11 Sep 2002 20:52:02 GMT
Received: from hotmail.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: f101.law4.hotmail.com [216.33.149.101])
	id QQnfxb03715
	for <mpls@uu.net>; Wed, 11 Sep 2002 20:52:02 GMT
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Wed, 11 Sep 2002 13:52:01 -0700
Received: from 47.248.0.42 by lw4fd.law4.hotmail.msn.com with HTTP;
	Wed, 11 Sep 2002 20:52:01 GMT
X-Originating-IP: [47.248.0.42]
From: "Ye Ding" <yeding71@hotmail.com>
To: mpls@UU.NET
Subject: question on EXP in shim header
Date: Wed, 11 Sep 2002 16:52:01 -0400
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F101WZzREUdsjTjd9qc0000d6ab@hotmail.com>
X-OriginalArrivalTime: 11 Sep 2002 20:52:01.0424 (UTC) FILETIME=[13C2E100:01C259D5]
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

I got a question and thanks for help.

In the edge LSR, use E-LSP, how could the EXP bits in shim header be set for 
supporting diffserv or not supporting diffserv? Is there any RFC talking 
about this?

Thanks,,
Ye



_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx



From owner-mpls@UU.NET  Thu Sep 12 07:59:09 2002
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 ESMTP id HAA20052
	for <mpls-archive@lists.ietf.org>; Thu, 12 Sep 2002 07:59:09 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfzk03931
	for <mpls-archive@lists.ietf.org>; Thu, 12 Sep 2002 12:00:48 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnfzk03203;
	Thu, 12 Sep 2002 12:00:31 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnfzk19264
	for mpls-outgoing; Thu, 12 Sep 2002 12:00:14 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnfzk19101
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 12 Sep 2002 12:00: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 QQnfzk24806
	for <mpls@uu.net>; Thu, 12 Sep 2002 12:00:08 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfzk22302
	for <mpls@uu.net>; Thu, 12 Sep 2002 12:00:07 GMT
Received: from funnel.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnfzk22285
	for <mpls@uu.net>; Thu, 12 Sep 2002 12:00:07 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id IAA28812 for <mpls@uu.net>; Thu, 12 Sep 2002 08:00:06 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8CC06O03504 for mpls@uu.net; Thu, 12 Sep 2002 08:00:06 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnfzj17328
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 12 Sep 2002 11:59:04 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 QQnfzj21133
	for <mpls@uu.net>; Thu, 12 Sep 2002 11:59:00 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfzj02287
	for <mpls@uu.net>; Thu, 12 Sep 2002 11:58:59 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 QQnfzj02282
	for <mpls@uu.net>; Thu, 12 Sep 2002 11:58:59 GMT
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19964;
	Thu, 12 Sep 2002 07:57:18 -0400 (EDT)
Message-Id: <200209121157.HAA19964@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-ldp-restart-04.txt
Date: Thu, 12 Sep 2002 07:57:17 -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		: Graceful Restart Mechanism for LDP
	Author(s)	: M. Leelanivas, Y. Rekhter, R. Aggarwal
	Filename	: draft-ietf-mpls-ldp-restart-04.txt
	Pages		: 12
	Date		: 2002-9-11
	
This document describes a mechanism that helps to minimize the
negative effects on MPLS traffic caused by Label Switching Router's
(LSR's) control plane restart, and specifically by the restart of its
Label Distribution Protocol (LDP) component, on LSRs that are capable
of preserving the MPLS forwarding component across the restart.
The mechanism described in this document is applicable to all LSRs,
both those with the ability to preserve forwarding state during LDP
restart and those without (although the latter need to implement only
a subset of the mechanism described in this document).  Supporting (a
subset of) the mechanism described here by the LSRs that can not
preserve their MPLS forwarding state across the restart would not
reduce the negative impact on MPLS traffic caused by their control
plane restart, but it would minimize the impact if their neighbor(s)
are capable of preserving the forwarding state across the restart of
their control plane and implement the mechanism described here.
The mechanism makes minimalistic assumptions on what has to be
preserved across restart - the mechanism assumes that only the actual
MPLS forwarding state has to be preserved; the mechanism does not
require any of the LDP-related state to be preserved across the
restart.
The procedures described in this document apply to downstream
unsolicited label distribution. Extending these procedures to
downstream on demand label distribution is for further study.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-mpls-ldp-restart-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-ldp-restart-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:	<2002-9-11142422.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--




From owner-mpls@UU.NET  Thu Sep 12 10:51:28 2002
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 ESMTP id KAA25481
	for <mpls-archive@lists.ietf.org>; Thu, 12 Sep 2002 10:51:28 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfzv20836
	for <mpls-archive@lists.ietf.org>; Thu, 12 Sep 2002 14:53:07 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnfzv20629;
	Thu, 12 Sep 2002 14:53:03 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnfzv19208
	for mpls-outgoing; Thu, 12 Sep 2002 14:52:49 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQnfzv19198
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 12 Sep 2002 14:52:40 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 QQnfzv05329
	for <mpls@uu.net>; Thu, 12 Sep 2002 14:52:09 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfzv16798
	for <mpls@uu.net>; Thu, 12 Sep 2002 14:52:08 GMT
Received: from funnel.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnfzv16793
	for <mpls@uu.net>; Thu, 12 Sep 2002 14:52:08 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id KAA10094 for <mpls@uu.net>; Thu, 12 Sep 2002 10:52:08 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8CEq8e21766 for mpls@uu.net; Thu, 12 Sep 2002 10:52:08 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQnfzk20282
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 12 Sep 2002 12:00: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 QQnfzj28645
	for <mpls@uu.net>; Thu, 12 Sep 2002 11:59:05 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnfzj02315
	for <mpls@uu.net>; Thu, 12 Sep 2002 11:59:04 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 QQnfzj02307
	for <mpls@uu.net>; Thu, 12 Sep 2002 11:59:04 GMT
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19982;
	Thu, 12 Sep 2002 07:57:22 -0400 (EDT)
Message-Id: <200209121157.HAA19982@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-hierarchy-08.txt
Date: Thu, 12 Sep 2002 07:57:22 -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		: LSP Hierarchy with Generalized MPLS TE
	Author(s)	: K. Kompella, Y. Rekhter
	Filename	: draft-ietf-mpls-lsp-hierarchy-08.txt
	Pages		: 13
	Date		: 2002-9-11
	
To improve scalability of Generalized Multi-Protocol Label Switching
(GMPLS) it may be useful to aggregate Label Switched Paths (LSPs) by
creating a hierarchy of such LSPs.  A way to create such a hierarchy
is by (a) a Label Switching Router (LSR) creating a Traffic
Engineering Label Switched Path (TE LSP), (b) the LSR forming a
forwarding adjacency (FA) out of that LSP (by advertising this LSP as
a Traffic Engineering (TE) link into the same instance of ISIS/OSPF
as the one that was used to create the LSP), (c) allowing other LSRs
to use FAs for their path computation, and (d) nesting of LSPs
originated by other LSRs into that LSP (by using the label stack
construct).
This document describes the mechanisms to accomplish this.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-hierarchy-08.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-hierarchy-08.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:	<2002-9-11142431.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mpls-lsp-hierarchy-08.txt

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

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

--OtherAccess--

--NextPart--




From owner-mpls@UU.NET  Thu Sep 12 12:34:06 2002
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 ESMTP id MAA28532
	for <mpls-archive@lists.ietf.org>; Thu, 12 Sep 2002 12:34:06 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngac21621
	for <mpls-archive@lists.ietf.org>; Thu, 12 Sep 2002 16:35:46 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngac21354;
	Thu, 12 Sep 2002 16:35:37 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngac29569
	for mpls-outgoing; Thu, 12 Sep 2002 16:35:20 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQngac29564
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 12 Sep 2002 16:35: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 QQngac09341
	for <mpls@uu.net>; Thu, 12 Sep 2002 16:35:04 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngac23352
	for <mpls@uu.net>; Thu, 12 Sep 2002 16:35:03 GMT
Received: from funnel.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQngac23343
	for <mpls@uu.net>; Thu, 12 Sep 2002 16:35:03 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id MAA18749 for <mpls@uu.net>; Thu, 12 Sep 2002 12:35:03 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8CGZ3403597 for mpls@uu.net; Thu, 12 Sep 2002 12:35:03 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQngac29532
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 12 Sep 2002 16:33:52 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 QQngac01094
	for <mpls@UU.NET>; Thu, 12 Sep 2002 16:32:50 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngac19990
	for <mpls@UU.NET>; Thu, 12 Sep 2002 16:32:50 GMT
Received: from pilgrim.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: pilgrim.cisco.com [161.44.168.94])
	id QQngac19984
	for <mpls@UU.NET>; Thu, 12 Sep 2002 16:32:49 GMT
Received: from ACHARNY-W2K1.cisco.com (acharny-frame1.cisco.com [10.84.14.34])
	by pilgrim.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id MAA23463;
	Thu, 12 Sep 2002 12:32:48 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020912121153.025c0bb8@pilgrim.cisco.com>
X-Sender: acharny@pilgrim.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 12 Sep 2002 12:32:47 -0400
To: <v.sharma@ieee.org>
From: Anna Charny <acharny@cisco.com>
Subject: Re: More comments on the Backup-Computation draft
Cc: <mpls@UU.NET>
In-Reply-To: <MMECLKMDFPCEJFECIBCMIEPGCPAA.v.sharma@ieee.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi Vishal,

Thanks a lot  for the comments. Please see in-line...

At 01:33 PM 9/11/2002 -0400, Vishal Sharma wrote:
>Hi Anna,
>
>As a continuation of my previous email, here are a few more comments
>on the draft. Some are editorial, some technical.
>
>-Vishal
>
>i) The draft mentions at various points "See Section 11". I think
>what is meant is probably Section 10.

yes, you are right - thanks for noticing. Will correct

>ii) References [lakshman] pp. 7 and [MPLS_DIFF] pp. 23 seem to
>be missing.

Yes, we also noticed that - will add the references

>iii) The definition of MP on pp. 4 says "in case of one-to-one
>backup, this is where multiple detours converge." Not sure why
>this has to be?

I am not sure I understand your concern?  It must be some wording issue 
here that I am missing. What would you say instead?

>iv) In Section 6.2, when discussing the distributed computation
>model, the last line on pp. 13 states "But again IGP-TE extensions
>is a benefit, not a requirement for this solution to work." If IGP-TE
>extensions are not used, is the assumption that the backup bandwidth
>pool for all links is explicitly configured at every node?
>(since an explicitly defined backup bandwidth pool is one of the
>key pieces of this [distributed] model).


We probably should clarify exactly what we mean here - I agree that the way 
we say may be misleading.
Let me try to explain what we really wanted to say - see if it makes sense. 
What we really meant was that there is a *limited* set of circumstances 
where the distributed model could work without IGP extensions.  For 
example, if the desire is to have strict bandwidth protection for the 
entire reservable bandwidth on a link (sort of a SONET replacement 
strategy), the max reservable bandwidth is configured to be strictly less 
than link speed on enough links, then the backup pool can be explicitly 
computed from the link speed and max reservable bandwidth.   Note that this 
does not really prevent configuring max reservable banwidth to exceed link 
capacity on *some* links. Strictly speaking you need to have non-zero 
backup pool on just enough links to be able to protect the traffic. Just 
exactly what is enough is very dependent on topology, of course.

That said, if no IGP extensions are defined for the backup pool, one is 
stuck with having some sort of network-wide policy that would allow 
deriving what the amount of backup bandwidth is that is available for the 
computation implicitly from the already available parameters.  You are 
quite right that for distributed model to support more flexible protection 
strategies, the IGP extension defining the value of the backup pool is 
necessary.



>v) Section 7, pp. 17, para 3, mentions that "the first case [a downstream
>router fails but a link does not] is typically identifiable by means of
>RSVP Hellos or some fast IGP Hellos mechanism". How so? If I don't receive
>Hellos, I know I cannot reach my neighbor, but cannot say anything about
>whether
>my neighbor or our intervening link is down. Yes?

You are quite right that if you do not receive a Hello, then just by that 
fact you cannot tell whether it is a link or a node.  But the case that we 
describe above and that we believe IS identifiable, is when you know two 
things:

1) the link is UP
2) there are no Hellos

Then you do know it is the node that failed.  The case where we cannot tell 
(and that is what requires additional currently undefined mechanisms) is 
when the link is DOWN. Then of course there are no Hellos as well, and you 
cannot say whether it is the link or the node.


>vi) Section 12 states that the PCS being stateless is the preferred
>approach.
>How so?
>It seems that for the centralized computation model (with zero b/w
>reservations
>for backup LSPs) to work, the PCS must keep state on which primary and
>backup
>LSPs are placed where, on how much b/w each uses, and on the residual
>bandwidth
>of each network link.

We meant to say that it is for the distributed approach that it is 
preferable to have a stateless PCS.  We should make sure it is clear from 
the text. You are quite right that in the centralized model (or at least in 
some implementations of the centralized model), the server cannot be 
stateless.  Note however that a centralized model COULD be stateless as 
well if what it is backing up is the bandwidth pools rather than the actual 
amount of used primary bandwidth.

Does this make sense?

Anna 



From owner-mpls@UU.NET  Fri Sep 13 07:47:34 2002
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 ESMTP id HAA01619
	for <mpls-archive@lists.ietf.org>; Fri, 13 Sep 2002 07:47:34 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngdb29997
	for <mpls-archive@lists.ietf.org>; Fri, 13 Sep 2002 11:49:16 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngdb29777;
	Fri, 13 Sep 2002 11:49:11 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngdb03158
	for mpls-outgoing; Fri, 13 Sep 2002 11:48:55 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQngdb03153
	for <mpls@mail-control.ash.ops.us.uu.net>; Fri, 13 Sep 2002 11:48: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 QQngdb24221
	for <mpls@uu.net>; Fri, 13 Sep 2002 11:48:04 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngdb29081
	for <mpls@uu.net>; Fri, 13 Sep 2002 11:48:04 GMT
Received: from funnel.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQngdb29076
	for <mpls@uu.net>; Fri, 13 Sep 2002 11:48:03 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id HAA23806 for <mpls@uu.net>; Fri, 13 Sep 2002 07:48:03 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8DBm3D29095 for mpls@uu.net; Fri, 13 Sep 2002 07:48:03 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQngdb03118
	for <mpls@mail-control.ash.ops.us.uu.net>; Fri, 13 Sep 2002 11:46:58 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 QQngdb20641
	for <mpls@uu.net>; Fri, 13 Sep 2002 11:46:38 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngdb28230
	for <mpls@uu.net>; Fri, 13 Sep 2002 11:46:38 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 QQngdb28219
	for <mpls@uu.net>; Fri, 13 Sep 2002 11:46:37 GMT
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01475;
	Fri, 13 Sep 2002 07:44:54 -0400 (EDT)
Message-Id: <200209131144.HAA01475@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-recovery-frmwrk-07.txt
Date: Fri, 13 Sep 2002 07:44:54 -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		: Framework for MPLS-based Recovery
	Author(s)	: V. Sharma, F. Hellstrand
	Filename	: draft-ietf-mpls-recovery-frmwrk-07.txt
	Pages		: 32
	Date		: 2002-9-12
	
Multi-protocol label switching (MPLS) integrates the label swapping 
forwarding paradigm with network layer routing. To deliver reliable 
service, MPLS requires a set of procedures to provide protection of 
the traffic carried on different paths. This requires that the label 
switched routers (LSRs) support fault detection, fault notification, 
and fault recovery mechanisms, and that MPLS signaling, support the 
configuration of recovery. With these objectives in mind, this 
document specifies a framework for MPLS based recovery.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-recovery-frmwrk-07.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-recovery-frmwrk-07.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:	<2002-9-12143645.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mpls-recovery-frmwrk-07.txt

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

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

--OtherAccess--

--NextPart--




From owner-mpls@UU.NET  Fri Sep 13 13:30:26 2002
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 ESMTP id NAA13075
	for <mpls-archive@lists.ietf.org>; Fri, 13 Sep 2002 13:30:26 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngdy19993
	for <mpls-archive@lists.ietf.org>; Fri, 13 Sep 2002 17:32:06 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngdy19420;
	Fri, 13 Sep 2002 17:31:51 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngdy06776
	for mpls-outgoing; Fri, 13 Sep 2002 17:31:31 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQngdy06771
	for <mpls@mail-control.ash.ops.us.uu.net>; Fri, 13 Sep 2002 17:31: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 QQngdy15135
	for <mpls@uu.net>; Fri, 13 Sep 2002 17:30:50 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngdy22502
	for <mpls@uu.net>; Fri, 13 Sep 2002 17:30:49 GMT
Received: from mail.san.yahoo.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail.san.yahoo.com [209.132.1.30])
	id QQngdy22498
	for <mpls@uu.net>; Fri, 13 Sep 2002 17:30:49 GMT
Received: from [207.172.11.150] by mail.san.yahoo.com with HTTP; Fri, 13 Sep 2002 10:33:53 -0700
Date: Fri, 13 Sep 2002 13:33:53 -0400
Message-ID: <3D7548710000A95B@mta08.san.yahoo.com>
From: "Kavita Khanna" <kkhanna@isocore.com>
Subject: MPLS 2002: Washington DC, Oct 27-29
To: mpls@UU.NET
MIME-Version: 1.0
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 NAA13075

The MPLS 2002 International Conference website at http://www.mpls2002.com
has been updated with technical program and speaker details. Full online
credit card processing for conference registrations is also now available
at:
   http://mpls2002.com/onlineregis.htm

The early registration fees are extremely attractive and we hope that you
can benefit from the opportunity and pre-register for MPLS2002 soon. 

Conference Details:
   MPLS2002 International Conference
   5th Annual International Conference on MPLS
   October 27-29, 2002
   Omni Shoreham Hotel, Washington, DC
   Tutorials: Oct 27, 1:00-6:00 pm
   Conference sessions: October 28-29 8:30am-6:00pm
   Exhibits: Oct 28, 8:30am-7:00 & Oct 28, 8:30am-3:00pm
   3rd Public Inter-Op Demo: October 30




From owner-mpls@UU.NET  Mon Sep 16 06:53:57 2002
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 ESMTP id GAA29968
	for <mpls-archive@lists.ietf.org>; Mon, 16 Sep 2002 06:53:57 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngnz14385
	for <mpls-archive@lists.ietf.org>; Mon, 16 Sep 2002 10:55:38 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngnz13510;
	Mon, 16 Sep 2002 10:55:11 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngnz08506
	for mpls-outgoing; Mon, 16 Sep 2002 10:54:49 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQngnz08501
	for <mpls@mail-control.ash.ops.us.uu.net>; Mon, 16 Sep 2002 10: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 QQngnz13942
	for <mpls@uu.net>; Mon, 16 Sep 2002 10:54:04 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngnz08433
	for <mpls@uu.net>; Mon, 16 Sep 2002 10:54:04 GMT
Received: from funnel.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQngnz08428
	for <mpls@uu.net>; Mon, 16 Sep 2002 10:54:03 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id GAA13506 for <mpls@uu.net>; Mon, 16 Sep 2002 06:54:03 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8GAs3B21136 for mpls@uu.net; Mon, 16 Sep 2002 06:54:03 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQngnz08470
	for <mpls@mail-control.ash.ops.us.uu.net>; Mon, 16 Sep 2002 10:52:37 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 QQngnz05729
	for <mpls@uu.net>; Mon, 16 Sep 2002 10:52:16 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngnz09763
	for <mpls@uu.net>; Mon, 16 Sep 2002 10:52:15 GMT
Received: from ganesh.ctd.hctech.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.64.2])
	id QQngnz09699
	for <mpls@uu.net>; Mon, 16 Sep 2002 10:52:14 GMT
Received: by GANESH with Internet Mail Service (5.5.2653.19)
	id <TA190VRP>; Mon, 16 Sep 2002 16:25:59 +0530
Message-ID: <55E277B99171E041ABF5F4B1C6DDCA06865403@haritha.hclt.com>
From: "Vijayanand C - CTD, Chennai." <vijayc@ctd.hcltech.com>
To: mpls@UU.NET
Subject: interarea- Te
Date: Mon, 16 Sep 2002 16:24:23 +0530
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 all,
I was looking for some material on interarea-mpls-te. I could not get the
draft 'draft-venkatachalam-interarea-mpls-te-03'. as it has expired and when
I tried to contact the authors the mail IDs seem to be invalid. 

Does anyone have pointers to the above draft or any similar material

Vijay



From owner-mpls@UU.NET  Mon Sep 16 08:37:43 2002
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 ESMTP id IAA02339
	for <mpls-archive@lists.ietf.org>; Mon, 16 Sep 2002 08:37:42 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngog29259
	for <mpls-archive@lists.ietf.org>; Mon, 16 Sep 2002 12:39:26 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngog29017;
	Mon, 16 Sep 2002 12:39:19 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngog15404
	for mpls-outgoing; Mon, 16 Sep 2002 12:38:56 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQngog15399
	for <mpls@mail-control.ash.ops.us.uu.net>; Mon, 16 Sep 2002 12:38:50 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 QQngog27707
	for <mpls@UU.NET>; Mon, 16 Sep 2002 12:36:59 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngog11979
	for <mpls@UU.NET>; Mon, 16 Sep 2002 12:36:59 GMT
Received: from pimout2-ext.prodigy.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: pimout2-ext.prodigy.net [207.115.63.101])
	id QQngog11925
	for <mpls@UU.NET>; Mon, 16 Sep 2002 12:36:55 GMT
Received: from ieee.org (adsl-64-171-188-215.dsl.snfc21.pacbell.net [64.171.188.215])
	by pimout2-ext.prodigy.net (8.12.3 da nor stuldap/8.12.3) with ESMTP id g8GCalIZ086780;
	Mon, 16 Sep 2002 08:36:48 -0400
Message-ID: <3D85CCF2.931A9ED3@ieee.org>
Date: Mon, 16 Sep 2002 05:22:10 -0700
From: Sudheer Dharanikota <sudheer@ieee.org>
X-Mailer: Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: "Vijayanand C - CTD, Chennai." <vijayc@ctd.hcltech.com>
CC: mpls@UU.NET
Subject: Re: interarea- Te
References: <55E277B99171E041ABF5F4B1C6DDCA06865403@haritha.hclt.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Vijay:

Here is the path to this draft..

http://www.cs.odu.edu/~sudheer/technical/contributions/standards/ietf/draft-venkatachalam-interarea-mpls-te-02.txt

Please let me know if you have any questions.

- sudheer

"Vijayanand C - CTD, Chennai." wrote:

> Hello all,
> I was looking for some material on interarea-mpls-te. I could not get the
> draft 'draft-venkatachalam-interarea-mpls-te-03'. as it has expired and when
> I tried to contact the authors the mail IDs seem to be invalid.
>
> Does anyone have pointers to the above draft or any similar material
>
> Vijay



From owner-mpls@UU.NET  Mon Sep 16 13:22:13 2002
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 ESMTP id NAA11662
	for <mpls-archive@lists.ietf.org>; Mon, 16 Sep 2002 13:22:12 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngoz23444
	for <mpls-archive@lists.ietf.org>; Mon, 16 Sep 2002 17:23:54 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngoz23079;
	Mon, 16 Sep 2002 17:23:44 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngoz26491
	for mpls-outgoing; Mon, 16 Sep 2002 17:23:31 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQngoz26486
	for <mpls@mail-control.ash.ops.us.uu.net>; Mon, 16 Sep 2002 17:23:15 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 QQngoz24830
	for <mpls@uu.net>; Mon, 16 Sep 2002 17:22:04 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngoz28554
	for <mpls@uu.net>; Mon, 16 Sep 2002 17:22:04 GMT
Received: from funnel.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQngoz28546
	for <mpls@uu.net>; Mon, 16 Sep 2002 17:22:03 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id NAA10452 for <mpls@uu.net>; Mon, 16 Sep 2002 13:22:03 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8GHM3T00484 for mpls@uu.net; Mon, 16 Sep 2002 13:22:03 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQngoz26308
	for <mpls@mail-control.ash.ops.us.uu.net>; Mon, 16 Sep 2002 17:21: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 QQngoz13408
	for <mpls@UU.NET>; Mon, 16 Sep 2002 17:20:29 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngoz27060
	for <mpls@UU.NET>; Mon, 16 Sep 2002 17:20:29 GMT
Received: from cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: europe.cisco.com [144.254.52.73])
	id QQngoz27049
	for <mpls@UU.NET>; Mon, 16 Sep 2002 17:20:28 GMT
Received: from JVASSEUR-W2K.cisco.com (dhcp-161-44-145-20.cisco.com [161.44.145.20])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id TAA07922;
	Mon, 16 Sep 2002 19:20:22 +0200 (MET DST)
Message-Id: <4.3.2.7.2.20020916131621.0377ebb8@paris.cisco.com>
X-Sender: jvasseur@paris.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 16 Sep 2002 13:20:21 -0400
To: "Vijayanand C - CTD, Chennai." <vijayc@ctd.hcltech.com>
From: Jean Philippe Vasseur <jvasseur@cisco.com>
Subject: Re: interarea- Te
Cc: mpls@UU.NET
In-Reply-To: <55E277B99171E041ABF5F4B1C6DDCA06865403@haritha.hclt.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

At 16:24 16/09/2002 +0530, Vijayanand C - CTD, Chennai. wrote:
>Hello all,
>I was looking for some material on interarea-mpls-te. I could not get the
>draft 'draft-venkatachalam-interarea-mpls-te-03'. as it has expired and when
>I tried to contact the authors the mail IDs seem to be invalid.
>
>Does anyone have pointers to the above draft or any similar material

You can read draft-ash-multi-area-te-compare-00.txt that gives an overview 
of the different approaches.

You can also read: draft-kompella-mpls-multiarea-te-03.txt

JP.

>Vijay



From owner-mpls@UU.NET  Tue Sep 17 04:33:44 2002
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 ESMTP id EAA07608
	for <mpls-archive@lists.ietf.org>; Tue, 17 Sep 2002 04:33:44 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngri29636
	for <mpls-archive@lists.ietf.org>; Tue, 17 Sep 2002 08:35:22 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngri29128;
	Tue, 17 Sep 2002 08:35:08 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngri05078
	for mpls-outgoing; Tue, 17 Sep 2002 08:34:39 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQngri05071
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 17 Sep 2002 08:34: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 QQngri28401
	for <mpls@uu.net>; Tue, 17 Sep 2002 08:33:06 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngri00139
	for <mpls@uu.net>; Tue, 17 Sep 2002 08:33:06 GMT
Received: from web20309.mail.yahoo.com by cmr0.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web20309.mail.yahoo.com [216.136.226.90])
	id QQngri00135
	for <mpls@uu.net>; Tue, 17 Sep 2002 08:33:05 GMT
Message-ID: <20020917083305.97739.qmail@web20309.mail.yahoo.com>
Received: from [203.200.20.226] by web20309.mail.yahoo.com via HTTP; Tue, 17 Sep 2002 01:33:05 PDT
Date: Tue, 17 Sep 2002 01:33:05 -0700 (PDT)
From: Mareline Sheldon <marelines@yahoo.com>
Subject: GMPLS Doubt
To: mpls@UU.NET
Cc: jyates@research.att.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,
I am aware that this is a MPLS mailing list but since i could not get this doubt clarified
from any other place .. 

This is in reference to "Challenges for MPLS in Optical Network Restoration" by Robert
Doverspike and Jennifer Yates which appeared in IEEE Communications Magazine (Feb 2001)

The authors say that an "Optical transport system (OTS) multiplexes multiple optical signals
onto a common fiber, necessitating the concept of a channel. An optical network connection is
provisioned by cross connecting channels within individual OTSs along its path. This fact
implies that zero-bandwidth paths cannot be established for later use. In contrast, in IP
networks MPLS LSPs may be established such that if no packets  are switched into the links
along the path, no bandwidth is consumed. Switching packets onto these predefined paths at
their endpoints is simple and rapid. This important difference between IP and optical networks
becomes crucial in allocating restoration capacity"

Can somebody help me understand the above?

regards,
mareline s.


__________________________________________________
Do you Yahoo!?
Yahoo! News - Today's headlines
http://news.yahoo.com


From owner-mpls@UU.NET  Tue Sep 17 04:54:12 2002
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 ESMTP id EAA07853
	for <mpls-archive@lists.ietf.org>; Tue, 17 Sep 2002 04:54:12 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngrj21283
	for <mpls-archive@lists.ietf.org>; Tue, 17 Sep 2002 08:55:55 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngrj21006;
	Tue, 17 Sep 2002 08:55:48 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngrj06689
	for mpls-outgoing; Tue, 17 Sep 2002 08:55:33 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQngrj06683
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 17 Sep 2002 08:55: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 QQngrj06870
	for <mpls@UU.NET>; Tue, 17 Sep 2002 08:54:46 GMT
From: suchauhan@hss.hns.com
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngrj21660
	for <mpls@UU.NET>; Tue, 17 Sep 2002 08:54:46 GMT
Received: from hindon.hss.co.in by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.26.202])
	id QQngrj21631
	for <mpls@UU.NET>; Tue, 17 Sep 2002 08:54:44 GMT
Received: from hindon.hss.co.in (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id g8H8scS23390
	for <mpls@UU.NET>; Tue, 17 Sep 2002 14:24:38 +0530 (IST)
Received: from ultra.hss.co.in (ultra.hss.hns.com [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id g8H8sai23377;
	Tue, 17 Sep 2002 14:24:36 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with SMTP id g8H8tgT20056;
	Tue, 17 Sep 2002 14:25:42 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256C37.0030785A ; Tue, 17 Sep 2002 14:19:25 +0530
X-Lotus-FromDomain: HSS
To: Mareline Sheldon <marelines@yahoo.com>
cc: mpls@UU.NET, jyates@research.att.com
Message-ID: <65256C37.0030780A.00@sandesh.hss.hns.com>
Date: Tue, 17 Sep 2002 14:19:43 +0530
Subject: Re: GMPLS Doubt
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-mpls@UU.NET
Precedence: bulk



hi Marline!
     In the case of using MPLS for IP, the consumable resource is a label that
is assigned to the FEC/flow of IP packets.
     In that respect once an LSP is setup the label is assigned for all traffic
belonging to that FEC/flow to be switched on
     this LSP. If these is no traffic to be forwarded on that LSP then the label
remains in use but the bandwidth of the
     outgoing link is free to be used/shared by other LSP. Again the assumption
here is that the TE policies in use
     allow/necessitate such a sharing/use by other LSPs.

     In case of GMPLS (more so in case of Optical domain) the label itself
generally maps to a frequency/wavelength for
     the optical stream. Once a label(frequency) is being assigned to a
FEC/(optical)flow, then the OXC all along the LSP
     reserve this frequency for this flow. Hence it cannot be shared between
other LSPs.

     In this regard the restoration capacity allocation for failure conditions
in Optical domain have to be dome more
     prudently as the reserved paths (backup paths) are actually equivalent to
allocating bandwidth even though they are
     not carrying data in case there is no failure/restoration.

     I hope this is of some help to you!

regards
sumit




Mareline Sheldon <marelines@yahoo.com> on 09/17/2002 02:03:05 PM

To:   mpls@UU.NET
cc:   jyates@research.att.com (bcc: Sumit Chauhan/HSS)

Subject:  GMPLS Doubt




Hi,
I am aware that this is a MPLS mailing list but since i could not get this doubt
clarified
from any other place ..

This is in reference to "Challenges for MPLS in Optical Network Restoration" by
Robert
Doverspike and Jennifer Yates which appeared in IEEE Communications Magazine
(Feb 2001)

The authors say that an "Optical transport system (OTS) multiplexes multiple
optical signals
onto a common fiber, necessitating the concept of a channel. An optical network
connection is
provisioned by cross connecting channels within individual OTSs along its path.
This fact
implies that zero-bandwidth paths cannot be established for later use. In
contrast, in IP
networks MPLS LSPs may be established such that if no packets  are switched into
the links
along the path, no bandwidth is consumed. Switching packets onto these
predefined paths at
their endpoints is simple and rapid. This important difference between IP and
optical networks
becomes crucial in allocating restoration capacity"

Can somebody help me understand the above?

regards,
mareline s.


__________________________________________________
Do you Yahoo!?
Yahoo! News - Today's headlines
http://news.yahoo.com






From owner-mpls@UU.NET  Tue Sep 17 05:18:31 2002
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 ESMTP id FAA08274
	for <mpls-archive@lists.ietf.org>; Tue, 17 Sep 2002 05:18:31 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngrl22379
	for <mpls-archive@lists.ietf.org>; Tue, 17 Sep 2002 09:20:15 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngrl22117;
	Tue, 17 Sep 2002 09:20:09 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngrl25163
	for mpls-outgoing; Tue, 17 Sep 2002 09:19:53 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQngrl25156
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 17 Sep 2002 09:19:50 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 QQngrl00563
	for <mpls@uu.net>; Tue, 17 Sep 2002 09:19:48 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngrl21638
	for <mpls@uu.net>; Tue, 17 Sep 2002 09:19:47 GMT
Received: from web20306.mail.yahoo.com by cmr1.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web20306.mail.yahoo.com [216.136.226.87])
	id QQngrl21630
	for <mpls@uu.net>; Tue, 17 Sep 2002 09:19:47 GMT
Message-ID: <20020917091946.66352.qmail@web20306.mail.yahoo.com>
Received: from [203.200.20.226] by web20306.mail.yahoo.com via HTTP; Tue, 17 Sep 2002 02:19:46 PDT
Date: Tue, 17 Sep 2002 02:19:46 -0700 (PDT)
From: Mareline Sheldon <marelines@yahoo.com>
Subject: Nodal Fault
To: mpls@UU.NET
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,
As i understand, the Nodal faults belong to the genre of faults wherein the control plane at
the node fails while all the data plane connections are maintained. This could be if the
reachability to the neighbouring nodes is lost, or the control processor fails or after a
restart or RSVP daemon crashes.

Can there be any other scenario when this may happen i.e control plane information is lost but
data plane is still preserved.

regards,
mareline s.



__________________________________________________
Do you Yahoo!?
Yahoo! News - Today's headlines
http://news.yahoo.com


From owner-mpls@UU.NET  Tue Sep 17 07:19:45 2002
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 ESMTP id HAA10374
	for <mpls-archive@lists.ietf.org>; Tue, 17 Sep 2002 07:19:45 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngrt28976
	for <mpls-archive@lists.ietf.org>; Tue, 17 Sep 2002 11:21:28 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngrt28717;
	Tue, 17 Sep 2002 11:21:20 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngrt06596
	for mpls-outgoing; Tue, 17 Sep 2002 11:20:54 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQngrt06589
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 17 Sep 2002 11:20: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 QQngrt17417
	for <mpls@UU.NET>; Tue, 17 Sep 2002 11:19:45 GMT
From: suchauhan@hss.hns.com
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngrt18089
	for <mpls@UU.NET>; Tue, 17 Sep 2002 11:19:44 GMT
Received: from hindon.hss.co.in by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.26.202])
	id QQngrt18054
	for <mpls@UU.NET>; Tue, 17 Sep 2002 11:19:43 GMT
Received: from hindon.hss.co.in (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id g8HBJaS18915
	for <mpls@UU.NET>; Tue, 17 Sep 2002 16:49:37 +0530 (IST)
Received: from ultra.hss.co.in (ultra.hss.hns.com [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id g8HBJZi18903;
	Tue, 17 Sep 2002 16:49:35 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with SMTP id g8HBKeG01369;
	Tue, 17 Sep 2002 16:50:40 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256C37.003DBDBA ; Tue, 17 Sep 2002 16:44:22 +0530
X-Lotus-FromDomain: HSS
To: Mareline Sheldon <marelines@yahoo.com>
cc: mpls@UU.NET
Message-ID: <65256C37.003DBCD8.00@sandesh.hss.hns.com>
Date: Tue, 17 Sep 2002 16:44:39 +0530
Subject: Re: Nodal Fault
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-mpls@UU.NET
Precedence: bulk



hi Mareline!
     IMHO Nodal faults is a genre of faults that include both the data and
control path failure. The case of just the control path failing shall be a
special case of a Nodal fault.

     Generally the signalling protocols are so designed that they should come to
know immediately of the node (control plane) going down and take corrective
action. Whether the data plane is up or not is I guess irrelevant for the
corrective action as     there is no reliable means to determine this (as the
control path is down).

best regards,
sumit




Mareline Sheldon <marelines@yahoo.com> on 09/17/2002 02:49:46 PM

To:   mpls@UU.NET
cc:    (bcc: Sumit Chauhan/HSS)

Subject:  Nodal Fault




Hi,
As i understand, the Nodal faults belong to the genre of faults wherein the
control plane at
the node fails while all the data plane connections are maintained. This could
be if the
reachability to the neighbouring nodes is lost, or the control processor fails
or after a
restart or RSVP daemon crashes.

Can there be any other scenario when this may happen i.e control plane
information is lost but
data plane is still preserved.

regards,
mareline s.



__________________________________________________
Do you Yahoo!?
Yahoo! News - Today's headlines
http://news.yahoo.com






From owner-mpls@UU.NET  Tue Sep 17 08:03:25 2002
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 ESMTP id IAA11483
	for <mpls-archive@lists.ietf.org>; Tue, 17 Sep 2002 08:03:25 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngrw18219
	for <mpls-archive@lists.ietf.org>; Tue, 17 Sep 2002 12:05:09 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngrw17944;
	Tue, 17 Sep 2002 12:05:02 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngrw24991
	for mpls-outgoing; Tue, 17 Sep 2002 12:04:33 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQngrw24977
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 17 Sep 2002 12:04:24 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 QQngrw02014
	for <mpls@uu.net>; Tue, 17 Sep 2002 12:04:04 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngrw01600
	for <mpls@uu.net>; Tue, 17 Sep 2002 12:04:04 GMT
Received: from funnel.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQngrw01594
	for <mpls@uu.net>; Tue, 17 Sep 2002 12:04:03 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id IAA11409 for <mpls@uu.net>; Tue, 17 Sep 2002 08:04:03 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8HC43423289 for mpls@uu.net; Tue, 17 Sep 2002 08:04:03 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQngrw18651
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 17 Sep 2002 12:02: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 QQngrw25979
	for <mpls@uu.net>; Tue, 17 Sep 2002 12:02:07 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngrw02881
	for <mpls@uu.net>; Tue, 17 Sep 2002 12:02:06 GMT
Received: from ietf.org by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: odin.ietf.org [132.151.1.176])
	id QQngrw02864
	for <mpls@uu.net>; Tue, 17 Sep 2002 12:02:06 GMT
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11295;
	Tue, 17 Sep 2002 08:00:20 -0400 (EDT)
Message-Id: <200209171200.IAA11295@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-ldp-ft-05.txt
Date: Tue, 17 Sep 2002 08:00:20 -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		: Fault Tolerance for the Label Distribution Protocol 
                          (LDP)
	Author(s)	: A. Farrel
	Filename	: draft-ietf-mpls-ldp-ft-05.txt
	Pages		: 52
	Date		: 2002-9-16
	
Multiprotocol Label Switching (MPLS) systems will be used
in core networks where system downtime must be kept to an
absolute minimum.  Many MPLS Label Switching Routers
(LSRs) may, therefore, exploit Fault Tolerant (FT)
hardware or software to provide high availability of the
core networks.
The details of how FT is achieved for the various
components of an FT LSR, including Label Distribution
Protocol (LDP), the switching hardware and TCP, are
implementation specific.  This document identifies issues
in the LDP specification in RFC 3036 'LDP Specification'
that make it difficult to implement an FT LSR using the
current LDP protocols, and proposes enhancements to the
LDP specification to ease such FT LSR implementations.
The issues and extensions described here are equally
applicable to RFC 3212, 'Constraint-Based LSP Setup Using
LDP' (CR-LDP).

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mpls-ldp-ft-05.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:	<2002-9-16152010.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mpls-ldp-ft-05.txt

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

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

--OtherAccess--

--NextPart--




From owner-mpls@UU.NET  Tue Sep 17 09:38:33 2002
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 ESMTP id JAA14478
	for <mpls-archive@lists.ietf.org>; Tue, 17 Sep 2002 09:38:33 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngsc06703
	for <mpls-archive@lists.ietf.org>; Tue, 17 Sep 2002 13:40:16 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngsc06542;
	Tue, 17 Sep 2002 13:40:11 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngsc19253
	for mpls-outgoing; Tue, 17 Sep 2002 13:39:56 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQngsc19248
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 17 Sep 2002 13:39: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 QQngsc09894
	for <mpls@uu.net>; Tue, 17 Sep 2002 13:38:53 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngsc02424
	for <mpls@uu.net>; Tue, 17 Sep 2002 13:38:53 GMT
Received: from aibo.runbox.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: aibo.runbox.com [193.71.199.94])
	id QQngsc02416
	for <mpls@uu.net>; Tue, 17 Sep 2002 13:38:52 GMT
Received: from [10.9.9.110] (helo=snoopy.runbox.com)
	by tramp.runbox.com with esmtp (Exim 4.05-VA-mm1)
	id 17rIZ2-0005BV-00
	for mpls@uu.net; Tue, 17 Sep 2002 15:38:52 +0200
Received: from [203.200.20.226] (helo=Manav)
	(Authenticated Sender=davidwaters)
	by snoopy.runbox.com with asmtp (Exim 3.35 #1)
	id 17rIYt-00085R-00
	for mpls@UU.NET; Tue, 17 Sep 2002 15:38:43 +0200
Message-ID: <002501c25e4f$7f40b690$b4036c6b@sisodomain.com>
From: "David Waters" <davidwaters@runbox.com>
To: <mpls@UU.NET>
References: <65256C37.003DBCD8.00@sandesh.hss.hns.com>
Subject: Re: Nodal Fault
Date: Tue, 17 Sep 2002 19:08:16 +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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sumit,
IMHO this is not the exact picture. Let me attempt to rephrase it.
The nodal faults and the control channel faults only apply when there are
mechanisms to detect data channel failures independent of the control
channel failures. Because otherwise all our just faults. We in our design
can detect them independently since data faults are recognized by (1) loss
of light or (2) SONET/SDH detects transport layer failure, etc. Nodal
faults then apply when we loose control information but we still maintain
the data plane connections. This can happen in many cases (as mentioned in
the original mail).

What i believe Mareline wants to know is that how other than the examples
which she (i assume!) cited can we have a scenario when we loose the
control plane information but still retain the data plane info.

This is something like the "hitless" concept we have in our routing
protocols wherein we maintain our routing protocol adjacencies if our
daemon goes down till certain time period (assuming that the forwarding
plane is intact!). If the daemon comes up in that time then our neighbours
never come to know of that flap and if it doesnt then we inform everybody
about it!

The chances of this happening are fairly high in distributed architectures
where the control process is running on a separate processor and the
forwarding on the other (the NPs!)

just my 2 cents.

----- Original Message -----
From: <suchauhan@hss.hns.com>
To: "Mareline Sheldon" <marelines@yahoo.com>
Cc: <mpls@UU.NET>
Sent: Tuesday, September 17, 2002 4:44 PM
Subject: Re: Nodal Fault


|
|
| hi Mareline!
|      IMHO Nodal faults is a genre of faults that include both the data
and
| control path failure. The case of just the control path failing shall be
a
| special case of a Nodal fault.
|
|      Generally the signalling protocols are so designed that they should
come to
| know immediately of the node (control plane) going down and take
corrective
| action. Whether the data plane is up or not is I guess irrelevant for the
| corrective action as     there is no reliable means to determine this (as
the
| control path is down).
|
| best regards,
| sumit
|
|
|
|
| Mareline Sheldon <marelines@yahoo.com> on 09/17/2002 02:49:46 PM
|
| To:   mpls@UU.NET
| cc:    (bcc: Sumit Chauhan/HSS)
|
| Subject:  Nodal Fault
|
|
|
|
| Hi,
| As i understand, the Nodal faults belong to the genre of faults wherein
the
| control plane at
| the node fails while all the data plane connections are maintained. This
could
| be if the
| reachability to the neighbouring nodes is lost, or the control processor
fails
| or after a
| restart or RSVP daemon crashes.
|
| Can there be any other scenario when this may happen i.e control plane
| information is lost but
| data plane is still preserved.
|
| regards,
| mareline s.
|
|
|
| __________________________________________________
| Do you Yahoo!?
| Yahoo! News - Today's headlines
| http://news.yahoo.com
|
|
|
|



From owner-mpls@UU.NET  Tue Sep 17 09:38:34 2002
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 ESMTP id JAA14492
	for <mpls-archive@lists.ietf.org>; Tue, 17 Sep 2002 09:38:34 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngsc17034
	for <mpls-archive@lists.ietf.org>; Tue, 17 Sep 2002 13:40:18 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngsc16661;
	Tue, 17 Sep 2002 13:40:08 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngsc19246
	for mpls-outgoing; Tue, 17 Sep 2002 13:39:45 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQngsc19241
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 17 Sep 2002 13:39:36 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 QQngsc09848
	for <mpls@uu.net>; Tue, 17 Sep 2002 13:38:53 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngsc05593
	for <mpls@uu.net>; Tue, 17 Sep 2002 13:38:52 GMT
Received: from mailhost.metro-optix.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [64.219.248.6])
	id QQngsc05589
	for <mpls@uu.net>; Tue, 17 Sep 2002 13:38:52 GMT
Received: by mailhost.metro-optix.com with Internet Mail Service (5.5.2653.19)
	id <SPWD4LKV>; Tue, 17 Sep 2002 08:36:37 -0500
Message-ID: <99EC34181384D611BE56000347227B2C019341@MAILHOSTNB>
From: Mohit Misra <mohit.misra@metro-optix.com>
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: RE: Nodal Fault
Date: Tue, 17 Sep 2002 19:09:47 -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

Well, the similar case arises during the system startup though you don't
call it a nodal fault.
During the startup all the cross connections (that were persisted) are
restored first before the RSVP gets started. Restoring the cross connection
would be taken care by the Connection memory of the switch rather than the
RSVP during the startup. RSVP can then use the restart cap to restore the
control plane.

						Mohit

-----Original Message-----
From: suchauhan@hss.hns.com [mailto:suchauhan@hss.hns.com]
Sent: Tuesday, September 17, 2002 4:45 PM
To: Mareline Sheldon
Cc: mpls@UU.NET
Subject: Re: Nodal Fault




hi Mareline!
     IMHO Nodal faults is a genre of faults that include both the data and
control path failure. The case of just the control path failing shall be a
special case of a Nodal fault.

     Generally the signalling protocols are so designed that they should
come to
know immediately of the node (control plane) going down and take corrective
action. Whether the data plane is up or not is I guess irrelevant for the
corrective action as     there is no reliable means to determine this (as
the
control path is down).

best regards,
sumit




Mareline Sheldon <marelines@yahoo.com> on 09/17/2002 02:49:46 PM

To:   mpls@UU.NET
cc:    (bcc: Sumit Chauhan/HSS)

Subject:  Nodal Fault




Hi,
As i understand, the Nodal faults belong to the genre of faults wherein the
control plane at
the node fails while all the data plane connections are maintained. This
could
be if the
reachability to the neighbouring nodes is lost, or the control processor
fails
or after a
restart or RSVP daemon crashes.

Can there be any other scenario when this may happen i.e control plane
information is lost but
data plane is still preserved.

regards,
mareline s.



__________________________________________________
Do you Yahoo!?
Yahoo! News - Today's headlines
http://news.yahoo.com





From owner-mpls@UU.NET  Tue Sep 17 09:55:01 2002
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 ESMTP id JAA15011
	for <mpls-archive@lists.ietf.org>; Tue, 17 Sep 2002 09:55:00 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngsd08322
	for <mpls-archive@lists.ietf.org>; Tue, 17 Sep 2002 13:56:41 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngsd07898;
	Tue, 17 Sep 2002 13:56:29 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngsd20561
	for mpls-outgoing; Tue, 17 Sep 2002 13:56:07 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQngsd20548
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 17 Sep 2002 13:56:07 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 QQngsd29738
	for <mpls@uu.net>; Tue, 17 Sep 2002 13:55:13 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngsd06090
	for <mpls@uu.net>; Tue, 17 Sep 2002 13:55:12 GMT
Received: from funnel.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQngsd06085
	for <mpls@uu.net>; Tue, 17 Sep 2002 13:55:12 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id JAA17732 for <mpls@uu.net>; Tue, 17 Sep 2002 09:55:12 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8HDtBv04667 for mpls@uu.net; Tue, 17 Sep 2002 09:55:11 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQngsc18727
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 17 Sep 2002 13:31: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 QQngsc04882
	for <mpls@UU.NET>; Tue, 17 Sep 2002 13:31:18 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngsc25927
	for <mpls@UU.NET>; Tue, 17 Sep 2002 13:31:18 GMT
Received: from mailhost.metro-optix.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [64.219.248.6])
	id QQngsc25912
	for <mpls@UU.NET>; Tue, 17 Sep 2002 13:31:17 GMT
Received: by mailhost.metro-optix.com with Internet Mail Service (5.5.2653.19)
	id <SPWD4LHF>; Tue, 17 Sep 2002 08:28:52 -0500
Message-ID: <99EC34181384D611BE56000347227B2C01933E@MAILHOSTNB>
From: Mohit Misra <mohit.misra@metro-optix.com>
To: "'suchauhan@hss.hns.com'" <suchauhan@hss.hns.com>,
        Mareline Sheldon
	 <marelines@yahoo.com>
Cc: mpls@UU.NET
Subject: RE: Nodal Fault
Date: Tue, 17 Sep 2002 19:02:02 -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

Well, the similar case arises during the system startup though you don't
call it a nodal fault.
During the startup all the cross connections (that were persisted) are
restored first before the RSVP gets started. Restoring the cross connection
would be taken care by the Connection memory of the switch rather than the
RSVP during the startup. RSVP can then use the restart cap to restore the
control plane.

-----Original Message-----
From: suchauhan@hss.hns.com [mailto:suchauhan@hss.hns.com]
Sent: Tuesday, September 17, 2002 4:45 PM
To: Mareline Sheldon
Cc: mpls@UU.NET
Subject: Re: Nodal Fault




hi Mareline!
     IMHO Nodal faults is a genre of faults that include both the data and
control path failure. The case of just the control path failing shall be a
special case of a Nodal fault.

     Generally the signalling protocols are so designed that they should
come to
know immediately of the node (control plane) going down and take corrective
action. Whether the data plane is up or not is I guess irrelevant for the
corrective action as     there is no reliable means to determine this (as
the
control path is down).

best regards,
sumit




Mareline Sheldon <marelines@yahoo.com> on 09/17/2002 02:49:46 PM

To:   mpls@UU.NET
cc:    (bcc: Sumit Chauhan/HSS)

Subject:  Nodal Fault




Hi,
As i understand, the Nodal faults belong to the genre of faults wherein the
control plane at
the node fails while all the data plane connections are maintained. This
could
be if the
reachability to the neighbouring nodes is lost, or the control processor
fails
or after a
restart or RSVP daemon crashes.

Can there be any other scenario when this may happen i.e control plane
information is lost but
data plane is still preserved.

regards,
mareline s.



__________________________________________________
Do you Yahoo!?
Yahoo! News - Today's headlines
http://news.yahoo.com





From owner-mpls@UU.NET  Tue Sep 17 12:47:27 2002
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 ESMTP id MAA21298
	for <mpls-archive@lists.ietf.org>; Tue, 17 Sep 2002 12:47:27 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngsp13830
	for <mpls-archive@lists.ietf.org>; Tue, 17 Sep 2002 16:49:11 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngsp13624;
	Tue, 17 Sep 2002 16:49:04 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngsp22657
	for mpls-outgoing; Tue, 17 Sep 2002 16:48:30 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQngsp22641
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 17 Sep 2002 16:48:13 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 QQngsp24451
	for <mpls@uu.net>; Tue, 17 Sep 2002 16:46:24 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngsp11698
	for <mpls@uu.net>; Tue, 17 Sep 2002 16:46:24 GMT
Received: from funnel.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQngsp11690
	for <mpls@uu.net>; Tue, 17 Sep 2002 16:46:23 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id MAA05147 for <mpls@uu.net>; Tue, 17 Sep 2002 12:46:23 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8HGkNo24555 for mpls@uu.net; Tue, 17 Sep 2002 12:46:23 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQngsc18727
	for <mpls@mail-control.ash.ops.us.uu.net>; Tue, 17 Sep 2002 13:31: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 QQngsc04882
	for <mpls@UU.NET>; Tue, 17 Sep 2002 13:31:18 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngsc25927
	for <mpls@UU.NET>; Tue, 17 Sep 2002 13:31:18 GMT
Received: from mailhost.metro-optix.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [64.219.248.6])
	id QQngsc25912
	for <mpls@UU.NET>; Tue, 17 Sep 2002 13:31:17 GMT
Received: by mailhost.metro-optix.com with Internet Mail Service (5.5.2653.19)
	id <SPWD4LHF>; Tue, 17 Sep 2002 08:28:52 -0500
Message-ID: <99EC34181384D611BE56000347227B2C01933E@MAILHOSTNB>
From: Mohit Misra <mohit.misra@metro-optix.com>
To: "'suchauhan@hss.hns.com'" <suchauhan@hss.hns.com>,
        Mareline Sheldon
	 <marelines@yahoo.com>
Cc: mpls@UU.NET
Subject: RE: Nodal Fault
Date: Tue, 17 Sep 2002 19:02:02 -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

Well, the similar case arises during the system startup though you don't
call it a nodal fault.
During the startup all the cross connections (that were persisted) are
restored first before the RSVP gets started. Restoring the cross connection
would be taken care by the Connection memory of the switch rather than the
RSVP during the startup. RSVP can then use the restart cap to restore the
control plane.

-----Original Message-----
From: suchauhan@hss.hns.com [mailto:suchauhan@hss.hns.com]
Sent: Tuesday, September 17, 2002 4:45 PM
To: Mareline Sheldon
Cc: mpls@UU.NET
Subject: Re: Nodal Fault




hi Mareline!
     IMHO Nodal faults is a genre of faults that include both the data and
control path failure. The case of just the control path failing shall be a
special case of a Nodal fault.

     Generally the signalling protocols are so designed that they should
come to
know immediately of the node (control plane) going down and take corrective
action. Whether the data plane is up or not is I guess irrelevant for the
corrective action as     there is no reliable means to determine this (as
the
control path is down).

best regards,
sumit




Mareline Sheldon <marelines@yahoo.com> on 09/17/2002 02:49:46 PM

To:   mpls@UU.NET
cc:    (bcc: Sumit Chauhan/HSS)

Subject:  Nodal Fault




Hi,
As i understand, the Nodal faults belong to the genre of faults wherein the
control plane at
the node fails while all the data plane connections are maintained. This
could
be if the
reachability to the neighbouring nodes is lost, or the control processor
fails
or after a
restart or RSVP daemon crashes.

Can there be any other scenario when this may happen i.e control plane
information is lost but
data plane is still preserved.

regards,
mareline s.



__________________________________________________
Do you Yahoo!?
Yahoo! News - Today's headlines
http://news.yahoo.com





From owner-mpls@UU.NET  Wed Sep 18 01:11:47 2002
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 ESMTP id BAA09308
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 01:11:46 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngum16746
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 05:13:32 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngum16350;
	Wed, 18 Sep 2002 05:13:22 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngum19446
	for mpls-outgoing; Wed, 18 Sep 2002 05:13:08 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQngum19441
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 05:13:05 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 QQngum27189
	for <mpls@UU.NET>; Wed, 18 Sep 2002 05:12:20 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngum00907
	for <mpls@UU.NET>; Wed, 18 Sep 2002 05:12:20 GMT
Received: from caduceus.jf.intel.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: fmr06.intel.com [134.134.136.7])
	id QQngum00893
	for <mpls@UU.NET>; Wed, 18 Sep 2002 05:12:19 GMT
Received: from talaria.jf.intel.com (talaria.jf.intel.com [10.7.209.7])
	by caduceus.jf.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.50 2002/08/30 20:04:57 dmccart Exp $) with ESMTP id g8I5A8l15374
	for <mpls@UU.NET>; Wed, 18 Sep 2002 05:10:08 GMT
Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206])
	by talaria.jf.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.24 2002/08/30 20:04:21 dmccart Exp $) with SMTP id g8I54Tp23233
	for <mpls@UU.NET>; Wed, 18 Sep 2002 05:04:29 GMT
Received: from orsmsx26.jf.intel.com ([192.168.65.26])
 by orsmsxvs040.jf.intel.com (NAVGW 2.5.2.11) with SMTP id M2002091722144310347
 for <mpls@UU.NET>; Tue, 17 Sep 2002 22:14:43 -0700
Received: by orsmsx26.jf.intel.com with Internet Mail Service (5.5.2653.19)
	id <TB3RZT6Q>; Tue, 17 Sep 2002 22:12:15 -0700
Message-ID: <12B638FEE763F74696D8544752E7204812EA17@bgsmsx101.iind.intel.com>
From: "Ramia, Kannan Babu" <kannan.babu.ramia@intel.com>
To: "MPLS (E-mail)" <mpls@UU.NET>
Subject: Clarification on Handling a specific event in LDP
Date: Tue, 17 Sep 2002 22:07:45 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C25ED1.53610C00"
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_01C25ED1.53610C00
Content-Type: text/plain;
	charset="iso-8859-1"

Hi all
 
    I am encountering a peculiar situation where I need some clarification.
 
    Here is my problem
 
    My LSR A acts in DOD ordered mode (also assumed all the other LSRs in
the domain acts in the same mode). For a particular FEC X it has found
itself as an Egress LSR and it knows that the penultimate LSR B supports
IMPLICIT NULL LABEL and it distributed a NULL Label for that FEC X. Now in
the data plane at my LSR it will receive only unlabeled packets since the
penultimate LSR pops the label in the packet (assuming no stacking of
labels).
 
    Now in later point of time if some other LSR C gets added to this MPLS
Domain which happens to be my Next Hop for the FEC X. Now my LSR will become
an intermediate LSR for that particular FEC-X and it will request a label
from LSR C and install it in the forwarding plane. Now the problem arises
because it had distributed an NULL Label in the upstream, so before
installing this new label it needs to withdraw the NULL label from its
penultimate LSR B and redistribute a new label so that LSR B wont acts like
a proxy egress for this FEC-X. If we send a label withdraw message then that
message will progressively travel in the upstream direction and the whole
Lsp context will be lost. Since LSR A now send a new label map for the same
FEC-X the LSR B which receives it, will not propagate because it has been
configured as a DOD ordered mode.
 
    Can anyone suggest any solution to this problem...
 
 
I have a solution for this problem.
Basically if any LSR receives an Label withdraw message from its valid Next
hop neighbor then before propagating to its upstream peers it need to check
the value of the label being withdrawn, if the label happens to be an NULL
label then it should not propagate the label withdraw to its upstream peers.
Now this LSR should now assume itself as an egress for that LSP. 
 
Second one could be there should be a provision to change the label for the
particular FEC. I.e any point of time the valid next hop LSR can advertise a
change of label for that FEC. Here problems are we need to maintain the
context of that advertisement (LM).
 
Kannan Babu
Senior Network Software Engineer
Network Software Division
Intel Corporation         
Bangalore
841 2333 extn 2506
 

------_=_NextPart_001_01C25ED1.53610C00
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

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

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C25F00.0A4CA8B0">
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
span.EmailStyle15
	{mso-style-type:personal-compose;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:black;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
 /* List Definitions */
@list l0
	{mso-list-id:1853716948;
	mso-list-type:hybrid;
	mso-list-template-ids:-2075867266 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
</head>

<body lang=3DEN-US style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>Hi all<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><span style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp; </span>I am
encountering a peculiar situation where I need some =
clarification.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><span style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp; </span>Here =
is my
problem<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><span style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp; </span>My =
LSR A acts
in DOD ordered mode (also assumed all the other LSRs in the domain acts =
in the
same mode). For a particular FEC X it has found itself as an Egress LSR =
and it
knows that the penultimate LSR B supports IMPLICIT NULL LABEL and it
distributed a NULL Label for that FEC X. Now in the data plane at my =
LSR it will
receive only unlabeled packets since the penultimate LSR pops the label =
in the
packet (assuming no stacking of =
labels).<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><span style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp; </span>Now =
in later
point of time if some other LSR C gets added to this MPLS Domain which =
happens
to be my Next Hop for the FEC X. Now my LSR will become an intermediate =
LSR for
that particular FEC-X and it will request a label from LSR C and =
install it in
the forwarding plane. Now the problem arises because it had distributed =
an NULL
Label in the upstream, so before installing this new label it needs to =
withdraw
the NULL label from its penultimate LSR B and redistribute a new label =
so that
LSR B wont acts like a proxy egress for this FEC-X. If we send a label =
withdraw
message then that message will progressively travel in the upstream =
direction
and the whole Lsp context will be lost. Since LSR A now send a new =
label map
for the same FEC-X the LSR B which receives it, will not propagate =
because it has
been configured as a DOD ordered =
mode.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><span style=3D"mso-spacerun: yes">&nbsp;&nbsp;&nbsp; </span>Can =
anyone suggest
any solution to this problem&#8230;<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>I have a solution for this =
problem.<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>Basically if any LSR receives an Label withdraw message from its =
valid
Next hop neighbor then before propagating to its upstream peers it need =
to
check the value of the label being withdrawn, if the label happens to =
be an
NULL label then it should not propagate the label withdraw to its =
upstream
peers. Now this LSR should now assume itself as an egress for that LSP. =
<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>Second one could be there should be a provision to change the =
label for
the particular FEC. I.e any point of time the valid next hop LSR can =
advertise
a change of label for that FEC. Here problems are we need to maintain =
the
context of that advertisement (LM).<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><!--[if supportFields]><font color=3Dblack><span=20
style=3D'color:black'><span =
style=3D'mso-element:field-begin'></span><span=20
style=3D"mso-spacerun: yes">&nbsp;</span>AUTOTEXTLIST \s &quot;E-mail=20
Signature&quot; <span =
style=3D'mso-element:field-separator'></span></span></font><![endif]--><=
font
size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
color:black'>Kannan Babu</span></font><font size=3D2 =
color=3Dblack><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;color:black;mso-colo=
r-alt:
windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;color:black'>Senior =
Network
Software Engineer</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:
10.0pt;mso-bidi-font-size:12.0pt;color:black;mso-color-alt:windowtext'><=
o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;color:black'>Network=
 Software
Division</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;color:black;mso-color-alt:windowtext'><o:p></o=
:p></span></font></p>

<p class=3DMsoNormal style=3D'tab-stops:88.3pt'><font size=3D2 =
color=3Dblack
face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
color:black'>Intel Corporation<span =
style=3D'mso-tab-count:1'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; </span></span></font><font
size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
color:black;mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;color:black'>Bangalo=
re</span></font><font
size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
color:black;mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;color:black'>841 =
2333 extn
2506</span></font><font size=3D2 color=3Dblack><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:12.0pt;color:black;mso-color-alt:windowtext'><o:p></o=
:p></span></font></p>

<p class=3DMsoNormal><!--[if supportFields]><font color=3Dblack><span=20
style=3D'color:black'><span =
style=3D'mso-element:field-end'></span></span></font><![endif]--><font
color=3Dblack><span style=3D'color:black'><![if =
!supportEmptyParas]>&nbsp;<![endif]></span></font><font
color=3Dblack><span =
style=3D'color:black;mso-color-alt:windowtext'><o:p></o:p></span></font>=
</p>

</div>

</body>

</html>

------_=_NextPart_001_01C25ED1.53610C00--


From owner-mpls@UU.NET  Wed Sep 18 01:22:29 2002
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 ESMTP id BAA09493
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 01:22:29 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngun03581
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 05:24:14 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngun03194;
	Wed, 18 Sep 2002 05:24:04 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngun20299
	for mpls-outgoing; Wed, 18 Sep 2002 05:23:47 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQngun20294
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 05:23:35 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 QQngun09017
	for <mpls@UU.NET>; Wed, 18 Sep 2002 05:23:07 GMT
From: suchauhan@hss.hns.com
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngun29100
	for <mpls@UU.NET>; Wed, 18 Sep 2002 05:23:07 GMT
Received: from hindon.hss.co.in by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.26.202])
	id QQngun29078
	for <mpls@UU.NET>; Wed, 18 Sep 2002 05:23:05 GMT
Received: from hindon.hss.co.in (localhost [127.0.0.1])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id g8I5MmS02431
	for <mpls@UU.NET>; Wed, 18 Sep 2002 10:52:48 +0530 (IST)
Received: from ultra.hss.co.in (ultra.hss.hns.com [192.168.100.5])
	by hindon.hss.co.in (8.10.0/8.10.0) with ESMTP id g8I5Mai02416;
	Wed, 18 Sep 2002 10:52:36 +0530 (IST)
Received: from sandesh.hss.hns.com (localhost [127.0.0.1])
	by ultra.hss.co.in (8.10.0/8.10.0) with SMTP id g8I5Nf111285;
	Wed, 18 Sep 2002 10:53:42 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256C38.001D0E75 ; Wed, 18 Sep 2002 10:47:22 +0530
X-Lotus-FromDomain: HSS
To: "David Waters" <davidwaters@runbox.com>
cc: mpls@UU.NET
Message-ID: <65256C38.001D0DE1.00@sandesh.hss.hns.com>
Date: Wed, 18 Sep 2002 10:47:37 +0530
Subject: Re: Nodal Fault
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-mpls@UU.NET
Precedence: bulk



David!
     I mostly agree with your points except a few. Please see my 2 pennies
inline ;o).

kind regards,
sumit





"David Waters" <davidwaters@runbox.com> on 09/17/2002 07:08:16 PM

To:   mpls@UU.NET
cc:    (bcc: Sumit Chauhan/HSS)

Subject:  Re: Nodal Fault




Sumit,
IMHO this is not the exact picture. Let me attempt to rephrase it.
The nodal faults and the control channel faults only apply when there are
mechanisms to detect data channel failures independent of the control
channel failures. Because otherwise all our just faults. We in our design
can detect them independently since data faults are recognized by (1) loss
of light or (2) SONET/SDH detects transport layer failure, etc. Nodal
faults then apply when we loose control information but we still maintain
the data plane connections. This can happen in many cases (as mentioned in
the original mail).
#################################>>>>sumit
You are correct in saying that the faults in the data plane and control plane
can be segregated but the point I wanted to make is that the design of the
signalling and the routing protocols (control plane) should be such that they
support it. Considering that the routing or signalling deamon goes down and the
reliable (e.g. TCP session in LDP) is timed out on the other side before the
data plane comes up again, then whether we are retaining the datapath
information or not is immaterial. This is cos' the signalling protocol will
assume that the node has failed and will take corrective action. Do I still miss
something?
##################################>>>>>

What i believe Mareline wants to know is that how other than the examples
which she (i assume!) cited can we have a scenario when we loose the
control plane information but still retain the data plane info.

This is something like the "hitless" concept we have in our routing
protocols wherein we maintain our routing protocol adjacencies if our
daemon goes down till certain time period (assuming that the forwarding
plane is intact!). If the daemon comes up in that time then our neighbours
never come to know of that flap and if it doesnt then we inform everybody
about it!
#################################>>>>sumit
What is critical in the hitless concept is that the timeout of the session
between control plane peers is longer than the time the deamon takes to come up
again after failure. If not then essentially the control plane failure will be
treated (by the peer deamons) as a node failure and
corrective/restoration/backup action will be taken.
##################################>>>>>
The chances of this happening are fairly high in distributed architectures
where the control process is running on a separate processor and the
forwarding on the other (the NPs!)

just my 2 cents.

----- Original Message -----
From: <suchauhan@hss.hns.com>
To: "Mareline Sheldon" <marelines@yahoo.com>
Cc: <mpls@UU.NET>
Sent: Tuesday, September 17, 2002 4:44 PM
Subject: Re: Nodal Fault


|
|
| hi Mareline!
|      IMHO Nodal faults is a genre of faults that include both the data
and
| control path failure. The case of just the control path failing shall be
a
| special case of a Nodal fault.
|
|      Generally the signalling protocols are so designed that they should
come to
| know immediately of the node (control plane) going down and take
corrective
| action. Whether the data plane is up or not is I guess irrelevant for the
| corrective action as     there is no reliable means to determine this (as
the
| control path is down).
|
| best regards,
| sumit
|
|
|
|
| Mareline Sheldon <marelines@yahoo.com> on 09/17/2002 02:49:46 PM
|
| To:   mpls@UU.NET
| cc:    (bcc: Sumit Chauhan/HSS)
|
| Subject:  Nodal Fault
|
|
|
|
| Hi,
| As i understand, the Nodal faults belong to the genre of faults wherein
the
| control plane at
| the node fails while all the data plane connections are maintained. This
could
| be if the
| reachability to the neighbouring nodes is lost, or the control processor
fails
| or after a
| restart or RSVP daemon crashes.
|
| Can there be any other scenario when this may happen i.e control plane
| information is lost but
| data plane is still preserved.
|
| regards,
| mareline s.
|
|
|
| __________________________________________________
| Do you Yahoo!?
| Yahoo! News - Today's headlines
| http://news.yahoo.com
|
|
|
|







From owner-mpls@UU.NET  Wed Sep 18 02:07:26 2002
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 ESMTP id CAA19358
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 02:07:26 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnguq16054
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 06:09:08 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnguq15596;
	Wed, 18 Sep 2002 06:08:54 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnguq09109
	for mpls-outgoing; Wed, 18 Sep 2002 06:08:27 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQnguq09103
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 06:08: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 QQnguq04927
	for <mpls@uu.net>; Wed, 18 Sep 2002 06:08:04 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnguq04680
	for <mpls@uu.net>; Wed, 18 Sep 2002 06:08:03 GMT
Received: from funnel.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnguq04672
	for <mpls@uu.net>; Wed, 18 Sep 2002 06:08:03 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id CAA22443 for <mpls@uu.net>; Wed, 18 Sep 2002 02:08:02 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8I682c15564 for mpls@uu.net; Wed, 18 Sep 2002 02:08:02 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQnguq08804
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 06:06: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 QQnguq05815
	for <mpls@uu.net>; Wed, 18 Sep 2002 06:06:30 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnguq13637
	for <mpls@uu.net>; Wed, 18 Sep 2002 06:06:30 GMT
Received: from ganesh.ctd.hctech.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.64.2])
	id QQnguq13618
	for <mpls@uu.net>; Wed, 18 Sep 2002 06:06:28 GMT
Received: by GANESH with Internet Mail Service (5.5.2653.19)
	id <TA10BK6L>; Wed, 18 Sep 2002 11:40:06 +0530
Message-ID: <55E277B99171E041ABF5F4B1C6DDCA0688568D@HARITHA>
From: "Vijayanand C - CTD, Chennai." <vijayc@ctd.hcltech.com>
To: "Ramia, Kannan Babu" <kannan.babu.ramia@intel.com>
Cc: mpls@UU.NET
Subject: RE: Clarification on Handling a specific event in LDP
Date: Wed, 18 Sep 2002 11:38:36 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C25ED9.D3785CB0"
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_01C25ED9.D3785CB0
Content-Type: text/plain;
	charset="iso-8859-1"

Kannan,
This is a special case. 
 
 
I have a solution for this problem.
Basically if any LSR receives an Label withdraw message from its valid Next
hop neighbor then before propagating to its upstream peers it need to check
the value of the label being withdrawn, if the label happens to be an NULL
label then it should not propagate the label withdraw to its upstream peers.
Now this LSR should now assume itself as an egress for that LSP.
[Vijayanand C - CTD, Chennai.]  What will happen in valid cases when the
eggress actually wants to withdraw label and when u no longer want to switch
for that FEC ?The pennultimate hop should not hold the label in that case.
How will the Phop know for which case the withdraw applies ?   
 
 
 
Second one could be there should be a provision to change the label for the
particular FEC. I.e any point of time the valid next hop LSR can advertise a
change of label for that FEC. Here problems are we need to maintain the
context of that advertisement (LM).
[Vijayanand C - CTD, Chennai.]  This becomes unsolicited advertisement.
 
 
 
A better way would be for the egress to withdraw the label. However the
ingress will not issue a request unless it is in Independent control. This
anyway is a problem. My suggestin would be - The ingress after sending a
release can issue a fresh request for the label even if its not in
independent control if it still supports label switching on the FEC. I feel
This would be more cleaner .
 
 
Vijay 
 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR>
<META content=3D"Microsoft Word 9" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C25F00.0A4CA8B0" rel=3DFile-List><!--[if gte =
mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in =
1.25in; mso-header-margin: .5in; mso-footer-margin: .5in; =
mso-paper-source: 0; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
P.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
LI.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
DIV.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
SPAN.EmailStyle15 {
	COLOR: black; mso-style-type: personal-compose; mso-ansi-font-size: =
10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
DIV.Section1 {
	page: Section1
}
OL {
	MARGIN-BOTTOM: 0in
}
UL {
	MARGIN-BOTTOM: 0in
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in">
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D169422705-18092002>Kannan,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D169422705-18092002>This=20
is a special case. </SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]><SPAN=20
  class=3DEmailStyle15><FONT face=3DArial color=3Dblack size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></DI=
V>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT face=3DArial =
color=3Dblack=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT face=3DArial =
color=3Dblack=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">I have=20
  a solution for this problem.<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Basically=20
  if any LSR receives an Label withdraw message from its valid Next hop =
neighbor=20
  then before propagating to its upstream peers it need to check the =
value of=20
  the label being withdrawn, if the label happens to be an NULL label =
then it=20
  should not propagate the label withdraw to its upstream peers. Now =
this LSR=20
  should now assume itself as an egress for that LSP.<BR><SPAN=20
  class=3D169422705-18092002><FONT color=3D#0000ff>[Vijayanand C - CTD, =

  Chennai.]&nbsp; What will happen in valid cases when the eggress =
actually=20
  wants to withdraw label&nbsp;and when u no longer want to switch for =
that FEC=20
  ?The pennultimate hop should&nbsp;not hold&nbsp;the label in that =
case.=20
  How&nbsp;will the Phop know&nbsp;for which case the withdraw applies=20
  ?</FONT></SPAN><FONT color=3D#0000ff><SPAN=20
  class=3D169422705-18092002>&nbsp;</SPAN><SPAN=20
  class=3D169422705-18092002>&nbsp;</SPAN><SPAN=20
  =
class=3D169422705-18092002>&nbsp;</SPAN></FONT></SPAN></FONT></SPAN></P>=
<![if !supportEmptyParas]><![endif]>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT face=3DArial =
color=3Dblack=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"></SPAN></FONT></SPAN>&nbsp;</P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT face=3DArial =
color=3Dblack=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"></SPAN></FONT></SPAN>&nbsp;</P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT face=3DArial =
color=3Dblack=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Second=20
  one could be there should be a provision to change the label for the=20
  particular FEC. I.e any point of time the valid next hop LSR can =
advertise a=20
  change of label for that FEC. Here problems are we need to maintain =
the=20
  context of that advertisement (LM).<BR><FONT color=3D#0000ff><SPAN=20
  class=3D169422705-18092002>[Vijayanand C - CTD, =
Chennai.]&nbsp;&nbsp;This=20
  becomes unsolicited =
advertisement.</SPAN></FONT></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><FONT=20
  color=3D#0000ff><SPAN=20
  =
class=3D169422705-18092002></SPAN></FONT></SPAN></FONT></SPAN>&nbsp;</P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><FONT=20
  color=3D#0000ff><SPAN=20
  =
class=3D169422705-18092002></SPAN></FONT></SPAN></FONT></SPAN>&nbsp;</P>=

  <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><FONT=20
  color=3D#0000ff><SPAN=20
  =
class=3D169422705-18092002></SPAN></FONT></SPAN></FONT></SPAN>&nbsp;</P>=
<![if !supportEmptyParas]><![endif]>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  class=3D169422705-18092002><FONT color=3D#0000ff>A better way would =
be for the=20
  egress to withdraw the label. However&nbsp;the ingress will not issue =
a=20
  request unless it is in Independent control. This anyway&nbsp;is=20
  a&nbsp;problem. My suggestin would be - The ingress after sending a =
release=20
  can issue a fresh request&nbsp;for the label even if its not in =
independent=20
  control if it still supports label switching on the FEC. I feel=20
  This&nbsp;would be more cleaner =
.</FONT></SPAN></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  class=3D169422705-18092002></SPAN></SPAN></FONT></SPAN>&nbsp;</P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  class=3D169422705-18092002></SPAN></SPAN></FONT></SPAN>&nbsp;</P>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
  class=3D169422705-18092002></SPAN><SPAN =
class=3D169422705-18092002><FONT=20
  color=3D#0000ff>Vijay</FONT></SPAN>&nbsp;<o:p></o:p></SPAN><!--[if =
supportFields]><font color=3Dblack><span=20
style=3D'color:black'><span =
style=3D'mso-element:field-begin'></span><span=20
style=3D"mso-spacerun: yes">&nbsp;</span>AUTOTEXTLIST \s &quot;E-mail=20
Signature&quot; <span =
style=3D'mso-element:field-separator'></span></span></font><![endif]--><=
/FONT></SPAN></P>
  <P class=3DMsoNormal><!--[if supportFields]><font color=3Dblack><span =

style=3D'color:black'><span =
style=3D'mso-element:field-end'></span></span></font><![endif]--><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black"><![if =
!supportEmptyParas]><![endif]>&nbsp;</SPAN></FONT><FONT=20
  color=3Dblack><SPAN=20
  style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTM=
L>

------_=_NextPart_001_01C25ED9.D3785CB0--



From owner-mpls@UU.NET  Wed Sep 18 02:25:51 2002
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 ESMTP id CAA01903
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 02:25:51 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngur22478
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 06:27:34 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngur21927;
	Wed, 18 Sep 2002 06:27:17 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngur11222
	for mpls-outgoing; Wed, 18 Sep 2002 06:27:06 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQngur11217
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 06:27:01 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 QQngur24653
	for <mpls@uu.net>; Wed, 18 Sep 2002 06:26:41 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngur07094
	for <mpls@uu.net>; Wed, 18 Sep 2002 06:26:40 GMT
Received: from petasus.ch.intel.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: petasus.ch.intel.com [143.182.124.5])
	id QQngur07084
	for <mpls@uu.net>; Wed, 18 Sep 2002 06:26:40 GMT
Received: from fmsmsxvs043.fm.intel.com (fmsmsxvs043.fm.intel.com [132.233.42.129])
	by petasus.ch.intel.com (8.11.6/8.11.6/d: solo.mc,v 1.43 2002/08/30 20:06:11 dmccart Exp $) with SMTP id g8I6SQo28586
	for <mpls@uu.net>; Wed, 18 Sep 2002 06:28:26 GMT
Received: from fmsmsx28.fm.intel.com ([132.233.42.28])
 by fmsmsxvs043.fm.intel.com (NAVGW 2.5.2.11) with SMTP id M2002091723250314061
 ; Tue, 17 Sep 2002 23:25:03 -0700
Received: by fmsmsx28.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <S62N3JFH>; Tue, 17 Sep 2002 23:26:37 -0700
Message-ID: <12B638FEE763F74696D8544752E7204812EA1B@bgsmsx101.iind.intel.com>
From: "Ramia, Kannan Babu" <kannan.babu.ramia@intel.com>
To: "'Vijayanand C - CTD, Chennai.'" <vijayc@ctd.hcltech.com>,
        "Ramia, Kannan Babu" <kannan.babu.ramia@intel.com>
Cc: mpls@UU.NET
Subject: RE: Clarification on Handling a specific event in LDP
Date: Tue, 17 Sep 2002 23:18:18 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C25EDB.2E0196A0"
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_01C25EDB.2E0196A0
Content-Type: text/plain;
	charset="iso-8859-1"

hi vijay..
   
thanks for ur reply ..but i still have some thing to get clarified ...
please see in line Comments
 
bye
kb
-----Original Message-----
From: Vijayanand C - CTD, Chennai. [mailto:vijayc@ctd.hcltech.com]
Sent: Wednesday, September 18, 2002 11:39 AM
To: Ramia, Kannan Babu
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP


Kannan,
This is a special case. 
 
 
I have a solution for this problem.
Basically if any LSR receives an Label withdraw message from its valid Next
hop neighbor then before propagating to its upstream peers it need to check
the value of the label being withdrawn, if the label happens to be an NULL
label then it should not propagate the label withdraw to its upstream peers.
Now this LSR should now assume itself as an egress for that LSP.
[Vijayanand C - CTD, Chennai.]  What will happen in valid cases when the
eggress actually wants to withdraw label and when u no longer want to switch
for that FEC ?The pennultimate hop should not hold the label in that case.
How will the Phop know for which case the withdraw applies ?   

[Ramia, Kannan Babu]  Actually here we are not holding the egress label, we
are sending a label release for the corresponding withdraw message and also
i am expecting only the INGRESS will start the LSP deletion process for any
genuine case (of course assumption is all LSR is configured with the
forwarding of the label release)
 
 
 
Second one could be there should be a provision to change the label for the
particular FEC. I.e any point of time the valid next hop LSR can advertise a
change of label for that FEC. Here problems are we need to maintain the
context of that advertisement (LM).
[Vijayanand C - CTD, Chennai.]  This becomes unsolicited advertisement.

[Ramia, Kannan Babu] i dont see any problem in this kind of advertisement,
even if u are configured with DOD ordered mode if any change in hop count or
PV, the downstream LSR will anyway generate a LM with out any outstanding
LR. So i want to treat the change in label also the same way as that of
change in hop count.
 
 
 
A better way would be for the egress to withdraw the label. However the
ingress will not issue a request unless it is in Independent control. This
anyway is a problem. My suggestin would be - The ingress after sending a
release can issue a fresh request for the label even if its not in
independent control if it still supports label switching on the FEC. I feel
This would be more cleaner .

[Ramia, Kannan Babu]  How the ingress will know that it need to request
again or initate LSP establishment once again for the same FEC (i mean here
what criteria or conditions it checks before it does this again..) because
in some genuine cases if egress wants to remove the LSP then it may lead to
infinite looping.
 
 
 
 
 
Vijay 
 

------_=_NextPart_001_01C25EDB.2E0196A0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 6.00.2716.2200" name=3DGENERATOR>
<META content=3D"Microsoft Word 9" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C25F00.0A4CA8B0" rel=3DFile-List><!--[if gte =
mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in =
1.25in; mso-header-margin: .5in; mso-footer-margin: .5in; =
mso-paper-source: 0; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
P.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
LI.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
DIV.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
SPAN.EmailStyle15 {
	COLOR: black; mso-style-type: personal-compose; mso-ansi-font-size: =
10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
DIV.Section1 {
	page: Section1
}
OL {
	MARGIN-BOTTOM: 0in
}
UL {
	MARGIN-BOTTOM: 0in
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in">
<DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff size=3D2>hi=20
vijay..</FONT></SPAN></DIV>
<DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>&nbsp;&nbsp; </FONT></SPAN></DIV>
<DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff size=3D2>thanks=20
for ur reply ..but i still have some thing to get clarified ... please=20
s</FONT></SPAN><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>ee in line Comments</FONT></SPAN></DIV>
<DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>bye</FONT></SPAN></DIV>
<DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>kb</FONT></SPAN></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> Vijayanand C - =
CTD, Chennai.=20
  [mailto:vijayc@ctd.hcltech.com]<BR><B>Sent:</B> Wednesday, September =
18, 2002=20
  11:39 AM<BR><B>To:</B> Ramia, Kannan Babu<BR><B>Cc:</B>=20
  mpls@uu.net<BR><B>Subject:</B> RE: Clarification on Handling a =
specific event=20
  in LDP<BR><BR></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D169422705-18092002>Kannan,</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D169422705-18092002>This=20
  is a special case. </SPAN></FONT></DIV>
  <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]><SPAN=20
    class=3DEmailStyle15><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></DI=
V>
    <DIV class=3DSection1>
    <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT face=3DArial =
color=3Dblack=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

    <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT face=3DArial =
color=3Dblack=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">I=20
    have a solution for this =
problem.<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Basically=20
    if any LSR receives an Label withdraw message from its valid Next =
hop=20
    neighbor then before propagating to its upstream peers it need to =
check the=20
    value of the label being withdrawn, if the label happens to be an =
NULL label=20
    then it should not propagate the label withdraw to its upstream =
peers. Now=20
    this LSR should now assume itself as an egress for that =
LSP.<BR><FONT=20
    color=3D#0000ff><SPAN class=3D169422705-18092002>[Vijayanand C - =
CTD,=20
    Chennai.]&nbsp; What will happen in valid cases when the eggress =
actually=20
    wants to withdraw label&nbsp;and when u no longer want to switch =
for that=20
    FEC ?The pennultimate hop should&nbsp;not hold&nbsp;the label in =
that case.=20
    How&nbsp;will the Phop know&nbsp;for which case the withdraw =
applies=20
    ?</SPAN><SPAN class=3D169422705-18092002>&nbsp;</SPAN><SPAN=20
    class=3D169422705-18092002>&nbsp;</SPAN></FONT><SPAN=20
    class=3D169422705-18092002><FONT color=3D#0000ff>&nbsp;<BR><SPAN=20
    =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></FONT></SPAN></P=
>
    <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
    class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
    class=3D400110906-18092002>[Ramia, Kannan Babu]&nbsp; Actually =
here&nbsp;we=20
    are not holding the egress label, we are sending a =
label&nbsp;release for=20
    the corresponding&nbsp;withdraw message and&nbsp;also&nbsp;i am =
expecting=20
    only the INGRESS will start the LSP deletion process for any =
genuine case=20
    (of course assumption is all LSR is configured with the forwarding =
of the=20
    label release)</SPAN></FONT></SPAN></SPAN></FONT></SPAN><![if =
!supportEmptyParas]><![endif]></P>
    <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT face=3DArial =
color=3Dblack=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"></SPAN></FONT></SPAN>&nbsp;</P>
    <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT face=3DArial =
color=3Dblack=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"></SPAN></FONT></SPAN>&nbsp;</P>
    <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT face=3DArial =
color=3Dblack=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Second=20
    one could be there should be a provision to change the label for =
the=20
    particular FEC. I.e any point of time the valid next hop LSR can =
advertise a=20
    change of label for that FEC. Here problems are we need to maintain =
the=20
    context of that advertisement (LM).<BR><SPAN =
class=3D169422705-18092002><FONT=20
    color=3D#0000ff>[Vijayanand C - CTD, Chennai.]&nbsp;&nbsp;This =
becomes=20
    unsolicited advertisement.<BR><SPAN=20
    =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></FONT></SPAN></P=
>
    <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
    class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
    class=3D400110906-18092002>[Ramia, Kannan Babu] i dont see any =
problem in this=20
    kind of advertisement, even if u are configured with DOD ordered =
mode if=20
    any&nbsp;change in hop count or&nbsp;PV, the downstream =
LSR&nbsp;will anyway=20
    generate a LM with out any outstanding LR.&nbsp;So i want to treat =
the=20
    change in label also the same way as that of change in hop=20
    count.</SPAN></FONT></SPAN></SPAN></FONT></SPAN></P>
    <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><FONT=20
    color=3D#0000ff><SPAN=20
    =
class=3D169422705-18092002></SPAN></FONT></SPAN></FONT></SPAN>&nbsp;</P>=

    <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><FONT=20
    color=3D#0000ff><SPAN=20
    =
class=3D169422705-18092002></SPAN></FONT></SPAN></FONT></SPAN>&nbsp;</P>=

    <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><FONT=20
    color=3D#0000ff><SPAN=20
    =
class=3D169422705-18092002></SPAN></FONT></SPAN></FONT></SPAN>&nbsp;</P>=
<![if !supportEmptyParas]><![endif]>
    <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
    class=3D169422705-18092002><FONT color=3D#0000ff>A better way would =
be for the=20
    egress to withdraw the label. However&nbsp;the ingress will not =
issue a=20
    request unless it is in Independent control. This anyway&nbsp;is=20
    a&nbsp;problem. My suggestin would be - The ingress after sending a =
release=20
    can issue a fresh request&nbsp;for the label even if its not in =
independent=20
    control if it still supports label switching on the FEC. I feel=20
    This&nbsp;would be more cleaner .<BR><SPAN=20
    class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></SPAN></P>
    <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
    class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
    class=3D400110906-18092002>[Ramia, Kannan Babu]&nbsp;&nbsp;How the =
ingress=20
    will know that it need to request again or initate LSP =
establishment once=20
    again for the same FEC (i mean here what criteria or conditions it =
checks=20
    before it does this again..) because in some genuine cases if =
egress wants=20
    to remove the LSP&nbsp;then it may lead to infinite=20
    looping.</SPAN></FONT></SPAN></SPAN></SPAN></P>
    <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
    class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
    =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></SPAN>&nbsp;</P>=

    <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
    class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
    =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></SPAN>&nbsp;</P>=

    <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
    class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
    =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></SPAN>&nbsp;</P>=

    <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: 12=
.0pt"><SPAN=20
    class=3D169422705-18092002></SPAN></SPAN></FONT></SPAN>&nbsp;</P>
    <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
    class=3D169422705-18092002></SPAN></SPAN></FONT></SPAN>&nbsp;</P>
    <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
    class=3D169422705-18092002></SPAN><SPAN =
class=3D169422705-18092002><FONT=20
    color=3D#0000ff>Vijay</FONT></SPAN>&nbsp;<o:p></o:p></SPAN><!--[if =
supportFields]><font color=3Dblack><span=20
style=3D'color:black'><span =
style=3D'mso-element:field-begin'></span><span=20
style=3D"mso-spacerun: yes">&nbsp;</span>AUTOTEXTLIST \s &quot;E-mail=20
Signature&quot; <span =
style=3D'mso-element:field-separator'></span></span></font><![endif]--><=
/FONT></SPAN></P>
    <P class=3DMsoNormal><!--[if supportFields]><font =
color=3Dblack><span=20
style=3D'color:black'><span =
style=3D'mso-element:field-end'></span></span></font><![endif]--><FONT=20
    color=3Dblack><SPAN=20
    style=3D"COLOR: black"><![if =
!supportEmptyParas]><![endif]>&nbsp;</SPAN></FONT><FONT=20
    color=3Dblack><SPAN=20
    style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BLOCKQUOTE=
></BODY></HTML>

------_=_NextPart_001_01C25EDB.2E0196A0--


From owner-mpls@UU.NET  Wed Sep 18 02:43:23 2002
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 ESMTP id CAA04279
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 02:43:22 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngut12626
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 06:45:04 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngus12340;
	Wed, 18 Sep 2002 06:44:53 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngus12180
	for mpls-outgoing; Wed, 18 Sep 2002 06:44:36 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQngus12175
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 06:44:28 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 QQngus11609
	for <mpls@uu.net>; Wed, 18 Sep 2002 06:44:04 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngus11636
	for <mpls@uu.net>; Wed, 18 Sep 2002 06:44:03 GMT
Received: from funnel.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQngus11628
	for <mpls@uu.net>; Wed, 18 Sep 2002 06:44:03 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id CAA25811 for <mpls@uu.net>; Wed, 18 Sep 2002 02:44:03 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8I6i2r20130 for mpls@uu.net; Wed, 18 Sep 2002 02:44:02 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQngus12104
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 06:43: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 QQngus09059
	for <mpls@uu.net>; Wed, 18 Sep 2002 06:43:12 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngus10894
	for <mpls@uu.net>; Wed, 18 Sep 2002 06:43:12 GMT
Received: from ganesh.ctd.hctech.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.64.2])
	id QQngus10884
	for <mpls@uu.net>; Wed, 18 Sep 2002 06:43:10 GMT
Received: by GANESH with Internet Mail Service (5.5.2653.19)
	id <TA10BLY3>; Wed, 18 Sep 2002 12:16:48 +0530
Message-ID: <55E277B99171E041ABF5F4B1C6DDCA0688574B@HARITHA>
From: "Vijayanand C - CTD, Chennai." <vijayc@ctd.hcltech.com>
To: "Ramia, Kannan Babu" <kannan.babu.ramia@intel.com>
Cc: mpls@UU.NET
Subject: RE: Clarification on Handling a specific event in LDP
Date: Wed, 18 Sep 2002 12:15:18 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C25EDE.F3E3D2E0"
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_01C25EDE.F3E3D2E0
Content-Type: text/plain;
	charset="iso-8859-1"

See my comments inline
-----Original Message-----
From: Ramia, Kannan Babu [mailto:kannan.babu.ramia@intel.com]
Sent: Wednesday, September 18, 2002 11:48 AM
To: 'Vijayanand C - CTD, Chennai.'; Ramia, Kannan Babu
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP


hi vijay..
   
thanks for ur reply ..but i still have some thing to get clarified ...
please see in line Comments
 
bye
kb
-----Original Message-----
From: Vijayanand C - CTD, Chennai. [mailto:vijayc@ctd.hcltech.com]
Sent: Wednesday, September 18, 2002 11:39 AM
To: Ramia, Kannan Babu
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP


Kannan,
This is a special case. 
 
 
I have a solution for this problem.
Basically if any LSR receives an Label withdraw message from its valid Next
hop neighbor then before propagating to its upstream peers it need to check
the value of the label being withdrawn, if the label happens to be an NULL
label then it should not propagate the label withdraw to its upstream peers.
Now this LSR should now assume itself as an egress for that LSP.
[Vijayanand C - CTD, Chennai.]  What will happen in valid cases when the
eggress actually wants to withdraw label and when u no longer want to switch
for that FEC ?The pennultimate hop should not hold the label in that case.
How will the Phop know for which case the withdraw applies ?   

[Ramia, Kannan Babu]  Actually here we are not holding the egress label, we
are sending a label release for the corresponding withdraw message and also
i am expecting only the INGRESS will start the LSP deletion process for any
genuine case (of course assumption is all LSR is configured with the
forwarding of the label release)
[Vijayanand C - CTD, Chennai.] By holding the label I mean, the PHop would
be holding its upstream labels unnecessarily even in genuine LSP tear down
scenarios( when withdraw is received from its downstream node which is
egress) 
 Here ingress is not initiating deletion the egress does it by sending
withdraw. 
 
 
 
 
Second one could be there should be a provision to change the label for the
particular FEC. I.e any point of time the valid next hop LSR can advertise a
change of label for that FEC. Here problems are we need to maintain the
context of that advertisement (LM).
[Vijayanand C - CTD, Chennai.]  This becomes unsolicited advertisement.

[Ramia, Kannan Babu] i dont see any problem in this kind of advertisement,
even if u are configured with DOD ordered mode if any change in hop count or
PV, the downstream LSR will anyway generate a LM with out any outstanding
LR. So i want to treat the change in label also the same way as that of
change in hop count.
[Vijayanand C - CTD, Chennai.] Changing the attributes of the label mapping
( like PV) is different from changing the label itself. Again the context
maintenance (old label, FEC) for this is a problem as you said. Even the
question of communicating changed attributes seldom arises in DOd Ord
control. In cases where it happens, such as Next hop change, it was debated
at length earlier in this list if it was proper to unsolicitedly advertise
the changed attributes.
 
 
A better way would be for the egress to withdraw the label. However the
ingress will not issue a request unless it is in Independent control. This
anyway is a problem. My suggestin would be - The ingress after sending a
release can issue a fresh request for the label even if its not in
independent control if it still supports label switching on the FEC. I feel
This would be more cleaner .

[Ramia, Kannan Babu]  How the ingress will know that it need to request
again or initate LSP establishment once again for the same FEC (i mean here
what criteria or conditions it checks before it does this again..) because
in some genuine cases if egress wants to remove the LSP then it may lead to
infinite looping.
[Vijayanand C - CTD, Chennai.] This kind of situation( retrying) will anyway
apply in Independent control( all nodes along the LSP may potentially
retry). So how will you solve the problem in that case ?  What I am
suggesting is if ordered control is used the retry can be done only by the
ingress. Any retry mechanism would have some back off and stopping criteria
associated with it implicitly.
 
 
 
 
 
Vijay 
 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR>
<META content=3D"Microsoft Word 9" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C25F00.0A4CA8B0" rel=3DFile-List><!--[if gte =
mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in =
1.25in; mso-header-margin: .5in; mso-footer-margin: .5in; =
mso-paper-source: 0; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
P.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
LI.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
DIV.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
SPAN.EmailStyle15 {
	COLOR: black; mso-style-type: personal-compose; mso-ansi-font-size: =
10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
DIV.Section1 {
	page: Section1
}
OL {
	MARGIN-BOTTOM: 0in
}
UL {
	MARGIN-BOTTOM: 0in
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in">
<DIV><SPAN class=3D821362606-18092002><FONT face=3DArial =
color=3D#0000ff size=3D2>See my=20
comments inline</FONT></SPAN></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> Ramia, Kannan =
Babu=20
  [mailto:kannan.babu.ramia@intel.com]<BR><B>Sent:</B> Wednesday, =
September 18,=20
  2002 11:48 AM<BR><B>To:</B> 'Vijayanand C - CTD, Chennai.'; Ramia, =
Kannan=20
  Babu<BR><B>Cc:</B> mpls@uu.net<BR><B>Subject:</B> RE: Clarification =
on=20
  Handling a specific event in LDP<BR><BR></FONT></DIV>
  <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff size=3D2>hi=20
  vijay..</FONT></SPAN></DIV>
  <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>&nbsp;&nbsp; </FONT></SPAN></DIV>
  <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>thanks for ur reply ..but i still have some thing to get =
clarified ...=20
  please s</FONT></SPAN><SPAN class=3D400110906-18092002><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>ee in line Comments</FONT></SPAN></DIV>
  <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>bye</FONT></SPAN></DIV>
  <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>kb</FONT></SPAN></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> Vijayanand C - =
CTD,=20
    Chennai. [mailto:vijayc@ctd.hcltech.com]<BR><B>Sent:</B> Wednesday, =

    September 18, 2002 11:39 AM<BR><B>To:</B> Ramia, Kannan =
Babu<BR><B>Cc:</B>=20
    mpls@uu.net<BR><B>Subject:</B> RE: Clarification on Handling a =
specific=20
    event in LDP<BR><BR></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D169422705-18092002>Kannan,</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D169422705-18092002>This is a special case. =
</SPAN></FONT></DIV>
    <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
      <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]><SPAN=20
      class=3DEmailStyle15><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></DI=
V>
      <DIV class=3DSection1>
      <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial color=3Dblack=20
      size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

      <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial color=3Dblack=20
      size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">I=20
      have a solution for this =
problem.<o:p></o:p></SPAN></FONT></SPAN></P>
      <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Basically=20
      if any LSR receives an Label withdraw message from its valid Next =
hop=20
      neighbor then before propagating to its upstream peers it need to =
check=20
      the value of the label being withdrawn, if the label happens to =
be an NULL=20
      label then it should not propagate the label withdraw to its =
upstream=20
      peers. Now this LSR should now assume itself as an egress for =
that=20
      LSP.<BR><FONT color=3D#0000ff><SPAN =
class=3D169422705-18092002>[Vijayanand C -=20
      CTD, Chennai.]&nbsp; What will happen in valid cases when the =
eggress=20
      actually wants to withdraw label&nbsp;and when u no longer want =
to switch=20
      for that FEC ?The pennultimate hop should&nbsp;not hold&nbsp;the =
label in=20
      that case. How&nbsp;will the Phop know&nbsp;for which case the =
withdraw=20
      applies ?</SPAN><SPAN =
class=3D169422705-18092002>&nbsp;</SPAN><SPAN=20
      class=3D169422705-18092002>&nbsp;</SPAN></FONT><SPAN=20
      class=3D169422705-18092002><FONT color=3D#0000ff>&nbsp;<BR><SPAN=20
      =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></FONT></SPAN></P=
>
      <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
      class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
      class=3D400110906-18092002>[Ramia, Kannan Babu]&nbsp; Actually =
here&nbsp;we=20
      are not holding the egress label, we are sending a =
label&nbsp;release for=20
      the corresponding&nbsp;withdraw message and&nbsp;also&nbsp;i am =
expecting=20
      only the INGRESS will start the LSP deletion process for any =
genuine case=20
      (of course assumption is all LSR is configured with the =
forwarding of the=20
      label release)<BR><SPAN class=3D821362606-18092002><FONT=20
      color=3D#0000ff>[Vijayanand C - CTD, Chennai.]&nbsp;By holding =
the label I=20
      mean, the PHop would be holding its upstream labels=20
      unnecessarily&nbsp;even in genuine LSP&nbsp;tear down scenarios( =
when=20
      withdraw is received from its downstream node which is egress)=20
      </FONT></SPAN></SPAN></FONT></SPAN></SPAN></SPAN></P>
      <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
      class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
      class=3D400110906-18092002><SPAN class=3D821362606-18092002><FONT =

      color=3D#0000ff>&nbsp;Here ingress is not initiating deletion the =
egress=20
      does it by sending=20
      withdraw.&nbsp;</FONT></SPAN></SPAN></FONT></SPAN></SPAN><![if =
!supportEmptyParas]><![endif]></SPAN></P>
      <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial color=3Dblack=20
      size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"></SPAN></FONT></SPAN>&nbsp;</P>
      <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial color=3Dblack=20
      size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"></SPAN></FONT></SPAN>&nbsp;</P>
      <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial color=3Dblack=20
      size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"></SPAN></FONT></SPAN>&nbsp;</P>
      <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial color=3Dblack=20
      size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
      <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">Second=20
      one could be there should be a provision to change the label for =
the=20
      particular FEC. I.e any point of time the valid next hop LSR can =
advertise=20
      a change of label for that FEC. Here problems are we need to =
maintain the=20
      context of that advertisement (LM).<BR><SPAN=20
      class=3D169422705-18092002><FONT color=3D#0000ff>[Vijayanand C - =
CTD,=20
      Chennai.]&nbsp;&nbsp;This becomes unsolicited =
advertisement.<BR><SPAN=20
      =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></FONT></SPAN></P=
>
      <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
      class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
      class=3D400110906-18092002>[Ramia, Kannan Babu] i dont see any =
problem in=20
      this kind of advertisement, even if u are configured with DOD =
ordered mode=20
      if any&nbsp;change in hop count or&nbsp;PV, the downstream =
LSR&nbsp;will=20
      anyway generate a LM with out any outstanding LR.&nbsp;So i want =
to treat=20
      the change in label also the same way as that of change in hop=20
      count.<BR><SPAN class=3D821362606-18092002><FONT =
color=3D#0000ff>[Vijayanand C=20
      - CTD, Chennai.]&nbsp;Changing the&nbsp;attributes of the label =
mapping=20
      (&nbsp;like PV)&nbsp;is different from changing the label itself. =
Again=20
      the context maintenance (old label, FEC) for this is a problem as =
you=20
      said. Even the question of communicating changed attributes =
seldom arises=20
      in DOd Ord control. In cases where it happens, such as Next hop =
change, it=20
      was debated at length earlier in this list if it was proper to=20
      unsolicitedly advertise the changed=20
      attributes.</FONT></SPAN></SPAN></FONT></SPAN></SPAN></SPAN></P>
      <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><FONT=20
      color=3D#0000ff><SPAN=20
      =
class=3D169422705-18092002></SPAN></FONT></SPAN></FONT></SPAN>&nbsp;</P>=

      <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><FONT=20
      color=3D#0000ff><SPAN=20
      =
class=3D169422705-18092002></SPAN></FONT></SPAN></FONT></SPAN>&nbsp;</P>=
<![if !supportEmptyParas]><![endif]>
      <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
      class=3D169422705-18092002><FONT color=3D#0000ff>A better way =
would be for the=20
      egress to withdraw the label. However&nbsp;the ingress will not =
issue a=20
      request unless it is in Independent control. This anyway&nbsp;is=20
      a&nbsp;problem. My suggestin would be - The ingress after sending =
a=20
      release can issue a fresh request&nbsp;for the label even if its =
not in=20
      independent control if it still supports label switching on the =
FEC. I=20
      feel This&nbsp;would be more cleaner .<BR><SPAN=20
      =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></SPAN></P>
      <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
      class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
      class=3D400110906-18092002>[Ramia, Kannan Babu]&nbsp;&nbsp;How =
the ingress=20
      will know that it need to request again or initate LSP =
establishment once=20
      again for the same FEC (i mean here what criteria or conditions =
it checks=20
      before it does this again..) because in some genuine cases if =
egress wants=20
      to remove the LSP&nbsp;then it may lead to infinite =
looping.<BR><SPAN=20
      class=3D821362606-18092002><FONT color=3D#0000ff>[Vijayanand C - =
CTD,=20
      Chennai.]&nbsp;This kind of situation(&nbsp;retrying)&nbsp;will =
anyway=20
      apply in Independent control( all nodes along the LSP may =
potentially=20
      retry). So&nbsp;how will you solve the problem in that case ? =
&nbsp;What I=20
      am suggesting is if ordered control is used the retry can be done =
only by=20
      the ingress. Any retry mechanism would have some back off and =
stopping=20
      criteria associated with it=20
      implicitly.</FONT></SPAN></SPAN></FONT></SPAN></SPAN></SPAN></P>
      <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
      class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
      =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></SPAN>&nbsp;</P>=

      <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
      class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
      =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></SPAN>&nbsp;</P>=

      <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
      class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
      =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></SPAN>&nbsp;</P>=

      <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
      class=3D169422705-18092002></SPAN></SPAN></FONT></SPAN>&nbsp;</P>
      <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
      class=3D169422705-18092002></SPAN></SPAN></FONT></SPAN>&nbsp;</P>
      <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt"><SPAN=20
      class=3D169422705-18092002></SPAN><SPAN =
class=3D169422705-18092002><FONT=20
      =
color=3D#0000ff>Vijay</FONT></SPAN>&nbsp;<o:p></o:p></SPAN><!--[if =
supportFields]><font color=3Dblack><span=20
style=3D'color:black'><span =
style=3D'mso-element:field-begin'></span><span=20
style=3D"mso-spacerun: yes">&nbsp;</span>AUTOTEXTLIST \s &quot;E-mail=20
Signature&quot; <span =
style=3D'mso-element:field-separator'></span></span></font><![endif]--><=
/FONT></SPAN></P>
      <P class=3DMsoNormal><!--[if supportFields]><font =
color=3Dblack><span=20
style=3D'color:black'><span =
style=3D'mso-element:field-end'></span></span></font><![endif]--><FONT=20
      color=3Dblack><SPAN style=3D"COLOR: black"><![if =
!supportEmptyParas]><![endif]>&nbsp;</SPAN></FONT><FONT=20
      color=3Dblack><SPAN=20
      style=3D"COLOR: black; mso-color-alt: windowtext"><o:p></o:p></SPA=
N></FONT></P></DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>=


------_=_NextPart_001_01C25EDE.F3E3D2E0--



From owner-mpls@UU.NET  Wed Sep 18 04:54:22 2002
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 ESMTP id EAA06177
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 04:54:22 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngvb02784
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 08:56:03 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngvb02002;
	Wed, 18 Sep 2002 08:55:34 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngvb24634
	for mpls-outgoing; Wed, 18 Sep 2002 08:55:16 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQngvb24629
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 08:55:09 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 QQngvb14971
	for <mpls@uu.net>; Wed, 18 Sep 2002 08:54:50 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngvb12335
	for <mpls@uu.net>; Wed, 18 Sep 2002 08:54:49 GMT
Received: from hermes.jf.intel.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: fmr05.intel.com [134.134.136.6])
	id QQngvb12322
	for <mpls@uu.net>; Wed, 18 Sep 2002 08:54:49 GMT
Received: from petasus.jf.intel.com (petasus.jf.intel.com [10.7.209.6])
	by hermes.jf.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.50 2002/08/30 20:04:57 dmccart Exp $) with ESMTP id g8I8qro04259
	for <mpls@uu.net>; Wed, 18 Sep 2002 08:52:53 GMT
Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206])
	by petasus.jf.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.24 2002/08/30 20:04:21 dmccart Exp $) with SMTP id g8I8q6F09106
	for <mpls@uu.net>; Wed, 18 Sep 2002 08:52:06 GMT
Received: from orsmsx26.jf.intel.com ([192.168.65.26])
 by orsmsxvs040.jf.intel.com (NAVGW 2.5.2.11) with SMTP id M2002091801570922193
 ; Wed, 18 Sep 2002 01:57:09 -0700
Received: by orsmsx26.jf.intel.com with Internet Mail Service (5.5.2653.19)
	id <TB3R6LQM>; Wed, 18 Sep 2002 01:54:42 -0700
Message-ID: <12B638FEE763F74696D8544752E7204812EA1D@bgsmsx101.iind.intel.com>
From: "Ramia, Kannan Babu" <kannan.babu.ramia@intel.com>
To: "'Vijayanand C - CTD, Chennai.'" <vijayc@ctd.hcltech.com>
Cc: mpls@UU.NET
Subject: RE: Clarification on Handling a specific event in LDP
Date: Wed, 18 Sep 2002 01:50:03 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C25EF0.60EF4250"
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_01C25EF0.60EF4250
Content-Type: text/plain;
	charset="iso-8859-1"

See my inline Comments
-----Original Message-----
From: Vijayanand C - CTD, Chennai. [mailto:vijayc@ctd.hcltech.com]
Sent: Wednesday, September 18, 2002 12:15 PM
To: Ramia, Kannan Babu
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP


See my comments inline
-----Original Message-----
From: Ramia, Kannan Babu [mailto:kannan.babu.ramia@intel.com]
Sent: Wednesday, September 18, 2002 11:48 AM
To: 'Vijayanand C - CTD, Chennai.'; Ramia, Kannan Babu
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP


hi vijay..
   
thanks for ur reply ..but i still have some thing to get clarified ...
please see in line Comments
 
bye
kb
-----Original Message-----
From: Vijayanand C - CTD, Chennai. [mailto:vijayc@ctd.hcltech.com]
Sent: Wednesday, September 18, 2002 11:39 AM
To: Ramia, Kannan Babu
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP


Kannan,
This is a special case. 
 
 
I have a solution for this problem.
Basically if any LSR receives an Label withdraw message from its valid Next
hop neighbor then before propagating to its upstream peers it need to check
the value of the label being withdrawn, if the label happens to be an NULL
label then it should not propagate the label withdraw to its upstream peers.
Now this LSR should now assume itself as an egress for that LSP.
[Vijayanand C - CTD, Chennai.]  What will happen in valid cases when the
eggress actually wants to withdraw label and when u no longer want to switch
for that FEC ?The pennultimate hop should not hold the label in that case.
How will the Phop know for which case the withdraw applies ?   

[Ramia, Kannan Babu]  Actually here we are not holding the egress label, we
are sending a label release for the corresponding withdraw message and also
i am expecting only the INGRESS will start the LSP deletion process for any
genuine case (of course assumption is all LSR is configured with the
forwarding of the label release)

[Ramia, Kannan Babu]  [Vijayanand C - CTD, Chennai.] By holding the label I
mean, the PHop would be holding its upstream labels unnecessarily even in
genuine LSP tear down scenarios( when withdraw is received from its
downstream node which is egress) 
 Here ingress is not initiating deletion the egress does it by sending
withdraw. 

[Ramia, Kannan Babu]  I have one more idea for differntiating a genuine
withdraw to the special withdraw. i.e if the LSR A sends a label with draw
message to LSR B with the FEC-X and label TLV has label value IMPLICIT NULL
and in the optinal paramters it can send a changed label value to be used,
there by we can differntiate from the genuine case (in genuine case the
optinal paramter wont contain any label) to the special case. if we have
this check in the label withdraw procedure it will solve our problem. This
solution wont distrub the LSP setup where as the ingress retry solution will
distrub the LSP, which is undesiarable one also we need to provide the
checking criteria for re-establishing the LSP.
 
 
 
 
Second one could be there should be a provision to change the label for the
particular FEC. I.e any point of time the valid next hop LSR can advertise a
change of label for that FEC. Here problems are we need to maintain the
context of that advertisement (LM).
[Vijayanand C - CTD, Chennai.]  This becomes unsolicited advertisement.

[Ramia, Kannan Babu] i dont see any problem in this kind of advertisement,
even if u are configured with DOD ordered mode if any change in hop count or
PV, the downstream LSR will anyway generate a LM with out any outstanding
LR. So i want to treat the change in label also the same way as that of
change in hop count.
[Vijayanand C - CTD, Chennai.] Changing the attributes of the label mapping
( like PV) is different from changing the label itself. Again the context
maintenance (old label, FEC) for this is a problem as you said. Even the
question of communicating changed attributes seldom arises in DOd Ord
control. In cases where it happens, such as Next hop change, it was debated
at length earlier in this list if it was proper to unsolicitedly advertise
the changed attributes.
 
 
A better way would be for the egress to withdraw the label. However the
ingress will not issue a request unless it is in Independent control. This
anyway is a problem. My suggestin would be - The ingress after sending a
release can issue a fresh request for the label even if its not in
independent control if it still supports label switching on the FEC. I feel
This would be more cleaner .

[Ramia, Kannan Babu]  How the ingress will know that it need to request
again or initate LSP establishment once again for the same FEC (i mean here
what criteria or conditions it checks before it does this again..) because
in some genuine cases if egress wants to remove the LSP then it may lead to
infinite looping.
[Vijayanand C - CTD, Chennai.] This kind of situation( retrying) will anyway
apply in Independent control( all nodes along the LSP may potentially
retry). So how will you solve the problem in that case ?  What I am
suggesting is if ordered control is used the retry can be done only by the
ingress. Any retry mechanism would have some back off and stopping criteria
associated with it implicitly.
 
 
 
 
 
Vijay 
 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 6.00.2716.2200" name=3DGENERATOR>
<META content=3D"Microsoft Word 9" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C25F00.0A4CA8B0" rel=3DFile-List><!--[if gte =
mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in =
1.25in; mso-header-margin: .5in; mso-footer-margin: .5in; =
mso-paper-source: 0; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
P.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
LI.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
DIV.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
SPAN.EmailStyle15 {
	COLOR: black; mso-style-type: personal-compose; mso-ansi-font-size: =
10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
DIV.Section1 {
	page: Section1
}
OL {
	MARGIN-BOTTOM: 0in
}
UL {
	MARGIN-BOTTOM: 0in
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in">
<DIV><SPAN class=3D040505406-18092002><FONT face=3DArial =
color=3D#0000ff size=3D2>See my=20
inline Comments</FONT></SPAN></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> Vijayanand C - =
CTD, Chennai.=20
  [mailto:vijayc@ctd.hcltech.com]<BR><B>Sent:</B> Wednesday, September =
18, 2002=20
  12:15 PM<BR><B>To:</B> Ramia, Kannan Babu<BR><B>Cc:</B>=20
  mpls@uu.net<BR><B>Subject:</B> RE: Clarification on Handling a =
specific event=20
  in LDP<BR><BR></FONT></DIV>
  <DIV><SPAN class=3D821362606-18092002><FONT face=3DArial =
color=3D#0000ff size=3D2>See=20
  my comments inline</FONT></SPAN></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> Ramia, Kannan =
Babu=20
    [mailto:kannan.babu.ramia@intel.com]<BR><B>Sent:</B> Wednesday, =
September=20
    18, 2002 11:48 AM<BR><B>To:</B> 'Vijayanand C - CTD, Chennai.'; =
Ramia,=20
    Kannan Babu<BR><B>Cc:</B> mpls@uu.net<BR><B>Subject:</B> RE: =
Clarification=20
    on Handling a specific event in LDP<BR><BR></FONT></DIV>
    <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff size=3D2>hi=20
    vijay..</FONT></SPAN></DIV>
    <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
    size=3D2>&nbsp;&nbsp; </FONT></SPAN></DIV>
    <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
    size=3D2>thanks for ur reply ..but i still have some thing to get =
clarified=20
    ... please s</FONT></SPAN><SPAN class=3D400110906-18092002><FONT =
face=3DArial=20
    color=3D#0000ff size=3D2>ee in line Comments</FONT></SPAN></DIV>
    <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
    size=3D2>bye</FONT></SPAN></DIV>
    <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
    size=3D2>kb</FONT></SPAN></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> Vijayanand C =
- CTD,=20
      Chennai. [mailto:vijayc@ctd.hcltech.com]<BR><B>Sent:</B> =
Wednesday,=20
      September 18, 2002 11:39 AM<BR><B>To:</B> Ramia, Kannan =
Babu<BR><B>Cc:</B>=20
      mpls@uu.net<BR><B>Subject:</B> RE: Clarification on Handling a =
specific=20
      event in LDP<BR><BR></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D169422705-18092002>Kannan,</SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D169422705-18092002>This is a special case. =
</SPAN></FONT></DIV>
      <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
        <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]><SPAN=20
        class=3DEmailStyle15><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></DI=
V>
        <DIV class=3DSection1>
        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial color=3Dblack=20
        size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial color=3Dblack=20
        size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt">I=20
        have a solution for this =
problem.<o:p></o:p></SPAN></FONT></SPAN></P>
        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt">Basically=20
        if any LSR receives an Label withdraw message from its valid =
Next hop=20
        neighbor then before propagating to its upstream peers it need =
to check=20
        the value of the label being withdrawn, if the label happens to =
be an=20
        NULL label then it should not propagate the label withdraw to =
its=20
        upstream peers. Now this LSR should now assume itself as an =
egress for=20
        that LSP.<BR><FONT color=3D#0000ff><SPAN=20
        class=3D169422705-18092002>[Vijayanand C - CTD, Chennai.]&nbsp; =
What will=20
        happen in valid cases when the eggress actually wants to =
withdraw=20
        label&nbsp;and when u no longer want to switch for that FEC =
?The=20
        pennultimate hop should&nbsp;not hold&nbsp;the label in that =
case.=20
        How&nbsp;will the Phop know&nbsp;for which case the withdraw =
applies=20
        ?</SPAN><SPAN class=3D169422705-18092002>&nbsp;</SPAN><SPAN=20
        class=3D169422705-18092002>&nbsp;</SPAN></FONT><SPAN=20
        class=3D169422705-18092002><FONT =
color=3D#0000ff>&nbsp;<BR><SPAN=20
        =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></FONT></SPAN></P=
>
        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
        class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
        class=3D400110906-18092002>[Ramia, Kannan Babu]&nbsp; Actually=20
        here&nbsp;we are not holding the egress label, we are sending a =

        label&nbsp;release for the corresponding&nbsp;withdraw message=20
        and&nbsp;also&nbsp;i am expecting only the INGRESS will start =
the LSP=20
        deletion process for any genuine case (of course assumption is =
all LSR=20
        is configured with the forwarding of the label =
release)<BR><SPAN=20
        class=3D821362606-18092002><BR><FONT color=3D#0000ff><SPAN=20
        class=3D040505406-18092002>[Ramia, Kannan=20
        Babu]&nbsp;&nbsp;</SPAN>[Vijayanand C - CTD, Chennai.]&nbsp;By =
holding=20
        the label I mean, the PHop would be holding its upstream labels =

        unnecessarily&nbsp;even in genuine LSP&nbsp;tear down =
scenarios( when=20
        withdraw is received from its downstream node which is egress)=20
        </FONT></SPAN></SPAN></FONT></SPAN></SPAN></SPAN></P>
        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
        class=3D169422705-18092002><SPAN =
class=3D400110906-18092002><SPAN=20
        class=3D821362606-18092002><FONT color=3D#0000ff>&nbsp;Here =
ingress is not=20
        initiating deletion the egress does it by sending=20
        withdraw.&nbsp;<BR><SPAN=20
        =
class=3D040505406-18092002></SPAN></FONT></SPAN></SPAN></SPAN></SPAN></S=
PAN></P>
        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
        class=3D169422705-18092002><SPAN =
class=3D400110906-18092002><SPAN=20
        class=3D821362606-18092002><FONT color=3D#0000ff><SPAN=20
        class=3D040505406-18092002><FONT color=3D#ff0000>[Ramia, Kannan =

        Babu]&nbsp;&nbsp;I have one more idea for&nbsp;differntiating a =
genuine=20
        withdraw to the special withdraw. i.e if the LSR A&nbsp;sends a =
label=20
        with draw message to LSR B with the&nbsp;FEC-X and label TLV =
has label=20
        value&nbsp;IMPLICIT NULL and in the optinal paramters it can =
send=20
        a&nbsp;changed label value to be used, there by we can =
differntiate from=20
        the genuine case (in genuine case the optinal paramter wont =
contain any=20
        label)&nbsp;to the special case. if we have this check in the =
label=20
        withdraw procedure it will solve our problem. This solution =
wont distrub=20
        the LSP setup where as the ingress retry solution will distrub =
the LSP,=20
        which is&nbsp;undesiarable one also we need to provide the =
checking=20
        criteria for re-establishing the=20
        LSP.</FONT></SPAN></FONT></SPAN></SPAN></SPAN><![if =
!supportEmptyParas]><![endif]></SPAN></SPAN></P>
        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial color=3Dblack=20
        size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"></SPAN></FONT></SPAN>&nbsp;</P>
        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial color=3Dblack=20
        size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"></SPAN></FONT></SPAN>&nbsp;</P>
        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial color=3Dblack=20
        size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"></SPAN></FONT></SPAN>&nbsp;</P>
        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial color=3Dblack=20
        size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt">Second=20
        one could be there should be a provision to change the label =
for the=20
        particular FEC. I.e any point of time the valid next hop LSR =
can=20
        advertise a change of label for that FEC. Here problems are we =
need to=20
        maintain the context of that advertisement (LM).<BR><SPAN=20
        class=3D169422705-18092002><FONT color=3D#0000ff>[Vijayanand C =
- CTD,=20
        Chennai.]&nbsp;&nbsp;This becomes unsolicited =
advertisement.<BR><SPAN=20
        =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></FONT></SPAN></P=
>
        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
        class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
        class=3D400110906-18092002>[Ramia, Kannan Babu] i dont see any =
problem in=20
        this kind of advertisement, even if u are configured with DOD =
ordered=20
        mode if any&nbsp;change in hop count or&nbsp;PV, the downstream =

        LSR&nbsp;will anyway generate a LM with out any outstanding =
LR.&nbsp;So=20
        i want to treat the change in label also the same way as that =
of change=20
        in hop count.<BR><SPAN class=3D821362606-18092002><FONT=20
        color=3D#0000ff>[Vijayanand C - CTD, Chennai.]&nbsp;Changing=20
        the&nbsp;attributes of the label mapping (&nbsp;like =
PV)&nbsp;is=20
        different from changing the label itself. Again the context =
maintenance=20
        (old label, FEC) for this is a problem as you said. Even the =
question of=20
        communicating changed attributes seldom arises in DOd Ord =
control. In=20
        cases where it happens, such as Next hop change, it was debated =
at=20
        length earlier in this list if it was proper to unsolicitedly =
advertise=20
        the changed=20
        =
attributes.</FONT></SPAN></SPAN></FONT></SPAN></SPAN></SPAN></P>
        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><FONT=20
        color=3D#0000ff><SPAN=20
        =
class=3D169422705-18092002></SPAN></FONT></SPAN></FONT></SPAN>&nbsp;</P>=

        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><FONT=20
        color=3D#0000ff><SPAN=20
        =
class=3D169422705-18092002></SPAN></FONT></SPAN></FONT></SPAN>&nbsp;</P>=
<![if !supportEmptyParas]><![endif]>
        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
        class=3D169422705-18092002><FONT color=3D#0000ff>A better way =
would be for=20
        the egress to withdraw the label. However&nbsp;the ingress will =
not=20
        issue a request unless it is in Independent control. This =
anyway&nbsp;is=20
        a&nbsp;problem. My suggestin would be - The ingress after =
sending a=20
        release can issue a fresh request&nbsp;for the label even if =
its not in=20
        independent control if it still supports label switching on the =
FEC. I=20
        feel This&nbsp;would be more cleaner .<BR><SPAN=20
        =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></SPAN></P>
        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
        class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
        class=3D400110906-18092002>[Ramia, Kannan Babu]&nbsp;&nbsp;How =
the ingress=20
        will know that it need to request again or initate LSP =
establishment=20
        once again for the same FEC (i mean here what criteria or =
conditions it=20
        checks before it does this again..) because in some genuine =
cases if=20
        egress wants to remove the LSP&nbsp;then it may lead to =
infinite=20
        looping.<BR><SPAN class=3D821362606-18092002><FONT=20
        color=3D#0000ff>[Vijayanand C - CTD, Chennai.]&nbsp;This kind =
of=20
        situation(&nbsp;retrying)&nbsp;will anyway apply in Independent =
control(=20
        all nodes along the LSP may potentially retry). So&nbsp;how =
will you=20
        solve the problem in that case ? &nbsp;What I am suggesting is =
if=20
        ordered control is used the retry can be done only by the =
ingress. Any=20
        retry mechanism would have some back off and stopping criteria=20
        associated with it=20
        implicitly.</FONT></SPAN></SPAN></FONT></SPAN></SPAN></SPAN></P>=

        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
        class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
        =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></SPAN>&nbsp;</P>=

        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
        class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
        =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></SPAN>&nbsp;</P>=

        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
        class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
        =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></SPAN>&nbsp;</P>=

        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
        =
class=3D169422705-18092002></SPAN></SPAN></FONT></SPAN>&nbsp;</P>
        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
        =
class=3D169422705-18092002></SPAN></SPAN></FONT></SPAN>&nbsp;</P>
        <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
        class=3D169422705-18092002></SPAN><SPAN =
class=3D169422705-18092002><FONT=20
        =
color=3D#0000ff>Vijay</FONT></SPAN>&nbsp;<o:p></o:p></SPAN><!--[if =
supportFields]><font color=3Dblack><span=20
style=3D'color:black'><span =
style=3D'mso-element:field-begin'></span><span=20
style=3D"mso-spacerun: yes">&nbsp;</span>AUTOTEXTLIST \s &quot;E-mail=20
Signature&quot; <span =
style=3D'mso-element:field-separator'></span></span></font><![endif]--><=
/FONT></SPAN></P>
        <P class=3DMsoNormal><!--[if supportFields]><font =
color=3Dblack><span=20
style=3D'color:black'><span =
style=3D'mso-element:field-end'></span></span></font><![endif]--><FONT=20
        color=3Dblack><SPAN style=3D"COLOR: black"><![if =
!supportEmptyParas]><![endif]>&nbsp;</SPAN></FONT><FONT=20
        color=3Dblack><SPAN=20
        style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BLOCKQUOTE=
></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C25EF0.60EF4250--


From owner-mpls@UU.NET  Wed Sep 18 05:19:56 2002
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 ESMTP id FAA06518
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 05:19:56 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngvd27310
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 09:21:39 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngvd26899;
	Wed, 18 Sep 2002 09:21:24 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngvd13262
	for mpls-outgoing; Wed, 18 Sep 2002 09:21:07 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQngvd13235
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 09:21:03 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 QQngvd13826
	for <mpls@uu.net>; Wed, 18 Sep 2002 09:20:18 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngvd26013
	for <mpls@uu.net>; Wed, 18 Sep 2002 09:20:18 GMT
Received: from funnel.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQngvd26006
	for <mpls@uu.net>; Wed, 18 Sep 2002 09:20:17 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id FAA07785 for <mpls@uu.net>; Wed, 18 Sep 2002 05:20:17 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8I9J3f06666 for mpls@uu.net; Wed, 18 Sep 2002 05:19:03 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQngvd13135
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 09:17:56 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 QQngvd27685
	for <mpls@uu.net>; Wed, 18 Sep 2002 09:17:20 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngvd03145
	for <mpls@uu.net>; Wed, 18 Sep 2002 09:17:20 GMT
Received: from ganesh.ctd.hctech.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.64.2])
	id QQngvd03128
	for <mpls@uu.net>; Wed, 18 Sep 2002 09:17:18 GMT
Received: by GANESH with Internet Mail Service (5.5.2653.19)
	id <TA10BP4R>; Wed, 18 Sep 2002 14:50:56 +0530
Message-ID: <55E277B99171E041ABF5F4B1C6DDCA0688599C@HARITHA>
From: "Vijayanand C - CTD, Chennai." <vijayc@ctd.hcltech.com>
To: "Ramia, Kannan Babu" <kannan.babu.ramia@intel.com>
Cc: mpls@UU.NET
Subject: RE: Clarification on Handling a specific event in LDP
Date: Wed, 18 Sep 2002 14:49:28 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C25EF4.7D70C990"
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_01C25EF4.7D70C990
Content-Type: text/plain;
	charset="iso-8859-1"

Again you are overriding the Dod Ord control by using a label map along with
a withdraw whereby  it becomes an unsolicited mapping.
Apart from the Question of syntactical correctness of sending an unsolicited
label map there is another problem.
 The domain in configured for Dod Ord. THis may be due to constraints in the
switches to install labels. For example, in GMPLS, the set of desired labels
is sent along with the request indicating the range of labels the upstream
can switch onto. Hence the Dod Ord control has significance in such
scenarios' and overriding it may cause confusion.
 
The issue of change in next hop for an FEC right at the egress( which is
usually egress for routing domain) is a very rare situation and I think it
does nt warrant drastic changes to the semantics and operation of LDP
 
Vijay
-----Original Message-----
From: Ramia, Kannan Babu [mailto:kannan.babu.ramia@intel.com]
Sent: Wednesday, September 18, 2002 2:20 PM
To: 'Vijayanand C - CTD, Chennai.'
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP


See my inline Comments
-----Original Message-----
From: Vijayanand C - CTD, Chennai. [mailto:vijayc@ctd.hcltech.com]
Sent: Wednesday, September 18, 2002 12:15 PM
To: Ramia, Kannan Babu
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP


See my comments inline
-----Original Message-----
From: Ramia, Kannan Babu [mailto:kannan.babu.ramia@intel.com]
Sent: Wednesday, September 18, 2002 11:48 AM
To: 'Vijayanand C - CTD, Chennai.'; Ramia, Kannan Babu
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP


hi vijay..
   
thanks for ur reply ..but i still have some thing to get clarified ...
please see in line Comments
 
bye
kb
-----Original Message-----
From: Vijayanand C - CTD, Chennai. [mailto:vijayc@ctd.hcltech.com]
Sent: Wednesday, September 18, 2002 11:39 AM
To: Ramia, Kannan Babu
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP


Kannan,
This is a special case. 
 
 
I have a solution for this problem.
Basically if any LSR receives an Label withdraw message from its valid Next
hop neighbor then before propagating to its upstream peers it need to check
the value of the label being withdrawn, if the label happens to be an NULL
label then it should not propagate the label withdraw to its upstream peers.
Now this LSR should now assume itself as an egress for that LSP.
[Vijayanand C - CTD, Chennai.]  What will happen in valid cases when the
eggress actually wants to withdraw label and when u no longer want to switch
for that FEC ?The pennultimate hop should not hold the label in that case.
How will the Phop know for which case the withdraw applies ?   

[Ramia, Kannan Babu]  Actually here we are not holding the egress label, we
are sending a label release for the corresponding withdraw message and also
i am expecting only the INGRESS will start the LSP deletion process for any
genuine case (of course assumption is all LSR is configured with the
forwarding of the label release)

[Ramia, Kannan Babu]  [Vijayanand C - CTD, Chennai.] By holding the label I
mean, the PHop would be holding its upstream labels unnecessarily even in
genuine LSP tear down scenarios( when withdraw is received from its
downstream node which is egress) 
 Here ingress is not initiating deletion the egress does it by sending
withdraw. 

[Ramia, Kannan Babu]  I have one more idea for differntiating a genuine
withdraw to the special withdraw. i.e if the LSR A sends a label with draw
message to LSR B with the FEC-X and label TLV has label value IMPLICIT NULL
and in the optinal paramters it can send a changed label value to be used,
there by we can differntiate from the genuine case (in genuine case the
optinal paramter wont contain any label) to the special case. if we have
this check in the label withdraw procedure it will solve our problem. This
solution wont distrub the LSP setup where as the ingress retry solution will
distrub the LSP, which is undesiarable one also we need to provide the
checking criteria for re-establishing the LSP.
 
 
 
 
Second one could be there should be a provision to change the label for the
particular FEC. I.e any point of time the valid next hop LSR can advertise a
change of label for that FEC. Here problems are we need to maintain the
context of that advertisement (LM).
[Vijayanand C - CTD, Chennai.]  This becomes unsolicited advertisement.

[Ramia, Kannan Babu] i dont see any problem in this kind of advertisement,
even if u are configured with DOD ordered mode if any change in hop count or
PV, the downstream LSR will anyway generate a LM with out any outstanding
LR. So i want to treat the change in label also the same way as that of
change in hop count.
[Vijayanand C - CTD, Chennai.] Changing the attributes of the label mapping
( like PV) is different from changing the label itself. Again the context
maintenance (old label, FEC) for this is a problem as you said. Even the
question of communicating changed attributes seldom arises in DOd Ord
control. In cases where it happens, such as Next hop change, it was debated
at length earlier in this list if it was proper to unsolicitedly advertise
the changed attributes.
 
 
A better way would be for the egress to withdraw the label. However the
ingress will not issue a request unless it is in Independent control. This
anyway is a problem. My suggestin would be - The ingress after sending a
release can issue a fresh request for the label even if its not in
independent control if it still supports label switching on the FEC. I feel
This would be more cleaner .

[Ramia, Kannan Babu]  How the ingress will know that it need to request
again or initate LSP establishment once again for the same FEC (i mean here
what criteria or conditions it checks before it does this again..) because
in some genuine cases if egress wants to remove the LSP then it may lead to
infinite looping.
[Vijayanand C - CTD, Chennai.] This kind of situation( retrying) will anyway
apply in Independent control( all nodes along the LSP may potentially
retry). So how will you solve the problem in that case ?  What I am
suggesting is if ordered control is used the retry can be done only by the
ingress. Any retry mechanism would have some back off and stopping criteria
associated with it implicitly.
 
 
 
 
 
Vijay 
 

------_=_NextPart_001_01C25EF4.7D70C990
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR>
<META content=3D"Microsoft Word 9" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C25F00.0A4CA8B0" rel=3DFile-List><!--[if gte =
mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in =
1.25in; mso-header-margin: .5in; mso-footer-margin: .5in; =
mso-paper-source: 0; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
P.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
LI.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
DIV.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
SPAN.EmailStyle15 {
	COLOR: black; mso-style-type: personal-compose; mso-ansi-font-size: =
10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
DIV.Section1 {
	page: Section1
}
OL {
	MARGIN-BOTTOM: 0in
}
UL {
	MARGIN-BOTTOM: 0in
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in">
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D878170609-18092002>Again=20
you are overriding the Dod Ord control by using a label map along with =
a=20
withdraw whereby&nbsp; it becomes an unsolicited =
mapping.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D878170609-18092002>Apart=20
from the Question of syntactical correctness of sending an unsolicited =
label map=20
there is another problem.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D878170609-18092002>&nbsp;The domain in configured for Dod Ord. =
THis may be=20
due to constraints in the switches to install labels. For example, in =
GMPLS, the=20
set of desired labels is sent along with the request indicating the =
range of=20
labels the upstream can switch onto. Hence the Dod Ord control has =
significance=20
in such scenarios' and overriding it may cause =
confusion.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D878170609-18092002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D878170609-18092002>The=20
issue of change in next hop for an FEC right at the egress( which is =
usually=20
egress for routing domain)&nbsp;is a very rare situation and I think it =
does nt=20
warrant drastic changes to the semantics and operation of=20
LDP</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D878170609-18092002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D878170609-18092002>Vijay</SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px"><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]>
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Ramia, Kannan =
Babu=20
  [mailto:kannan.babu.ramia@intel.com]<BR><B>Sent:</B> Wednesday, =
September 18,=20
  2002 2:20 PM<BR><B>To:</B> 'Vijayanand C - CTD, =
Chennai.'<BR><B>Cc:</B>=20
  mpls@uu.net<BR><B>Subject:</B> RE: Clarification on Handling a =
specific event=20
  in LDP<BR><BR></FONT></DIV>
  <DIV><SPAN class=3D040505406-18092002><FONT face=3DArial =
color=3D#0000ff size=3D2>See=20
  my inline Comments</FONT></SPAN></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> Vijayanand C - =
CTD,=20
    Chennai. [mailto:vijayc@ctd.hcltech.com]<BR><B>Sent:</B> Wednesday, =

    September 18, 2002 12:15 PM<BR><B>To:</B> Ramia, Kannan =
Babu<BR><B>Cc:</B>=20
    mpls@uu.net<BR><B>Subject:</B> RE: Clarification on Handling a =
specific=20
    event in LDP<BR><BR></FONT></DIV>
    <DIV><SPAN class=3D821362606-18092002><FONT face=3DArial =
color=3D#0000ff=20
    size=3D2>See my comments inline</FONT></SPAN></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> Ramia, Kannan =
Babu=20
      [mailto:kannan.babu.ramia@intel.com]<BR><B>Sent:</B> Wednesday, =
September=20
      18, 2002 11:48 AM<BR><B>To:</B> 'Vijayanand C - CTD, Chennai.'; =
Ramia,=20
      Kannan Babu<BR><B>Cc:</B> mpls@uu.net<BR><B>Subject:</B> RE: =
Clarification=20
      on Handling a specific event in LDP<BR><BR></FONT></DIV>
      <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
      size=3D2>hi vijay..</FONT></SPAN></DIV>
      <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
      size=3D2>&nbsp;&nbsp; </FONT></SPAN></DIV>
      <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
      size=3D2>thanks for ur reply ..but i still have some thing to get =
clarified=20
      ... please s</FONT></SPAN><SPAN class=3D400110906-18092002><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>ee in line Comments</FONT></SPAN></DIV>
      <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
      size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
      size=3D2>bye</FONT></SPAN></DIV>
      <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
      size=3D2>kb</FONT></SPAN></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> Vijayanand =
C - CTD,=20
        Chennai. [mailto:vijayc@ctd.hcltech.com]<BR><B>Sent:</B> =
Wednesday,=20
        September 18, 2002 11:39 AM<BR><B>To:</B> Ramia, Kannan=20
        Babu<BR><B>Cc:</B> mpls@uu.net<BR><B>Subject:</B> RE: =
Clarification on=20
        Handling a specific event in LDP<BR><BR></FONT></DIV>
        <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
        class=3D169422705-18092002>Kannan,</SPAN></FONT></DIV>
        <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
        class=3D169422705-18092002>This is a special case. =
</SPAN></FONT></DIV>
        <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
          <DIV class=3DOutlookMessageHeader dir=3Dltr =
align=3Dleft><SPAN=20
          class=3DEmailStyle15><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></DI=
V>
          <DIV class=3DSection1>
          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial=20
          color=3Dblack size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial=20
          color=3Dblack size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt">I=20
          have a solution for this =
problem.<o:p></o:p></SPAN></FONT></SPAN></P>
          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt">Basically=20
          if any LSR receives an Label withdraw message from its valid =
Next hop=20
          neighbor then before propagating to its upstream peers it =
need to=20
          check the value of the label being withdrawn, if the label =
happens to=20
          be an NULL label then it should not propagate the label =
withdraw to=20
          its upstream peers. Now this LSR should now assume itself as =
an egress=20
          for that LSP.<BR><FONT color=3D#0000ff><SPAN=20
          class=3D169422705-18092002>[Vijayanand C - CTD, =
Chennai.]&nbsp; What=20
          will happen in valid cases when the eggress actually wants to =
withdraw=20
          label&nbsp;and when u no longer want to switch for that FEC =
?The=20
          pennultimate hop should&nbsp;not hold&nbsp;the label in that =
case.=20
          How&nbsp;will the Phop know&nbsp;for which case the withdraw =
applies=20
          ?</SPAN><SPAN class=3D169422705-18092002>&nbsp;</SPAN><SPAN=20
          class=3D169422705-18092002>&nbsp;</SPAN></FONT><SPAN=20
          class=3D169422705-18092002><FONT =
color=3D#0000ff>&nbsp;<BR><SPAN=20
          =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></FONT></SPAN></P=
>
          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
          class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
          class=3D400110906-18092002>[Ramia, Kannan Babu]&nbsp; =
Actually=20
          here&nbsp;we are not holding the egress label, we are sending =
a=20
          label&nbsp;release for the corresponding&nbsp;withdraw =
message=20
          and&nbsp;also&nbsp;i am expecting only the INGRESS will start =
the LSP=20
          deletion process for any genuine case (of course assumption =
is all LSR=20
          is configured with the forwarding of the label =
release)<BR><SPAN=20
          class=3D821362606-18092002><BR><FONT color=3D#0000ff><SPAN=20
          class=3D040505406-18092002>[Ramia, Kannan=20
          Babu]&nbsp;&nbsp;</SPAN>[Vijayanand C - CTD, =
Chennai.]&nbsp;By holding=20
          the label I mean, the PHop would be holding its upstream =
labels=20
          unnecessarily&nbsp;even in genuine LSP&nbsp;tear down =
scenarios( when=20
          withdraw is received from its downstream node which is =
egress)=20
          </FONT></SPAN></SPAN></FONT></SPAN></SPAN></SPAN></P>
          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
          class=3D169422705-18092002><SPAN =
class=3D400110906-18092002><SPAN=20
          class=3D821362606-18092002><FONT color=3D#0000ff>&nbsp;Here =
ingress is not=20
          initiating deletion the egress does it by sending=20
          withdraw.&nbsp;<BR><SPAN=20
          =
class=3D040505406-18092002></SPAN></FONT></SPAN></SPAN></SPAN></SPAN></S=
PAN></P>
          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
          class=3D169422705-18092002><SPAN =
class=3D400110906-18092002><SPAN=20
          class=3D821362606-18092002><FONT color=3D#0000ff><SPAN=20
          class=3D040505406-18092002><FONT color=3D#ff0000>[Ramia, =
Kannan=20
          Babu]&nbsp;&nbsp;I have one more idea for&nbsp;differntiating =
a=20
          genuine withdraw to the special withdraw. i.e if the LSR =
A&nbsp;sends=20
          a label with draw message to LSR B with the&nbsp;FEC-X and =
label TLV=20
          has label value&nbsp;IMPLICIT NULL and in the optinal =
paramters it can=20
          send a&nbsp;changed label value to be used, there by we can=20
          differntiate from the genuine case (in genuine case the =
optinal=20
          paramter wont contain any label)&nbsp;to the special case. if =
we have=20
          this check in the label withdraw procedure it will solve our =
problem.=20
          This solution wont distrub the LSP setup where as the ingress =
retry=20
          solution will distrub the LSP, which is&nbsp;undesiarable one =
also we=20
          need to provide the checking criteria for re-establishing the =

          LSP.</FONT></SPAN></FONT></SPAN></SPAN></SPAN><![if =
!supportEmptyParas]><![endif]></SPAN></SPAN></P>
          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial=20
          color=3Dblack size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"></SPAN></FONT></SPAN>&nbsp;</P>
          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial=20
          color=3Dblack size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"></SPAN></FONT></SPAN>&nbsp;</P><![if =
!supportEmptyParas]><![endif]><!--[if supportFields]><font =
color=3Dblack><span=20
style=3D'color:black'><span =
style=3D'mso-element:field-begin'></span><span=20
style=3D"mso-spacerun: yes">&nbsp;</span>AUTOTEXTLIST \s &quot;E-mail=20
Signature&quot; <span =
style=3D'mso-element:field-separator'></span></span></font><![endif]--><=
!--[if supportFields]><font color=3Dblack><span=20
style=3D'color:black'><span =
style=3D'mso-element:field-end'></span></span></font><![endif]-->
          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial=20
          color=3Dblack size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"></SPAN></FONT></SPAN>&nbsp;</P>
          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial=20
          color=3Dblack size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt">Second=20
          one could be there should be a provision to change the label =
for the=20
          particular FEC. I.e any point of time the valid next hop LSR =
can=20
          advertise a change of label for that FEC. Here problems are =
we need to=20
          maintain the context of that advertisement (LM).<BR><SPAN=20
          class=3D169422705-18092002><FONT color=3D#0000ff>[Vijayanand =
C - CTD,=20
          Chennai.]&nbsp;&nbsp;This becomes unsolicited =
advertisement.<BR><SPAN=20
          =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></FONT></SPAN></P=
>
          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
          class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
          class=3D400110906-18092002>[Ramia, Kannan Babu] i dont see =
any problem=20
          in this kind of advertisement, even if u are configured with =
DOD=20
          ordered mode if any&nbsp;change in hop count or&nbsp;PV, the=20
          downstream LSR&nbsp;will anyway generate a LM with out any =
outstanding=20
          LR.&nbsp;So i want to treat the change in label also the same =
way as=20
          that of change in hop count.<BR><SPAN =
class=3D821362606-18092002><FONT=20
          color=3D#0000ff>[Vijayanand C - CTD, Chennai.]&nbsp;Changing=20
          the&nbsp;attributes of the label mapping (&nbsp;like =
PV)&nbsp;is=20
          different from changing the label itself. Again the context=20
          maintenance (old label, FEC) for this is a problem as you =
said. Even=20
          the question of communicating changed attributes seldom =
arises in DOd=20
          Ord control. In cases where it happens, such as Next hop =
change, it=20
          was debated at length earlier in this list if it was proper =
to=20
          unsolicitedly advertise the changed=20
          =
attributes.</FONT></SPAN></SPAN></FONT></SPAN></SPAN></SPAN></P>
          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><FONT=20
          color=3D#0000ff><SPAN=20
          =
class=3D169422705-18092002></SPAN></FONT></SPAN></FONT></SPAN>&nbsp;</P>=

          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><FONT=20
          color=3D#0000ff><SPAN=20
          =
class=3D169422705-18092002></SPAN></FONT></SPAN></FONT></SPAN>&nbsp;</P>=

          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
          class=3D169422705-18092002><FONT color=3D#0000ff>A better way =
would be for=20
          the egress to withdraw the label. However&nbsp;the ingress =
will not=20
          issue a request unless it is in Independent control. This=20
          anyway&nbsp;is a&nbsp;problem. My suggestin would be - The =
ingress=20
          after sending a release can issue a fresh request&nbsp;for =
the label=20
          even if its not in independent control if it still supports =
label=20
          switching on the FEC. I feel This&nbsp;would be more cleaner=20
          .<BR><SPAN=20
          =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></SPAN></P>
          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
          class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
          class=3D400110906-18092002>[Ramia, Kannan =
Babu]&nbsp;&nbsp;How the=20
          ingress will know that it need to request again or initate =
LSP=20
          establishment once again for the same FEC (i mean here what =
criteria=20
          or conditions it checks before it does this again..) because =
in some=20
          genuine cases if egress wants to remove the LSP&nbsp;then it =
may lead=20
          to infinite looping.<BR><SPAN =
class=3D821362606-18092002><FONT=20
          color=3D#0000ff>[Vijayanand C - CTD, Chennai.]&nbsp;This kind =
of=20
          situation(&nbsp;retrying)&nbsp;will anyway apply in =
Independent=20
          control( all nodes along the LSP may potentially retry). =
So&nbsp;how=20
          will you solve the problem in that case ? &nbsp;What I am =
suggesting=20
          is if ordered control is used the retry can be done only by =
the=20
          ingress. Any retry mechanism would have some back off and =
stopping=20
          criteria associated with it=20
          =
implicitly.</FONT></SPAN></SPAN></FONT></SPAN></SPAN></SPAN></P>
          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
          class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
          =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></SPAN>&nbsp;</P>=

          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
          class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
          =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></SPAN>&nbsp;</P>=

          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
          class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
          =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></SPAN>&nbsp;</P>=

          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
          =
class=3D169422705-18092002></SPAN></SPAN></FONT></SPAN>&nbsp;</P>
          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
          =
class=3D169422705-18092002></SPAN></SPAN></FONT></SPAN>&nbsp;</P>
          <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
          class=3D169422705-18092002></SPAN><SPAN =
class=3D169422705-18092002><FONT=20
          =
color=3D#0000ff>Vijay</FONT></SPAN>&nbsp;<o:p></o:p></SPAN></FONT></SPAN=
></P>
          <P class=3DMsoNormal><FONT color=3Dblack><SPAN =
style=3D"COLOR: black"><![if =
!supportEmptyParas]><![endif]>&nbsp;</SPAN></FONT><FONT=20
          face=3DArial color=3D#0000ff size=3D2><SPAN=20
          style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BLOCKQUOTE=
></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C25EF4.7D70C990--



From owner-mpls@UU.NET  Wed Sep 18 05:58:32 2002
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 ESMTP id FAA07204
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 05:58:32 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngvg01509
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 10:00:16 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngvg01222;
	Wed, 18 Sep 2002 10:00:08 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngvf15692
	for mpls-outgoing; Wed, 18 Sep 2002 09:59:48 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQngvf15687
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 09:59:33 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 QQngvf20038
	for <mpls@UU.NET>; Wed, 18 Sep 2002 09:59:05 GMT
From: neil.2.harrison@bt.com
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngvf06606
	for <mpls@UU.NET>; Wed, 18 Sep 2002 09:59:05 GMT
Received: from cbibipnt05.hc.bt.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: saturn.bt.com [193.113.57.20])
	id QQngvf06576
	for <mpls@UU.NET>; Wed, 18 Sep 2002 09:59:03 GMT
Received: by cbibipnt05.hc.bt.com with Internet Mail Service (5.5.2654.89)
	id <TC5QJP10>; Wed, 18 Sep 2002 10:59:10 +0100
Message-ID: <B9571FDEBD3DD21181E500606DD5EE0514BAC1F9@mbddmknt01.nat.bt.com>
To: vijayc@ctd.hcltech.com, kannan.babu.ramia@intel.com
Cc: mpls@UU.NET
Subject: RE: Clarification on Handling a specific event in LDP
Date: Wed, 18 Sep 2002 10:58:30 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.89)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C25EF9.F1115DB0"
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_01C25EF9.F1115DB0
Content-Type: text/plain;
	charset="iso-8859-1"

2 questions....please see below.  regards Neil
-----Original Message-----
From: Vijayanand C - CTD, Chennai. [mailto:vijayc@ctd.hcltech.com]
Sent: 18 September 2002 10:19
To: Ramia, Kannan Babu
Cc: mpls@UU.NET
Subject: RE: Clarification on Handling a specific event in LDP


Again you are overriding the Dod Ord control by using a label map along with
a withdraw whereby  it becomes an unsolicited mapping.
Apart from the Question of syntactical correctness of sending an unsolicited
label map there is another problem.
 The domain in configured for Dod Ord. THis may be due to constraints in the
switches to install labels. For example, in GMPLS, the set of desired labels
is sent along with the request indicating the range of labels the upstream
can switch onto. Hence the Dod Ord control has significance in such
scenarios' and overriding it may cause confusion. 
NH=> How does PHP work with GMPLS? 
 
The issue of change in next hop for an FEC right at the egress( which is
usually egress for routing domain) is a very rare situation and I think it
does nt warrant drastic changes to the semantics and operation of LDP 
NH=> If you stopped using PHP would this problem not 'go away'?
<snipped to end NH>
 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 5.00.3013.2600" name=3DGENERATOR>
<META content=3D"Microsoft Word 9" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C25F00.0A4CA8B0" rel=3DFile-List><!--[if gte =
mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in =
1.25in; mso-header-margin: .5in; mso-footer-margin: .5in; =
mso-paper-source: 0; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
P.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
LI.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
DIV.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
SPAN.EmailStyle15 {
	COLOR: black; mso-style-type: personal-compose; mso-ansi-font-size: =
10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
DIV.Section1 {
	page: Section1
}
OL {
	MARGIN-BOTTOM: 0in
}
UL {
	MARGIN-BOTTOM: 0in
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in">
<DIV><FONT color=3D#0000ff face=3D"Comic Sans MS" size=3D2><SPAN=20
class=3D770235609-18092002>2&nbsp;questions....please see below.&nbsp; =
regards=20
Neil</SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; =
MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Vijayanand C - =
CTD, Chennai.=20
  [mailto:vijayc@ctd.hcltech.com]<BR><B>Sent:</B> 18 September 2002=20
  10:19<BR><B>To:</B> Ramia, Kannan Babu<BR><B>Cc:</B>=20
  mpls@UU.NET<BR><B>Subject:</B> RE: Clarification on Handling a =
specific event=20
  in LDP<BR><BR></DIV></FONT>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D878170609-18092002>Again you are overriding the Dod Ord =
control by using=20
  a label map along with a withdraw whereby&nbsp; it becomes an =
unsolicited=20
  mapping.</SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D878170609-18092002>Apart from the Question of syntactical =
correctness of=20
  sending an unsolicited label map there is another =
problem.</SPAN></FONT></DIV>
  <DIV><FONT size=3D2><FONT color=3D#0000ff><FONT face=3DArial><SPAN=20
  class=3D878170609-18092002>&nbsp;The domain in configured for Dod =
Ord. THis may=20
  be due to constraints in the switches to install labels. For example, =
in=20
  GMPLS, the set of desired labels is sent along with the request =
indicating the=20
  range of labels the upstream can switch onto. Hence the Dod Ord =
control has=20
  significance in such scenarios' and overriding it may cause =
confusion.<FONT=20
  face=3D"Comic Sans MS"><SPAN=20
  =
class=3D770235609-18092002>&nbsp;</SPAN></FONT></SPAN></FONT></FONT></FO=
NT></DIV>
  <DIV><FONT size=3D2><FONT face=3DArial><SPAN =
class=3D878170609-18092002><FONT=20
  color=3D#800080 face=3D"Comic Sans MS"><SPAN =
class=3D770235609-18092002>NH=3D&gt; How=20
  does PHP work with =
GMPLS?&nbsp;</SPAN></FONT></SPAN></FONT></FONT></DIV>
  <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
  class=3D878170609-18092002></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT size=3D2><FONT color=3D#0000ff><FONT face=3DArial><SPAN=20
  class=3D878170609-18092002>The issue of change in next hop for an FEC =
right at=20
  the egress( which is usually egress for routing domain)&nbsp;is a =
very rare=20
  situation and I think it does nt warrant drastic changes to the =
semantics and=20
  operation of LDP<FONT face=3D"Comic Sans MS"><SPAN=20
  =
class=3D770235609-18092002>&nbsp;</SPAN></FONT></SPAN></FONT></FONT></FO=
NT></DIV>
  <DIV><FONT size=3D2><FONT face=3DArial><SPAN =
class=3D878170609-18092002><FONT=20
  color=3D#800080 face=3D"Comic Sans MS"><SPAN=20
  class=3D770235609-18092002>NH=3D&gt;&nbsp;If you stopped using PHP =
would this=20
  problem not 'go away'?</SPAN></FONT></SPAN></FONT></FONT></DIV>
  <DIV><FONT size=3D2><FONT face=3DArial><SPAN =
class=3D878170609-18092002><FONT=20
  color=3D#800080 face=3D"Comic Sans MS"><SPAN =
class=3D770235609-18092002>&lt;snipped=20
  to end NH&gt;</SPAN></FONT></SPAN></FONT></FONT></DIV>
  <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px"><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]>
    <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
      <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
        <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
          <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px"><![if =
!supportEmptyParas]><![endif]>
            <DIV class=3DSection1><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]><!--[if supportFields]><font =
color=3Dblack><span=20
style=3D'color:black'><span =
style=3D'mso-element:field-begin'></span><span=20
style=3D"mso-spacerun: yes">&nbsp;</span>AUTOTEXTLIST \s &quot;E-mail=20
Signature&quot; <span =
style=3D'mso-element:field-separator'></span></span></font><![endif]--><=
!--[if supportFields]><font color=3Dblack><span=20
style=3D'color:black'><span =
style=3D'mso-element:field-end'></span></span></font><![endif]-->
            <P=20
            class=3DMsoNormal><![if =
!supportEmptyParas]><![endif]>&nbsp;</P></DIV></BLOCKQUOTE></BLOCKQUOTE>=
</BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C25EF9.F1115DB0--


From owner-mpls@UU.NET  Wed Sep 18 06:23:05 2002
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 ESMTP id GAA07650
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 06:23:05 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngvh22621
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 10:24:49 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngvh22225;
	Wed, 18 Sep 2002 10:24:34 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngvh04225
	for mpls-outgoing; Wed, 18 Sep 2002 10:24:08 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQngvh04219
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 10:24: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 QQngvh06650
	for <mpls@uu.net>; Wed, 18 Sep 2002 10:23:18 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngvh24285
	for <mpls@uu.net>; Wed, 18 Sep 2002 10:23:17 GMT
Received: from funnel.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQngvh24277
	for <mpls@uu.net>; Wed, 18 Sep 2002 10:23:17 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id GAA12772 for <mpls@uu.net>; Wed, 18 Sep 2002 06:23:03 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8IAN3F13980 for mpls@uu.net; Wed, 18 Sep 2002 06:23:03 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQngvh04178
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 10:22:04 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 QQngvh12552
	for <mpls@UU.NET>; Wed, 18 Sep 2002 10:22:01 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngvh24821
	for <mpls@UU.NET>; Wed, 18 Sep 2002 10:22:01 GMT
Received: from ganesh.ctd.hctech.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.64.2])
	id QQngvh24803
	for <mpls@UU.NET>; Wed, 18 Sep 2002 10:22:00 GMT
Received: by GANESH with Internet Mail Service (5.5.2653.19)
	id <TA10BRKG>; Wed, 18 Sep 2002 15:55:37 +0530
Message-ID: <55E277B99171E041ABF5F4B1C6DDCA06885A87@HARITHA>
From: "Vijayanand C - CTD, Chennai." <vijayc@ctd.hcltech.com>
To: neil.2.harrison@bt.com, kannan.babu.ramia@intel.com
Cc: mpls@UU.NET
Subject: RE: Clarification on Handling a specific event in LDP
Date: Wed, 18 Sep 2002 15:54:09 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C25EFD.8690F960"
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_01C25EFD.8690F960
Content-Type: text/plain;
	charset="iso-8859-1"

I am not stating that PHP is used in GMPLS. I am just stating that using
unsolicited mappings in Dod Ord scenarios is not advisable. If unsolicited
mappings were allowed for this PHP problem it would encourage application to
similar problems.It would allow the flexibility for LSRs to change labels
allocated unsolicitedly in a strictly Dod Ord domain.
 
Please correct me if I am wrong
 
Regards,
Vijay
-----Original Message-----
From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]
Sent: Wednesday, September 18, 2002 3:29 PM
To: vijayc@ctd.hcltech.com; kannan.babu.ramia@intel.com
Cc: mpls@UU.NET
Subject: RE: Clarification on Handling a specific event in LDP


2 questions....please see below.  regards Neil
-----Original Message-----
From: Vijayanand C - CTD, Chennai. [mailto:vijayc@ctd.hcltech.com]
Sent: 18 September 2002 10:19
To: Ramia, Kannan Babu
Cc: mpls@UU.NET
Subject: RE: Clarification on Handling a specific event in LDP


Again you are overriding the Dod Ord control by using a label map along with
a withdraw whereby  it becomes an unsolicited mapping.
Apart from the Question of syntactical correctness of sending an unsolicited
label map there is another problem.
 The domain in configured for Dod Ord. THis may be due to constraints in the
switches to install labels. For example, in GMPLS, the set of desired labels
is sent along with the request indicating the range of labels the upstream
can switch onto. Hence the Dod Ord control has significance in such
scenarios' and overriding it may cause confusion. 
NH=> How does PHP work with GMPLS? 
 
The issue of change in next hop for an FEC right at the egress( which is
usually egress for routing domain) is a very rare situation and I think it
does nt warrant drastic changes to the semantics and operation of LDP 
NH=> If you stopped using PHP would this problem not 'go away'?
<snipped to end NH>
 

------_=_NextPart_001_01C25EFD.8690F960
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR>
<META content=3D"Microsoft Word 9" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C25F00.0A4CA8B0" rel=3DFile-List><!--[if gte =
mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in =
1.25in; mso-header-margin: .5in; mso-footer-margin: .5in; =
mso-paper-source: 0; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
P.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
LI.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
DIV.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
SPAN.EmailStyle15 {
	COLOR: black; mso-style-type: personal-compose; mso-ansi-font-size: =
10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
DIV.Section1 {
	page: Section1
}
OL {
	MARGIN-BOTTOM: 0in
}
UL {
	MARGIN-BOTTOM: 0in
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in">
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D982261310-18092002>I am=20
not stating that PHP is used in GMPLS. I am just stating that using =
unsolicited=20
mappings in Dod Ord scenarios is not advisable. If unsolicited mappings =
were=20
allowed for this PHP problem it would encourage application =
to&nbsp;similar=20
problems.It would allow the flexibility for LSRs to change labels =
allocated=20
unsolicitedly in a strictly Dod Ord domain.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D982261310-18092002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D982261310-18092002>Please=20
correct me if I am wrong</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D982261310-18092002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D982261310-18092002>Regards,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D982261310-18092002>Vijay</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> =
neil.2.harrison@bt.com=20
  [mailto:neil.2.harrison@bt.com]<BR><B>Sent:</B> Wednesday, September =
18, 2002=20
  3:29 PM<BR><B>To:</B> vijayc@ctd.hcltech.com;=20
  kannan.babu.ramia@intel.com<BR><B>Cc:</B> =
mpls@UU.NET<BR><B>Subject:</B> RE:=20
  Clarification on Handling a specific event in LDP<BR><BR></FONT></DIV>=

  <DIV><FONT face=3D"Comic Sans MS" color=3D#0000ff size=3D2><SPAN=20
  class=3D770235609-18092002>2&nbsp;questions....please see =
below.&nbsp; regards=20
  Neil</SPAN></FONT></DIV>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff =
2px solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
    size=3D2>-----Original Message-----<BR><B>From:</B> Vijayanand C - =
CTD,=20
    Chennai. [mailto:vijayc@ctd.hcltech.com]<BR><B>Sent:</B> 18 =
September 2002=20
    10:19<BR><B>To:</B> Ramia, Kannan Babu<BR><B>Cc:</B>=20
    mpls@UU.NET<BR><B>Subject:</B> RE: Clarification on Handling a =
specific=20
    event in LDP<BR><BR></DIV></FONT>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D878170609-18092002>Again you are overriding the Dod Ord =
control by=20
    using a label map along with a withdraw whereby&nbsp; it becomes an =

    unsolicited mapping.</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D878170609-18092002>Apart from the Question of syntactical =
correctness=20
    of sending an unsolicited label map there is another=20
    problem.</SPAN></FONT></DIV>
    <DIV><FONT size=3D2><FONT color=3D#0000ff><FONT face=3DArial><SPAN=20
    class=3D878170609-18092002>&nbsp;The domain in configured for Dod =
Ord. THis=20
    may be due to constraints in the switches to install labels. For =
example, in=20
    GMPLS, the set of desired labels is sent along with the request =
indicating=20
    the range of labels the upstream can switch onto. Hence the Dod Ord =
control=20
    has significance in such scenarios' and overriding it may cause=20
    confusion.<FONT face=3D"Comic Sans MS"><SPAN=20
    =
class=3D770235609-18092002>&nbsp;</SPAN></FONT></SPAN></FONT></FONT></FO=
NT></DIV>
    <DIV><FONT size=3D2><FONT face=3DArial><SPAN =
class=3D878170609-18092002><FONT=20
    face=3D"Comic Sans MS" color=3D#800080><SPAN =
class=3D770235609-18092002>NH=3D&gt;=20
    How does PHP work with =
GMPLS?&nbsp;</SPAN></FONT></SPAN></FONT></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D878170609-18092002></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT size=3D2><FONT color=3D#0000ff><FONT face=3DArial><SPAN=20
    class=3D878170609-18092002>The issue of change in next hop for an =
FEC right at=20
    the egress( which is usually egress for routing domain)&nbsp;is a =
very rare=20
    situation and I think it does nt warrant drastic changes to the =
semantics=20
    and operation of LDP<FONT face=3D"Comic Sans MS"><SPAN=20
    =
class=3D770235609-18092002>&nbsp;</SPAN></FONT></SPAN></FONT></FONT></FO=
NT></DIV>
    <DIV><FONT size=3D2><FONT face=3DArial><SPAN =
class=3D878170609-18092002><FONT=20
    face=3D"Comic Sans MS" color=3D#800080><SPAN=20
    class=3D770235609-18092002>NH=3D&gt;&nbsp;If you stopped using PHP =
would this=20
    problem not 'go away'?</SPAN></FONT></SPAN></FONT></FONT></DIV>
    <DIV><FONT size=3D2><FONT face=3DArial><SPAN =
class=3D878170609-18092002><FONT=20
    face=3D"Comic Sans MS" color=3D#800080><SPAN=20
    class=3D770235609-18092002>&lt;snipped to end=20
    NH&gt;</SPAN></FONT></SPAN></FONT></FONT></DIV>
    <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px"><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]>
      <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
        <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
          <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
            <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px"><![if =
!supportEmptyParas]><![endif]>
              <DIV class=3DSection1><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]><!--[if supportFields]><font =
color=3Dblack><span=20
style=3D'color:black'><span =
style=3D'mso-element:field-begin'></span><span=20
style=3D"mso-spacerun: yes">&nbsp;</span>AUTOTEXTLIST \s &quot;E-mail=20
Signature&quot; <span =
style=3D'mso-element:field-separator'></span></span></font><![endif]--><=
!--[if supportFields]><font color=3Dblack><span=20
style=3D'color:black'><span =
style=3D'mso-element:field-end'></span></span></font><![endif]-->
              <P class=3DMsoNormal><![if =
!supportEmptyParas]><![endif]><FONT=20
              face=3DArial color=3D#0000ff=20
          =
size=3D2></FONT>&nbsp;</P></DIV></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE><=
/BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C25EFD.8690F960--



From owner-mpls@UU.NET  Wed Sep 18 08:51:20 2002
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 ESMTP id IAA10954
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 08:51:20 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngvr20452
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 12:53:04 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngvr20145;
	Wed, 18 Sep 2002 12:52:56 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngvr17711
	for mpls-outgoing; Wed, 18 Sep 2002 12:52:43 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQngvr17706
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 12:52:30 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 QQngvr06469
	for <mpls@UU.NET>; Wed, 18 Sep 2002 12:52:25 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngvr29293
	for <mpls@UU.NET>; Wed, 18 Sep 2002 12:52:24 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 QQngvr29282
	for <mpls@UU.NET>; Wed, 18 Sep 2002 12:52:24 GMT
Received: from cisco.com (erosen-u10.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8ICqHKB010068;
	Wed, 18 Sep 2002 05:52:17 -0700 (PDT)
Message-Id: <200209181252.g8ICqHKB010068@sj-msg-core-1.cisco.com>
To: "Ramia, Kannan Babu" <kannan.babu.ramia@intel.com>
cc: "MPLS (E-mail)" <mpls@UU.NET>
Subject: Re: Clarification on Handling a specific event in LDP 
In-reply-to: Your message of Tue, 17 Sep 2002 22:07:45 -0700.
             <12B638FEE763F74696D8544752E7204812EA17@bgsmsx101.iind.intel.com> 
Reply-To: erosen@cisco.com
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.2
 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Wed, 18 Sep 2002 08:52:16 -0400
From: Eric Rosen <erosen@cisco.com>
Sender: owner-mpls@UU.NET
Precedence: bulk


I think  this case  slipped through the  cracks, because  the use of  LDP in
DoD/Ordered mode was envisioned for  use in networks consisting of ATM-LSRs,
which of course don't do PHP.

Is this a practical problem for you, or simply a theoretical one? 


From owner-mpls@UU.NET  Wed Sep 18 09:25:50 2002
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 ESMTP id JAA11996
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 09:25:50 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngvt25335
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 13:27:35 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngvt25195;
	Wed, 18 Sep 2002 13:27:30 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngvt06759
	for mpls-outgoing; Wed, 18 Sep 2002 13:27:04 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQngvt06752
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 13:26: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 QQngvt17935
	for <mpls@UU.NET>; Wed, 18 Sep 2002 13:26:13 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngvt06230
	for <mpls@UU.NET>; Wed, 18 Sep 2002 13:26:13 GMT
Received: from celox-ma1-ems1.celoxnetworks.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: celox-ma1-imap1.celoxnetworks.com [12.40.60.233])
	id QQngvt06217
	for <mpls@UU.NET>; Wed, 18 Sep 2002 13:26:12 GMT
Received: by celox-ma1-ems1.celoxnetworks.com with Internet Mail Service (5.5.2653.19)
	id <RBC1GN0W>; Wed, 18 Sep 2002 09:26:12 -0400
Message-ID: <1117F7D44159934FB116E36F4ABF221B0267EB09@celox-ma1-ems1.celoxnetworks.com>
From: "Gray, Eric" <egray@celoxnetworks.com>
To: "'Vijayanand C - CTD, Chennai.'" <vijayc@ctd.hcltech.com>,
        "Ramia, Kannan Babu" <kannan.babu.ramia@intel.com>
Cc: mpls@UU.NET
Subject: RE: Clarification on Handling a specific event in LDP
Date: Wed, 18 Sep 2002 09:26:03 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C25F16.EF9F9F10"
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_01C25F16.EF9F9F10
Content-Type: text/plain

Vijay/Kannan,

 

            Please see below...

 

Eric W. Gray

Systems Architect

Celox Networks, Inc.

egray@celoxnetworks.com

508 305 7214

 

-----Original Message-----
From: Vijayanand C - CTD, Chennai. [mailto:vijayc@ctd.hcltech.com] 
Sent: Wednesday, September 18, 2002 5:19 AM
To: Ramia, Kannan Babu
Cc: mpls@UU.NET
Subject: RE: Clarification on Handling a specific event in LDP

 

Again you are overriding the Dod Ord control by using a label map along with
a withdraw whereby  it becomes an unsolicited mapping.

Apart from the Question of syntactical correctness of sending an unsolicited
label map there is another problem.

 

There are cases in which DoD vs DU distribution and Ordered vs Independent
control

become rather vague distinctions.  That is the problem hidden behind the
fact that

people talk past each other on this topic, rather than talking to each
other.

 

Rather than talking about the gross terms, consider the details of
implementation

you are likely to encounter. If the negotiated mode between two LSRs is DoD,
then

each LSR is required to accept one or more Label Request messages for each
FEC

and neither is required to accept _any_ unsolicited Label Mapping messages.
The

LSR that receives an unsolicited Label Mapping may decide to immediate
release

it - or worse yet - it may assume the peer has become confused and tear down
the

LDP session. This is in essence the problem that Vijay is probably concerned
with.

 

However, there is always the robust notion of being generous in what you
accept.

 

While, IMHO, the LSR that sends an unsolicited Label Mapping when in DoD
mode

is generally in the wrong, it seems _very_ un-robust behavior to terminate
the LDP

session and it might be more robust to at least retain the new Label Mapping
(yes,

even if in conservative retention mode - thus blurring another distinction).
In fact,

it is likely that some implementations will treat such an unsolicited Label
Mapping

as an implied Label Withdraw (though - with effort - I can dredge up an old
E-Mail

message in which members of the LDP design team were adamant that this was 

not the way it is intended to work).

 

In the case Kannan is pointing out, the retention of the new Label Mapping
(in case

the previous one is withdrawn) is very much more robust than almost anything
else 

you might do (with the possible exception of using it as an implied
Withdraw).  If

the new Label Mapping is not retained, then the LSP is removed edge to edge
and

must be re-established.  

 

This - by the way - is exactly the behavior originally intended in the DoD,
Ordered 

control mode: LSR A in Kannan's case would Withdraw all Labels associated
with

forwarding toward the newly discovered peer LSR C and then wait for all
affected

ingress LSRs to send Label Requests to re-establish LSPs.  I brought this up
with 

the LDP design team 3 years ago and many of them agreed that this would not
be 

good behavior.  However, it was not clear that any other behavior should be
explicitly

specified.

 

 The domain in configured for Dod Ord. THis may be due to constraints in the
switches to install labels. For example, in GMPLS, the set of desired labels
is sent along with the request indicating the range of labels the upstream
can switch onto. Hence the Dod Ord control has significance in such
scenarios' and overriding it may cause confusion.

 

The issue of change in next hop for an FEC right at the egress( which is
usually egress for routing domain) is a very rare situation and I think it
does nt warrant drastic changes to the semantics and operation of LDP

 

Vijay

-----Original Message-----
From: Ramia, Kannan Babu [mailto:kannan.babu.ramia@intel.com]
Sent: Wednesday, September 18, 2002 2:20 PM
To: 'Vijayanand C - CTD, Chennai.'
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP

See my inline Comments

-----Original Message-----
From: Vijayanand C - CTD, Chennai. [mailto:vijayc@ctd.hcltech.com]
Sent: Wednesday, September 18, 2002 12:15 PM
To: Ramia, Kannan Babu
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP

See my comments inline

-----Original Message-----
From: Ramia, Kannan Babu [mailto:kannan.babu.ramia@intel.com]
Sent: Wednesday, September 18, 2002 11:48 AM
To: 'Vijayanand C - CTD, Chennai.'; Ramia, Kannan Babu
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP

hi vijay..

   

thanks for ur reply ..but i still have some thing to get clarified ...
please see in line Comments

 

bye

kb

-----Original Message-----
From: Vijayanand C - CTD, Chennai. [mailto:vijayc@ctd.hcltech.com]
Sent: Wednesday, September 18, 2002 11:39 AM
To: Ramia, Kannan Babu
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP

Kannan,

This is a special case. 

 

 

I have a solution for this problem.

Basically if any LSR receives an Label withdraw message from its valid Next
hop neighbor then before propagating to its upstream peers it need to check
the value of the label being withdrawn, if the label happens to be an NULL
label then it should not propagate the label withdraw to its upstream peers.
Now this LSR should now assume itself as an egress for that LSP.
[Vijayanand C - CTD, Chennai.]  What will happen in valid cases when the
eggress actually wants to withdraw label and when u no longer want to switch
for that FEC ?The pennultimate hop should not hold the label in that case.
How will the Phop know for which case the withdraw applies ?   

[Ramia, Kannan Babu]  Actually here we are not holding the egress label, we
are sending a label release for the corresponding withdraw message and also
i am expecting only the INGRESS will start the LSP deletion process for any
genuine case (of course assumption is all LSR is configured with the
forwarding of the label release)

[Ramia, Kannan Babu]  [Vijayanand C - CTD, Chennai.] By holding the label I
mean, the PHop would be holding its upstream labels unnecessarily even in
genuine LSP tear down scenarios( when withdraw is received from its
downstream node which is egress) 

 Here ingress is not initiating deletion the egress does it by sending
withdraw. 

[Ramia, Kannan Babu]  I have one more idea for differntiating a genuine
withdraw to the special withdraw. i.e if the LSR A sends a label with draw
message to LSR B with the FEC-X and label TLV has label value IMPLICIT NULL
and in the optinal paramters it can send a changed label value to be used,
there by we can differntiate from the genuine case (in genuine case the
optinal paramter wont contain any label) to the special case. if we have
this check in the label withdraw procedure it will solve our problem. This
solution wont distrub the LSP setup where as the ingress retry solution will
distrub the LSP, which is undesiarable one also we need to provide the
checking criteria for re-establishing the LSP.

 

 



 

 

Second one could be there should be a provision to change the label for the
particular FEC. I.e any point of time the valid next hop LSR can advertise a
change of label for that FEC. Here problems are we need to maintain the
context of that advertisement (LM).
[Vijayanand C - CTD, Chennai.]  This becomes unsolicited advertisement.

[Ramia, Kannan Babu] i dont see any problem in this kind of advertisement,
even if u are configured with DOD ordered mode if any change in hop count or
PV, the downstream LSR will anyway generate a LM with out any outstanding
LR. So i want to treat the change in label also the same way as that of
change in hop count.
[Vijayanand C - CTD, Chennai.] Changing the attributes of the label mapping
( like PV) is different from changing the label itself. Again the context
maintenance (old label, FEC) for this is a problem as you said. Even the
question of communicating changed attributes seldom arises in DOd Ord
control. In cases where it happens, such as Next hop change, it was debated
at length earlier in this list if it was proper to unsolicitedly advertise
the changed attributes.

 

 

A better way would be for the egress to withdraw the label. However the
ingress will not issue a request unless it is in Independent control. This
anyway is a problem. My suggestin would be - The ingress after sending a
release can issue a fresh request for the label even if its not in
independent control if it still supports label switching on the FEC. I feel
This would be more cleaner .

[Ramia, Kannan Babu]  How the ingress will know that it need to request
again or initate LSP establishment once again for the same FEC (i mean here
what criteria or conditions it checks before it does this again..) because
in some genuine cases if egress wants to remove the LSP then it may lead to
infinite looping.
[Vijayanand C - CTD, Chennai.] This kind of situation( retrying) will anyway
apply in Independent control( all nodes along the LSP may potentially
retry). So how will you solve the problem in that case ?  What I am
suggesting is if ordered control is used the retry can be done only by the
ingress. Any retry mechanism would have some back off and stopping criteria
associated with it implicitly.

 

 

 

 

 

Vijay 

 


------_=_NextPart_001_01C25F16.EF9F9F10
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">


<meta name=Generator content="Microsoft Word 10 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle16
	{font-family:Arial;
	color:black;}
span.EmailStyle19
	{font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Vijay/Kannan,</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></font><font
size=2 color=green face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:green'>Please see below...</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<div>

<p class=MsoAutoSig><font size=2 color=navy face="Times New Roman"><span
style='font-size:10.0pt;color:navy'>Eric W. Gray</span></font></p>

<p class=MsoAutoSig><font size=2 color=navy face="Times New Roman"><span
style='font-size:10.0pt;color:navy'>Systems Architect</span></font></p>

<p class=MsoAutoSig><font size=2 color=navy face="Times New Roman"><span
style='font-size:10.0pt;color:navy'>Celox Networks, Inc.</span></font></p>

<p class=MsoAutoSig><font size=2 color=navy face="Times New Roman"><span
style='font-size:10.0pt;color:navy'>egray@celoxnetworks.com</span></font></p>

<p class=MsoPlainText><font size=2 color=navy face="Courier New"><span
style='font-size:10.0pt;color:navy'>508 305 7214</span></font></p>

</div>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>

<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma'>-----Original Message-----<br>
<b><span style='font-weight:bold'>From:</span></b> Vijayanand C - CTD, Chennai.
[mailto:vijayc@ctd.hcltech.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, September 18,
2002 5:19 AM<br>
<b><span style='font-weight:bold'>To:</span></b> Ramia, Kannan Babu<br>
<b><span style='font-weight:bold'>Cc:</span></b> mpls@UU.NET<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: Clarification on
Handling a specific event in LDP</span></font></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

<div>

<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Again you are overriding the Dod Ord
control by using a label map along with a withdraw whereby&nbsp; it becomes an
unsolicited mapping.</span></font></p>

</div>

<div>

<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Apart from the Question of syntactical
correctness of sending an unsolicited label map there is another problem.</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>There are cases in which DoD vs DU distribution
and Ordered vs Independent control</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>become rather vague distinctions.&nbsp;
That is the problem hidden behind the fact that</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>people talk past each other on this
topic, rather than talking to each other.</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>Rather than talking about the gross
terms, consider the details of implementation</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>you are likely to encounter. If the
negotiated mode between two LSRs is DoD, then</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>each LSR is required to accept one or
more Label Request messages for each FEC</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>and neither is required to accept _<i><span
style='font-style:italic'>any</span></i>_ unsolicited Label Mapping
messages.&nbsp; The</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>LSR that receives an unsolicited Label
Mapping may decide to immediate release</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>it - or worse yet - it may
assume the peer has become confused and tear down the</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>LDP session. This is in essence the
problem that Vijay is probably concerned with.</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>However, there is always the robust notion
of being generous in what you accept.</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>While, IMHO, the LSR that sends an
unsolicited Label Mapping when in DoD mode</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>is generally in the wrong, it seems _<i><span
style='font-style:italic'>very</span></i>_ un-robust behavior to terminate the
LDP</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>session and it might be more robust to at
least retain the new Label Mapping (yes,</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>even if in conservative retention mode -
thus blurring another distinction).&nbsp; In fact,</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>it is likely that some implementations
will treat such an unsolicited Label Mapping</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>as an implied Label Withdraw (though -
with effort - I can dredge up an old E-Mail</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>message in which members of the LDP
design team were adamant that this was </span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>not the way it is intended to work).</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>In the case Kannan is pointing out, the
retention of the new Label Mapping (in case</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>the previous one is withdrawn) is very
much more robust than almost anything else </span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>you might do (with the possible exception
of using it as an implied Withdraw).&nbsp; If</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>the new Label Mapping is not retained,
then the LSP is removed edge to edge and</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>must be re-established.&nbsp; </span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>This - by the way - is exactly
the behavior originally intended in the DoD, Ordered </span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>control mode: LSR A in Kannan's case
would Withdraw all Labels associated with</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>forwarding toward the newly discovered
peer LSR C and then wait for all affected</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>ingress LSRs to send Label Requests to
re-establish LSPs.&nbsp; I brought this up with </span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>the LDP design team 3 years ago and many
of them agreed that this would not be </span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>good behavior.&nbsp; However, it was not
clear that any other behavior should be explicitly</span></font></p>

<p class=MsoNormal><font size=2 color=green face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:green'>specified.</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

</div>

<div>

<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>&nbsp;The domain in configured for Dod
Ord. THis may be due to constraints in the switches to install labels. For
example, in GMPLS, the set of desired labels is sent along with the request
indicating the range of labels the upstream can switch onto. Hence the Dod Ord
control has significance in such scenarios' and overriding it may cause
confusion.</span></font></p>

</div>

<div>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>The issue of change in next hop for an FEC
right at the egress( which is usually egress for routing domain)&nbsp;is a very
rare situation and I think it does nt warrant drastic changes to the semantics
and operation of LDP</span></font></p>

</div>

<div>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Vijay</span></font></p>

</div>

<blockquote style='margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>

<p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'>-----Original Message-----<br>
<b><span style='font-weight:bold'>From:</span></b> Ramia, Kannan Babu
[mailto:kannan.babu.ramia@intel.com]<br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, September 18,
2002 2:20 PM<br>
<b><span style='font-weight:bold'>To:</span></b> 'Vijayanand C - CTD, Chennai.'<br>
<b><span style='font-weight:bold'>Cc:</span></b> mpls@uu.net<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: Clarification on
Handling a specific event in LDP</span></font></p>

<div>

<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>See my inline Comments</span></font></p>

</div>

<blockquote style='margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>

<p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'>-----Original Message-----<br>
<b><span style='font-weight:bold'>From:</span></b> Vijayanand C - CTD, Chennai.
[mailto:vijayc@ctd.hcltech.com]<br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, September 18,
2002 12:15 PM<br>
<b><span style='font-weight:bold'>To:</span></b> Ramia, Kannan Babu<br>
<b><span style='font-weight:bold'>Cc:</span></b> mpls@uu.net<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: Clarification on
Handling a specific event in LDP</span></font></p>

<div>

<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>See my comments inline</span></font></p>

</div>

<blockquote style='margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>

<p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'>-----Original Message-----<br>
<b><span style='font-weight:bold'>From:</span></b> Ramia, Kannan Babu
[mailto:kannan.babu.ramia@intel.com]<br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, September 18,
2002 11:48 AM<br>
<b><span style='font-weight:bold'>To:</span></b> 'Vijayanand C - CTD,
Chennai.'; Ramia, Kannan Babu<br>
<b><span style='font-weight:bold'>Cc:</span></b> mpls@uu.net<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: Clarification on
Handling a specific event in LDP</span></font></p>

<div>

<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>hi vijay..</span></font></p>

</div>

<div>

<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>&nbsp;&nbsp; </span></font></p>

</div>

<div>

<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>thanks for ur reply ..but i still have
some thing to get clarified ... please see in line Comments</span></font></p>

</div>

<div>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>bye</span></font></p>

</div>

<div>

<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>kb</span></font></p>

</div>

<blockquote style='margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>

<p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'>-----Original Message-----<br>
<b><span style='font-weight:bold'>From:</span></b> Vijayanand C - CTD, Chennai.
[mailto:vijayc@ctd.hcltech.com]<br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, September 18,
2002 11:39 AM<br>
<b><span style='font-weight:bold'>To:</span></b> Ramia, Kannan Babu<br>
<b><span style='font-weight:bold'>Cc:</span></b> mpls@uu.net<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: Clarification on
Handling a specific event in LDP</span></font></p>

<div>

<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Kannan,</span></font></p>

</div>

<div>

<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>This is a special case. </span></font></p>

</div>

<blockquote style='margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>

<p class=MsoNormal><span class=EmailStyle16><font size=2 color=black
face=Arial><span style='font-size:10.0pt'>&nbsp;</span></font></span></p>

<p class=MsoNormal><span class=EmailStyle16><font size=2 color=black
face=Arial><span style='font-size:10.0pt'>&nbsp;</span></font></span></p>

<p class=MsoNormal><span class=EmailStyle16><font size=2 color=black
face=Arial><span style='font-size:10.0pt'>I have a solution for this problem.</span></font></span></p>

<p class=MsoNormal><span class=EmailStyle16><font size=2 color=black
face=Arial><span style='font-size:10.0pt'>Basically if any LSR receives an
Label withdraw message from its valid Next hop neighbor then before propagating
to its upstream peers it need to check the value of the label being withdrawn,
if the label happens to be an NULL label then it should not propagate the label
withdraw to its upstream peers. Now this LSR should now assume itself as an
egress for that LSP.</span></font></span><font size=2 color=black face=Arial><span
style='font-size:10.0pt;font-family:Arial;color:black'><br>
</span></font><span class=EmailStyle16><font size=2 color=blue face=Arial><span
style='font-size:10.0pt;color:blue'>[Vijayanand C - CTD, Chennai.]&nbsp; What
will happen in valid cases when the eggress actually wants to withdraw
label&nbsp;and when u no longer want to switch for that FEC ?The pennultimate
hop should&nbsp;not hold&nbsp;the label in that case. How&nbsp;will the Phop
know&nbsp;for which case the withdraw applies ?&nbsp;&nbsp;&nbsp;</span></font></span></p>

<p class=MsoNormal><span class=EmailStyle16><font size=2 color=red face=Arial><span
style='font-size:10.0pt;color:red'>[Ramia, Kannan Babu]&nbsp; Actually
here&nbsp;we are not holding the egress label, we are sending a
label&nbsp;release for the corresponding&nbsp;withdraw message
and&nbsp;also&nbsp;i am expecting only the INGRESS will start the LSP deletion
process for any genuine case (of course assumption is all LSR is configured
with the forwarding of the label release)</span></font></span><font size=2
color=red face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:red'><br>
<br>
</span></font><span class=EmailStyle16><font size=2 color=blue face=Arial><span
style='font-size:10.0pt;color:blue'>[Ramia, Kannan Babu]&nbsp;&nbsp;[Vijayanand
C - CTD, Chennai.]&nbsp;By holding the label I mean, the PHop would be holding
its upstream labels unnecessarily&nbsp;even in genuine LSP&nbsp;tear down
scenarios( when withdraw is received from its downstream node which is egress) </span></font></span></p>

<p class=MsoNormal><span class=EmailStyle16><font size=2 color=blue face=Arial><span
style='font-size:10.0pt;color:blue'>&nbsp;Here ingress is not initiating
deletion the egress does it by sending withdraw.&nbsp;</span></font></span></p>

<p class=MsoNormal><span class=EmailStyle16><font size=2 color=red face=Arial><span
style='font-size:10.0pt;color:red'>[Ramia, Kannan Babu]&nbsp;&nbsp;I have one
more idea for&nbsp;differntiating a genuine withdraw to the special withdraw.
i.e if the LSR A&nbsp;sends a label with draw message to LSR B with
the&nbsp;FEC-X and label TLV has label value&nbsp;IMPLICIT NULL and in the
optinal paramters it can send a&nbsp;changed label value to be used, there by
we can differntiate from the genuine case (in genuine case the optinal paramter
wont contain any label)&nbsp;to the special case. if we have this check in the
label withdraw procedure it will solve our problem. This solution wont distrub
the LSP setup where as the ingress retry solution will distrub the LSP, which
is&nbsp;undesiarable one also we need to provide the checking criteria for
re-establishing the LSP.</span></font></span></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=MsoNormal></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=MsoNormal><span class=EmailStyle16><font size=2 color=black
face=Arial><span style='font-size:10.0pt'>&nbsp;</span></font></span></p>

<p class=MsoNormal><span class=EmailStyle16><font size=2 color=black
face=Arial><span style='font-size:10.0pt'>Second one could be there should be a
provision to change the label for the particular FEC. I.e any point of time the
valid next hop LSR can advertise a change of label for that FEC. Here problems
are we need to maintain the context of that advertisement (LM).</span></font></span><font
size=2 color=black face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:black'><br>
</span></font><span class=EmailStyle16><font size=2 color=blue face=Arial><span
style='font-size:10.0pt;color:blue'>[Vijayanand C - CTD,
Chennai.]&nbsp;&nbsp;This becomes unsolicited advertisement.</span></font></span></p>

<p class=MsoNormal><span class=EmailStyle16><font size=2 color=red face=Arial><span
style='font-size:10.0pt;color:red'>[Ramia, Kannan Babu] i dont see any problem
in this kind of advertisement, even if u are configured with DOD ordered mode
if any&nbsp;change in hop count or&nbsp;PV, the downstream LSR&nbsp;will anyway
generate a LM with out any outstanding LR.&nbsp;So i want to treat the change
in label also the same way as that of change in hop count.</span></font></span><font
size=2 color=red face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:red'><br>
</span></font><span class=EmailStyle16><font size=2 color=blue face=Arial><span
style='font-size:10.0pt;color:blue'>[Vijayanand C - CTD,
Chennai.]&nbsp;Changing the&nbsp;attributes of the label mapping (&nbsp;like
PV)&nbsp;is different from changing the label itself. Again the context
maintenance (old label, FEC) for this is a problem as you said. Even the
question of communicating changed attributes seldom arises in DOd Ord control.
In cases where it happens, such as Next hop change, it was debated at length
earlier in this list if it was proper to unsolicitedly advertise the changed
attributes.</span></font></span></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=MsoNormal><span class=EmailStyle16><font size=2 color=blue face=Arial><span
style='font-size:10.0pt;color:blue'>A better way would be for the egress to
withdraw the label. However&nbsp;the ingress will not issue a request unless it
is in Independent control. This anyway&nbsp;is a&nbsp;problem. My suggestin
would be - The ingress after sending a release can issue a fresh
request&nbsp;for the label even if its not in independent control if it still
supports label switching on the FEC. I feel This&nbsp;would be more cleaner .</span></font></span></p>

<p class=MsoNormal><span class=EmailStyle16><font size=2 color=red face=Arial><span
style='font-size:10.0pt;color:red'>[Ramia, Kannan Babu]&nbsp;&nbsp;How the
ingress will know that it need to request again or initate LSP establishment
once again for the same FEC (i mean here what criteria or conditions it checks
before it does this again..) because in some genuine cases if egress wants to
remove the LSP&nbsp;then it may lead to infinite looping.</span></font></span><font
size=2 color=red face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:red'><br>
</span></font><span class=EmailStyle16><font size=2 color=blue face=Arial><span
style='font-size:10.0pt;color:blue'>[Vijayanand C - CTD, Chennai.]&nbsp;This
kind of situation(&nbsp;retrying)&nbsp;will anyway apply in Independent
control( all nodes along the LSP may potentially retry). So&nbsp;how will you
solve the problem in that case ? &nbsp;What I am suggesting is if ordered
control is used the retry can be done only by the ingress. Any retry mechanism
would have some back off and stopping criteria associated with it implicitly.</span></font></span></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=MsoNormal><span class=EmailStyle16><font size=2 color=blue face=Arial><span
style='font-size:10.0pt;color:blue'>Vijay</span></font></span><span
class=EmailStyle16><font size=2 color=black face=Arial><span style='font-size:
10.0pt'>&nbsp;</span></font></span></p>

<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt;color:black'>&nbsp;</span></font></p>

</blockquote>

</blockquote>

</blockquote>

</blockquote>

</blockquote>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C25F16.EF9F9F10--


From owner-mpls@UU.NET  Wed Sep 18 09:30:34 2002
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 ESMTP id JAA12216
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 09:30:33 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngvu05810
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 13:32:17 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngvt28463;
	Wed, 18 Sep 2002 13:29:00 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngvt06785
	for mpls-outgoing; Wed, 18 Sep 2002 13:28:25 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQngvt06779
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 13:28: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 QQngvt21944
	for <mpls@UU.NET>; Wed, 18 Sep 2002 13:27:53 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngvt08123
	for <mpls@UU.NET>; Wed, 18 Sep 2002 13:27:52 GMT
Received: from celox-ma1-ems1.celoxnetworks.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: celox-ma1-imap1.celoxnetworks.com [12.40.60.233])
	id QQngvt08104
	for <mpls@UU.NET>; Wed, 18 Sep 2002 13:27:52 GMT
Received: by celox-ma1-ems1.celoxnetworks.com with Internet Mail Service (5.5.2653.19)
	id <RBC1GN05>; Wed, 18 Sep 2002 09:27:52 -0400
Message-ID: <1117F7D44159934FB116E36F4ABF221B0267EB0A@celox-ma1-ems1.celoxnetworks.com>
From: "Gray, Eric" <egray@celoxnetworks.com>
To: "'erosen@cisco.com'" <erosen@cisco.com>,
        "Ramia, Kannan Babu"
	 <kannan.babu.ramia@intel.com>
Cc: "MPLS (E-mail)" <mpls@UU.NET>
Subject: RE: Clarification on Handling a specific event in LDP 
Date: Wed, 18 Sep 2002 09:27:50 -0400
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,

	This did not slip between the cracks, it was pushed.

	:-)

Eric W. Gray
Systems Architect
Celox Networks, Inc.
egray@celoxnetworks.com
508 305 7214


> -----Original Message-----
> From: Eric Rosen [mailto:erosen@cisco.com]
> Sent: Wednesday, September 18, 2002 8:52 AM
> To: Ramia, Kannan Babu
> Cc: MPLS (E-mail)
> Subject: Re: Clarification on Handling a specific event in LDP
> 
> 
> I think this case slipped through the cracks, because the use of LDP in
> DoD/Ordered mode was envisioned for use in networks consisting of ATM-
> LSRs, which of course don't do PHP.
> 
> Is this a practical problem for you, or simply a theoretical one?


From owner-mpls@UU.NET  Wed Sep 18 09:35:40 2002
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 ESMTP id JAA12451
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 09:35:39 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngvu15156
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 13:37:25 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngvu14666;
	Wed, 18 Sep 2002 13:37:15 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngvu07387
	for mpls-outgoing; Wed, 18 Sep 2002 13:36:48 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQngvu07382
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 13:36:47 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 QQngvu00223
	for <mpls@UU.NET>; Wed, 18 Sep 2002 13:35:23 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngvu27729
	for <mpls@UU.NET>; Wed, 18 Sep 2002 13:35:22 GMT
Received: from celox-ma1-ems1.celoxnetworks.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: celox-ma1-imap1.celoxnetworks.com [12.40.60.233])
	id QQngvu27723
	for <mpls@UU.NET>; Wed, 18 Sep 2002 13:35:22 GMT
Received: by celox-ma1-ems1.celoxnetworks.com with Internet Mail Service (5.5.2653.19)
	id <RBC1G3BD>; Wed, 18 Sep 2002 09:35:22 -0400
Message-ID: <1117F7D44159934FB116E36F4ABF221B0267EB0B@celox-ma1-ems1.celoxnetworks.com>
From: "Gray, Eric" <egray@celoxnetworks.com>
To: "'neil.2.harrison@bt.com'" <neil.2.harrison@bt.com>,
        vijayc@ctd.hcltech.com, kannan.babu.ramia@intel.com
Cc: mpls@UU.NET
Subject: RE: Clarification on Handling a specific event in LDP
Date: Wed, 18 Sep 2002 09:35:16 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C25F18.395A53B0"
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_01C25F18.395A53B0
Content-Type: text/plain

This would be a great topic for an RFC next April...

 

Eric W. Gray

Systems Architect

Celox Networks, Inc.

egray@celoxnetworks.com

508 305 7214

 

-----Original Message-----
From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com] 
Sent: Wednesday, September 18, 2002 5:59 AM
To: vijayc@ctd.hcltech.com; kannan.babu.ramia@intel.com
Cc: mpls@UU.NET
Subject: RE: Clarification on Handling a specific event in LDP

 

2 questions....please see below.  regards Neil

-----Original Message-----
From: Vijayanand C - CTD, Chennai. [mailto:vijayc@ctd.hcltech.com]
Sent: 18 September 2002 10:19
To: Ramia, Kannan Babu
Cc: mpls@UU.NET
Subject: RE: Clarification on Handling a specific event in LDP

Again you are overriding the Dod Ord control by using a label map along with
a withdraw whereby  it becomes an unsolicited mapping.

Apart from the Question of syntactical correctness of sending an unsolicited
label map there is another problem.

 The domain in configured for Dod Ord. THis may be due to constraints in the
switches to install labels. For example, in GMPLS, the set of desired labels
is sent along with the request indicating the range of labels the upstream
can switch onto. Hence the Dod Ord control has significance in such
scenarios' and overriding it may cause confusion. 

NH=> How does PHP work with GMPLS? 

 

The issue of change in next hop for an FEC right at the egress( which is
usually egress for routing domain) is a very rare situation and I think it
does nt warrant drastic changes to the semantics and operation of LDP 

NH=> If you stopped using PHP would this problem not 'go away'?

<snipped to end NH>



 


------_=_NextPart_001_01C25F18.395A53B0
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">


<meta name=Generator content="Microsoft Word 10 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"Comic Sans MS";
	panose-1:3 15 7 2 3 3 2 2 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle16
	{font-family:Arial;
	color:black;}
span.EmailStyle19
	{font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>This would be a great topic for an RFC
next April...</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<div>

<p class=MsoAutoSig><font size=2 color=navy face="Times New Roman"><span
style='font-size:10.0pt;color:navy'>Eric W. Gray</span></font></p>

<p class=MsoAutoSig><font size=2 color=navy face="Times New Roman"><span
style='font-size:10.0pt;color:navy'>Systems Architect</span></font></p>

<p class=MsoAutoSig><font size=2 color=navy face="Times New Roman"><span
style='font-size:10.0pt;color:navy'>Celox Networks, Inc.</span></font></p>

<p class=MsoAutoSig><font size=2 color=navy face="Times New Roman"><span
style='font-size:10.0pt;color:navy'>egray@celoxnetworks.com</span></font></p>

<p class=MsoPlainText><font size=2 color=navy face="Courier New"><span
style='font-size:10.0pt;color:navy'>508 305 7214</span></font></p>

</div>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>

<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma'>-----Original Message-----<br>
<b><span style='font-weight:bold'>From:</span></b> neil.2.harrison@bt.com
[mailto:neil.2.harrison@bt.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, September 18,
2002 5:59 AM<br>
<b><span style='font-weight:bold'>To:</span></b> vijayc@ctd.hcltech.com;
kannan.babu.ramia@intel.com<br>
<b><span style='font-weight:bold'>Cc:</span></b> mpls@UU.NET<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: Clarification on
Handling a specific event in LDP</span></font></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

<div>

<p class=MsoNormal><font size=2 color=blue face="Comic Sans MS"><span
style='font-size:10.0pt;font-family:"Comic Sans MS";color:blue'>2&nbsp;questions....please
see below.&nbsp; regards Neil</span></font></p>

</div>

<blockquote style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>

<p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'>-----Original Message-----<br>
<b><span style='font-weight:bold'>From:</span></b> Vijayanand C - CTD, Chennai.
[mailto:vijayc@ctd.hcltech.com]<br>
<b><span style='font-weight:bold'>Sent:</span></b> 18 September 2002 10:19<br>
<b><span style='font-weight:bold'>To:</span></b> Ramia, Kannan Babu<br>
<b><span style='font-weight:bold'>Cc:</span></b> mpls@UU.NET<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: Clarification on
Handling a specific event in LDP</span></font></p>

<div>

<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Again you are overriding the Dod Ord
control by using a label map along with a withdraw whereby&nbsp; it becomes an
unsolicited mapping.</span></font></p>

</div>

<div>

<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>Apart from the Question of syntactical
correctness of sending an unsolicited label map there is another problem.</span></font></p>

</div>

<div>

<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>&nbsp;The domain in configured for Dod
Ord. THis may be due to constraints in the switches to install labels. For
example, in GMPLS, the set of desired labels is sent along with the request
indicating the range of labels the upstream can switch onto. Hence the Dod Ord
control has significance in such scenarios' and overriding it may cause
confusion.</span></font><font size=2 color=blue face="Comic Sans MS"><span
style='font-size:10.0pt;font-family:"Comic Sans MS";color:blue'>&nbsp;</span></font></p>

</div>

<div>

<p class=MsoNormal><font size=2 color=purple face="Comic Sans MS"><span
style='font-size:10.0pt;font-family:"Comic Sans MS";color:purple'>NH=&gt; How
does PHP work with GMPLS?&nbsp;</span></font></p>

</div>

<div>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

</div>

<div>

<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>The issue of change in next hop for an FEC
right at the egress( which is usually egress for routing domain)&nbsp;is a very
rare situation and I think it does nt warrant drastic changes to the semantics
and operation of LDP</span></font><font size=2 color=blue face="Comic Sans MS"><span
style='font-size:10.0pt;font-family:"Comic Sans MS";color:blue'>&nbsp;</span></font></p>

</div>

<div>

<p class=MsoNormal><font size=2 color=purple face="Comic Sans MS"><span
style='font-size:10.0pt;font-family:"Comic Sans MS";color:purple'>NH=&gt;&nbsp;If
you stopped using PHP would this problem not 'go away'?</span></font></p>

</div>

<div>

<p class=MsoNormal><font size=2 color=purple face="Comic Sans MS"><span
style='font-size:10.0pt;font-family:"Comic Sans MS";color:purple'>&lt;snipped
to end NH&gt;</span></font></p>

</div>

<blockquote style='margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>

<blockquote style='margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>

<blockquote style='margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>

<blockquote style='margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>

<blockquote style='margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>

<p class=MsoNormal></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

</blockquote>

</blockquote>

</blockquote>

</blockquote>

</blockquote>

</blockquote>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C25F18.395A53B0--


From owner-mpls@UU.NET  Wed Sep 18 10:08:25 2002
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 ESMTP id KAA14341
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 10:08:25 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngvw14095
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 14:10:08 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngvw13685;
	Wed, 18 Sep 2002 14:09:58 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngvw25494
	for mpls-outgoing; Wed, 18 Sep 2002 14:09:29 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQngvw25463
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 14:09: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 QQngvw16875
	for <mpls@uu.net>; Wed, 18 Sep 2002 14:08:32 GMT
From: nagabhushana.ramaswamy@wipro.com
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngvw12486
	for <mpls@uu.net>; Wed, 18 Sep 2002 14:08:32 GMT
Received: from wiproecmx1.wipro.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: wiproecmx1.wipro.com [164.164.31.5])
	id QQngvw12464
	for <mpls@uu.net>; Wed, 18 Sep 2002 14:08:28 GMT
Received: from m2vwall5.wipro.com (m2vwall5.wipro.com [10.115.50.5])
	by wiproecmx1.wipro.com (8.11.3/8.11.3) with SMTP id g8IE2v103117
	for <mpls@uu.net>; Wed, 18 Sep 2002 19:32:59 +0530 (IST)
Received: from blr-m1-bh2.wipro.com ([10.115.50.92]) by
          ace.mail.wipro.com (Netscape Messaging Server 4.15) with ESMTP
          id H2N0LU00.P3Y for <mpls@uu.net>; Wed, 18 Sep 2002 19:38:18 +0530 
Received: from blr-k1-msg.wipro.com ([10.117.50.99]) by blr-m1-bh2.wipro.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 18 Sep 2002 19:38:17 +0530
Received: from bhushan.wipro.com ([10.117.3.144]) by blr-k1-msg.wipro.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 18 Sep 2002 19:38:17 +0530
Date: Wed, 18 Sep 2002 23:52:02 +0400 (RET)
X-X-Sender: <bhushanr@boochi>
Reply-To: <nagabhushana.ramaswamy@wipro.com>
To: <mpls@UU.NET>
Subject: mailing list admin??
Message-ID: <Pine.LNX.4.31.0209182349460.6988-100000@boochi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-OriginalArrivalTime: 18 Sep 2002 14:08:17.0737 (UTC) FILETIME=[D635D390:01C25F1C]
Sender: owner-mpls@UU.NET
Precedence: bulk


Hi,
  Can I know at address can I contact the mailing list admin for some list
management problems?
I looked at a few places, but couldn't trace. Sorry for mailing to the
list.

regrads
Bhushana



From owner-mpls@UU.NET  Wed Sep 18 11:28:16 2002
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 ESMTP id LAA17753
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 11:28:15 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwc10788
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 15:30:00 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngwb10375;
	Wed, 18 Sep 2002 15:29:49 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngwb17468
	for mpls-outgoing; Wed, 18 Sep 2002 15:29:28 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQngwb17455
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 15:29: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 QQngwb03429
	for <mpls@UU.NET>; Wed, 18 Sep 2002 15:26:33 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwb07742
	for <mpls@UU.NET>; Wed, 18 Sep 2002 15:26:33 GMT
Received: from atlntex01.movaz.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: exchange.movaz.com [65.205.166.141])
	id QQngwb07731
	for <mpls@UU.NET>; Wed, 18 Sep 2002 15:26:32 GMT
Received: from BLIULAPTOP ([172.16.24.104]) by atlntex01.movaz.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 18 Sep 2002 11:26:32 -0400
Message-ID: <003c01c25f27$c47265f0$681810ac@movaz.com>
From: "Adrian Farrel" <afarrel@movaz.com>
To: "'mpls@uu.net'" <mpls@UU.NET>
Subject: draft-ietf-mpls-ldp-ft-05.txt
Date: Wed, 18 Sep 2002 11:26:32 -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: 18 Sep 2002 15:26:32.0411 (UTC) FILETIME=[C4743AB0:01C25F27]
Sender: owner-mpls@UU.NET
Precedence: bulk

All,

draft-ietf-mpls-ldp-ft-05.txt has been posted.

This contains editorial changes from WG chair review.
There is no functional change.

In summary the changes are...

- In section 7.1 the FT Session TLV is called "FT Session".
- Same comment for FT Protection and FT Cork in section 7.2
- Section 4 bullet 2, indicate the use of the R bit
- In "Conventions and terminology" explain the use of "bit" and "flag"
- Make LDP Restart a normative reference
- Make CR-LDP an informational reference
- Table in 8.2 show {A=1, L=1} is invalid
- Significantly reduce the references to CR-LDP
- Remove authors from front page (add section 2 to highlight
  existence of other authors)
- Expand acronyms in abstract
- Remove references in abstract and use explicit RFC names
- Section 3 make 1:n "one-to-many"
- 3.1, 3.2 clarify text
- Move 2026 and 2119 to be normative references
- Add section 4.8 to describe tunneling
- fix typos
- correct LSR to "Label Switching Router"

Adrian





From owner-mpls@UU.NET  Wed Sep 18 11:57:38 2002
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 ESMTP id LAA18750
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 11:57:38 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwd15326
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 15:59:22 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngwd15024;
	Wed, 18 Sep 2002 15:59:15 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngwd19073
	for mpls-outgoing; Wed, 18 Sep 2002 15:58:47 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQngwd19067
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 15:58: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 QQngwd26390
	for <mpls@UU.NET>; Wed, 18 Sep 2002 15:56:25 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwd18354
	for <mpls@UU.NET>; Wed, 18 Sep 2002 15:56: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 QQngwd18344
	for <mpls@UU.NET>; Wed, 18 Sep 2002 15:56: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 LAA26319
	for <mpls@UU.NET>; Wed, 18 Sep 2002 11:56: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 LAA17435
	for <mpls@UU.NET>; Wed, 18 Sep 2002 11:56:22 -0400 (EDT)
Message-ID: <3D88A225.F6A8B3FE@marconi.com>
Date: Wed, 18 Sep 2002 11:56:21 -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 (E-mail)" <mpls@UU.NET>
Subject: Re: Clarification on Handling a specific event in LDP
References: <200209181252.g8ICqHKB010068@sj-msg-core-1.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Eric Rosen wrote:
>
> Is this a practical problem for you, or simply a theoretical one?
>

It's an implementation detail for any implementor whose LSR gives out
NULL labels (either implicit or explicit).  Specifically, what should
the behavior be when a NULL label has been sent upstream, and a "real"
(non-NULL) label becomes available from the next hop (either through
a next hop change or through receipt of a Label Mapping or an Address
message)?  How is the behavior modified by the three major "knobs" of
LDP (DoD/Unsolicited, Ordered/Independent, Liberal/Conservative)?

RFC 3036 is silent on the matter, so I would assume that the behavior
is implementation-dependent, with the following possibilities (there
may be more, but these come to mind):

  (1)  Avoid the issue -- don't send NULL labels.  :-)

  (2)  Leave the NULL label in place; take no action.

  (3)  Withdraw the NULL label; readvertise using a non-NULL label
       only if the session supports Unsolicited advertisement.

  (4)  Withdraw the NULL label; readvertise using a non-NULL label
       regardless of the session's advertisement setting.

  (5)  Advertise using a non-NULL label, without withdrawing the
       NULL label.  The upstream peer *might* realize what you are
       trying to do...

It seems to me that any of these behaviors should be allowed; the
upstream peer should not interpret any of these behaviors as a
fatal error.  Additionally, it seems evident that any of these
behaviors is "acceptable" -- the data flow in question should be
correctly forwarded regardless of which behavior is chosen.

    Jack


From owner-mpls@UU.NET  Wed Sep 18 12:49:30 2002
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 ESMTP id MAA20856
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 12:49:30 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwh18802
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 16:51:15 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngwh18502;
	Wed, 18 Sep 2002 16:51:05 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngwh08962
	for mpls-outgoing; Wed, 18 Sep 2002 16:50:48 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQngwh08952
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 16:50: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 QQngwh13831
	for <mpls@uu.net>; Wed, 18 Sep 2002 16:50:04 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwh27958
	for <mpls@uu.net>; Wed, 18 Sep 2002 16:50:03 GMT
Received: from funnel.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQngwh27938
	for <mpls@uu.net>; Wed, 18 Sep 2002 16:50:03 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id MAA27317 for <mpls@uu.net>; Wed, 18 Sep 2002 12:50:02 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8IGo2v25926 for mpls@uu.net; Wed, 18 Sep 2002 12:50:02 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQngwh08885
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 16:49: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 QQngwh20229
	for <mpls@UU.NET>; Wed, 18 Sep 2002 16:48:21 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwh27017
	for <mpls@UU.NET>; Wed, 18 Sep 2002 16:48:20 GMT
Received: from pilgrim.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: pilgrim.cisco.com [161.44.168.94])
	id QQngwh27011
	for <mpls@UU.NET>; Wed, 18 Sep 2002 16:48:20 GMT
Received: from tappan-w2k.cisco.com (tappan-frame1.cisco.com [10.83.99.42])
	by pilgrim.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id MAA14699;
	Wed, 18 Sep 2002 12:48:18 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020918124106.021b0ab0@pilgrim.cisco.com>
X-Sender: tappan@pilgrim.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 18 Sep 2002 12:48:15 -0400
To: Jack Brennen <John.Brennen@marconi.com>
From: Dan Tappan <tappan@cisco.com>
Subject: Re: Clarification on Handling a specific event in LDP
Cc: "MPLS (E-mail)" <mpls@UU.NET>
In-Reply-To: <3D88A225.F6A8B3FE@marconi.com>
References: <200209181252.g8ICqHKB010068@sj-msg-core-1.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk

At 11:56 AM 9/18/2002 -0400, Jack Brennen wrote:
>It seems to me that any of these behaviors should be allowed; the
>upstream peer should not interpret any of these behaviors as a
>fatal error.  Additionally, it seems evident that any of these
>behaviors is "acceptable" -- the data flow in question should be
>correctly forwarded regardless of which behavior is chosen.

Actually, that point is arguable. In fact, in the case where the LSP in 
question didn't terminate at this LSR, i.e. where the FEC did not 
correspond to the LSR or to one of its connected interfaces, then 
advertising a NULL label at all will not produce correct forwarding 
behavior in the presence of a label stack.

So, the "correct" behavior is more like:

(1a) Advertise NULL labels only for terminating LSPs. For non-terminating 
LSPs, always advertise a non-NULL label even if no label has been received 
from the next-hop.


>Eric Rosen wrote:
> >
> > Is this a practical problem for you, or simply a theoretical one?
> >
>
>It's an implementation detail for any implementor whose LSR gives out
>NULL labels (either implicit or explicit).  Specifically, what should
>the behavior be when a NULL label has been sent upstream, and a "real"
>(non-NULL) label becomes available from the next hop (either through
>a next hop change or through receipt of a Label Mapping or an Address
>message)?  How is the behavior modified by the three major "knobs" of
>LDP (DoD/Unsolicited, Ordered/Independent, Liberal/Conservative)?
>
>RFC 3036 is silent on the matter, so I would assume that the behavior
>is implementation-dependent, with the following possibilities (there
>may be more, but these come to mind):
>
>   (1)  Avoid the issue -- don't send NULL labels.  :-)
>
>   (2)  Leave the NULL label in place; take no action.
>
>   (3)  Withdraw the NULL label; readvertise using a non-NULL label
>        only if the session supports Unsolicited advertisement.
>
>   (4)  Withdraw the NULL label; readvertise using a non-NULL label
>        regardless of the session's advertisement setting.
>
>   (5)  Advertise using a non-NULL label, without withdrawing the
>        NULL label.  The upstream peer *might* realize what you are
>        trying to do...
>
>It seems to me that any of these behaviors should be allowed; the
>upstream peer should not interpret any of these behaviors as a
>fatal error.  Additionally, it seems evident that any of these
>behaviors is "acceptable" -- the data flow in question should be
>correctly forwarded regardless of which behavior is chosen.
>
>     Jack



From owner-mpls@UU.NET  Wed Sep 18 13:00:01 2002
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 ESMTP id NAA21272
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 13:00:00 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwi19467
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 17:01:45 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngwi19104;
	Wed, 18 Sep 2002 17:01:36 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngwi15114
	for mpls-outgoing; Wed, 18 Sep 2002 17:01:09 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQngwi14977
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 17:01: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 QQngwi04967
	for <mpls@UU.NET>; Wed, 18 Sep 2002 17:00:47 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwi18244
	for <mpls@UU.NET>; Wed, 18 Sep 2002 17:00:47 GMT
Received: from celox-ma1-ems1.celoxnetworks.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: celox-ma1-imap1.celoxnetworks.com [12.40.60.233])
	id QQngwi18234
	for <mpls@UU.NET>; Wed, 18 Sep 2002 17:00:47 GMT
Received: by celox-ma1-ems1.celoxnetworks.com with Internet Mail Service (5.5.2653.19)
	id <RBC1GPBB>; Wed, 18 Sep 2002 13:00:47 -0400
Message-ID: <1117F7D44159934FB116E36F4ABF221B0267EB0E@celox-ma1-ems1.celoxnetworks.com>
From: "Gray, Eric" <egray@celoxnetworks.com>
To: "'Dan Tappan'" <tappan@cisco.com>,
        Jack Brennen
	 <John.Brennen@marconi.com>
Cc: "MPLS (E-mail)" <mpls@UU.NET>
Subject: RE: Clarification on Handling a specific event in LDP
Date: Wed, 18 Sep 2002 13:00:43 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Dan,

	The distinction between terminating LSPs and
non-terminating LSPs is not always readily apparent.
One of the scenarios I pointed out (much) earlier
is the one in which LDP is 'turned on' in a router.
This has the effect of changing a routing peer into
both a routing and LDP peer.  It also changes LSPs
that previously terminated on surrounding routing
peers into non-terminating LSPs. 

Eric W. Gray
Systems Architect
Celox Networks, Inc.
egray@celoxnetworks.com
508 305 7214


> -----Original Message-----
> From: Dan Tappan [mailto:tappan@cisco.com]
> Sent: Wednesday, September 18, 2002 12:48 PM
> To: Jack Brennen
> Cc: MPLS (E-mail)
> Subject: Re: Clarification on Handling a specific event in LDP
> 
> At 11:56 AM 9/18/2002 -0400, Jack Brennen wrote:
> >It seems to me that any of these behaviors should be allowed; the
> >upstream peer should not interpret any of these behaviors as a
> >fatal error.  Additionally, it seems evident that any of these
> >behaviors is "acceptable" -- the data flow in question should be
> >correctly forwarded regardless of which behavior is chosen.
> 
> Actually, that point is arguable. In fact, in the case where the LSP in
> question didn't terminate at this LSR, i.e. where the FEC did not
> correspond to the LSR or to one of its connected interfaces, then
> advertising a NULL label at all will not produce correct forwarding
> behavior in the presence of a label stack.
> 
> So, the "correct" behavior is more like:
> 
> (1a) Advertise NULL labels only for terminating LSPs. For non-terminating
> LSPs, always advertise a non-NULL label even if no label has been received
> from the next-hop.
> 
> 
> >Eric Rosen wrote:
> > >
> > > Is this a practical problem for you, or simply a theoretical one?
> > >
> >
> >It's an implementation detail for any implementor whose LSR gives out
> >NULL labels (either implicit or explicit).  Specifically, what should
> >the behavior be when a NULL label has been sent upstream, and a "real"
> >(non-NULL) label becomes available from the next hop (either through
> >a next hop change or through receipt of a Label Mapping or an Address
> >message)?  How is the behavior modified by the three major "knobs" of
> >LDP (DoD/Unsolicited, Ordered/Independent, Liberal/Conservative)?
> >
> >RFC 3036 is silent on the matter, so I would assume that the behavior
> >is implementation-dependent, with the following possibilities (there
> >may be more, but these come to mind):
> >
> >   (1)  Avoid the issue -- don't send NULL labels.  :-)
> >
> >   (2)  Leave the NULL label in place; take no action.
> >
> >   (3)  Withdraw the NULL label; readvertise using a non-NULL label
> >        only if the session supports Unsolicited advertisement.
> >
> >   (4)  Withdraw the NULL label; readvertise using a non-NULL label
> >        regardless of the session's advertisement setting.
> >
> >   (5)  Advertise using a non-NULL label, without withdrawing the
> >        NULL label.  The upstream peer *might* realize what you are
> >        trying to do...
> >
> >It seems to me that any of these behaviors should be allowed; the
> >upstream peer should not interpret any of these behaviors as a
> >fatal error.  Additionally, it seems evident that any of these
> >behaviors is "acceptable" -- the data flow in question should be
> >correctly forwarded regardless of which behavior is chosen.
> >
> >     Jack


From owner-mpls@UU.NET  Wed Sep 18 13:41:06 2002
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 ESMTP id NAA23128
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 13:41:05 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwk29172
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 17:42:51 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngwk28766;
	Wed, 18 Sep 2002 17:42:41 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngwk29163
	for mpls-outgoing; Wed, 18 Sep 2002 17:42:27 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQngwk29158
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 17:42:24 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 QQngwk05654
	for <mpls@UU.NET>; Wed, 18 Sep 2002 17:42:15 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwk02951
	for <mpls@UU.NET>; Wed, 18 Sep 2002 17:42:15 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 QQngwk02939
	for <mpls@UU.NET>; Wed, 18 Sep 2002 17:42:14 GMT
Received: from cisco.com (erosen-u10.cisco.com [161.44.134.50])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8IHgB1X015572;
	Wed, 18 Sep 2002 10:42:11 -0700 (PDT)
Message-Id: <200209181742.g8IHgB1X015572@sj-msg-core-1.cisco.com>
To: Jack Brennen <John.Brennen@marconi.com>
cc: "MPLS (E-mail)" <mpls@UU.NET>
Subject: Re: Clarification on Handling a specific event in LDP 
In-reply-to: Your message of Wed, 18 Sep 2002 11:56:21 -0400.
             <3D88A225.F6A8B3FE@marconi.com> 
Reply-To: erosen@cisco.com
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.2
 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Wed, 18 Sep 2002 13:42:11 -0400
From: Eric Rosen <erosen@cisco.com>
Sender: owner-mpls@UU.NET
Precedence: bulk

Jack> It's an implementation detail for  any implementor whose LSR gives out
Jack> NULL labels 

No, it's only  an issue if the  LSR gives out NULL labels  on sessions which
are  running in  ordered DoD  mode.   If there  aren't any  such LSRs,  then
there's no problem in practice.  (Even  if the are such LSRs, it's still not
clear that there's much of a problem in practice.)

Jack> (1) Avoid the issue -- don't send NULL labels.  :-)

That works, but may have some costs.

Jack> (2) Leave the NULL label in place; take no action. 

This doesn't work, as Dan points out.

Jack> (3)  Withdraw the NULL label; readvertise using a non-NULL label
Jack>      only if the session supports Unsolicited advertisement. 

This isn't the case we're talking about.

Jack> (4)  Withdraw the NULL label; readvertise using a non-NULL label
Jack>      regardless of the session's advertisement setting. 

This will probably upset the peer.

Jack> (5)  Advertise using a non-NULL label, without withdrawing the
Jack>      NULL label.  The upstream peer *might* realize what you are
Jack>      trying to do...

This will probably upset the peer. 

Once you withdraw a label, you have to wait for the upstream peer to request
a new  label.  The upstream peer  could probably get away  with requesting a
new  label immediately,  not percolating  the withdraw  upstream  unless the
new  request is  refused.  Or the  upstream  peer could  just percolate  the
withdraws upstream,  in which  case the ingress  would have to  reinitiate a
request.  I  don't  really see  what  else  could  be done  without  causing
interoperability problems. 


From owner-mpls@UU.NET  Wed Sep 18 13:47:44 2002
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 ESMTP id NAA23402
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 13:47:43 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwl09635
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 17:49:28 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngwl09303;
	Wed, 18 Sep 2002 17:49:17 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngwl29972
	for mpls-outgoing; Wed, 18 Sep 2002 17:49:03 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQngwl29962
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 17:48:52 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 QQngwl23423
	for <mpls@uu.net>; Wed, 18 Sep 2002 17:48:09 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwl08212
	for <mpls@uu.net>; Wed, 18 Sep 2002 17:48:09 GMT
Received: from funnel.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQngwl08208
	for <mpls@uu.net>; Wed, 18 Sep 2002 17:48:08 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id NAA04830 for <mpls@uu.net>; Wed, 18 Sep 2002 13:48:08 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8IHm8203048 for mpls@uu.net; Wed, 18 Sep 2002 13:48:08 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQngwk29262
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 17:44:17 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 QQngwk24704
	for <mpls@UU.NET>; Wed, 18 Sep 2002 17:43:20 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwk03627
	for <mpls@UU.NET>; Wed, 18 Sep 2002 17:43:20 GMT
Received: from pilgrim.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: pilgrim.cisco.com [161.44.168.94])
	id QQngwk03621
	for <mpls@UU.NET>; Wed, 18 Sep 2002 17:43:19 GMT
Received: from tappan-w2k.cisco.com (tappan-frame1.cisco.com [10.83.99.42])
	by pilgrim.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id NAA20023;
	Wed, 18 Sep 2002 13:43:17 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020918130719.021b6da0@pilgrim.cisco.com>
X-Sender: tappan@pilgrim.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 18 Sep 2002 13:43:14 -0400
To: "Gray, Eric" <egray@celoxnetworks.com>
From: Dan Tappan <tappan@cisco.com>
Subject: RE: Clarification on Handling a specific event in LDP
Cc: Jack Brennen <John.Brennen@marconi.com>, "MPLS (E-mail)" <mpls@UU.NET>
In-Reply-To: <1117F7D44159934FB116E36F4ABF221B0267EB0E@celox-ma1-ems1.ce
 loxnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk

At 01:00 PM 9/18/2002 -0400, Gray, Eric wrote:
>Dan,
>
>         The distinction between terminating LSPs and
>non-terminating LSPs is not always readily apparent.
>One of the scenarios I pointed out (much) earlier
>is the one in which LDP is 'turned on' in a router.
>This has the effect of changing a routing peer into
>both a routing and LDP peer.  It also changes LSPs
>that previously terminated on surrounding routing
>peers into non-terminating LSPs.

You're missing the point.

If the FEC in question corresponds to the LSR advertising the label, then 
it is appropriate to advertise a NULL label.

If the FEC does _not_ correspond to this LSR, then advertising a NULL label 
will cause the LSP to terminate prematurely. So, if a packet contains a 
label stack the underlying label will be exposed prematurely, causing it to 
be interpreted by an LSR other than the one which advertised it.

With your example, given

  LSR_A --- LSR_B

----LSPx----->

Where the path for LSPx goes through LSR_B. Turning on LDP in LSR_B does 
not change the LSP from "terminating" to "non-terminating" as far as LSR_A 
is concerned, in either case the next hop for the LSP goes through LSR_B. 
What it changes is whether or not LSR_A has received a valid label from the 
next hop. So, LSR_A can always advertise a non-NULL label, but it may 
change the forwarding behavior for that label depending on what it learns 
from LSR_B. It may also change whether LSR_A is the "egress" for LSPx, and 
so may affect whether or not LSR_A even advertises a label at all if in 
Ordered mode, but that is a separate issue from whether or not the 
advertised label should be null.

If the complete corner case we're worrying about is:
- DoD
- Ordered
- LSR_A changes from Egress to non-egress for an LSP

Then the correct behavior was:
- advertise a non-null label while egress (because the LSP did not terminate)
- if LSR_B starts to run LDP, meaning LSR_A realizes it is no longer 
egress, then withdraw the label. Presumably the upstream LSR(s) should 
re-request the mapping (see the last sentence in the "Summary" of RFC3036 
A.1.5), in which case the existing state machine applies.

> > -----Original Message-----
> > From: Dan Tappan [mailto:tappan@cisco.com]
> > Sent: Wednesday, September 18, 2002 12:48 PM
> > To: Jack Brennen
> > Cc: MPLS (E-mail)
> > Subject: Re: Clarification on Handling a specific event in LDP
> >
> > At 11:56 AM 9/18/2002 -0400, Jack Brennen wrote:
> > >It seems to me that any of these behaviors should be allowed; the
> > >upstream peer should not interpret any of these behaviors as a
> > >fatal error.  Additionally, it seems evident that any of these
> > >behaviors is "acceptable" -- the data flow in question should be
> > >correctly forwarded regardless of which behavior is chosen.
> >
> > Actually, that point is arguable. In fact, in the case where the LSP in
> > question didn't terminate at this LSR, i.e. where the FEC did not
> > correspond to the LSR or to one of its connected interfaces, then
> > advertising a NULL label at all will not produce correct forwarding
> > behavior in the presence of a label stack.
> >
> > So, the "correct" behavior is more like:
> >
> > (1a) Advertise NULL labels only for terminating LSPs. For non-terminating
> > LSPs, always advertise a non-NULL label even if no label has been received
> > from the next-hop.
> >
> >
> > >Eric Rosen wrote:
> > > >
> > > > Is this a practical problem for you, or simply a theoretical one?
> > > >
> > >
> > >It's an implementation detail for any implementor whose LSR gives out
> > >NULL labels (either implicit or explicit).  Specifically, what should
> > >the behavior be when a NULL label has been sent upstream, and a "real"
> > >(non-NULL) label becomes available from the next hop (either through
> > >a next hop change or through receipt of a Label Mapping or an Address
> > >message)?  How is the behavior modified by the three major "knobs" of
> > >LDP (DoD/Unsolicited, Ordered/Independent, Liberal/Conservative)?
> > >
> > >RFC 3036 is silent on the matter, so I would assume that the behavior
> > >is implementation-dependent, with the following possibilities (there
> > >may be more, but these come to mind):
> > >
> > >   (1)  Avoid the issue -- don't send NULL labels.  :-)
> > >
> > >   (2)  Leave the NULL label in place; take no action.
> > >
> > >   (3)  Withdraw the NULL label; readvertise using a non-NULL label
> > >        only if the session supports Unsolicited advertisement.
> > >
> > >   (4)  Withdraw the NULL label; readvertise using a non-NULL label
> > >        regardless of the session's advertisement setting.
> > >
> > >   (5)  Advertise using a non-NULL label, without withdrawing the
> > >        NULL label.  The upstream peer *might* realize what you are
> > >        trying to do...
> > >
> > >It seems to me that any of these behaviors should be allowed; the
> > >upstream peer should not interpret any of these behaviors as a
> > >fatal error.  Additionally, it seems evident that any of these
> > >behaviors is "acceptable" -- the data flow in question should be
> > >correctly forwarded regardless of which behavior is chosen.
> > >
> > >     Jack



From owner-mpls@UU.NET  Wed Sep 18 14:00:52 2002
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 ESMTP id OAA23811
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 14:00:52 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwm28167
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 18:02:36 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngwm27865;
	Wed, 18 Sep 2002 18:02:27 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngwm10110
	for mpls-outgoing; Wed, 18 Sep 2002 18:01:59 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQngwm10105
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 18:01: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 QQngwm20829
	for <mpls@UU.NET>; Wed, 18 Sep 2002 18:01:29 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwm19164
	for <mpls@UU.NET>; Wed, 18 Sep 2002 18:01:29 GMT
Received: from celox-ma1-ems1.celoxnetworks.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: celox-ma1-imap1.celoxnetworks.com [12.40.60.233])
	id QQngwm19159
	for <mpls@UU.NET>; Wed, 18 Sep 2002 18:01:29 GMT
Received: by celox-ma1-ems1.celoxnetworks.com with Internet Mail Service (5.5.2653.19)
	id <RBC1GPLS>; Wed, 18 Sep 2002 14:01:29 -0400
Message-ID: <1117F7D44159934FB116E36F4ABF221B0267EB12@celox-ma1-ems1.celoxnetworks.com>
From: "Gray, Eric" <egray@celoxnetworks.com>
To: "'erosen@cisco.com'" <erosen@cisco.com>,
        Jack Brennen
	 <John.Brennen@marconi.com>
Cc: "MPLS (E-mail)" <mpls@UU.NET>
Subject: RE: Clarification on Handling a specific event in LDP 
Date: Wed, 18 Sep 2002 14:01:22 -0400
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,

	Please see below...

Eric W. Gray
Systems Architect
Celox Networks, Inc.
egray@celoxnetworks.com
508 305 7214


> ---

[snip]
Jack> (5)  Advertise using a non-NULL label, without withdrawing the
Jack>      NULL label.  The upstream peer *might* realize what you are
Jack>      trying to do...
> 
> This will probably upset the peer.

That depends on what you mean by "upset".  Assuming we do
not have to worry about the defective implementation case,
the worst that could happen is for the peer to decide that 
the session is compromised and reset it.  That would be BAD,
but it would also be very unusual.

Any reasonably robust implementation would simply release
the unsolicited label mapping if it does not know what else
to do with it.

> 
> Once you withdraw a label, you have to wait for the upstream 
> peer to request a new label.  The upstream peer could 
> probably get away  with requesting a new label immediately,  
> not percolating the withdraw upstream unless the new  
> request is refused.  Or the upstream peer could just percolate
> the withdraws upstream, in which case the ingress would have to  
> reinitiate a request.  I don't really see what else could be 
> done without causing interoperability problems.

This case does not have the LSR withdraw the label.  Even
if the LSR does withdraw the label after advertising a new
one (assuming it does not get a release for either of the
outstanding Label Mappings), by that time, the upstream 
LSR should have a replacement label and will not need to
either request one or withdraw corresponding labels from
upstream LSR peers.


From owner-mpls@UU.NET  Wed Sep 18 14:05:27 2002
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 ESMTP id OAA24011
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 14:05:26 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwm24953
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 18:07:11 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngwm24523;
	Wed, 18 Sep 2002 18:06:57 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngwm17070
	for mpls-outgoing; Wed, 18 Sep 2002 18:06:42 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQngwm17062
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 18:06:36 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 QQngwm05117
	for <mpls@uu.net>; Wed, 18 Sep 2002 18:06:07 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwm29303
	for <mpls@uu.net>; Wed, 18 Sep 2002 18:06:07 GMT
Received: from funnel.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQngwm29285
	for <mpls@uu.net>; Wed, 18 Sep 2002 18:06:07 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id OAA07366 for <mpls@uu.net>; Wed, 18 Sep 2002 14:06:02 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8II62g06015 for mpls@uu.net; Wed, 18 Sep 2002 14:06:02 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQngwm07432
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 18:01: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 QQngwm18228
	for <mpls@UU.NET>; Wed, 18 Sep 2002 18:00:14 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwm25494
	for <mpls@UU.NET>; Wed, 18 Sep 2002 18:00:13 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 QQngwm25485
	for <mpls@UU.NET>; Wed, 18 Sep 2002 18:00:13 GMT
Received: from bucket.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8II0QB3010137;
	Wed, 18 Sep 2002 14:00:26 -0400 (EDT)
Received: from tnadeau-w2k.cisco.com (che-vpn1-63.cisco.com [10.86.240.63])
	by bucket.cisco.com (Mirapoint)
	with ESMTP id ABQ41636;
	Wed, 18 Sep 2002 14:00:08 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020918135848.0175d2f0@bucket.cisco.com>
X-Sender: tnadeau@bucket.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 18 Sep 2002 14:00:08 -0400
To: "Gray, Eric" <egray@celoxnetworks.com>
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: RE: Clarification on Handling a specific event in LDP
Cc: "'Dan Tappan'" <tappan@cisco.com>, Jack Brennen <John.Brennen@marconi.com>,
        "MPLS (E-mail)" <mpls@UU.NET>
In-Reply-To: <1117F7D44159934FB116E36F4ABF221B0267EB0E@celox-ma1-ems1.ce
 loxnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mpls@UU.NET
Precedence: bulk

At 01:00 PM 9/18/2002 -0400, Gray, Eric wrote:
>Dan,
>
>         The distinction between terminating LSPs and
>non-terminating LSPs is not always readily apparent.
>One of the scenarios I pointed out (much) earlier
>is the one in which LDP is 'turned on' in a router.
>This has the effect of changing a routing peer into
>both a routing and LDP peer.  It also changes LSPs
>that previously terminated on surrounding routing
>peers into non-terminating LSPs.

         Shouldn't the labels bound to these LSPs be withdrawn
and be re-requested?

         --Tom



>Eric W. Gray
>Systems Architect
>Celox Networks, Inc.
>egray@celoxnetworks.com
>508 305 7214
>
>
> > -----Original Message-----
> > From: Dan Tappan [mailto:tappan@cisco.com]
> > Sent: Wednesday, September 18, 2002 12:48 PM
> > To: Jack Brennen
> > Cc: MPLS (E-mail)
> > Subject: Re: Clarification on Handling a specific event in LDP
> >
> > At 11:56 AM 9/18/2002 -0400, Jack Brennen wrote:
> > >It seems to me that any of these behaviors should be allowed; the
> > >upstream peer should not interpret any of these behaviors as a
> > >fatal error.  Additionally, it seems evident that any of these
> > >behaviors is "acceptable" -- the data flow in question should be
> > >correctly forwarded regardless of which behavior is chosen.
> >
> > Actually, that point is arguable. In fact, in the case where the LSP in
> > question didn't terminate at this LSR, i.e. where the FEC did not
> > correspond to the LSR or to one of its connected interfaces, then
> > advertising a NULL label at all will not produce correct forwarding
> > behavior in the presence of a label stack.
> >
> > So, the "correct" behavior is more like:
> >
> > (1a) Advertise NULL labels only for terminating LSPs. For non-terminating
> > LSPs, always advertise a non-NULL label even if no label has been received
> > from the next-hop.
> >
> >
> > >Eric Rosen wrote:
> > > >
> > > > Is this a practical problem for you, or simply a theoretical one?
> > > >
> > >
> > >It's an implementation detail for any implementor whose LSR gives out
> > >NULL labels (either implicit or explicit).  Specifically, what should
> > >the behavior be when a NULL label has been sent upstream, and a "real"
> > >(non-NULL) label becomes available from the next hop (either through
> > >a next hop change or through receipt of a Label Mapping or an Address
> > >message)?  How is the behavior modified by the three major "knobs" of
> > >LDP (DoD/Unsolicited, Ordered/Independent, Liberal/Conservative)?
> > >
> > >RFC 3036 is silent on the matter, so I would assume that the behavior
> > >is implementation-dependent, with the following possibilities (there
> > >may be more, but these come to mind):
> > >
> > >   (1)  Avoid the issue -- don't send NULL labels.  :-)
> > >
> > >   (2)  Leave the NULL label in place; take no action.
> > >
> > >   (3)  Withdraw the NULL label; readvertise using a non-NULL label
> > >        only if the session supports Unsolicited advertisement.
> > >
> > >   (4)  Withdraw the NULL label; readvertise using a non-NULL label
> > >        regardless of the session's advertisement setting.
> > >
> > >   (5)  Advertise using a non-NULL label, without withdrawing the
> > >        NULL label.  The upstream peer *might* realize what you are
> > >        trying to do...
> > >
> > >It seems to me that any of these behaviors should be allowed; the
> > >upstream peer should not interpret any of these behaviors as a
> > >fatal error.  Additionally, it seems evident that any of these
> > >behaviors is "acceptable" -- the data flow in question should be
> > >correctly forwarded regardless of which behavior is chosen.
> > >
> > >     Jack



------------------------------------------------------------------------
Mathematics is the supreme nostalgia of our time. 



From owner-mpls@UU.NET  Wed Sep 18 14:30:13 2002
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 ESMTP id OAA24902
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 14:30:13 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwo00929
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 18:31:57 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngwo00623;
	Wed, 18 Sep 2002 18:31:49 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngwo20117
	for mpls-outgoing; Wed, 18 Sep 2002 18:31:24 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQngwo20004
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 18:31: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 QQngwn17423
	for <mpls@UU.NET>; Wed, 18 Sep 2002 18:28:50 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwn17087
	for <mpls@UU.NET>; Wed, 18 Sep 2002 18:28:49 GMT
Received: from celox-ma1-ems1.celoxnetworks.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: celox-ma1-imap1.celoxnetworks.com [12.40.60.233])
	id QQngwn17082
	for <mpls@UU.NET>; Wed, 18 Sep 2002 18:28:49 GMT
Received: by celox-ma1-ems1.celoxnetworks.com with Internet Mail Service (5.5.2653.19)
	id <RBC1GPPM>; Wed, 18 Sep 2002 14:28:49 -0400
Message-ID: <1117F7D44159934FB116E36F4ABF221B0267EB14@celox-ma1-ems1.celoxnetworks.com>
From: "Gray, Eric" <egray@celoxnetworks.com>
To: "'Dan Tappan'" <tappan@cisco.com>,
        "Gray, Eric"
	 <egray@celoxnetworks.com>
Cc: Jack Brennen <John.Brennen@marconi.com>, "MPLS (E-mail)" <mpls@UU.NET>
Subject: RE: Clarification on Handling a specific event in LDP
Date: Wed, 18 Sep 2002 14:28:49 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Dan,

	Please see below...

Eric W. Gray
Systems Architect
Celox Networks, Inc.
egray@celoxnetworks.com
508 305 7214


> -----Original Message-----
> From: Dan Tappan [mailto:tappan@cisco.com]
> Sent: Wednesday, September 18, 2002 1:43 PM
> To: Gray, Eric
> Cc: Jack Brennen; MPLS (E-mail)
> Subject: RE: Clarification on Handling a specific event in LDP
> 
> At 01:00 PM 9/18/2002 -0400, Gray, Eric wrote:
> >Dan,
> >
> >         The distinction between terminating LSPs and
> >non-terminating LSPs is not always readily apparent.
> >One of the scenarios I pointed out (much) earlier
> >is the one in which LDP is 'turned on' in a router.
> >This has the effect of changing a routing peer into
> >both a routing and LDP peer.  It also changes LSPs
> >that previously terminated on surrounding routing
> >peers into non-terminating LSPs.
> 
> You're missing the point.
> 
> If the FEC in question corresponds to the LSR advertising the label, then
> it is appropriate to advertise a NULL label.

I personally have no problem with this statement.  However, 
there are some implementers who will feel it is excessively 
restrictive.

While it is true that an LSR should not give out an implicit 
NULL label if it is not the terminating point for an LSP on 
which it may receive either labeled traffic or a mix of labeled 
and unlabeled traffic, there are many scenarios in which an LSR 
will be in a position to know that there are no other labels in 
the stack.  This is the case, for example, if it is currently 
the end point for an LSP on which it is getting IP packets that 
it is then forwarding as IP packets on some other interface.

But this is obvious.  What are you really getting at?

> 
> If the FEC does _not_ correspond to this LSR, then advertising a NULL
> label will cause the LSP to terminate prematurely.  So, if a packet 
> contains a label stack the underlying label will be exposed prematurely, 
> causing it to be interpreted by an LSR other than the one which 
> advertised it.

There is nothing implying the existence of a label stack in
this discussion.  The egress LSR is simply forwarding LSP
packets using IP and subsequently discovers that it could
start forwarding them using MPLS.  If there was a mixture
of IP and MPLS labeled traffic being received on the LSP,
the LSR was already presumably dealing with this.

> 
> With your example, given
> 
>   LSR_A --- LSR_B
> 
> ----LSPx----->
> 
> Where the path for LSPx goes through LSR_B. Turning on LDP in LSR_B does
> not change the LSP from "terminating" to "non-terminating" as far as LSR_A
> is concerned, in either case the next hop for the LSP goes through LSR_B.
> What it changes is whether or not LSR_A has received a valid label from
> the
> next hop. So, LSR_A can always advertise a non-NULL label, but it may
> change the forwarding behavior for that label depending on what it learns
> from LSR_B. It may also change whether LSR_A is the "egress" for LSPx, and
> so may affect whether or not LSR_A even advertises a label at all if in
> Ordered mode, but that is a separate issue from whether or not the
> advertised label should be null.

If you drop the fact that we are discussing DoD behavior
rather than DU behavior, I once had this same discussion 
with one of your colleagues at Cisco only with reversed
roles.  It is certainly arguable that the need to support
PHP is just is great in the DoD case as it is in the DU
case.  What may be a little harder to justify (I think
this was Eric Rosen's point earlier) is whether there is
as much need to support DoD as there is to support DU in 
any case where there is a need to support PHP.

Once you accept the fact that there is a legitimate need
to support PHP, then the restriction that it can only be
used when the LSP is for a FEC corresponding to the LSR
_is_ excessive.

> 
> If the complete corner case we're worrying about is:
> - DoD
> - Ordered
> - LSR_A changes from Egress to non-egress for an LSP
> 
> Then the correct behavior was:
> - advertise a non-null label while egress (because the LSP did not
> terminate)
> - if LSR_B starts to run LDP, meaning LSR_A realizes it is no longer
> egress, then withdraw the label. Presumably the upstream LSR(s) should
> re-request the mapping (see the last sentence in the "Summary" of RFC3036
> A.1.5), in which case the existing state machine applies.
> 
> > > -----Original Message-----
> > > From: Dan Tappan [mailto:tappan@cisco.com]
> > > Sent: Wednesday, September 18, 2002 12:48 PM
> > > To: Jack Brennen
> > > Cc: MPLS (E-mail)
> > > Subject: Re: Clarification on Handling a specific event in LDP
> > >
> > > At 11:56 AM 9/18/2002 -0400, Jack Brennen wrote:
> > > >It seems to me that any of these behaviors should be allowed; the
> > > >upstream peer should not interpret any of these behaviors as a
> > > >fatal error.  Additionally, it seems evident that any of these
> > > >behaviors is "acceptable" -- the data flow in question should be
> > > >correctly forwarded regardless of which behavior is chosen.
> > >
> > > Actually, that point is arguable. In fact, in the case where the LSP
> in
> > > question didn't terminate at this LSR, i.e. where the FEC did not
> > > correspond to the LSR or to one of its connected interfaces, then
> > > advertising a NULL label at all will not produce correct forwarding
> > > behavior in the presence of a label stack.
> > >
> > > So, the "correct" behavior is more like:
> > >
> > > (1a) Advertise NULL labels only for terminating LSPs. For non-
> terminating
> > > LSPs, always advertise a non-NULL label even if no label has been
> received
> > > from the next-hop.
> > >
> > >
> > > >Eric Rosen wrote:
> > > > >
> > > > > Is this a practical problem for you, or simply a theoretical one?
> > > > >
> > > >
> > > >It's an implementation detail for any implementor whose LSR gives out
> > > >NULL labels (either implicit or explicit).  Specifically, what should
> > > >the behavior be when a NULL label has been sent upstream, and a
> "real"
> > > >(non-NULL) label becomes available from the next hop (either through
> > > >a next hop change or through receipt of a Label Mapping or an Address
> > > >message)?  How is the behavior modified by the three major "knobs" of
> > > >LDP (DoD/Unsolicited, Ordered/Independent, Liberal/Conservative)?
> > > >
> > > >RFC 3036 is silent on the matter, so I would assume that the behavior
> > > >is implementation-dependent, with the following possibilities (there
> > > >may be more, but these come to mind):
> > > >
> > > >   (1)  Avoid the issue -- don't send NULL labels.  :-)
> > > >
> > > >   (2)  Leave the NULL label in place; take no action.
> > > >
> > > >   (3)  Withdraw the NULL label; readvertise using a non-NULL label
> > > >        only if the session supports Unsolicited advertisement.
> > > >
> > > >   (4)  Withdraw the NULL label; readvertise using a non-NULL label
> > > >        regardless of the session's advertisement setting.
> > > >
> > > >   (5)  Advertise using a non-NULL label, without withdrawing the
> > > >        NULL label.  The upstream peer *might* realize what you are
> > > >        trying to do...
> > > >
> > > >It seems to me that any of these behaviors should be allowed; the
> > > >upstream peer should not interpret any of these behaviors as a
> > > >fatal error.  Additionally, it seems evident that any of these
> > > >behaviors is "acceptable" -- the data flow in question should be
> > > >correctly forwarded regardless of which behavior is chosen.
> > > >
> > > >     Jack


From owner-mpls@UU.NET  Wed Sep 18 20:40:51 2002
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 ESMTP id UAA05297
	for <mpls-archive@lists.ietf.org>; Wed, 18 Sep 2002 20:40:51 -0400 (EDT)
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngwk03316;
	Wed, 18 Sep 2002 17:44:38 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngwk29210
	for mpls-outgoing; Wed, 18 Sep 2002 17:43:48 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQngwk29205
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 18 Sep 2002 17:43: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 QQngwk08646
	for <mpls@UU.NET>; Wed, 18 Sep 2002 17:43:39 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngwk02751
	for <mpls@UU.NET>; Wed, 18 Sep 2002 17:43:39 GMT
Received: from celox-ma1-ems1.celoxnetworks.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: celox-ma1-imap1.celoxnetworks.com [12.40.60.233])
	id QQngwk02743
	for <mpls@UU.NET>; Wed, 18 Sep 2002 17:43:39 GMT
Received: by celox-ma1-ems1.celoxnetworks.com with Internet Mail Service (5.5.2653.19)
	id <RBC1GP2M>; Wed, 18 Sep 2002 13:43:39 -0400
Message-ID: <1117F7D44159934FB116E36F4ABF221B0267EB10@celox-ma1-ems1.celoxnetworks.com>
From: "Gray, Eric" <egray@celoxnetworks.com>
To: "'Jack Brennen'" <John.Brennen@marconi.com>,
        "MPLS (E-mail)"
	 <mpls@UU.NET>
Subject: RE: Clarification on Handling a specific event in LDP
Date: Wed, 18 Sep 2002 13:43:32 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mpls@UU.NET
Precedence: bulk

Jack et al,

	Please see comments below...

Eric W. Gray
Systems Architect
Celox Networks, Inc.
egray@celoxnetworks.com
508 305 7214


> -----Original Message-----
> From: Jack Brennen [mailto:John.Brennen@marconi.com]
> Sent: Wednesday, September 18, 2002 11:56 AM
> To: MPLS (E-mail)
> Subject: Re: Clarification on Handling a specific event in LDP
> 
> Eric Rosen wrote:
> >
> > Is this a practical problem for you, or simply a theoretical one?
> >
> 
> It's an implementation detail for any implementor whose LSR gives out
> NULL labels (either implicit or explicit).  Specifically, what should
> the behavior be when a NULL label has been sent upstream, and a "real"
> (non-NULL) label becomes available from the next hop (either through
> a next hop change or through receipt of a Label Mapping or an Address
> message)?  How is the behavior modified by the three major "knobs" of
> LDP (DoD/Unsolicited, Ordered/Independent, Liberal/Conservative)?
> 
> RFC 3036 is silent on the matter, so I would assume that the behavior
> is implementation-dependent, with the following possibilities (there
> may be more, but these come to mind):
> 
>   (1)  Avoid the issue -- don't send NULL labels.  :-)

This is a rational approach, particularly when there is a next
hop that may become an LDP peer (even theoretically).  However
it is not an option for some implementations.

> 
>   (2)  Leave the NULL label in place; take no action.

This works for implementations that do not 'suffer' with
the overhead of providing LSP ingress.  Otherwise, it is
sub-optimal.

> 
>   (3)  Withdraw the NULL label; readvertise using a non-NULL label
>        only if the session supports Unsolicited advertisement.

In the DoD/Ordered control case - strictly interpreted - this 
is the implied behavior and would result in tearing down all 
affected LSPs to ingress and waiting for the ingress LSRs to 
start over for each LSP.  Because the local LSR should not be
in the business of trying to predict the distribution/control
modes of upstream LSRs (beyond the immediate peer), it should 
behave as if upstream LSRs are observing the same behavior as 
its immediate upstream LSR peer - both because this is one 
reasonable assumption and it is the worst case.  Using this 
assumption, the behavior of Withdrawing the Implicit NULL label 
(just to remove the growing ambiguity in this thread) should be 
considered sociopathic.

> 
>   (4)  Withdraw the NULL label; readvertise using a non-NULL label
>        regardless of the session's advertisement setting.

See response to 3 above.  This is slightly less pathological
in the sense that it is possible that LSPs will take less 
time to be re-established.  It is slightly more pathological
given the possibility that some implementations may simply
release any label they receive unsolicited - you still end
up waiting for the ingress LSRs to re-establish LSPs and you
also end up with a great deal more signaling.

> 
>   (5)  Advertise using a non-NULL label, without withdrawing the
>        NULL label.  The upstream peer *might* realize what you are
>        trying to do...

Indeed, and this behavior is harmless in the event that the
upstream peer does not.  I have previously referred to this 
as implied withdraw.  There are reasons why 'implied withdraw' 
may not work in general.  For example, how does this work if
more than one label has previously been given for the same
FEC?  However, in the case where the one and only previously 
advertised label was the implicit NULL label (which had zero
- or possibly negative semantic value), this behavior will
work nicely.

Moreover, if the upstream LSR does not know what to do with
the label, it will simply release it (potentially telling 
the local LSR not to bother trying this again) and subsequent
behavior is no worse than it would be otherwise.

The downstream LSR should do one other thing.  Because the 
upstream LSR may be 'conservatively' implemented, it may 
simply 'liberally' retain the new Label Mapping.  Hence, 
the local LSR must withdraw the implicit NULL label if
the upstream LSR does not release it within some period of 
time.

Note that - if you cruise through the appendices in RFC 3036
- you should find that things work out correctly when done
this way.

> 
> It seems to me that any of these behaviors should be allowed; the
> upstream peer should not interpret any of these behaviors as a
> fatal error.  Additionally, it seems evident that any of these
> behaviors is "acceptable" -- the data flow in question should be
> correctly forwarded regardless of which behavior is chosen.

In the standards process, anything not explicitly forbidden
is implicitly allowed.  Sometimes things which are explicitly
forbidden are implicitly allowed if undetectable.  Finally,
even if a thing is never allowed, it may not be advisable to
assume that it is not done.  :-)

> 
>     Jack


From owner-mpls@UU.NET  Thu Sep 19 00:05:04 2002
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 ESMTP id AAA09764
	for <mpls-archive@lists.ietf.org>; Thu, 19 Sep 2002 00:05:03 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngya24422
	for <mpls-archive@lists.ietf.org>; Thu, 19 Sep 2002 04:06:49 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngya24202;
	Thu, 19 Sep 2002 04:06:42 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngya15882
	for mpls-outgoing; Thu, 19 Sep 2002 04:06:28 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQngya15872
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 19 Sep 2002 04:06:18 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 QQngya15900
	for <mpls@UU.NET>; Thu, 19 Sep 2002 04:05:57 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngya08218
	for <mpls@UU.NET>; Thu, 19 Sep 2002 04:05:57 GMT
Received: from petasus.ch.intel.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: petasus.ch.intel.com [143.182.124.5])
	id QQngya08210
	for <mpls@UU.NET>; Thu, 19 Sep 2002 04:05:56 GMT
Received: from fmsmsxvs043.fm.intel.com (fmsmsxvs043.fm.intel.com [132.233.42.129])
	by petasus.ch.intel.com (8.11.6/8.11.6/d: solo.mc,v 1.43 2002/08/30 20:06:11 dmccart Exp $) with SMTP id g8J47fY00163
	for <mpls@UU.NET>; Thu, 19 Sep 2002 04:07:42 GMT
Received: from fmsmsx26.fm.intel.com ([132.233.42.26])
 by fmsmsxvs043.fm.intel.com (NAVGW 2.5.2.11) with SMTP id M2002091821041831271
 ; Wed, 18 Sep 2002 21:04:18 -0700
Received: by fmsmsx26.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <S62KLR5A>; Wed, 18 Sep 2002 21:05:54 -0700
Message-ID: <12B638FEE763F74696D8544752E7204812EA20@bgsmsx101.iind.intel.com>
From: "Ramia, Kannan Babu" <kannan.babu.ramia@intel.com>
To: "'Gray, Eric'" <egray@celoxnetworks.com>,
        "'Vijayanand C - CTD, Chennai.'" <vijayc@ctd.hcltech.com>,
        "'Eric Rosen'"
	 <erosen@cisco.com>
Cc: mpls@UU.NET
Subject: RE: Clarification on Handling a specific event in LDP
Date: Wed, 18 Sep 2002 21:01:17 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C25F91.349C2460"
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_01C25F91.349C2460
Content-Type: text/plain;
	charset="iso-8859-1"

Sorry.. due to the time zone difference i didnt look at your resposes.. Here
are my view point on the solution.. please see below
 
-----Original Message-----
From: Gray, Eric [mailto:egray@celoxnetworks.com]
Sent: Wednesday, September 18, 2002 6:56 PM
To: 'Vijayanand C - CTD, Chennai.'; Ramia, Kannan Babu
Cc: mpls@UU.NET
Subject: RE: Clarification on Handling a specific event in LDP



Vijay/Kannan,

 

            Please see below...

 

Eric W. Gray

Systems Architect

Celox Networks, Inc.

egray@celoxnetworks.com

508 305 7214

 

-----Original Message-----
From: Vijayanand C - CTD, Chennai. [mailto:vijayc@ctd.hcltech.com] 
Sent: Wednesday, September 18, 2002 5:19 AM
To: Ramia, Kannan Babu
Cc: mpls@UU.NET
Subject: RE: Clarification on Handling a specific event in LDP

 

Again you are overriding the Dod Ord control by using a label map along with
a withdraw whereby  it becomes an unsolicited mapping.

Apart from the Question of syntactical correctness of sending an unsolicited
label map there is another problem.

 

There are cases in which DoD vs DU distribution and Ordered vs Independent
control

become rather vague distinctions.  That is the problem hidden behind the
fact that

people talk past each other on this topic, rather than talking to each
other.

 

Rather than talking about the gross terms, consider the details of
implementation

you are likely to encounter. If the negotiated mode between two LSRs is DoD,
then

each LSR is required to accept one or more Label Request messages for each
FEC

and neither is required to accept _any_ unsolicited Label Mapping messages.
The

LSR that receives an unsolicited Label Mapping may decide to immediate
release

it - or worse yet - it may assume the peer has become confused and tear down
the

LDP session. This is in essence the problem that Vijay is probably concerned
with.

 

However, there is always the robust notion of being generous in what you
accept.

 

While, IMHO, the LSR that sends an unsolicited Label Mapping when in DoD
mode

is generally in the wrong, it seems _very_ un-robust behavior to terminate
the LDP

session and it might be more robust to at least retain the new Label Mapping
(yes,

even if in conservative retention mode - thus blurring another distinction).
In fact,

it is likely that some implementations will treat such an unsolicited Label
Mapping

as an implied Label Withdraw (though - with effort - I can dredge up an old
E-Mail

message in which members of the LDP design team were adamant that this was 

not the way it is intended to work).

 

In the case Kannan is pointing out, the retention of the new Label Mapping
(in case

the previous one is withdrawn) is very much more robust than almost anything
else 

you might do (with the possible exception of using it as an implied
Withdraw).  If

the new Label Mapping is not retained, then the LSP is removed edge to edge
and

must be re-established.  


[Ramia, Kannan Babu]  here i am using the Label Withdraw message (which is
again doesnt lose any context) as my implied Label mapping message in
addition to its withdrawing function, but here only difference is that
implied label mapping may not have any out standing label request so in the
sense it is unsolicited label mapping. But in this case the main difference
will be this label mapping is not a pure Unsolicited case because it has the
context of the LSP it refers. so i dont see this procedural changes should
not confuse the LSRs operating in DOD ordered mode.

 

This - by the way - is exactly the behavior originally intended in the DoD,
Ordered 

control mode: LSR A in Kannan's case would Withdraw all Labels associated
with

forwarding toward the newly discovered peer LSR C and then wait for all
affected

ingress LSRs to send Label Requests to re-establish LSPs.  I brought this up
with 

the LDP design team 3 years ago and many of them agreed that this would not
be 

good behavior.  However, it was not clear that any other behavior should be
explicitly

specified.

 

 The domain in configured for Dod Ord. THis may be due to constraints in the
switches to install labels. For example, in GMPLS, the set of desired labels
is sent along with the request indicating the range of labels the upstream
can switch onto. Hence the Dod Ord control has significance in such
scenarios' and overriding it may cause confusion.

 

The issue of change in next hop for an FEC right at the egress( which is
usually egress for routing domain) is a very rare situation and I think it
does nt warrant drastic changes to the semantics and operation of LDP

 

Vijay

-----Original Message-----
From: Ramia, Kannan Babu [mailto:kannan.babu.ramia@intel.com]
Sent: Wednesday, September 18, 2002 2:20 PM
To: 'Vijayanand C - CTD, Chennai.'
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP

See my inline Comments

-----Original Message-----
From: Vijayanand C - CTD, Chennai. [mailto:vijayc@ctd.hcltech.com]
Sent: Wednesday, September 18, 2002 12:15 PM
To: Ramia, Kannan Babu
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP

See my comments inline

-----Original Message-----
From: Ramia, Kannan Babu [mailto:kannan.babu.ramia@intel.com]
Sent: Wednesday, September 18, 2002 11:48 AM
To: 'Vijayanand C - CTD, Chennai.'; Ramia, Kannan Babu
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP

hi vijay..

   

thanks for ur reply ..but i still have some thing to get clarified ...
please see in line Comments

 

bye

kb

-----Original Message-----
From: Vijayanand C - CTD, Chennai. [mailto:vijayc@ctd.hcltech.com]
Sent: Wednesday, September 18, 2002 11:39 AM
To: Ramia, Kannan Babu
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP

Kannan,

This is a special case. 

 

 

I have a solution for this problem.

Basically if any LSR receives an Label withdraw message from its valid Next
hop neighbor then before propagating to its upstream peers it need to check
the value of the label being withdrawn, if the label happens to be an NULL
label then it should not propagate the label withdraw to its upstream peers.
Now this LSR should now assume itself as an egress for that LSP.
[Vijayanand C - CTD, Chennai.]  What will happen in valid cases when the
eggress actually wants to withdraw label and when u no longer want to switch
for that FEC ?The pennultimate hop should not hold the label in that case.
How will the Phop know for which case the withdraw applies ?   

[Ramia, Kannan Babu]  Actually here we are not holding the egress label, we
are sending a label release for the corresponding withdraw message and also
i am expecting only the INGRESS will start the LSP deletion process for any
genuine case (of course assumption is all LSR is configured with the
forwarding of the label release)

[Ramia, Kannan Babu]  [Vijayanand C - CTD, Chennai.] By holding the label I
mean, the PHop would be holding its upstream labels unnecessarily even in
genuine LSP tear down scenarios( when withdraw is received from its
downstream node which is egress) 

 Here ingress is not initiating deletion the egress does it by sending
withdraw. 

[Ramia, Kannan Babu]  I have one more idea for differntiating a genuine
withdraw to the special withdraw. i.e if the LSR A sends a label with draw
message to LSR B with the FEC-X and label TLV has label value IMPLICIT NULL
and in the optinal paramters it can send a changed label value to be used,
there by we can differntiate from the genuine case (in genuine case the
optinal paramter wont contain any label) to the special case. if we have
this check in the label withdraw procedure it will solve our problem. This
solution wont distrub the LSP setup where as the ingress retry solution will
distrub the LSP, which is undesiarable one also we need to provide the
checking criteria for re-establishing the LSP.

 

 



 

 

Second one could be there should be a provision to change the label for the
particular FEC. I.e any point of time the valid next hop LSR can advertise a
change of label for that FEC. Here problems are we need to maintain the
context of that advertisement (LM).
[Vijayanand C - CTD, Chennai.]  This becomes unsolicited advertisement.

[Ramia, Kannan Babu] i dont see any problem in this kind of advertisement,
even if u are configured with DOD ordered mode if any change in hop count or
PV, the downstream LSR will anyway generate a LM with out any outstanding
LR. So i want to treat the change in label also the same way as that of
change in hop count.
[Vijayanand C - CTD, Chennai.] Changing the attributes of the label mapping
( like PV) is different from changing the label itself. Again the context
maintenance (old label, FEC) for this is a problem as you said. Even the
question of communicating changed attributes seldom arises in DOd Ord
control. In cases where it happens, such as Next hop change, it was debated
at length earlier in this list if it was proper to unsolicitedly advertise
the changed attributes.

 

 

A better way would be for the egress to withdraw the label. However the
ingress will not issue a request unless it is in Independent control. This
anyway is a problem. My suggestin would be - The ingress after sending a
release can issue a fresh request for the label even if its not in
independent control if it still supports label switching on the FEC. I feel
This would be more cleaner .

[Ramia, Kannan Babu]  How the ingress will know that it need to request
again or initate LSP establishment once again for the same FEC (i mean here
what criteria or conditions it checks before it does this again..) because
in some genuine cases if egress wants to remove the LSP then it may lead to
infinite looping.
[Vijayanand C - CTD, Chennai.] This kind of situation( retrying) will anyway
apply in Independent control( all nodes along the LSP may potentially
retry). So how will you solve the problem in that case ?  What I am
suggesting is if ordered control is used the retry can be done only by the
ingress. Any retry mechanism would have some back off and stopping criteria
associated with it implicitly.

 

 

 

 

 

Vijay 

 


------_=_NextPart_001_01C25F91.349C2460
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 6.00.2716.2200" name=GENERATOR>
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
P.MsoPlainText {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
LI.MsoPlainText {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
DIV.MsoPlainText {
	FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
P.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
SPAN.EmailStyle16 {
	COLOR: black; FONT-FAMILY: Arial
}
SPAN.EmailStyle19 {
	COLOR: navy; FONT-FAMILY: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV><SPAN class=607035203-19092002><FONT face=Arial color=#0000ff 
size=2>Sorry.. due to the time zone difference i didnt look at your resposes.. 
Here are my view point on the solution.. please see below</FONT></SPAN></DIV>
<DIV><SPAN class=607035203-19092002><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><FONT face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Gray, 
Eric [mailto:egray@celoxnetworks.com]<BR><B>Sent:</B> Wednesday, September 18, 
2002 6:56 PM<BR><B>To:</B> 'Vijayanand C - CTD, Chennai.'; Ramia, Kannan 
Babu<BR><B>Cc:</B> mpls@UU.NET<BR><B>Subject:</B> RE: Clarification on Handling 
a specific event in LDP<BR><BR></FONT></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV class=Section1>
  <P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Vijay/Kannan,</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  </SPAN></FONT><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">Please see 
  below...</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <DIV>
  <P class=MsoAutoSig><FONT face="Times New Roman" color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy">Eric W. Gray</SPAN></FONT></P>
  <P class=MsoAutoSig><FONT face="Times New Roman" color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy">Systems Architect</SPAN></FONT></P>
  <P class=MsoAutoSig><FONT face="Times New Roman" color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy">Celox Networks, Inc.</SPAN></FONT></P>
  <P class=MsoAutoSig><FONT face="Times New Roman" color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy">egray@celoxnetworks.com</SPAN></FONT></P>
  <P class=MsoPlainText><FONT face="Courier New" color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy">508 305 7214</SPAN></FONT></P></DIV>
  <P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <DIV 
  style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
  <P class=MsoNormal><FONT face=Tahoma size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original 
  Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Vijayanand 
  C - CTD, Chennai. [mailto:vijayc@ctd.hcltech.com] <BR><B><SPAN 
  style="FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, September 18, 2002 5:19 
  AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> Ramia, Kannan 
  Babu<BR><B><SPAN style="FONT-WEIGHT: bold">Cc:</SPAN></B> 
  mpls@UU.NET<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: 
  Clarification on Handling a specific event in LDP</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=#0000ff size=2><SPAN 
  style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <DIV>
  <P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Again you are 
  overriding the Dod Ord control by using a label map along with a withdraw 
  whereby&nbsp; it becomes an unsolicited mapping.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Apart from the 
  Question of syntactical correctness of sending an unsolicited label map there 
  is another problem.</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">There are cases in 
  which DoD vs DU distribution and Ordered vs Independent 
  control</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">become rather vague 
  distinctions.&nbsp; That is the problem hidden behind the fact 
  that</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">people talk past 
  each other on this topic, rather than talking to each other.</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">Rather than talking 
  about the gross terms, consider the details of 
implementation</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">you are likely to 
  encounter. If the negotiated mode between two LSRs is DoD, 
  then</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">each LSR is required 
  to accept one or more Label Request messages for each FEC</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">and neither is 
  required to accept _<I><SPAN style="FONT-STYLE: italic">any</SPAN></I>_ 
  unsolicited Label Mapping messages.&nbsp; The</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">LSR that receives an 
  unsolicited Label Mapping may decide to immediate release</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">it - or worse yet - 
  it may assume the peer has become confused and tear down the</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">LDP session. This is 
  in essence the problem that Vijay is probably concerned 
with.</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">However, there is 
  always the robust notion of being generous in what you 
  accept.</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">While, IMHO, the LSR 
  that sends an unsolicited Label Mapping when in DoD mode</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">is generally in the 
  wrong, it seems _<I><SPAN style="FONT-STYLE: italic">very</SPAN></I>_ 
  un-robust behavior to terminate the LDP</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">session and it might 
  be more robust to at least retain the new Label Mapping 
(yes,</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">even if in 
  conservative retention mode - thus blurring another distinction).&nbsp; In 
  fact,</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">it is likely that 
  some implementations will treat such an unsolicited Label 
  Mapping</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">as an implied Label 
  Withdraw (though - with effort - I can dredge up an old 
  E-Mail</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">message in which 
  members of the LDP design team were adamant that this was </SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">not the way it is 
  intended to work).</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">In the case Kannan 
  is pointing out, the retention of the new Label Mapping (in 
  case</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">the previous one is 
  withdrawn) is very much more robust than almost anything else 
  </SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">you might do (with 
  the possible exception of using it as an implied Withdraw).&nbsp; 
  If</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">the new Label 
  Mapping is not retained, then the LSP is removed edge to edge 
  and</SPAN></FONT></P>
  <P class=MsoNormal><FONT color=green><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">must be 
  re-established.&nbsp; <BR><SPAN class=607035203-19092002><FONT 
  color=#0000ff></FONT></SPAN></SPAN></FONT></P>
  <P class=MsoNormal><FONT color=green><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial"><SPAN 
  class=607035203-19092002><FONT color=#0000ff>[Ramia, Kannan 
  Babu]&nbsp;&nbsp;here i am using the Label Withdraw message (which is again 
  doesnt lose any context) as my implied Label mapping message in addition to 
  its withdrawing function, but here only difference is that implied label 
  mapping may not have&nbsp;any out standing label request so in the sense it is 
  unsolicited label mapping. But in this case the main difference will be this 
  label mapping is not a pure Unsolicited case because it has the context of the 
  LSP it refers. so i dont see this procedural changes should not confuse the 
  LSRs operating in DOD ordered mode.</FONT></SPAN></SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">This - by the way - 
  is exactly the behavior originally intended in the DoD, Ordered 
  </SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">control mode: LSR A 
  in Kannan's case would Withdraw all Labels associated with</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">forwarding toward 
  the newly discovered peer LSR C and then wait for all 
  affected</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">ingress LSRs to send 
  Label Requests to re-establish LSPs.&nbsp; I brought this up with 
  </SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">the LDP design team 
  3 years ago and many of them agreed that this would not be </SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">good behavior.&nbsp; 
  However, it was not clear that any other behavior should be 
  explicitly</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=green size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: green; FONT-FAMILY: Arial">specified.</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">&nbsp;The domain in 
  configured for Dod Ord. THis may be due to constraints in the switches to 
  install labels. For example, in GMPLS, the set of desired labels is sent along 
  with the request indicating the range of labels the upstream can switch onto. 
  Hence the Dod Ord control has significance in such scenarios' and overriding 
  it may cause confusion.</SPAN></FONT></P></DIV>
  <DIV>
  <P class=MsoNormal><FONT face=Arial color=#0000ff size=2><SPAN 
  style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">The issue of change 
  in next hop for an FEC right at the egress( which is usually egress for 
  routing domain)&nbsp;is a very rare situation and I think it does nt warrant 
  drastic changes to the semantics and operation of LDP</SPAN></FONT></P></DIV>
  <DIV>
  <P class=MsoNormal><FONT face=Arial color=#0000ff size=2><SPAN 
  style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></DIV>
  <DIV>
  <P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN 
  style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Vijay</SPAN></FONT></P></DIV>
  <BLOCKQUOTE style="MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt; MARGIN-RIGHT: 0in">
    <P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><FONT face=Tahoma 
    size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original 
    Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Ramia, 
    Kannan Babu [mailto:kannan.babu.ramia@intel.com]<BR><B><SPAN 
    style="FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, September 18, 2002 
    2:20 PM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> 'Vijayanand C - 
    CTD, Chennai.'<BR><B><SPAN style="FONT-WEIGHT: bold">Cc:</SPAN></B> 
    mpls@uu.net<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: 
    Clarification on Handling a specific event in LDP</SPAN></FONT></P>
    <DIV>
    <P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN 
    style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">See my inline 
    Comments</SPAN></FONT></P></DIV>
    <BLOCKQUOTE 
      style="MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt; MARGIN-RIGHT: 0in"><P 
      class=MsoNormal style="MARGIN-BOTTOM: 12pt"><FONT face=Tahoma size=2><SPAN 
      style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original 
      Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> 
      Vijayanand C - CTD, Chennai. [mailto:vijayc@ctd.hcltech.com]<BR><B><SPAN 
      style="FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, September 18, 2002 
      12:15 PM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> Ramia, 
      Kannan Babu<BR><B><SPAN style="FONT-WEIGHT: bold">Cc:</SPAN></B> 
      mpls@uu.net<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: 
      Clarification on Handling a specific event in LDP</SPAN></FONT></P>
      <DIV>
      <P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN 
      style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">See my comments 
      inline</SPAN></FONT></P></DIV>
      <BLOCKQUOTE 
style="MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt; MARGIN-RIGHT: 0in">
        <P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><FONT face=Tahoma 
        size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original 
        Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> 
        Ramia, Kannan Babu [mailto:kannan.babu.ramia@intel.com]<BR><B><SPAN 
        style="FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, September 18, 2002 
        11:48 AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> 
        'Vijayanand C - CTD, Chennai.'; Ramia, Kannan Babu<BR><B><SPAN 
        style="FONT-WEIGHT: bold">Cc:</SPAN></B> mpls@uu.net<BR><B><SPAN 
        style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: Clarification on 
        Handling a specific event in LDP</SPAN></FONT></P>
        <DIV>
        <P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN 
        style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">hi 
        vijay..</SPAN></FONT></P></DIV>
        <DIV>
        <P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN 
        style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">&nbsp;&nbsp; 
        </SPAN></FONT></P></DIV>
        <DIV>
        <P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN 
        style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">thanks for ur 
        reply ..but i still have some thing to get clarified ... please see in 
        line Comments</SPAN></FONT></P></DIV>
        <DIV>
        <P class=MsoNormal><FONT face=Arial color=#0000ff size=2><SPAN 
        style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P></DIV>
        <DIV>
        <P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN 
        style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">bye</SPAN></FONT></P></DIV>
        <DIV>
        <P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN 
        style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">kb</SPAN></FONT></P></DIV>
        <BLOCKQUOTE 
        style="MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt; MARGIN-RIGHT: 0in">
          <P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><FONT face=Tahoma 
          size=2><SPAN 
          style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original 
          Message-----<BR><B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> 
          Vijayanand C - CTD, Chennai. 
          [mailto:vijayc@ctd.hcltech.com]<BR><B><SPAN 
          style="FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, September 18, 
          2002 11:39 AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> 
          Ramia, Kannan Babu<BR><B><SPAN 
          style="FONT-WEIGHT: bold">Cc:</SPAN></B> mpls@uu.net<BR><B><SPAN 
          style="FONT-WEIGHT: bold">Subject:</SPAN></B> RE: Clarification on 
          Handling a specific event in LDP</SPAN></FONT></P>
          <DIV>
          <P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN 
          style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Kannan,</SPAN></FONT></P></DIV>
          <DIV>
          <P class=MsoNormal><FONT face=Arial color=blue size=2><SPAN 
          style="FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">This is a 
          special case. </SPAN></FONT></P></DIV>
          <BLOCKQUOTE 
          style="MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt; MARGIN-RIGHT: 0in">
            <P class=MsoNormal><SPAN class=EmailStyle16><FONT face=Arial 
            color=black size=2><SPAN 
            style="FONT-SIZE: 10pt"></SPAN></FONT></SPAN>&nbsp;</P>
            <P class=MsoNormal><SPAN class=EmailStyle16><FONT face=Arial 
            color=black size=2><SPAN 
            style="FONT-SIZE: 10pt"></SPAN></FONT></SPAN>&nbsp;</P>
            <P class=MsoNormal><SPAN class=EmailStyle16><FONT face=Arial 
            color=black size=2><SPAN style="FONT-SIZE: 10pt">I have a solution 
            for this problem.</SPAN></FONT></SPAN></P>
            <P class=MsoNormal><SPAN class=EmailStyle16><FONT face=Arial 
            color=black size=2><SPAN style="FONT-SIZE: 10pt">Basically if any 
            LSR receives an Label withdraw message from its valid Next hop 
            neighbor then before propagating to its upstream peers it need to 
            check the value of the label being withdrawn, if the label happens 
            to be an NULL label then it should not propagate the label withdraw 
            to its upstream peers. Now this LSR should now assume itself as an 
            egress for that LSP.</SPAN></FONT></SPAN><FONT face=Arial 
            color=black size=2><SPAN 
            style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial"><BR></SPAN></FONT><SPAN 
            class=EmailStyle16><FONT face=Arial color=blue size=2><SPAN 
            style="FONT-SIZE: 10pt; COLOR: blue">[Vijayanand C - CTD, 
            Chennai.]&nbsp; What will happen in valid cases when the eggress 
            actually wants to withdraw label&nbsp;and when u no longer want to 
            switch for that FEC ?The pennultimate hop should&nbsp;not 
            hold&nbsp;the label in that case. How&nbsp;will the Phop 
            know&nbsp;for which case the withdraw applies 
            ?&nbsp;&nbsp;&nbsp;</SPAN></FONT></SPAN></P>
            <P class=MsoNormal><SPAN class=EmailStyle16><FONT face=Arial 
            color=red size=2><SPAN style="FONT-SIZE: 10pt; COLOR: red">[Ramia, 
            Kannan Babu]&nbsp; Actually here&nbsp;we are not holding the egress 
            label, we are sending a label&nbsp;release for the 
            corresponding&nbsp;withdraw message and&nbsp;also&nbsp;i am 
            expecting only the INGRESS will start the LSP deletion process for 
            any genuine case (of course assumption is all LSR is configured with 
            the forwarding of the label release)</SPAN></FONT></SPAN><FONT 
            face=Arial color=red size=2><SPAN 
            style="FONT-SIZE: 10pt; COLOR: red; FONT-FAMILY: Arial"><BR><BR></SPAN></FONT><SPAN 
            class=EmailStyle16><FONT face=Arial color=blue size=2><SPAN 
            style="FONT-SIZE: 10pt; COLOR: blue">[Ramia, Kannan 
            Babu]&nbsp;&nbsp;[Vijayanand C - CTD, Chennai.]&nbsp;By holding the 
            label I mean, the PHop would be holding its upstream labels 
            unnecessarily&nbsp;even in genuine LSP&nbsp;tear down scenarios( 
            when withdraw is received from its downstream node which is egress) 
            </SPAN></FONT></SPAN></P>
            <P class=MsoNormal><SPAN class=EmailStyle16><FONT face=Arial 
            color=blue size=2><SPAN 
            style="FONT-SIZE: 10pt; COLOR: blue">&nbsp;Here ingress is not 
            initiating deletion the egress does it by sending 
            withdraw.&nbsp;</SPAN></FONT></SPAN></P>
            <P class=MsoNormal><SPAN class=EmailStyle16><FONT face=Arial 
            color=red size=2><SPAN style="FONT-SIZE: 10pt; COLOR: red">[Ramia, 
            Kannan Babu]&nbsp;&nbsp;I have one more idea for&nbsp;differntiating 
            a genuine withdraw to the special withdraw. i.e if the LSR 
            A&nbsp;sends a label with draw message to LSR B with the&nbsp;FEC-X 
            and label TLV has label value&nbsp;IMPLICIT NULL and in the optinal 
            paramters it can send a&nbsp;changed label value to be used, there 
            by we can differntiate from the genuine case (in genuine case the 
            optinal paramter wont contain any label)&nbsp;to the special case. 
            if we have this check in the label withdraw procedure it will solve 
            our problem. This solution wont distrub the LSP setup where as the 
            ingress retry solution will distrub the LSP, which 
            is&nbsp;undesiarable one also we need to provide the checking 
            criteria for re-establishing the LSP.</SPAN></FONT></SPAN></P>
            <P class=MsoNormal><FONT face=Arial color=#0000ff size=2><SPAN 
            style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
            <P class=MsoNormal><FONT face=Arial color=#0000ff size=2><SPAN 
            style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
            <P class=MsoNormal></P>
            <P class=MsoNormal><FONT face=Arial color=#0000ff size=2><SPAN 
            style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
            <P class=MsoNormal><SPAN class=EmailStyle16><FONT face=Arial 
            color=black size=2><SPAN 
            style="FONT-SIZE: 10pt"></SPAN></FONT></SPAN>&nbsp;</P>
            <P class=MsoNormal><SPAN class=EmailStyle16><FONT face=Arial 
            color=black size=2><SPAN style="FONT-SIZE: 10pt">Second one could be 
            there should be a provision to change the label for the particular 
            FEC. I.e any point of time the valid next hop LSR can advertise a 
            change of label for that FEC. Here problems are we need to maintain 
            the context of that advertisement (LM).</SPAN></FONT></SPAN><FONT 
            face=Arial color=black size=2><SPAN 
            style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial"><BR></SPAN></FONT><SPAN 
            class=EmailStyle16><FONT face=Arial color=blue size=2><SPAN 
            style="FONT-SIZE: 10pt; COLOR: blue">[Vijayanand C - CTD, 
            Chennai.]&nbsp;&nbsp;This becomes unsolicited 
            advertisement.</SPAN></FONT></SPAN></P>
            <P class=MsoNormal><SPAN class=EmailStyle16><FONT face=Arial 
            color=red size=2><SPAN style="FONT-SIZE: 10pt; COLOR: red">[Ramia, 
            Kannan Babu] i dont see any problem in this kind of advertisement, 
            even if u are configured with DOD ordered mode if any&nbsp;change in 
            hop count or&nbsp;PV, the downstream LSR&nbsp;will anyway generate a 
            LM with out any outstanding LR.&nbsp;So i want to treat the change 
            in label also the same way as that of change in hop 
            count.</SPAN></FONT></SPAN><FONT face=Arial color=red size=2><SPAN 
            style="FONT-SIZE: 10pt; COLOR: red; FONT-FAMILY: Arial"><BR></SPAN></FONT><SPAN 
            class=EmailStyle16><FONT face=Arial color=blue size=2><SPAN 
            style="FONT-SIZE: 10pt; COLOR: blue">[Vijayanand C - CTD, 
            Chennai.]&nbsp;Changing the&nbsp;attributes of the label mapping 
            (&nbsp;like PV)&nbsp;is different from changing the label itself. 
            Again the context maintenance (old label, FEC) for this is a problem 
            as you said. Even the question of communicating changed attributes 
            seldom arises in DOd Ord control. In cases where it happens, such as 
            Next hop change, it was debated at length earlier in this list if it 
            was proper to unsolicitedly advertise the changed 
            attributes.</SPAN></FONT></SPAN></P>
            <P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN 
            style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
            <P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN 
            style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
            <P class=MsoNormal><SPAN class=EmailStyle16><FONT face=Arial 
            color=blue size=2><SPAN style="FONT-SIZE: 10pt; COLOR: blue">A 
            better way would be for the egress to withdraw the label. 
            However&nbsp;the ingress will not issue a request unless it is in 
            Independent control. This anyway&nbsp;is a&nbsp;problem. My 
            suggestin would be - The ingress after sending a release can issue a 
            fresh request&nbsp;for the label even if its not in independent 
            control if it still supports label switching on the FEC. I feel 
            This&nbsp;would be more cleaner .</SPAN></FONT></SPAN></P>
            <P class=MsoNormal><SPAN class=EmailStyle16><FONT face=Arial 
            color=red size=2><SPAN style="FONT-SIZE: 10pt; COLOR: red">[Ramia, 
            Kannan Babu]&nbsp;&nbsp;How the ingress will know that it need to 
            request again or initate LSP establishment once again for the same 
            FEC (i mean here what criteria or conditions it checks before it 
            does this again..) because in some genuine cases if egress wants to 
            remove the LSP&nbsp;then it may lead to infinite 
            looping.</SPAN></FONT></SPAN><FONT face=Arial color=red size=2><SPAN 
            style="FONT-SIZE: 10pt; COLOR: red; FONT-FAMILY: Arial"><BR></SPAN></FONT><SPAN 
            class=EmailStyle16><FONT face=Arial color=blue size=2><SPAN 
            style="FONT-SIZE: 10pt; COLOR: blue">[Vijayanand C - CTD, 
            Chennai.]&nbsp;This kind of situation(&nbsp;retrying)&nbsp;will 
            anyway apply in Independent control( all nodes along the LSP may 
            potentially retry). So&nbsp;how will you solve the problem in that 
            case ? &nbsp;What I am suggesting is if ordered control is used the 
            retry can be done only by the ingress. Any retry mechanism would 
            have some back off and stopping criteria associated with it 
            implicitly.</SPAN></FONT></SPAN></P>
            <P class=MsoNormal><FONT face=Arial color=#0000ff size=2><SPAN 
            style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
            <P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN 
            style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
            <P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN 
            style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
            <P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN 
            style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
            <P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN 
            style="FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
            <P class=MsoNormal><SPAN class=EmailStyle16><FONT face=Arial 
            color=blue size=2><SPAN 
            style="FONT-SIZE: 10pt; COLOR: blue">Vijay</SPAN></FONT></SPAN><SPAN 
            class=EmailStyle16><FONT face=Arial color=black size=2><SPAN 
            style="FONT-SIZE: 10pt">&nbsp;</SPAN></FONT></SPAN></P>
            <P class=MsoNormal><FONT face=Arial color=#0000ff size=2><SPAN 
            style="FONT-SIZE: 12pt; COLOR: black"></SPAN></FONT>&nbsp;</P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></DIV></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C25F91.349C2460--


From owner-mpls@UU.NET  Thu Sep 19 00:07:46 2002
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 ESMTP id AAA09797
	for <mpls-archive@lists.ietf.org>; Thu, 19 Sep 2002 00:07:45 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngya11056
	for <mpls-archive@lists.ietf.org>; Thu, 19 Sep 2002 04:09:29 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngya10663;
	Thu, 19 Sep 2002 04:09:15 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngya16207
	for mpls-outgoing; Thu, 19 Sep 2002 04:08:34 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQngya16113
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 19 Sep 2002 04:08: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 QQngya20055
	for <mpls@uu.net>; Thu, 19 Sep 2002 04:07:34 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngya01622
	for <mpls@uu.net>; Thu, 19 Sep 2002 04:07:34 GMT
Received: from petasus.ch.intel.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: petasus.ch.intel.com [143.182.124.5])
	id QQngya01606
	for <mpls@uu.net>; Thu, 19 Sep 2002 04:07:33 GMT
Received: from fmsmsxv040-1.fm.intel.com (fmsmsxvs040.fm.intel.com [132.233.42.124])
	by petasus.ch.intel.com (8.11.6/8.11.6/d: solo.mc,v 1.43 2002/08/30 20:06:11 dmccart Exp $) with SMTP id g8J49JY00634
	for <mpls@uu.net>; Thu, 19 Sep 2002 04:09:19 GMT
Received: from FMSMSX016.fm.intel.com ([132.233.42.195])
 by fmsmsxv040-1.fm.intel.com (NAVGW 2.5.2.11) with SMTP id M2002091821081200463
 ; Wed, 18 Sep 2002 21:08:12 -0700
Received: by fmsmsx016.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <S06W335M>; Wed, 18 Sep 2002 21:07:32 -0700
Message-ID: <12B638FEE763F74696D8544752E7204812EA21@bgsmsx101.iind.intel.com>
From: "Ramia, Kannan Babu" <kannan.babu.ramia@intel.com>
To: "'Vijayanand C - CTD, Chennai.'" <vijayc@ctd.hcltech.com>
Cc: mpls@UU.NET
Subject: RE: Clarification on Handling a specific event in LDP
Date: Wed, 18 Sep 2002 21:02:43 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C25F91.67F68120"
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_01C25F91.67F68120
Content-Type: text/plain;
	charset="ISO-8859-1"

HI vijay..
 
    i didnt understand why PHP behavior will come in GMPLS..in GMPLS we are
using actual resources as our labels..so i dont think this case is
applicable to GMPLS.
 
 
bye
kb
-----Original Message-----
From: Vijayanand C - CTD, Chennai. [mailto:vijayc@ctd.hcltech.com]
Sent: Wednesday, September 18, 2002 2:49 PM
To: Ramia, Kannan Babu
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP


Again you are overriding the Dod Ord control by using a label map along with
a withdraw whereby  it becomes an unsolicited mapping.
Apart from the Question of syntactical correctness of sending an unsolicited
label map there is another problem.
 The domain in configured for Dod Ord. THis may be due to constraints in the
switches to install labels. For example, in GMPLS, the set of desired labels
is sent along with the request indicating the range of labels the upstream
can switch onto. Hence the Dod Ord control has significance in such
scenarios' and overriding it may cause confusion.
 
The issue of change in next hop for an FEC right at the egress( which is
usually egress for routing domain) is a very rare situation and I think it
does nt warrant drastic changes to the semantics and operation of LDP
 
Vijay
-----Original Message-----
From: Ramia, Kannan Babu [mailto:kannan.babu.ramia@intel.com]
Sent: Wednesday, September 18, 2002 2:20 PM
To: 'Vijayanand C - CTD, Chennai.'
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP


See my inline Comments
-----Original Message-----
From: Vijayanand C - CTD, Chennai. [mailto:vijayc@ctd.hcltech.com]
Sent: Wednesday, September 18, 2002 12:15 PM
To: Ramia, Kannan Babu
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP


See my comments inline
-----Original Message-----
From: Ramia, Kannan Babu [mailto:kannan.babu.ramia@intel.com]
Sent: Wednesday, September 18, 2002 11:48 AM
To: 'Vijayanand C - CTD, Chennai.'; Ramia, Kannan Babu
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP


hi vijay..
   
thanks for ur reply ..but i still have some thing to get clarified ...
please see in line Comments
 
bye
kb
-----Original Message-----
From: Vijayanand C - CTD, Chennai. [mailto:vijayc@ctd.hcltech.com]
Sent: Wednesday, September 18, 2002 11:39 AM
To: Ramia, Kannan Babu
Cc: mpls@uu.net
Subject: RE: Clarification on Handling a specific event in LDP


Kannan,
This is a special case. 
 
 
I have a solution for this problem.
Basically if any LSR receives an Label withdraw message from its valid Next
hop neighbor then before propagating to its upstream peers it need to check
the value of the label being withdrawn, if the label happens to be an NULL
label then it should not propagate the label withdraw to its upstream peers.
Now this LSR should now assume itself as an egress for that LSP.
[Vijayanand C - CTD, Chennai.]  What will happen in valid cases when the
eggress actually wants to withdraw label and when u no longer want to switch
for that FEC ?The pennultimate hop should not hold the label in that case.
How will the Phop know for which case the withdraw applies ?   

[Ramia, Kannan Babu]  Actually here we are not holding the egress label, we
are sending a label release for the corresponding withdraw message and also
i am expecting only the INGRESS will start the LSP deletion process for any
genuine case (of course assumption is all LSR is configured with the
forwarding of the label release)

[Ramia, Kannan Babu]  [Vijayanand C - CTD, Chennai.] By holding the label I
mean, the PHop would be holding its upstream labels unnecessarily even in
genuine LSP tear down scenarios( when withdraw is received from its
downstream node which is egress) 
 Here ingress is not initiating deletion the egress does it by sending
withdraw. 

[Ramia, Kannan Babu]  I have one more idea for differntiating a genuine
withdraw to the special withdraw. i.e if the LSR A sends a label with draw
message to LSR B with the FEC-X and label TLV has label value IMPLICIT NULL
and in the optinal paramters it can send a changed label value to be used,
there by we can differntiate from the genuine case (in genuine case the
optinal paramter wont contain any label) to the special case. if we have
this check in the label withdraw procedure it will solve our problem. This
solution wont distrub the LSP setup where as the ingress retry solution will
distrub the LSP, which is undesiarable one also we need to provide the
checking criteria for re-establishing the LSP.
 
 
 
 
Second one could be there should be a provision to change the label for the
particular FEC. I.e any point of time the valid next hop LSR can advertise a
change of label for that FEC. Here problems are we need to maintain the
context of that advertisement (LM).
[Vijayanand C - CTD, Chennai.]  This becomes unsolicited advertisement.

[Ramia, Kannan Babu] i dont see any problem in this kind of advertisement,
even if u are configured with DOD ordered mode if any change in hop count or
PV, the downstream LSR will anyway generate a LM with out any outstanding
LR. So i want to treat the change in label also the same way as that of
change in hop count.
[Vijayanand C - CTD, Chennai.] Changing the attributes of the label mapping
( like PV) is different from changing the label itself. Again the context
maintenance (old label, FEC) for this is a problem as you said. Even the
question of communicating changed attributes seldom arises in DOd Ord
control. In cases where it happens, such as Next hop change, it was debated
at length earlier in this list if it was proper to unsolicitedly advertise
the changed attributes.
 
 
A better way would be for the egress to withdraw the label. However the
ingress will not issue a request unless it is in Independent control. This
anyway is a problem. My suggestin would be - The ingress after sending a
release can issue a fresh request for the label even if its not in
independent control if it still supports label switching on the FEC. I feel
This would be more cleaner .

[Ramia, Kannan Babu]  How the ingress will know that it need to request
again or initate LSP establishment once again for the same FEC (i mean here
what criteria or conditions it checks before it does this again..) because
in some genuine cases if egress wants to remove the LSP then it may lead to
infinite looping.
[Vijayanand C - CTD, Chennai.] This kind of situation( retrying) will anyway
apply in Independent control( all nodes along the LSP may potentially
retry). So how will you solve the problem in that case ?  What I am
suggesting is if ordered control is used the retry can be done only by the
ingress. Any retry mechanism would have some back off and stopping criteria
associated with it implicitly.
 
 
 
 
 
Vijay 
 

------_=_NextPart_001_01C25F91.67F68120
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DISO-8859-1">


<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 6.00.2716.2200" name=3DGENERATOR>
<META content=3D"Microsoft Word 9" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C25F00.0A4CA8B0" rel=3DFile-List><!--[if gte =
mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in =
1.25in; mso-header-margin: .5in; mso-footer-margin: .5in; =
mso-paper-source: 0; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
P.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
LI.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
DIV.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
SPAN.EmailStyle15 {
	COLOR: black; mso-style-type: personal-compose; mso-ansi-font-size: =
10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
DIV.Section1 {
	page: Section1
}
OL {
	MARGIN-BOTTOM: 0in
}
UL {
	MARGIN-BOTTOM: 0in
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in">
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D841560504-19092002>HI=20
vijay..</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D841560504-19092002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D841560504-19092002>&nbsp;&nbsp;&nbsp; i didnt understand why =
PHP behavior=20
will come in GMPLS..in GMPLS we are using actual resources as our =
labels..so i=20
dont think this case is applicable to GMPLS.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D841560504-19092002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D841560504-19092002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D841560504-19092002>bye</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D841560504-19092002>kb</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> Vijayanand C - =
CTD, Chennai.=20
  [mailto:vijayc@ctd.hcltech.com]<BR><B>Sent:</B> Wednesday, September =
18, 2002=20
  2:49 PM<BR><B>To:</B> Ramia, Kannan Babu<BR><B>Cc:</B>=20
  mpls@uu.net<BR><B>Subject:</B> RE: Clarification on Handling a =
specific event=20
  in LDP<BR><BR></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D878170609-18092002>Again you are overriding the Dod Ord =
control by using=20
  a label map along with a withdraw whereby&nbsp; it becomes an =
unsolicited=20
  mapping.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D878170609-18092002>Apart from the Question of syntactical =
correctness of=20
  sending an unsolicited label map there is another =
problem.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D878170609-18092002>&nbsp;The domain in configured for Dod =
Ord. THis may=20
  be due to constraints in the switches to install labels. For example, =
in=20
  GMPLS, the set of desired labels is sent along with the request =
indicating the=20
  range of labels the upstream can switch onto. Hence the Dod Ord =
control has=20
  significance in such scenarios' and overriding it may cause=20
  confusion.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D878170609-18092002></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D878170609-18092002>The=20
  issue of change in next hop for an FEC right at the egress( which is =
usually=20
  egress for routing domain)&nbsp;is a very rare situation and I think =
it does=20
  nt warrant drastic changes to the semantics and operation of=20
  LDP</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D878170609-18092002></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D878170609-18092002>Vijay</SPAN></FONT></DIV>
  <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px"><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]>
    <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
    size=3D2>-----Original Message-----<BR><B>From:</B> Ramia, Kannan =
Babu=20
    [mailto:kannan.babu.ramia@intel.com]<BR><B>Sent:</B> Wednesday, =
September=20
    18, 2002 2:20 PM<BR><B>To:</B> 'Vijayanand C - CTD, =
Chennai.'<BR><B>Cc:</B>=20
    mpls@uu.net<BR><B>Subject:</B> RE: Clarification on Handling a =
specific=20
    event in LDP<BR><BR></FONT></DIV>
    <DIV><SPAN class=3D040505406-18092002><FONT face=3DArial =
color=3D#0000ff=20
    size=3D2>See my inline Comments</FONT></SPAN></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> Vijayanand C =
- CTD,=20
      Chennai. [mailto:vijayc@ctd.hcltech.com]<BR><B>Sent:</B> =
Wednesday,=20
      September 18, 2002 12:15 PM<BR><B>To:</B> Ramia, Kannan =
Babu<BR><B>Cc:</B>=20
      mpls@uu.net<BR><B>Subject:</B> RE: Clarification on Handling a =
specific=20
      event in LDP<BR><BR></FONT></DIV>
      <DIV><SPAN class=3D821362606-18092002><FONT face=3DArial =
color=3D#0000ff=20
      size=3D2>See my comments inline</FONT></SPAN></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> Ramia, =
Kannan Babu=20
        [mailto:kannan.babu.ramia@intel.com]<BR><B>Sent:</B> Wednesday, =

        September 18, 2002 11:48 AM<BR><B>To:</B> 'Vijayanand C - CTD,=20
        Chennai.'; Ramia, Kannan Babu<BR><B>Cc:</B>=20
        mpls@uu.net<BR><B>Subject:</B> RE: Clarification on Handling a =
specific=20
        event in LDP<BR><BR></FONT></DIV>
        <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
        size=3D2>hi vijay..</FONT></SPAN></DIV>
        <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
        size=3D2>&nbsp;&nbsp; </FONT></SPAN></DIV>
        <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
        size=3D2>thanks for ur reply ..but i still have some thing to =
get=20
        clarified ... please s</FONT></SPAN><SPAN =
class=3D400110906-18092002><FONT=20
        face=3DArial color=3D#0000ff size=3D2>ee in line =
Comments</FONT></SPAN></DIV>
        <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
        size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
        size=3D2>bye</FONT></SPAN></DIV>
        <DIV><SPAN class=3D400110906-18092002><FONT face=3DArial =
color=3D#0000ff=20
        size=3D2>kb</FONT></SPAN></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> =
Vijayanand C - CTD,=20
          Chennai. [mailto:vijayc@ctd.hcltech.com]<BR><B>Sent:</B> =
Wednesday,=20
          September 18, 2002 11:39 AM<BR><B>To:</B> Ramia, Kannan=20
          Babu<BR><B>Cc:</B> mpls@uu.net<BR><B>Subject:</B> RE: =
Clarification on=20
          Handling a specific event in LDP<BR><BR></FONT></DIV>
          <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
          class=3D169422705-18092002>Kannan,</SPAN></FONT></DIV>
          <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
          class=3D169422705-18092002>This is a special case. =
</SPAN></FONT></DIV>
          <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
            <DIV class=3DOutlookMessageHeader dir=3Dltr =
align=3Dleft><SPAN=20
            class=3DEmailStyle15><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></DI=
V>
            <DIV class=3DSection1>
            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial=20
            color=3Dblack size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><![if =
!supportEmptyParas]><![endif]>&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>=

            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial=20
            color=3Dblack size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt">I=20
            have a solution for this=20
problem.<o:p></o:p></SPAN></FONT></SPAN></P>
            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt">Basically=20
            if any LSR receives an Label withdraw message from its =
valid Next=20
            hop neighbor then before propagating to its upstream peers =
it need=20
            to check the value of the label being withdrawn, if the =
label=20
            happens to be an NULL label then it should not propagate =
the label=20
            withdraw to its upstream peers. Now this LSR should now =
assume=20
            itself as an egress for that LSP.<BR><FONT =
color=3D#0000ff><SPAN=20
            class=3D169422705-18092002>[Vijayanand C - CTD, =
Chennai.]&nbsp; What=20
            will happen in valid cases when the eggress actually wants =
to=20
            withdraw label&nbsp;and when u no longer want to switch for =
that FEC=20
            ?The pennultimate hop should&nbsp;not hold&nbsp;the label =
in that=20
            case. How&nbsp;will the Phop know&nbsp;for which case the =
withdraw=20
            applies ?</SPAN><SPAN =
class=3D169422705-18092002>&nbsp;</SPAN><SPAN=20
            class=3D169422705-18092002>&nbsp;</SPAN></FONT><SPAN=20
            class=3D169422705-18092002><FONT =
color=3D#0000ff>&nbsp;<BR><SPAN=20
            =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></FONT></SPAN></P=
>
            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
            class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
            class=3D400110906-18092002>[Ramia, Kannan Babu]&nbsp; =
Actually=20
            here&nbsp;we are not holding the egress label, we are =
sending a=20
            label&nbsp;release for the corresponding&nbsp;withdraw =
message=20
            and&nbsp;also&nbsp;i am expecting only the INGRESS will =
start the=20
            LSP deletion process for any genuine case (of course =
assumption is=20
            all LSR is configured with the forwarding of the label=20
            release)<BR><SPAN class=3D821362606-18092002><BR><FONT=20
            color=3D#0000ff><SPAN class=3D040505406-18092002>[Ramia, =
Kannan=20
            Babu]&nbsp;&nbsp;</SPAN>[Vijayanand C - CTD, =
Chennai.]&nbsp;By=20
            holding the label I mean, the PHop would be holding its =
upstream=20
            labels unnecessarily&nbsp;even in genuine LSP&nbsp;tear =
down=20
            scenarios( when withdraw is received from its downstream =
node which=20
            is egress) =
</FONT></SPAN></SPAN></FONT></SPAN></SPAN></SPAN></P>
            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
            class=3D169422705-18092002><SPAN =
class=3D400110906-18092002><SPAN=20
            class=3D821362606-18092002><FONT color=3D#0000ff>&nbsp;Here =
ingress is=20
            not initiating deletion the egress does it by sending=20
            withdraw.&nbsp;<BR><SPAN=20
            =
class=3D040505406-18092002></SPAN></FONT></SPAN></SPAN></SPAN></SPAN></S=
PAN></P>
            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
            class=3D169422705-18092002><SPAN =
class=3D400110906-18092002><SPAN=20
            class=3D821362606-18092002><FONT color=3D#0000ff><SPAN=20
            class=3D040505406-18092002><FONT color=3D#ff0000>[Ramia, =
Kannan=20
            Babu]&nbsp;&nbsp;I have one more idea =
for&nbsp;differntiating a=20
            genuine withdraw to the special withdraw. i.e if the LSR=20
            A&nbsp;sends a label with draw message to LSR B with =
the&nbsp;FEC-X=20
            and label TLV has label value&nbsp;IMPLICIT NULL and in the =
optinal=20
            paramters it can send a&nbsp;changed label value to be =
used, there=20
            by we can differntiate from the genuine case (in genuine =
case the=20
            optinal paramter wont contain any label)&nbsp;to the =
special case.=20
            if we have this check in the label withdraw procedure it =
will solve=20
            our problem. This solution wont distrub the LSP setup where =
as the=20
            ingress retry solution will distrub the LSP, which=20
            is&nbsp;undesiarable one also we need to provide the =
checking=20
            criteria for re-establishing the=20
            LSP.</FONT></SPAN></FONT></SPAN></SPAN></SPAN><![if =
!supportEmptyParas]><![endif]></SPAN></SPAN></P>
            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial=20
            color=3Dblack size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"></SPAN></FONT></SPAN>&nbsp;</P>
            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial=20
            color=3Dblack size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"></SPAN></FONT></SPAN>&nbsp;</P><![if =
!supportEmptyParas]><![endif]><!--[if supportFields]><font =
color=3Dblack><span=20
style=3D'color:black'><span =
style=3D'mso-element:field-begin'></span><span=20
style=3D"mso-spacerun: yes">&nbsp;</span>AUTOTEXTLIST \s &quot;E-mail=20
Signature&quot; <span =
style=3D'mso-element:field-separator'></span></span></font><![endif]--><=
!--[if supportFields]><font color=3Dblack><span=20
style=3D'color:black'><span =
style=3D'mso-element:field-end'></span></span></font><![endif]-->
            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial=20
            color=3Dblack size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"></SPAN></FONT></SPAN>&nbsp;</P>
            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
face=3DArial=20
            color=3Dblack size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt">&nbsp;<o:p></o:p></SPAN></FONT></SPAN></P>
            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt">Second=20
            one could be there should be a provision to change the =
label for the=20
            particular FEC. I.e any point of time the valid next hop =
LSR can=20
            advertise a change of label for that FEC. Here problems are =
we need=20
            to maintain the context of that advertisement =
(LM).<BR><SPAN=20
            class=3D169422705-18092002><FONT =
color=3D#0000ff>[Vijayanand C - CTD,=20
            Chennai.]&nbsp;&nbsp;This becomes unsolicited=20
            advertisement.<BR><SPAN=20
            =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></FONT></SPAN></P=
>
            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
            class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
            class=3D400110906-18092002>[Ramia, Kannan Babu] i dont see =
any problem=20
            in this kind of advertisement, even if u are configured =
with DOD=20
            ordered mode if any&nbsp;change in hop count or&nbsp;PV, =
the=20
            downstream LSR&nbsp;will anyway generate a LM with out any=20
            outstanding LR.&nbsp;So i want to treat the change in label =
also the=20
            same way as that of change in hop count.<BR><SPAN=20
            class=3D821362606-18092002><FONT =
color=3D#0000ff>[Vijayanand C - CTD,=20
            Chennai.]&nbsp;Changing the&nbsp;attributes of the label =
mapping=20
            (&nbsp;like PV)&nbsp;is different from changing the label =
itself.=20
            Again the context maintenance (old label, FEC) for this is =
a problem=20
            as you said. Even the question of communicating changed =
attributes=20
            seldom arises in DOd Ord control. In cases where it =
happens, such as=20
            Next hop change, it was debated at length earlier in this =
list if it=20
            was proper to unsolicitedly advertise the changed=20
            =
attributes.</FONT></SPAN></SPAN></FONT></SPAN></SPAN></SPAN></P>
            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><FONT=20
            color=3D#0000ff><SPAN=20
            =
class=3D169422705-18092002></SPAN></FONT></SPAN></FONT></SPAN>&nbsp;</P>=

            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><FONT=20
            color=3D#0000ff><SPAN=20
            =
class=3D169422705-18092002></SPAN></FONT></SPAN></FONT></SPAN>&nbsp;</P>=

            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
            class=3D169422705-18092002><FONT color=3D#0000ff>A better =
way would be=20
            for the egress to withdraw the label. However&nbsp;the =
ingress will=20
            not issue a request unless it is in Independent control. =
This=20
            anyway&nbsp;is a&nbsp;problem. My suggestin would be - The =
ingress=20
            after sending a release can issue a fresh request&nbsp;for =
the label=20
            even if its not in independent control if it still supports =
label=20
            switching on the FEC. I feel This&nbsp;would be more =
cleaner=20
            .<BR><SPAN=20
            =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></SPAN></P>
            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
            class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
            class=3D400110906-18092002>[Ramia, Kannan =
Babu]&nbsp;&nbsp;How the=20
            ingress will know that it need to request again or initate =
LSP=20
            establishment once again for the same FEC (i mean here what =
criteria=20
            or conditions it checks before it does this again..) =
because in some=20
            genuine cases if egress wants to remove the LSP&nbsp;then =
it may=20
            lead to infinite looping.<BR><SPAN =
class=3D821362606-18092002><FONT=20
            color=3D#0000ff>[Vijayanand C - CTD, Chennai.]&nbsp;This =
kind of=20
            situation(&nbsp;retrying)&nbsp;will anyway apply in =
Independent=20
            control( all nodes along the LSP may potentially retry). =
So&nbsp;how=20
            will you solve the problem in that case ? &nbsp;What I am =
suggesting=20
            is if ordered control is used the retry can be done only by =
the=20
            ingress. Any retry mechanism would have some back off and =
stopping=20
            criteria associated with it=20
            =
implicitly.</FONT></SPAN></SPAN></FONT></SPAN></SPAN></SPAN></P>
            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
            class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
            =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></SPAN>&nbsp;</P>=

            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
            class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
            =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></SPAN>&nbsp;</P>=

            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
            class=3D169422705-18092002><FONT color=3D#ff0000><SPAN=20
            =
class=3D400110906-18092002></SPAN></FONT></SPAN></SPAN></SPAN>&nbsp;</P>=

            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
            =
class=3D169422705-18092002></SPAN></SPAN></FONT></SPAN>&nbsp;</P>
            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
            =
class=3D169422705-18092002></SPAN></SPAN></FONT></SPAN>&nbsp;</P>
            <P class=3DMsoNormal><SPAN class=3DEmailStyle15><FONT =
color=3Dblack><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; =
mso-bidi-font-size: 12.0pt"><SPAN=20
            class=3D169422705-18092002></SPAN><SPAN =
class=3D169422705-18092002><FONT=20
            =
color=3D#0000ff>Vijay</FONT></SPAN>&nbsp;<o:p></o:p></SPAN></FONT></SPAN=
></P>
            <P class=3DMsoNormal><FONT color=3Dblack><SPAN =
style=3D"COLOR: black"><![if =
!supportEmptyParas]><![endif]>&nbsp;</SPAN></FONT><FONT=20
            face=3DArial color=3D#0000ff size=3D2><SPAN=20
            style=3D"COLOR: black; mso-color-alt: =
windowtext"><o:p></o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BLOCKQUOTE=
></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C25F91.67F68120--


From owner-mpls@UU.NET  Thu Sep 19 03:27:42 2002
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 ESMTP id DAA22699
	for <mpls-archive@lists.ietf.org>; Thu, 19 Sep 2002 03:27:42 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngyn27406
	for <mpls-archive@lists.ietf.org>; Thu, 19 Sep 2002 07:29:26 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngyn27151;
	Thu, 19 Sep 2002 07:29:20 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngyn20240
	for mpls-outgoing; Thu, 19 Sep 2002 07:29:00 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQngyn20235
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 19 Sep 2002 07:28: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 QQngyn19519
	for <mpls@UU.NET>; Thu, 19 Sep 2002 07:28:38 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngyn04132
	for <mpls@UU.NET>; Thu, 19 Sep 2002 07:28:37 GMT
Received: from mailhost.metro-optix.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [64.219.248.6])
	id QQngyn04124
	for <mpls@UU.NET>; Thu, 19 Sep 2002 07:28:37 GMT
Received: by mailhost.metro-optix.com with Internet Mail Service (5.5.2653.19)
	id <SPWD4V7N>; Thu, 19 Sep 2002 02:26:16 -0500
Message-ID: <99EC34181384D611BE56000347227B2C0728BE@MAILHOSTNB>
From: Khuzema Pithewan <khuzema.pithewan@metro-optix.com>
To: "Mpls (E-mail)" <mpls@UU.NET>, "Ccamp (E-mail)" <ccamp@ops.ietf.org>
Subject: Downstream label in  ERO
Date: Thu, 19 Sep 2002 02:28:04 -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

Hi,

draft-ietf-mpls-generalized-rsvp-te-08 , While talking about Explicit Label
control in ERO, it says..

"If the U-bit of the subobject being examined is set (1), then value
   of the label is label to be used for upstream traffic associated with
   the bidirectional LSP.  If this label is not acceptable, a "Bad
   EXPLICIT_ROUTE object" error SHOULD be generated."

and 

"If the U-bit of the subobject being examined is clear (0), then value of
the label is copied into a new Label_Set object."

what if the downstream label in sub-object (with U-Bit cleared, getting
copied in Label_Set ) is not acceptable? 
Do we need to generate "BAD EXPLICIT_ROUTE object" error for that also?

Regards,
Khuzema.




From owner-mpls@UU.NET  Thu Sep 19 07:23:30 2002
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 ESMTP id HAA29875
	for <mpls-archive@lists.ietf.org>; Thu, 19 Sep 2002 07:23:29 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngzd08448
	for <mpls-archive@lists.ietf.org>; Thu, 19 Sep 2002 11:25:14 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngzd08178;
	Thu, 19 Sep 2002 11:25:08 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngzd12400
	for mpls-outgoing; Thu, 19 Sep 2002 11:24:44 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQngzd12395
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 19 Sep 2002 11:24: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 QQngzd17704
	for <mpls@UU.NET>; Thu, 19 Sep 2002 11:23:08 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngzd23713
	for <mpls@UU.NET>; Thu, 19 Sep 2002 11:23:07 GMT
Received: from relay2.clb.oleane.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: relay2.clb.oleane.net [213.56.31.22])
	id QQngzd23696
	for <mpls@UU.NET>; Thu, 19 Sep 2002 11:23:06 GMT
Received: from chantal ([194.250.212.114]) 
	by relay2.clb.oleane.net with SMTP id g8JBN53u026523
	for <mpls@UU.NET>; Thu, 19 Sep 2002 13:23:06 +0200
Message-ID: <007501c25fcf$572e0d20$0701a8c0@upperside>
From: "Peter Lewis" <peter.lewis@upperside.fr>
To: <mpls@UU.NET>
Subject: MPLS World Congress 2003
Date: Thu, 19 Sep 2002 13:26:03 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0071_01C25FE0.1A59C900"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.

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


We are pleased to inform you that the MPLS World Congress 2003's Schedule is
now online:
http://www.upperside.fr/mplswc2003/mplswc03pro.htm

Please notice that the Early Bird Registration is still going on and that
you can now benefit from a 20% discount until the 1st of November 2002.
To register please visit:
http://www.upperside.fr/mplswc2003/mplswc03earlyreg.htm

More info: www.upperside.fr

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>&nbsp;=20
<DIV><FONT face=3DArial>We are pleased to inform you that the MPLS World =
Congress=20
2003's Schedule is now online:</FONT></DIV>
<DIV><FONT face=3DArial><A=20
href=3D"http://www.upperside.fr/mplswc2003/mplswc03pro.htm">http://www.up=
perside.fr/mplswc2003/mplswc03pro.htm</A></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D3>
<DIV><FONT face=3DArial>
<DIV><FONT face=3DArial>Please notice that the Early Bird Registration =
is still=20
going on and that you can now benefit from <STRONG>a 20% discount =
</STRONG>until=20
the <U>1st of November 2002</U>. </FONT></DIV>
<DIV><FONT face=3DArial>To register please visit: </FONT><A=20
href=3D"http://www.upperside.fr/mplswc2003/mplswc03earlyreg.htm">http://w=
ww.upperside.fr/mplswc2003/mplswc03earlyreg.htm</A></DIV></FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>
<DIV><FONT size=3D2>More info: <A=20
href=3D"http://www.upperside.fr">www.upperside.fr</A></FONT></DIV></FONT>=
</DIV></FONT></DIV></BODY></HTML>

------=_NextPart_000_0071_01C25FE0.1A59C900--



From owner-mpls@UU.NET  Thu Sep 19 11:17:57 2002
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 ESMTP id LAA09426
	for <mpls-archive@lists.ietf.org>; Thu, 19 Sep 2002 11:17:56 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngzt10985
	for <mpls-archive@lists.ietf.org>; Thu, 19 Sep 2002 15:19:41 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQngzt10745;
	Thu, 19 Sep 2002 15:19:33 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQngzt12813
	for mpls-outgoing; Thu, 19 Sep 2002 15:19:16 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQngzt12806
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 19 Sep 2002 15:19: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 QQngzt18465
	for <mpls@uu.net>; Thu, 19 Sep 2002 15:19:05 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngzt27434
	for <mpls@uu.net>; Thu, 19 Sep 2002 15:19:05 GMT
Received: from funnel.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQngzt27430
	for <mpls@uu.net>; Thu, 19 Sep 2002 15:19:04 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id LAA17831 for <mpls@uu.net>; Thu, 19 Sep 2002 11:19:04 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8JFJ4F27586 for mpls@uu.net; Thu, 19 Sep 2002 11:19:04 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQngzt12724
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 19 Sep 2002 15:17: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 QQngzt14357
	for <mpls@UU.NET>; Thu, 19 Sep 2002 15:17:44 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQngzt16241
	for <mpls@UU.NET>; Thu, 19 Sep 2002 15:17:44 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 QQngzt16232
	for <mpls@UU.NET>; Thu, 19 Sep 2002 15:17: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 LAA19135
	for <mpls@UU.NET>; Thu, 19 Sep 2002 11:17:42 -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 LAA12733
	for <mpls@UU.NET>; Thu, 19 Sep 2002 11:17:42 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <S8R7BQNF>; Thu, 19 Sep 2002 11:17:42 -0400
Message-ID: <313680C9A886D511A06000204840E1CF092510@whq-msgusr-02.pit.comms.marconi.com>
From: "Ren, Liwei" <Liwei.Ren@marconi.com>
To: "'mpls@UU.NET'" <mpls@UU.NET>
Subject: Subscribe
Date: Thu, 19 Sep 2002 11:17:36 -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

Subscribe 




From owner-mpls@UU.NET  Fri Sep 20 07:55:25 2002
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 ESMTP id HAA19297
	for <mpls-archive@lists.ietf.org>; Fri, 20 Sep 2002 07:55:25 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhcx18966
	for <mpls-archive@lists.ietf.org>; Fri, 20 Sep 2002 11:57:12 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnhcx18717;
	Fri, 20 Sep 2002 11:57:05 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnhcx10856
	for mpls-outgoing; Fri, 20 Sep 2002 11:56:37 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQnhcx10851
	for <mpls@mail-control.ash.ops.us.uu.net>; Fri, 20 Sep 2002 11:56:27 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 QQnhcx21752
	for <mpls@uu.net>; Fri, 20 Sep 2002 11:56:02 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhcx00819
	for <mpls@uu.net>; Fri, 20 Sep 2002 11:56:02 GMT
Received: from funnel.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnhcx00782
	for <mpls@uu.net>; Fri, 20 Sep 2002 11:56:02 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id HAA21081 for <mpls@uu.net>; Fri, 20 Sep 2002 07:56:01 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8KBu1C14602 for mpls@uu.net; Fri, 20 Sep 2002 07:56:01 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQnhcx10655
	for <mpls@mail-control.ash.ops.us.uu.net>; Fri, 20 Sep 2002 11:55: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 QQnhcx13991
	for <mpls@uu.net>; Fri, 20 Sep 2002 11:55:02 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhcx29913
	for <mpls@uu.net>; Fri, 20 Sep 2002 11:55:02 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 QQnhcx29906
	for <mpls@uu.net>; Fri, 20 Sep 2002 11:55:02 GMT
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19153;
	Fri, 20 Sep 2002 07:53:13 -0400 (EDT)
Message-Id: <200209201153.HAA19153@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-ldp-restart-05.txt
Date: Fri, 20 Sep 2002 07:53:12 -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		: Graceful Restart Mechanism for LDP
	Author(s)	: M. Leelanivas, Y. Rekhter, R. Aggarwal
	Filename	: draft-ietf-mpls-ldp-restart-05.txt
	Pages		: 12
	Date		: 2002-9-19
	
This document describes a mechanism that helps to minimize the
negative effects on MPLS traffic caused by Label Switching Router's
(LSR's) control plane restart, and specifically by the restart of its
Label Distribution Protocol (LDP) component, on LSRs that are capable
of preserving the MPLS forwarding component across the restart.
The mechanism described in this document is applicable to all LSRs,
both those with the ability to preserve forwarding state during LDP
restart and those without (although the latter need to implement only
a subset of the mechanism described in this document).  Supporting (a
subset of) the mechanism described here by the LSRs that can not
preserve their MPLS forwarding state across the restart would not
reduce the negative impact on MPLS traffic caused by their control
plane restart, but it would minimize the impact if their neighbor(s)
are capable of preserving the forwarding state across the restart of
their control plane and implement the mechanism described here.
The mechanism makes minimalistic assumptions on what has to be
preserved across restart - the mechanism assumes that only the actual
MPLS forwarding state has to be preserved; the mechanism does not
require any of the LDP-related state to be preserved across the
restart.
The procedures described in this document apply to downstream
unsolicited label distribution. Extending these procedures to
downstream on demand label distribution is for further study.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mpls-ldp-restart-05.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:	<2002-9-19154758.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mpls-ldp-restart-05.txt

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

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

--OtherAccess--

--NextPart--




From owner-mpls@UU.NET  Mon Sep 23 09:53:57 2002
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 ESMTP id JAA09077
	for <mpls-archive@lists.ietf.org>; Mon, 23 Sep 2002 09:53:57 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhoh13771
	for <mpls-archive@lists.ietf.org>; Mon, 23 Sep 2002 13:55:46 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnhoh13578;
	Mon, 23 Sep 2002 13:55:41 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnhoh07109
	for mpls-outgoing; Mon, 23 Sep 2002 13:55:19 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnhoh07100
	for <mpls@mail-control.ash.ops.us.uu.net>; Mon, 23 Sep 2002 13:55: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 QQnhoh19311
	for <mpls@uu.net>; Mon, 23 Sep 2002 13:55:14 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhoh23344
	for <mpls@uu.net>; Mon, 23 Sep 2002 13:55:13 GMT
Received: from blooper.utfors.se by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail.utfors.se [195.58.103.125])
	id QQnhoh23331
	for <mpls@uu.net>; Mon, 23 Sep 2002 13:55:13 GMT
Received: from utfors.se (nat-sto.utfors.se [212.73.0.237])
	by blooper.utfors.se (8.12.6/8.12.6) with ESMTP id g8NDsstA020385;
	Mon, 23 Sep 2002 15:54:55 +0200 (MEST)
Message-ID: <3D8F1D2F.6060401@utfors.se>
Date: Mon, 23 Sep 2002 15:54:55 +0200
From: Loa Andersson <loa.andersson@utfors.se>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3
X-Accept-Language: en-us
MIME-Version: 1.0
To: MPLS wg <mpls@UU.NET>
CC: George Swallow <swallow@cisco.com>, Bert Wijnen <bwijnen@lucent.com>,
        Scott Bradner <sob@harvard.edu>
Subject: Open MIB review meeting - November 16th
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit

All,


At the MPLS Working Group meeting in Yokohama Bert Wijnen presented
the experiences from the MIB doctor reviews of the MPLS MIBs. It is
our feeling that there still is some way to go before we have the
consensus on MIBs and the MIB structure we need.

The WG chairs and the AD for O&M Bert Wijnen has decided to call a
MIB meeting meeting in Atlanta with participation from the main MIB
MPLS authors, MIB implementors and people from the MIB Doctors team.

At the meeting the individual MIBs will be reviewed to some extent,
but the main focus on this meeting should be on that the MPLS MIBs as
a group has an internal logic and consistency.

We therefore suggest an open meeting on the Saturday before the next
IETF meeting (November 16th) in Atlanta.

There will a further mail with venue and other meeting information
sent out shortly. There will also be mail requesting some information
on MIB implementation and deployment.

/Loa, George and Bert

-- 
     Loa Andersson
     Chief Architect,
     Utfors Research, Architecture and Future Lab (URAX)
     Utfors AB
     R錽undav鋑en 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 Sep 23 10:46:05 2002
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 ESMTP id KAA11138
	for <mpls-archive@lists.ietf.org>; Mon, 23 Sep 2002 10:46:04 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhol00713
	for <mpls-archive@lists.ietf.org>; Mon, 23 Sep 2002 14:47:54 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnhol00549;
	Mon, 23 Sep 2002 14:47:50 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnhol27477
	for mpls-outgoing; Mon, 23 Sep 2002 14:47:26 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQnhol27472
	for <mpls@mail-control.ash.ops.us.uu.net>; Mon, 23 Sep 2002 14:47: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 QQnhol27086
	for <mpls@uu.net>; Mon, 23 Sep 2002 14:46:21 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhol29699
	for <mpls@uu.net>; Mon, 23 Sep 2002 14:46:21 GMT
Received: from mail.san.yahoo.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail.san.yahoo.com [209.132.1.30])
	id QQnhol29694
	for <mpls@uu.net>; Mon, 23 Sep 2002 14:46:20 GMT
Received: from [65.213.193.52] by mail.san.yahoo.com with HTTP; Mon, 23 Sep 2002 07:49:30 -0700
Date: Mon, 23 Sep 2002 10:49:30 -0400
Message-ID: <3D87C44500004DB8@mta08.san.yahoo.com>
From: "Kavita Khanna" <kkhanna@isocore.com>
Subject: MPLS 2002 (www.mpls2002.com): Oct 27-29, Wash, DC
To: mpls@UU.NET
MIME-Version: 1.0
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 KAA11138

Friends,

The leading service providers, major networking and test equipment vendors,
and many IETF contributors will gather at MPLS 2002, October 27-29, in Washington,
DC, in the Omni Shoreham Hotel (http://www.mpls2002.com).

This unique international event, which is in its 5th year, is hosted by
Worldcom, Cable & Wireless, France Telecom, NTT and Isocore; and sponsored
by industry leaders such as Alcatel, Avici Systems, Cisco Systems, CoSine
Communications, Laurel Networks, Lucent, Nortel Networks, Redback Networks;
IXIA, NetTest, and Spirent Communications. The exhibits will be open throughout
Monday and Tuesday. There will be new product or software feature announcements.
Prominent members of the press and well-regarded industry analysts will
also be present at MPLS 2002.

MPLS 2002 consists of a two-day highly technical sessions, six technical
tutorials and exhibits. The technical sessions offer an excellent blend
of topics including deployment, application, and management aspects of MPLS
(please visit "Program" section http://www.mpls2002.com/sessions.htm). The
event will be followed by the third public MPLS Interoperability demo, on
October 30. Major vendors will showcase interoperability of their MPLS-based
leading-edge features on their core and edge routers.

We hope you would be able to actively participate in the MPLS 2002 International
Conference. You may register (on-line or off-line) for MPLS 2002 by visiting
http://www.mpls2002.com/registration.htm and following the instructions.
The reduced registration fees, currently in effect, are extremely attractive.


If you are planning to attend MPLS 2002, please make your hotel reservations
at the Omni Shoreham Hotel immediately, as only a limited number of rooms,
blocked for the conference at special rates, are left. You may visit (http://www.mpls2002.com/hotels.htm)
for more information on hotel reservations.

To celebrate the 5th anniversary of this series, all participants will receive
the conference proceedings from previous years MPLS1998, MPLS1999, MPLS2000,
MPLS2001) in addition to MPLS 2002 presentations on a CD. We look forward
to seeing you at MPLS 2002, in Washington, DC.

Regards,
MPLS 2002 Team



From owner-mpls@UU.NET  Mon Sep 23 11:35:16 2002
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 ESMTP id LAA12973
	for <mpls-archive@lists.ietf.org>; Mon, 23 Sep 2002 11:35:15 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhoo25373
	for <mpls-archive@lists.ietf.org>; Mon, 23 Sep 2002 15:37:05 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnhoo24978;
	Mon, 23 Sep 2002 15:36:53 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnhoo17666
	for mpls-outgoing; Mon, 23 Sep 2002 15:36:26 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQnhoo17661
	for <mpls@mail-control.ash.ops.us.uu.net>; Mon, 23 Sep 2002 15:36: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 QQnhoo20964
	for <mpls@UU.NET>; Mon, 23 Sep 2002 15:35:39 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhoo06073
	for <mpls@UU.NET>; Mon, 23 Sep 2002 15:35:39 GMT
Received: from evita3.cs.fredonia.edu by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: evita2.cs.fredonia.edu [141.238.30.15])
	id QQnhoo06066
	for <mpls@UU.NET>; Mon, 23 Sep 2002 15:35:39 GMT
Received: from zubairi (zubairi.cs.fredonia.edu [141.238.30.211])
	by evita3.cs.fredonia.edu (8.10.2/8.10.2) with SMTP id g8NFZXG14522
	for <mpls@UU.NET>; Mon, 23 Sep 2002 11:35:34 -0400
Message-ID: <00ce01c26317$4747f150$d31eee8d@zubairi>
Reply-To: "Junaid Ahmed Zubairi" <zubairi@cs.fredonia.edu>
From: "Junaid Ahmed Zubairi" <zubairi@cs.fredonia.edu>
To: <mpls@UU.NET>
References: <3D87C44500004DB8@mta08.san.yahoo.com>
Subject: ATS2003: CFP for New Track on Traffic Engineering
Date: Mon, 23 Sep 2002 11:38:31 -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.2919.6700
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Greetings,

Please participate in the new traffic engineering track
in ATS2003 (Orlando, Florida) by contributing your
papers:

Full CFP is below:

*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^*^

CALL FOR PAPERS
Track on Traffic Engineering With Protocols and Devices
in
Applied Telecommunication Symposium (ATS)
Part of the 2003 Advanced Simulation Technologies Conference (ASTC 2003)
March 30 through April 3, 2003
Hyatt Orlando Hotel, Orlando, FL, USA

The Applied Telecommunication Symposium (ATS) is an international forum for
exchange of technical knowledge and presentation of original papers on the
analysis of telecommunication systems and technologies. It is intended for
professionals, engineers, software developers, managers, and others
interested in cellular and packet traffic characteristics, analysis of
telecommunication networks, and practitioners operating telecommunication
networks. We are looking for innovative technical papers describing
projects, applications, and research and development work pertinent to
telecommunication. The following tracks (with track chairs listed) will be
held; the topics are representative of the track, but are not necessarily
exclusive to that track:

Wireless
Chairs - Dr. Hassan Rajaei, Bowling Green State University
Dr. Mohsen Guizani, University of West Florida
-CDMA
-UMTS
-GSM
-2.5G/3G Wireless
-Wireless Data
-Cell Traffic
-Network Performance and Engineering

Telecommunications Business and Regulation
Chair - Dr. George Kraft, Stuart School of Business, Illinois Institute of
Technology
-Cost modeling
-Call center operations
-Billing models
-E-commerce

Measurements
Chair - Dr. Shakil Akhtar, UAE University, Al-Ain, United Arab Emirates
-Measured Internet Traffic Characteristics
-Wireless Traffic Characteristics
-Observed Problems with Current Packet Switching Protocols
-Tools

Network Management and Security
Chair - Dr. Axel Lehmann, Universitaet der Bundeswehr Muenchen
-Operations, Administration, Maintenance
-Overload control
-Load balancing
-Influence of security measures on network performance

Networks and Multimedia
Chairs - Dr. Aftab Ahmad, DePaul University
-Internet
-Network performance
-Traffic characterization
-Packet switch architecture evaluation

Modeling Techniques
Chair - Kamala Murti, Lucent Technologies, Inc.
-Simulation techniques
-Acceleration methods
-Traffic synthesis
-Combined simulation/analytic procedures

*Traffic Engineering with Protocols and Devices
Chair - Dr. Junaid Zubairi, SUNY at Fredonia
-Traffic Management and control
-Traffic engineering architectures
-Bandwidth management
-GMPLS

Three copies of a 300 word abstract or a draft paper should be submitted to
the session organizers by November 1, 2002. Please indicate for which
track(s) you wish to have your paper considered for; note that the final
track selection will be at the discretion of the ATS organizers. The
abstract must include the author(s), e-mail address(es), and affiliation.
Abstracts may be submitted electronically to
http://scs.proceedingscentral.com or directly to:

Dr. Bohdan Bodnar, ATS Chair, Motorola, USA,
bbodnar1@motorola.com,  or to

Dr. Ariel Sharon, Lucent Technologies, Inc.,
E-mail: asharon@lucent.com.

Further information is available at
http://www.scs.org/confernc/astc/astc03/cfp/ats03.htm

Deadlines
Abstract/Draft paper dueNovember 1, 2002
Notification of acceptance sentNovember 30, 2002
Camera-ready paper dueJanuary 31, 2003

Conference Committee
General Chair
Dr. Bohdan Bodnar
Motorola, Inc.
bbodnar1@motorola.com

Co-Chair
Dr. Ariel Sharon
Lucent Technologies, Inc.
asharon@lucent.com

Program Chair
Dr. George Kraft
Illinois Institute of Technology

Sponsored by The Society for Modeling and Simulation International
P.O. Box 17900
San Diego, CA 92177-7900
Tel 858-277-3888
Fax: 858-277-3930
E-mail scs@scs.org
http://www.scs.org



* For more information on the Traffic Engineering track, please contact the
track chair at the following address:
Dr. Junaid Ahmed Zubairi
Department of Mathematics and Computer Science
College at Fredonia, State University of New York
Fredonia, NY 14063, USA

Tel: +1-716-673-4694
Fax: +1-508-256-8324
Email: zubairi@cs.fredonia.edu

WWW: http://www.cs.fredonia.edu/~zubairi




From owner-mpls@UU.NET  Wed Sep 25 13:55:07 2002
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 ESMTP id NAA04605
	for <mpls-archive@lists.ietf.org>; Wed, 25 Sep 2002 13:55:07 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhwh28934
	for <mpls-archive@lists.ietf.org>; Wed, 25 Sep 2002 17:56:56 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnhwh28699;
	Wed, 25 Sep 2002 17:56:48 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnhwh22992
	for mpls-outgoing; Wed, 25 Sep 2002 17:56:21 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQnhwh22985
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 25 Sep 2002 17:56: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 QQnhwh00973
	for <mpls@uu.net>; Wed, 25 Sep 2002 17:56:05 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhwh04993
	for <mpls@uu.net>; Wed, 25 Sep 2002 17:56:04 GMT
Received: from funnel.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnhwh04980
	for <mpls@uu.net>; Wed, 25 Sep 2002 17:56:04 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id NAA13860 for <mpls@uu.net>; Wed, 25 Sep 2002 13:56:03 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8PHu3u03946 for mpls@uu.net; Wed, 25 Sep 2002 13:56:03 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQnhwh22942
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 25 Sep 2002 17:55: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 QQnhwh10913
	for <mpls@uu.net>; Wed, 25 Sep 2002 17:53:57 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhwh03537
	for <mpls@uu.net>; Wed, 25 Sep 2002 17:53:57 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 QQnhwh03528
	for <mpls@uu.net>; Wed, 25 Sep 2002 17:53:56 GMT
Received: by miles.datcon.co.uk with Internet Mail Service (5.5.2656.59)
	id <PTR7HLNR>; Wed, 25 Sep 2002 18:53:48 +0100
Message-ID: <37701240971DD31193970000F6CCB9F702E282E6@duke.datcon.co.uk>
From: John Salloway <JS@dataconnection.com>
To: "'rhthomas@cisco.com'" <rhthomas@cisco.com>
Cc: "'loa.andersson@utfors.se'" <loa.andersson@utfors.se>,
        "'swallow@cisco.com'" <swallow@cisco.com>,
        "'mpls@uu.net'" <mpls@UU.NET>
Subject: LDP to Draft Standard - implementation survey
Date: Wed, 25 Sep 2002 18:53:54 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Bob,

Attached is Data Connection's response to the LDP to Draft Standard -
implementation survey.

Regards

John Salloway
Network Protocols Group 
Data Connection Ltd 
Tel: +44 20 8366 1177 
Fax: +44 20 8363 1468 
EMail: mailto:js@dataconnection.com
Web: http://www.dataconnection.com/




-----Original Message-----
From: Loa Andersson [mailto:loa.andersson@utfors.se]
Sent: 13 August 2002 16:18
To: MPLS wg
Cc: George Swallow; Loa Andersson; Bob Thomas; Scott Bradner
Subject: LDP to Draft Standard - implementation survey


LDP to Draft Standard

  As protocols gets implemented and deployed, there is an IETF process
  to take them further on the standrads track. LDP is a protocol that
  has been both widely implemented and deployed, we will therefore
  start the process to progress LDP to Draft Standard.

  Included is an "LDP Implemenation Survey Form", it specifies in
  some detail the information needed to take this step. We ask
  companies and other organizations that have implemented LDP to take
  the time and answer the questions. The result of the survey will
  be made available as an Internet Draft, the time schedule depends
  very much on that we have the responses in a timely fashion.

  Send the response to the Bob Thomas, who will act as Internet Draft
  editor for the resulting summary document:

  rhthomas@cisco.com


  with a Cc to the wg chairs and the mpls list:

  loa.andersson@utfors.se
  swallow@cisco.com
  mpls@uu.net


  Earlier experiences with this kind of survey indicates that there
  are always a few that likes to respond anonymously, if you want to
  do that send the response to our AD, Scott Bradner:

  sob@harvard.edu

  We want to stress the importance of getting the highest possible
  number of responses, since it is important to create a protocol
  specification of highest possible quality. If there are further
  questions contact the wg chairs.

    Loa and George

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




LDP Implementation Survey Form [V 1.0]

The purpose of this form is to gather information about implementations
of LDP as defined by RFC3036.  The information is being requested as
part of the process of advancing LDP from Proposed to Draft Standard.

The form is patterned after the implementation report form used
for HTTP/1.1; see:

   http://www.ietf.org/IESG/Implementations/http1.1-implementations.txt

=======================================================================
A. General information.

Please provide the following information.
----------------------------------------------------------------

Organization:			Data Connection Ltd

Organization url(s):		www.dataconnection.com

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

Product title(s):		DC-MPLS
	
Brief description(s):	DC-MPLS is a full function MPLS software 
				implementation which supports RSVP-TE,
CR-LDP, and LDP.

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

Contact for LDP information
    Name:				Ben Miller
    Title:				VP sales and marketing

    E-mail:				bmm@dataconnection.com
    Organization/department:	Data Connection Ltd
    Postal address:			100 Church St, Enfield, Middlesex,
EN2 6BQ, United Kingdom
    Phone:				+44 20 8366 1177
    Fax:				+44 20 8363 1468	


=======================================================================
B. LDP Implementation Status, Availability, Origin

Please check [x] the boxes that apply.
----------------------------------------------------------------

Status:
      [ ]  Development
      [ ]  Alpha
      [ ]  Beta
      [X]  Product
      [ ]  Other (describe):

Availability
      [ ]  Public and free
      [ ]  Only to selected organizations/companies but free
      [X]  On sale.
      [ ]  For internal company use only
      [ ]  Other:

Implementation based on:  (check all that apply)
      [ ]  Purchased code
           (please list source if possible)
      [ ]  Free code
           (please list source if possible)
      [X]  Internal implementation
           (no outside code, just from specs)
      [ ]  Internal implementation on top of purchased
           or free code
           List portions from external source:
           List portions developed internally:


=======================================================================
C. LDP Feature Survey.

For each features listed, please indicate the Status of the implementation
using one of the following:

     't'   tested against another independent implementation
     'y'   implemented but not tested against independent implementation
     'n'   not implemented
     '-'   not applicable to this type of implementation

     Optional: For 'n' status, indicate reason not implemented using
               one of the following:

             's'  RFC specification inadequate, unclear, or confusing
             'u'  utility of feature unclear
             'r'  feature not required for feature set implemented

------------------+-----------------------------+-------------------------
                   |                             | Status (one of t, y, n -
                   |                             |   If n, optionally one of
Feature           | RFC3036 Section(s)          |   s, u, r)
==================+=============================+=========================
Interface types   | 2.2.1, 2.5.3, 2.8.2, 3,4,2
   ----------------+-----------------------------+-------------------------
   Packet          |                             |			t
   ----------------+-----------------------------+-------------------------
   Frame Relay     |                             |			y
   ----------------+-----------------------------+-------------------------
   ATM             |                             |			t
==================+=============================+=========================
Label Spaces      | 2.2.1, 2.2.2
   ----------------+-----------------------------+-------------------------
   Per platform    |                             |			t
   ----------------+-----------------------------+-------------------------
   Per interface   |                             |			t
==================+=============================+=========================
LDP Discovery     | 2.4
   ----------------+-----------------------------+-------------------------
   Basic           | 2.4.1                       |			t
   ----------------+-----------------------------+-------------------------
   Targeted        | 2.4.2                       |			t
------------------+-----------------------------+-------------------------
LDP Sessions      | 2.2.3
   ----------------+-----------------------------+-------------------------
   Directly        | --                          |			t
   Connected       |                             |
   ----------------+-----------------------------+-------------------------
   Targeted        | 2.3                         |			t
==================+=============================+=========================
LDP Modes         | 2.6
   ----------------+-----------------------------+-------------------------
   DU, Ind cntl,   | 2.6                         |
   Lib retention   |                             |			t
   ----------------+-----------------------------+-------------------------
   DU, Ord cntl,   | 2.6                         |
   Lib retention   |                             |			t
   ----------------+-----------------------------+-------------------------
   DU, Ind cntl,   | 2.6                         |
   Cons retention  |                             |			t
   ----------------+-----------------------------+-------------------------
   DU, Ord cntl,   | 2.6                         |
   Cons retention  |                             |			t
   ----------------+-----------------------------+-------------------------
   DoD, Ind cntl,  | 2.6                         |
   Lib retention   |                             |			y
   ----------------+-----------------------------+-------------------------
   DoD, Ord cntl,  | 2.6                         |
   Lib retention   |                             |			y
   ----------------+-----------------------------+-------------------------
   DoD, Ind cntl,  | 2.6                         |
   Cons retention  |                             |			t
   ----------------+-----------------------------+-------------------------
   DoD, Ord cntl,  | 2.6                         |
   Cons retention  |                             |			t
==================+=============================+=========================
Loop Detection    | 2.8                         |			t
==================+=============================+=========================
TCP MD5 Option    | 2.9                         |			n
r
==================+=============================+=========================
LDP TLVs          | 3.3, 3.4, throughout
   ----------------+-----------------------------+-------------------------
   U-bit           | 3.3                         |			t
   ----------------+-----------------------------+-------------------------
   F-bit           | 3.3                         |			t
------------------+-----------------------------+-------------------------
   FEC             | 1., 2.1, 3.4.1              |			t
   ----------------+-----------------------------+-------------------------
     Wildcard      | 3.4.1                       |			y
   ----------------+-----------------------------+-------------------------
     Prefix        | 2.1, 3.4.1                  |			t
   ----------------+-----------------------------+-------------------------
     Host          | 2.1, 3.4.1                  |			t
------------------+-----------------------------+-------------------------
   Address List    | 3.4.3                       |			t
------------------+-----------------------------+-------------------------
   Hop Count       | 3.4.4                       |			t
------------------+-----------------------------+-------------------------
   Path Vector     | 3.4.5                       |			t
------------------+-----------------------------+-------------------------
   Generic Label   | 3.4.2.1                     |			t
------------------+-----------------------------+-------------------------
   ATM Label       | 3.4.2.2                     |			t
------------------+-----------------------------+-------------------------
   Frame Relay     | 3.4.2.3                     |			y
   Label           |                             |
------------------+-----------------------------+-------------------------
   Status          | 3.4.6                       |			t
------------------+-----------------------------+-------------------------
   Extended Status | 3.5.1                       |			t
------------------+-----------------------------+-------------------------
   Returned PDU    | 3.5.1                       |			t
------------------+-----------------------------+-------------------------
   Returned Message| 3.5.1                       |			t
------------------+-----------------------------+-------------------------
   Common Hello    | 3.5.2                       |			t
   Parameters      |                             |
   ----------------+-----------------------------+-------------------------
     T-bit         | 3.5.2                       |			t
   ----------------+-----------------------------+-------------------------
     R-bit         | 3.5.2                       |			t
   ----------------+-----------------------------+-------------------------
     Hold Time     | 3.5.2                       |			t
------------------+-----------------------------+-------------------------
   IPv4 Transport  | 3.5.2                       |			t
   Address         |                             |
------------------+-----------------------------+-------------------------
   Configuration   | 3.5.2                       |			t
   Sequence Number |                             |
------------------+-----------------------------+-------------------------
   IPv6 Transport  | 3.5.2                       |			n  r

   Address         |                             |
------------------+-----------------------------+-------------------------
   Common Session  | 3.5.3                       |			t
   Parameters      |                             |
   ----------------+-----------------------------+-------------------------
     KeepAlive Time| 3.5.3                       |			t
   ----------------+-----------------------------+-------------------------
     PVLim         | 3.5.3                       |			t
   ----------------+-----------------------------+-------------------------
     Max PDU Length| 3.5.3                       |			t
------------------+-----------------------------+-------------------------
   ATM Session     | 3.5.3                       |			t
   Parameters      |                             |
   ----------------+-----------------------------+-------------------------
     M values      |                             |			t
       0 No Merge  | 3.5.3                       |
       ------------+-----------------------------+-------------------------
       1 VP Merge  | 3.5.3                       |			t
       ------------+-----------------------------+-------------------------
       2 VC Merge  | 3.5.3                       |			t
       ------------+-----------------------------+-------------------------
       3 VP &      | 3.5.3                       |			t
         VC Merge  |                             |
   ----------------+-----------------------------+-------------------------
     D-bit         | 3.5.3                       |			t
   ----------------+-----------------------------+-------------------------
     ATM Label     | 3.5.3                       |			t
     Range         |                             |
     Component     |                             |
------------------+-----------------------------+-------------------------
   Frame Relay     | 3.5.3                       |			y
   Session         |                             |
   Parameters      |                             |
------------------+-----------------------------+-------------------------
     M values      |                             |			y
       0 No Merge  | 3.5.3                       |
       ------------+-----------------------------+-------------------------
       1 Merge     | 3.5.3                       |			y
   ----------------+-----------------------------+-------------------------
     D-bit         | 3.5.3                       |			y
   ----------------+-----------------------------+-------------------------
     Frame Relay   | 3.5.3                       |			y
     Label Range   |                             |
     Component     |                             |
   ----------------+-----------------------------+-------------------------
   Label Request   | 3.5.7                       |			t
   Message ID      |                             |
------------------+-----------------------------+-------------------------
   Vendor-Private  | 3.6.1.1                     |			y
------------------+-----------------------------+-------------------------
   Experimental    | 3.6.2                       |			y
==================+=============================+=========================
LDP Messages      | 3.5, throughout
------------------+-----------------------------+-------------------------
   Notification    | 3.5.1                       |			t
------------------+-----------------------------+-------------------------
   Hello           | 3.5.2                       |			t
------------------+-----------------------------+-------------------------
   Initialization  | 3.5.3                       |			t
------------------+-----------------------------+-------------------------
   KeepAlive       | 3.5.4                       |			t
------------------+-----------------------------+-------------------------
   Address         | 3.5.5                       |			t
------------------+-----------------------------+-------------------------
   Address Withdraw| 3.5.6                       |			t
------------------+-----------------------------+-------------------------
   Label Mapping   | 3.5.7                       |			t
   ----------------+-----------------------------+-------------------------
     Label Request | 3.5.7                       |			t
     Message ID TLV|                             |
   ----------------+-----------------------------+-------------------------
     Hop Count TLV | 3.5.7                       |			t
   ----------------+-----------------------------+-------------------------
     Path Vect TLV | 3.5.7                       |			t
------------------+-----------------------------+-------------------------
   Label Request   | 3.5.8                       |			t
   ----------------+-----------------------------+-------------------------
     Hop Count TLV | 3.5.8                       |			t
   ----------------+-----------------------------+-------------------------
     Path Vect TLV | 3.5.8                       |			t
------------------+-----------------------------+-------------------------
   Label Withdraw  | 3.5.10                      |			t
   ----------------+-----------------------------+-------------------------
     Label TLV     | 3.5.10                      |			t
------------------+-----------------------------+-------------------------
   Label Release   | 3.5.11                      |			t
   ----------------+-----------------------------+-------------------------
     Label TLV     | 3.5.11                      |			t
------------------+-----------------------------+-------------------------
   Label Abort Req | 3.5.9                       |			y
------------------+-----------------------------+-------------------------
   Vendor-Private  | 3.6.1.2                     |			y
------------------+-----------------------------+-------------------------
   Experimental    | 3.6.2                       |			y
==================+=============================+=========================
LDP Status Codes  | 3.4.6
------------------+-----------------------------+-------------------------
   Success         | 3.4.6, 3.9                  |			y
------------------+-----------------------------+-------------------------
   Bad LDP Id      | 3.5.1.2.1                   |			y
------------------+-----------------------------+-------------------------
   Bad Ptcl Version| 3.5.1.2.1                   |			y
------------------+-----------------------------+-------------------------
   Bad PDU Length  | 3.5.1.2.1                   |			y
------------------+-----------------------------+-------------------------
   Unknown Message | 3.5.1.2.1                   |			y
   Type            |                             |
------------------+-----------------------------+-------------------------
   Bad Message     | 3.5.1.2.1                   |			y
   Length          |                             |
------------------+-----------------------------+-------------------------
   Unknown TLV     | 3.5.1.2.2                   |			y
------------------+-----------------------------+-------------------------
   Bad TLV length  | 3.5.1.2.2                   |			y
------------------+-----------------------------+-------------------------
   Malformed TLV   | 3.5.1.2.2                   |			y
   Value           |                             |
------------------+-----------------------------+-------------------------
   Hold Timer      | 3.5.1.2.3                   |			t
   Expired         |                             |
------------------+-----------------------------+-------------------------
   Shutdown        | 3.5.1.2.4                   |			t
------------------+-----------------------------+-------------------------
   Loop Detected   | 3.4.5.1.2, 3.5.8.1          |			t
------------------+-----------------------------+-------------------------
   Unknown FEC     | 3.4.1.1                     |			y
------------------+-----------------------------+-------------------------
   No Route        | 3.5.8.1                     |			t
------------------+-----------------------------+-------------------------
   No Label        | 3.5.8.1                     |			y
   Resources       |                             |
------------------+-----------------------------+-------------------------
   Label Resources | 3.5.8.1                     |			y
   Available       |                             |
------------------+-----------------------------+-------------------------
   Session Rejected| 2.5.3, 3.5.3                |			y
   No Hello        |                             |
------------------+-----------------------------+-------------------------
   Session Rejected| 2.5.3, 3.5.3                |			y
   Parameters      |                             |
   Advert Mode     |                             |
------------------+-----------------------------+-------------------------
   Session Rejected| 2.5.3, 3.5.3                |			t
   Parameters      |                             |
   Max PDU Length  |                             |
------------------+-----------------------------+-------------------------
   Session Rejected| 2.5.3, 3.5.3                |			t
   Parameters      |                             |
   Label Range     |                             |
------------------+-----------------------------+-------------------------
   KeepAlive Timer | 2.5.6, 3.5.1.2.3            |			t
   Expired         |                             |
------------------+-----------------------------+-------------------------
   Label Request   | 3.5.9.1                     |			t
   Aborted         |                             |
------------------+-----------------------------+-------------------------
   Missing Message | 3.5.1.2.1                   |			y
   Parameters      |                             |
------------------+-----------------------------+-------------------------
   Unsupported     | 3.4.1.1, 3.5.5.1            |			y
   Address Family  |                             |
------------------+-----------------------------+-------------------------
   Session Rejected| 3.5.1.2.5, 3.5.3            |			y
   Bad KeepAlive   |                             |
   Time            |                             |
------------------+-----------------------------+-------------------------
   Internal Error  | 3.5.1.2.7                   |			y
==================+=============================+=========================


-- 
     Loa Andersson
     Chief Architect,
     Utfors Research, Architecture and Future Lab (URAX)
     Utfors AB
     R錽undav鋑en 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  Wed Sep 25 15:20:12 2002
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 ESMTP id PAA07308
	for <mpls-archive@lists.ietf.org>; Wed, 25 Sep 2002 15:20:11 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhwn25543
	for <mpls-archive@lists.ietf.org>; Wed, 25 Sep 2002 19:22:01 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnhwn24477;
	Wed, 25 Sep 2002 19:21:29 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnhwn03140
	for mpls-outgoing; Wed, 25 Sep 2002 19:21:02 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnhwn03132
	for <mpls@mail-control.ash.ops.us.uu.net>; Wed, 25 Sep 2002 19:20: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 QQnhwn18834
	for <mpls@UU.NET>; Wed, 25 Sep 2002 19:20:35 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhwn05064
	for <mpls@UU.NET>; Wed, 25 Sep 2002 19:20:35 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 QQnhwn05059
	for <mpls@UU.NET>; Wed, 25 Sep 2002 19:20:34 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 PAA17369
	for <mpls@UU.NET>; Wed, 25 Sep 2002 15:20:32 -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 PAA26667
	for <mpls@UU.NET>; Wed, 25 Sep 2002 15:20:28 -0400 (EDT)
Message-ID: <3D920C82.4040805@marconi.com>
Date: Wed, 25 Sep 2002 15:20:34 -0400
From: David Charlap <David.Charlap@marconi.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.2b) Gecko/20020920
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: IETF MPLS List <mpls@UU.NET>
Subject: RSVP Refresh Reduction question
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

The Refresh Reduction RFC (RFC 2961) says that the "refresh reduction 
enabled" bit must be set in the common header of all messages that an 
RR-enabled router sends.  Routers receiving RSVP messages check for the 
presence or absence of this bit to determine if the neighbor will 
understand Bundle, SRefresh and Ack messages.  All this is clear.

Obviously, all Bundle, SRefresh and Ack messages must have this bit set 
in their headers, since only an RR-enabled router could send such a message.

My question is what should a router do if it receives a Bundle, SRefresh 
or Ack message where the RR-enabled bit is not set in the common header.

One opinion I've heard is that the message should be silently dropped, 
since its header is non-compliant with the RFC.

I disagree, however.  I think that the message should be processed as if 
the bit was set.  The information conveyed by the RR-enabled bit (that 
the sender supports RR) is implicit in the fact that the message is a 
Bundle, SRefresh or Ack.  Leaving the RR-enabled bit out of the header 
doesn't remove any information from the message, so there is no reason 
why it should be dropped.

What do others here think?  Should routers accept or drop such messages?

-- David



From owner-mpls@UU.NET  Wed Sep 25 22:17:30 2002
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 ESMTP id WAA15781
	for <mpls-archive@lists.ietf.org>; Wed, 25 Sep 2002 22:17:29 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhxp13133
	for <mpls-archive@lists.ietf.org>; Thu, 26 Sep 2002 02:19:20 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnhxp12921;
	Thu, 26 Sep 2002 02:19:13 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnhxp27517
	for mpls-outgoing; Thu, 26 Sep 2002 02:18:46 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnhxp27510
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 26 Sep 2002 02:18:40 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 QQnhxp23922
	for <mpls@uu.net>; Thu, 26 Sep 2002 02:16:07 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhxp11012
	for <mpls@uu.net>; Thu, 26 Sep 2002 02:16:07 GMT
Received: from funnel.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnhxp10970
	for <mpls@uu.net>; Thu, 26 Sep 2002 02:16:06 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id WAA07717 for <mpls@uu.net>; Wed, 25 Sep 2002 22:16:05 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8Q2G5827362 for mpls@uu.net; Wed, 25 Sep 2002 22:16:05 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQnhxp27220
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 26 Sep 2002 02:15:07 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 QQnhxp27553
	for <mpls@UU.NET>; Thu, 26 Sep 2002 02:15:03 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhxp18813
	for <mpls@UU.NET>; Thu, 26 Sep 2002 02:15:03 GMT
Received: from workhorse.fictitious.org by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: workhorse.fictitious.org [209.150.1.230])
	id QQnhxp18805
	for <mpls@UU.NET>; Thu, 26 Sep 2002 02:15:02 GMT
Received: from workhorse.fictitious.org (localhost.fictitious.org [127.0.0.1])
	by workhorse.fictitious.org (8.9.3/8.9.3) with ESMTP id WAA88781;
	Wed, 25 Sep 2002 22:13:41 -0400 (EDT)
	(envelope-from curtis@workhorse.fictitious.org)
Message-Id: <200209260213.WAA88781@workhorse.fictitious.org>
To: David Charlap <David.Charlap@marconi.com>
cc: IETF MPLS List <mpls@UU.NET>
Reply-To: curtis@fictitious.org
Subject: Re: RSVP Refresh Reduction question 
In-reply-to: Your message of "Wed, 25 Sep 2002 15:20:34 EDT."
             <3D920C82.4040805@marconi.com> 
Date: Wed, 25 Sep 2002 22:13:40 -0400
From: Curtis Villamizar <curtis@workhorse.fictitious.org>
Sender: owner-mpls@UU.NET
Precedence: bulk


In message <3D920C82.4040805@marconi.com>, David Charlap writes:
> The Refresh Reduction RFC (RFC 2961) says that the "refresh reduction 
> enabled" bit must be set in the common header of all messages that an 
> RR-enabled router sends.  Routers receiving RSVP messages check for the 
> presence or absence of this bit to determine if the neighbor will 
> understand Bundle, SRefresh and Ack messages.  All this is clear.
> 
> Obviously, all Bundle, SRefresh and Ack messages must have this bit set 
> in their headers, since only an RR-enabled router could send such a message.
> 
> My question is what should a router do if it receives a Bundle, SRefresh 
> or Ack message where the RR-enabled bit is not set in the common header.
> 
> One opinion I've heard is that the message should be silently dropped, 
> since its header is non-compliant with the RFC.
> 
> I disagree, however.  I think that the message should be processed as if 
> the bit was set.  The information conveyed by the RR-enabled bit (that 
> the sender supports RR) is implicit in the fact that the message is a 
> Bundle, SRefresh or Ack.  Leaving the RR-enabled bit out of the header 
> doesn't remove any information from the message, so there is no reason 
> why it should be dropped.
> 
> What do others here think?  Should routers accept or drop such messages?
> 
> -- David


David,

I think that falls under "Be conservative in what you send and liberal
in what you accept".  It need not be in the spec, but if you recognize
what appears to be a minor coding error in another implementation, it
might be a logical choice to log the error and process the messages.
The counter argument is that if the implementation is that shakey
maybe you don't want to trust it and disabling a buggy Refresh
Reduction implementation would also be a logical choice since it is
just an optimization.

Again, this is not something that should be in the spec.  The sender
should get it right and it would be acceptable as far as the spec is
concerned to either reject it or log and accept and try to continue.

Curtis



From owner-mpls@UU.NET  Thu Sep 26 02:53:51 2002
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 ESMTP id CAA29173
	for <mpls-archive@lists.ietf.org>; Thu, 26 Sep 2002 02:53:51 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhyh27000
	for <mpls-archive@lists.ietf.org>; Thu, 26 Sep 2002 06:55:42 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnhyh26820;
	Thu, 26 Sep 2002 06:55:37 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnhyh22790
	for mpls-outgoing; Thu, 26 Sep 2002 06:55:22 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQnhyh22785
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 26 Sep 2002 06:55:17 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 QQnhyh15282
	for <mpls@UU.NET>; Thu, 26 Sep 2002 06:54:40 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhyh25643
	for <mpls@UU.NET>; Thu, 26 Sep 2002 06:54:40 GMT
Received: from xover.netplane.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: fwout.maker.com [12.27.183.253] (may be forged))
	id QQnhyh25638
	for <mpls@UU.NET>; Thu, 26 Sep 2002 06:54:39 GMT
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2653.19)
	id <S1D0BR1A>; Thu, 26 Sep 2002 02:54:39 -0400
Message-ID: <E7E13AAF2F3ED41197C100508BD6A328853DD5@india_exch.hyderabad.mindspeed.com>
From: "Reddy, Vikram" <vikramr@netplane.com>
To: "'David Charlap'" <David.Charlap@marconi.com>,
        IETF MPLS List
	 <mpls@UU.NET>
Subject: RE: RSVP Refresh Reduction question
Date: Thu, 26 Sep 2002 02:56: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

Hi David,

This is interesting. The following is my opinion.

If the recieving node had set the RR Capable bit in its last msg Common
Header,
it should accept a Bundle, SRefresh msg from its neighbor. If the receiver
node
had not set the bit it should not accept the message, irrespective of
whether
it has RR capability or not.

The sender should not need to set the bit. The sender could be RR enabled,
may send RR messages
to a willing neighbor, but must have the flexibility to not want to accept
RR messages from the 
neighbor. If it sets the RR capable bit, then it is advertising that it is 
open to recieve RR messages, else it is saying, "I will drop RR messages if
you send them to me".

The significane of the bit is whether a reciever is willing to receive RR
messages
or not. 


"Obviously, all Bundle, SRefresh and Ack messages must have this bit set 
in their headers, since only an RR-enabled router could send such a
message."

Also, I would like to differ from the statement you made above.Consider the
following,
1) The case where a node wishes to send RR capable messages but does not
want to receive them.
   (Although I can't think of why it wouldn't want to receive them).
2) A node has been recieving RR messages but wants to turn it off. But there
is a Bundle Message
   which has been waiting for some time (accumulation time). It has to send
the bundle 
   message but with the bit not set.


Thanks,
Vikram.




-----Original Message-----
From: David Charlap [mailto:David.Charlap@marconi.com]
Sent: Thursday, September 26, 2002 12:51 AM
To: IETF MPLS List
Subject: RSVP Refresh Reduction question


The Refresh Reduction RFC (RFC 2961) says that the "refresh reduction 
enabled" bit must be set in the common header of all messages that an 
RR-enabled router sends.  Routers receiving RSVP messages check for the 
presence or absence of this bit to determine if the neighbor will 
understand Bundle, SRefresh and Ack messages.  All this is clear.

Obviously, all Bundle, SRefresh and Ack messages must have this bit set 
in their headers, since only an RR-enabled router could send such a message.

My question is what should a router do if it receives a Bundle, SRefresh 
or Ack message where the RR-enabled bit is not set in the common header.

One opinion I've heard is that the message should be silently dropped, 
since its header is non-compliant with the RFC.

I disagree, however.  I think that the message should be processed as if 
the bit was set.  The information conveyed by the RR-enabled bit (that 
the sender supports RR) is implicit in the fact that the message is a 
Bundle, SRefresh or Ack.  Leaving the RR-enabled bit out of the header 
doesn't remove any information from the message, so there is no reason 
why it should be dropped.

What do others here think?  Should routers accept or drop such messages?

-- David


From owner-mpls@UU.NET  Thu Sep 26 03:07:07 2002
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 ESMTP id DAA29334
	for <mpls-archive@lists.ietf.org>; Thu, 26 Sep 2002 03:07:07 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhyi12131
	for <mpls-archive@lists.ietf.org>; Thu, 26 Sep 2002 07:08:57 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnhyi11877;
	Thu, 26 Sep 2002 07:08:49 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnhyi09732
	for mpls-outgoing; Thu, 26 Sep 2002 07:08:22 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQnhyi09712
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 26 Sep 2002 07:08: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 QQnhyi17984
	for <mpls@uu.net>; Thu, 26 Sep 2002 07:08:03 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhyi06287
	for <mpls@uu.net>; Thu, 26 Sep 2002 07:08:03 GMT
Received: from funnel.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnhyi06272
	for <mpls@uu.net>; Thu, 26 Sep 2002 07:08:02 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id DAA05713 for <mpls@uu.net>; Thu, 26 Sep 2002 03:08:02 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8Q782m11458 for mpls@uu.net; Thu, 26 Sep 2002 03:08:02 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQnhyi09475
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 26 Sep 2002 07:07: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 QQnhyi29813
	for <mpls@uu.net>; Thu, 26 Sep 2002 07:05:21 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhyi04481
	for <mpls@uu.net>; Thu, 26 Sep 2002 07:05:21 GMT
Received: from ganesh.ctd.hctech.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [202.54.64.2])
	id QQnhyi04456
	for <mpls@uu.net>; Thu, 26 Sep 2002 07:05:20 GMT
Received: by GANESH with Internet Mail Service (5.5.2653.19)
	id <TA10H85P>; Thu, 26 Sep 2002 12:40:24 +0530
Message-ID: <55E277B99171E041ABF5F4B1C6DDCA0691BC7A@haritha.hclt.com>
From: "Vijayanand C - CTD, Chennai." <vijayc@ctd.hcltech.com>
To: David Charlap <David.Charlap@marconi.com>
Cc: mpls@UU.NET
Subject: RE: RSVP Refresh Reduction question
Date: Thu, 26 Sep 2002 12:37:29 +0530
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

One would expect the behaviour to be implementation dependent. While it
would be perfectly legitimate for the reciver to drop these messages, it may
be robust/liberal enought to accept them. But, I think it would not be right
to expect all implementations to accept such messages.

Vijay

-----Original Message-----
From: David Charlap [mailto:David.Charlap@marconi.com]
Sent: Thursday, September 26, 2002 12:51 AM
To: IETF MPLS List
Subject: RSVP Refresh Reduction question


The Refresh Reduction RFC (RFC 2961) says that the "refresh reduction 
enabled" bit must be set in the common header of all messages that an 
RR-enabled router sends.  Routers receiving RSVP messages check for the 
presence or absence of this bit to determine if the neighbor will 
understand Bundle, SRefresh and Ack messages.  All this is clear.

Obviously, all Bundle, SRefresh and Ack messages must have this bit set 
in their headers, since only an RR-enabled router could send such a message.

My question is what should a router do if it receives a Bundle, SRefresh 
or Ack message where the RR-enabled bit is not set in the common header.

One opinion I've heard is that the message should be silently dropped, 
since its header is non-compliant with the RFC.

I disagree, however.  I think that the message should be processed as if 
the bit was set.  The information conveyed by the RR-enabled bit (that 
the sender supports RR) is implicit in the fact that the message is a 
Bundle, SRefresh or Ack.  Leaving the RR-enabled bit out of the header 
doesn't remove any information from the message, so there is no reason 
why it should be dropped.

What do others here think?  Should routers accept or drop such messages?

-- David



From owner-mpls@UU.NET  Thu Sep 26 08:18:28 2002
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 ESMTP id IAA03865
	for <mpls-archive@lists.ietf.org>; Thu, 26 Sep 2002 08:18:27 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhzd08092
	for <mpls-archive@lists.ietf.org>; Thu, 26 Sep 2002 12:20:15 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnhzd07698;
	Thu, 26 Sep 2002 12:20:02 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnhzd24072
	for mpls-outgoing; Thu, 26 Sep 2002 12:19:33 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnhzd24067
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 26 Sep 2002 12:19: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 QQnhzc09597
	for <mpls@uu.net>; Thu, 26 Sep 2002 12:07:03 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhzc14875
	for <mpls@uu.net>; Thu, 26 Sep 2002 12:07:02 GMT
Received: from funnel.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnhzc14870
	for <mpls@uu.net>; Thu, 26 Sep 2002 12:07:02 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id IAA00606 for <mpls@uu.net>; Thu, 26 Sep 2002 08:07:02 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8QC71H24907 for mpls@uu.net; Thu, 26 Sep 2002 08:07:01 -0400 (EDT)
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQnhzc22160
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 26 Sep 2002 12:05: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 QQnhzc23006
	for <mpls@UU.NET>; Thu, 26 Sep 2002 12:04:56 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhzc13497
	for <mpls@UU.NET>; Thu, 26 Sep 2002 12:04:55 GMT
Received: from funnel.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnhzc13487
	for <mpls@UU.NET>; Thu, 26 Sep 2002 12:04:55 GMT
Received: from bifocal.cisco.com (bifocal.cisco.com [161.44.172.150]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id IAA00412; Thu, 26 Sep 2002 08:04:54 -0400 (EDT)
Received: from localhost (swallow@localhost) by bifocal.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) with ESMTP id IAA18476; Thu, 26 Sep 2002 08:04:54 -0400 (EDT)
Message-Id: <200209261204.IAA18476@bifocal.cisco.com>
X-Authentication-Warning: bifocal.cisco.com: swallow owned process doing -bs
To: "Reddy, Vikram" <vikramr@netplane.com>
cc: "'David Charlap'" <David.Charlap@marconi.com>,
        IETF MPLS List <mpls@UU.NET>, swallow@cisco.com
Subject: Re: RSVP Refresh Reduction question 
In-reply-to: Your message of "Thu, 26 Sep 2002 02:56:59 EDT."
             <E7E13AAF2F3ED41197C100508BD6A328853DD5@india_exch.hyderabad.mindspeed.com> 
Date: Thu, 26 Sep 2002 08:04:54 -0400
From: George Swallow <swallow@cisco.com>
Sender: owner-mpls@UU.NET
Precedence: bulk

Reddy -

I don't like the idea of using the bit to mean "willing to receive".
For a properly compliant implementation, if you want to send then you
MUST set the bit and MUST be willing to receive.  If (for reasons that
I haven't imagined yet) you want to just receive, then just set the
bit and don't send.

As far as dealing with a *non-compliant* implementation, I completely
agree with Curtis.

...George

==================================================================
George Swallow       Cisco Systems                  (978) 497-8143
                     250 Apollo Drive
                     Chelmsford, Ma 01824



From owner-mpls@UU.NET  Thu Sep 26 09:41:03 2002
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 ESMTP id JAA07345
	for <mpls-archive@lists.ietf.org>; Thu, 26 Sep 2002 09:41:03 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhzi25964
	for <mpls-archive@lists.ietf.org>; Thu, 26 Sep 2002 13:42:51 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnhzi25728;
	Thu, 26 Sep 2002 13:42:44 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnhzi15492
	for mpls-outgoing; Thu, 26 Sep 2002 13:42:30 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnhzi15483
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 26 Sep 2002 13:42:19 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 QQnhzf18630
	for <mpls@UU.NET>; Thu, 26 Sep 2002 12:49:19 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhzf17703
	for <mpls@UU.NET>; Thu, 26 Sep 2002 12:49:19 GMT
Received: from xover.netplane.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: fwout.maker.com [12.27.183.253] (may be forged))
	id QQnhzf17679
	for <mpls@UU.NET>; Thu, 26 Sep 2002 12:49:18 GMT
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2653.19)
	id <S1D0BRPG>; Thu, 26 Sep 2002 08:49:17 -0400
Message-ID: <E7E13AAF2F3ED41197C100508BD6A328853DD8@india_exch.hyderabad.mindspeed.com>
From: "Reddy, Vikram" <vikramr@netplane.com>
To: "'George Swallow'" <swallow@cisco.com>,
        "Reddy, Vikram"
	 <vikramr@netplane.com>
Cc: "'David Charlap'" <David.Charlap@marconi.com>,
        IETF MPLS List
	 <mpls@UU.NET>
Subject: RE: RSVP Refresh Reduction question 
Date: Thu, 26 Sep 2002 08:51:33 -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 George,

Then, maybe the wording in the RFC should specify this. According to the
current wording, this is not explicitly mentioned. Also, the interpretation
of
"willing to receive" is from the RFC.

From Section 2
         0x01: Refresh (overhead) reduction capable

           When set, indicates that this node is willing and capable of
           receiving all the messages and objects described in this
           document.  This includes the Bundle message described in
           Section 3, the MESSAGE_ID objects and Ack messages described
           in Section 4, and the MESSAGE_ID LIST objects and Srefresh
           message described in Section 5.  This bit is meaningful only
           between RSVP neighbors.

Thanks,
Vikram.

-----Original Message-----
From: George Swallow [mailto:swallow@cisco.com]
Sent: Thursday, September 26, 2002 5:35 PM
To: Reddy, Vikram
Cc: 'David Charlap'; IETF MPLS List; swallow@cisco.com
Subject: Re: RSVP Refresh Reduction question 


Reddy -

I don't like the idea of using the bit to mean "willing to receive".
For a properly compliant implementation, if you want to send then you
MUST set the bit and MUST be willing to receive.  If (for reasons that
I haven't imagined yet) you want to just receive, then just set the
bit and don't send.

As far as dealing with a *non-compliant* implementation, I completely
agree with Curtis.

...George

==================================================================
George Swallow       Cisco Systems                  (978) 497-8143
                     250 Apollo Drive
                     Chelmsford, Ma 01824


From owner-mpls@UU.NET  Thu Sep 26 10:55:30 2002
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 ESMTP id KAA10385
	for <mpls-archive@lists.ietf.org>; Thu, 26 Sep 2002 10:55:29 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhzn23432
	for <mpls-archive@lists.ietf.org>; Thu, 26 Sep 2002 14:57:18 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnhzn22177;
	Thu, 26 Sep 2002 14:56:37 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnhzn07389
	for mpls-outgoing; Thu, 26 Sep 2002 14:56:23 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQnhzn07369
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 26 Sep 2002 14:56:10 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 QQnhzn14862
	for <mpls@uu.net>; Thu, 26 Sep 2002 14:54:08 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhzn17127
	for <mpls@uu.net>; Thu, 26 Sep 2002 14:54:07 GMT
Received: from funnel.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnhzn17117
	for <mpls@uu.net>; Thu, 26 Sep 2002 14:54:07 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id KAA20680 for <mpls@uu.net>; Thu, 26 Sep 2002 10:54:06 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8QEs6l04419 for mpls@uu.net; Thu, 26 Sep 2002 10:54:06 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQnhzn06948
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 26 Sep 2002 14:51: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 QQnhzn09041
	for <mpls@UU.NET>; Thu, 26 Sep 2002 14:50:35 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhzn08762
	for <mpls@UU.NET>; Thu, 26 Sep 2002 14:50:34 GMT
Received: from pimout4-ext.prodigy.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: pimout4-ext.prodigy.net [207.115.63.103])
	id QQnhzn08754
	for <mpls@UU.NET>; Thu, 26 Sep 2002 14:50:34 GMT
Received: from ciena.com (adsl-66-127-240-156.dsl.sntc01.pacbell.net [66.127.240.156])
	by pimout4-ext.prodigy.net (8.12.3 da nor stuldap/8.12.3) with ESMTP id g8QEoW0N457598;
	Thu, 26 Sep 2002 10:50:32 -0400
Message-ID: <3D931EC2.1020002@ciena.com>
Date: Thu, 26 Sep 2002 07:50:42 -0700
From: Ping Pan <ppan@ciena.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: David Charlap <David.Charlap@marconi.com>
CC: IETF MPLS List <mpls@UU.NET>
Subject: Re: RSVP Refresh Reduction question
References: <3D920C82.4040805@marconi.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

David,

First of all, this is an implementation issue.

The real issue here is not at the receiving nodes, rather it is at the 
sending nodes. When refresh reduction is set on an outgoing interface, 
how do you know that the messages can be processed by the receiving nodes?

Worse, if a receiving node has implemented only one of the 4 features in 
refresh reduction, it may send messages with RR-enabled bit on, now what 
  do you do? For example, in my past life, I need to deal the following: 
per OIF standard, a receiving node needs only support msg-ack, but will 
turn on the RR-enable bit anyway. Great! When a sending node starts to 
send out summary refreshes, the receiving node will drop the refreshes 
and time-out all sessions.

Thus, the focus is to make the sending nodes knowing the status of the 
receiving nodes. One solution is the following: once a RR-enable bit is 
detected from a RSVP neighbor, the sending node starts to probe the 
neighbor by sending two identical refresh messages periodically: one 
with RR-enabled bit, and msg-ack; the other without. If an ack is 
received from the receiving node, the life is good... (there ,ay be some 
other twisted corner cases). If there is no ack, only send the plain 
refreshes to the receiving nodes, and log the error.

I agree with Curtis, don't anything with the spec, and beat up the code 
again and again.

Regards,

- Ping



David Charlap wrote:
> The Refresh Reduction RFC (RFC 2961) says that the "refresh reduction 
> enabled" bit must be set in the common header of all messages that an 
> RR-enabled router sends.  Routers receiving RSVP messages check for the 
> presence or absence of this bit to determine if the neighbor will 
> understand Bundle, SRefresh and Ack messages.  All this is clear.
> 
> Obviously, all Bundle, SRefresh and Ack messages must have this bit set 
> in their headers, since only an RR-enabled router could send such a 
> message.
> 
> My question is what should a router do if it receives a Bundle, SRefresh 
> or Ack message where the RR-enabled bit is not set in the common header.
> 
> One opinion I've heard is that the message should be silently dropped, 
> since its header is non-compliant with the RFC.
> 
> I disagree, however.  I think that the message should be processed as if 
> the bit was set.  The information conveyed by the RR-enabled bit (that 
> the sender supports RR) is implicit in the fact that the message is a 
> Bundle, SRefresh or Ack.  Leaving the RR-enabled bit out of the header 
> doesn't remove any information from the message, so there is no reason 
> why it should be dropped.
> 
> What do others here think?  Should routers accept or drop such messages?
> 
> -- David




From owner-mpls@UU.NET  Thu Sep 26 11:22:07 2002
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 ESMTP id LAA11424
	for <mpls-archive@lists.ietf.org>; Thu, 26 Sep 2002 11:22:06 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhzp09536
	for <mpls-archive@lists.ietf.org>; Thu, 26 Sep 2002 15:23:55 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnhzp08676;
	Thu, 26 Sep 2002 15:23:31 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnhzp26080
	for mpls-outgoing; Thu, 26 Sep 2002 15:23:16 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQnhzp26075
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 26 Sep 2002 15:23: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 QQnhzp29289
	for <mpls@UU.NET>; Thu, 26 Sep 2002 15:21:53 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnhzp07484
	for <mpls@UU.NET>; Thu, 26 Sep 2002 15:21:53 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 QQnhzp07473
	for <mpls@UU.NET>; Thu, 26 Sep 2002 15:21: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 LAA28772
	for <mpls@UU.NET>; Thu, 26 Sep 2002 11:21: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 LAA26697
	for <mpls@UU.NET>; Thu, 26 Sep 2002 11:21:49 -0400 (EDT)
Message-ID: <3D932617.1030400@marconi.com>
Date: Thu, 26 Sep 2002 11:21:59 -0400
From: David Charlap <David.Charlap@marconi.com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.2b) Gecko/20020920
X-Accept-Language: en-US,en-GB,en
MIME-Version: 1.0
To: IETF MPLS List <mpls@UU.NET>
Subject: Re: RSVP Refresh Reduction question
References: <3D920C82.4040805@marconi.com> <3D931EC2.1020002@ciena.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7bit

Ping Pan wrote:
> 
> The real issue here is not at the receiving nodes, rather it is at the 
> sending nodes. When refresh reduction is set on an outgoing interface, 
> how do you know that the messages can be processed by the receiving nodes?

That's another important issue, but not the one I was asking about.  We 
have a piece of conformance-test software which thinks switches must 
drop Bundle messages that don't have the RR bit.  My posting here was 
mostly to determine if they are correct in making that a requirement or 
not - and the consensus here is that they are not correct.

> Worse, if a receiving node has implemented only one of the 4 features in 
> refresh reduction, it may send messages with RR-enabled bit on, now what 
>  do you do? For example, in my past life, I need to deal the following: 
> per OIF standard, a receiving node needs only support msg-ack, but will 
> turn on the RR-enable bit anyway. Great! When a sending node starts to 
> send out summary refreshes, the receiving node will drop the refreshes 
> and time-out all sessions.

Sounds like a broken node.  The RFC clearly states that a node setting 
the bit is telling neighbors that he can receive SRefresh, Bundle and 
Ack messages.

Note also that support for MESSAGE_ID objects is separate from these. 
Support for them is indicated by returning an ACK object upon receipt of 
a MESSAGE_ID, or by returning an "invalid object class" error if it 
isn't supported.

A node should not generate an SRefresh message until it knows that the 
neighbor both supports the RR messages (from the header bit) and that it 
supports MESSAGE_ID (by acknowledging an incoming message ID).

> Thus, the focus is to make the sending nodes knowing the status of the 
> receiving nodes. One solution is the following: once a RR-enable bit is 
> detected from a RSVP neighbor, the sending node starts to probe the 
> neighbor by sending two identical refresh messages periodically: one 
> with RR-enabled bit, and msg-ack; the other without. If an ack is 
> received from the receiving node, the life is good... (there ,ay be some 
> other twisted corner cases). If there is no ack, only send the plain 
> refreshes to the receiving nodes, and log the error.

Yes.  But your solution here doesn't solve your problem.  Your test will 
prove that the other end knows about MESSAGE_ID, not that it can support 
an SRefresh or Bundle message.

Personally, I don't think supporting them is that difficult.  If you 
support MESSAGE_ID, then you already have all the infrastructure in 
place ncessary to support an incoming SRefresh, even if you don't have 
the infrastructure needed to generate one.  Ditto for Ack messages - if 
you can proces the ACK object in other messages, then you can process it 
in an Ack message.  Bundle messages can be processed with virtually no 
changes to any code-bsae, even if generating them may be difficult.

I would seriously question the viability of any implementation that sets 
the RR bit and doesn't handle all three of these messages.

> I agree with Curtis, don't anything with the spec, and beat up the code 
> again and again.

I'm not sure what you're recommending here.  If you're saying that lots 
of interop testing is required, I agree completely.  But that doesn't 
mean the spec isn't ambiguous here.

Personally, I don't like the fact that several parts of RSVP-TE post 
requirements regarding how a message must be formatted, but fail to 
specify how to handle a non-compliant message.

-- David



From owner-mpls@UU.NET  Thu Sep 26 17:20:41 2002
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 ESMTP id RAA22592
	for <mpls-archive@lists.ietf.org>; Thu, 26 Sep 2002 17:20:40 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnian05001
	for <mpls-archive@lists.ietf.org>; Thu, 26 Sep 2002 21:22:30 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnian03949;
	Thu, 26 Sep 2002 21:22:02 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnian00412
	for mpls-outgoing; Thu, 26 Sep 2002 21:21:36 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnian00405
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 26 Sep 2002 21:21:30 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 QQnian29998
	for <mpls@uu.net>; Thu, 26 Sep 2002 21:16:03 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnian09721
	for <mpls@uu.net>; Thu, 26 Sep 2002 21:16:03 GMT
Received: from funnel.cisco.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnian09712
	for <mpls@uu.net>; Thu, 26 Sep 2002 21:16:02 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id RAA12640 for <mpls@uu.net>; Thu, 26 Sep 2002 17:16:02 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8QLG2p23776 for mpls@uu.net; Thu, 26 Sep 2002 17:16:02 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQniam29808
	for <mpls@mail-control.ash.ops.us.uu.net>; Thu, 26 Sep 2002 21:14: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 QQniam11215
	for <mpls@UU.NET>; Thu, 26 Sep 2002 21:13:21 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQniam20369
	for <mpls@UU.NET>; Thu, 26 Sep 2002 21:13:20 GMT
Received: from c2.ciena.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [63.118.32.25])
	id QQniam20338
	for <mpls@UU.NET>; Thu, 26 Sep 2002 21:13:20 GMT
Received: by c2.ciena.com (8.8.8+Sun/SMI-SVR4-8.0)
	id RAA17203; Thu, 26 Sep 2002 17:13:19 -0400 (EDT)
Received: from wntcsdexg01.csd.ciena.com(10.128.2.158) by c2.ciena.com via smap (V2.0)
	id xma016650; Thu, 26 Sep 02 17:11:34 -0400
Received: by wntcsdexg01.csd.ciena.com with Internet Mail Service (5.5.2653.19)
	id <PQWWXTTA>; Thu, 26 Sep 2002 14:11:32 -0700
Received: from ciena.com (ppan [10.128.20.74]) by wntcsdexg02.csd.ciena.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id PF7Z5DHW; Thu, 26 Sep 2002 14:11:24 -0700
From: "Pan, Ping" <ppan@ciena.com>
To: "Reddy, Vikram" <vikramr@netplane.com>
Cc: "'George Swallow'" <swallow@cisco.com>,
        "'David Charlap'"
	 <David.Charlap@marconi.com>,
        IETF MPLS List <mpls@UU.NET>
Message-ID: <3D937841.1040007@ciena.com>
Date: Thu, 26 Sep 2002 14:12:33 -0700
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
Subject: Re: RSVP Refresh Reduction question
References: <E7E13AAF2F3ED41197C100508BD6A328853DD8@india_exch.hyderabad.mindspeed.com>
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,

Actually, having this bit in RSVP message head is a questionable design 
in the first place.

During the design of graceful restart, we invented this capability 
object that is used in RSVP Hello's. One day, Jonathan Lang in a private 
email told me that we should have put all refresh reduction features in 
this capability object. At the time, I was just hoping he won't make me 
to put them in LMP. ;-) But come to think of it, we should have 
advertised the feature capability information via Hello. After all, this 
is only useful among RSVP neighbors.

But, having said that, it's all too late to change. The code has been 
deployed; the feature has been used. Developers can figure out the 
operation details eventually. IMHO, IETF drafts and RFC's are meant to 
describe what's on the wire. Running code is all that matters. Let's 
move on.

Regards,

- Ping

Reddy, Vikram wrote:
> Hi George,
> 
> Then, maybe the wording in the RFC should specify this. According to the
> current wording, this is not explicitly mentioned. Also, the interpretation
> of
> "willing to receive" is from the RFC.
> 
>>From Section 2
>          0x01: Refresh (overhead) reduction capable
> 
>            When set, indicates that this node is willing and capable of
>            receiving all the messages and objects described in this
>            document.  This includes the Bundle message described in
>            Section 3, the MESSAGE_ID objects and Ack messages described
>            in Section 4, and the MESSAGE_ID LIST objects and Srefresh
>            message described in Section 5.  This bit is meaningful only
>            between RSVP neighbors.
> 
> Thanks,
> Vikram.
> 
> -----Original Message-----
> From: George Swallow [mailto:swallow@cisco.com]
> Sent: Thursday, September 26, 2002 5:35 PM
> To: Reddy, Vikram
> Cc: 'David Charlap'; IETF MPLS List; swallow@cisco.com
> Subject: Re: RSVP Refresh Reduction question 
> 
> 
> Reddy -
> 
> I don't like the idea of using the bit to mean "willing to receive".
> For a properly compliant implementation, if you want to send then you
> MUST set the bit and MUST be willing to receive.  If (for reasons that
> I haven't imagined yet) you want to just receive, then just set the
> bit and don't send.
> 
> As far as dealing with a *non-compliant* implementation, I completely
> agree with Curtis.
> 
> ...George
> 
> ==================================================================
> George Swallow       Cisco Systems                  (978) 497-8143
>                      250 Apollo Drive
>                      Chelmsford, Ma 01824



From owner-mpls@UU.NET  Fri Sep 27 03:13:50 2002
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 ESMTP id DAA13134
	for <mpls-archive@lists.ietf.org>; Fri, 27 Sep 2002 03:13:49 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnicb26442
	for <mpls-archive@lists.ietf.org>; Fri, 27 Sep 2002 07:15:41 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnicb25899;
	Fri, 27 Sep 2002 07:15:26 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnica26582
	for mpls-outgoing; Fri, 27 Sep 2002 07:14:59 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQnica26577
	for <mpls@mail-control.ash.ops.us.uu.net>; Fri, 27 Sep 2002 07:14: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 QQnica19102
	for <mpls@UU.NET>; Fri, 27 Sep 2002 07:14:40 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnica16315
	for <mpls@UU.NET>; Fri, 27 Sep 2002 07:14:40 GMT
Received: from xover.netplane.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: fwout.maker.com [12.27.183.253] (may be forged))
	id QQnica16304
	for <mpls@UU.NET>; Fri, 27 Sep 2002 07:14:39 GMT
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2653.19)
	id <S1D0BTC5>; Fri, 27 Sep 2002 03:14:38 -0400
Message-ID: <E7E13AAF2F3ED41197C100508BD6A328853DDB@india_exch.hyderabad.mindspeed.com>
From: "Reddy, Vikram" <vikramr@netplane.com>
To: ccamp@ops.ietf.org, IETF MPLS List <mpls@UU.NET>
Subject: Question on Control Channel -Data Channel association
Date: Fri, 27 Sep 2002 03:16:58 -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 all,

I have a question on the association of Control Channel and Data 
Channel. I would appreciate if somebody could answer it

In the following figure (A*,B*) are for Control Channel Interface 
addresses and  (X*,Y*) are for Data Channel Interface Addresses.  
Dotted lines (....) for control channel, Dashed line (----) for 
data channel.

	      A1 .................................B1
  Node 1      X1 ---------------------------------Y1     Node 2
                  A2 .................................B2

In the above configuration can we have Node1 use A1-B1 for sending 
control messages for X1-Y1 but expect to receive control messages
for X1-Y1 on A2-B2. 
Similarly can we have Node2 use B2-A2 for sending 
control messages for X1-Y1 but expect to receive control messages
for X1-Y1 on B2-A2. 

Is this prohibited and if it is, which document specifies it?


Thanks,
Vikram.




From owner-mpls@UU.NET  Fri Sep 27 06:39:04 2002
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 ESMTP id GAA16051
	for <mpls-archive@lists.ietf.org>; Fri, 27 Sep 2002 06:39:04 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnico29694
	for <mpls-archive@lists.ietf.org>; Fri, 27 Sep 2002 10:40:56 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnico29312;
	Fri, 27 Sep 2002 10:40:47 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnico29823
	for mpls-outgoing; Fri, 27 Sep 2002 10:40:20 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQnico29818
	for <mpls@mail-control.ash.ops.us.uu.net>; Fri, 27 Sep 2002 10: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 QQnico02088
	for <mpls@uu.net>; Fri, 27 Sep 2002 10:40:03 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnico12452
	for <mpls@uu.net>; Fri, 27 Sep 2002 10:40:03 GMT
Received: from funnel.cisco.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnico12404
	for <mpls@uu.net>; Fri, 27 Sep 2002 10:40:02 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id GAA24552 for <mpls@uu.net>; Fri, 27 Sep 2002 06:40:02 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8RAe1I01518 for mpls@uu.net; Fri, 27 Sep 2002 06:40:01 -0400 (EDT)
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnico29795
	for <mpls@mail-control.ash.ops.us.uu.net>; Fri, 27 Sep 2002 10:39:01 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 QQnico06178
	for <mpls@uu.net>; Fri, 27 Sep 2002 10:38:52 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnico24285
	for <mpls@uu.net>; Fri, 27 Sep 2002 10:38:52 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 QQnico24279
	for <mpls@uu.net>; Fri, 27 Sep 2002 10:38:52 GMT
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15980;
	Fri, 27 Sep 2002 06:36:58 -0400 (EDT)
Message-Id: <200209271036.GAA15980@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-bgp-mpls-restart-01.txt
Date: Fri, 27 Sep 2002 06:36:58 -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		: Graceful Restart Mechanism for BGP with MPLS
	Author(s)	: Y. Rekhter, R. Aggarwal
	Filename	: draft-ietf-mpls-bgp-mpls-restart-01.txt
	Pages		: 10
	Date		: 2002-9-26
	
A mechanism for BGP that would help minimize the negative effects on
routing caused by BGP restart is described in 'Graceful Restart
Mechanism for BGP' (see [1]). This document extends this mechanism to
also minimize the negative effects on MPLS forwarding caused by the
Label Switching Router's (LSR's) control plane restart, and
specifically by the restart of its BGP component when BGP is used to
carry MPLS labels and the LSR is capable of preserving the MPLS
forwarding state across the restart.
The mechanism described in this document is agnostic with respect to
the types of the addresses carried in the BGP Network Layer
Reachability Information (NLRI) field. As such it works in
conjunction with any of the address famililies that could be carried
in BGP (e.g., IPv4, IPv6, etc...)
The mechanism described in this document is applicable to all LSRs,
both those with the ability to preserve their forwarding state during
BGP restart and those without (although the latter need to implement
only a subset of the mechanism described in this document).
Supporting (a subset of) the mechanism described here by the LSRs
that can not preserve their MPLS forwarding state across the restart
would not reduce the negative impact on MPLS traffic caused by their
control plane restart, but it would minimize the impact if their
neighbor(s) are capable of preserving the forwarding state across the
restart of their control plane and implement the mechanism described
here.
The mechanism makes minimalistic assumptions on what has to be
preserved across restart - the mechanism assumes that only the actual
MPLS forwarding state has to be preserved; the mechanism does not
require any of the BGP-related state to be preserved across the
restart.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-bgp-mpls-restart-01.txt".

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mpls-bgp-mpls-restart-01.txt

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

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

--OtherAccess--

--NextPart--




From owner-mpls@UU.NET  Fri Sep 27 10:03:27 2002
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 ESMTP id KAA21033
	for <mpls-archive@lists.ietf.org>; Fri, 27 Sep 2002 10:03:27 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnidc07476
	for <mpls-archive@lists.ietf.org>; Fri, 27 Sep 2002 14:05:17 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnidc07052;
	Fri, 27 Sep 2002 14:05:02 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnidc18861
	for mpls-outgoing; Fri, 27 Sep 2002 14:04:41 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQnidc18839
	for <mpls@mail-control.ash.ops.us.uu.net>; Fri, 27 Sep 2002 14:04: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 QQnidc07534
	for <mpls@uu.net>; Fri, 27 Sep 2002 14:03:02 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnidc27207
	for <mpls@uu.net>; Fri, 27 Sep 2002 14:03:02 GMT
Received: from funnel.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnidc27139
	for <mpls@uu.net>; Fri, 27 Sep 2002 14:02:57 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id KAA13289 for <mpls@uu.net>; Fri, 27 Sep 2002 10:02:56 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8RE2uH11346 for mpls@uu.net; Fri, 27 Sep 2002 10:02:56 -0400 (EDT)
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQnicd29473
	for <mpls@mail-control.ash.ops.us.uu.net>; Fri, 27 Sep 2002 07:58:54 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 QQnicd15843
	for <mpls@UU.NET>; Fri, 27 Sep 2002 07:58:45 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnicd18637
	for <mpls@UU.NET>; Fri, 27 Sep 2002 07:58:45 GMT
Received: from lit.a-star.edu.sg by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: rodin.krdl.org.sg [192.122.139.27])
	id QQnicd18625
	for <mpls@UU.NET>; Fri, 27 Sep 2002 07:58:43 GMT
Received: from mailhost1 (localhost [127.0.0.1])
	by lit.a-star.edu.sg (8.11.1/8.11.1) with ESMTP id g8R7uOv17000
	for <mpls@UU.NET>; Fri, 27 Sep 2002 15:56:24 +0800 (SGT)
X-Authentication-Warning: rodin.lit.org.sg: iscan owned process doing -bs
Received: from flamingo (FLAMINGO.lit.org.sg [192.168.133.218])
 by mailhost.lit.org.sg
 (iPlanet Messaging Server 5.2 HotFix 0.5 (built Jun  7 2002))
 with SMTP id <0H3300D2R7JL20@mailhost.lit.org.sg> for mpls@UU.NET; Fri,
 27 Sep 2002 15:59:58 +0800 (SGT)
Date: Fri, 27 Sep 2002 16:05:28 +0800
From: Liu Qiang <qliu@lit.a-star.edu.sg>
Subject: RE: Question on Control Channel -Data Channel association
In-reply-to: 
 <E7E13AAF2F3ED41197C100508BD6A328853DDB@india_exch.hyderabad.mindspeed.com>
To: "Reddy, Vikram" <vikramr@netplane.com>, ccamp@ops.ietf.org,
        IETF MPLS List <mpls@UU.NET>
Message-id: <NGBBJAJGOLOECPJHDOEBGECDCBAA.qliu@lit.a-star.edu.sg>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 7BIT

Hi,

  Your question is some interesting. As I know the control channel is a pair
bi-directional reachable interface. That means messages can flow in the
"path"  A1->B1 and B1->A1. So does the "path" A2->B2 and B2->A2.
  The common idea is take one channel as active one, and another one as
backup, certainly you can set both of them as active and each of them serve
for a certain group of TE link.
  Here, you have two seperate "udi-direction" control channels, are they
physical  "uni" or just logical "uni-directional"?
  So far, I don't think any document prohibites or specifies it.

regards,

Liu Qiang

-----Original Message-----
From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org]On Behalf Of
Reddy, Vikram
Sent: 2002?9?27? 15:17
To: ccamp@ops.ietf.org; IETF MPLS List
Subject: Question on Control Channel -Data Channel association


Hi all,

I have a question on the association of Control Channel and Data
Channel. I would appreciate if somebody could answer it

In the following figure (A*,B*) are for Control Channel Interface
addresses and  (X*,Y*) are for Data Channel Interface Addresses.
Dotted lines (....) for control channel, Dashed line (----) for
data channel.

	      A1 .................................B1
  Node 1      X1 ---------------------------------Y1     Node 2
                  A2 .................................B2

In the above configuration can we have Node1 use A1-B1 for sending
control messages for X1-Y1 but expect to receive control messages
for X1-Y1 on A2-B2.
Similarly can we have Node2 use B2-A2 for sending
control messages for X1-Y1 but expect to receive control messages
for X1-Y1 on B2-A2.

Is this prohibited and if it is, which document specifies it?


Thanks,
Vikram.





From owner-mpls@UU.NET  Fri Sep 27 10:39:36 2002
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 ESMTP id KAA22060
	for <mpls-archive@lists.ietf.org>; Fri, 27 Sep 2002 10:39:36 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnide24819
	for <mpls-archive@lists.ietf.org>; Fri, 27 Sep 2002 14:41:27 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnide24147;
	Fri, 27 Sep 2002 14:41:05 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnide22860
	for mpls-outgoing; Fri, 27 Sep 2002 14:40:38 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnide22853
	for <mpls@mail-control.ash.ops.us.uu.net>; Fri, 27 Sep 2002 14:40:27 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 QQnide05237
	for <mpls@uu.net>; Fri, 27 Sep 2002 14:39:09 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnide22827
	for <mpls@uu.net>; Fri, 27 Sep 2002 14:39:08 GMT
Received: from funnel.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnide22822
	for <mpls@uu.net>; Fri, 27 Sep 2002 14:39:08 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id KAA18579 for <mpls@uu.net>; Fri, 27 Sep 2002 10:39:07 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8REd7Y14305 for mpls@uu.net; Fri, 27 Sep 2002 10:39:07 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQnide22803
	for <mpls@mail-control.ash.ops.us.uu.net>; Fri, 27 Sep 2002 14:38: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 QQnide20792
	for <mpls@UU.NET>; Fri, 27 Sep 2002 14:37:56 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnide09087
	for <mpls@UU.NET>; Fri, 27 Sep 2002 14:37:55 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 QQnide09063
	for <mpls@UU.NET>; Fri, 27 Sep 2002 14:37:55 GMT
Received: (qmail 10630 invoked by uid 104); 27 Sep 2002 14:37:46 -0000
Received: from Shahram_Davari@pmc-sierra.com by father with qmail-scanner-1.00 (uvscan: v4.1.40/v4225. . Clean. Processed in 0.480041 secs); 27 Sep 2002 14:37:46 -0000
Received: from unknown (HELO hymir.pmc-sierra.bc.ca) (134.87.114.120)
  by father.pmc-sierra.bc.ca with SMTP; 27 Sep 2002 14:37:45 -0000
Received: from bby1exi01.pmc-sierra.bc.ca (bby1exi01.pmc-sierra.bc.ca [216.241.231.251])
	by hymir.pmc-sierra.bc.ca (jason/8.11.6) with ESMTP id g8REbjQ02313;
	Fri, 27 Sep 2002 07:37:45 -0700 (PDT)
Received: by bby1exi01 with Internet Mail Service (5.5.2656.59)
	id <TLWW7308>; Fri, 27 Sep 2002 07:38:14 -0700
Message-ID: <4B6D09F3B826D411A67300D0B706EFDEB03933@nt-exch-yow.pmc-sierra.bc.ca>
From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
To: "'Liu Qiang'" <qliu@lit.a-star.edu.sg>,
        "Reddy, Vikram"
	 <vikramr@netplane.com>, ccamp@ops.ietf.org,
        IETF MPLS List <mpls@UU.NET>
Subject: RE: Question on Control Channel -Data Channel association
Date: Fri, 27 Sep 2002 07:37:43 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mpls@UU.NET
Precedence: bulk

Hi,

What you described is permitted and in fact is used for example when per-platform
label spaces are used.

-Shahram

> 
> Hi all,
> 
> I have a question on the association of Control Channel and Data
> Channel. I would appreciate if somebody could answer it
> 
> In the following figure (A*,B*) are for Control Channel Interface
> addresses and  (X*,Y*) are for Data Channel Interface Addresses.
> Dotted lines (....) for control channel, Dashed line (----) for
> data channel.
> 
> 	      A1 .................................B1
>   Node 1      X1 ---------------------------------Y1     Node 2
>                   A2 .................................B2
> 
> In the above configuration can we have Node1 use A1-B1 for sending
> control messages for X1-Y1 but expect to receive control messages
> for X1-Y1 on A2-B2.
> Similarly can we have Node2 use B2-A2 for sending
> control messages for X1-Y1 but expect to receive control messages
> for X1-Y1 on B2-A2.
> 
> Is this prohibited and if it is, which document specifies it?
> 
> 
> Thanks,
> Vikram.
> 
> 
> 



From owner-mpls@UU.NET  Fri Sep 27 20:01:18 2002
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 ESMTP id UAA13861
	for <mpls-archive@lists.ietf.org>; Fri, 27 Sep 2002 20:01:18 -0400 (EDT)
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnieq02713
	for <mpls-archive@lists.ietf.org>; Sat, 28 Sep 2002 00:03:09 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnieq29531;
	Sat, 28 Sep 2002 00:01:46 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnieq08192
	for mpls-outgoing; Sat, 28 Sep 2002 00:01:20 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQnieq07404
	for <mpls@mail-control.ash.ops.us.uu.net>; Sat, 28 Sep 2002 00:01: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 QQnieq28441
	for <mpls@uu.net>; Sat, 28 Sep 2002 00:00:21 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnieq27636
	for <mpls@uu.net>; Sat, 28 Sep 2002 00:00:21 GMT
Received: from omnivergent.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: [63.99.209.9])
	id QQnieq27621
	for <mpls@uu.net>; Sat, 28 Sep 2002 00:00:21 GMT
Received: from pepsithechoice [24.219.16.65] by omnivergent.com with ESMTP
  (SMTPD32-7.07) id A0D11D1012E; Fri, 27 Sep 2002 18:59:13 -0500
From: "Shannon Lake" <shannon@omnivergent.com>
To: <mpls@UU.NET>
Subject: Economic Justification for MPLS
Date: Fri, 27 Sep 2002 17:00:14 -0700
Message-ID: <007e01c26682$08fc9db0$640a0a0a@pepsithechoice>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_007F_01C26647.5C9DC5B0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_007F_01C26647.5C9DC5B0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0080_01C26647.5C9DC5B0"


------=_NextPart_001_0080_01C26647.5C9DC5B0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Ladies and Gentlemen:

 

I have been doing some research looking for the economic justification
for MPLS?  Does anyone have a paper, website, etc that explains why
carriers would implement MPLS (other than technical)?  
I understand its technical merits, but I am really interested in its
economic and/or other rationale for MPLS.

  

Thanks in advance, 

 

Shannon M. Lake Sr.

 


------=_NextPart_001_0080_01C26647.5C9DC5B0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I have been doing some research looking for the =
economic justification
for MPLS?&nbsp; Does anyone have a paper, website, etc that explains why
carriers would implement MPLS (other than technical)? &nbsp;<br>
I understand its technical merits, but I am really interested in its =
economic
and/or other rationale for MPLS.</span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thanks in advance, </span></font></p>

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

<p class=3DMsoAutoSig><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Shannon M. Lake Sr.</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

</div>

</body>

</html>

------=_NextPart_001_0080_01C26647.5C9DC5B0--

------=_NextPart_000_007F_01C26647.5C9DC5B0
Content-Type: text/x-vcard;
	name="Shannon M. Lake Sr. (shannon@omnivergent.com).vcf"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="Shannon M. Lake Sr. (shannon@omnivergent.com).vcf"
Content-Transfer-Encoding: quoted-printable

BEGIN:VCARD
VERSION:2.1
N:Lake;Shannon;M.;;Sr.
FN:Shannon M. Lake Sr. (shannon@omnivergent.com)
ORG:OMNIVERGENT Communications
TITLE:CEO
TEL;WORK;VOICE:(408) 366-0383
TEL;CELL;VOICE:(408) 507-0359
TEL;WORK;FAX:(413) 208-8540
ADR;WORK:;;5255 Stevens Creek Bvld #282;Santa Clara;CA;95051;United =
States of America
LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:5255 Stevens Creek Bvld =
#282=3D0D=3D0ASanta Clara, CA 95051=3D0D=3D0AUnited States o=3D
f America
URL;WORK:http://www.omnivergent.com
EMAIL;PREF;INTERNET:shannon@omnivergent.com
REV:20020731T065335Z
END:VCARD

------=_NextPart_000_007F_01C26647.5C9DC5B0--




From owner-mpls@UU.NET  Fri Sep 27 21:11:42 2002
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 ESMTP id VAA15133
	for <mpls-archive@lists.ietf.org>; Fri, 27 Sep 2002 21:11:41 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnieu04213
	for <mpls-archive@lists.ietf.org>; Sat, 28 Sep 2002 01:13:33 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnieu03610;
	Sat, 28 Sep 2002 01:13:17 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnieu09954
	for mpls-outgoing; Sat, 28 Sep 2002 01:13:04 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnieu09944
	for <mpls@mail-control.ash.ops.us.uu.net>; Sat, 28 Sep 2002 01:12:58 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 QQnieu14630
	for <mpls@UU.NET>; Sat, 28 Sep 2002 01:12:52 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnieu09546
	for <mpls@UU.NET>; Sat, 28 Sep 2002 01:12:52 GMT
Received: from web20804.mail.yahoo.com by cmr2.ash.ops.us.uu.net with SMTP 
	(peer crosschecked as: web20804.mail.yahoo.com [216.136.226.193])
	id QQnieu09527
	for <mpls@UU.NET>; Sat, 28 Sep 2002 01:12:51 GMT
Message-ID: <20020928011250.55621.qmail@web20804.mail.yahoo.com>
Received: from [134.193.6.40] by web20804.mail.yahoo.com via HTTP; Fri, 27 Sep 2002 18:12:50 PDT
Date: Fri, 27 Sep 2002 18:12:50 -0700 (PDT)
From: senthil ayyasamy <mplsgeek@yahoo.com>
Subject: Re: Economic Justification for MPLS
To: Shannon Lake <shannon@omnivergent.com>, mpls@UU.NET
In-Reply-To: <007e01c26682$08fc9db0$640a0a0a@pepsithechoice>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mpls@UU.NET
Precedence: bulk


> I have been doing some research looking for the
> economic justification
> for MPLS?  Does anyone have a paper, website, etc
> that explains why
> carriers would implement MPLS (other than
> technical)?  
> I understand its technical merits, but I am really
> interested in its
> economic and/or other rationale for MPLS.
If you have access to cookreport
(http://www.cookreport.com/)...you can get lot of
information.




__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com


From owner-mpls@UU.NET  Fri Sep 27 23:42:46 2002
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 ESMTP id XAA17471
	for <mpls-archive@lists.ietf.org>; Fri, 27 Sep 2002 23:42:45 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnife13277
	for <mpls-archive@lists.ietf.org>; Sat, 28 Sep 2002 03:44:38 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnife12481;
	Sat, 28 Sep 2002 03:44:11 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnife23353
	for mpls-outgoing; Sat, 28 Sep 2002 03:43:58 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQnife23348
	for <mpls@mail-control.ash.ops.us.uu.net>; Sat, 28 Sep 2002 03: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 QQnife24083
	for <mpls@uu.net>; Sat, 28 Sep 2002 03:43:03 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnife09487
	for <mpls@uu.net>; Sat, 28 Sep 2002 03:43:03 GMT
Received: from funnel.cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: funnel.cisco.com [161.44.168.79])
	id QQnife09483
	for <mpls@uu.net>; Sat, 28 Sep 2002 03:43:02 GMT
Received: from erosen-u10.cisco.com (erosen-u10.cisco.com [161.44.134.50]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id XAA13146 for <mpls@uu.net>; Fri, 27 Sep 2002 23:43:02 -0400 (EDT)
Received: (erosen@localhost) by erosen-u10.cisco.com (8.11.2/CISCO.WS.1.2) id g8S3h2E22460 for mpls@uu.net; Fri, 27 Sep 2002 23:43:02 -0400 (EDT)
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQnife23317
	for <mpls@mail-control.ash.ops.us.uu.net>; Sat, 28 Sep 2002 03:41:41 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 QQnife24853
	for <mpls@UU.NET>; Sat, 28 Sep 2002 03:40:02 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnife07887
	for <mpls@UU.NET>; Sat, 28 Sep 2002 03:40:01 GMT
Received: from cisco.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: uzura.cisco.com [64.102.17.77])
	id QQnife07880
	for <mpls@UU.NET>; Sat, 28 Sep 2002 03:40:01 GMT
Received: from asimha-u10.cisco.com (asimha-u10.cisco.com [64.102.48.65])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id XAA26744;
	Fri, 27 Sep 2002 23:40:00 -0400 (EDT)
Date: Fri, 27 Sep 2002 23:40:00 -0400 (EDT)
From: Ajay Simha <asimha@cisco.com>
To: Shannon Lake <shannon@omnivergent.com>
cc: mpls@UU.NET
Subject: Re: Economic Justification for MPLS
In-Reply-To: <007e01c26682$08fc9db0$640a0a0a@pepsithechoice>
Message-ID: <Pine.GSO.4.44.0209272304180.9461-100000@asimha-u10.cisco.com>
References: <007e01c26682$08fc9db0$640a0a0a@pepsithechoice>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mpls@UU.NET
Precedence: bulk

On Fri, 27 Sep 2002, Shannon Lake wrote:

>SL:Ladies and Gentlemen:
>SL:
>SL:
>SL:
>SL:I have been doing some research looking for the economic justification
>SL:for MPLS?  Does anyone have a paper, website, etc that explains why
>SL:carriers would implement MPLS (other than technical)?
>SL:I understand its technical merits, but I am really interested in its
>SL:economic and/or other rationale for MPLS.

Hi Shannon,

Let me begin by saying that MPLS is one of the ways of having a common core
for a SP to provide various types of services (Folks on this mailing list may
have other ideas/opinions as well).

The following services/applications may be enabled by MPLS:

- MPLS Forwarding(LDP based Core): Integration of IP+ATM, Enables L2/L3 VPNs,
  Transparent QoS. This allows for a SP to restrict growth of legacy L2
  transport service. For example stop buying/deploying more Frame Relay
  Switches. However, there are customers who may want FR service at a POP
  where this SP does not have FR reachability. In such cases the SP may choose
  to do something like FRoMPLS to bring this customers into the FR network

- MPLS TE: If a service provider can deploy MPLS-TE to squeeze more bandwidth
  out of their network, they may able to postpone buying expensive highspeed
  links for a while. Avoiding OC48/OC192 links for even 6 months could add up

- L3 VPNs: traditionally if customer wanted their remote offices (Banks for
  example) to be interconnected, they would be say Frame or ATM services and
  either manage their WAN routing themselves, buy managed services from the SP
  OR outsource WAN routing. With MPLS L3 VPNs they can do simple routing
 (RIPv2/Static) and interconnect their offices and avoid this overhead.

- L2/L3 VPNs: The savings from having a common core for various services get
  passed on to the customers. If they SP had to have dedicated circuits for
  these customers it obviously costs more money.

These are some of the points that I could come up with. Not everyone applies
in all situations...

Regards,

-ajay



>SL:
>SL:
>SL:
>SL:Thanks in advance,
>SL:
>SL:
>SL:
>SL:Shannon M. Lake Sr.
>SL:
>SL:
>SL:
>SL:




From owner-mpls@UU.NET  Sat Sep 28 18:27:53 2002
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 ESMTP id SAA12414
	for <mpls-archive@lists.ietf.org>; Sat, 28 Sep 2002 18:27:52 -0400 (EDT)
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnihy06215;
	Sat, 28 Sep 2002 21:34:29 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnihy03363
	for mpls-outgoing; Sat, 28 Sep 2002 21:33:58 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQnihy03358
	for <mpls@mail-control.ash.ops.us.uu.net>; Sat, 28 Sep 2002 21:33: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 QQnihx26003
	for <mpls@UU.NET>; Sat, 28 Sep 2002 21:29:19 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnihx21032
	for <mpls@UU.NET>; Sat, 28 Sep 2002 21:29:19 GMT
Received: from traven9.uol.com.br by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: traven9.uol.com.br [200.221.4.35])
	id QQnihx21025
	for <mpls@UU.NET>; Sat, 28 Sep 2002 21:29:18 GMT
Received: from lavoisie3z0va6 ([200.227.183.175])
	by traven9.uol.com.br (8.9.1/8.9.1) with ESMTP id SAA08248
	for <mpls@UU.NET>; Sat, 28 Sep 2002 18:30:59 -0300 (BRT)
From: "Lavoisier J.L.Farias" <lavoisier_farias@uol.com.br>
To: <mpls@UU.NET>
Subject: MPLS Traffic Parameters
Date: Sat, 28 Sep 2002 18:29:14 -0300
Organization: Lavoisier
Message-ID: <000001c26736$184ba220$afb7e3c8@lavoisie3z0va6>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0001_01C2671C.F2FE6A20"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0001_01C2671C.F2FE6A20
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Ladies and Gentlemen,
 
At first I apologize due my beginners  questions!!
 
I am currently working at my master thesis, and modelling the ATM-MPLS
Interworking, so I would like to know what are the traffic parameters
used to establish LSPs on MPLS like the parameters specified in ATM.
Does RSVP-TE can guarantee this ? ATM establishes a PVC/SVC based on
traffic class (CBR, VBR-rt, VBR-nrt, UBR or ABR) and the follwing
traffic parameters: PCR, SCR, MBS, CLR, CTD. Lets suppoese that I am
doing the interworking of PVC, VBT-rt, is there exist some mapping
between the ATM traffic parameters and MPLS traffic parameters used by
RSVP-TE ?
 
In addition to that, does RSVP-TE specify some Admission Control
Algorithm like in ATM that specifies GRCA ?
 
Thank you in advance,
 
Best Regards,
 
Lavoisier Farias.
 
PS> Any help will be more than welcomed!! 

------=_NextPart_000_0001_01C2671C.F2FE6A20
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C2671C.F220B450">
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:EnvelopeVis/>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
  </w:Compatibility>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EstiloDeEmail17
	{mso-style-type:personal-compose;
	mso-style-noshow:yes;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:windowtext;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;
	mso-header-margin:35.4pt;
	mso-footer-margin:35.4pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Tabela normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]-->
</head>

<body lang=3DPT-BR link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:35.4pt'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-US'>Ladies and =
Gentlemen,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-US'>At first I apologize =
due my beginners
<span =
style=3D'mso-spacerun:yes'>&nbsp;</span>questions!!<o:p></o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-US'>I am currently working =
at my
master thesis, and modelling the ATM-MPLS Interworking, so I would like =
to know
what are the traffic parameters used to establish LSPs on MPLS like the
parameters specified in ATM. Does RSVP-TE can guarantee this ? ATM =
establishes
a PVC/SVC based on traffic class (CBR, VBR-rt, VBR-nrt, UBR or ABR) and =
the
follwing traffic parameters: PCR, SCR, MBS, CLR, CTD. Lets suppoese that =
I am
doing the interworking of PVC, VBT-rt, is there exist some mapping =
between the
ATM traffic parameters and MPLS traffic parameters used by RSVP-TE =
?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-US'>In addition to that, =
does
RSVP-TE specify some Admission Control Algorithm like in ATM that =
specifies GRCA
?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-US'>Thank you in =
advance,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-US'>Best =
Regards,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-US'>Lavoisier =
Farias.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-US'><o:p>&nbsp;</o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-US'>PS&gt; Any help will =
be more
than welcomed!! </span></font><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US'><o:p></o:p></span></p>

</div>

</body>

</html>

------=_NextPart_000_0001_01C2671C.F2FE6A20--



From owner-mpls@UU.NET  Sun Sep 29 02:01:39 2002
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 ESMTP id CAA20801
	for <mpls-archive@lists.ietf.org>; Sun, 29 Sep 2002 02:01:39 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnijg23602
	for <mpls-archive@lists.ietf.org>; Sun, 29 Sep 2002 06:03:31 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnijg22491;
	Sun, 29 Sep 2002 06:02:55 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnijg00488
	for mpls-outgoing; Sun, 29 Sep 2002 06:02:24 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQnijg00427
	for <mpls@mail-control.ash.ops.us.uu.net>; Sun, 29 Sep 2002 06:02: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 QQnijg16166
	for <mpls@UU.NET>; Sun, 29 Sep 2002 06:00:47 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnijg14291
	for <mpls@UU.NET>; Sun, 29 Sep 2002 06:00:47 GMT
Received: from mtiwmhc13.worldnet.att.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mtiwmhc13.worldnet.att.net [204.127.131.117])
	id QQnijg14275
	for <mpls@UU.NET>; Sun, 29 Sep 2002 06:00:46 GMT
Received: from 6640bbc3r131 ([12.81.0.251]) by mtiwmhc13.worldnet.att.net
          (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with SMTP
          id <20020929060040.NOEI8019.mtiwmhc13.worldnet.att.net@6640bbc3r131>;
          Sun, 29 Sep 2002 06:00:40 +0000
Message-ID: <009101c2677d$ab682fa0$fb00510c@6640bbc3r131>
From: "Brijesh Kumar" <brijesh.kumar@att.net>
To: "Shannon Lake" <shannon@omnivergent.com>, <mpls@UU.NET>
References: <007e01c26682$08fc9db0$640a0a0a@pepsithechoice>
Subject: Re: Economic Justification for MPLS
Date: Sat, 28 Sep 2002 23:01:33 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_008E_01C26742.FD874B80"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-mpls@UU.NET
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_008E_01C26742.FD874B80
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Shannon,

The ecomomic utility of technology like MPLS will vary from a carrier to =
another carrier depending on what kind of infrastructure they already  =
have. You may have better luck in getting meaningful (planned and =
actual) ROI data if you ask this questions on nanog list since some of =
the carriers who  have deployed technology may have done this economic =
modeling before deployment, and may be willing to share some of this =
info with you. Good luck!

cheers,

--brijesh
  ----- Original Message -----=20
  From: Shannon Lake=20
  To: mpls@UU.NET=20
  Sent: Friday, September 27, 2002 5:00 PM
  Subject: Economic Justification for MPLS


  Ladies and Gentlemen:



  I have been doing some research looking for the economic justification =
for MPLS?  Does anyone have a paper, website, etc that explains why =
carriers would implement MPLS (other than technical)? =20
  I understand its technical merits, but I am really interested in its =
economic and/or other rationale for MPLS.

   =20

  Thanks in advance,=20



  Shannon M. Lake Sr.




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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR>
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in =
1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
P.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>Shannon,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>The ecomomic utility of technology like =

MPLS&nbsp;will vary from a carrier to another carrier depending on what =
kind of=20
infrastructure they already &nbsp;have.&nbsp;You may have better luck in =
getting=20
meaningful (planned and actual) ROI data if you ask&nbsp;this questions=20
on&nbsp;nanog list since some of the carriers who&nbsp; have deployed=20
technology&nbsp;may have done this economic modeling before deployment, =
and may=20
be willing to share some of this info with you. Good luck!</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>cheers,</DIV>
<DIV>&nbsp;</DIV>
<DIV>--brijesh</DIV></FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-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 title=3Dshannon@omnivergent.com =
href=3D"mailto:shannon@omnivergent.com">Shannon=20
  Lake</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3Dmpls@UU.NET=20
  href=3D"mailto:mpls@UU.NET">mpls@UU.NET</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Friday, September 27, =
2002 5:00=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Economic Justification =
for=20
  MPLS</DIV>
  <DIV><BR></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Ladies and=20
  Gentlemen:</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I have been doing some =
research=20
  looking for the economic justification for MPLS?&nbsp; Does anyone =
have a=20
  paper, website, etc that explains why carriers would implement MPLS =
(other=20
  than technical)? &nbsp;<BR>I understand its technical merits, but I am =
really=20
  interested in its economic and/or other rationale for =
MPLS.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp; =
</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Thanks in advance,=20
  </SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoAutoSig><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Shannon M. Lake=20
  Sr.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: =
12pt"></SPAN></FONT>&nbsp;</P></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_008E_01C26742.FD874B80--



From owner-mpls@UU.NET  Mon Sep 30 01:46:50 2002
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 ESMTP id BAA15283
	for <mpls-archive@lists.ietf.org>; Mon, 30 Sep 2002 01:46:50 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnimx15261
	for <mpls-archive@lists.ietf.org>; Mon, 30 Sep 2002 05:48:41 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnimx14339;
	Mon, 30 Sep 2002 05:48:14 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnimx01736
	for mpls-outgoing; Mon, 30 Sep 2002 05:47:48 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQnimx01729
	for <mpls@mail-control.ash.ops.us.uu.net>; Mon, 30 Sep 2002 05:47: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 QQnimx08742
	for <mpls@uu.net>; Mon, 30 Sep 2002 05:47:03 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnimx12701
	for <mpls@uu.net>; Mon, 30 Sep 2002 05:47:02 GMT
Received: from blooper.utfors.se by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail.utfors.se [195.58.103.125])
	id QQnimx12693
	for <mpls@uu.net>; Mon, 30 Sep 2002 05:47:02 GMT
Received: from utfors.se (nat-sto.utfors.se [212.73.0.237])
	by blooper.utfors.se (8.12.6/8.12.6) with ESMTP id g8U5kRtA012847;
	Mon, 30 Sep 2002 07:46:27 +0200 (MEST)
Message-ID: <3D97E533.2020107@utfors.se>
Date: Mon, 30 Sep 2002 07:46:27 +0200
From: Loa Andersson <loa.andersson@utfors.se>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ospf wg <OSPF@DISCUSS.MICROSOFT.COM>, isis-wg <isis-wg@ietf.org>
CC: Loa Andersson <loa.andersson@utfors.se>, MPLS wg <mpls@UU.NET>
Subject: Last Call: draft-ietf-mpls-bundle-04.txt - has ended
References: <3D6DBFBE.4050603@utfors.se> <3D7CC9FF.6010509@utfors.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit

All,

the last call on the

<draft-ietf-mpls-bundle-04.txt>

on the ospf and isis list has ended. Thanks for comments.

/Loa

Loa Andersson wrote:
> All,
> 
> it is my understanding that there has been some hick-ups on
> the is-is list, so I'm re-issueing this last call and extending
> the time to September 29th. At the same time I would like point out
> that there is an acompanying mib draft-ietf-mpls-bundle-mib-03.txt.
> 
> Also comments on the mib is welcome.
> 
> BTW, thanks to those of you who already sent us comments :)
> 
> The wg last call on
> 
>  <draft-ietf-mpls-bundle-04.txt>
>  <draft-ietf-mpls-bundle-mib-03.txt>
> 
> has been extended to September 29.
> 
> /Loa
> 
> Loa Andersson wrote:
> 
>> OSPF and IS-IS working groups, (mpls wg for info)
>>
>> the iesg has started the review of the mpls working group draft
>> draft-ietf-mpls-bundle-04.txt. The immediate response from the iesg
>> is that the draft contains OSPF and ISIS related details (see
>> the included mail). After discussing with the wg chairs for ospf
>> and is-is working groups, there is a feeling that the two weeks
>> the iesg allocated for this last call might not be enough, since the
>> draft has not been widely circulated in the routing working groups.
>>
>> Therefore:
>>
>> This is to initiate a last call for the
>>
>> <draft-ietf-mpls-bundle-04.txt>
>>
>> by the ospf and is-is working groups.
>> The last call ends September 22nd at 12PM CET
>>
>>
>> Please include the mpls mailing list (mpls@uu.net) in your responses.
>>
>> /Loa (co-chair of the mpls wg)
>>
>> -------- Original Message --------
>> Subject: draft-ietf-mpls-bundle-04.txt
>> Date: Tue, 27 Aug 2002 15:06:48 -0400 (EDT)
>> From: Scott Bradner
>> To: loa.andersson@utfors.se, swallow@cisco.com
>>
>>
>> The IESG discussed this ID last week during its teleconference
>> one issue was raised during the discussion
>>
>> "the draft contains OSPF & ISIS
>> related details and I don't remember it being LC'ed or reviewed
>> in the corresponding WGs."
>>
>> can you start a 2 week last call on the IS-IS and OSPF mailing
>> lists for this document?
>>
>> Scott
>>
> 
> 


-- 
     Loa Andersson
     Chief Architect,
     Utfors Research, Architecture and Future Lab (URAX)
     Utfors AB
     R錽undav鋑en 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 Sep 30 03:29:17 2002
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 ESMTP id DAA25764
	for <mpls-archive@lists.ietf.org>; Mon, 30 Sep 2002 03:29:17 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnine08020
	for <mpls-archive@lists.ietf.org>; Mon, 30 Sep 2002 07:31:12 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnine07425;
	Mon, 30 Sep 2002 07:30:56 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnine11741
	for mpls-outgoing; Mon, 30 Sep 2002 07:30:40 GMT
Received: from imr0.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11])
	id QQnine11735
	for <mpls@mail-control.ash.ops.us.uu.net>; Mon, 30 Sep 2002 07:30:36 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 QQnind08656
	for <mpls@uu.net>; Mon, 30 Sep 2002 07:29:51 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnind17854
	for <mpls@uu.net>; Mon, 30 Sep 2002 07:29:51 GMT
Received: from blooper.utfors.se by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail.utfors.se [195.58.103.125])
	id QQnind17849
	for <mpls@uu.net>; Mon, 30 Sep 2002 07:29:50 GMT
Received: from utfors.se (nat-sto.utfors.se [212.73.0.237])
	by blooper.utfors.se (8.12.6/8.12.6) with ESMTP id g8U7TetA016437;
	Mon, 30 Sep 2002 09:29:40 +0200 (MEST)
Message-ID: <3D97FD64.1030707@utfors.se>
Date: Mon, 30 Sep 2002 09:29:40 +0200
From: Loa Andersson <loa.andersson@utfors.se>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: MPLS wg <mpls@UU.NET>
CC: George Swallow <swallow@cisco.com>,
        Loa Andersson
 <loa.andersson@utfors.se>
Subject: wg lst call on ft/restart drafts
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-mpls@UU.NET
Precedence: bulk
Content-Transfer-Encoding: 8bit

All,

this is to initiate a wg last call on the following drafts.

draft-ietf-mpls-bgp-mpls-restart-01.txt
draft-ietf-mpls-ldp-restart-03.txt
draft-ietf-mpls-ldp-ft-05.txt


All draft has been through wg last call and been updated according
to the comments in the last call. The normal way of doing this would
be to restrict the comments in this last call to the changes only,
however in this case I would like to invite comments on the
drafts as a group, since there has been a need to coordinate them.

Further information on this is found in:

<draft-farrel-mpls-ldp-restart-applic-00.txt>

This document is not yet up for a last call, but, as a first step,
we propose it to become a working group document. Comments on the
draft will be viewed in this context.

The last call will end October 13th  12.00 PM GMT


/Loa
-- 
     Loa Andersson
     Chief Architect,
     Utfors Research, Architecture and Future Lab (URAX)
     Utfors AB
     R錽undav鋑en 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 Sep 30 06:26:30 2002
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 ESMTP id GAA27786
	for <mpls-archive@lists.ietf.org>; Mon, 30 Sep 2002 06:26:29 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQninp10828
	for <mpls-archive@lists.ietf.org>; Mon, 30 Sep 2002 10:28:23 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQninp10241;
	Mon, 30 Sep 2002 10:28:07 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQninp13409
	for mpls-outgoing; Mon, 30 Sep 2002 10:27:17 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQninp13404
	for <mpls@mail-control.ash.ops.us.uu.net>; Mon, 30 Sep 2002 10:27: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 QQninp20638
	for <mpls@UU.NET>; Mon, 30 Sep 2002 10:23:26 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQninp17066
	for <mpls@UU.NET>; Mon, 30 Sep 2002 10:23:25 GMT
Received: from mail2.hd.intel.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: hdfdns02.hd.intel.com [192.52.58.11])
	id QQninp17054
	for <mpls@UU.NET>; Mon, 30 Sep 2002 10:23:25 GMT
Received: from fmsmsxvs041.fm.intel.com (fmsmsxvs041.fm.intel.com [132.233.42.126])
	by mail2.hd.intel.com (8.11.6/8.11.6/d: solo.mc,v 1.46 2002/09/23 20:41:22 dmccart Exp $) with SMTP id g8UANOd28166
	for <mpls@UU.NET>; Mon, 30 Sep 2002 10:23:24 GMT
Received: from FMSMSX017.fm.intel.com ([132.233.42.196])
 by fmsmsxvs041.fm.intel.com (NAVGW 2.5.2.11) with SMTP id M2002093003221628072
 for <mpls@UU.NET>; Mon, 30 Sep 2002 03:22:16 -0700
Received: by fmsmsx017.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <TB2QMCDV>; Mon, 30 Sep 2002 03:23:24 -0700
Message-ID: <12B638FEE763F74696D8544752E7204826467F@bgsmsx101.iind.intel.com>
From: "Gowda, Sidde" <sidde.gowda@intel.com>
To: "'mpls@UU.NET'" <mpls@UU.NET>
Subject: Martini
Date: Mon, 30 Sep 2002 03:18: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

Hi All

Do Martini drafts talks about label request?
What does that label mapping request means?
If I release the label (or withdraw) then I have to send this message. Am I
really requesting for a label in this situation?

Thanks & Regards,
/*-----------------------------------------------------------------*/
 void siddu.b.gowda {
        char* company="INTEL CORP";
        long   residence phone= 3396926;
        char* email="sidde.gowda@intel.com";
        int     extension=2505;
        ulong wwid=10665328;
     };
/*------------------------------------------------------------------*/



From owner-mpls@UU.NET  Mon Sep 30 06:44:53 2002
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 ESMTP id GAA28041
	for <mpls-archive@lists.ietf.org>; Mon, 30 Sep 2002 06:44:53 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQninr03672
	for <mpls-archive@lists.ietf.org>; Mon, 30 Sep 2002 10:46:46 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQninr02409;
	Mon, 30 Sep 2002 10:46:14 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQninr14605
	for mpls-outgoing; Mon, 30 Sep 2002 10:45:48 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQninr14598
	for <mpls@mail-control.ash.ops.us.uu.net>; Mon, 30 Sep 2002 10:45: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 QQninq01145
	for <mpls@UU.NET>; Mon, 30 Sep 2002 10:44:09 GMT
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQninq00533
	for <mpls@UU.NET>; Mon, 30 Sep 2002 10:44:08 GMT
Received: from momus.sc.intel.com by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: momus.sc.intel.com [143.183.152.8])
	id QQninq00521
	for <mpls@UU.NET>; Mon, 30 Sep 2002 10:44:07 GMT
Received: from fmsmsxvs042.fm.intel.com (fmsmsxvs042.fm.intel.com [132.233.42.128])
	by momus.sc.intel.com (8.11.6/8.11.6/d: solo.mc,v 1.46 2002/09/23 20:41:22 dmccart Exp $) with SMTP id g8UAhg227284
	for <mpls@UU.NET>; Mon, 30 Sep 2002 10:43:52 GMT
Received: from fmsmsx28.fm.intel.com ([132.233.42.28])
 by fmsmsxvs042.fm.intel.com (NAVGW 2.5.2.11) with SMTP id M2002093003445621537
 for <mpls@UU.NET>; Mon, 30 Sep 2002 03:44:56 -0700
Received: by fmsmsx28.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <S62NYP1F>; Mon, 30 Sep 2002 03:43:27 -0700
Message-ID: <12B638FEE763F74696D8544752E72048025441F4@bgsmsx101.iind.intel.com>
From: "Manchanda, Monika" <monika.manchanda@intel.com>
To: "Mpls (E-mail)" <mpls@UU.NET>
Subject: Regarding Label Mapping Advertisements and Label Mapping Release 
	in maritini-trans-10
Date: Mon, 30 Sep 2002 03:38:52 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2686D.91E36CC0"
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_01C2686D.91E36CC0
Content-Type: text/plain;
	charset="iso-8859-1"

Hi,
 
 1. The maritini draft section 5.4.1. Label Mapping Advertisements says that

 
"   After a label has been withdrawn by the disposition router and/or
   released by the imposition router, care must be taken to not re-
   advertise (re-use) the released label until the disposition router
   can be reasonably certain that old packets containing the released
   label no longer persist in the MPLS network."
 
According to this the implementation should no re issue the same label for
some time period t, which should ideally be the time till all the packets
containing the released label reach the disposition router. But how do we
determine that what will be the value of t?
 
2. Also the section 5.4.2. Label Mapping Release says that 
 
   "In situations where the imposition router wants to restart forwarding
   of packets with sequence number 1, the router shall 1) Send to
   disposition router a label mapping release, and 2) Send to
   disposition router a label mapping request."
 
Here what do we exactly mean by label mapping release and label mapping
request? 
 
TIA and Regards,
-Monika 

------_=_NextPart_001_01C2686D.91E36CC0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

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

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C2689C.4A1FCC60">
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
@font-face
	{font-family:"MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;
	mso-font-alt:"\FF2D\FF33 \660E\671D";
	mso-font-charset:128;
	mso-generic-font-family:roman;
	mso-font-format:other;
	mso-font-pitch:fixed;
	mso-font-signature:1 134676480 16 0 131072 0;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;
	mso-font-charset:128;
	mso-generic-font-family:roman;
	mso-font-format:other;
	mso-font-pitch:fixed;
	mso-font-signature:1 134676480 16 0 131072 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:"Times New Roman";}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
span.EmailStyle15
	{mso-style-type:personal-compose;
	mso-ansi-font-size:10.0pt;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:black;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
</head>

<body lang=3DEN-US style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D3 =
color=3Dblack
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;mso-ansi-font-size:12.0pt;
mso-ascii-font-family:"Times New Roman";mso-hansi-font-family:"Times =
New Roman";
mso-bidi-font-family:"Times New =
Roman"'>Hi,<o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D3 =
color=3Dblack
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;mso-ansi-font-size:12.0pt;
mso-ascii-font-family:"Times New Roman";mso-hansi-font-family:"Times =
New Roman";
mso-bidi-font-family:"Times New Roman"'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D3 =
color=3Dblack
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;mso-ansi-font-size:12.0pt;
mso-ascii-font-family:"Times New Roman";mso-hansi-font-family:"Times =
New Roman";
mso-bidi-font-family:"Times New Roman"'><span style=3D"mso-spacerun:
yes">&nbsp;</span>1. The maritini draft section =
</span></font></span><font
color=3Dblack><span style=3D'mso-fareast-font-family:"MS =
Mincho";color:black'>5.4.1.
Label Mapping Advertisements</span><span class=3DEmailStyle15><font =
color=3Dblack><span
style=3D'mso-ansi-font-size:12.0pt;mso-ascii-font-family:"Times New =
Roman";
mso-hansi-font-family:"Times New Roman";mso-bidi-font-family:"Times New =
Roman"'>
says that</span></font></span></font><span class=3DEmailStyle15><font =
size=3D2
color=3Dblack face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
font-family:Arial'> <o:p></o:p></span></font></span></p>

<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'><![if =
!supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></font></span></p>=


<p class=3DMsoPlainText style=3D'margin-left:.5in'><span =
class=3DEmailStyle15><font
size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>&#8220;</span></font></span=
><font
color=3Dblack><span style=3D'mso-fareast-font-family:"MS =
Mincho";color:black'><span
style=3D"mso-spacerun: yes">&nbsp;&nbsp; </span>After a label has been =
withdrawn
by the disposition router and/or<br>
<span style=3D"mso-spacerun:
yes">&nbsp;&nbsp; </span>released by the imposition router, care must =
be taken
to not re-<br>
<span style=3D"mso-spacerun: yes">&nbsp;&nbsp; </span>advertise
(re-use) the released label until the disposition router<br>
<span
style=3D"mso-spacerun: yes">&nbsp;&nbsp; </span>can be reasonably =
certain that
old packets containing the released<br>
<span style=3D"mso-spacerun:
yes">&nbsp;&nbsp; </span>label no longer persist in the MPLS =
network.&#8221;</span></font><font
color=3Dblack><span style=3D'mso-fareast-font-family:"MS =
Mincho";color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblack
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;mso-fareast-font-family:"MS Mincho";
color:black'><![if =
!supportEmptyParas]>&nbsp;<![endif]></span></font><font
color=3Dblack><span style=3D'mso-fareast-font-family:"MS =
Mincho";color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'margin-left:.5in'><font size=3D3 =
color=3Dblack
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;mso-bidi-font-size:10.0pt;
font-family:"Times New Roman";mso-fareast-font-family:"MS =
Mincho";color:black'>According
to this the implementation should no re issue the same label for some =
time
period t, which should ideally be the time till all the packets =
containing the
released label reach the disposition router. But how do we determine =
that what
will be the value of t?</span></font><font size=3D3 color=3Dblack
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;mso-bidi-font-size:10.0pt;
font-family:"Times New Roman";mso-fareast-font-family:"MS =
Mincho";color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoPlainText><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;mso-bidi-font-size:10.0pt;font-family:"Times =
New Roman";
mso-fareast-font-family:"MS Mincho";color:black'><![if =
!supportEmptyParas]>&nbsp;<![endif]></span></font><font
size=3D3 color=3Dblack face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
mso-bidi-font-size:10.0pt;font-family:"Times New =
Roman";mso-fareast-font-family:
"MS =
Mincho";color:black;mso-color-alt:windowtext'><o:p></o:p></span></font><=
/p>

<p class=3DMsoNormal><span class=3DEmailStyle15><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:
Arial'>2. Also the section </span></font></span><font =
color=3Dblack><span
style=3D'mso-fareast-font-family:"MS Mincho";color:black'>5.4.2. Label =
Mapping
Release says that </span></font><font color=3Dblack><span =
style=3D'mso-fareast-font-family:
"MS =
Mincho";color:black;mso-color-alt:windowtext'><o:p></o:p></span></font><=
/p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;mso-fareast-font-family:"MS =
Mincho";color:black'><![if =
!supportEmptyParas]>&nbsp;<![endif]></span></font><font
color=3Dblack><span style=3D'mso-fareast-font-family:"MS =
Mincho";color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoPlainText style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblack
face=3D"Courier New"><span style=3D'font-size:10.0pt;mso-fareast-font-fa=
mily:"MS Mincho";
color:black'><span style=3D"mso-spacerun: yes">&nbsp;&nbsp; =
</span>&#8220;In situations
where the imposition router wants to restart forwarding<br>
<span
style=3D"mso-spacerun: yes">&nbsp;&nbsp; </span>of packets with =
sequence number
1, the router shall 1) Send to<br>
<span style=3D"mso-spacerun:
yes">&nbsp;&nbsp; </span>disposition router a label mapping release, =
and 2)
Send to<br>
</span></font><font color=3Dblack><span style=3D'mso-bidi-font-size:
12.0pt;mso-fareast-font-family:"MS Mincho";color:black'><span
style=3D"mso-spacerun: yes">&nbsp;&nbsp; </span>disposition router a =
label
mapping request.&#8221;</span></font><font color=3Dblack><span =
style=3D'mso-bidi-font-size:
12.0pt;mso-fareast-font-family:"MS =
Mincho";color:black;mso-color-alt:windowtext'><o:p></o:p></span></font><=
/p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D2 =
color=3Dblack
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
font-family:"Courier New";mso-fareast-font-family:"MS =
Mincho";color:black'><![if =
!supportEmptyParas]>&nbsp;<![endif]></span></font><font
size=3D2 color=3Dblack face=3D"Courier New"><span =
style=3D'font-size:10.0pt;mso-bidi-font-size:
12.0pt;font-family:"Courier New";mso-fareast-font-family:"MS Mincho";
color:black;mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
color=3Dblack
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;mso-fareast-font-family:
"MS Mincho";color:black'>Here what do we exactly mean by label mapping =
release
and label mapping request? </span></font><font color=3Dblack><span
style=3D'mso-fareast-font-family:"MS =
Mincho";color:black;mso-color-alt:windowtext'><o:p></o:p></span></font><=
/p>

<p class=3DMsoNormal style=3D'margin-left:.5in'><font size=3D3 =
color=3Dblack
face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;mso-fareast-font-family:
"MS Mincho";color:black'><![if =
!supportEmptyParas]>&nbsp;<![endif]></span></font><font
color=3Dblack><span style=3D'mso-fareast-font-family:"MS =
Mincho";color:black;
mso-color-alt:windowtext'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;mso-fareast-font-family:"MS =
Mincho";color:black'>TIA
and Regards,</span></font><font color=3Dblack><span =
style=3D'mso-fareast-font-family:
"MS =
Mincho";color:black;mso-color-alt:windowtext'><o:p></o:p></span></font><=
/p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;mso-fareast-font-family:"MS =
Mincho";color:black'>-Monika
</span><span class=3DEmailStyle15><font color=3Dblack><span =
style=3D'mso-ansi-font-size:
12.0pt;mso-ascii-font-family:"Times New =
Roman";mso-hansi-font-family:"Times New Roman";
mso-bidi-font-family:"Times New =
Roman"'><o:p></o:p></span></font></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C2686D.91E36CC0--


From owner-mpls@UU.NET  Mon Sep 30 06:45:14 2002
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 ESMTP id GAA28057
	for <mpls-archive@lists.ietf.org>; Mon, 30 Sep 2002 06:45:14 -0400 (EDT)
Received: from cmr1.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQninr04269
	for <mpls-archive@lists.ietf.org>; Mon, 30 Sep 2002 10:47:01 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQninr02784;
	Mon, 30 Sep 2002 10:46:23 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQninr14612
	for mpls-outgoing; Mon, 30 Sep 2002 10:45:57 GMT
Received: from imr1.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr1.ash.ops.us.uu.net [153.39.43.46])
	id QQninr14607
	for <mpls@mail-control.ash.ops.us.uu.net>; Mon, 30 Sep 2002 10:45:50 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 QQninr16588
	for <mpls@UU.NET>; Mon, 30 Sep 2002 10:45:46 GMT
From: daipayan_kar-choudhuri@agilent.com
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQninr28807
	for <mpls@UU.NET>; Mon, 30 Sep 2002 10:45:46 GMT
Received: from msgbas2.sgp.agilent.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: msgbas2x.net.asiapac.agilent.com [192.25.46.26])
	id QQninr28768
	for <mpls@UU.NET>; Mon, 30 Sep 2002 10:45:44 GMT
Received: from msgrel1.sgp.agilent.com (msgrel1.sgp.agilent.com [141.183.101.233])
	by msgbas2.sgp.agilent.com (Postfix) with ESMTP
	id 278B02C9; Mon, 30 Sep 2002 18:45:02 +0800 (SGP)
Received: from apbrg1.sgp.agilent.com (apbrg1.sgp.agilent.com [141.183.6.40])
	by msgrel1.sgp.agilent.com (Postfix) with SMTP
	id BBB7F44B; Mon, 30 Sep 2002 18:44:57 +0800 (SGP)
Received: from 141.183.6.40 by apbrg1.sgp.agilent.com (InterScan E-Mail VirusWall NT); Mon, 30 Sep 2002 18:45:01 +0800
Received: by apbrg1.sgp.agilent.com with Internet Mail Service (5.5.2653.19)
	id <SSR8CQ8S>; Mon, 30 Sep 2002 18:45:01 +0800
Message-ID: <89D04169635E024E8FD2174A852D788B82D3AD@apmail16.ind.agilent.com>
To: sidde.gowda@intel.com
Cc: mpls@UU.NET
Subject: RE: Martini
Date: Mon, 30 Sep 2002 18:45:21 +0800
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 Gowda,
          According to Martini draft the VC label MUST be distributed using LDP in the
   downstream unsolicited mode .However, the label request operation  MUST  also be implemented.
To simulate this situation you need to send a Label release message to the PE LSR after receiving the DU Label Mapping message. Then you can send the Label request message. The PE LSR will respond with another Label Mapping Message.Since the PE LSR acts in the DU mode you need to send a Label release before sending a Label Request Message. However I am not sure what you meant by 
Label mapping Request.

Regards,
Daipayan

-----Original Message-----
From: Gowda, Sidde [mailto:sidde.gowda@intel.com]
Sent: Monday, September 30, 2002 3:49 PM
To: 'mpls@UU.NET'
Subject: Martini


Hi All

Do Martini drafts talks about label request?
What does that label mapping request means?
If I release the label (or withdraw) then I have to send this message. Am I
really requesting for a label in this situation?

Thanks & Regards,
/*-----------------------------------------------------------------*/
 void siddu.b.gowda {
        char* company="INTEL CORP";
        long   residence phone= 3396926;
        char* email="sidde.gowda@intel.com";
        int     extension=2505;
        ulong wwid=10665328;
     };
/*------------------------------------------------------------------*/


From owner-mpls@UU.NET  Mon Sep 30 07:24:59 2002
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 ESMTP id HAA28707
	for <mpls-archive@lists.ietf.org>; Mon, 30 Sep 2002 07:24:59 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnint22179
	for <mpls-archive@lists.ietf.org>; Mon, 30 Sep 2002 11:26:54 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQnint21593;
	Mon, 30 Sep 2002 11:26:39 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQnint04420
	for mpls-outgoing; Mon, 30 Sep 2002 11:26:20 GMT
Received: from imr3.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47])
	id QQnint04370
	for <mpls@mail-control.ash.ops.us.uu.net>; Mon, 30 Sep 2002 11:26: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 QQnint16265
	for <mpls@UU.NET>; Mon, 30 Sep 2002 11:24:32 GMT
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQnint18951
	for <mpls@UU.NET>; Mon, 30 Sep 2002 11:24:31 GMT
Received: from momus.sc.intel.com by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: momus.sc.intel.com [143.183.152.8])
	id QQnint18880
	for <mpls@UU.NET>; Mon, 30 Sep 2002 11:24:26 GMT
Received: from fmsmsxvs042.fm.intel.com (fmsmsxvs042.fm.intel.com [132.233.42.128])
	by momus.sc.intel.com (8.11.6/8.11.6/d: solo.mc,v 1.46 2002/09/23 20:41:22 dmccart Exp $) with SMTP id g8UBO0E02682
	for <mpls@UU.NET>; Mon, 30 Sep 2002 11:24:10 GMT
Received: from FMSMSX018.fm.intel.com ([132.233.42.197])
 by fmsmsxvs042.fm.intel.com (NAVGW 2.5.2.11) with SMTP id M2002093004245918960
 ; Mon, 30 Sep 2002 04:24:59 -0700
Received: by fmsmsx018.fm.intel.com with Internet Mail Service (5.5.2653.19)
	id <TF5AVJC1>; Mon, 30 Sep 2002 04:23:30 -0700
Message-ID: <12B638FEE763F74696D8544752E72048264680@bgsmsx101.iind.intel.com>
From: "Gowda, Sidde" <sidde.gowda@intel.com>
To: "'daipayan_kar-choudhuri@agilent.com'"
	 <daipayan_kar-choudhuri@agilent.com>,
        "Gowda, Sidde"
	 <sidde.gowda@intel.com>
Cc: mpls@UU.NET
Subject: RE: Martini
Date: Mon, 30 Sep 2002 04:18:59 -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

Thanks for your reply.
ButMartini says in trans-10.txt sec 5.4.2 that imposition router shall send
to disposition router a label mapping request and a label mapping request if
it wants to restart forwarding of packets with initial sequence number. Does
mean that label release and mapping messages?.

Gowda

-----Original Message-----
From: daipayan_kar-choudhuri@agilent.com
[mailto:daipayan_kar-choudhuri@agilent.com]
Sent: Monday, September 30, 2002 4:15 PM
To: sidde.gowda@intel.com
Cc: mpls@UU.NET
Subject: RE: Martini


Hi Gowda,
          According to Martini draft the VC label MUST be distributed using
LDP in the
   downstream unsolicited mode .However, the label request operation  MUST
also be implemented.
To simulate this situation you need to send a Label release message to the
PE LSR after receiving the DU Label Mapping message. Then you can send the
Label request message. The PE LSR will respond with another Label Mapping
Message.Since the PE LSR acts in the DU mode you need to send a Label
release before sending a Label Request Message. However I am not sure what
you meant by 
Label mapping Request.

Regards,
Daipayan

-----Original Message-----
From: Gowda, Sidde [mailto:sidde.gowda@intel.com]
Sent: Monday, September 30, 2002 3:49 PM
To: 'mpls@UU.NET'
Subject: Martini


Hi All

Do Martini drafts talks about label request?
What does that label mapping request means?
If I release the label (or withdraw) then I have to send this message. Am I
really requesting for a label in this situation?

Thanks & Regards,
/*-----------------------------------------------------------------*/
 void siddu.b.gowda {
        char* company="INTEL CORP";
        long   residence phone= 3396926;
        char* email="sidde.gowda@intel.com";
        int     extension=2505;
        ulong wwid=10665328;
     };
/*------------------------------------------------------------------*/


From owner-mpls@UU.NET  Mon Sep 30 08:57:09 2002
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 ESMTP id IAA01810
	for <mpls-archive@lists.ietf.org>; Mon, 30 Sep 2002 08:57:08 -0400 (EDT)
Received: from cmr2.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQninz11838
	for <mpls-archive@lists.ietf.org>; Mon, 30 Sep 2002 12:59:05 GMT
Received: from mail-control.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: mail-control.ash.ops.us.uu.net [153.39.10.50])
	id QQninz07101;
	Mon, 30 Sep 2002 12:57:23 GMT
Received: by mail-control.ash.ops.us.uu.net 
	id QQninz27364
	for mpls-outgoing; Mon, 30 Sep 2002 12:57:00 GMT
Received: from imr2.ash.ops.us.uu.net by mail-control.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: imr2.ash.ops.us.uu.net [153.39.43.15])
	id QQninz27359
	for <mpls@mail-control.ash.ops.us.uu.net>; Mon, 30 Sep 2002 12:56: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 QQninz21591
	for <mpls@UU.NET>; Mon, 30 Sep 2002 12:55:27 GMT
Received: from cmr0.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQninz23266
	for <mpls@UU.NET>; Mon, 30 Sep 2002 12:55:27 GMT
Received: from celox-ma1-ems1.celoxnetworks.com by cmr0.ash.ops.us.uu.net with ESMTP 
	(peer crosschecked as: celox-ma1-imap1.celoxnetworks.com [12.40.60.233])
	id QQninz23217
	for <mpls@UU.NET>; Mon, 30 Sep 2002 12:55:24 GMT
Received: by celox-ma1-ems1.celoxnetworks.com with Internet Mail Service (5.5.2653.19)
	id <RBC12F6F>; Mon, 30 Sep 2002 08:55:22 -0400
Message-ID: <1117F7D44159934FB116E36F4ABF221B0267EB69@celox-ma1-ems1.celoxnetworks.com>
From: "Gray, Eric" <egray@celoxnetworks.com>
To: "'Manchanda, Monika'" <monika.manchanda@intel.com>
Cc: "Mpls (E-mail)" <mpls@UU.NET>
Subject: RE: Regarding Label Mapping Advertisements and Label Mapping Rele
	ase  in maritini-trans-10
Date: Mon, 30 Sep 2002 08:55:17 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C26880.A02AD760"
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_01C26880.A02AD760
Content-Type: text/plain

There is no reason to specify a timer since the implementation

may use one of several approaches to ensure that a reasonable

delay occurs before the label is re-used.  Not all such approaches

are directly timer related.  If an implementation uses a timer, a

reasonable delay can be anything from tens of milliseconds to 

tens of seconds.  The actual time that it takes for all labeled 

packets to clear the LSP depends on the type of LSP, the 

conditions prevailing in the networks along which the LSP exists

and whether or not it is possible for the label release message 

to arrive prior to the last labeled packet from the imposition LSR.

 

Eric W. Gray

Systems Architect

Celox Networks, Inc.

egray@celoxnetworks.com

508 305 7214

 

-----Original Message-----
From: Manchanda, Monika [mailto:monika.manchanda@intel.com] 
Sent: Monday, September 30, 2002 6:39 AM
To: Mpls (E-mail)
Subject: Regarding Label Mapping Advertisements and Label Mapping Release in
maritini-trans-10

 

Hi,

 

 1. The maritini draft section 5.4.1. Label Mapping Advertisements says that


 

"   After a label has been withdrawn by the disposition router and/or
   released by the imposition router, care must be taken to not re-
   advertise (re-use) the released label until the disposition router
   can be reasonably certain that old packets containing the released
   label no longer persist in the MPLS network."

 

According to this the implementation should no re issue the same label for
some time period t, which should ideally be the time till all the packets
containing the released label reach the disposition router. But how do we
determine that what will be the value of t?

 

2. Also the section 5.4.2. Label Mapping Release says that 

 

   "In situations where the imposition router wants to restart forwarding
   of packets with sequence number 1, the router shall 1) Send to
   disposition router a label mapping release, and 2) Send to
   disposition router a label mapping request."

 

Here what do we exactly mean by label mapping release and label mapping
request? 

 

TIA and Regards,

-Monika 


------_=_NextPart_001_01C26880.A02AD760
Content-Type: text/html

<html>

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">


<meta name=Generator content="Microsoft Word 10 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle17
	{font-family:Arial;
	color:black;}
span.EmailStyle20
	{font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>There is no reason to specify a timer
since the implementation</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>may use one of several approaches to
ensure that a reasonable</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>delay occurs before the label is
re-used.&nbsp; Not all such approaches</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>are directly timer related.&nbsp; If an implementation
uses a timer, a</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>reasonable delay can be anything from tens
of milliseconds to </span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>tens of seconds.&nbsp; The actual time
that it takes for all labeled </span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>packets to clear the LSP depends on the
type of LSP, the </span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>conditions prevailing in the networks
along which the LSP exists</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>and whether or not it is possible for the
label release message </span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>to arrive prior to the last labeled packet
from the imposition LSR.</span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<div>

<p class=MsoAutoSig><font size=2 color=navy face="Times New Roman"><span
style='font-size:10.0pt;color:navy'>Eric W. Gray</span></font></p>

<p class=MsoAutoSig><font size=2 color=navy face="Times New Roman"><span
style='font-size:10.0pt;color:navy'>Systems Architect</span></font></p>

<p class=MsoAutoSig><font size=2 color=navy face="Times New Roman"><span
style='font-size:10.0pt;color:navy'>Celox Networks, Inc.</span></font></p>

<p class=MsoAutoSig><font size=2 color=navy face="Times New Roman"><span
style='font-size:10.0pt;color:navy'>egray@celoxnetworks.com</span></font></p>

<p class=MsoAutoSig><font size=2 color=navy face="Times New Roman"><span
style='font-size:10.0pt;color:navy'>508 305 7214</span></font></p>

</div>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;</span></font></p>

<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>

<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma'>-----Original Message-----<br>
<b><span style='font-weight:bold'>From:</span></b> Manchanda, Monika
[mailto:monika.manchanda@intel.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> </span></font><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>Monday,
 September 30, 2002</span></font><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'> </span></font><font
 size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>6:39 AM</span></font><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'><br>
<b><span style='font-weight:bold'>To:</span></b> Mpls (E-mail)<br>
<b><span style='font-weight:bold'>Subject:</span></b> Regarding Label Mapping
Advertisements and Label Mapping Release in maritini-trans-10</span></font></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=MsoNormal><span class=EmailStyle17><font size=3 color=black
face="Times New Roman"><span style='font-size:12.0pt;font-family:"Times New Roman"'>Hi,</span></font></span></p>

<p class=MsoNormal><span class=EmailStyle17><font size=3 color=black
face="Times New Roman"><span style='font-size:12.0pt;font-family:"Times New Roman"'>&nbsp;</span></font></span></p>

<p class=MsoNormal><span class=EmailStyle17><font size=3 color=black
face="Times New Roman"><span style='font-size:12.0pt;font-family:"Times New Roman"'>&nbsp;1.
The maritini draft section </span></font></span><font color=black><span
style='color:black'>5.4.1. Label Mapping Advertisements</span><span
class=EmailStyle17><font color=black face="Times New Roman"><span
style='font-family:"Times New Roman"'> says that</span></font></span></font><span
class=EmailStyle17><font size=2 color=black face=Arial><span style='font-size:
10.0pt'> </span></font></span></p>

<p class=MsoNormal><span class=EmailStyle17><font size=2 color=black
face=Arial><span style='font-size:10.0pt'>&nbsp;</span></font></span></p>

<p class=MsoPlainText style='margin-left:.5in'><span class=EmailStyle17><font
size=2 color=black face=Arial><span style='font-size:10.0pt'>"</span></font></span><font
color=black><span style='color:black'>&nbsp;&nbsp; After a label has been
withdrawn by the disposition router and/or<br>
&nbsp;&nbsp; released by the imposition router, care must be taken to not re-<br>
&nbsp;&nbsp; advertise (re-use) the released label until the disposition router<br>
&nbsp;&nbsp; can be reasonably certain that old packets containing the released<br>
&nbsp;&nbsp; label no longer persist in the MPLS network."</span></font></p>

<p class=MsoPlainText style='margin-left:.5in'><font size=2 face="Courier New"><span
style='font-size:10.0pt'>&nbsp;</span></font></p>

<p class=MsoPlainText style='margin-left:.5in'><font size=3 color=black
face="Times New Roman"><span style='font-size:12.0pt;font-family:"Times New Roman";
color:black'>According to this the implementation should no re issue the same
label for some time period t, which should ideally be the time till all the
packets containing the released label reach the disposition router. But how do
we determine that what will be the value of t?</span></font></p>

<p class=MsoPlainText><font size=3 face="Times New Roman"><span
style='font-size:12.0pt;font-family:"Times New Roman"'>&nbsp;</span></font></p>

<p class=MsoNormal><span class=EmailStyle17><font size=2 color=black
face=Arial><span style='font-size:10.0pt'>2. Also the section </span></font></span><font
color=black><span style='color:black'>5.4.2. Label Mapping Release says that </span></font></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=MsoPlainText style='margin-left:.5in'><font size=2 color=black
face="Courier New"><span style='font-size:10.0pt;color:black'>&nbsp;&nbsp;
"In situations where the imposition router wants to restart forwarding<br>
&nbsp;&nbsp; of packets with sequence number 1, the router shall 1) Send to<br>
&nbsp;&nbsp; disposition router a label mapping release, and 2) Send to<br>
</span></font><font color=black><span style='color:black'>&nbsp;&nbsp;
disposition router a label mapping request."</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=2 face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=3 color=black
face="Times New Roman"><span style='font-size:12.0pt;color:black'>Here what do
we exactly mean by label mapping release and label mapping request? </span></font></p>

<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt;color:black'>TIA and Regards,</span></font></p>

<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt;color:black'>-Monika </span></font></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C26880.A02AD760--


