[sfc] NSH MD-1 documents

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 02 August 2017 15:37 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 50376129B7A for <sfc@ietfa.amsl.com>; Wed, 2 Aug 2017 08:37:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.722
X-Spam-Level:
X-Spam-Status: No, score=-2.722 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, 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 kHh0mfNy8_Mw for <sfc@ietfa.amsl.com>; Wed, 2 Aug 2017 08:37:08 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 551E9124B18 for <sfc@ietf.org>; Wed, 2 Aug 2017 08:37:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 3775A1C00A0 for <sfc@ietf.org>; Wed, 2 Aug 2017 08:37:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1501688228; bh=TZ7FErCZnK3NgpEvNBakW+TmH5SijoryEhEuP5dSQLI=; h=To:From:Subject:Date:From; b=SnJXRSJoAj9T91Y/Fchtf1aOG+tlF/nkQS0CZPX+RQjiuCjcZ07NgWMBRmmB65C3o iNNA42lh5BlQw4Xgo8N2gENUA4SXNzto4vqPubs29zjQ4tLKYayjlZ4Z9mYE68zw9G cEhyD7P622ybnyMN/f1PYgVW+q7oCWLqg2FKs3OY=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [50.225.209.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id D4A7D1C052D for <sfc@ietf.org>; Wed, 2 Aug 2017 08:37:07 -0700 (PDT)
To: "sfc@ietf.org" <sfc@ietf.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <a27f8974-1eb1-5dfb-938f-b106aac3a25a@joelhalpern.com>
Date: Wed, 02 Aug 2017 11:37:07 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/LDuHG7x6AtdFimiJwzvQrh2Cqj4>
Subject: [sfc] NSH MD-1 documents
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 02 Aug 2017 15:37:09 -0000

There have been a number of documents brought forward describing layouts 
of the 16 byte MD-1 metadata for specific situations.  The working group 
has discussed publishing some set of these as informational RFCs.  We 
would like to progress this work.  Without either overloading the 
working group or serving as a rubber stamp for proposals.

As such, would authors of MD-1 proposals that they believe should be 
worked on by the WG please do two things:
1) Refresh your documents, so we know they reflect your current view.
2) Provide an explanation to the WG of why this proposal has 
sufficiently broad applicability to warrant WG effort.  Not just "Data 
Centers are important".  But something that gives the WG members more 
context as to why the document addresses a broad range of cases.  We are 
not looking for detailed use cases, but a summary in email of the key 
points would help folks decide what to read.

Thank you,
Joel and Jim