RE: 6man w.g. last call for <draft-ietf-6man-segment-routing-header-19.txt>

<mohamed.boucadair@orange.com> Mon, 27 May 2019 09:02 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7021312004B for <ipv6@ietfa.amsl.com>; Mon, 27 May 2019 02:02:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, 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 cCTDidf_1Nqq for <ipv6@ietfa.amsl.com>; Mon, 27 May 2019 02:02:38 -0700 (PDT)
Received: from orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25E2E12003E for <ipv6@ietf.org>; Mon, 27 May 2019 02:02:38 -0700 (PDT)
Received: from opfedar07.francetelecom.fr (unknown [xx.xx.xx.9]) by opfedar23.francetelecom.fr (ESMTP service) with ESMTP id 45C9wX0hlzzBsZ9; Mon, 27 May 2019 11:02:36 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.86]) by opfedar07.francetelecom.fr (ESMTP service) with ESMTP id 45C9wW6xKTz5vP8; Mon, 27 May 2019 11:02:35 +0200 (CEST)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBMA4.corporate.adroot.infra.ftgroup ([fe80::4538:d7b0:3c64:8ed3%22]) with mapi id 14.03.0439.000; Mon, 27 May 2019 11:02:35 +0200
From: mohamed.boucadair@orange.com
To: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
Subject: RE: 6man w.g. last call for <draft-ietf-6man-segment-routing-header-19.txt>
Thread-Topic: 6man w.g. last call for <draft-ietf-6man-segment-routing-header-19.txt>
Thread-Index: AQHVEKPnN+YPM/37/0qu2E2QlucJZ6Z+s4Ew
Date: Mon, 27 May 2019 09:02:34 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302EA8F6B2@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <588C586F-C303-418E-8D26-477C4B37CF92@gmail.com>
In-Reply-To: <588C586F-C303-418E-8D26-477C4B37CF92@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/sndPjctYoujctupAVIRoVKgdF74>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2019 09:02:41 -0000

Hi Bob, all,

I do still don't understand the intent of this field:  

   o  Tag: tag a packet as part of a class or group of packets, e.g.,
      packets sharing the same set of properties.  When tag is not used
      at source it MUST be set to zero on transmission.  When tag is not
      used during SRH Processing it SHOULD be ignored.  Tag is not used
      when processing the SID defined in Section 4.3.1.  It may be used
      when processing other SID types which are not defined in this
      document.  The allocation and use of tag is outside the scope of
      this document.

In the absence of a clear definition of this field, it is better to set these bits as unassigned. 

Cheers,
Med

> -----Message d'origine-----
> De : ipv6 [mailto:ipv6-bounces@ietf.org] De la part de Bob Hinden
> Envoyé : mercredi 22 mai 2019 15:40
> À : IPv6 List
> Cc : Bob Hinden
> Objet : 6man w.g. last call for <draft-ietf-6man-segment-routing-header-
> 19.txt>
> 
> Hello,
> 
> This message starts a new two week 6MAN Working Group Last Call on
> advancing:
> 
>        Title           : IPv6 Segment Routing Header (SRH)
>        Authors         : Clarence Filsfils
>                          Darren Dukes
>                          Stefano Previdi
>                          John Leddy
>                          Satoru Matsushima
>                          Daniel Voyer
> 	Filename        : draft-ietf-6man-segment-routing-header-19.txt
> 	Pages           : 32
> 	Date            : 2019-05-21
> 
>     https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header
> 
> as a Proposed Standard.
> 
> This document was in an extended last call that started in March of 2018.
> An issue tracker was set up, and eight new versions of the draft were
> produced and discussed on the list and at face to face 6man sessions.
> All of the issues in the tracker have been closed.  The chairs believe it
> is ready to advance, but given the number of changes and the time that
> elapsed, a new w.g. last call is warranted.  Please review the new
> document.
> 
> Our thanks to the authors/editors and the working group for the work on
> this document.
> 
> Substantive comments and statements of support for publishing this
> document should be directed to the mailing list. Editorial suggestions can
> be sent to the author.  This last call will
> end on 5 June 2019.
> 
> Thanks,
> Bob & Ole
> 
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------