Re: [Pals] Mirja Kühlewind's No Objection on draft-ietf-pals-mpls-tp-dual-homing-coordination-05: (with COMMENT)

"Dongjie (Jimmy)" <jie.dong@huawei.com> Wed, 01 March 2017 06:48 UTC

Return-Path: <jie.dong@huawei.com>
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 42FDD129469; Tue, 28 Feb 2017 22:48:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 O2VqMam_hmtF; Tue, 28 Feb 2017 22:48:46 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73ED512941D; Tue, 28 Feb 2017 22:48:45 -0800 (PST)
Received: from 172.18.7.190 (EHLO LHREML711-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DBX20548; Wed, 01 Mar 2017 06:48:42 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 1 Mar 2017 06:48:41 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Wed, 1 Mar 2017 14:48:35 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Mirja Kühlewind <ietf@kuehlewind.net>, The IESG <iesg@ietf.org>
Thread-Topic: Mirja Kühlewind's No Objection on draft-ietf-pals-mpls-tp-dual-homing-coordination-05: (with COMMENT)
Thread-Index: AQHSkeEdXSW/2QPYykKkT1H/fkjpJKF/g+FQ
Date: Wed, 01 Mar 2017 06:50:17 +0000
Message-ID: <76CD132C3ADEF848BD84D028D243C9279358B0C4@NKGEML515-MBX.china.huawei.com>
References: <148829989956.29494.7224618792577082144.idtracker@ietfa.amsl.com>
In-Reply-To: <148829989956.29494.7224618792577082144.idtracker@ietfa.amsl.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.151.75]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.58B66ECA.033D, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 201379164c96210eecc695711b2f21b1
Archived-At: <https://mailarchive.ietf.org/arch/msg/pals/SUDi_EKs7Pq8nbF6_svAzK4X_Ro>
Cc: "stewart.bryant@gmail.com" <stewart.bryant@gmail.com>, "pals-chairs@ietf.org" <pals-chairs@ietf.org>, "draft-ietf-pals-mpls-tp-dual-homing-coordination@ietf.org" <draft-ietf-pals-mpls-tp-dual-homing-coordination@ietf.org>, "pals@ietf.org" <pals@ietf.org>
Subject: Re: [Pals] Mirja Kühlewind's No Objection on draft-ietf-pals-mpls-tp-dual-homing-coordination-05: (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: Wed, 01 Mar 2017 06:48:50 -0000

Hi Mirja, 

Thanks a lot for your comments. Please see my replies inline.

> -----Original Message-----
> From: Mirja Kühlewind [mailto:ietf@kuehlewind.net]
> Sent: Wednesday, March 01, 2017 12:38 AM
> To: The IESG <iesg@ietf.org>
> Cc: draft-ietf-pals-mpls-tp-dual-homing-coordination@ietf.org; Stewart Bryant
> <stewart.bryant@gmail.com>; pals-chairs@ietf.org;
> stewart.bryant@gmail.com; pals@ietf.org
> Subject: Mirja Kühlewind's No Objection on
> draft-ietf-pals-mpls-tp-dual-homing-coordination-05: (with COMMENT)
> 
> Mirja Kühlewind has entered the following ballot position for
> draft-ietf-pals-mpls-tp-dual-homing-coordination-05: No Objection
> 
> 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-mpls-tp-dual-homing-coordinati
> on/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Minor mostly editorial comments:
> 
> 1) When I first saw "DHC Code Point" in figure 2, I was slightly confused
> because this doesn't show in the rest of the doc anymore. Maybe rename to
> 'DHC channel type' or use the same term in the text or directly put the value in
> there that will be assigned by IANA.

Thanks for pointing out this. Will change this to "DHC Channel Type" in next revision. 
> 
> 2) 3.1.:"After the transmission of the three messages, the
>    dual-homing PE MUST send the most recently transmitted Dual-Node
>    Switching TLV periodically to the other dual-homing PE on a continual
>    basis using the DHC message."
>    This is only if the protection is active, right?

Yes, the switching TLV is sent periodically after the protection is in active. 

> 
> 3) 3.2.:"Whenever a change of service PW status is detected by a dual-homing
>    PE, it MUST be reflected in the PW Status TLV and sent to the other
>    dual-homing PE immediately using the 3 consecutive DHC messages.
>    This way, both dual-homing PEs have the status of the working and
>    protection PW consistently."
>    Note, it's possible that all three messages get lost. If you want to make
> sure you stay in sync, you need an explicit mechanism for reliability, e.g.
> sending an ack.

The 3 consecutive message mechanism is similar to the mechanism defined in section 4.1 of rfc6378 (MPLS-TP linear protection). It can ensure the state exchange if one or two of the 3 messages get lost. And after the 3 consecutive messages, the message will still be transmitted continuously as defined in section 3.1 of this draft, so the dual-homing PEs would stay in sync. 

Best regards,
Jie