[rtcweb] Question on draft-ietf-rtcweb-use-cases-and-requirements-14

srivastava_samir@hush.com Fri, 18 April 2014 14:53 UTC

Return-Path: <srivastava_samir@hush.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 2590F1A0303 for <rtcweb@ietfa.amsl.com>; Fri, 18 Apr 2014 07:53:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.799
X-Spam-Status: No, score=0.799 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id jgkMOvkUDEYt for <rtcweb@ietfa.amsl.com>; Fri, 18 Apr 2014 07:53:13 -0700 (PDT)
Received: from smtp2.hushmail.com (smtp2.hushmail.com []) by ietfa.amsl.com (Postfix) with ESMTP id 0474F1A01AF for <rtcweb@ietf.org>; Fri, 18 Apr 2014 07:53:12 -0700 (PDT)
Received: from smtp2.hushmail.com (localhost []) by smtp2.hushmail.com (Postfix) with SMTP id B02A8A0124 for <rtcweb@ietf.org>; Fri, 18 Apr 2014 14:53:08 +0000 (UTC)
X-hush-tls-connected: 1
Received: from smtp.hushmail.com (w9.hushmail.com []) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp2.hushmail.com (Postfix) with ESMTPS for <rtcweb@ietf.org>; Fri, 18 Apr 2014 14:53:08 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99) id 46CB4A039F; Fri, 18 Apr 2014 14:53:08 +0000 (UTC)
MIME-Version: 1.0
Date: Fri, 18 Apr 2014 10:53:08 -0400
To: rtcweb@ietf.org
From: srivastava_samir@hush.com
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20140418145308.46CB4A039F@smtp.hushmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/9F04a3WNNI2Zsfz3R4D2y7k064g
Subject: [rtcweb] Question on draft-ietf-rtcweb-use-cases-and-requirements-14
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: Fri, 18 Apr 2014 14:53:14 -0000


  I am new to rtcweb so pl excuse my lack of knowledge. 
1)  Refer 
   F33     The browser must be able to initiate and
           accept a media session where the data needed
           for establishment can be carried in SIP.

   In other places in other documents it is stated that browser is 
given freedom to do signaling it likes. Then this requirement will 
be met with signaling gateway. And there is no work in progress for 
that. Whether IETF mandates for browser to understand SIP or not?

2) It will be better if 1-800-Go-Fedex (Fedex call) is referred as 
IVR call and Fedex should be taken out as SKYPE was taken out.