Re: [mpls] PSC: draft-dj-mpls-tp-exer-psc

Yuji Tochio <tochio@jp.fujitsu.com> Mon, 29 April 2013 23:52 UTC

Return-Path: <tochio@jp.fujitsu.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8966C21F9AFF for <mpls@ietfa.amsl.com>; Mon, 29 Apr 2013 16:52:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.09
X-Spam-Level:
X-Spam-Status: No, score=-104.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 gqaSFvJfcttD for <mpls@ietfa.amsl.com>; Mon, 29 Apr 2013 16:52:02 -0700 (PDT)
Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by ietfa.amsl.com (Postfix) with ESMTP id 3D0C521F9B01 for <mpls@ietf.org>; Mon, 29 Apr 2013 16:52:02 -0700 (PDT)
Received: from m2.gw.fujitsu.co.jp (unknown [10.0.50.72]) by fgwmail6.fujitsu.co.jp (Postfix) with ESMTP id 4EFAB3EE0BB for <mpls@ietf.org>; Tue, 30 Apr 2013 08:52:01 +0900 (JST)
Received: from smail (m2 [127.0.0.1]) by outgoing.m2.gw.fujitsu.co.jp (Postfix) with ESMTP id 418F145DE4E for <mpls@ietf.org>; Tue, 30 Apr 2013 08:52:01 +0900 (JST)
Received: from s2.gw.fujitsu.co.jp (s2.gw.fujitsu.co.jp [10.0.50.92]) by m2.gw.fujitsu.co.jp (Postfix) with ESMTP id 2774645DD6C for <mpls@ietf.org>; Tue, 30 Apr 2013 08:52:01 +0900 (JST)
Received: from s2.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s2.gw.fujitsu.co.jp (Postfix) with ESMTP id 1BB6E1DB803A for <mpls@ietf.org>; Tue, 30 Apr 2013 08:52:01 +0900 (JST)
Received: from flabmail.flab.fujitsu.co.jp (flabmail.flab.fujitsu.co.jp [10.25.192.37]) by s2.gw.fujitsu.co.jp (Postfix) with ESMTP id C11A01DB802C for <mpls@ietf.org>; Tue, 30 Apr 2013 08:52:00 +0900 (JST)
Received: from vskawa.flab.fujitsu.co.jp (vskawa.flab.fujitsu.co.jp [10.25.192.39]) by flabmail.flab.fujitsu.co.jp (8.14.4/8.14.4/110310-Fujitsu Labs. Domain Mail Master) with ESMTP id r3TNq0Bn018049 for <mpls@ietf.org>; Tue, 30 Apr 2013 08:52:00 +0900 (JST)
X-AuditID: 0a19c027-b7f866d00000132d-31-517f07a0ccc9
Received: from dm.kawasaki.flab.fujitsu.co.jp (dm.kawasaki.flab.fujitsu.co.jp [10.25.192.105]) by vskawa.flab.fujitsu.co.jp (Symantec Messaging Gateway) with SMTP id AE.60.04909.0A70F715; Tue, 30 Apr 2013 08:52:00 +0900 (JST)
Received: from [127.0.0.1] (dhcp20.dream.flab.fujitsu.co.jp [10.25.144.235]) by dm.kawasaki.flab.fujitsu.co.jp (8.14.4/8.14.4/110311-Fujitsu Labs. Kawasaki Domain Mail Master) with ESMTP id r3TNptNk028373 for <mpls@ietf.org>; Tue, 30 Apr 2013 08:52:00 +0900 (JST)
X-SecurityPolicyCheck: OK by SHieldMailChecker v1.8.4
Message-ID: <517F078E.5030002@jp.fujitsu.com>
Date: Tue, 30 Apr 2013 08:51:42 +0900
From: Yuji Tochio <tochio@jp.fujitsu.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: mpls@ietf.org
References: <20ECF67871905846A80F77F8F4A27572101502A9@xmb-rcd-x09.cisco.com>
In-Reply-To: <20ECF67871905846A80F77F8F4A27572101502A9@xmb-rcd-x09.cisco.com>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprALMWRmVeSWpSXmKPExsXCJXkgU3cBe32gwf8DGha3lq5kdWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxsMtPxgLGrgqPvbPZG9g/MPexcjJISFgInH3yi82CFtM4sK9 9UA2F4eQwGNGif6vsxkhnG4miYZLjVAdphIT1z1jBLF5BXQlFj89DBTn4GARUJWYdo0JJMwm oClxbeYdsBJRgWCJnx1TocoFJU7OfMICYosA2dOuHgWzhQWMgOyNYL1CAj4SE7YsYwWxOQV8 JfofPwazmYFW3TzxkQnClpfY/nYO8wRGgVlIxs5CUjYLSdkCRuZVjJJlxdmJ5Yl6aTmJSXpp pVmZJcWlesn5elkFmxghoai+g/HZIs1DjAIcjEo8vF/+1QUKsSaWFVfmHmKU4GBWEuE9fRMo xJuSWFmVWpQfX1Sak1p8iJGJg1OqgbG4Sd/K/qqnNu9UqSVXSwzSd2+1z1d7J7v1dzfbQ//C iX+/HWSduvXWrKlzz/W3TJqWuKAl207ib1Lmzf6/1+8I1FWssNzaefzU4mlLZ/y+sbvzGBdz pxdz74Jt7DfKzB19Lz7VlHjMXXB8Z5hRwC9msd2M7z8s+5n4cmLQ57/x33cae9dw6XQqsRRn JBpqMRcVJwIAYXAuaiMCAAA=
Subject: Re: [mpls] PSC: draft-dj-mpls-tp-exer-psc
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 29 Apr 2013 23:52:06 -0000

Hi Eric O and all,

As to the first bullet to the question below, my opinion is YES.
The reason is it is align with #84 (84A) in RFC 5654.

Just my 2c,
Yuji

(2013/04/17 21:21), Eric Osborne (eosborne) wrote:
> This thread is for discussing draft-dj-mpls-tp-exer-psc.  We started with -00, but there is now a -01.  
>
> The draft proposes adding the EXER/RR commands found in some ITU linear protection protocols to PSC.  
> I have also posted an alternative approach, draft-osborne-mpls-psc-alive-00.
> Briefly, EXER is a mechanism designed to check the responsiveness of the far-end state machine.  My proposal, ALIVE, is for a similar mechanism.  It works differently and thus may be more or less acceptable.
>
> The big questions here are:
>
> - do we need any sort of EXER-type function at all?
> - if so, are either of the two proposals sufficient?  Is there a better way?
> - if not, is it possible to provide the same kind of testing and awareness through existing mechanisms?  is this testing and awareness desirable or necessary?
>
> but of course any and all discussion is welcome.
>
>
>
>
>
> eric
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>