[Idr] draft-ietf-idr-tunnel-encaps

<bruno.decraene@orange.com> Tue, 26 November 2019 15:38 UTC

Return-Path: <bruno.decraene@orange.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 3D5D9120942; Tue, 26 Nov 2019 07:38:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.49
X-Spam-Status: No, score=-1.49 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, LOCALPART_IN_SUBJECT=1.107, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id ICUaqbHRzoZ8; Tue, 26 Nov 2019 07:38:03 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C223C12093A; Tue, 26 Nov 2019 07:38:02 -0800 (PST)
Received: from opfedar01.francetelecom.fr (unknown [xx.xx.xx.2]) by opfedar22.francetelecom.fr (ESMTP service) with ESMTP id 47Mp2K1RG7z2xRw; Tue, 26 Nov 2019 16:38:01 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.104]) by opfedar01.francetelecom.fr (ESMTP service) with ESMTP id 47Mp2K08bRzBrLb; Tue, 26 Nov 2019 16:38:01 +0100 (CET)
Received: from OPEXCAUBM43.corporate.adroot.infra.ftgroup ([fe80::b846:2467:1591:5d9d]) by OPEXCAUBM5F.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0468.000; Tue, 26 Nov 2019 16:38:00 +0100
From: <bruno.decraene@orange.com>
To: "draft-ietf-idr-tunnel-encaps@ietf.org" <draft-ietf-idr-tunnel-encaps@ietf.org>
CC: idr wg <idr@ietf.org>, John Scudder <jgs=40juniper.net@dmarc.ietf.org>, Alvaro Retana <aretana.ietf@gmail.com>
Thread-Topic: draft-ietf-idr-tunnel-encaps
Thread-Index: AdWkbffsrLIMj4YkS+S+IQcrwqTqKQ==
Date: Tue, 26 Nov 2019 15:38:00 +0000
Message-ID: <16327_1574782681_5DDD46D9_16327_358_1_53C29892C857584299CBF5D05346208A48D0BCB7@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A48D0BCB7OPEXCAUBM43corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Cw2tBmlWIZuSq1qeqGype3CA99E>
Subject: [Idr] draft-ietf-idr-tunnel-encaps
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Nov 2019 15:38:05 -0000

Hi authors,
Cc'ing John and Alvaro as the document has left IDR WG.

TL;DR: I think that you should remove "an "IPv6 SID (Segment Identifier)" TLV,"

https://tools.ietf.org/html/draft-ietf-idr-tunnel-encaps-14#section-3.7 says:

   [I-D.ietf-idr-bgp-prefix-sid] defines a BGP Path attribute known as
   the "Prefix-SID Attribute".  This attribute is defined to contain a
   sequence of one or more TLVs, where each TLV is either a "Label-
   Index" TLV, an "IPv6 SID (Segment Identifier)" TLV, or an "Originator
   SRGB (Source Routing Global Block)" TLV.

Actually latest version of [I-D.ietf-idr-bgp-prefix-sid] has removed the support for "IPv6 SID (Segment Identifier)" TLV

The value 2 previously corresponded to the IPv6 SID TLV which was

   specified in previous versions of this document.  It was removed and

   usage of the BGP Prefix-SID for Segment Routing over the IPv6

   dataplane [I-D.ietf-spring-segment-routing<https://tools.ietf.org/html/draft-ietf-idr-bgp-prefix-sid-27#ref-I-D.ietf-spring-segment-routing>] has been deferred to

   future specifications.

Best regards,


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.