[sfc] New revisions for SFC network security use cases and NSH allocation

"Eric Wang (ejwang)" <ejwang@cisco.com> Tue, 01 November 2016 05:39 UTC

Return-Path: <ejwang@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 E46F712950D for <sfc@ietfa.amsl.com>; Mon, 31 Oct 2016 22:39:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.017
X-Spam-Level:
X-Spam-Status: No, score=-16.017 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001, 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 vWoxHLrL6yQz for <sfc@ietfa.amsl.com>; Mon, 31 Oct 2016 22:39:03 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6BD012941C for <sfc@ietf.org>; Mon, 31 Oct 2016 22:39:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8950; q=dns/txt; s=iport; t=1477978742; x=1479188342; h=from:to:cc:subject:date:message-id:mime-version; bh=LmoxBpIMfHEfGmsllz+psPPpFKkgCAt+yeyB/e8Bm6s=; b=C2I7xvsQKg5IP5w92yFQmf0ePUoTxRD3I24fpYKkCQ0IFCePy3G+5ycH tGD1FHoM0PBl6iTUVKoWGHLwRhz4wskZ8NITFJWg30RQWvyhdC31vEGGa KoB2WhMchOk0Nkp3PsFvSjFlVex6vBPBxKQ0mqRgHFJTf7gwh8e38NuN7 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D4AQBpKRhY/51dJa1dHAEBBAEBCgEBgyoBAQEBAR9YfQeNL6YphReCByqFeIIXPxQBAgEBAQEBAQFiHQuEaXkSAYEAJwQOiFkOtGkBAQEBAQEBAQEBAQEBAQEBAQEBAQEXBYg6CIJQh3iCLwWOTotMAYE9hHOKBJAGjQAThAIBHjZghRNyAYcSgQwBAQE
X-IronPort-AV: E=Sophos;i="5.31,430,1473120000"; d="scan'208,217";a="164158984"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Nov 2016 05:39:01 +0000
Received: from XCH-RTP-014.cisco.com (xch-rtp-014.cisco.com [64.101.220.154]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id uA15d1js009131 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <sfc@ietf.org>; Tue, 1 Nov 2016 05:39:01 GMT
Received: from xch-rtp-011.cisco.com (64.101.220.151) by XCH-RTP-014.cisco.com (64.101.220.154) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 1 Nov 2016 01:39:00 -0400
Received: from xch-rtp-011.cisco.com ([64.101.220.151]) by XCH-RTP-011.cisco.com ([64.101.220.151]) with mapi id 15.00.1210.000; Tue, 1 Nov 2016 01:39:00 -0400
From: "Eric Wang (ejwang)" <ejwang@cisco.com>
To: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: New revisions for SFC network security use cases and NSH allocation
Thread-Index: AQHSNAI/ixKcnteGcE61QT4N87ecRQ==
Date: Tue, 01 Nov 2016 05:39:00 +0000
Message-ID: <82855924-06FB-40A2-AA08-9F6D6C3B9DFC@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3124)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.19.59.179]
Content-Type: multipart/alternative; boundary="_000_8285592406FB40A2AA089F6D6C3B9DFCciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/48yqguCc1Fly2NZYWJch11z2J88>
Cc: "Kent Leung (kleung)" <kleung@cisco.com>
Subject: [sfc] New revisions for SFC network security use cases and NSH allocation
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: Tue, 01 Nov 2016 05:39:05 -0000

Hi folks,

We have submitted new revisions for two drafts:
draft-wang-sfc-ns-use-cases-02.txt
draft-wang-sfc-nsh-ns-allocation-01.txt

Appreciate all the comments so far, and we look forward to more discussions on the list and live in Seoul.


A new version of I-D, draft-wang-sfc-ns-use-cases-02.txt
has been successfully submitted by Eric Wang and posted to the
IETF repository.

Name: draft-wang-sfc-ns-use-cases
Revision: 02
Title: Service Function Chaining Use Cases for Network Security
Document date: 2016-10-25
Group: Individual Submission
Pages: 20
URL:            https://www.ietf.org/internet-drafts/draft-wang-sfc-ns-use-cases-02.txt
Status:         https://datatracker.ietf.org/doc/draft-wang-sfc-ns-use-cases/
Htmlized:       https://tools.ietf.org/html/draft-wang-sfc-ns-use-cases-02
Diff:           https://www.ietf.org/rfcdiff?url2=draft-wang-sfc-ns-use-cases-02

Abstract:
  Enterprise networks deploy a variety of security devices to protect
  the network, hosts and endpoints.  Network security devices, both
  hardware and virtual, operate at all OSI layers with scanning and
  analysis capabilities for application content.  Multiple specific
  devices are often deployed together for breadth and depth of defense.
  This document describes use cases of Service Function Chaining (SFC)
  when deploying network security devices in the manner described above
  and also puts forth requirements for their effective operation.


A new version of I-D, draft-wang-sfc-nsh-ns-allocation-01.txt
has been successfully submitted by Eric Wang and posted to the
IETF repository.

Name: draft-wang-sfc-nsh-ns-allocation
Revision: 01
Title: Network Service Header (NSH) Context Header Allocation (Network Security)
Document date: 2016-10-25
Group: Individual Submission
Pages: 7
URL:            https://www.ietf.org/internet-drafts/draft-wang-sfc-nsh-ns-allocation-01.txt
Status:         https://datatracker.ietf.org/doc/draft-wang-sfc-nsh-ns-allocation/
Htmlized:       https://tools.ietf.org/html/draft-wang-sfc-nsh-ns-allocation-01
Diff:           https://www.ietf.org/rfcdiff?url2=draft-wang-sfc-nsh-ns-allocation-01

Abstract:
  This document provides a recommended default allocation of the
  mandatory fixed context headers for a Network Service Header (NSH)
  relevant to Service Function Chaining (SFC) for network security
  Service Functions.  NSH is defined in [I-D.ietf-sfc-nsh].  This
  allocation is intended to support the use cased described in
  [I-D.wang-sfc-ns-use-cases].


Cheers,
-Eric