RFC 8151 on Use Cases for Data Center Network Virtualization Overlay Networks

rfc-editor@rfc-editor.org Fri, 26 May 2017 15:37 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 675C812E957; Fri, 26 May 2017 08:37:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 LLa7XYrFf6Tu; Fri, 26 May 2017 08:37:24 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 682B31296CD; Fri, 26 May 2017 08:37:11 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5D8E9B81D9D; Fri, 26 May 2017 08:36:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8151 on Use Cases for Data Center Network Virtualization Overlay Networks
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, nvo3@ietf.org
Message-Id: <20170526153656.5D8E9B81D9D@rfc-editor.org>
Date: Fri, 26 May 2017 08:36:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/hf9o4gv324ZxpKJ5vTcnCu51B90>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 26 May 2017 15:37:32 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8151

        Title:      Use Cases for Data Center 
                    Network Virtualization Overlay Networks 
        Author:     L. Yong, L. Dunbar,
                    M. Toy, A. Isaac,
                    V. Manral
        Status:     Informational
        Stream:     IETF
        Date:       May 2017
        Mailbox:    lucy.yong@huawei.com, 
                    Linda.dunbar@huawei.com, 
                    mehmet.toy@verizon.com,
                    aldrin.isaac@gmail.com, 
                    vishwas@nanosec.io
        Pages:      16
        Characters: 34962
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-nvo3-use-case-17.txt

        URL:        https://www.rfc-editor.org/info/rfc8151

        DOI:        10.17487/RFC8151

This document describes Network Virtualization over Layer 3
(NVO3) use cases that can be deployed in various data
centers and serve different data-center applications.

This document is a product of the Network Virtualization Overlays Working Group of the IETF.


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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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