[mpls-tp] MPLS-TP tunnel and PW establishment over multiple different operators

venkatesan mahalingam <venkatflex@gmail.com> Mon, 28 June 2010 17:43 UTC

Return-Path: <venkatflex@gmail.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1022D3A6825 for <mpls-tp@core3.amsl.com>; Mon, 28 Jun 2010 10:43:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.648
X-Spam-Level:
X-Spam-Status: No, score=-0.648 tagged_above=-999 required=5 tests=[AWL=-0.650, 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 E6S5v1a8iDgy for <mpls-tp@core3.amsl.com>; Mon, 28 Jun 2010 10:43:14 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id 6A1FC3A68FD for <mpls-tp@ietf.org>; Mon, 28 Jun 2010 10:43:14 -0700 (PDT)
Received: by pwi2 with SMTP id 2so131651pwi.31 for <mpls-tp@ietf.org>; Mon, 28 Jun 2010 10:43:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=0ElZshb1BDaccjY/hxptGmGKV5ajmhDGjUTaZ5dIL1U=; b=QhHpisjs/MRM1ojgQY+9FpqTajB+xk19qlo3NapzqBwDTIZmgzL5RmlZMVv2h6IJQo VqHc+0WKnqO8U2aeSYhkKVYKQqTzLUyqwVBdIvI5Zw07J9SAGCdlCiZwzTWlDizy73Wy igvw7t6kECjXLQ7o9W1SJI7zaq5lfhdguZ5qo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=dODrZQoG0ciao+OKOGtvOJfE1W2xwtIifVObcUs2ob4q0vDnAcQU9CVoEItZ82/UhY yn6esusfybieZRX73GHIRlAQ//0qv/ihdyftVuL0+5gzrzQdzItliLAztbFJJlN7Ig+Q +3AlFqKhdZuzLLLXVA7OBYgMLXqIKwhr4Jfgs=
MIME-Version: 1.0
Received: by 10.143.26.19 with SMTP id d19mr6257261wfj.160.1277746998759; Mon, 28 Jun 2010 10:43:18 -0700 (PDT)
Received: by 10.143.167.14 with HTTP; Mon, 28 Jun 2010 10:43:18 -0700 (PDT)
Date: Mon, 28 Jun 2010 23:13:18 +0530
Message-ID: <AANLkTik-HZHcVP8ZZR-kj3bmbHKDsTzlPUdlzvnDepPu@mail.gmail.com>
From: venkatesan mahalingam <venkatflex@gmail.com>
To: mpls-tp@ietf.org
Content-Type: multipart/alternative; boundary=001636e0b142f9cda6048a1aa738
Subject: [mpls-tp] MPLS-TP tunnel and PW establishment over multiple different operators
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jun 2010 17:43:18 -0000

Hi,

Please clarify whether the below operations are valid for MPLS-TP
deployment.

For example,
*Scenario-1:*
Operator1 -------------------Operator2--------------------Operator3
 (ICC - IP capable)    (ICC- IP capable)        (ICC IP incapable)

 Can single LSP/PW be established over ICC based operators in an IP and
Non-IP environments?
 **
*Scenario-2:*
Operator1
-------------------Operator2--------------------Operator3----------------------Operator-4
 (ICC - IP capable)    (ICC- IP capable)        (ICC IP
incapable)               (ICC IP incapable)

Can single LSP/PW be established between Operator1 and Opearator-4?
If the answer is NO, do we need to maintain two LSPs/PWs, one between
Operator1 and Operator2 and
another one between Operator3 and Operator4 and LSP/PW stitching with these
two LSPs/PWs?

 *Scenario-3:*
Operator1
---------------------------Operator2--------------------------------Operator3
(Global_ID - IP capable)    (Global_ID - IP capable)        (Global_ID IP
incapable)

 Can single LSP/PW be established over Global_ID based operators in an IP
and Non-IP environments?
 **
*Scenario-4:*
Operator1
-----------------------------Operator2------------------------Operator3------------------------------Operator-4
 (Global_ID - IP capable)    (Global_ID- IP capable)        (Global_ID IP
incapable)       (Global_ID IP incapable)

Can single LSP/PW be established between Operator1 and Opearator-4?
If the answer is NO, do we need to maintain two LSPs/PWs, one between
Operator1 and Operator2 and
another one between Operator3 and Operator4 and LSP/PW stitching with these
two LSPs/PWs?

*Scenario-5:*
 Operator1
--------------------------------Operator2--------------------Operator3
 (Global_ID- IP capable)         (ICC- IP capable)        (Global_ID IP
capable)

 Can single LSP/PW be established over different operators in an IP
environments?
 **
 *Scenario-6:*
 Operator1
-----------------------------Operator2--------------------Operator3
 (ICC- IP incapable)         (Global- IP incapable)        (ICC IP
incapable)

 Can single LSP/PW be established over different operators in an Non-IP
environments?

*Scenario-7:*
Operator1
-------------------Operator2--------------------Operator3---------------------------Operator-4
 (ICC - IP capable)    (ICC- IP capable)        (Global_ID IP
capable)            (Global_ID IP capable)

Can single LSP/PW be established between Operator1 and Opearator-4?
If the answer is NO, do we need to maintain two LSPs/PWs, one between
Operator1 and Operator2 and
another one between Operator3 and Operator4 and LSP/PW stitching with these
two LSPs/PWs?

 *Scenario-8:*
Operator1
-------------------Operator2--------------------Operator3---------------------------Operator-4
 (ICC - IP capable)    (ICC- IP capable)        (Global_ID IP
incapable)          (Global_ID IP incapable)

Can single LSP/PW be established between Operator1 and Opearator-4?
If the answer is NO, do we need to maintain two LSPs/PWs, one between
Operator1 and Operator2 and
another one between Operator3 and Operator4 and LSP/PW stitching with these
two LSPs/PWs?

 *Scenario-9:*
Operator1
-------------------Operator2-----------------------------Operator3---------------------------Operator-4
 (ICC - IP capable)    (Global_ID- IP capable)        (ICC IP
incapable)          (Global_ID IP incapable)

Can single LSP/PW be established between Operator1 and Opearator-4?
If the answer is NO, do we need to maintain two LSPs/PWs, one between
Operator1 and Operator2 and
another one between Operator3 and Operator4 and LSP/PW stitching with these
two LSPs/PWs?

 *Scenario-9:*
Operator1
-------------------------Operator2------------------------Operator3---------------------------Operator-4
 (ICC - IP capable)    (Global_ID- IP incapable)        (Global_ID IP
capable)          (ICC IP incapable)

Can single LSP/PW be established between Operator1 and Opearator-4?
Is this a valid scenario?

-- 
Best Regards,
Venkatesan Mahalingam.