[sfc] Upcoming SFC WG Interim meeting

James N Guichard <james.n.guichard@huawei.com> Fri, 13 January 2017 18:21 UTC

Return-Path: <james.n.guichard@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 5BFB3129533 for <sfc@ietfa.amsl.com>; Fri, 13 Jan 2017 10:21:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.419
X-Spam-Status: No, score=-7.419 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id rEQ7sU12gqzX for <sfc@ietfa.amsl.com>; Fri, 13 Jan 2017 10:21:37 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0439D1294BD for <sfc@ietf.org>; Fri, 13 Jan 2017 10:21:33 -0800 (PST)
Received: from (EHLO lhreml708-cah.china.huawei.com) ([]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DEJ59492; Fri, 13 Jan 2017 18:21:31 +0000 (GMT)
Received: from DFWEML703-CAH.china.huawei.com ( by lhreml708-cah.china.huawei.com ( with Microsoft SMTP Server (TLS) id 14.3.301.0; Fri, 13 Jan 2017 18:21:30 +0000
Received: from DFWEML501-MBB.china.huawei.com ([]) by DFWEML703-CAH.china.huawei.com ([]) with mapi id 14.03.0301.000; Fri, 13 Jan 2017 10:21:25 -0800
From: James N Guichard <james.n.guichard@huawei.com>
To: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: Upcoming SFC WG Interim meeting
Thread-Index: AdJtyPf1jf+42QB6SRiAz9Ecnd7TuQ==
Date: Fri, 13 Jan 2017 18:21:25 +0000
Message-ID: <BF1BE6D99B52F84AB9B48B7CF6F17DA3414CFE@dfweml501-mbb>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_BF1BE6D99B52F84AB9B48B7CF6F17DA3414CFEdfweml501mbb_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.58791AAC.0084, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: abcac7389d2b88f112aac88d63008bd6
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/7IngVUZcqNDFVdqtMHtsL7kihhY>
Subject: [sfc] Upcoming SFC WG Interim meeting
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.17
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, 13 Jan 2017 18:21:46 -0000

Greetings WG:

The following is a rough agenda for the upcoming SFC WG Interim meeting in Boston. We have deliberately left the agenda as flexible as possible so that we can make good use of our face-to-face time in discussion/white boarding rather than slide ware.

Chair Introduction:
                - Logistics
                - Agenda bashing
                                - emphasis on discussion to move our work forward and capturing WG action items
                                - accept/deny requests for any other formats/agenda items
                                - summary of status of planned discussion items

What follows is not split across days and purposefully not time-estimated:

NSH document discussion:
                - review agreed upon document changes
                - review remaining open items

Security Environment document discussion:
                - what do we want from this document
                - review what is already covered and what the reader should gain from reading

OAM drafts discussion:
                - Common work in NVO3
                                - how to use the common work
                                - special needs of SFC
                - Discussion of what things we need OAM to address
                                - conventional / CV problems
                                - In-situ
                - What can/should we cover in the OAM framework document

Control-plane Requirements document discussion:
                - how do we make this a useful document as an RFC that can be implemented

Metadata discussion:
                - documenting general attributes and review of existing drafts
                - approach for document MD-1 usages
                - documenting MD-2 TLVs
                                - what do we want from a registry creation document
                                - what do we expect from other defining documents

Summary and review of action items:
                - with decisions to be taken to the WG list for discussion and verification


Jim & Joel