RFC 7149 on Software-Defined Networking: A Perspective from within a Service Provider Environment
rfc-editor@rfc-editor.org Wed, 05 March 2014 15:08 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02BF61A023A for <ietf-announce@ietfa.amsl.com>; Wed, 5 Mar 2014 07:08:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 jsibkR0D4nyo for <ietf-announce@ietfa.amsl.com>; Wed, 5 Mar 2014 07:08:10 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id A0D341A0276 for <ietf-announce@ietf.org>; Wed, 5 Mar 2014 07:08:10 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 001877FC399; Wed, 5 Mar 2014 07:08:06 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7149 on Software-Defined Networking: A Perspective from within a Service Provider Environment
From: rfc-editor@rfc-editor.org
Message-Id: <20140305150807.001877FC399@rfc-editor.org>
Date: Wed, 05 Mar 2014 07:08:06 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/NP7J-PvYaDTetY03jlPmGDuAANU
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Mar 2014 15:08:17 -0000
A new Request for Comments is now available in online RFC libraries. RFC 7149 Title: Software-Defined Networking: A Perspective from within a Service Provider Environment Author: M. Boucadair, C. Jacquenet Status: Informational Stream: IETF Date: March 2014 Mailbox: mohamed.boucadair@orange.com, christian.jacquenet@orange.com Pages: 20 Characters: 47516 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-sin-sdnrg-sdn-approach-09.txt URL: http://www.rfc-editor.org/rfc/rfc7149.txt Software-Defined Networking (SDN) has been one of the major buzz words of the networking industry for the past couple of years. And yet, no clear definition of what SDN actually covers has been broadly admitted so far. This document aims to clarify the SDN landscape by providing a perspective on requirements, issues, and other considerations about SDN, as seen from within a service provider environment. It is not meant to endlessly discuss what SDN truly means but rather to suggest a functional taxonomy of the techniques that can be used under an SDN umbrella and to elaborate on the various pending issues the combined activation of such techniques inevitably raises. As such, a definition of SDN is only mentioned for the sake of clarification. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/search For downloading RFCs, see http://www.rfc-editor.org/rfc.html Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC