[rtcweb] New Version Notification for draft-cheng-rtcweb-teleauth-00.txt

齐旻鹏 <qiminpeng@chinamobile.com> Wed, 19 February 2014 09:13 UTC

Return-Path: <qiminpeng@chinamobile.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id B49DB1A0396 for <rtcweb@ietfa.amsl.com>; Wed, 19 Feb 2014 01:13:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.074
X-Spam-Status: No, score=0.074 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RELAY_IS_221=2.222, RP_MATCHES_RCVD=-0.548] autolearn=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id k8n1xxPuDBRt for <rtcweb@ietfa.amsl.com>; Wed, 19 Feb 2014 01:13:07 -0800 (PST)
Received: from cmccmta.chinamobile.com (cmccmta.chinamobile.com []) by ietfa.amsl.com (Postfix) with SMTP id 33C851A037C for <rtcweb@ietf.org>; Wed, 19 Feb 2014 01:13:06 -0800 (PST)
Received: from spf.mail.chinamobile.com (unknown[]) by rmmx-oa_allagent02-12002 (RichMail) with SMTP id 2ee25304751496f-6f96f; Wed, 19 Feb 2014 17:10:45 +0800 (CST)
X-RM-TRANSID: 2ee25304751496f-6f96f
Received: from [] (unknown[]) by rmsmtp-oa_rmapp02-12002 (RichMail) with SMTP id 2ee2530475146b8-0c303; Wed, 19 Feb 2014 17:10:45 +0800 (CST)
X-RM-TRANSID: 2ee2530475146b8-0c303
From: 齐旻鹏 <qiminpeng@chinamobile.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 19 Feb 2014 17:14:45 +0800
Message-Id: <9BD45388-7675-4165-82D7-ED4BE518BDED@chinamobile.com>
To: rtcweb@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/bY7VYGzNEykSBRLaG5loyUdXxqM
Subject: [rtcweb] New Version Notification for draft-cheng-rtcweb-teleauth-00.txt
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 09:13:14 -0000

Dear all,

We have submit a draft about authentication for WebRTC telephony terminal use-case. 
Your attention and comments are welcome.

A new version of I-D, draft-cheng-rtcweb-teleauth-00.txt
has been successfully submitted by Minpeng Qi and posted to the
IETF repository.

Name:		draft-cheng-rtcweb-teleauth
Revision:	00
Title:		Security Authentication of WebRTC Communication Service for Telephony Terminal
Document date:	2014-02-08
Group:		Individual Submission
Pages:		12
URL:            http://www.ietf.org/id/draft-cheng-rtcweb-teleauth-00.txt
Status:         https://datatracker.ietf.org/doc/draft-cheng-rtcweb-teleauth
Htmlized:       http://tools.ietf.org/html/draft-cheng-rtcweb-teleauth-00

   The WebRTC use-cases and related requirements are defined in
   [draft-ietf-rtcweb-use-cases-and-requirements] that contains browser to
   browser use-cases and browser-GW/server use-cases (e.g., telephony
   terminal). In the use-case of telephony terminal, it is necessary for
   telephony terminal to be able to attest his identity to the telephony
   operator. Unlike the current authentication specified in
   [draft-ietf-rtcweb-security] such as PKI based authentication and web
   based peer authentication WebRTC communication is directly controlled
   by the telephony operator, which poses new authentication methods,
   including re-using existence authentication mechanism of telephony
   operator and authentication by using web credentials. This document
   presents the security authentication of WebRTC communication for
   telephony terminal.