Re: [Idr] draft-ietf-idr-bgpls-srv6-ext - 2 week Early Allocation Call [6/2 - 6/16/2019]

<bruno.decraene@orange.com> Mon, 03 June 2019 08:59 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 33C761200D6; Mon, 3 Jun 2019 01:59:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, 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 AHQ7B72jIc77; Mon, 3 Jun 2019 01:59:33 -0700 (PDT)
Received: from orange.com (mta240.mail.business.static.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EAFF4120020; Mon, 3 Jun 2019 01:59:32 -0700 (PDT)
Received: from opfedar00.francetelecom.fr (unknown [xx.xx.xx.11]) by opfedar21.francetelecom.fr (ESMTP service) with ESMTP id 45HTWk6zM9z7vhh; Mon, 3 Jun 2019 10:59:30 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.29]) by opfedar00.francetelecom.fr (ESMTP service) with ESMTP id 45HTWk5lZJzCqkh; Mon, 3 Jun 2019 10:59:30 +0200 (CEST)
Received: from OPEXCAUBM43.corporate.adroot.infra.ftgroup ([fe80::b846:2467:1591:5d9d]) by OPEXCAUBM21.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0439.000; Mon, 3 Jun 2019 10:59:30 +0200
From: bruno.decraene@orange.com
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
CC: "draft-dawra-idr-bgpls-srv6-ext@ietf.org" <draft-dawra-idr-bgpls-srv6-ext@ietf.org>, "'Ketan Talaulikar (ketant)'" <ketant@cisco.com>
Thread-Topic: draft-ietf-idr-bgpls-srv6-ext - 2 week Early Allocation Call [6/2 - 6/16/2019]
Thread-Index: AdUZs3u0tmJ+YUSFThS9+Y9TF6t5cQANsTmQ
Date: Mon, 03 Jun 2019 08:59:30 +0000
Message-ID: <2629_1559552370_5CF4E172_2629_299_2_53C29892C857584299CBF5D05346208A48AF4496@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
References: <027301d519b3$d76887d0$86399770$@ndzh.com>
In-Reply-To: <027301d519b3$d76887d0$86399770$@ndzh.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: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A48AF4496OPEXCAUBM43corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/UWBN8PUo7TBQOqjDeOlE0edZaX4>
Subject: Re: [Idr] draft-ietf-idr-bgpls-srv6-ext - 2 week Early Allocation Call [6/2 - 6/16/2019]
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Jun 2019 08:59:36 -0000

Support as co-author.

Thank you,
--Bruno

From: Susan Hares [mailto:shares@ndzh.com]
Sent: Monday, June 3, 2019 4:27 AM
To: 'Ketan Talaulikar (ketant)'; idr@ietf.org
Cc: draft-dawra-idr-bgpls-srv6-ext@ietf.org
Subject: draft-ietf-idr-bgpls-srv6-ext - 2 week Early Allocation Call [6/2 - 6/16/2019]

This begins a 2 week Early Allocation call for parameters from:


https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgpls-srv6-ext-00

The authors are requesting for early code point allocation from
IANA to enable implementations with suggested code points as indicated below.

The criteria for early allocation includes:  stable working group document,
clear technical solution and implementation interest.   The IDR chairs
believe this document meets these criteria. Please let us know if you
think this draft meets these criteria.

If you support early adoption,  please include "support" in your along
with any comments about the draft's technical solution.  Since the
authors are heading into testing implementations, any comments about
error or improvements will be helpful to the authors.

If you do not support early allocation, please include
include "no support in your email" and indicate why.

Cheerily, Sue Hares

----------------------

   The following codepoints is suggested (to be assigned by IANA) from
   within the sub-registry called "BGP-LS NLRI-Types":

    +------+----------------------------+---------------+
    | Type | NLRI Type                  |   Reference   |
    +------+----------------------------+---------------+
    |  6   | SRv6 SID                   | this document |
    +------+----------------------------+---------------+

   The following TLV codepoints are suggested (to be assigned by IANA)
   from within the sub-registry called "BGP-LS Node Descriptor, Link
   Descriptor, Prefix Descriptor, and Attribute TLVs":

   +----------+----------------------------------------+---------------+
   | TLV Code |             Description                | Value defined |
   |  Point   |                                        |       in      |
   +----------+----------------------------------------+---------------+
   |  1038    |   SRv6 Capabilities TLV                | this document |
   |  1106    |   SRv6 End.X SID TLV                   | this document |
   |  1107    |   IS-IS SRv6 LAN End.X SID TLV         | this document |
  |  1108    |   OSPFv3 SRv6 LAN End.X SID TLV        | this document |
   |  1162    |   SRv6 Locator TLV                     | this document |
   |   518    |   SRv6 SID Information TLV             | this document |
   |  1250    |   SRv6 Endpoint Function TLV           | this document |
   |  1251    |   SRv6 BGP Peer Node SID TLV           | this document |
   +----------+----------------------------------------+---------------+


_________________________________________________________________________________________________________________________

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.