Re: [Pals] Alia Atlas' Yes on draft-ietf-pals-endpoint-fast-protection-04: (with COMMENT)

Yimin Shen <yshen@juniper.net> Fri, 16 December 2016 21:13 UTC

Return-Path: <yshen@juniper.net>
X-Original-To: pals@ietfa.amsl.com
Delivered-To: pals@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A664129EB0; Fri, 16 Dec 2016 13:13:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level:
X-Spam-Status: No, score=-1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=junipernetworks.onmicrosoft.com
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 qzYhYvk78yKw; Fri, 16 Dec 2016 13:13:30 -0800 (PST)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0109.outbound.protection.outlook.com [104.47.38.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D19A1294C6; Fri, 16 Dec 2016 13:13:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=rQXwgTxZJJow6XfItT4SvVPR7q2h0/PLYmsznFRfI6k=; b=SH8m48yPaByHFQJIMuD566LKSKjFXZnTtMSnM9mDEh8H1WQRrJU7vIfa0+Wbl+lVdTRg0/BNZ1YTDO0LJnEboLoB9iFbWnOBR2qkXX4gN/SNJhbiAPEbgAQExGrdJ84pXZg5hKIJ+YQCzy9MupZysAlP7qZihJGI8DcVznQHur8=
Received: from BN3PR0501MB1554.namprd05.prod.outlook.com (10.161.217.144) by BN3PR0501MB1555.namprd05.prod.outlook.com (10.161.217.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.803.5; Fri, 16 Dec 2016 21:13:29 +0000
Received: from BN3PR0501MB1554.namprd05.prod.outlook.com ([10.161.217.144]) by BN3PR0501MB1554.namprd05.prod.outlook.com ([10.161.217.144]) with mapi id 15.01.0789.013; Fri, 16 Dec 2016 21:13:29 +0000
From: Yimin Shen <yshen@juniper.net>
To: Alia Atlas <akatlas@gmail.com>, The IESG <iesg@ietf.org>
Thread-Topic: Alia Atlas' Yes on draft-ietf-pals-endpoint-fast-protection-04: (with COMMENT)
Thread-Index: AQHSVjDhS0hUpgSSKUGrRWFGBZeFZ6EKwkoA
Date: Fri, 16 Dec 2016 21:13:29 +0000
Message-ID: <4C898049-4580-4F84-9867-524E34D6F3B1@juniper.net>
References: <148173710514.16775.4455276390142203374.idtracker@ietfa.amsl.com>
In-Reply-To: <148173710514.16775.4455276390142203374.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.18.0.160709
authentication-results: spf=none (sender IP is ) smtp.mailfrom=yshen@juniper.net;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [66.129.241.10]
x-ms-office365-filtering-correlation-id: efa651b9-6aec-4d53-90c1-08d425f86206
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001); SRVR:BN3PR0501MB1555;
x-microsoft-exchange-diagnostics: 1; BN3PR0501MB1555; 7:mqdK41bQuzkRsyrBZPnu/nxDR/aa58ta9zVN5jLhafXlBDk4tEHg/QE3Dsf6y9qY1Zatq5/I/vqZDisszhyuel9LE2gl71DI3c1eonwxSW9YP8u6p+OE2sTOGeyKhHSVPZTbpjcXROqOQDi6mM4LAcs5aqVEQC6xRqn7aiLnN0y9PDX0jHa9OJgnTLOq1zaCBl0MIyfMx1kJCx3akYkqSrFIm5RM71RmBJpvpLNqJn9T08Lwwas1zc07yfZa75gyJ7IpHAKXrMWhULwIcqC8JVGgFv45T6YUjnXvRACOGl15piw8dKHVODZd25/ztJUYkUtFy8Dbka8xyiBSNLOtJTs3f3ivQl9Pc0kz9tt6An7g/1+xBcyL5jT/9JBNWVAEwZ0fMODYQOnC+2rbZ+q8gTBBaAGIcIEXfhQNh6auesji390WMznD/4AYtBpFygod/1gJNAWScJVL0j3hFbTOdg==
x-microsoft-antispam-prvs: <BN3PR0501MB155539982940EE449CF9A7CBBD9C0@BN3PR0501MB1555.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026)(6041248)(20161123564025)(20161123560025)(20161123555025)(20161123562025)(20161123558021)(6072148); SRVR:BN3PR0501MB1555; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0501MB1555;
x-forefront-prvs: 01583E185C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(39840400002)(39410400002)(39450400003)(39860400002)(39850400002)(199003)(377454003)(24454002)(189002)(5001770100001)(189998001)(5660300001)(76176999)(230783001)(4001350100001)(50986999)(54356999)(3660700001)(3280700002)(68736007)(101416001)(7736002)(305945005)(33656002)(6436002)(77096006)(229853002)(92566002)(2900100001)(86362001)(97736004)(105586002)(2950100002)(99286002)(2906002)(106116001)(6512006)(6506006)(25786008)(82746002)(83716003)(3846002)(6116002)(102836003)(38730400001)(36756003)(8936002)(122556002)(106356001)(6486002)(4326007)(81166006)(39060400001)(8676002)(81156014)(66066001)(83506001)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR0501MB1555; H:BN3PR0501MB1554.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <E46B082A600AC640AE77C13A60550ABD@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Dec 2016 21:13:29.0765 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0501MB1555
Archived-At: <https://mailarchive.ietf.org/arch/msg/pals/bIcvy02XBIVDbqWk7ExeJnG0JAw>
Cc: "draft-ietf-pals-endpoint-fast-protection@ietf.org" <draft-ietf-pals-endpoint-fast-protection@ietf.org>, "pals-chairs@ietf.org" <pals-chairs@ietf.org>, "pals@ietf.org" <pals@ietf.org>, Stewart Bryant <stewart.bryant@gmail.com>
Subject: Re: [Pals] Alia Atlas' Yes on draft-ietf-pals-endpoint-fast-protection-04: (with COMMENT)
X-BeenThere: pals@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Pseudowire And LDP-enabled Services dicussion list." <pals.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pals>, <mailto:pals-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pals/>
List-Post: <mailto:pals@ietf.org>
List-Help: <mailto:pals-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pals>, <mailto:pals-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2016 21:13:34 -0000

Hi Alia,

Thanks very much for the detailed review (for those examples) and comments. Please see my clarification below, using Figure-11.

There are two bypass tunnels. One goes from P3 – P4 – PE4. So, P3 pushes label 2000, and P4 swaps it to the context label 999. (PE4 has bound label 999 to the bypass tunnel).

Likewise, the other bypass tunnel goes from PE2 – P5 – PE4. So, PE2 pushes label 3000, and P5 swaps it to the context label 999. (PE4 has bound label 999 to this bypass tunnel as well).

I will add forwarding state detail of P4 and P5 to the document, like below.


          |<-------------- PW1 --------------->|

      - PE1 -------------- P1 ------- P3 --------- PE2 ------
     /                                             PLR \         PLR        \
    /                                                         \        |             \
   /                                                            \      |                \
CE1                                            bypass P4   P5 bypass   CE2
   \                                                                \   |              /
    \                                                                \  |           /
     \                                                                \ |        /
      - PE3 -------------- P2 ---------------- PE4 ------
                                            protector

          |<-------------- PW2 --------------->|

	 PW1's label assigned by PE2: 100
	 PW2's label assigned by PE4: 200
	 On P3: </t>
	     Incoming label of transport tunnel to PE2: 1000
	     Outgoing label of transport tunnel to PE2: implicit null
	     Outgoing label of bypass tunnel to PE4: 2000
	 On PE2:
	     Outgoing label of bypass tunnel to PE4: 3000
	 On PE4:
	     Context label (incoming label of bypass tunnels): 999 <<<<<<<<<< Notice this
	 
	 Forwarding state on P3:
	 label 1000 -- primary nexthop: pop, to PE2
	                         backup nexthop:  swap 2000, to P4

	 Forwarding state on PE2:
	 label 100 -- primary nexthop: pop, to CE2
	                       backup nexthop:  push 3000, to P5

	 Forwarding state on P4:  <<<<<<<<<<<<<<<<< Will add 
	 label 2000 -- nexthop: swap to 999, to PE4 <<<<<<<<<<<<<<<<< Will add

	 Forwarding state on P5: <<<<<<<<<<<<<<<< Will add
	 label 3000 -- nexthop: swap to 999, to PE4 <<<<<<<<<<<<<<<< Will add


	 Forwarding state on PE4:
	 label 200 -- nexthop: pop, to CE2
	 label 999 -- nexthop: label table of PE2's label space <<<<<<<<<<<<<< This is the context label, which is also the in-coming label of both bypass tunnels.

Thanks,

-- Yimin


On 12/14/16, 12:38 PM, "Alia Atlas" <akatlas@gmail.com> wrote:

    Alia Atlas has entered the following ballot position for
    draft-ietf-pals-endpoint-fast-protection-04: Yes
    
    When responding, please keep the subject line intact and reply to all
    email addresses included in the To and CC lines. (Feel free to cut this
    introductory paragraph, however.)
    
    
    Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
    for more information about IESG DISCUSS and COMMENT positions.
    
    
    The document, along with other ballot positions, can be found here:
    https://datatracker.ietf.org/doc/draft-ietf-pals-endpoint-fast-protection/
    
    
    
    ----------------------------------------------------------------------
    COMMENT:
    ----------------------------------------------------------------------
    
    Minor:
    
    1) The details in Figure 11 on p. 22 don't look quite right.    There is
    no forwarding state shown on PE4 to handle the incoming labels of 2000
    (P3's outgoing label of bypass tunnel to PE4) or 3000 (P2's outgoing
    label of bypass tunnel to PE4).    Either there should be additional
    forwarding state on PE4 that says to pop 2000 (or 3000) and identify a
    context label space - or PE4 should have allocated the context label 999
    to the bypass tunnels from P3 and PE2.
    
    I see the same issue in Figures 12, 13, and 14.   Is there  a detail or
    explanation missing?