Re: [Idr] Working group last call for draft-ietf-idr-tunnel-encaps-04

<bruno.decraene@orange.com> Mon, 26 June 2017 08:47 UTC

Return-Path: <bruno.decraene@orange.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1C60129503; Mon, 26 Jun 2017 01:47:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.609
X-Spam-Level:
X-Spam-Status: No, score=-2.609 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, UNPARSEABLE_RELAY=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 0i4zPTzCS2I3; Mon, 26 Jun 2017 01:47:19 -0700 (PDT)
Received: from relais-inet.orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C60012955F; Mon, 26 Jun 2017 01:47:19 -0700 (PDT)
Received: from opfednr06.francetelecom.fr (unknown [xx.xx.xx.70]) by opfednr25.francetelecom.fr (ESMTP service) with ESMTP id B598B18034A; Mon, 26 Jun 2017 10:47:17 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.43]) by opfednr06.francetelecom.fr (ESMTP service) with ESMTP id 8BD351A006A; Mon, 26 Jun 2017 10:47:17 +0200 (CEST)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM5F.corporate.adroot.infra.ftgroup ([fe80::e172:f13e:8be6:71cc%18]) with mapi id 14.03.0352.000; Mon, 26 Jun 2017 10:47:17 +0200
From: bruno.decraene@orange.com
To: "draft-ietf-idr-tunnel-encaps@ietf.org" <draft-ietf-idr-tunnel-encaps@ietf.org>
CC: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] Working group last call for draft-ietf-idr-tunnel-encaps-04
Thread-Index: AQHS0aHw2gkF+4EIwk6O9LK6laxSJKIyXyZwgAStGKA=
Date: Mon, 26 Jun 2017 08:47:16 +0000
Message-ID: <10494_1498466837_5950CA15_10494_242_1_53C29892C857584299CBF5D05346208A477AC7BA@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <2AEDAB02-02F4-46C2-92CA-8880BBAFAAAB@juniper.net> <25760_1498215376_594CF3D0_25760_174_1_53C29892C857584299CBF5D05346208A477A7C7E@OPEXCLILM21.corporate.adroot.infra.ftgroup>
In-Reply-To: <25760_1498215376_594CF3D0_25760_174_1_53C29892C857584299CBF5D05346208A477A7C7E@OPEXCLILM21.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.3]
Content-Type: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A477AC7BAOPEXCLILM21corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/zIJ_-YCXM71ZAur51wEaz6wnTTk>
Subject: Re: [Idr] Working group last call for draft-ietf-idr-tunnel-encaps-04
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 26 Jun 2017 08:47:22 -0000

Hi Eric,



Please find below a possible typo in §2



   Each sub-TLV consists of three fields: a 1-octet type, 1-octet

   length, and zero or more octets of value.  A sub-TLV is structured as

   shown in Figure 2:



                   +-----------------------------------+

                   |      Sub-TLV Type (1 Octet)       |

                   +-----------------------------------+

                   |     Sub-TLV Length (1 or 2 Octets)|

                   +-----------------------------------+

                   |     Sub-TLV Value (Variable)      |

                   |                                   |

                   +-----------------------------------+



               Figure 2: Tunnel Encapsulation Sub-TLV Format





OLD : 1-octet length,

NEW : 1-octet or 2-octets length,



Thanks,

Best regards,

--Bruno



> -----Original Message-----

> From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of bruno.decraene@orange.com

> Sent: Friday, June 23, 2017 12:56 PM

> To: draft-ietf-idr-tunnel-encaps@ietf.org

> Cc: idr@ietf.org

> Subject: Re: [Idr] Working group last call for draft-ietf-idr-tunnel-encaps-04

>

 > Hi Eric,

>

 > I wouldn't said that I have reviewed the document (-06), nor the discussion, but section

> 3.3.1 " IPv4 DS Field" seems IPv4 specific and we probably need to also cover IPv6. Possibly,

> the same sub-TLV may be used.

> In addition, there is the IPv6 flow label, but I don't know whether it would be useful to

> specify it or not.

>

 > Thanks,

> Regards,

> --Bruno

>

 > > From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of John G. Scudder

> >

>  > Hi All,

>  >

>  > A working group last call has been requested for draft-ietf-idr-tunnel-encaps-04. Please

>  > reply to the list with your comments. As usual note we cannot advance the draft without

>  > participation from the group. Please get your comments in before June 5, 2017.

>  >

>  > Authors, please confirm that any relevant IPR has been disclosed.

>  >

>  > https://tools.ietf.org/html/draft-ietf-idr-tunnel-encaps-04

>  >

>  > Thanks,

>  >

>  > --John

>  > _______________________________________________

>  > Idr mailing list

>  > Idr@ietf.org<mailto:Idr@ietf.org>

>  > https://www.ietf.org/mailman/listinfo/idr

>

 > _____________________________________________________________________________

> ____________________________________________

>

 > 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.

>

 > _______________________________________________

> Idr mailing list

> Idr@ietf.org<mailto:Idr@ietf.org>

> https://www.ietf.org/mailman/listinfo/idr

_________________________________________________________________________________________________________________________

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.