Re: [spring] https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-04#page-24

2019-10-21 Thread Ron Bonica
Ketan,

Previously in this thread, we have agreed on the following:


  *   PSP and USP operate upon SRH with SL equal to zero
  *   SRH with SL equal to zero is a functional NOOP

Because SRH with SL equal to zero is a functional  NOOP, there is limited value 
is  special operations that removes it.

Currently, there is an unresolved issue regarding whether a transit node can 
insert or remove extension headers in flight. As a result of that argument, 
END.B6.INSERT and T.INSERT have been moved to a separate document. You might 
want to move PSP and USP to that same document for the following reasons:


  *   Moving PSP and USP will allow the network programming draft to progress 
before the larger issue of extension header insertion and removal is resolved
  *   Moving PSP and USP will prevent the network programming draft from being 
delayed over a functional NOOP.


Ron




Juniper Business Use Only
From: Ketan Talaulikar (ketant) 
Sent: Saturday, October 19, 2019 12:22 AM
To: Rajesh M ; Rajesh M 
; Wang, Weibin (NSB - CN/Shanghai) 
; Pablo Camarillo (pcamaril) ; 
SPRING WG List ; Peter Psenak (ppsenak) 
Cc: Srihari Sangli ; Shraddha Hegde 
; Ron Bonica 
Subject: RE: [spring] 
https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-04#page-24

Hi Rajesh,

T.insert is definitely not deprecated. Please check 
https://mailarchive.ietf.org/arch/msg/spring/zRwYRZrKEwzMor2cXpYiag--_y0
 - I would suggest you go through the archives to get the history/context.

In fact, it is already deployed - check 
https://tools.ietf.org/html/draft-matsushima-spring-srv6-deployment-status-02

Thanks,
Ketan

From: Rajesh M mailto:mraj...@juniper.net>>
Sent: 19 October 2019 09:34
To: Rajesh M 
mailto:mrajesh=40juniper@dmarc.ietf.org>>;
 Wang, Weibin (NSB - CN/Shanghai) 
mailto:weibin.w...@nokia-sbell.com>>; Pablo 
Camarillo (pcamaril) mailto:pcama...@cisco.com>>; SPRING WG 
List mailto:spring@ietf.org>>; Peter Psenak (ppsenak) 
mailto:ppse...@cisco.com>>; Ketan Talaulikar (ketant) 
mailto:ket...@cisco.com>>
Cc: Srihari Sangli mailto:ssan...@juniper.net>>; Shraddha 
Hegde mailto:shrad...@juniper.net>>; Ron Bonica 
mailto:rbon...@juniper.net>>
Subject: RE: [spring] 
https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-04#page-24


if we use T.Insert Mode for TI-LFA then PSP and USP Flavours are useful.



T.insert mode is  deprecated ? if Yes then PSP and USP Flavours also must be 
deprecated as per me.



Thanks

Rajesh







Juniper Business Use Only
From: Rajesh M 
mailto:mrajesh=40juniper@dmarc.ietf.org>>
Sent: Saturday, October 19, 2019 7:59 AM
To: Wang, Weibin (NSB - CN/Shanghai) 
mailto:weibin.w...@nokia-sbell.com>>; Rajesh M 
mailto:mraj...@juniper.net>>; Pablo Camarillo (pcamaril) 
mailto:pcama...@cisco.com>>; SPRING WG List 
mailto:spring@ietf.org>>
Cc: Srihari Sangli mailto:ssan...@juniper.net>>; Shraddha 
Hegde mailto:shrad...@juniper.net>>; Ron Bonica 
mailto:rbon...@juniper.net>>
Subject: RE: [spring] 
https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-04#page-24

MPLS world PSP will help in avoiding one more lookup at egress for VPN cases.

I feel both PSP and USP are not useful in case of SRV6.



Juniper Business Use Only
From: Wang, Weibin (NSB - CN/Shanghai) 
mailto:weibin.w...@nokia-sbell.com>>
Sent: Saturday, October 19, 2019 6:26 AM
To: Rajesh M mailto:mraj...@juniper.net>>; Rajesh M 
mailto:mrajesh=40juniper@dmarc.ietf.org>>;
 Pablo Camarillo (pcamaril) mailto:pcama...@cisco.com>>; 
SPRING WG List mailto:spring@ietf.org>>
Cc: Srihari Sangli mailto:ssan...@juniper.net>>; Shraddha 
Hegde mailto:shrad...@juniper.net>>
Subject: RE: [spring] 
https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-04#page-24

Hi Rajesh:
The answer to your question, I think, had better be provided by Authors of 
NET-PGM, You can also refer to Ron’s email previously one or two days before 
who give some guess, I think it make sense, in addition , also including 
processing-load mitigation in Last hop (egress PE);
Could you Pls explain the benefit of similar behavior in PHP of MPLS world.  I 
think it may be same.


[spring] 答复: Request for WG adoption of draft-dong-spring-sr-for-enhanced-vpn-05

2019-10-21 Thread qinfengwei
WG,
I support the adoption poll as a co-author.
I have reviewed this doc, my comments have been addressed and I think it is
mature enough to be a working group doc.



Thanks,
Fengwei Qin

-邮件原件-
发件人: spring [mailto:spring-boun...@ietf.org] 代表 Dongjie (Jimmy)
发送时间: 2019年10月21日 13:22
收件人: 'SPRING WG List'
抄送: spring-cha...@ietf.org
主题: [spring] Request for WG adoption of
draft-dong-spring-sr-for-enhanced-vpn-05

Dear WG and Chairs, 

A new revision of draft-dong-spring-sr-for-enhanced-vpn has been uploaded to
resolve some recently received comments. This document describes the Segment
Routing based mechanism to provide enhanced VPN, which aligns with the
enhanced VPN (VPN)+ framework document in TEAS WG. The mechanism could be
used to enable transport network slicing for 5G.

The major changes compared to the -04 version are:

  1. Update the draft template. 

  2. Add reference to the definition of network slicing in 3GPP TS23.501 and
the definition of transport network slicing in
draft-ietf-teas-enhanced-vpn-03 respectively.

  3. Editorial changes in several sections to clarify and improve the
readability.

  4. Change some coauthors' affiliation and mail address.

This update shows that the major content of this draft has become stable and
solid, thus the authors would like to request the WG to consider the
adoption of this document. 

Comments are always welcome. Thanks.

Best regards,
Jie

-Original Message-
From: internet-dra...@ietf.org [mailto:internet-dra...@ietf.org] 
Sent: Wednesday, October 16, 2019 3:28 PM
To: Takuya Miyasaka ; Zhenqiang Li
; Fengwei Qin ;
Stewart Bryant ; Yongqing Zhu
; Dongjie (Jimmy) 
Subject: New Version Notification for
draft-dong-spring-sr-for-enhanced-vpn-05.txt


A new version of I-D, draft-dong-spring-sr-for-enhanced-vpn-05.txt
has been successfully submitted by Jie Dong and posted to the IETF
repository.

Name:   draft-dong-spring-sr-for-enhanced-vpn
Revision:   05
Title:  Segment Routing for Enhanced VPN Service
Document date:  2019-10-16
Group:  Individual Submission
Pages:  20
URL:
https://www.ietf.org/internet-drafts/draft-dong-spring-sr-for-enhanced-vpn-0
5.txt
Status:
https://datatracker.ietf.org/doc/draft-dong-spring-sr-for-enhanced-vpn/
Htmlized:
https://tools.ietf.org/html/draft-dong-spring-sr-for-enhanced-vpn-05
Htmlized:
https://datatracker.ietf.org/doc/html/draft-dong-spring-sr-for-enhanced-vpn
Diff:
https://www.ietf.org/rfcdiff?url2=draft-dong-spring-sr-for-enhanced-vpn-05

Abstract:
   Enhanced VPN (VPN+) is an enhancement to VPN services to enable it to
   support the needs of new applications, particularly applications that
   are associated with 5G services.  These applications require better
   isolation from both control and data plane's perspective and have
   more stringent performance requirements than can be provided with
   overlay VPNs.  The characteristics of an enhanced VPN as perceived by
   its tenant needs to be comparable to those of a dedicated private
   network.  This requires tight integration between the overlay VPN and
   the underlay network topology and resources in a scalable manner.  An
   enhanced VPN may form the underpinning of 5G network slicing, but
   will also be of use in its own right.  This document describes how to
   use segment routing based mechanisms to provide the enhanced VPN
   service with the required network topology and resources.  The
   overall mechanism of providing segment routing based enhanced VPN
   service is also described.  The proposed mechanism is applicable to
   both segment routing with MPLS data plane (SR-MPLS) and segment
   routing with IPv6 data plane (SRv6).


 



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.

The IETF Secretariat

___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring



___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring


Re: [spring] Request for WG adoption of draft-dong-spring-sr-for-enhanced-vpn-05

2019-10-21 Thread Xiejingrong (Jingrong)
I support the adoption of this document.

It is well-written, and I think it is very timely and useful, as the SR being 
widely developed and the requirements for enhanced VPN services being strong.

Thanks
Jingrong

-Original Message-
From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Loa Andersson
Sent: Monday, October 21, 2019 6:33 PM
To: spring@ietf.org
Cc: Dongjie (Jimmy) ; spring-cha...@ietf.org; li zhenqiang 

Subject: Re: [spring] Request for WG adoption of 
draft-dong-spring-sr-for-enhanced-vpn-05

WG,

I reviewed this document before the last version, my comments have been 
addressed and I think this is ready for adoption as a working grouo document.

/Loa

On 2019-10-21 12:16, li zhenqiang wrote:
> Hello all and chairs,
> 
> I support the adoption poll as a co-author. I believe the doc is 
> mature enough to be a wg item.
> 
> Best Regards,
> Zhenqiang Li
> --
> --
> li_zhenqi...@hotmail.com
> 
> *From:* Dongjie (Jimmy) 
> *Date:* 2019-10-21 13:21
> *To:* 'SPRING WG List' 
> *CC:* spring-cha...@ietf.org 
> *Subject:* [spring] Request for WG adoption of
> draft-dong-spring-sr-for-enhanced-vpn-05
> Dear WG and Chairs,
> A new revision of draft-dong-spring-sr-for-enhanced-vpn has been
> uploaded to resolve some recently received comments. This document
> describes the Segment Routing based mechanism to provide enhanced
> VPN, which aligns with the enhanced VPN (VPN)+ framework document in
> TEAS WG. The mechanism could be used to enable transport network
> slicing for 5G.
> The major changes compared to the -04 version are:
>    1. Update the draft template.
>    2. Add reference to the definition of network slicing in 3GPP
> TS23.501 and the definition of transport network slicing in
> draft-ietf-teas-enhanced-vpn-03 respectively.
>    3. Editorial changes in several sections to clarify and improve
> the readability.
>    4. Change some coauthors' affiliation and mail address.
> This update shows that the major content of this draft has become
> stable and solid, thus the authors would like to request the WG to
> consider the adoption of this document.
> Comments are always welcome. Thanks.
> Best regards,
> Jie
> -Original Message-
> From: internet-dra...@ietf.org [mailto:internet-dra...@ietf.org]
> Sent: Wednesday, October 16, 2019 3:28 PM
> To: Takuya Miyasaka ; Zhenqiang Li
> ; Fengwei Qin
> ; Stewart Bryant
> ; Yongqing Zhu ;
> Dongjie (Jimmy) 
> Subject: New Version Notification for
> draft-dong-spring-sr-for-enhanced-vpn-05.txt
> A new version of I-D, draft-dong-spring-sr-for-enhanced-vpn-05.txt
> has been successfully submitted by Jie Dong and posted to the IETF
> repository.
> Name: draft-dong-spring-sr-for-enhanced-vpn
> Revision: 05
> Title: Segment Routing for Enhanced VPN Service
> Document date: 2019-10-16
> Group: Individual Submission
> Pages: 20
> URL:   
> 
> https://www.ietf.org/internet-drafts/draft-dong-spring-sr-for-enhanced-vpn-05.txt
> Status:
> https://datatracker.ietf.org/doc/draft-dong-spring-sr-for-enhanced-vpn/
> Htmlized:  
> https://tools.ietf.org/html/draft-dong-spring-sr-for-enhanced-vpn-05
> Htmlized:  
> 
> https://datatracker.ietf..org/doc/html/draft-dong-spring-sr-for-enhanced-vpn
> Diff:  
> https://www.ietf.org/rfcdiff?url2=draft-dong-spring-sr-for-enhanced-vpn-05
> Abstract:
>     Enhanced VPN (VPN+) is an enhancement to VPN services to enable
> it to
>     support the needs of new applications, particularly applications
> that
>     are associated with 5G services.  These applications require better
>     isolation from both control and data plane's perspective and have
>     more stringent performance requirements than can be provided with
>     overlay VPNs.  The characteristics of an enhanced VPN as
> perceived by
>     its tenant needs to be comparable to those of a dedicated private
>     network.  This requires tight integration between the overlay
> VPN and
>     the underlay network topology and resources in a scalable
> manner.  An
>     enhanced VPN may form the underpinning of 5G network slicing, but
>     will also be of use in its own right.  This document describes
> how to
>     use segment routing based mechanisms to provide the enhanced VPN
>     service with the required network topology and resources.  The
>     overall mechanism of providing segment routing based enhanced VPN
>     service is also described.  The proposed mechanism is applicable to
>     both segment routing with MPLS data plane (SR-MPLS) and segment
>  

Re: [spring] Request for WG adoption of draft-dong-spring-sr-for-enhanced-vpn-05

2019-10-21 Thread Loa Andersson

WG,

I reviewed this document before the last version, my comments have been
addressed and I think this is ready for adoption as a working grouo
document.

/Loa

On 2019-10-21 12:16, li zhenqiang wrote:

Hello all and chairs,

I support the adoption poll as a co-author. I believe the doc is mature 
enough to be a wg item.


Best Regards,
Zhenqiang Li

li_zhenqi...@hotmail.com

*From:* Dongjie (Jimmy) 
*Date:* 2019-10-21 13:21
*To:* 'SPRING WG List' 
*CC:* spring-cha...@ietf.org 
*Subject:* [spring] Request for WG adoption of
draft-dong-spring-sr-for-enhanced-vpn-05
Dear WG and Chairs,
A new revision of draft-dong-spring-sr-for-enhanced-vpn has been
uploaded to resolve some recently received comments. This document
describes the Segment Routing based mechanism to provide enhanced
VPN, which aligns with the enhanced VPN (VPN)+ framework document in
TEAS WG. The mechanism could be used to enable transport network
slicing for 5G.
The major changes compared to the -04 version are:
   1. Update the draft template.
   2. Add reference to the definition of network slicing in 3GPP
TS23.501 and the definition of transport network slicing in
draft-ietf-teas-enhanced-vpn-03 respectively.
   3. Editorial changes in several sections to clarify and improve
the readability.
   4. Change some coauthors' affiliation and mail address.
This update shows that the major content of this draft has become
stable and solid, thus the authors would like to request the WG to
consider the adoption of this document.
Comments are always welcome. Thanks.
Best regards,
Jie
-Original Message-
From: internet-dra...@ietf.org [mailto:internet-dra...@ietf.org]
Sent: Wednesday, October 16, 2019 3:28 PM
To: Takuya Miyasaka ; Zhenqiang Li
; Fengwei Qin
; Stewart Bryant
; Yongqing Zhu ;
Dongjie (Jimmy) 
Subject: New Version Notification for
draft-dong-spring-sr-for-enhanced-vpn-05.txt
A new version of I-D, draft-dong-spring-sr-for-enhanced-vpn-05.txt
has been successfully submitted by Jie Dong and posted to the IETF
repository.
Name: draft-dong-spring-sr-for-enhanced-vpn
Revision: 05
Title: Segment Routing for Enhanced VPN Service
Document date: 2019-10-16
Group: Individual Submission
Pages: 20
URL:   
https://www.ietf.org/internet-drafts/draft-dong-spring-sr-for-enhanced-vpn-05.txt
Status:
https://datatracker.ietf.org/doc/draft-dong-spring-sr-for-enhanced-vpn/
Htmlized:  
https://tools.ietf.org/html/draft-dong-spring-sr-for-enhanced-vpn-05
Htmlized:  
https://datatracker.ietf..org/doc/html/draft-dong-spring-sr-for-enhanced-vpn
Diff:  
https://www.ietf.org/rfcdiff?url2=draft-dong-spring-sr-for-enhanced-vpn-05

Abstract:
    Enhanced VPN (VPN+) is an enhancement to VPN services to enable
it to
    support the needs of new applications, particularly applications
that
    are associated with 5G services.  These applications require better
    isolation from both control and data plane's perspective and have
    more stringent performance requirements than can be provided with
    overlay VPNs.  The characteristics of an enhanced VPN as
perceived by
    its tenant needs to be comparable to those of a dedicated private
    network.  This requires tight integration between the overlay
VPN and
    the underlay network topology and resources in a scalable
manner.  An
    enhanced VPN may form the underpinning of 5G network slicing, but
    will also be of use in its own right.  This document describes
how to
    use segment routing based mechanisms to provide the enhanced VPN
    service with the required network topology and resources.  The
    overall mechanism of providing segment routing based enhanced VPN
    service is also described.  The proposed mechanism is applicable to
    both segment routing with MPLS data plane (SR-MPLS) and segment
    routing with IPv6 data plane (SRv6).
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.
The IETF Secretariat
___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring


___
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring



--


Loa Anderssonemail: l...@pi.nu
Senior MPLS Expert
Bronze Dragon Consulting phone: +46 739 81 21 64

___
spring mailing list