[PWE3] Comments on draft-jc-pwe3-mpls-tp-static-checking-00.txt
Sriganesh Kini <sriganesh.kini@ericsson.com> Wed, 28 March 2012 14:30 UTC
Return-Path: <sriganeshkini@gmail.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEB8021E8097 for <pwe3@ietfa.amsl.com>; Wed, 28 Mar 2012 07:30:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2uv5x71KL6CY for <pwe3@ietfa.amsl.com>; Wed, 28 Mar 2012 07:30:21 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0ABF621F88BB for <pwe3@ietf.org>; Wed, 28 Mar 2012 07:30:20 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so849581vbb.31 for <pwe3@ietf.org>; Wed, 28 Mar 2012 07:30:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=DB66Hfn3cl1xqP07w/da4XKGBCQlq8s0UFTKK66MVE0=; b=Yu1Dn6znIK9flERVbt/uwADrukFO1nYef4TJHXPvoEBlWc6zpCicwcIWbQgCOHZYXW 4wnhkbZ5OWb56CEUAQcQO83MmYYIhEzFCK0hpw8h3w2twBUB+ax0BjmLN6oej2el7tif bJa8vglQAIHkk3v6MEbDEr8m4jpTL/yLVOzUl18yxgkd9MZqrRMQJ/4HVW/dCOXnqySw aWy9H8zsSAq+8wLpX7A/WU+Ayc2qUUfJTsb+iLf8N/VC4qqLA6XP4c89si4U6KayMtKn Zx/aMEEgEk3bXk+3GGbCpDacBg+MmbmkJy9jXoKY8fFLGHrq7ycBd2epTUB9DCmWe5/L mjRw==
MIME-Version: 1.0
Received: by 10.220.152.205 with SMTP id h13mr9908744vcw.12.1332945020333; Wed, 28 Mar 2012 07:30:20 -0700 (PDT)
Sender: sriganeshkini@gmail.com
Received: by 10.220.200.193 with HTTP; Wed, 28 Mar 2012 07:30:19 -0700 (PDT)
Date: Wed, 28 Mar 2012 07:30:19 -0700
X-Google-Sender-Auth: aM8NBen0PkY40pd3tn_y5i1w-gg
Message-ID: <CAOndX-uWUpdr9Pc53QvGjfunSchSMLNJsS8OOyuxghgwX8GfKQ@mail.gmail.com>
From: Sriganesh Kini <sriganesh.kini@ericsson.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Content-Type: multipart/alternative; boundary="f46d043c7d0e712dcc04bc4e7243"
Subject: [PWE3] Comments on draft-jc-pwe3-mpls-tp-static-checking-00.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Mar 2012 14:30:22 -0000
Comments 1. My first thought on looking at this - what is the relationship of this to a signaling protocol (LDP) ? Is this trying to replicate that functionality or provide som new functionality ? 2. Is this checking intended to be used as operator initiated or proactive checking ? 3. The term "corresponding PSN tunnel" has been used. I guess this means the PSN tunnel to which the PW is nailed to (?) However there is no receive check to ensure that the received msg is indeed on a tunnel that is carrying the PW. Even if there was, what is the need to map this to the 'corresponding' PSN tunnel ? 4. If just the in-label is sent can this be used as a label advertisement mechanism ? -- - Sri
- [PWE3] Comments on draft-jc-pwe3-mpls-tp-static-c… Sriganesh Kini
- Re: [PWE3] Comments on draft-jc-pwe3-mpls-tp-stat… Lizhong Jin