Re: [sfc] WG Adoption calls: two MD-1 drafts

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 30 November 2017 14:14 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 C0FB112948D for <sfc@ietfa.amsl.com>; Thu, 30 Nov 2017 06:14:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, SPF_PASS=-0.001, URIBL_BLOCKED=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 2GJcPbBl_T_L for <sfc@ietfa.amsl.com>; Thu, 30 Nov 2017 06:14:57 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 51E53126C2F for <sfc@ietf.org>; Thu, 30 Nov 2017 06:14:57 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 3ED788E0FD1; Thu, 30 Nov 2017 06:14:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1512051297; bh=9abmAMCDLXmJbx7luHM7wUFZz2Q09MufbZAyveXVR2g=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=ax53VdswWFtm20IOnDb1kSqSUoNB0MxV9n65VJjl+SC+4SugfHXlpdi6L3nZlsrMo oxpk4VHNve/0F0QWF/08Ue57FTKeb4K+mUEPb6UYm8yaky5ReMBCWPXRtNDwJvscVf XWPZCBwdjCgmm/MXvI/aKucYgh0w8lslhAQMnsmA=
X-Virus-Scanned: Debian amavisd-new at maila2.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 maila2.tigertech.net (Postfix) with ESMTPSA id A1D102407AE; Thu, 30 Nov 2017 06:14:56 -0800 (PST)
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Cc: "sfc@ietf.org" <sfc@ietf.org>
References: <a4824833-03da-16e4-2d5e-b88757454d9c@joelhalpern.com> <B4ECCD19-C19D-48C0-A05E-6D64CF1F48AE@cisco.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <18270cdf-d0de-4cbc-f61f-3e7d300bdd8f@joelhalpern.com>
Date: Thu, 30 Nov 2017 09:14:55 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <B4ECCD19-C19D-48C0-A05E-6D64CF1F48AE@cisco.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/GbgKPT1xivoFb5ZILEz65KYmgbo>
Subject: Re: [sfc] WG Adoption calls: two MD-1 drafts
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: Thu, 30 Nov 2017 14:14:59 -0000

Sumandra (the pen holding author) did ask for WG adoption for that draft.
I was concerned about sending too many requests to the WG.  However, as 
noted by you and Med, there is a strong relationship with the two MD-1 
drafts and the MD-2 draft.  As such, I will send an adoption call for 
the MD-2 draft later today.

Thank you,
Joel

On 11/30/17 9:00 AM, Carlos Pignataro (cpignata) wrote:
> Joel,
> 
> I’ll look at this call and the other concurrent ones. But in the mean 
> time, a quick question:
> 
> Should the WG attempt to advance the MD field definitions for MD-1 and 
> MD-2 together as they apply to the same use-cases? For things like 
> Tenant ID, Network ingress identification, etc.
> 
> Should there be a parallel call to 
> https://datatracker.ietf.org/doc/draft-quinn-sfc-nsh-tlv/ ?
> 
> Thanks,
> 
> —
> Carlos Pignataro, carlos@cisco.com <mailto:carlos@cisco.com>
> 
> /“Sometimes I use big words that I do not fully understand, to make 
> myself sound more photosynthesis."/
> 
>> On Nov 29, 2017, at 4:19 PM, Joel M. Halpern <jmh@joelhalpern.com 
>> <mailto:jmh@joelhalpern.com>> wrote:
>>
>> The WG chairs have been asked to issue calls for adoption for two of 
>> the MD-1 related drafts:
>>
>> https://datatracker.ietf.org/doc/draft-napper-sfc-nsh-broadband-allocation/
>>
>> and
>>
>> https://datatracker.ietf.org/doc/draft-guichard-sfc-nsh-dc-allocation/
>>
>> These documents aim for publication as Informational RFCs.
>>
>> As Jim is the coauthor on one of these two, I will be overseeing both 
>> adoption calls.
>>
>> Given that there are two last calls an two calls for working group 
>> adoption (see following emails) we are allowing 3 weeks for these calls.
>>
>> Please respond with either support or objection to the WG adopting 
>> either or both of these documents.
>>
>> We need to see feedback.  Silence does not imply consent.
>> We would prefer feedback with content.
>>
>> Thank you,
>> Joel
>>
>> _______________________________________________
>> sfc mailing list
>> sfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/sfc
>