Re: [spring] draft-ietf-spring-srv6-network-programming - 2 week Early Allocation Call

Gyan Mishra <hayabusagsm@gmail.com> Sat, 04 January 2020 04:15 UTC

Return-Path: <hayabusagsm@gmail.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02D35120103 for <spring@ietfa.amsl.com>; Fri, 3 Jan 2020 20:15:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, HTML_MESSAGE=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: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 W5uV1NWS8mvK for <spring@ietfa.amsl.com>; Fri, 3 Jan 2020 20:15:46 -0800 (PST)
Received: from mail-il1-x132.google.com (mail-il1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AB16120020 for <spring@ietf.org>; Fri, 3 Jan 2020 20:15:46 -0800 (PST)
Received: by mail-il1-x132.google.com with SMTP id t8so38259523iln.4 for <spring@ietf.org>; Fri, 03 Jan 2020 20:15:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eK1u9JfFp36WGfiUyz7FdhfsnoxWLY/qYtIHLcM48Vo=; b=gIr73snxLSlNNlcKz9j0quUW/JvymFDF3R67jPJYUqG6UrUy9X6Owxuhit4GA/EjC3 UmRpztf3Xyt6LEzNGblpQDweuRkwx9AQM1+EV6mpP8i1bqf/+LSJn5Quu5ZJHVmk9TaJ ne/gCB61hGzvlM7wsuIZnMzx3P8Yc+LozXvjT0b8ZZfyXv9/TExzZhoGyNR2OEIB19GF sVJFE9AuIVBHX15huNuCJLcji8sYh2sjeAE30sEJwEDh4e30jOcZhn2vzUwaUDOKi7dP RlYz9C2Q3tpA2H91iw92YXNA1zo+en4iEVfN5CdfVytI8ItRNfIvGd4j438Smq2SEXu1 ytVw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eK1u9JfFp36WGfiUyz7FdhfsnoxWLY/qYtIHLcM48Vo=; b=Ph8C1hjZA4IG0SWnDkGxAxXYkdjkTk7uyXOovg3cqnIgJRHI70HFdH1lCcI+6RZ2KQ fCCo+/TD/aOMzGRJPNlILGp4gFIdqbrGCxPLdS6j/H+sUeYGWp1AE+q/V68c3oMR/hOY yG2QffivgYXbdxqo4Qb5cOSrUzdlQfOyO+/mf+Ledo/CSoilZEQSYk+z+ZeCpk8TsdYM tX/oZZ+4ELfFcecagRElLj32lx9oESp7j6F9lXH5gdVxmNE3X7ciKUzUZxp5EPcOdY5q VRF8QYeqShwZ8ZxSh6Tidc+WpoOZb8OJ+sGfedELAjofbiIecOBG8Tkb5tcs0905WVRQ 8IsQ==
X-Gm-Message-State: APjAAAVbjRn1rC3TO+F7PB4psmRBs9IzpwV/W/dHK2rrg9dKLImxb6ZC 3gdQYYZLlfRdzXlMhsbLwHJSr1jsqHfOU+5zEuA=
X-Google-Smtp-Source: APXvYqxZYHLqU1acdIM7axanxikYlywL6JB9mtjc7vb6n4sER2p6TYWEpKbp/FLpG9IXunRduYqPJ6gigKFPCsDM3yg=
X-Received: by 2002:a92:350d:: with SMTP id c13mr81250905ila.205.1578111345564; Fri, 03 Jan 2020 20:15:45 -0800 (PST)
MIME-Version: 1.0
References: <18437_1576774434_5DFBAB22_18437_317_31_53C29892C857584299CBF5D05346208A48D392D1@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <19AB2A007F56DB4E8257F949A2FB9858E5E99B70@NKGEML515-MBX.china.huawei.com>
In-Reply-To: <19AB2A007F56DB4E8257F949A2FB9858E5E99B70@NKGEML515-MBX.china.huawei.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Fri, 03 Jan 2020 23:15:34 -0500
Message-ID: <CABNhwV2GvZHe4AFg45i9kjy6aTEi47hrjtkukwbjSTgdNo0yTg@mail.gmail.com>
To: Zhuangshunwan <zhuangshunwan@huawei.com>
Cc: SPRING WG <spring@ietf.org>, "bruno.decraene@orange.com" <bruno.decraene@orange.com>
Content-Type: multipart/alternative; boundary="0000000000002b2246059b48ae60"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/eD-UKYAHj4CneFJe-ZMR4hjqhB4>
Subject: Re: [spring] draft-ietf-spring-srv6-network-programming - 2 week Early Allocation Call
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Jan 2020 04:15:49 -0000

I support early allocation as their are many IPv6 deployments around the
world.

Gyan

On Thu, Jan 2, 2020 at 11:00 PM Zhuangshunwan <zhuangshunwan@huawei.com>
wrote:

> I support this early allocation.
>
>
>
> Thanks,
>
> Shunwan
>
>
>
> *From:* spring [mailto:spring-bounces@ietf.org] *On Behalf Of *
> bruno.decraene@orange.com
> *Sent:* Friday, December 20, 2019 12:54 AM
> *To:* SPRING WG <spring@ietf.org>
> *Subject:* [spring] draft-ietf-spring-srv6-network-programming - 2 week
> Early Allocation Call
>
>
>
> Hi SPRING WG,
>
>
>
> This begins a 2 week Early Allocation call for a “Ethernet” value from the "Protocol Numbers" registry.
>
> https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-07#section-9.1
>
> https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-07#section-5.3
>
> https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml
>
>
>
> In parallel of the Working Group Last Call which is currently running, the authors are requesting for early code point allocation from IANA as implementations are under way.
>
>
>
> The criteria for early allocation are:
>
>    a.  The code points must be from a space designated as "RFC
>
>        Required", "IETF Review", or "Standards Action".  Additionally,
>
>        requests for early assignment of code points from a
>
>        "Specification Required" registry are allowed if the
>
>        specification will be published as an RFC.
>
>
>
>    b.  The format, semantics, processing, and other rules related to
>
>        handling the protocol entities defined by the code points
>
>        (henceforth called "specifications") must be adequately described
>
>        in an Internet-Draft.
>
>
>
>    c.  The specifications of these code points must be stable; i.e., if
>
>        there is a change, implementations based on the earlier and later
>
>        specifications must be seamlessly interoperable.
>
>
>
>    d.  The Working Group chairs and Area Directors (ADs) judge that
>
>        there is sufficient interest in the community for early (pre-RFC)
>
>        implementation and deployment, or that failure to make an early
>
>        allocation might lead to contention for the code point in the
>
>        field.
>
> https://tools.ietf.org/html/rfc7120#section-2
>
>
>
> I believe the above conditions are met. (minus the AD judgement which is further down in the process)
>
>
>
> As a reminder, this topic has mainly been discussed following IETF 105 (Montréal) both during the meeting and on the mailing list.
>
> During IETF 106 it has been discussed in the IntArea WG. https://datatracker.ietf.org/meeting/106/proceedings#intarea
>
>
>
> Note that this code point is not to be specific to SRv6. Depending on AD guidance, this specific code point even be moved from draft-ietf-spring-srv6-network-programming into a specific 1 page draft.
>
>
>
> If you support early adoption,  please include “support” along with any comments about the draft’s technical solution.
>
>
>
> If you do not support early allocation, please include “no support” in your email and indicate why.
>
>
>
> Thank you,
>
> --Bruno
>
>
>
> _________________________________________________________________________________________________________________________
>
>
>
> 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.
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
-- 

Gyan S. Mishra

IT Network Engineering & Technology

Verizon Communications Inc. (VZ)

13101 Columbia Pike FDC1 3rd Floor

Silver Spring, MD 20904

United States

Phone: 301 502-1347

Email: gyan.s.mishra@verizon.com

www.linkedin.com/in/networking-technologies-consultant