Re: [spring] FW: I-D Action: draft-ietf-spring-srv6-network-programming-03.txt

"Wang, Weibin (NSB - CN/Shanghai)" <weibin.wang@nokia-sbell.com> Tue, 08 October 2019 02:23 UTC

Return-Path: <weibin.wang@nokia-sbell.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2830C120111; Mon, 7 Oct 2019 19:23:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.106
X-Spam-Level:
X-Spam-Status: No, score=-1.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 JVZkQAbBGSxY; Mon, 7 Oct 2019 19:23:37 -0700 (PDT)
Received: from cnshjsmin03.alcatel-sbell.com.cn (unknown [116.246.26.71]) (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 B28ED120019; Mon, 7 Oct 2019 19:23:34 -0700 (PDT)
X-AuditID: ac189297-82bff7000001426c-32-5d9bf2ee1e5d
Received: from CNSHPPEXCH1604.nsn-intra.net (Unknown_Domain [135.251.51.104]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by cnshjsmin03.alcatel-sbell.com.cn (Symantec Messaging Gateway) with SMTP id EF.76.17004.EE2FB9D5; Tue, 8 Oct 2019 10:22:38 +0800 (HKT)
Received: from CNSHPPEXCH1605.nsn-intra.net (135.251.51.105) by CNSHPPEXCH1604.nsn-intra.net (135.251.51.104) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Tue, 8 Oct 2019 10:22:37 +0800
Received: from CNSHPPEXCH1605.nsn-intra.net ([135.251.51.105]) by CNSHPPEXCH1605.nsn-intra.net ([135.251.51.105]) with mapi id 15.01.1713.007; Tue, 8 Oct 2019 10:22:37 +0800
From: "Wang, Weibin (NSB - CN/Shanghai)" <weibin.wang@nokia-sbell.com>
To: li zhenqiang <li_zhenqiang@hotmail.com>, "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com>, "spring@ietf.org" <spring@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
CC: draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org>
Thread-Topic: RE: [spring] FW: I-D Action: draft-ietf-spring-srv6-network-programming-03.txt
Thread-Index: AQHVcwZHuPajcK5w7kyDna3/5tWK0adQD0rg
Date: Tue, 08 Oct 2019 02:22:37 +0000
Message-ID: <95454cb2ed384974af6ed8f841486189@nokia-sbell.com>
References: <156934935460.15603.11867492604510639688@ietfa.amsl.com>, <031BE952-7C37-4E4A-8F16-6038CB26C4A1@cisco.com>, <HK0PR03MB406608C49475C873C6EFA3A5FC810@HK0PR03MB4066.apcprd03.prod.outlook.com>, <498DEE4B-0119-4A9B-98FC-BBD0579F1E58@cisco.com>, <HK0PR03MB40661A3BC55E507916567364FC800@HK0PR03MB4066.apcprd03.prod.outlook.com>, <d248c9e5841a4e0aba4e4aa613e1a8ba@nokia-sbell.com> <HK0PR03MB4066A143540A2E53670EE545FC9A0@HK0PR03MB4066.apcprd03.prod.outlook.com>
In-Reply-To: <HK0PR03MB4066A143540A2E53670EE545FC9A0@HK0PR03MB4066.apcprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.251.51.115]
Content-Type: multipart/alternative; boundary="_000_95454cb2ed384974af6ed8f841486189nokiasbellcom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrNIsWRmVeSWpSXmKPExsXS/ts4Q/fdp9mxBmdW8ljMn7yV1eLl2fdM Fvv3rWe2+HV8F4vF8Qu/GR1YPab83sjq8bjnDJvHkiU/mQKYo7hsUlJzMstSi/TtErgybj9a yFjw4xJLxYy7ncwNjIcOs3QxcnBICJhIbFqu18XIxSEkcJxJ4vyLHYwQzh9GifYN/ewQzkZG iRmNZ1i7GDk52ATcJCZt28UGkhARWMEoMfH4JCaQUcwCaRK3t+mC1AgLxEpMb13ACGKLCMRJ /Fz7gRnCNpJYsOICWDmLgIrElkMxIGFeATuJFUsWMkHsesQsMfPRebBdnEBzrj28zQ5iMwqI SXw/tYYJxGYWEJe49WQ+mC0hICCxZM95ZghbVOLl43+sEJ8pSfRtgCpPlZg8bw0bxC5BiZMz n7BMYBSdhWTSLCRls5CUzQJ7TFNi/S59iBJFiSndD9khbA2J1jlz2ZHFFzCyr2KUTs4rzsgq zs3MMzDWy8vPzkzULU5KzcnRS87P3cQIjNI1EpOm72A8dsD7EKMAB6MSD2+B7uxYIdbEsuLK 3EOMEhzMSiK8cktnxArxpiRWVqUW5ccXleakFh9ilOZgURLn/d3qFCskkJ5YkpqdmlqQWgST ZeLglGpg3CHj35LzjdXrWsL7uTvXFhzQXznhzzEFze5l+nW3WWubOz5dvTHx6c9Ld2dtSfRb XxV1+mX3NedO7yyGCQ8/x72yi0+Ss+Nt3rDjz24r0zj/HzG/Ynwvhkrevt8SGu/anaLCes1X c4JDnNHiysD3rwt6P70XSWmvO7r+SI164v8/SWqvuW6eVmIpzkg01GIuKk4EAGXDVPHOAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/V0ZpjVLSVZxHaBwecXFxqJjlg_c>
Subject: Re: [spring] FW: I-D Action: draft-ietf-spring-srv6-network-programming-03.txt
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Oct 2019 02:23:46 -0000

Hi Li:

For example in SRv6-based L3VPN service scenario,  The ingress PE within SRv6-enabled domain can utilize SR-TE policy to enable TE-path function when encapsulating and transiting L3VPN traffic, The Ingress PE push on customer packets with SID list representing SR-TE policy plus END.DT4 as last SRv6 SID in SRH;  So I think,  each flavor of PSP/USP/USD can be designed to perform in related SRv6 endpoint. Imaging the PSP, the penultimate Endpoint can perform PSP, e.g. copy the last SID (END.DT4) of SRH to destination field of IPv6 header and POP the SRH, then forwarding it toward egress PE identified by DA.

--------------------------------------
Cheers !


WANG Weibin

From: li zhenqiang <li_zhenqiang@hotmail.com>
Sent: 2019年10月8日 9:35
To: Wang, Weibin (NSB - CN/Shanghai) <weibin.wang@nokia-sbell.com>; Pablo Camarillo (pcamaril) <pcamaril@cisco.com>; spring@ietf.org; ipv6@ietf.org
Cc: draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org>
Subject: Re: RE: [spring] FW: I-D Action: draft-ietf-spring-srv6-network-programming-03.txt

Would you please illustrate your examples in detail with specific topologies? Thanks. I want to see the differences among PSP, USP and USD.

Best Regards,
Zhenqiang Li
________________________________
li_zhenqiang@hotmail.com<mailto:li_zhenqiang@hotmail.com>

From: Wang, Weibin (NSB - CN/Shanghai)<mailto:weibin.wang@nokia-sbell.com>
Date: 2019-09-29 08:35
To: li zhenqiang<mailto:li_zhenqiang@hotmail.com>; Pablo Camarillo (pcamaril)<mailto:pcamaril@cisco.com>; spring@ietf.org<mailto:spring@ietf.org>; ipv6@ietf.org<mailto:ipv6@ietf.org>
CC: draft-ietf-spring-srv6-network-programming<mailto:draft-ietf-spring-srv6-network-programming@ietf.org>
Subject: RE: Re: [spring] FW: I-D Action: draft-ietf-spring-srv6-network-programming-03.txt
I think, If SRv6 domain ingress Node encapsulated new outer IPv6 header and inserted SRH simultaneously on Packets entering the SRv6 domain, when the packet reach penultimate or egress Node, the PSP and USP may be invoked;  another example, if packet which is originated or destined to Nodes within SRv6 domain, and the SRH inserted at originated at source represent a TE-path within SRv6 domain, the PSP and USP May also be used, such as CLI Ping command.

--------------------------------------
Cheers !


WANG Weibin

From: ipv6 <ipv6-bounces@ietf.org<mailto:ipv6-bounces@ietf.org>> On Behalf Of li zhenqiang
Sent: 2019年9月28日 23:15
To: Pablo Camarillo (pcamaril) <pcamaril@cisco.com<mailto:pcamaril@cisco.com>>; spring@ietf.org<mailto:spring@ietf.org>; ipv6@ietf.org<mailto:ipv6@ietf.org>
Cc: draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org<mailto:draft-ietf-spring-srv6-network-programming@ietf.org>>
Subject: Re: Re: [spring] FW: I-D Action: draft-ietf-spring-srv6-network-programming-03.txt

Hello Pablo,

Without SRH insertion, PSP and USP are not needed. The example you give is decapsulation, not SRH pop.
I can not imagine the scenario that will use PSP or USP without SRH insertion. We need illustration to keep them in the draft.

Best Regards,
Zhenqiang Li
________________________________
li_zhenqiang@hotmail.com<mailto:li_zhenqiang@hotmail.com>

From: Pablo Camarillo (pcamaril)<mailto:pcamaril@cisco.com>
Date: 2019-09-27 19:13
To: li zhenqiang<mailto:li_zhenqiang@hotmail.com>; spring@ietf.org<mailto:spring@ietf.org>; ipv6@ietf.org<mailto:ipv6@ietf.org>
CC: draft-ietf-spring-srv6-network-programming<mailto:draft-ietf-spring-srv6-network-programming@ietf.org>
Subject: Re: [spring] FW: I-D Action: draft-ietf-spring-srv6-network-programming-03.txt
Hi Zhenqiang,

Can you clarify what is the issue with the PSP and USP flavors and how it is related to SRH insertion?

For example USP flavor removes the SRH at the last segment (the final destination of the IP packet), before proceeding with the upper layer header processing.

Cheers,
Pablo.

From: li zhenqiang <li_zhenqiang@hotmail.com<mailto:li_zhenqiang@hotmail.com>>
Date: Friday, 27 September 2019 at 10:41
To: "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com<mailto:pcamaril@cisco.com>>, "spring@ietf.org<mailto:spring@ietf.org>" <spring@ietf.org<mailto:spring@ietf.org>>, "ipv6@ietf.org<mailto:ipv6@ietf.org>" <ipv6@ietf.org<mailto:ipv6@ietf.org>>
Cc: draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org<mailto:draft-ietf-spring-srv6-network-programming@ietf.org>>
Subject: Re: [spring] FW: I-D Action: draft-ietf-spring-srv6-network-programming-03.txt

Hi Pablo and all,

Thank the authors for their efforts and quick reponse to the discussion in the list.
Since the SRH insertion parts are now removed from the base srv6 network programming draft, are the PSP and USP flavors appropriate to stay here? They do the SRH POP action.

Best Regards,
Zhenqiang Li
________________________________
li_zhenqiang@hotmail.com<mailto:li_zhenqiang@hotmail.com>

From: Pablo Camarillo (pcamaril)<mailto:pcamaril@cisco.com>
Date: 2019-09-25 02:30
To: spring@ietf.org<mailto:spring@ietf.org>
CC: draft-ietf-spring-srv6-network-programming@ietf.org<mailto:draft-ietf-spring-srv6-network-programming@ietf.org>
Subject: [spring] FW: I-D Action: draft-ietf-spring-srv6-network-programming-03.txt
Hi all,

We have just posted the split of SRv6 Network Programming.
The SR endpoint and transit behaviors that perform SRH insertion are now under a new individual draft (draft-filsfils-spring-srv6-net-pgm-insertion). This revision does not contain any other update.

As mentioned last week, throughout the rest of the week we will push another update with a few functional updates (e.g. NH=59).

Thank you,
Pablo (on behalf of the authors).


-----Original Message-----
From: spring <spring-bounces@ietf.org<mailto:spring-bounces@ietf.org>> on behalf of "internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>" <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Reply to: "spring@ietf.org<mailto:spring@ietf.org>" <spring@ietf.org<mailto:spring@ietf.org>>
Date: Tuesday, 24 September 2019 at 20:23
To: "i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>" <i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>>
Cc: "spring@ietf.org<mailto:spring@ietf.org>" <spring@ietf.org<mailto:spring@ietf.org>>
Subject: [spring] I-D Action: draft-ietf-spring-srv6-network-programming-03.txt


    A New Internet-Draft is available from the on-line Internet-Drafts directories.
    This draft is a work item of the Source Packet Routing in Networking WG of the IETF.

            Title           : SRv6 Network Programming
            Authors         : Clarence Filsfils
                              Pablo Camarillo Garvia
                              John Leddy
                              Daniel Voyer
                              Satoru Matsushima
                              Zhenbin Li
    Filename        : draft-ietf-spring-srv6-network-programming-03.txt
    Pages           : 42
    Date            : 2019-09-24

    Abstract:
       This document describes the SRv6 network programming concept and its
       most basic functions.



    The IETF datatracker status page for this draft is:
    https://datatracker.ietf.org/doc/draft-ietf-spring-srv6-network-programming/

    There are also htmlized versions available at:
    https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-03
    https://datatracker.ietf.org/doc/html/draft-ietf-spring-srv6-network-programming-03

    A diff from the previous version is available at:
    https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-srv6-network-programming-03


    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/

    _______________________________________________
    spring mailing list
    spring@ietf.org<mailto:spring@ietf.org>
    https://www.ietf.org/mailman/listinfo/spring


_______________________________________________
spring mailing list
spring@ietf.org<mailto:spring@ietf.org>
https://www.ietf.org/mailman/listinfo/spring