![]() RFRAG Acknowledgment Dispatch type and Header Recoverable Fragment Dispatch type and Header Updating draft-watteyne-6lo-minimal-fragment Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. ![]() Please review these documents carefully, as they describe your rights and restrictions with respect to this document. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents () in effect on the date of publication of this document. Copyright NoticeĬopyright (c) 2019 IETF Trust and the persons identified as the document authors. This Internet-Draft will expire on July 27, 2019. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. The list of current Internet-Drafts is at. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. ![]() This draft updates RFC 4944 with a simple protocol to recover individual fragments across a route-over mesh network, with a minimal flow control to protect the network against bloat. Draft-ietf-6lo-fragment-recovery-02 Abstract ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |