Re: [Pals] Suresh Krishnan's Discuss on draft-ietf-pals-endpoint-fast-protection-04: (with DISCUSS)

Yimin Shen <yshen@juniper.net> Thu, 15 December 2016 13:17 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 00949129536; Thu, 15 Dec 2016 05:17:21 -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_H4=-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 O73-_zjBTAV7; Thu, 15 Dec 2016 05:17:15 -0800 (PST)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0117.outbound.protection.outlook.com [104.47.36.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86B3F1295CA; Thu, 15 Dec 2016 05:17:15 -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=yW3nB6xY3isJZBLaWceN6WFlI+hAsTBaEw4uVoqw4XM=; b=eLM4xNLkbQecLTnmFXJPk3gNEmDoW6V7IaURzIrxHQhM4pNc0URcNY2eWRUeFeVj/ZbC5bQJYpn70v/Mbun09Y+ZTgl/4towriBUsieoupddvJWkuTbo5BVxrRokgMvph3Mih2VkHsysrDlPbNYSeb0vpD8MEtPGXSA5qWgQ5e8=
Received: from BN3PR0501MB1554.namprd05.prod.outlook.com (10.161.217.144) by BN3PR0501MB1556.namprd05.prod.outlook.com (10.161.217.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.803.5; Thu, 15 Dec 2016 13:17:14 +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; Thu, 15 Dec 2016 13:17:14 +0000
From: Yimin Shen <yshen@juniper.net>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, The IESG <iesg@ietf.org>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Thread-Topic: Suresh Krishnan's Discuss on draft-ietf-pals-endpoint-fast-protection-04: (with DISCUSS)
Thread-Index: AQHSVcOlAXzAUavoVUeC0EkuMsWrTaEIq8AA
Date: Thu, 15 Dec 2016 13:17:14 +0000
Message-ID: <EADBD9DF-9946-471B-A1D1-9E99FEC3803D@juniper.net>
References: <148169019017.10781.10584169948958330338.idtracker@ietfa.amsl.com> <3359736A-2192-435B-93C0-38514D10235F@juniper.net> <E87B771635882B4BA20096B589152EF64408839C@eusaamb107.ericsson.se>
In-Reply-To: <E87B771635882B4BA20096B589152EF64408839C@eusaamb107.ericsson.se>
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.14]
x-ms-office365-filtering-correlation-id: 170efdfa-3804-4572-1448-08d424ecafb9
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001); SRVR:BN3PR0501MB1556;
x-microsoft-exchange-diagnostics: 1; BN3PR0501MB1556; 7:GL8y4na/jsgQXY1jF0cvruuxecMan+EeIxo3i6Xe2DLNY22tg0SlpUl3mR33ynwa+qUwG9x7QOtJijBdSizKWeUmjo3zXtntAjYL0JnMudbm/GkCwDOOdGXFXrLMX33QM2kW3L5xhq4ySZeC7TQXUqIYM6nSTmYr11/uDNkTLM7oXuyY8E4ASAaus1KHumL2RR94DlL+l+HtlMDxZm36keQOqTp80o8WO2Jd5h8ftgIzaKpWM36mD9BI9AWBwvhdUlyLosDi+qVnpJ7K9VmngjXCfEjjsKpEmzmtIzAPDqcRh4lQUi+1aOufgci01GYJQvHlJGFmgqgo71qts2zbAKCMx+FCWXdKnSvw9pe02ur5iFlaraWv9BFkPhzucRRegN7mfDJ9maBEoP2MCab1qye5Kpef2+JFaGGrsDagtL7ZKlcbv14rDwewmlbiIradJv2EvIiLN0TPkMlUhjCegQ==
x-microsoft-antispam-prvs: <BN3PR0501MB1556EB3E1AEAFDE45BB89860BD9D0@BN3PR0501MB1556.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026)(6041248)(20161123555025)(20161123562025)(20161123564025)(20161123560025)(6072148); SRVR:BN3PR0501MB1556; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0501MB1556;
x-forefront-prvs: 0157DEB61B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(39450400003)(39860400002)(39410400002)(39850400002)(39840400002)(24454002)(43784003)(377454003)(199003)(189002)(81166006)(8676002)(81156014)(82746002)(8936002)(3846002)(68736007)(92566002)(102836003)(101416001)(2906002)(4326007)(6116002)(97736004)(3280700002)(3660700001)(83506001)(7736002)(36756003)(83716003)(76176999)(50986999)(189998001)(54356999)(105586002)(122556002)(106356001)(106116001)(305945005)(99286002)(2900100001)(77096006)(6512006)(2950100002)(86362001)(39060400001)(38730400001)(25786008)(6506006)(6486002)(6436002)(5001770100001)(561944003)(66066001)(4001350100001)(229853002)(230783001)(5660300001)(33656002)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR0501MB1556; 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: <DBCD95E9B4D9D548A7CBE25C48C4E5C1@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Dec 2016 13:17:14.2464 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0501MB1556
Archived-At: <https://mailarchive.ietf.org/arch/msg/pals/fVT9v5_Y-6qbm0Co87ih_77_q_0>
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] Suresh Krishnan's Discuss on draft-ietf-pals-endpoint-fast-protection-04: (with DISCUSS)
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: Thu, 15 Dec 2016 13:17:21 -0000

Hi Suresh, Carlos,

After rethinking of this, yes, I think you’ve made a good point, and I agree with you on that proposal. We will add encodings for IPv6 PE addresses for PWid and Generalized PWid in sections 6.4.1 and 6.4.2, respectively. This will be in a manner similar to RFC 6829.

Thanks again for your review and this valuable comment!

Thanks,

-- Yimin


On 12/14/16, 10:55 PM, "Suresh Krishnan" <suresh.krishnan@ericsson.com> wrote:

    Hi Yimin,
    
    On 12/14/2016 01:57 PM, Yimin Shen wrote:
    > Hi Suresh,
    >
    > Thanks very much for your review and the question about section 6.4.1 and 6.4.2.
    >
    > This document does not define any new encoding. Instead it is using the definitions of RFC4447, as noted in 6.4 for intro to 6.4.1 and 6.4.2. Specifically, the “Protection FEC Element TLV” uses the encoding and semantics of PWid FEC and Genercalize PWid FEC defined in RFC 4447. These FECs carry IPv4 addresses, and there is currently no IPv6 encoding defined for these FECs by IETF.
    
    I have a hard time understanding how this document does not define a new 
    encoding. The title of the section 6.4.1. is "Encoding Format for PWid" and 
    the TLV type is 0x83 which is *not* defined in RFC4447. Can you please 
    clarify what you mean? I think the proposal by Carlos to resolve this seems 
    to be reasonable to me.
    
    Thanks
    Suresh