# Networking WG newletter #1
**URL:** https://internals.rust-lang.org/t/networking-wg-newletter-1/7431
**Category:** Uncategorized
**Created:** [May 1, 2018, 5:39pm UTC](https://internals.rust-lang.org/t/networking-wg-newletter-1/7431 "2018-05-01T17:39:27Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@aturon](https://internals.rust-lang.org/u/aturon)
#### Post date: [May 1, 2018, 5:39pm UTC](https://internals.rust-lang.org/t/networking-wg-newletter-1/7431/1 "2018-05-01T17:39:27Z")
This is the first newsletter of the new [Networking Services WG](https://internals.rust-lang.org/t/announcing-the-network-services-working-group-wg-net/7354). Our goal for Rust 2018 is to solidify the foundations of the networking story in Rust, including async I/O, shared interfaces, and documentation.
## Updates on async/await
- [The RFC](https://github.com/rust-lang/rfcs/pull/2394) introducing `async`/`await` syntax is in its final comment period and, barring any last-minute issues, should be merged in the next few days! @withoutboats is beginning a preliminary implementation.
- There’s a [new RFC](https://github.com/rust-lang/rfcs/pull/2418) revising our proposal for the standard library support needed for async/await. The main shift is to provide a more gradual migration path toward “pin”-based APIs, which we’re still learning how to work with effectively. @aturon is actively working on a futures 0.3 branch embracing this approach. **Help wanted** : once the foundations are in place, there will be a lot of parallelizable work here; please let @aturon know if you’re interested in helping with futures 0.3!
## Updates on futures
- After a significant amount of discussion, @cramertj landed [a revised channel implementation](https://github.com/rust-lang-nursery/futures-rs/pull/985) that provides a better backpressure story when working with combinators.
- @cramertj also [made a proposal](https://github.com/rust-lang-nursery/net-wg/issues/13#issuecomment-384112189) for future-proofing the default executor system for single-threaded executors. Further comments are welcome!
## Broader discussion
- Several people have asked about low-level networking, e.g. implementation of a TCP stack. The WG would love to assemble a critical mass of folks interested in this space to help drive efforts there and to inform work elsewhere. There’s a [general issue](https://github.com/rust-lang-nursery/net-wg/issues/15) you can use to get discussion going.
## Join in!
You can find ongoing discussion in [the issue tracker](https://github.com/rust-lang-nursery/net-wg/issues) and [the Gitter channel](https://gitter.im/rust-lang/WG-net).
* * *
This newsletter will be released regularly. If you’d like something mentioned in the next instance, please leave a comment [here](https://github.com/rust-lang-nursery/net-wg/issues/16).
---
### Author:  [@jimmycuadra](https://internals.rust-lang.org/u/jimmycuadra)
#### Post date: [May 2, 2018, 5:26am UTC](https://internals.rust-lang.org/t/networking-wg-newletter-1/7431/2 "2018-05-02T05:26:58Z")
I’d be interested to hear more about how to help with futures 0.3.
---
### Author:  [@macronaut](https://internals.rust-lang.org/u/macronaut)
#### Post date: [May 2, 2018, 1:36pm UTC](https://internals.rust-lang.org/t/networking-wg-newletter-1/7431/3 "2018-05-02T13:36:30Z")
Hi. I’m a newbie to Rust (background in C, Objective-C, Swift, and Python). How can I help?
---
### Author:  [@aturon](https://internals.rust-lang.org/u/aturon)
#### Post date: [March 25, 2019, 8:30am UTC](https://internals.rust-lang.org/t/networking-wg-newletter-1/7431/4 "2019-03-25T08:30:08Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.