RFC 7778 on Mobile Communication Congestion Exposure Scenario
rfc-editor@rfc-editor.org Sat, 12 March 2016 00:07 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 6553B12DDD5; Fri, 11 Mar 2016 16:07:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.923
X-Spam-Level:
X-Spam-Status: No, score=-106.923 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 pOrpVj2rcJaH; Fri, 11 Mar 2016 16:07:35 -0800 (PST)
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 E8B3812DDE5; Fri, 11 Mar 2016 16:07:01 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 45F0D187E25; Fri, 11 Mar 2016 16:06:38 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7778 on Mobile Communication Congestion Exposure Scenario
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160312000638.45F0D187E25@rfc-editor.org>
Date: Fri, 11 Mar 2016 16:06:38 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/aCWPHV1q8bIhrqOZciTRwVtPSJw>
Cc: drafts-update-ref@iana.org, conex@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 12 Mar 2016 00:07:39 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7778
Title: Mobile Communication Congestion Exposure Scenario
Author: D. Kutscher, F. Mir,
R. Winter, S. Krishnan,
Y. Zhang, CJ. Bernardos
Status: Informational
Stream: IETF
Date: March 2016
Mailbox: kutscher@neclab.eu,
faisal.mir@gmail.com,
rolf.winter@neclab.eu,
suresh.krishnan@ericsson.com,
ying.zhang13@hp.com,
cjbc@it.uc3m.es
Pages: 25
Characters: 56883
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-conex-mobile-06.txt
URL: https://www.rfc-editor.org/info/rfc7778
DOI: http://dx.doi.org/10.17487/RFC7778
This memo describes a mobile communications use case for congestion
exposure (ConEx) with a particular focus on those mobile
communication networks that are architecturally similar to the 3GPP
Evolved Packet System (EPS). This memo provides a brief overview of
the architecture of these networks (both access and core networks)
and current QoS mechanisms and then discusses how congestion exposure
concepts could be applied. Based on this discussion, this memo
suggests a set of requirements for ConEx mechanisms that particularly
apply to these mobile networks.
This document is a product of the Congestion Exposure 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