Re: [Pce] I-D Action: draft-ietf-pce-segment-routing-ipv6-02.txt
Mahendra Singh Negi <mahendrasingh@huawei.com> Mon, 08 April 2019 05:01 UTC
Return-Path: <mahendrasingh@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 A8B24120071 for <pce@ietfa.amsl.com>; Sun, 7 Apr 2019 22:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 WhZeNbzb5Hqr for <pce@ietfa.amsl.com>; Sun, 7 Apr 2019 22:01:02 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 142EA1203A6 for <pce@ietf.org>; Sun, 7 Apr 2019 22:01:02 -0700 (PDT)
Received: from LHREML713-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id A809C5D2EC1183D37C8D for <pce@ietf.org>; Mon, 8 Apr 2019 06:00:59 +0100 (IST)
Received: from DGGEMI423-HUB.china.huawei.com (10.1.199.152) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 8 Apr 2019 06:00:59 +0100
Received: from DGGEMI532-MBX.china.huawei.com ([169.254.7.210]) by dggemi423-hub.china.huawei.com ([10.1.199.152]) with mapi id 14.03.0415.000; Mon, 8 Apr 2019 13:00:49 +0800
From: Mahendra Singh Negi <mahendrasingh@huawei.com>
To: "pce@ietf.org" <pce@ietf.org>
Thread-Topic: [Pce] I-D Action: draft-ietf-pce-segment-routing-ipv6-02.txt
Thread-Index: AQHU7cM6fVaZd6QZDk6S1KR0LclIU6Yxr5Eg
Date: Mon, 08 Apr 2019 05:00:48 +0000
Message-ID: <B495DF531F7B5943B1816E2031125EF8B5651499@DGGEMI532-MBX.china.huawei.com>
References: <155469755810.18250.1359855505282242745@ietfa.amsl.com>
In-Reply-To: <155469755810.18250.1359855505282242745@ietfa.amsl.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.153.41]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/Bu7xhjsBiNO9zTp61MgYJkdEBSw>
Subject: Re: [Pce] I-D Action: draft-ietf-pce-segment-routing-ipv6-02.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 08 Apr 2019 05:01:05 -0000
Hi All, Thanks for the valuable suggestions/comments. We have fixed all the comments received, difference link goes below: Diff: https://www.ietf.org/rfcdiff?url1=draft-ietf-pce-segment-routing-ipv6-00&url2=draft-ietf-pce-segment-routing-ipv6-02 Please do reach out to us in case you have comments/suggestions. Regards, Mahendra -----Original Message----- From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org Sent: 08 April 2019 09:56 To: i-d-announce@ietf.org Cc: pce@ietf.org Subject: [Pce] I-D Action: draft-ietf-pce-segment-routing-ipv6-02.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Path Computation Element WG of the IETF. Title : PCEP Extensions for Segment Routing leveraging the IPv6 data plane Authors : Mahendra Singh Negi Cheng Li Siva Sivabalan Prejeeth Kaladharan Yongqing Zhu Filename : draft-ietf-pce-segment-routing-ipv6-02.txt Pages : 22 Date : 2019-04-07 Abstract: The Source Packet Routing in Networking (SPRING) architecture describes how Segment Routing (SR) can be used to steer packets through an IPv6 or MPLS network using the source routing paradigm. SR enables any head-end node to select any path without relying on a hop-by-hop signaling technique (e.g., LDP or RSVP-TE). It depends only on "segments" that are advertised by Link- State IGPs. A Segment Routed Path can be derived from a variety of mechanisms, including an IGP Shortest Path Tree (SPT), explicit configuration, or a Path Computation Element (PCE). Since SR can be applied to both MPLS and IPv6 forwarding plane, a PCE should be able to compute SR-Path for both MPLS and IPv6 forwarding plane. This document describes the extensions required for SR support for IPv6 data plane in Path Computation Element communication Protocol (PCEP). The PCEP extension and mechanism to support SR-MPLS is described in [I-D.ietf-pce-segment-routing]. This document extends it to support SRv6 (SR over IPv6). The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-pce-segment-routing-ipv6/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-pce-segment-routing-ipv6-02 https://datatracker.ietf.org/doc/html/draft-ietf-pce-segment-routing-ipv6-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-segment-routing-ipv6-02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce
- [Pce] I-D Action: draft-ietf-pce-segment-routing-… internet-drafts
- Re: [Pce] I-D Action: draft-ietf-pce-segment-rout… Mahendra Singh Negi