[L3sm] draft-ietf-l3sm-l3vpn-service-model feedback

Benoit Claise <bclaise@cisco.com> Mon, 06 July 2015 11:13 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: l3sm@ietfa.amsl.com
Delivered-To: l3sm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EACC01A01E7 for <l3sm@ietfa.amsl.com>; Mon, 6 Jul 2015 04:13:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.91
X-Spam-Level:
X-Spam-Status: No, score=-13.91 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, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 VW2txEUhfnHu for <l3sm@ietfa.amsl.com>; Mon, 6 Jul 2015 04:13:53 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EDB061A01AA for <l3sm@ietf.org>; Mon, 6 Jul 2015 04:13:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2118; q=dns/txt; s=iport; t=1436181233; x=1437390833; h=to:from:subject:message-id:date:mime-version; bh=46+zU9/JpvrFJYnVgE883x6PJ52pRKF0pPaLpq1ntFc=; b=cBRv1B2gLGyoTXEpowL7w66A67D15zuLIm59Tj1+cBNgxmkZJnc0o623 ZPP83+Z+rT4VuneEFEhfVssCtTkg+uoI3Nvt1hdIC/B7/GO488UmfNFaA by6baIhr60G5c39nFw4AX2Y8MewyKhCxv/2+3+ZrVLy4J6S5ITCxEZ7sS U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D4BAAQYppV/xbLJq1cg2aDf7wqhXuBaBEBAQEBAQEBgQqETVUgARwWCwILAwIBAgFLDQgBAYgqDaJaj1+VcgEBAQcBAQEBGgSPeFWCc4FDBZQVhGKHBog8kBomghEXgVU8gTWBRwEBAQ
X-IronPort-AV: E=Sophos;i="5.15,414,1432598400"; d="scan'208,217";a="556758003"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 06 Jul 2015 11:13:50 +0000
Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t66BDnp6011153 for <l3sm@ietf.org>; Mon, 6 Jul 2015 11:13:49 GMT
To: "l3sm@ietf.org" <l3sm@ietf.org>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <559A62ED.9060001@cisco.com>
Date: Mon, 06 Jul 2015 13:13:49 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.0.1
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------060908060704070601010207"
Archived-At: <http://mailarchive.ietf.org/arch/msg/l3sm/JGhnjl5q617unHiFpEsMI-BJADc>
Subject: [L3sm] draft-ietf-l3sm-l3vpn-service-model feedback
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: L3VPN Service YANG Model discussion group <l3sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3sm>, <mailto:l3sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l3sm/>
List-Post: <mailto:l3sm@ietf.org>
List-Help: <mailto:l3sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3sm>, <mailto:l3sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jul 2015 11:13:55 -0000

Dear authors,

Thanks for posting draft-ietf-l3sm-l3vpn-service-model.
 From the abstract, I see:

    This document defines a YANG data model that can be used to deliver a
    Layer 3 Provider Provisioned VPN service.  The document is limited to
    the BGP PE-based VPNs as described inRFC4110 <https://tools.ietf.org/html/rfc4110>  andRFC4364 <https://tools.ietf.org/html/rfc4364>.

I wonder:  What is specific to BGP PE-based VPNs in this YANG model?
 From the L3SM charter, "Instead it contains the characteristics of the 
service, as discussed between the operators and their customers."
"Do you want a BGP PE-based VPNs", is this a typical question that 
operators ask to the customers?

Regards, Benoit