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

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 16 December 2019 01:26 UTC

Return-Path: <jmh@joelhalpern.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 F17831200A3 for <sfc@ietfa.amsl.com>; Sun, 15 Dec 2019 17:26:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 fr5840Wap4zm for <sfc@ietfa.amsl.com>; Sun, 15 Dec 2019 17:26:45 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2523D12004A for <sfc@ietf.org>; Sun, 15 Dec 2019 17:26:45 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 47bkBs0dhsz6G8Vd; Sun, 15 Dec 2019 17:26:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1576459605; bh=pnsL/zofhrh/MDj+48B3VHOlA829+MMML36wYd+XPqw=; h=Subject:To:References:From:Date:In-Reply-To:From; b=GZ2yipeqOlUvpTVVy1PTKLSyuQ1andsM6JmpG7vON3mGSDiJWr5a7jtNqH52fMHLw iB21yAmBI8aKFI3ImMbH4X25UB1V92uu/LcL5AcNW/KhV99WqlctPj4dppQ8Bby/KN B1ytmvoTm4sgKCQCg8OsAauuoaX83ejiZTNEAVhE=
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 47bkBr1SH4z6G87d; Sun, 15 Dec 2019 17:26:44 -0800 (PST)
To: Qin Wu <bill.wu@huawei.com>, "sfc@ietf.org" <sfc@ietf.org>
References: <B8F9A780D330094D99AF023C5877DABAA94FC3A2@dggeml511-mbx.china.huawei.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <f0bf8a0e-0c5f-178c-e0d9-234a0390708b@joelhalpern.com>
Date: Sun, 15 Dec 2019 20:26:42 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <B8F9A780D330094D99AF023C5877DABAA94FC3A2@dggeml511-mbx.china.huawei.com>
Content-Type: text/plain; charset="gbk"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/WUt2GTj-4dHuaWFzCSCE3quRk0g>
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: Mon, 16 Dec 2019 01:26:47 -0000

I am not confident that I follow your reasoning.   So let me restate 
slightly, and then add some observations and questions.

You appear to be observing that the information as to what serviceID 
could come from the control plane framework.  Is that what you are 
getting at?

That draft has not been updated in more than 3 years, expired for 2.5 
years.  It does not appear that the working group has any interest in 
the document.  When it was last considered, there was a lot of 
controversey about the draft, and if I recall correctly no agreement 
that it was structured the right way.

Our approach to metadata, and for that matter to SPFID selection, and to 
the forwarding entries in SFF, has been that the information can come 
from a number of places and we do not tie the definitions to the 
mechanisms used to provide them.

As such, I do not understand what form of reference would be 
appropriate, even if the cited document were an active WG document.

Yours,
Joel

On 12/15/2019 8:07 PM, Qin Wu wrote:
> I believe this draft is under umbrella of draft-ietf-sfc-control-plane-08, suggest to add reference to it.
> In addition, It will be great to add usage example of new defined subscriber identifier and Performance Policy Identifier.
> Besides these, I think this draft is ready to go.
> 
> -Qin
> -----邮件原件-----
> 发件人: sfc [mailto:sfc-bounces@ietf.org] 代表 Joel M. Halpern
> 发送时间: 2019年12月11日 21:52
> 收件人: sfc@ietf.org
> 主题: [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
>