Re: [sfc] Fwd: IETF WG state changed for draft-ietf-sfc-serviceid-header
Loa Andersson <loa@pi.nu> Fri, 20 December 2019 17:09 UTC
Return-Path: <loa@pi.nu>
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 46EFB120856 for <sfc@ietfa.amsl.com>; Fri, 20 Dec 2019 09:09:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 6dvvs9-uA9Lt for <sfc@ietfa.amsl.com>; Fri, 20 Dec 2019 09:09:53 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9AEB12084D for <sfc@ietf.org>; Fri, 20 Dec 2019 09:09:52 -0800 (PST)
Received: from [192.168.1.6] (unknown [119.94.167.108]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 5709735DF54; Fri, 20 Dec 2019 18:09:49 +0100 (CET)
To: "Joel M. Halpern" <jmh@joelhalpern.com>
References: <B8F9A780D330094D99AF023C5877DABAA94FC3A2@dggeml511-mbx.china.huawei.com> <f0bf8a0e-0c5f-178c-e0d9-234a0390708b@joelhalpern.com>
From: Loa Andersson <loa@pi.nu>
Cc: "sfc@ietf.org" <sfc@ietf.org>
Message-ID: <da07ff62-8b60-368b-0190-f13481b1c802@pi.nu>
Date: Sat, 21 Dec 2019 01:09:47 +0800
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: <f0bf8a0e-0c5f-178c-e0d9-234a0390708b@joelhalpern.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/iOynH0hjATJ-wqaBXXhwu3pjmVg>
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: Fri, 20 Dec 2019 17:09:55 -0000
Joel, A naive question inline. On 16/12/2019 09:26, Joel M. Halpern wrote: > 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 Is what you say that draft-ietf-sfc-control-plane has not been changed for 3 years and expired for 2.5? Sometimes umbrella documents is useful, in this case we seems to be doing good without one. /Loa > 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 >> > > _______________________________________________ > sfc mailing list > sfc@ietf.org > https://www.ietf.org/mailman/listinfo/sfc -- Loa Andersson email: loa@pi.nu Senior MPLS Expert Bronze Dragon Consulting phone: +46 739 81 21 64
- [sfc] Fwd: IETF WG state changed for draft-ietf-s… Joel M. Halpern
- Re: [sfc] Fwd: IETF WG state changed for draft-ie… christian.jacquenet
- Re: [sfc] Fwd: IETF WG state changed for draft-ie… Donald Eastlake
- Re: [sfc] Fwd: IETF WG state changed for draft-ie… mohamed.boucadair
- Re: [sfc] Fwd: IETF WG state changed for draft-ie… Qin Wu
- Re: [sfc] Fwd: IETF WG state changed for draft-ie… Joel M. Halpern
- Re: [sfc] Fwd: IETF WG state changed for draft-ie… Qin Wu
- Re: [sfc] Fwd: IETF WG state changed for draft-ie… Shunsuke Homma
- Re: [sfc] Fwd: IETF WG state changed for draft-ie… Dirk.von-Hugo
- Re: [sfc] Fwd: IETF WG state changed for draft-ie… Dirk.von-Hugo
- Re: [sfc] Fwd: IETF WG state changed for draft-ie… Qin Wu
- Re: [sfc] Fwd: IETF WG state changed for draft-ie… Loa Andersson
- Re: [sfc] Fwd: IETF WG state changed for draft-ie… Joel M. Halpern
- Re: [sfc] Fwd: IETF WG state changed for draft-ie… Shunsuke Homma
- Re: [sfc] Fwd: IETF WG state changed for draft-ie… Dirk.von-Hugo
- Re: [sfc] Fwd: IETF WG state changed for draft-ie… Shunsuke Homma