[core] Fwd: New Version Notification for draft-groves-coap-webrtcdc-00.txt

Christian Groves <Christian.Groves@nteczone.com> Tue, 05 July 2016 00:30 UTC

Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E134F12B02E for <core@ietfa.amsl.com>; Mon, 4 Jul 2016 17:30:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level:
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=nteczone.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 fLtxrnTPni1S for <core@ietfa.amsl.com>; Mon, 4 Jul 2016 17:30:42 -0700 (PDT)
Received: from msh03.myshophosting.com (msh03.myshophosting.com [101.0.109.158]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4629E12B00A for <core@ietf.org>; Mon, 4 Jul 2016 17:30:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=nteczone.com; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:To:References:Subject:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=4IQ/KCvxYVeXFZF4L10X1MIovybcT/abfrfUrgVjqh4=; b=gUUVm82MFeiQa50bKE0orNXGQc 8mgfWreAeZ4jTEv+Enhy7vzAK1Ms/O9joGFys0sv4i5MCXaDDS3O2IGsGeA9XokRQnrxMIv+jdLc7 +dblkowg33nQuIH/ib8g7pgTwPdmsn+XPAmpT5lB4bEyVNJ0uf5ix4foeTRCzTWFnb93iZInPDUcK 88l904Zwotzt9fwSUy1hH7EBZyJqxI9xFYlUGGKwuuLt5UM2d8A7TvzW5RFTJ5KjpP6dlThSzAByi kZ3m+tNpyZTVepAtKRnOi6jTVnkDA6BCu7ZpG5rMtn/4JqxWMc5GVUtFBCXVtGvi72DW4SkLd0fQB 0+vL7Bww==;
Received: from ppp118-209-41-225.lns20.mel4.internode.on.net ([118.209.41.225]:50087 helo=[192.168.1.22]) by msh03.myshophosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <Christian.Groves@nteczone.com>) id 1bKEG7-002pke-Sd for core@ietf.org; Tue, 05 Jul 2016 10:30:39 +1000
References: <20160705001738.2578.25202.idtracker@ietfa.amsl.com>
To: core <core@ietf.org>
From: Christian Groves <Christian.Groves@nteczone.com>
X-Forwarded-Message-Id: <20160705001738.2578.25202.idtracker@ietfa.amsl.com>
Message-ID: <0257c801-317d-7432-7c79-1c4c5ee533c3@nteczone.com>
Date: Tue, 05 Jul 2016 10:30:38 +1000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <20160705001738.2578.25202.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - msh03.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: msh03.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Authenticated-Sender: msh03.myshophosting.com: christian.groves@nteczone.com
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/nHBJXRPFs73nim8pduquWty1gH8>
Subject: [core] Fwd: New Version Notification for draft-groves-coap-webrtcdc-00.txt
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2016 00:30:45 -0000

Hello all,

FYI, to throw another transport in the CoAP transport mix I've developed 
a draft looking at transport of CoAP over a WebRTC data channels.

I think what's interesting in the transport discussions is to what 
extent the CoAP "transport functions" are replaced by the underlying 
transport and also whether CoAP messages are optimised for message 
transmission or ease of interworking. Several author's notes touch on 
issues related to these aspects.

Regards, Christian



-------- Forwarded Message --------
Subject: 	New Version Notification for draft-groves-coap-webrtcdc-00.txt
Date: 	Mon, 04 Jul 2016 17:17:38 -0700
From: 	internet-drafts@ietf.org
To: 	Christian Groves <Christian.Groves@nteczone.com>, Weiwei Yang 
<tommy@huawei.com>



A new version of I-D, draft-groves-coap-webrtcdc-00.txt
has been successfully submitted by Christian Groves and posted to the
IETF repository.

Name:		draft-groves-coap-webrtcdc
Revision:	00
Title:		A WebRTC Data Channel Transport for the Constrained Application Protocol (CoAP)
Document date:	2016-07-04
Group:		Individual Submission
Pages:		22
URL:            https://www.ietf.org/internet-drafts/draft-groves-coap-webrtcdc-00.txt
Status:         https://datatracker.ietf.org/doc/draft-groves-coap-webrtcdc/
Htmlized:       https://tools.ietf.org/html/draft-groves-coap-webrtcdc-00


Abstract:
    The WebRTC framework defines a generic transport service allowing
    WEB-browsers and other endpoints to exchange generic data from peer
    to peer utilizing a Stream Control Transmission Protocol (SCTP)
    transport.  This service is known as Web Real Time Communication
    WebRTC data channels (WebRTC DC).  The use of WebRTC DCs for the
    Constrained Application Protocol (CoAP) allows WebRTC enabled devices
    to exchange CoAP data between peers in a secure reliable manner.

                                                                                   


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