IETF Logo Mail Archive

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

Shunsuke Homma <shunsuke.homma.fp@hco.ntt.co.jp> Mon, 16 December 2019 04:36 UTC

Return-Path: <shunsuke.homma.fp@hco.ntt.co.jp>
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 78B471200D5 for <sfc@ietfa.amsl.com>; Sun, 15 Dec 2019 20:36:30 -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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 wcbRnhjFj8vX for <sfc@ietfa.amsl.com>; Sun, 15 Dec 2019 20:36:28 -0800 (PST)
Received: from dish-sg.nttdocomo.co.jp (dish-sg.nttdocomo.co.jp [202.19.227.74]) by ietfa.amsl.com (Postfix) with ESMTP id 87C5A1200CC for <sfc@ietf.org>; Sun, 15 Dec 2019 20:36:28 -0800 (PST)
X-dD-Source: Outbound
Received: from zssg-mailmd105.ddreams.local (zssg-mailmd900.ddreams.local [10.160.172.63]) by zssg-mailou104.ddreams.local (Postfix) with ESMTP id D4FEC1200E9; Mon, 16 Dec 2019 13:36:27 +0900 (JST)
Received: from zssg-mailcc302.ddreams.local (zssg-mailcc302.ddreams.local [10.160.162.153]) by zssg-mailmd105.ddreams.local (dDREAMS) with ESMTP id <0Q2L01BU68SRIB30@dDREAMS>; Mon, 16 Dec 2019 13:36:27 +0900 (JST)
Received: from zssg-mailcc302 (localhost [127.0.0.1]) by zssg-mailcc302.ddreams.local (unknown) with SMTP id xBG4aRE5049984; Mon, 16 Dec 2019 13:36:27 +0900
Received: from zssg-mailmf104.ddreams.local (unknown [127.0.0.1]) by zssg-mailmf104.ddreams.local (Postfix) with ESMTP id 7171E7E603C; Mon, 16 Dec 2019 13:36:18 +0900 (JST)
Received: from zssg-mailmf104.ddreams.local (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 6FB008E605D; Mon, 16 Dec 2019 13:36:18 +0900 (JST)
Received: from localhost (unknown [127.0.0.1]) by IMSVA (Postfix) with SMTP id 6E0AA8E605A; Mon, 16 Dec 2019 13:36:18 +0900 (JST)
X-IMSS-HAND-OFF-DIRECTIVE: localhost:10026
Received: from zssg-mailmf104.ddreams.local (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 40C898E605A; Mon, 16 Dec 2019 13:36:17 +0900 (JST)
Received: from zssg-mailua105.ddreams.local (unknown [10.160.172.62]) by zssg-mailmf104.ddreams.local (Postfix) with ESMTP; Mon, 16 Dec 2019 13:36:17 +0900 (JST)
Received: from rcR9101318 (unknown [10.171.96.193]) by zssg-mailua105.ddreams.local (dDREAMS) with ESMTPA id <0Q2L017QN8SE7T11@dDREAMS>; Mon, 16 Dec 2019 13:36:14 +0900 (JST)
From: Shunsuke Homma <shunsuke.homma.fp@hco.ntt.co.jp>
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>
Date: Mon, 16 Dec 2019 13:36:14 +0900
Message-id: <000301d5b3ca$59ae0480$0d0a0d80$@hco.ntt.co.jp_1>
MIME-version: 1.0
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Content-language: ja
Thread-index: AQHVYpH9R96HV3RunLwFWrsfMzwM0QIqZvm+p6t7ezA=
X-TM-AS-GCONF: 00
To: "'Joel M. Halpern'" <jmh@joelhalpern.com>, sfc@ietf.org
X-CC-Mail-RelayStamp: CC/Mail Relayed
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/tx7JOj6kQ39Lfo8Z75WQBGNHN5Y>
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 04:36:30 -0000

Hi authors,

I agree with that subscriber id will be useful, and simultaneously I have some questions on Performance Policy Identifier as below:
- In my understanding, SFC path and SF instance selection will be done at CF as starting point of SFC, and these information would
be implied in SFP. Why is the information needed to be represented as metadata in context header? (I agree that information for
policy selection at SFs would be needed because, for example, customers use multiple applications and they may have different
requirements for processes at SFs.) 
- ULL and UHR should be fulfilled as e2e communication, and some interwork with underlay transport (and maybe user plane in 3GPP if
it is used in mobile network) would be needed. Don't you describe some means how to interwork with other layers by using performance
policy identifier?

Also, I have some small comments:
- This document uses some 3GPP terms such as SGi and P/S-GW, and 3GPP documents(e.g., TS23.401) should be referred.
- SGi and P/S-GW are terms of 4G, but 5G is coming soon, thus why don't you add 5G terms (e.g., N6/DN, UPF) in addition to 4G terms?

Regards,

Shunsuke

-----Original Message-----
From: sfc <sfc-bounces@ietf.org> On Behalf Of Joel M. Halpern
Sent: Wednesday, December 11, 2019 10:52 PM
To: sfc@ietf.org
Subject: [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

v2.23.0 | Report a Bug | By Email