New non-WG malign list : Network Service Chaining (NSC)

"Adrian Farrel" <adrian@olddog.co.uk> Mon, 17 June 2013 17:51 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FE7321F9CBF for <ietf@ietfa.amsl.com>; Mon, 17 Jun 2013 10:51:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.583
X-Spam-Level:
X-Spam-Status: No, score=-2.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cGphgll+c4-U for <ietf@ietfa.amsl.com>; Mon, 17 Jun 2013 10:51:35 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 1D3A121F9CB5 for <ietf@ietf.org>; Mon, 17 Jun 2013 10:51:34 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r5HHpXRb017210 for <ietf@ietf.org>; Mon, 17 Jun 2013 18:51:33 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r5HHpWau017199 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Mon, 17 Jun 2013 18:51:33 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: ietf@ietf.org
Subject: New non-WG malign list : Network Service Chaining (NSC)
Date: Mon, 17 Jun 2013 18:51:32 +0100
Message-ID: <02a901ce6b83$4e22bbb0$ea683310$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5rgz8KIpl429SoSZ+5N4KbdHLRiA==
Content-Language: en-gb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jun 2013 17:51:35 -0000

There is a new non-working group mailing list for discussion of Network Service
Chaining (NSC)

The web page for users is:

    https://www.ietf.org/mailman/listinfo/nsc

There is also an email-based interface for users. You can get info about using
it by sending a message with just the word `help' as subject or in the body, to:

    nsc-request@ietf.org

The mailing list is configured with a public archive which can be found at: 

   http://www.ietf.org/mail-archive/web/nsc

The purpose of the list
 
  Network services are widely deployed and essential in many networks. The
  services provide a range of functions such as security, WAN acceleration, and
  server load balancing. Service functions that form part of the overall service
  may be physically located at different points in the network infrastructure
such
  as the wide area network, data center, campus, and so forth.
 
  New data center network and Internet cloud architectures require more flexible
  network service deployment models. Additionally, the transition to virtual
  platforms requires an agile service insertion model that supports elastic
  service delivery, the movement of service functions and application workloads
in
  the network and the ability to easily bind service policy to granular
  information such as per-subscriber state.
 
  Service chaining is a broad term used to describe a common model for
delivering
  multiple services in a specific order. Service chaining de-couples service
  delivery from the underlying network topology and creates a dynamic services
  plane that addresses the requirements of cloud and virtual application
delivery.
  Traffic that requires service chaining is classified, and context is shared
  between the network and the services.
 
  This list is for discussion of aspects of Network Service Chaining (NSC) that
  impact upon the IETF's work, the applicability of IETF protocols to NSC, as
well
  as new protocols and changes to IETF protocols that might be required.
 
  A BoF has been proposed for NSC in Berlin. This list also serves to discuss
that
  BoF proposal. See the proposal at http://trac.tools.ietf.org/bof/trac/
 
Thanks,
Adrian