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

Bob Hinden <> Fri, 14 June 2019 17:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BBABC1206F1 for <>; Fri, 14 Jun 2019 10:55:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2qU2QcyBXOkl for <>; Fri, 14 Jun 2019 10:55:23 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::32b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 699EC120156 for <>; Fri, 14 Jun 2019 10:55:23 -0700 (PDT)
Received: by with SMTP id f17so642512wme.2 for <>; Fri, 14 Jun 2019 10:55:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0J2bQtW70odLD6J3d5Kt5EKCgOBz5zoSazlT38MvpoE=; b=S0moLCdTAk0pQGVxDrb1qV3PysRZkzAAurPTMbUS/BycjmniMRxt8UIKxGv+RIqfdG mb7ROyrB0w43kgqqL7bTFl4JN1F578fRkgoTfF/BpVt1yPLwQMCkxdkHLFobdZ2pvq8X ECgtJ2FvoK3Xq0BxKLAR4cm7gqGsBnwv13CYXtYKt2x6tum6TdKj/cP/EgD47Q8OmRzO F1Ht9KmIAAzG3jX3JxMUjzJNp7ootdoH1/+cmhYzAd/eaoI0UeoKRskHQa3e73qYOG9B fEXGyKKu4thKh8Se7OzIRrK/rO19YF3oseszxct9RTbtgIzklhHXzvjWz9SjitpOuz6B cRhA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0J2bQtW70odLD6J3d5Kt5EKCgOBz5zoSazlT38MvpoE=; b=q8rmxRoodsZVsbnSBzkit2md9cmfJt+tYguPeYmphHrhu7H9YVp6cZSRFeEg5mKo6Y T09o2YBZam0iuEQfEnfj43X6jy/Ae7VWl3H6HvC4e9uMJHA/MQ34F5k4W5liruBq9dwR MQ/9sFk5BqvllcW4rNbxwmeJHjPX2Qha20Rujz8qPgI9qjYoH6HTGzirfQQfPFCuNwe7 blMnBmPVb0xzU9EUd5QXLDz7RdbhE2hNGUAfKrwIBt7a9eja4W5uSf36Dhbs8y6tO7zX I5YsROFynrhqpId3eaWrS3SzvrEmOTKf10+Vrn9fxKTHKj9C3WKOyefQzDpT5/SmYMHu xQWg==
X-Gm-Message-State: APjAAAXSWXjZE/9x/JyAP6jzQL2LSVc0BozK3Mwf9WxIL2hj6S6hY2ZQ 0c7Qj+1N9J+7SDKfxovoqEps8aj4
X-Google-Smtp-Source: APXvYqy6kjcVnelKkCjwLtyJXpwZAJx1R3aHDsbJ2/W5iCGrGQGbHGH67pMJJYJZQCKpCRYXKivjeg==
X-Received: by 2002:a1c:cc02:: with SMTP id h2mr8696348wmb.13.1560534921706; Fri, 14 Jun 2019 10:55:21 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:ef0b:7807:139f:e865:ab47? ([2601:647:5a00:ef0b:7807:139f:e865:ab47]) by with ESMTPSA id o11sm3459368wmh.37.2019. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 14 Jun 2019 10:55:21 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Conclusion of 6man w.g. last call for <draft-ietf-6man-segment-routing-header-19.txt>
From: Bob Hinden <>
In-Reply-To: <>
Date: Fri, 14 Jun 2019 10:55:15 -0700
Cc: =?utf-8?Q?Ole_Tr=C3=B8an?= <>, Bob Hinden <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <>
To: IPv6 List <>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 14 Jun 2019 17:55:26 -0000

The 6man chairs believe there is a consensus to advance draft-ietf-6man-segment-routing-header-21.txt to the IESG to be published as a Proposed Standard.

It’s been a long road to get here.  Two working group last calls, many presentations at 6man IETF sessions, and countless emails on the list.   We think that the current document (-21) is significantly improved based on discussion on the list and resolves the issues raised.   The changes since -19 include:


 - Updates the mutability text in section 2 as discussed on the list.
 - Changed pad0 to pad1
 - Updates the TLV type registry definition for IANA (pending verification)
 - Changed “SID Type” to “SID”.
 - Changed TLV mutability text to align with RFC8200.


 - Added request to IANA considerations section for ICMP “SR Upper-layer
   Header Error and a request for ICMPv6 Parameter Problem error
   code assignment.
 - Removed reservations of TLV types 3 and 6 for opaque and NSH TLVs based
   on draft-xuclad-spring-sr-service-programming.  That draft requires new
   allocations in the mutable range for TLV types, the authors realized
   the current values won’t be usable any longer.
 - Changed TLV type in IANA Considerations for Type 3 and 6 to Reserved

We think the 6MAN consensus is strong to advance, but clearly not unanimous.  

We plan to submit the shepherd's writeup and advance the document in the next few days.  Like all  documents we request for advancement, it will undergo AD review, then an IETF Last call, IESG directorate reviews, and AD reviews, followed by an IESG teleconference ballot.   

We want to thank the 6man working for all of the feedback on this draft and the authors for resolving the issues.

Bob & Ole

> On May 22, 2019, at 6:39 AM, Bob Hinden <> wrote:
> 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
> 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