[OPSAWG] FW: New Version Notification for draft-pularikkal-opsawg-wifi-calling-02.txt

"Byju Pularikkal (byjupg)" <byjupg@cisco.com> Fri, 17 March 2017 05:59 UTC

Return-Path: <byjupg@cisco.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E36761201F2 for <opsawg@ietfa.amsl.com>; Thu, 16 Mar 2017 22:59:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 IGKsfSVDKieQ for <opsawg@ietfa.amsl.com>; Thu, 16 Mar 2017 22:59:07 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2744E127F0E for <opsawg@ietf.org>; Thu, 16 Mar 2017 22:59:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2362; q=dns/txt; s=iport; t=1489730347; x=1490939947; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=uv1NvIGGGBJkU6q6hBEaNrrpUEK5Nf+aL8//XTpZk3o=; b=aVKDo+cxKd9GR6YmnLRwxX4N13BxYmQeEpl1fiwSWDkT1GSKtM3xIE1o sWjwk4fYDBjn8GKIMUVvELWfRYSq9ZF2FvXnRqqOQ5T4jWjKjSBIzcbu2 89olNn8oWScWv8iS1MFQEQFYUXD1mK/A8ODsCb0JFixrNHNPeF7qLu7Aq I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AVAQCIestY/4wNJK1dGQEBAQEBAQEBAQEBBwEBAQEBg1FhgQoHjWqnF4IOLIV2AoMHPxgBAgEBAQEBAQFrHQuFFgMDOi0KBgIQAgEINhAyGwEGAwIEDgUUB4llDrNZilIBAQEBAQEBAQIBAQEBAQEBAQEBHos9gxeHIgWPW4xqAYZ2i0eBe1SEVIoGk0wBHziBBFgVGIcAdYhKgQ0BAQE
X-IronPort-AV: E=Sophos;i="5.36,175,1486425600"; d="scan'208";a="219318028"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 17 Mar 2017 05:59:06 +0000
Received: from XCH-RCD-006.cisco.com (xch-rcd-006.cisco.com [173.37.102.16]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v2H5x6mn004959 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 17 Mar 2017 05:59:06 GMT
Received: from xch-rcd-005.cisco.com (173.37.102.15) by XCH-RCD-006.cisco.com (173.37.102.16) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 17 Mar 2017 00:59:05 -0500
Received: from xch-rcd-005.cisco.com ([173.37.102.15]) by XCH-RCD-005.cisco.com ([173.37.102.15]) with mapi id 15.00.1210.000; Fri, 17 Mar 2017 00:59:05 -0500
From: "Byju Pularikkal (byjupg)" <byjupg@cisco.com>
To: "opsawg@ietf.org" <opsawg@ietf.org>
CC: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>, Tommy Pauly <tpauly@apple.com>
Thread-Topic: New Version Notification for draft-pularikkal-opsawg-wifi-calling-02.txt
Thread-Index: AQHSjueFgU7g3QyVJU6Tk6GNH/Ovs6GYiEgA
Date: Fri, 17 Mar 2017 05:59:05 +0000
Message-ID: <D4F0C819.6C8A0%byjupg@cisco.com>
References: <148797281462.3167.18126508069542557298.idtracker@ietfa.amsl.com>
In-Reply-To: <148797281462.3167.18126508069542557298.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.2.160219
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.182.87]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4918E6AA795BF844A158CBAD71FC7B78@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/43lDU5u80E5rk3PmL15gnpNpscU>
Subject: [OPSAWG] FW: New Version Notification for draft-pularikkal-opsawg-wifi-calling-02.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Mar 2017 05:59:10 -0000

Dear working group members,
Kindly request some feedback from the community on the following work
item. This covers deployment scenarios and some best practice
recommendations for Carrier Wi-Fi calling. We do see lot of relevance in
the industry on this topic, as many mobile carriers have deployed the
solution and it is also triggering partnerships between Mobile Carriers
and Wi-Fi Service Providers.

Appreciate your time in reviewing this and providing some feedback on the
content prior to IETF 98

Regards

Byju

On 2/24/17, 1:46 PM, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
wrote:

>
>A new version of I-D, draft-pularikkal-opsawg-wifi-calling-02.txt
>has been successfully submitted by Byju Pularikkal and posted to the
>IETF repository.
>
>Name:		draft-pularikkal-opsawg-wifi-calling
>Revision:	02
>Title:		Carrier Wi-Fi Calling Deployment Considerations
>Document date:	2017-02-24
>Group:		Individual Submission
>Pages:		26
>URL:            
>https://www.ietf.org/internet-drafts/draft-pularikkal-opsawg-wifi-calling-
>02.txt
>Status:         
>https://datatracker.ietf.org/doc/draft-pularikkal-opsawg-wifi-calling/
>Htmlized:       
>https://tools.ietf.org/html/draft-pularikkal-opsawg-wifi-calling-02
>Diff:           
>https://www.ietf.org/rfcdiff?url2=draft-pularikkal-opsawg-wifi-calling-02
>
>Abstract:
>   Carrier Wi-Fi Calling is a solution that allows mobile operators to
>   seamlessly offload mobile voice signaling and bearer traffic onto Wi-
>   Fi access networks, which may or may not be managed by the mobile
>   operators.  Mobile data offload onto Wi-Fi access networks has
>   already become very common, as Wi-Fi access has become more
>   ubiquitous.  However, the offload of mobile voice traffic onto Wi-Fi
>   networks has become prevalent only in recent years.  This was
>   primarily driven by the native Wi-Fi Calling client support
>   introduced by device vendors.  The objective of this document is to
>   provide a high level deployment reference to Mobile Operators and Wi-
>   Fi Operators on Carrier Wi-Fi Calling.
>
>                  
>        
>
>
>Please note that it may take a couple of minutes from the time of
>submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>The IETF Secretariat
>