Re: [Pce] Jim Guichard's No Objection on draft-ietf-pce-segment-routing-ipv6-22: (with COMMENT)
Cheng Li <c.l@huawei.com> Tue, 02 April 2024 18:40 UTC
Return-Path: <c.l@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C2A4C1840E5; Tue, 2 Apr 2024 11:40:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.194
X-Spam-Level:
X-Spam-Status: No, score=-4.194 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8TF_Qhfh1EIZ; Tue, 2 Apr 2024 11:40:40 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FC07C14CE5D; Tue, 2 Apr 2024 11:40:40 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4V8GrC1xTGz6K5xJ; Wed, 3 Apr 2024 02:39:23 +0800 (CST)
Received: from frapeml500004.china.huawei.com (unknown [7.182.85.22]) by mail.maildlp.com (Postfix) with ESMTPS id 3E70C140B2F; Wed, 3 Apr 2024 02:40:37 +0800 (CST)
Received: from dggpemm500003.china.huawei.com (7.185.36.56) by frapeml500004.china.huawei.com (7.182.85.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Tue, 2 Apr 2024 20:40:36 +0200
Received: from dggpemm500003.china.huawei.com ([7.185.36.56]) by dggpemm500003.china.huawei.com ([7.185.36.56]) with mapi id 15.01.2507.035; Wed, 3 Apr 2024 02:40:34 +0800
From: Cheng Li <c.l@huawei.com>
To: James Guichard <james.n.guichard@futurewei.com>, Dhruv Dhody <dhruv.ietf@gmail.com>
CC: The IESG <iesg@ietf.org>, "draft-ietf-pce-segment-routing-ipv6@ietf.org" <draft-ietf-pce-segment-routing-ipv6@ietf.org>, "hari@netflix.com" <hari@netflix.com>, "pce@ietf.org" <pce@ietf.org>, "pce-chairs@ietf.org" <pce-chairs@ietf.org>
Thread-Topic: [Pce] Jim Guichard's No Objection on draft-ietf-pce-segment-routing-ipv6-22: (with COMMENT)
Thread-Index: AQHahDFMqRJOpHySa0ayCdD0wqNcS7FUBf8AgABQpoCAAPrqUA==
Date: Tue, 02 Apr 2024 18:40:34 +0000
Message-ID: <0770bdb14557472a98940a9f163d8b98@huawei.com>
References: <171197500439.37966.2137822713915824613@ietfa.amsl.com> <CAB75xn7X=Khi4qSeop0MfU0Dge2HUDmogCkYvF3UvTbk+r1wUA@mail.gmail.com> <MW5PR13MB54854BC726A9F22E443EC676D23E2@MW5PR13MB5485.namprd13.prod.outlook.com>
In-Reply-To: <MW5PR13MB54854BC726A9F22E443EC676D23E2@MW5PR13MB5485.namprd13.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.81.213.176]
Content-Type: multipart/alternative; boundary="_000_0770bdb14557472a98940a9f163d8b98huaweicom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/1hi49O4m67D3BEp2SBuLNrTfL38>
Subject: Re: [Pce] Jim Guichard's No Objection on draft-ietf-pce-segment-routing-ipv6-22: (with COMMENT)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Apr 2024 18:40:44 -0000
Thank you Dhruv for proposing the text, and Jim for your comments. We have updated the draft accordingly, please see the update below. Thanks, Cheng From: James Guichard <james.n.guichard@futurewei.com> Sent: Tuesday, April 2, 2024 1:41 PM To: Dhruv Dhody <dhruv.ietf@gmail.com> Cc: The IESG <iesg@ietf.org>; draft-ietf-pce-segment-routing-ipv6@ietf.org; hari@netflix.com; pce@ietf.org; pce-chairs@ietf.org Subject: Re: [Pce] Jim Guichard's No Objection on draft-ietf-pce-segment-routing-ipv6-22: (with COMMENT) Thanks Dhruv that certainly reads better. Jim Get Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: Dhruv Dhody <dhruv.ietf@gmail.com<mailto:dhruv.ietf@gmail.com>> Sent: Tuesday, April 2, 2024 2:51:54 AM To: James Guichard <james.n.guichard@futurewei.com<mailto:james.n.guichard@futurewei.com>> Cc: The IESG <iesg@ietf.org<mailto:iesg@ietf.org>>; draft-ietf-pce-segment-routing-ipv6@ietf.org<mailto:draft-ietf-pce-segment-routing-ipv6@ietf.org> <draft-ietf-pce-segment-routing-ipv6@ietf.org<mailto:draft-ietf-pce-segment-routing-ipv6@ietf.org>>; hari@netflix.com<mailto:hari@netflix.com> <hari@netflix.com<mailto:hari@netflix.com>>; pce@ietf.org<mailto:pce@ietf.org> <pce@ietf.org<mailto:pce@ietf.org>>; pce-chairs@ietf.org<mailto:pce-chairs@ietf.org> <pce-chairs@ietf.org<mailto:pce-chairs@ietf.org>> Subject: Re: [Pce] Jim Guichard's No Objection on draft-ietf-pce-segment-routing-ipv6-22: (with COMMENT) Hi Jim, On Mon, Apr 1, 2024 at 6:06 PM Jim Guichard via Datatracker <noreply@ietf.org<mailto:noreply@ietf.org>> wrote: Jim Guichard has entered the following ballot position for draft-ietf-pce-segment-routing-ipv6-22: 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/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-pce-segment-routing-ipv6/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you for a well written document. Minor nit: Section 3.1 - 2nd Paragraph. Please review this paragraph as it seems to say that the MPLS mechanisms remain unchanged, but the text is difficult to parse. Please make the meaning clear. Yes, I can see that. The text aimed to clarify that in the case IPv6 is used (instead of IPv4) for SR-MPLS, the PCEP procedures are as per RFC 8664 and not this document. How is this change -> OLD: For the use of an IPv6 control plane but an MPLS data plane, mechanism remains the same as specified in [RFC8664]. This document describes the extension to support SRv6 in PCEP. NEW: When SR-MPLS is used with an IPv6 network, the PCEP procedures and mechanisms are as specified in [RFC8664]. When SR leverages the IPv6 forwarding plane (i.e. SRv6), the PCEP procedures and mechanisms are extended in this document. END Thanks! Dhruv _______________________________________________ Pce mailing list Pce@ietf.org<mailto:Pce@ietf.org> https://www.ietf.org/mailman/listinfo/pce
- [Pce] Jim Guichard's No Objection on draft-ietf-p… Jim Guichard via Datatracker
- Re: [Pce] Jim Guichard's No Objection on draft-ie… Dhruv Dhody
- Re: [Pce] Jim Guichard's No Objection on draft-ie… James Guichard
- Re: [Pce] Jim Guichard's No Objection on draft-ie… Cheng Li