Re: [mpls] [mpls-tp] mpls wg last call on draft-ietf-mpls-tp-identifiers-01
venkatesan mahalingam <venkatflex@gmail.com> Thu, 06 May 2010 18:09 UTC
Return-Path: <venkatflex@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 473743A6A3F; Thu, 6 May 2010 11:09:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.957
X-Spam-Level:
X-Spam-Status: No, score=-0.957 tagged_above=-999 required=5 tests=[AWL=-0.959, BAYES_50=0.001, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h1njgqsjdkxu; Thu, 6 May 2010 11:09:13 -0700 (PDT)
Received: from mail-pz0-f182.google.com (mail-pz0-f182.google.com [209.85.222.182]) by core3.amsl.com (Postfix) with ESMTP id 874FF3A6ADA; Thu, 6 May 2010 11:09:13 -0700 (PDT)
Received: by pzk12 with SMTP id 12so117836pzk.32 for <multiple recipients>; Thu, 06 May 2010 11:08:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=2GsxG2a0EKGYvmX6znKYh7F0aq17ABjx3Bhn/vgt9C4=; b=a3vJd83RyKwjMTiEIO9hmrWHISBuJIez4v58bP6g/j7PxWyZK7SzAOEnCSuMut9deR MbH149L6sZw9ORQMSL04WOdGN/JKd+HpecgCZ1N/KEO5jEGBerW6S8ViNMUju9XSJjZ8 rFfuramJrDkX3Ycf4drkTSR52th/6zrhT9AUc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=se23jKXWi1hvoE2UHn5whxosoZIPYPVkKu2WE//T/qKFgtXkzZkLvBZUaxIS/+Dqv7 4rMNoCfbYBVAQjw0hiN2o9c7SZCOWbFT4wZWUosGIliwm/hIbHtuVV+IV9qcbofOmjYZ TA1lP0skqfzz/LDkrsKcsf3kJ8RlVFG9/mfJ4=
MIME-Version: 1.0
Received: by 10.142.66.11 with SMTP id o11mr2527044wfa.121.1273169337886; Thu, 06 May 2010 11:08:57 -0700 (PDT)
Received: by 10.142.53.16 with HTTP; Thu, 6 May 2010 11:08:57 -0700 (PDT)
In-Reply-To: <C7EE0C65.241B2%swallow@cisco.com>
References: <79F41BA1E9BF3C489375521EF8DDE23C12B1B1A5BB@ESESSCMS0355.eemea.ericsson.se> <C7EE0C65.241B2%swallow@cisco.com>
Date: Thu, 06 May 2010 23:38:57 +0530
Message-ID: <q2k715756491005061108r650202bfm6c36bc6d31a4b7cb@mail.gmail.com>
From: venkatesan mahalingam <venkatflex@gmail.com>
To: George Swallow <swallow@cisco.com>
Content-Type: multipart/alternative; boundary="001636e0b9b81fabd70485f0d61f"
Cc: "mpls@ietf.org" <mpls@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, Attila Takacs <Attila.Takacs@ericsson.com>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [mpls] [mpls-tp] mpls wg last call on draft-ietf-mpls-tp-identifiers-01
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 May 2010 18:09:15 -0000
Hi George, >> Is it there to support associated unidirectional Tunnels/LSPs? If so it should >> be called out in the text. >That was not my original intent, but you are quite correct that this would >be very useful. Particularly if the associated tunnels pass through a share >mid-point somewhere along the path. VM: Can you please explain the original intention with an example? >> -In Section 5.3 Mapping to GMPLS signaling does not use the Dst-Tunnel_Num. So >> this means that we may have two different tunnels identified with >> Src-Node_ID::Src-Tunnel_Num:: Dst-Node_ID::Dst-Tunnel_Num. Is this intentional, >> e.g., the associated unidirectional case? >For the associated unidirectional, this works perfectly. For bidirectional, >I was thinking of two options. >1) Strict binding - both ends are configure with the full identifier and >will only accept the connection if everything matches. >2) Dynamic binding - Source signals with just its Tunnel_Num. RESV message >would carry back the destination's tunnel_num. Note that both ends need >both pieces for some of the OAM to work. VM: Do we need extensions in the RSVP-TE signaling to carry back the destination's tunnel_num in the RESV message? Thanks, Venkatesan Mahalingam On Fri, Apr 16, 2010 at 10:15 PM, George Swallow <swallow@cisco.com> wrote: > > > > On 4/2/10 2:53 AM, "Attila Takacs" <Attila.Takacs@ericsson.com> wrote: > > > Hi Matthew and George, > > > > Please find some comments/questions below. > > > > -In Section 5.1 you have: > > > > Src-Node_ID::Src-Tunnel_Num::Dst-Node_ID::Dst-Tunnel_Num > > > > What is the reason of having a Dst-Tunnel_Num besides the Src-Tunnel_Num? > > Existing implementations of RSVP-TE have used the tunnel space as global to > the node. It is difficult if not impossible to coordinate such spaces > between nodes. In RSVP-TE the coordination does not matter, since the tail > end of the tunnel doesn't have a real interface - it only receives and > usually with a PHP of the tunnel label, so the packets only belong to the > physical interface. > > In a bidirectional world, separate tunnel spaces at the two ends becomes > useful. > > If this independence is not need is some environments then one can > configure > just one value and use it in both fields. > > > Is it there to support associated unidirectional Tunnels/LSPs? If so it > should > > be called out in the text. > > That was not my original intent, but you are quite correct that this would > be very useful. Particularly if the associated tunnels pass through a > share > mid-point somewhere along the path. > > > Same applies to the globally unique case. > > Of course. > > > -In Section 5.2 you simply append one LSP_Num to the above. This is a bit > > confusing to me, if there are Src/Dst Tunnel_Nums then two LSP_Nums would > be > > needed too, wouldn't it? > > Once, you have independent tunnel-ids, coordination of the LSP numbers > becomes easy. It also could be used to allow the two ends to readily > identify which is working and which is protection. > > > -In Section 5.3 Mapping to GMPLS signaling does not use the > Dst-Tunnel_Num. So > > this means that we may have two different tunnels identified with > > Src-Node_ID::Src-Tunnel_Num::Dst-Node_ID::Dst-Tunnel_Num. Is this > intentional, > > e.g., the associated unidirectional case? > > For the associated unidirectional, this works perfectly. For > bidirectional, > I was thinking of two options. > > 1) Strict binding - both ends are configure with the full identifier and > will only accept the connection if everything matches. > > 2) Dynamic binding - Source signals with just its Tunnel_Num. RESV > message > would carry back the destination's tunnel_num. Note that both ends need > both pieces for some of the OAM to work. > > > This should be clarified. > > I'll see what I can do. But this is not supposed to the MPLS-TP signaling > draft. > > > Hmm, maybe the Dst-Tunnel_Num should be omitted altogether. > > I'm planning to keep it. > > > -Section 7 has a note saying to be aligned with the OAM fwk, is this > still to > > be done? > > Yes. That draft is also being updated. We appear to be converging. > > > -In section 7.1.2.1 there is a discussion on Tunnel MEG IDs. > > How would Tunnel and LSP MEGs be used? What OAM would run at the Tunnel > level > > and not at the LSP level? > > > > Do we need Tunnel MEG_IDs as defined in 7.1.2.1? > > I had been told early on that MEGs were needed for tunnels. Now getting > comments that they are not (same comment is in the ITU liaison). So I > planning to remove it, unless I hear other opinions. > > > -Section 7.1.2.2, the Dst-Tunnel_Num question applies here too. > > See above. > > > -Section 8 talks about open issues? When will these be addressed? > > Before it is re-issued. Goal is end of next week. > > ...George > > > Thanks, > > Attila > > > >> -----Original Message----- > >> From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On > >> Behalf Of Loa Andersson > >> Sent: Friday, March 12, 2010 12:33 AM > >> To: mpls@ietf.org; mpls-tp@ietf.org; pwe3@ietf.org; ccamp@ietf.org > >> Subject: [mpls] mpls wg last call on draft-ietf-mpls-tp-identifiers-01 > >> > >> All, > >> > >> this is to start an MPLS working group last call on > >> draft-ietf-mpls-tp-identifiers-01 > >> > >> There is a discussion on the OAM model for MS-PWs where we > >> haven't been able to come to conclusion. Once we reach > >> agreement the document will be updated. Comments in this area > >> are welcome during the working group last call. > >> > >> > >> Please send your comments to the mpls-tp@ietf.org mailing list. > >> > >> The working group last ends eob April 2nd. > >> > >> /Loa > >> > >> -- > >> > >> Loa Andersson > >> > >> Sr Strategy and Standards Manager > >> Ericsson /// > >> phone: +46 10 717 52 13 > >> +46 767 72 92 13 > >> > >> email: loa.andersson@ericsson.com > >> loa@pi.nu > >> > >> > >> > >> > >> _______________________________________________ > >> mpls mailing list > >> mpls@ietf.org > >> https://www.ietf.org/mailman/listinfo/mpls > >> > > _______________________________________________ > > mpls-tp mailing list > > mpls-tp@ietf.org > > https://www.ietf.org/mailman/listinfo/mpls-tp > > _______________________________________________ > mpls mailing list > mpls@ietf.org > https://www.ietf.org/mailman/listinfo/mpls > -- Best Regards, Venkatesan Mahalingam.
- [mpls] mpls wg last call on draft-ietf-mpls-tp-id… Loa Andersson
- Re: [mpls] mpls wg last call on draft-ietf-mpls-t… Shahram Davari
- Re: [mpls] mpls wg last call on draft-ietf-mpls-t… Shahram Davari
- Re: [mpls] mpls wg last call on draft-ietf-mpls-t… Alexander Vainshtein
- Re: [mpls] mpls wg last call on draft-ietf-mpls-t… Sriganesh Kini
- Re: [mpls] mpls wg last call on draft-ietf-mpls-t… Attila Takacs
- Re: [mpls] mpls wg last call on draft-ietf-mpls-t… Diego Caviglia
- Re: [mpls] [mpls-tp] mpls wg last call on draft-i… George Swallow
- Re: [mpls] [mpls-tp] mpls wg last call on draft-i… Maarten Vissers
- Re: [mpls] [mpls-tp] mpls wg last call on draft-i… neil.2.harrison
- Re: [mpls] [mpls-tp] mpls wg last call on draft-i… Maarten Vissers
- Re: [mpls] [mpls-tp] mpls wg last call on draft-i… neil.2.harrison
- Re: [mpls] mpls wg last call on draft-ietf-mpls-t… Shahram Davari
- Re: [mpls] [mpls-tp] mpls wg last call on draft-i… George Swallow
- Re: [mpls] [mpls-tp] mpls wg last call on draft-i… George Swallow
- Re: [mpls] mpls wg last call on draft-ietf-mpls-t… George Swallow
- Re: [mpls] [mpls-tp] mpls wg last call on draft-i… venkatesan mahalingam
- Re: [mpls] [CCAMP] [mpls-tp] mpls wg last call on… Lou Berger
- Re: [mpls] [mpls-tp] mpls wg last call on draft-i… venkatesan mahalingam
- Re: [mpls] [PWE3] [mpls-tp] mpls wg last call ond… George Swallow
- Re: [mpls] [PWE3] [mpls-tp] mpls wg last call ond… venkatesan mahalingam