[L2sm] Alia Atlas' No Objection on charter-ietf-l2sm-00-01: (with COMMENT)

"Alia Atlas" <akatlas@gmail.com> Thu, 13 October 2016 13:19 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: l2sm@ietf.org
Delivered-To: l2sm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 58DED129454; Thu, 13 Oct 2016 06:19:56 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Alia Atlas" <akatlas@gmail.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.34.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147636479632.2894.7376748604935262928.idtracker@ietfa.amsl.com>
Date: Thu, 13 Oct 2016 06:19:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/dE4QMxw0hIg1jNoZsfptV0_olMk>
Cc: l2sm-chairs@ietf.org, l2sm@ietf.org
Subject: [L2sm] Alia Atlas' No Objection on charter-ietf-l2sm-00-01: (with COMMENT)
X-BeenThere: l2sm@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" <l2sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2sm>, <mailto:l2sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l2sm/>
List-Post: <mailto:l2sm@ietf.org>
List-Help: <mailto:l2sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2sm>, <mailto:l2sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Oct 2016 13:19:56 -0000

Alia Atlas has entered the following ballot position for
charter-ietf-l2sm-00-01: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-l2sm/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I am surprised not to see EVPN included in the list of technologies,
since it is a replacement for VPLS.
I understand that the service model should be fairly technology
independent, but if it can't handle EVPN,
that'll be an issue.   Could you please update it to at least mention
EVPN as one of the technologies?