Re: [sfc] Fwd: IETF WG state changed for draft-ietf-sfc-serviceid-header

<christian.jacquenet@orange.com> Thu, 12 December 2019 07:11 UTC

Return-Path: <christian.jacquenet@orange.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F6761200FD for <sfc@ietfa.amsl.com>; Wed, 11 Dec 2019 23:11:32 -0800 (PST)
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, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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 iTBDvpEbolZm for <sfc@ietfa.amsl.com>; Wed, 11 Dec 2019 23:11:30 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.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 2388912008C for <sfc@ietf.org>; Wed, 11 Dec 2019 23:11:30 -0800 (PST)
Received: from opfedar04.francetelecom.fr (unknown [xx.xx.xx.6]) by opfedar27.francetelecom.fr (ESMTP service) with ESMTP id 47YQ2S5s0gz2xcs; Thu, 12 Dec 2019 08:11:28 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.89]) by opfedar04.francetelecom.fr (ESMTP service) with ESMTP id 47YQ2S51Nmz1xnn; Thu, 12 Dec 2019 08:11:28 +0100 (CET)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM44.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0468.000; Thu, 12 Dec 2019 08:11:28 +0100
From: christian.jacquenet@orange.com
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: [sfc] Fwd: IETF WG state changed for draft-ietf-sfc-serviceid-header
Thread-Index: AQHVsCoq//fIcB6esEqgJgn7w4VPtqe2FdAw
Date: Thu, 12 Dec 2019 07:11:28 +0000
Message-ID: <31711_1576134688_5DF1E820_31711_489_1_88132E969123D14D9BD844E1CD516EDE3B48871D@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <157599887144.9975.7887971558651782704.idtracker@ietfa.amsl.com> <71423503-e1a3-31f1-43fc-527a0004ec2a@joelhalpern.com>
In-Reply-To: <71423503-e1a3-31f1-43fc-527a0004ec2a@joelhalpern.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.245]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/TxNCfzIzQOMATzULITvMkXVuQeU>
Subject: Re: [sfc] Fwd: IETF WG state changed for draft-ietf-sfc-serviceid-header
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Dec 2019 07:11:32 -0000

Hello sfc WG,

I believe this document is useful to optimize SFC design and operation, it's in good shape and should be moved forward.

Cheers,

Christian.

-----Message d'origine-----
De : sfc [mailto:sfc-bounces@ietf.org] De la part de Joel M. Halpern
Envoyé : mercredi 11 décembre 2019 14:52
À : sfc@ietf.org
Objet : [sfc] Fwd: IETF WG state changed for draft-ietf-sfc-serviceid-header

Starting WG Last call.  See comment below for description.
Thank you,
Joel


-------- Forwarded Message --------
Subject: IETF WG state changed for draft-ietf-sfc-serviceid-header
Resent-Date: Tue, 10 Dec 2019 09:27:51 -0800 (PST)
Resent-From: alias-bounces@ietf.org
Resent-To: james.n.guichard@futurewei.com, jmh@joelhalpern.com, 
tal.mizrahi.phd@gmail.com
Date: Tue, 10 Dec 2019 09:27:51 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
To: draft-ietf-sfc-serviceid-header@ietf.org, sfc-chairs@ietf.org


The IETF WG state of draft-ietf-sfc-serviceid-header has been changed to "In
WG Last Call" from "WG Document" by Joel Halpern:

https://datatracker.ietf.org/doc/draft-ietf-sfc-serviceid-header/

Comment:
This starts the working group last call for this document.  It has been
discussed on the email list.  We need to see responses.  If you see issues
with publishing this document as an RFC, please speak up now.  And please be
clear about what your concerns are.   At the same time, if you think that
publishing this as an RFC is a good thing for the working group, please 
speak
up.

As a note for those who may be concerned about the relationship to the TLV
draft, the chairs have noticed that problem, and we believe we have gotten
that document unstuck.

Given the propensity for people to disappear at this time of year, I am
giving the document a 4 week last call.

Thank you for your time and attention,
Joel (& Jim)

_______________________________________________
sfc mailing list
sfc@ietf.org
https://www.ietf.org/mailman/listinfo/sfc

_________________________________________________________________________________________________________________________

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.