[bess] Discussion on various NH encoding

<stephane.litkowski@orange.com> Fri, 28 June 2019 08:40 UTC

Return-Path: <stephane.litkowski@orange.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 7717812018B; Fri, 28 Jun 2019 01:40:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
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_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 4HcDnx1qqPMU; Fri, 28 Jun 2019 01:40:22 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D5931200B5; Fri, 28 Jun 2019 01:40:22 -0700 (PDT)
Received: from opfedar04.francetelecom.fr (unknown [xx.xx.xx.6]) by opfedar26.francetelecom.fr (ESMTP service) with ESMTP id 45Zqw50wPxzFvBJ; Fri, 28 Jun 2019 10:40:21 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.82]) by opfedar04.francetelecom.fr (ESMTP service) with ESMTP id 45Zqw470Vdz1xpC; Fri, 28 Jun 2019 10:40:20 +0200 (CEST)
Received: from OPEXCAUBMA3.corporate.adroot.infra.ftgroup ([fe80::90fe:7dc1:fb15:a02b]) by OPEXCAUBM5E.corporate.adroot.infra.ftgroup ([fe80::849f:f804:b713:d99a%21]) with mapi id 14.03.0439.000; Fri, 28 Jun 2019 10:40:20 +0200
From: stephane.litkowski@orange.com
To: "bess@ietf.org" <bess@ietf.org>
CC: "bess-chairs@ietf.org" <bess-chairs@ietf.org>, "martin.vigoureux@nokia.com" <martin.vigoureux@nokia.com>
Thread-Topic: Discussion on various NH encoding
Thread-Index: AdUtjD/rUEm8SotyQRCgbbuAgYPCbA==
Date: Fri, 28 Jun 2019 08:40:20 +0000
Message-ID: <26436_1561711221_5D15D275_26436_180_1_9E32478DFA9976438E7A22F69B08FF924C25BA2A@OPEXCAUBMA3.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_9E32478DFA9976438E7A22F69B08FF924C25BA2AOPEXCAUBMA3corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/GdBvw_i6NWXPHlKTIQ9zW4ixjm4>
Subject: [bess] Discussion on various NH encoding
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Jun 2019 08:40:25 -0000

Hi WG,

(Speaking as co-chair)

The current discussion on the NH encodings in our AFI/SAFIs requires some particular attention.
We would like to take the opportunity of the next IETF to discuss the subject face to face.

In the meantime, we are looking for few volunteers who will:

-          Do an inventory of what do we have in our specifications: which AFI/SAFI, which NH encoding rules

-          Identify inconsistencies (if any) or assess if it hurts or not (theoretically)

-          What is implemented or is there some known implementation issues

-          Present and drive the discussion at next IETF

Based on this, we will see if there is something to do or not.
Timing is short before next IETF, however the more material we have, the better the discussion will be.

Who wants to help on this ?


Stephane & Matthew


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.