idnits 2.17.1 draft-mcquistin-augmented-udp-example-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (2 November 2020) is 1269 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Outdated reference: A later version (-13) exists of draft-mcquistin-augmented-ascii-diagrams-07 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group S. McQuistin 3 Internet-Draft V. Band 4 Intended status: Experimental D. Jacob 5 Expires: 6 May 2021 C. S. Perkins 6 University of Glasgow 7 2 November 2020 9 Describing UDP with Augmented Packet Header Diagrams 10 draft-mcquistin-augmented-udp-example-00 12 Abstract 14 This document describes UDP using Augmented Packet Header Diagrams. 15 This document is an example of the Augmented Packet Header Diagram 16 language: it is not intended as a contribution to any ongoing or 17 future work on maintaining or extending UDP. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on 6 May 2021. 36 Copyright Notice 38 Copyright (c) 2020 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 43 license-info) in effect on the date of publication of this document. 44 Please review these documents carefully, as they describe your rights 45 and restrictions with respect to this document. Code Components 46 extracted from this document must include Simplified BSD License text 47 as described in Section 4.e of the Trust Legal Provisions and are 48 provided without warranty as described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 2. UDP Header . . . . . . . . . . . . . . . . . . . . . . . . . 2 54 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 55 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 56 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 57 6. Informative References . . . . . . . . . . . . . . . . . . . 3 58 Appendix A. Source code repository . . . . . . . . . . . . . . . 3 59 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 3 61 1. Introduction 63 This document uses Augmented Packet Header Diagrams 64 [AUGMENTED-DIAGRAMS] to describe UDP [RFC768], and is intended to 65 further discussion about the design and implementation of the 66 Augmented Packet Header Diagram language and tooling. Given this 67 purpose, this document is not intended as a contribution to any 68 ongoing or future work on maintaining or extending UDP. Further, 69 this document does not necessarily reflect UDP, and its extensions, 70 as presently standardised. 72 2. UDP Header 74 This document describes the UDP protocol. The UDP protocol uses UDP 75 Headers. 77 A UDP Header is formatted as follows: 79 0 1 2 3 80 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 81 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 82 | Source port | Destination port | 83 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 84 | Length | Checksum | 85 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 86 | : 87 : Payload : 88 : | 89 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 91 where: 93 Source port (Src): 2 bytes. Sending port. 95 Destination port (Dest): 2 bytes. Destination port. 97 Length (L): 2 bytes; L >= 8. Length of the header and payload in 98 bytes. 100 Checksum: 2 bytes. Checksum is the 16-bit one's complement of the 101 one's complement sum of a pseudo header of information from the IP 102 header, the UDP header, and the data, padded with zero octets at 103 the end (if necessary) to make a multiple of two octets. 105 Payload: L-8 bytes. The payload of the UDP datagram, which is the 106 whose size is the value of the Length field, less 8 bytes for the 107 header. 109 3. IANA Considerations 111 This document contains no actions for IANA. 113 4. Security Considerations 115 The security implications of the Augmented Packet Header Diagrams 116 format are considered in [AUGMENTED-DIAGRAMS]. 118 5. Acknowledgements 120 This work has received funding from the UK Engineering and Physical 121 Sciences Research Council under grant EP/R04144X/1. 123 6. Informative References 125 [AUGMENTED-DIAGRAMS] 126 McQuistin, S., Band, V., Jacob, D., and C. S. Perkins, 127 "Describing Protocol Data Units with Augmented Packet 128 Header Diagrams", Work in Progress, Internet-Draft, draft- 129 mcquistin-augmented-ascii-diagrams-07, 2 November 2020, 130 . 133 [RFC768] Postel, J., "User Datagram Protocol", RFC 768, August 134 1980, . 136 Appendix A. Source code repository 138 The source code for tooling that can be used to parse this document, 139 and generate parser code for the protocol it describes, is available 140 from https://github.com/glasgow-ipl/ips-protodesc-code. 142 Authors' Addresses 143 Stephen McQuistin 144 University of Glasgow 145 School of Computing Science 146 Glasgow 147 G12 8QQ 148 United Kingdom 150 Email: sm@smcquistin.uk 152 Vivian Band 153 University of Glasgow 154 School of Computing Science 155 Glasgow 156 G12 8QQ 157 United Kingdom 159 Email: vivianband0@gmail.com 161 Dejice Jacob 162 University of Glasgow 163 School of Computing Science 164 Glasgow 165 G12 8QQ 166 United Kingdom 168 Email: d.jacob.1@research.gla.ac.uk 170 Colin Perkins 171 University of Glasgow 172 School of Computing Science 173 Glasgow 174 G12 8QQ 175 United Kingdom 177 Email: csp@csperkins.org