Re: [Teas] Comparison Analysis (TEAS WG Virtual Interim Meeting (before IETF-95))

Gregory Mirsky <gregory.mirsky@ericsson.com> Mon, 25 January 2016 19:20 UTC

Return-Path: <gregory.mirsky@ericsson.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D55F1B3969; Mon, 25 Jan 2016 11:20:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.199
X-Spam-Level:
X-Spam-Status: No, score=-104.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5WUHpM9JMH46; Mon, 25 Jan 2016 11:20:07 -0800 (PST)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F8BB1B3967; Mon, 25 Jan 2016 11:20:07 -0800 (PST)
X-AuditID: c6180641-f799c6d000007d66-55-56a675546f08
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usplmg21.ericsson.net (Symantec Mail Security) with SMTP id 20.AA.32102.45576A65; Mon, 25 Jan 2016 20:19:48 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.03.0248.002; Mon, 25 Jan 2016 14:19:51 -0500
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: Vishnu Pavan Beeram <vishnupavan@gmail.com>, Huaimo Chen <huaimo.chen@huawei.com>
Thread-Topic: [Teas] Comparison Analysis (TEAS WG Virtual Interim Meeting (before IETF-95))
Thread-Index: AQHRVvoS/uTFWzfpNUWRMIfAGUbQ5p8MmxKw
Date: Mon, 25 Jan 2016 19:19:50 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF11221993D66@eusaamb103.ericsson.se>
References: <CA+YzgTtWFWX08ae=1yT29Sx8K040Cv9vAk5+pfA0Rhujf+LNHA@mail.gmail.com> <5316A0AB3C851246A7CA5758973207D44E4D14CE@SJCEML701-CHM.china.huawei.com> <CA+YzgTsk-xR7XMhPfJNULgs2L-=wcb++iQWnJLZyhrPdB+=aNQ@mail.gmail.com>
In-Reply-To: <CA+YzgTsk-xR7XMhPfJNULgs2L-=wcb++iQWnJLZyhrPdB+=aNQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.10]
Content-Type: multipart/alternative; boundary="_000_7347100B5761DC41A166AC17F22DF11221993D66eusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrHIsWRmVeSWpSXmKPExsUyuXRPrG5I6bIwg5OPDSy2Pr3CaDHnJbNF 09xdTBatP3awWMxpe8LswOox5fdGVo+ds+6ye7QcecvqsWTJT6YAligum5TUnMyy1CJ9uwSu jGVPVrEVNHxlrFh84QFLA+OJd4xdjJwcEgImEos7+9ggbDGJC/fWA9lcHEICRxgl5j3pZYVw ljNK3Ft0jRWkik3ASOLFxh52EFtEIFzixYmfTCA2s0C5xIRDz8FqhAViJE58Xs8EURMrMXP/ ZGYI20iiY8N/sM0sAqoSq5svg83hFfCVOLZgFtSyx4wSq242gw3iFAiUeDB1DlgRI9B530+t gVomLnHryXwmiLMFJJbsOc8MYYtKvHz8jxXCVpKYtPQcK0R9vkTf+n+MEMsEJU7OfMIygVF0 FpJRs5CUzUJSNouRAyiuKbF+lz5EiaLElO6H7BC2hkTrnLnsyOILGNlXMXKUFhfk5KYbGW5i BMbiMQk2xx2Me3s9DzEKcDAq8fBuKFgWJsSaWFZcmXuIUYKDWUmE9z8fUIg3JbGyKrUoP76o NCe1+BCjNAeLkjjvFv5FYUIC6YklqdmpqQWpRTBZJg5OqQZGe7Go6HPbGY6a7ow8rTkxu2Ld K1btHl5uKf2O3x65zWcqdl7s3mby+LV68pn3P2+6C5cu2GsWdmDjwQMBR8OTPqgscL1UWrOQ bwKDsjPjpsU8MwRuLLNaZvZqg9CTDx/8vacmhN15/XV31sw1alIunzSO60/Ilj660kD72qUZ n77MdnmQopobo8RSnJFoqMVcVJwIAJDPbzDBAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/teas/FKrvL6wZJV_iYXj3cD4c8Mx3NII>
Cc: Matt Hartley <mhartley@cisco.com>, "teas-chairs@ietf.org" <teas-chairs@ietf.org>, "teas@ietf.org" <teas@ietf.org>
Subject: Re: [Teas] Comparison Analysis (TEAS WG Virtual Interim Meeting (before IETF-95))
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2016 19:20:10 -0000

Dear Pavan, Huiamo, et. al,
I’d like to draw your attention to the fact that both methods rely on the Backup Ingress detecting when the Primary Ingress fails, e.g. slide 13 “When primary ingress fails, …”. I’m concerned that without clear indication that failure occurred at the Primary Ingress and not on the link, physical or logical, that connects the Backup and Primary, ingress protection is guaranteed to produce false negatives and, in my view, is not practical. I’d appreciate if we can discuss OAM aspects of ingress protection during our meeting on Thursday.

                Regards,
                                Greg

From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Vishnu Pavan Beeram
Sent: Sunday, January 24, 2016 2:54 PM
To: Huaimo Chen
Cc: Matt Hartley; teas-chairs@ietf.org; teas@ietf.org
Subject: Re: [Teas] Comparison Analysis (TEAS WG Virtual Interim Meeting (before IETF-95))

Huaimo,
Much Thanks for putting this slide-set together. It will help drive the discussion forward during the interim meeting.
It would be very useful if the comparative analysis covers all of the below aspects for both approaches (please see if you can fill in the missing pieces in your slide-set):

- Configuration Model: Discuss the "TE Tunnel" configuration needed for requesting "ingress protection". Discuss other prerequisites (if any) for configuring this.
- Protection Setup Procedures: Discuss the procedures on all relevant nodes ("primary ingress", " backup ingress" [,"proxy ingress"]) for setting up the primary LSP and the corresponding backup LSP. A signaling sequence diagram would be useful. Discuss the procedures for both "on path backup ingress" and "off path backup ingress".
- Session Maintenance Procedures: Discuss the procedures on all relevant nodes for maintaining (refreshes, triggers, teardown) primary-LSP state and the corresponding backup-LSP state.
- Local Repair Procedures: Discuss the procedures that come into play at the "backup ingress" when the "primary ingress" node failure is detected.
- "Revert to Primary Ingress" Procedures
- "Global Repair" Procedures

- Backwards Compatibility: Discuss "backwards compatibility" considerations for the proposed signaling extensions/procedures.
- Scaling Considerations: Discuss "scaling considerations" (amount of signaling state/messages to be maintained/processed).

- Security Considerations: Discuss "security considerations".
For items in the above list which do not entail any difference in the 2 approaches, just specify what is common to both.

****
Others in the WG,
If you disagree with any of the points made in the slide-set shared by Huaimo, please plan on presenting your arguments.

****
Please do plan on sending your slides to the chairs and the secretary (Matt on cc) by Wednesday.
Regards,
-Pavan

On Sat, Jan 23, 2016 at 11:26 PM, Huaimo Chen <huaimo.chen@huawei.com<mailto:huaimo.chen@huawei.com>> wrote:
Hi Chairs,

    Thanks for organizing the interim meeting.

    Lou asked for technical trade-off discussion of the current options in the I-D, these are:

        (1) Relay-Message Method

        (2) Proxy-Ingress Method

I conducted analysis and documented my results, these can be seen at:
http://www.slideshare.net/HuaimoChen/analysis-2methods
The findings include an example of both techniques. Looking forward to the interim call.

Best Regards,
Huaimo


From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Vishnu Pavan Beeram
Sent: Tuesday, January 05, 2016 9:33 PM
To: teas@ietf.org<mailto:teas@ietf.org>; teas-chairs@ietf.org<mailto:teas-chairs@ietf.org>
Subject: [Teas] TEAS WG Virtual Interim Meeting (before IETF-95)

Folks, Hi!

Happy New Year!!

We’d like the TEAS WG to hold a virtual interim meeting before IETF-95 to cover the following topic -

"RSVP Ingress Protection / Egress Protection” -- target meeting the week
of 25 January 2015 (with a second meeting possible if needed):
The main purpose of the meeting is to help select one of the two alternatives contained in <draft-ietf-teas-rsvp-ingress-protection>. A secondary purpose is to facilitate further discussion on <draft-ietf-teas-rsvp-egress-protection>, and gauge WG consensus on both drafts.

The following doodle poll will aid in selecting the exact date/time for this meeting: http://doodle.com/poll/7g4st77huxv66z2d

Regards,
Pavan and Lou.



_______________________________________________
Teas mailing list
Teas@ietf.org<mailto:Teas@ietf.org>
https://www.ietf.org/mailman/listinfo/teas