RE: Call for adoption: <draft-krishnan-6man-sids-00>

"john leddy.net" <john@leddy.net> Mon, 04 April 2022 16:58 UTC

Return-Path: <john@leddy.net>
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 130DC3A0D84 for <ipv6@ietfa.amsl.com>; Mon, 4 Apr 2022 09:58:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 AWnBh-ueud9p for <ipv6@ietfa.amsl.com>; Mon, 4 Apr 2022 09:58:10 -0700 (PDT)
Received: from atl4mhob21.registeredsite.com (atl4mhob21.registeredsite.com [209.17.115.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0DC63A0D1D for <ipv6@ietf.org>; Mon, 4 Apr 2022 09:58:10 -0700 (PDT)
Received: from atl4oxapp110 ([10.30.71.182]) by atl4mhob21.registeredsite.com (8.14.4/8.14.4) with ESMTP id 234Gw7Oa193414 (version=TLSv1/SSLv3 cipher=AES256-SHA256 bits=256 verify=NO) for <ipv6@ietf.org>; Mon, 4 Apr 2022 12:58:07 -0400
Date: Mon, 04 Apr 2022 12:58:07 -0400
From: "john leddy.net" <john@leddy.net>
Reply-To: "john leddy.net" <john@leddy.net>
To: IPv6 List <ipv6@ietf.org>
Message-ID: <1332289213.23081.1649091487656@webmail.networksolutionsemail.com>
In-Reply-To: <B38A4359-CB0F-4FFE-8330-D6A126E31AAC@bell.ca>
References: <92790B16-19F8-40AD-BF8B-F9CBB619EE37@gmail.com> <B38A4359-CB0F-4FFE-8330-D6A126E31AAC@bell.ca>
Subject: RE: Call for adoption: <draft-krishnan-6man-sids-00>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.2-Rev26
X-Originating-Client: open-xchange-appsuite
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/8gBmbStSotnm1HkeMHlydTUeX9s>
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, 04 Apr 2022 16:58:13 -0000

I support the adoption of draft-krishnan-6man-sids-00

John


> 
> On 2022-03-30, 4:31 PM, "ipv6 on behalf of Bob Hinden" <ipv6-bounces@ietf.org on behalf of bob.hinden@gmail.com> wrote:
> 
>     This message starts a two week 6MAN call on adopting:
> 
>        Title:          Segment Identifiers in SRv6
>        Authors:        S. Krishnan
>        File Name:      draft-krishnan-6man-sids-00
>        Document date:  February 10, 2022
> 
>        https://datatracker.ietf.org/doc/html/draft-krishnan-6man-sids-00
> 
>     as a 6MAN working group document.
> 
>     For background this draft was the result a query to the 6MAN working group from the SPRING w.g. chairs regarding regarding draft-filsfilscheng-spring-srv6-srh-compression.  The query was:
> 
>       https://mailarchive.ietf.org/arch/msg/ipv6/5IpkHf5tVa-G4sKca-EWGEziYSo/
> 
>     After an active discussion, the reply from the 6MAN chairs and ADs was:
> 
>       https://mailarchive.ietf.org/arch/msg/ipv6/rGgpWZyPaKonLaeuT37D7qZ1Vcw/
> 
>     This topic was also presented at IETF 112, slides here:
> 
>       https://datatracker.ietf.org/meeting/112/materials/slides-112-6man-srv6-sids-00
> 
>     Substantive comments and statements of support for adopting this document should be sent to the mailing list.  Editorial suggestions can be sent to the author.  This adoption call will end on 13 April 2022.
> 
>     Further, if you are willing to work on this document, either as contributor, author, or reviewer please notify the list.   This will provide the chairs with an indication of the energy level in the working group to work on this document.
> 
>     Bob, Jen, Ole
> 
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------