[Accord] New Non-WG Mailing List: Accord -- Alternatives to Content Classification for Operator Resource Deployment

IETF Secretariat <ietf-secretariat@ietf.org> Wed, 16 December 2015 19:18 UTC

Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: accord@ietf.org
Delivered-To: accord@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8004C1A88F0; Wed, 16 Dec 2015 11:18:39 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.11.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151216191839.8676.1594.idtracker@ietfa.amsl.com>
Date: Wed, 16 Dec 2015 11:18:39 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/accord/IW9kxoqjEnf0YFmRj--OsM8QNBk>
X-Mailman-Approved-At: Fri, 18 Dec 2015 08:31:45 -0800
Cc: ietf@trammell.ch, ted.ietf@gmail.com, jhildebr@cisco.com, accord@ietf.org
Subject: [Accord] New Non-WG Mailing List: Accord -- Alternatives to Content Classification for Operator Resource Deployment
X-BeenThere: accord@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: Alternatives to Content Classification for Operator Resource Deployment <accord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/accord>, <mailto:accord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/accord/>
List-Post: <mailto:accord@ietf.org>
List-Help: <mailto:accord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/accord>, <mailto:accord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Dec 2015 19:18:39 -0000

A new IETF non-working group email list has been created.

List address: accord@ietf.org
Archive: https://mailarchive.ietf.org/arch/search/?email_list=accord
To subscribe: https://www.ietf.org/mailman/listinfo/accord

Purpose:

Radio Access Networks (RANs) have historically used content-based classification to associate service descriptions with flows and then allocated radio resources based on those services. The increased deployment of encryption in the Internet forces a re-examination of this method. A naive approach would be to have endpoints directly expose classification metadata to the RAN outside the encryption envelope, but this would hinder the confidentiality provided by encryption and require extensive coordination between application developers and RAN operators. To avoid the disadvantages of that approach, this list will discuss both what specific network treatments need to be elicited for the efficient operation of RANs, if any, and what the minimal communication to elicit those treatments would be.

For additional information, please contact the list administrators.