From adrian@olddog.co.uk Wed Jan 29 11:09:03 2014 Return-Path: X-Original-To: routing-discussion@ietfa.amsl.com Delivered-To: routing-discussion@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C93D1A0383 for ; Wed, 29 Jan 2014 11:09:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.553 X-Spam-Level: X-Spam-Status: No, score=-0.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 z-0hmNgqGOIz for ; Wed, 29 Jan 2014 11:09:02 -0800 (PST) Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id CFBA81A02B6 for ; Wed, 29 Jan 2014 11:09:01 -0800 (PST) Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s0TJ8wrA026701 for ; Wed, 29 Jan 2014 19:08:58 GMT Received: from 950129200 (110.26.90.92.rev.sfr.net [92.90.26.110]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s0TJ8uLY026686 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 29 Jan 2014 19:08:57 GMT From: "Adrian Farrel" To: Subject: FW: BOF on Transport Services (TAPS) Date: Wed, 29 Jan 2014 19:08:55 -0000 Message-ID: <01d201cf1d25$8f3ba540$adb2efc0$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac8dJXdm8pj2OWJpTtGjJ+qN2Vcmkg== Content-language: en-gb X-TM-AS-MML: No X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Routing Area General mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jan 2014 19:09:03 -0000 Some folk maybe don't realise, but routing is a consumer of transport services (wow, layer inversion or what?) You might be interested in this BoF and the mail below originally sent to encourage participation by the Applications community. Adrian > -----Original Message----- > From: apps-discuss [mailto:apps-discuss-bounces@ietf.org] On Behalf Of Michael > Welzl > Sent: 29 January 2014 14:40 > To: apps-discuss@ietf.org > Subject: [apps-discuss] BOF on Transport Services (TAPS) > > Dear all, > > A BOF called "TAPS" has been approved as a non-WG-forming BOF in London. > The point of this activity is to move away from applications choosing "TCP" or > "UDP" by letting them select a service instead. This is bound to let the transport > layer evolve - details are at: > https://sites.google.com/site/transportprotocolservices/ > > Much of this is about the API that the transport layer exposes to applications. We > had a bar BOF in Vancouver, where the major criticism was that we might be > ignoring what applications *really* want, as many aren't really using the socket > layer anyway. We're trying to counter this criticism as good as we can, because > we really do want to do something useful here, something that does help > applications. e.g., if the socket layer provided a richer set of services than "TCP" > and "UDP", some of these services might be reasonably replicated in higher-level > APIs; also, these higher-level APIs could be improved by using a richer set of > services underneath - we've begun analyzing some in draft-hurtig-tsvwg- > transport-apis > > What's more, if there was a common API that's independent of the transport > protocol, it wouldn't be necessary to implement functions like PMTUD, things for > middlebox traversal etc. in the application per protocol, but these functions could > be taken care of underneath the API, leading to a better integrated networking > stack. > > At this point, I'm hoping for folks from the applications area to join our mailing list > and participate in discussions - raise your concerns there and help us create > something that will really be useful. the list management page is at: > https://sympa.uio.no/ifi.uio.no/info/transport-services > > Cheers, > Michael > > _______________________________________________ > apps-discuss mailing list > apps-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/apps-discuss