IETF Logo Mail Archive

Re: [Idr] WG Adoption call for draft-snijders-idr-shutdown (11/16 to 11/30)

<stephane.litkowski@orange.com> Thu, 17 November 2016 03:03 UTC

Return-Path: <stephane.litkowski@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 370CD12957B for <idr@ietfa.amsl.com>; Wed, 16 Nov 2016 19:03:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.415
X-Spam-Level:
X-Spam-Status: No, score=-3.415 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 hAqv5Fbs9h0c for <idr@ietfa.amsl.com>; Wed, 16 Nov 2016 19:03:34 -0800 (PST)
Received: from relais-inet.orange.com (mta239.mail.business.static.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89CA9129559 for <idr@ietf.org>; Wed, 16 Nov 2016 19:03:34 -0800 (PST)
Received: from opfedar07.francetelecom.fr (unknown [xx.xx.xx.9]) by opfedar20.francetelecom.fr (ESMTP service) with ESMTP id 442121201DC; Thu, 17 Nov 2016 04:03:33 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.17]) by opfedar07.francetelecom.fr (ESMTP service) with ESMTP id 20623C0057; Thu, 17 Nov 2016 04:03:33 +0100 (CET)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM24.corporate.adroot.infra.ftgroup ([fe80::a1e6:3e6a:1f68:5f7e%18]) with mapi id 14.03.0319.002; Thu, 17 Nov 2016 04:03:32 +0100
From: stephane.litkowski@orange.com
To: Susan Hares <shares@ndzh.com>, 'idr wg' <idr@ietf.org>, Robert Raszuk <robert@raszuk.net>
Thread-Topic: [Idr] WG Adoption call for draft-snijders-idr-shutdown (11/16 to 11/30)
Thread-Index: AdJATQXKePgAmF1nTgStU0J//yEVUAAMZM4Q
Date: Thu, 17 Nov 2016 03:03:32 +0000
Message-ID: <29352_1479351813_582D1E05_29352_19421_1_9E32478DFA9976438E7A22F69B08FF921DBB17E3@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <013f01d2404d$3dfff610$b9ffe230$@ndzh.com>
In-Reply-To: <013f01d2404d$3dfff610$b9ffe230$@ndzh.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.1]
Content-Type: multipart/alternative; boundary="_000_9E32478DFA9976438E7A22F69B08FF921DBB17E3OPEXCLILMA4corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/IKZFVWHMron3WTrZvUbXUnuBLjE>
Subject: Re: [Idr] WG Adoption call for draft-snijders-idr-shutdown (11/16 to 11/30)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 17 Nov 2016 03:03:41 -0000

I support it as conveying informations between BGP Speakers is useful but this is a sort of subset of a previous operational message work on BGP that has never been achieved. Was it just because of lack of implementations ? I do not have history on this.
I would like to avoid falling into the same issues.


From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Thursday, November 17, 2016 06:06
To: 'idr wg'
Subject: [Idr] WG Adoption call for draft-snijders-idr-shutdown (11/16 to 11/30)

This begins a 2 week WG Adoption call for draft-snijders-idr-shutdown (11/16/2016 to 11/30/2016).   The discussion should consider whether this is useful to operators and technical issues.


Sue

_________________________________________________________________________________________________________________________

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.

v2.46.0 | Report a Bug | By Email | System Status