[LOOPS] Fw: New Version Notification for draft-wang-loops-srv6-binding-00.txt

wangjl50 <wangjl50@chinatelecom.cn> Fri, 13 March 2020 02:18 UTC

HMM_SOURCE_IP: 172.18.0.48:46842.1742731250
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-123.116.101.129?logid-B488FDBC19494F1EB258C5E80F588AF7 (unknown [172.18.0.48]) by chinatelecom.cn (HERMES) with SMTP id 747172800D2; Fri, 13 Mar 2020 10:18:05 +0800 (CST)
X-189-SAVE-TO-SEND: 71069678@chinatelecom.cn
Received: from ([172.18.0.48]) by App0024 with ESMTP id B488FDBC19494F1EB258C5E80F588AF7 for loops@ietf.org; Fri Mar 13 10:18:11 2020
X-Transaction-ID: B488FDBC19494F1EB258C5E80F588AF7
X-filter-score: filter<0>
X-Real-From: wangjl50@chinatelecom.cn
X-Receive-IP: 172.18.0.48
X-MEDUSA-Status: 0
Date: Fri, 13 Mar 2020 10:18:04 +0800
From: wangjl50 <wangjl50@chinatelecom.cn>
To: loops <loops@ietf.org>
Cc: spring <spring@ietf.org>, leibo <leibo@chinatelecom.cn>, nieshzh <nieshzh@chinatelecom.cn>, cabo <cabo@tzi.org>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.12.322[cn]
Mime-Version: 1.0
Message-ID: <202003130753199584443@chinatelecom.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart005022781265_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/loops/TyX5IDnZ3n_37r8MfvnT4bahRnk>
Subject: [LOOPS] Fw: New Version Notification for draft-wang-loops-srv6-binding-00.txt
X-BeenThere: loops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Local Optimizations on Path Segments <loops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/loops>, <mailto:loops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/loops/>
List-Post: <mailto:loops@ietf.org>
List-Help: <mailto:loops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/loops>, <mailto:loops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2020 02:18:26 -0000

Hi all,

     We have uploaded a new draft which discusses the concrete mechanisms to embed LOOPS in SRv6 segment.
https://www.ietf.org/internet-drafts/draft-wang-loops-srv6-binding-00.txt 

Segment Routing (SR) uses source routing techniques to deliver the data through a pre-defined path and/or functions.  SRv6 (SR over IPv6) runs on best effort IPv6 network, and its segments suffer from different levels of packet loss. 
This draft is a binding of LOOPS to SRv6 encapsulation, it identifies how to embed LOOPS in SRv6 segment to perform in-network packet loss recovery.

Any questions and comments are welcome.
 
Thank you very much!
 
Best regards,
Jianglong Wang


From: internet-drafts
Date: 2020-03-10 00:48
To: Bo Lei; Lei Bo; Jianglong Wang; Jianglong; Carsten Bormann; Shizhong Nie
Subject: New Version Notification for draft-wang-loops-srv6-binding-00.txt
 
A new version of I-D, draft-wang-loops-srv6-binding-00.txt
has been successfully submitted by Carsten Bormann and posted to the
IETF repository.
 
Name: draft-wang-loops-srv6-binding
Revision: 00
Title: Embedding LOOPS in SRv6
Document date: 2020-03-09
Group: Individual Submission
Pages: 10
URL:            https://www.ietf.org/internet-drafts/draft-wang-loops-srv6-binding-00.txt
Status:         https://datatracker.ietf.org/doc/draft-wang-loops-srv6-binding/
Htmlized:       https://tools.ietf.org/html/draft-wang-loops-srv6-binding-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-wang-loops-srv6-binding
 
 
Abstract:
   LOOPS (Local Optimizations on Path Segments) aims to provide local
   in-network loss recovery.  It can be used with tunneling protocols to
   efficiently recover lost packets on a single segment of an end-to-end
   path instead of leaving recovery to the end-to-end protocol,
   traversing the entire path.
 
   Segment Routing (SR) leverages the source routing mechanisms and
   steers the packets through an policy instantiated as an ordered list
   of instructions called segments.  LOOPS can be embedded in an SR
   segment to improve the packet recovery. draft-welzl-loops-gen-info
   defines the generic information model, without binding that to any
   specific protocols, to be carried between LOOPS ingress and egress
   nodes, which can be SR segment endpoints.  This document specifies
   the concrete mechanisms to embed LOOPS in SRv6 segment.
 
                                                                                  
 
 
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

[LOOPS] Fw: New Version Notification for draft-wa… wangjl50