FW: WG Review: BGP Enabled Services (bess)

"Adrian Farrel" <adrian@olddog.co.uk> Fri, 03 October 2014 16:30 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AEB91A0390; Fri, 3 Oct 2014 09:30:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level:
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=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 8lh6MAAlhyXd; Fri, 3 Oct 2014 09:30:21 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1A4D1A0379; Fri, 3 Oct 2014 09:30:20 -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 s93GUI1E016430; Fri, 3 Oct 2014 17:30:18 +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 s93GUH4p016410 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 3 Oct 2014 17:30:18 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: routing-discussion@ietf.org, l2vpn@ietf.org, l3vpn@ietf.org, nvo3@ietf.org
References: <20141003153712.10842.27062.idtracker@ietfa.amsl.com>
In-Reply-To: <20141003153712.10842.27062.idtracker@ietfa.amsl.com>
Subject: FW: WG Review: BGP Enabled Services (bess)
Date: Fri, 03 Oct 2014 17:30:12 +0100
Message-ID: <0a9e01cfdf27$4edfeb90$ec9fc2b0$@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: AQHHpq1sE18ASYmn/XZhikB1G5mQQZwvAJqg
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1018-20994.000
X-TM-AS-Result: No--16.231-10.0-31-10
X-imss-scan-details: No--16.231-10.0-31-10
X-TMASE-MatchedRID: rqmDq8+jU9O68Mln9Nwu0y/MZ1E/Ptpxt3aeg7g/usAutoY2UtFqGEvV O7EcQqdbJmLqKu2yqdnvkzitR82DjT+YkS80Uv51CFaAixm5eU+Hxi2fvkKUM0SVpnjjB2vkwRz 9azOIZGMlpVclvjJJDCTmHbEJ0nNdeYojpvrZ9+cS3RGfZcILv6SrVYfmfZT8Ed+K6O5Nt53zb5 kmgp405TmoOWEBgQUvShDPPqb0JNqCLUZ3A9cbBWgws6g0ewz2lnrMq7Sriu3jsTquy0JRi+sDA +IumPfLMiP3JgLmy75SQfAAka0pZqoDZpNjSrDV1x307doliZvomPrNi98UBPgnJH5vm2+gNTDt WcfAQQpR8ca2I5imNDobWbmQlX1eX/LM4Em7bYIx87MtvE/hlZqCl1R34jDPOcqlsYvgKFXeDaw 3ixkM75zRNqTUNarR1GzjMWYTqTl+HQEHIpIak691/YHX0i1lfS0Ip2eEHny+qryzYw2E8M8943 oc3p3sq7rFUcuGp/EgBwKKRHe+rzNvLsMhxFYGMHRy6p/Q3pO5ZDbVa/ELbdAYjCh7rOTCcTlGM E7gGsw=
Archived-At: http://mailarchive.ietf.org/arch/msg/l3vpn/k6QE_7XPONpZ5jl0h9BBMjY_hw4
Cc: idr@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn/>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Oct 2014 16:30:23 -0000

Heads-up.

BESS charter is in IETF-wide review.

Adrian

> -----Original Message-----
> From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The
> IESG
> Sent: 03 October 2014 16:37
> To: IETF-Announce
> Cc: bess WG
> Subject: WG Review: BGP Enabled Services (bess)
> 
> A new IETF working group has been proposed in the Routing Area. The IESG
> has not made any determination yet. The following draft charter was
> submitted, and is provided for informational purposes only. Please send
> your comments to the IESG mailing list (iesg at ietf.org) by 2014-10-13.
> 
> BGP Enabled Services (bess)
> ------------------------------------------------
> Current Status: Proposed WG
> 
> Assigned Area Director:
>   Adrian Farrel <adrian@olddog.co.uk>
> 
> Mailing list
>   Address: bess@ietf.org
>   To Subscribe: https://www.ietf.org/mailman/listinfo/bess
>   Archive: http://www.ietf.org/mail-archive/web/bess/
> 
> Charter:
> 
> BGP is established as a protocol for provisioning and operating Layer-3
> (routed) Virtual Private Networks (L3VPNs). It is also used in certain
> Layer-2  Virtual Private Networks (L2VPNs).
> 
> The BGP Enabled Services (BESS) working group is responsible for
> defining, specifying, and extending network services based on BGP. In
> particular, the working group will work on the following services:
> 
>  - BGP/MPLS IP VPN solutions (based on RFC4364 and RFC4659) for
>    supporting provider-provisioned L3VPNs including methods for enabling
>    multicast over BGP/MPLS VPNs.
> 
>  - BGP-enabled L2VPNs (as described in RFC 4664) that operate over IP or
>    MPLS packet switched network tunnels. All types of L2VPN are in scope
>    provided they utilize BGP for discovery, signaling, or for some other
>    purposes related to the VPN. But L2VPN solutions that operate over
>    pseudowires or use LDP and that do not utilize BGP will be addressed
>    by the PALS working group. Any contention in placement of the work
>    between these working groups will be resolved by the chairs.
> 
>  - BGP-enabled VPN solutions for use in the data center networking.
>    This work includes consideration of VPN scaling issues and
>    mechanisms applicable to such environments.
> 
>  - Extensions to BGP-enabled VPN solutions for the construction of
>    virtual topologies in support of services such as Service Function
>    Chaining.
> 
> The working group may also suggest new services to be supported by BGP
> and these may be added to the working group charter subject to
> rechartering.
> 
> The working group may work on:
> 
>  - Mechanisms to support BGP-enabled services in the presence of multi-
>    homing of Customer Edge (CE) devices to multiple Provider Edge (PE)
>    devices to provide load-balancing and resilience.
> 
>  - Auto-discovery of sites that participate in the BGP-enabled service.
> 
>  - Data models for modeling, managing, and operating BGP-based services
>    using SMI or YANG.
> 
>  - OAM or resiliency mechanisms operating over BGP-enabled services. But
>    native data plane OAM mechanisms may be worked on only in conjunction
>    with the working groups responsible for the relevant data planes.
> 
>  - Extensions to BGP and extensions to YANG models for BGP. All such
>    work must be reviewed by the IDR WG, but the decision to request
>    publication of such work remains with the BESS WG.
> 
> The working group will also coordinate with other working groups where
> appropriate. For example, with the MPLS working group for issues
> related to the MPLS architecture, and the NVO3 working group for
> coordination of protocols to support data center VPNs.
> 
> The BESS working group will not define new data plane or forwarding
> plane encapsulations.
> 
> Milestones: