RE: [mpls] moving discussion to the mpls working group list
benjamin.niven-jenkins@bt.com Wed, 18 May 2005 10:42 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DYM05-0007G3-CP; Wed, 18 May 2005 06:42:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DYM03-0007Fy-FV for mpls@megatron.ietf.org; Wed, 18 May 2005 06:42:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03074 for <mpls@ietf.org>; Wed, 18 May 2005 06:42:00 -0400 (EDT)
From: benjamin.niven-jenkins@bt.com
Received: from smtp2.smtp.bt.com ([217.32.164.150]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DYMGy-0004a2-96 for mpls@ietf.org; Wed, 18 May 2005 06:59:33 -0400
Received: from i2km99-ukbr.domain1.systemhost.net ([193.113.197.31]) by smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 18 May 2005 11:41:52 +0100
Received: from i2km86-ukdy.domain1.systemhost.net ([193.113.30.79]) by i2km99-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(5.0.2195.6713); Wed, 18 May 2005 11:41:51 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mpls] moving discussion to the mpls working group list
Date: Wed, 18 May 2005 11:42:03 +0100
Message-ID: <F5AAFD21F2034349BF638211B5F27B0F01B37F06@i2km86-ukdy.domain1.systemhost.net>
Thread-Topic: [mpls] moving discussion to the mpls working group list
Thread-Index: AcVbjz5Wa4lTlVuDSuOeTCAgE+MDTQABXy+A
To: mpls@ietf.org
X-OriginalArrivalTime: 18 May 2005 10:41:51.0940 (UTC) FILETIME=[33A1F040:01C55B96]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Content-Transfer-Encoding: quoted-printable
Cc:
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@lists.ietf.org
Errors-To: mpls-bounces@lists.ietf.org
Loa, Colleagues, I have not been following the rtgwg and I can not find any drafts on LDP next-next-hop so apologies if my questions have already been addressed. My understanding is that the path LDP uses for a flow 'tracks' the IGP and an LDP flow will take the same path through the network as an IP flow to the same destination/FEC (assuming ECMP is not running). Therefore is there really a need for LDP FRR as well as IP FRR, when LDP tracks the IGP anyway? (Or am I getting ahead of myself and the proposal is to modify LDP to make it so that it can still track the IGP when IP FRR is used?) Ben > -----Original Message----- > From: mpls-bounces@lists.ietf.org > [mailto:mpls-bounces@lists.ietf.org] On Behalf Of Loa Andersson > Sent: Wednesday, May 18, 2005 10:47 AM > To: mpls@ietf.org > Subject: [mpls] moving discussion to the mpls working group list > > > MPLS working group, > > there has been a discussion on the rtgwg mailing list on > possible extension to LDP for finding out the next-next-hop > label mapping. Possible applications for this functionality > world be fast reroute. Since the extensions to the LDP should > be handled by the MPLS working group, this mail is to > indicate that the discussion will be contiuned on the MPLS > working group list. > > The non-MPLS part of this discussion will remain on the rtgwg > mailing list. > > This is the content of the last mail on the rtgwg thread > called "Re: the shen-mpls-nnhop Was:(Re: thoughts on > draft-bryant-shand-ipfrr-notvia-addresses-00.txt)" > > /Loa > > > Naiming and Stewart, > > you wrote - and I guess this is valid: > > Naiming Shen wrote: > > > I think the needs start emerging, any important services > > riding on top of IP/MPLS transport infrastructure needs > > fast convergence services. It's not reasonable to assume > > only RSVP-TE LSPs need fast reroute, and other > > network transport does not. This nnhop-ldp draft is to > > facilitate the LDP based MPLS network for FRR with > > node protection. I have been talking to some providers > > in the past year, there are certainly interests in > > this service. > > > > Stewart Bryant wrote: > > > > I think the interest that we are seeing in IPFRR for LDP > > networks demonstrates the usefulness of this work. Sure > > RSVP-TE FRR exists, but some customers have expressed > > an interest in a solution that does not use RSVP. > > > > However the MPLS working group need to take a decision if, > when and how this functionality should be developed. > > > The way of doing this would be > > - write down the requirements > - send them to the mpls wg > - we go through the moces to establish the mpls wg consensus > > Comments: > > - I don't think FRR for LDP based MPLS enabled IP networks > should not go into the rtgwg, the charter of the rtgwg seems > to say the rtgwg takes of everything that does not fit into > other routing are working groups (Alex and Bill comments on this?) > > - my take is that for this purpose you could either document > the requirements in a separate document or put them into one > the existing documents. I've no preferences, but this should > be rather short. > > - my preference would be to speed this up so we could have > a decision going into the Paris meeting. > > Also I think it will be right to take this discussion to the > mpls wg list. I will write a mail to mpls list to that effect. > > > /Loa > > > -- > Loa Andersson > > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls
- [mpls] moving discussion to the mpls working grou… Loa Andersson
- RE: [mpls] moving discussion to the mpls working … benjamin.niven-jenkins
- RE: [mpls] moving discussion to the mpls working … Alia Atlas