Re: [sfc] I-D Action: draft-farrel-sfc-convent-06.txt

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Fri, 16 February 2018 22:02 UTC

Return-Path: <cpignata@cisco.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 E8601126BF0 for <sfc@ietfa.amsl.com>; Fri, 16 Feb 2018 14:02:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level:
X-Spam-Status: No, score=-14.531 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 jZm9OpJDxjQh for <sfc@ietfa.amsl.com>; Fri, 16 Feb 2018 14:02:10 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53B70124205 for <sfc@ietf.org>; Fri, 16 Feb 2018 14:02:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3524; q=dns/txt; s=iport; t=1518818530; x=1520028130; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=hp0J86/jFV+T+XBVnHgCHUriBFSXaiEs80Va5a/cdk4=; b=WHQjSPgr7UuRMXxujGo4uf84eL0uPnrS8jLlLWsBWdn8ixQSzDnWKUrQ tzEqQRKVUjxl/rac8a8Zhd6OdvMAtiClLxrbBEmWaNf7Ho/PuddBYh+o4 HRkrSuDPRk7LIB+5a7/2ZKYF1gK+SvVRHNDTxiKf0tb8jpzPs8WEGEhy6 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BQAwDaU4da/5xdJa1cGQEBAQEBAQEBAQEBAQcBAQEBAYNPZnAoCoNKmCuBWyeBF5ZJghYKGAuFGAIagixVFwECAQEBAQEBAmsohSMBAQEBAgEBASEROgsFBwQCAQgRBAEBAQICIwMCAgIlCxQBCAgCBA4FihkIEK01gieJAYITAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYEPg3iCKIFXghEMgnmDMAEBAgEBF4RtMYI0BaQ1CQKIIo1mgiBnhUOLfY4GiWwCERkBgTsBIAE3gVFwFRkhKgGCGAmEbXiNIYEZAQEB
X-IronPort-AV: E=Sophos;i="5.46,520,1511827200"; d="scan'208";a="356831261"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Feb 2018 22:02:09 +0000
Received: from XCH-RTP-017.cisco.com (xch-rtp-017.cisco.com [64.101.220.157]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id w1GM283C020432 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 16 Feb 2018 22:02:09 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-017.cisco.com (64.101.220.157) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 16 Feb 2018 17:02:08 -0500
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1320.000; Fri, 16 Feb 2018 17:02:08 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Adrian Farrel <adrian@olddog.co.uk>
CC: Alia Atlas <akatlas@gmail.com>, "sfc@ietf.org" <sfc@ietf.org>, Mirja Kuehlewind <ietf@kuehlewind.net>
Thread-Topic: [sfc] I-D Action: draft-farrel-sfc-convent-06.txt
Thread-Index: AQHTp29K29i8Xg08rUmHeJSAusjx5aOn5TaAgAADUAA=
Date: Fri, 16 Feb 2018 22:02:08 +0000
Message-ID: <1995278D-82AC-4896-ADD3-04B49748F71F@cisco.com>
References: <151881741177.1389.6711240505872310784@ietfa.amsl.com> <030b01d3a770$2355fd10$6a01f730$@olddog.co.uk>
In-Reply-To: <030b01d3a770$2355fd10$6a01f730$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.116.133]
Content-Type: text/plain; charset="utf-8"
Content-ID: <7BF9CEB39A4779448453B81FE631DEDF@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/Bu985EAeYbkFvJpr4A_kx3VtB30>
Subject: Re: [sfc] I-D Action: draft-farrel-sfc-convent-06.txt
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: Fri, 16 Feb 2018 22:02:14 -0000


> On Feb 16, 2018, at 4:50 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:
> 
> This new version is a place marker as my plane takes off soon.
> 
> Needs Carlos to say yay/nay.

Yay — safe flight!

C.

> Needs Mirja to approve and clear.
> 
> Adrian
> 
>> -----Original Message-----
>> From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
>> Sent: 16 February 2018 21:44
>> To: i-d-announce@ietf.org
>> Cc: sfc@ietf.org
>> Subject: [sfc] I-D Action: draft-farrel-sfc-convent-06.txt
>> 
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>> This draft is a work item of the Service Function Chaining WG of the IETF.
>> 
>>        Title           : Operating the Network Service Header (NSH) with Next
> Protocol
>> "None"
>>        Authors         : Adrian Farrel
>>                          John Drake
>> 	Filename        : draft-farrel-sfc-convent-06.txt
>> 	Pages           : 12
>> 	Date            : 2018-02-16
>> 
>> Abstract:
>>   This document describes the use of the Network Service Header (NSH)
>>   in a Service Function Chaining (SFC) enabled network with no payload
>>   data and carrying only metadata.  This is achieved by defining a new
>>   NSH "Next Protocol" type value of "None".
>> 
>>   This document illustrates some of the functions that may be achieved
>>   or enhanced by this mechanism, but it does not provide an exhaustive
>>   list of use cases, nor is it intended to be definitive about the
>>   functions it describes.  It is expected that other documents will
>>   describe specific use cases in more detail and will define the
>>   protocol mechanics for each use case.
>> 
>> 
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-farrel-sfc-convent/
>> 
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-farrel-sfc-convent-06
>> https://datatracker.ietf.org/doc/html/draft-farrel-sfc-convent-06
>> 
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-farrel-sfc-convent-06
>> 
>> 
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>> 
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>> 
>> _______________________________________________
>> sfc mailing list
>> sfc@ietf.org
>> https://www.ietf.org/mailman/listinfo/sfc
>