[secdir] [new-work] WG Review: Service Function Chaining (sfc)

The IESG <iesg@ietf.org> Fri, 26 January 2018 21:10 UTC

Return-Path: <new-work-bounces@ietf.org>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C2E0712DA41; Fri, 26 Jan 2018 13:10:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1517001040; bh=qSqOPsknRCYIK72jW84yls9Jl9m/e0nITbz8b7EeR7A=; h=From:To:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=SQdxCakgoVpSWvK6N0SuyxVrIkDbt/93fhYsfYJhynUI6C70Gbg+xdhThT7mBT6Xl +UTibbyqWVUThMBv42FjrU8CO4G7w9dZ+QxKG3lp51EulgQSW8ipGvtVSXrDS1Z/l2 zEO93+jYvwi2F2EOmleWJAGILHuYewQN59wiKVrI=
X-Original-To: new-work@ietf.org
Delivered-To: new-work@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CAA71270AC for <new-work@ietf.org>; Fri, 26 Jan 2018 13:10:33 -0800 (PST)
MIME-Version: 1.0
From: The IESG <iesg@ietf.org>
To: <new-work@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.70.0
Auto-Submitted: auto-generated
Precedence: bulk
MIME-Version: 1.0
Reply_to: <iesg@ietf.org>
Message-ID: <151700103344.4373.16879925767925585636.idtracker@ietfa.amsl.com>
Date: Fri, 26 Jan 2018 13:10:33 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/new-work/lTePN4wL-rUaRN1uGFc7PpB6qgE>
X-BeenThere: new-work@ietf.org
X-Mailman-Version: 2.1.22
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: new-work-bounces@ietf.org
Sender: "new-work" <new-work-bounces@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/IP82F3HKwASKZAoZAFK7OvFNpI0>
X-Mailman-Approved-At: Fri, 26 Jan 2018 13:45:10 -0800
Subject: [secdir] [new-work] WG Review: Service Function Chaining (sfc)
X-BeenThere: secdir@ietf.org
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jan 2018 21:10:41 -0000

The Service Function Chaining (sfc) WG in the Routing Area of the IETF is
undergoing rechartering. The IESG has not made any determination yet. The
following draft charter was submitted, and is provided for informational
purposes only. Please send your comments to the IESG mailing list
(iesg@ietf.org) by 2018-02-05.

Service Function Chaining (sfc)
-----------------------------------------------------------------------
Current status: Active WG

Chairs:
  Joel Halpern <jmh@joelhalpern.com>;
  Jim Guichard <james.n.guichard@huawei.com>;

Secretaries:
  Tal Mizrahi <talmi@marvell.com>;

Assigned Area Director:
  Alia Atlas <akatlas@gmail.com>;

Routing Area Directors:
  Alia Atlas <akatlas@gmail.com>;
  Alvaro Retana <aretana.ietf@gmail.com>;
  Deborah Brungard <db3546@att.com>;

Mailing list:
  Address: sfc@ietf.org
  To subscribe: https://www.ietf.org/mailman/listinfo/sfc
  Archive: https://mailarchive.ietf.org/arch/browse/sfc/

Group page: https://datatracker.ietf.org/group/sfc/

Charter: https://datatracker.ietf.org/doc/charter-ietf-sfc/

Network operators frequently utilize service functions such as packet
filtering at firewalls, load-balancing and transactional proxies (for example
spam filters) in the delivery of services to end users. Delivery of these
types of services is undergoing significant change with the introduction of
virtualization, network overlays, and orchestration.

The SFC Working Group has developed an Architecture [RFC 7665] and the
Network Service Header [RFC 8300] for service function chaining.

The focus of the SFC working group moving forward is on aspects of the
architecture and/or protocol that need to be addressed to enable effective
deployment and usage of this work. In order to maintain focus, the working
group primarily produces and advances documents on four topics:

1) Metadata - Define the common type-length-value encoded metadata types with
Standards Track RFCs, and produce Informational RFCs to describe common
fixed-length (MD-1) metadata usages.

2) Security and Privacy - Mechanisms and guidance for securing metadata via
authentication, integrity protection, confidentiality, and/or data
minimization are not yet defined.  What can be effectively provided, for
which scenarios, and how those tools can be provided need to be determined
and the tools standardized.

3) OAM and Operations & Management - In order for operators to use these
tools in production networks, they need Operations, Administration, and
Maintenance tools, as well as management mechanisms.  This includes YANG
models, OAM frameworks, and specific OAM mechanisms to address operational
needs.

4) Transport Considerations - This will capture the expectations SFC places
on transport behavior, including dealing with issues such as congestion
indications and responses.  This should define how NSH works on standardized
transports that are expected to see widespread use.

Specifically, the SFC WG is chartered to deliver the following:

1. A Standards Track base set of the metadata MD-2 type codes within the
metadata class reserved for IETF usage, as specified in RFC 8300.

2. Related Metadata drafts that require more explanation than is reasonable
to include in the base MD-2 draft, including MD-1 descriptions and items done
once the base draft is complete.

3. YANG models for the management of SFC Components.

4. One or more security related Standards Track and / or Informational RFCs. 
At least one Standards Track security mechanism RFC is needed.

5. OAM Framework document to provide a common basis for OAM work.  This draft
will include guidance on how active, passive, and hybrid OAM are to be
supported if at all.

6. Specific OAM mechanism documents to provide the tools needed for
operational environments.

7. Transport Considerations RFC to cover the expectations SFC and NSH place
on transport, and the operational constraints transports used by NSH need to
meet.

The SFC WG may work on Informational applicability documents that show how
the technology, meta-data, and associated control-plane mechanisms can be
used in specific use-cases.  The SFC WG may work on Informational documents
that provide operational considerations.

The SFC WG will coordinate with BESS and PCE on the control-plane work
related to SFC.

Milestones:

TBD

_______________________________________________
new-work mailing list
new-work@ietf.org
https://www.ietf.org/mailman/listinfo/new-work