RFC 8975 on Network Coding for Satellite Systems
rfc-editor@rfc-editor.org Fri, 22 January 2021 17:23 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 495E53A1395 for <ietf-announce@ietfa.amsl.com>; Fri, 22 Jan 2021 09:23:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=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 6ImjMbaTmy12 for <ietf-announce@ietfa.amsl.com>; Fri, 22 Jan 2021 09:23:50 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F01033A12A9 for <ietf-announce@ietf.org>; Fri, 22 Jan 2021 09:23:49 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 0D39AF40758; Fri, 22 Jan 2021 09:23:31 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org
Subject: RFC 8975 on Network Coding for Satellite Systems
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, nwcrg@irtf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210122172331.0D39AF40758@rfc-editor.org>
Date: Fri, 22 Jan 2021 09:23:31 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/IAvQ-ODtpwrPYT66jAuxdA3vwLw>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 17:23:56 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8975
Title: Network Coding for Satellite Systems
Author: N. Kuhn, Ed.,
E. Lochin, Ed.
Status: Informational
Stream: IRTF
Date: January 2021
Mailbox: nicolas.kuhn@cnes.fr,
emmanuel.lochin@enac.fr
Pages: 14
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-irtf-nwcrg-network-coding-satellites-15.txt
URL: https://www.rfc-editor.org/info/rfc8975
DOI: 10.17487/RFC8975
This document is a product of the Coding for Efficient Network
Communications Research Group (NWCRG). It conforms to the directions
found in the NWCRG taxonomy (RFC 8406).
The objective is to contribute to a larger deployment of Network
Coding techniques in and above the network layer in satellite
communication systems. This document also identifies open research
issues related to the deployment of Network Coding in satellite
communication systems.
This document is a product of the Coding for Efficient Network Communications Research Group of the IRTF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce, rfc-dist and IRTF-Announce lists.To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
https://www.irtf.org/mailman/listinfo/irtf-announce
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC