idnits 2.17.1 draft-thubert-lpwan-schc-over-ppp-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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC5172, but the abstract doesn't seem to directly say this. It does mention RFC5172 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. (Using the creation date from RFC5172, updated by this document, for RFC5378 checks: 2007-05-17) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (3 December 2019) is 1600 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Downref: Normative reference to an Informational RFC: RFC 2516 == Outdated reference: A later version (-24) exists of draft-ietf-lpwan-ipv6-static-context-hc-23 Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 LPWAN P. Thubert, Ed. 3 Internet-Draft Cisco Systems 4 Updates: 5172 (if approved) 3 December 2019 5 Intended status: Standards Track 6 Expires: 5 June 2020 8 SCHC over PPP 9 draft-thubert-lpwan-schc-over-ppp-00 11 Abstract 13 This document extends RFC 5172 to signal the use of SCHC as the 14 compression method between a pair of nodes over PPP. Combined with 15 RFC 2516, this enables the use of SCHC over Ethernet and Wi-Fi. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at https://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on 5 June 2020. 34 Copyright Notice 36 Copyright (c) 2019 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 41 license-info) in effect on the date of publication of this document. 42 Please review these documents carefully, as they describe your rights 43 and restrictions with respect to this document. Code Components 44 extracted from this document must include Simplified BSD License text 45 as described in Section 4.e of the Trust Legal Provisions and are 46 provided without warranty as described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 51 2. BCP 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 52 3. Extending RFC 5172 . . . . . . . . . . . . . . . . . . . . . 3 53 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 54 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 55 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 56 7. Normative References . . . . . . . . . . . . . . . . . . . . 4 57 8. Informative References . . . . . . . . . . . . . . . . . . . 4 58 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 60 1. Introduction 62 The Point-to-Point Protocol (PPP) [RFC5172] provides a standard 63 method of encapsulating network-layer protocol information over 64 point-to-point links. "A Method for Transmitting PPP Over Ethernet 65 (PPPoE)" [RFC2516] transports PPP over Ethernet between a pair of 66 nodes. It is compatible with a translating bridge to Wi-Fi, and 67 therefore enables PPP over Wi-Fi as well. 69 PPP also defines an extensible Link Control Protocol, and proposes a 70 family of Network Control Protocols (NCPs) for establishing and 71 configuring different network-layer protocols. "IP Version 6 over 72 PPP" [RFC5072] defines the IPv6 Control Protocol (IPV6CP) , which is 73 an NCP for a PPP link, and allows for the negotiation of desirable 74 parameters for an IPv6 interface over PPP. 76 "Negotiation for IPv6 Datagram Compression Using IPv6 Control 77 Protocol" [RFC5172] defines the IPv6 datagram compression option that 78 can be negotiated by a node on the link through the IPV6CP. The 79 "Static Context Header Compression (SCHC) and fragmentation for 80 LPWAN, application to UDP/IPv6" [SCHC] is a compression and 81 fragmentation technique that was defined after the publication of 82 [RFC5172]. In order to enable SCHC over PPP and therefore Ethernet 83 and Wi-Fi, [RFC5172] must be extended to signal SCHC as an additional 84 compression method for use over PPP. 86 2. BCP 14 88 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 89 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 90 "OPTIONAL" in this document are to be interpreted as described in BCP 91 14 [RFC2119][RFC8174] when, and only when, they appear in all 92 capitals, as shown here. 94 3. Extending RFC 5172 96 [RFC5172] defines an IPV6CP option called the IPv6-Compression- 97 Protocol Configuration option with a type of 2. The option contains 98 an IPv6-Compression-Protocol field value that indicates a compression 99 protocol and an optional data field as shown in Figure 1: 101 0 1 2 3 102 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 103 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 104 | Type | Length | IPv6-Compression-Protocol | 105 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 106 | Data ... 107 +-+-+-+-+ 109 Figure 1: The IPv6-Compression-Protocol Configuration Option 111 This specification indicates a new IPv6-Compression-Protocol field 112 value for [SCHC] (see Section 5, and enables to transport a Uniform 113 Resource Identifier (URI) [RFC3986] of the set of rules in the 114 optional data. The default format for the set of rules is YANG using 115 the "Data Model for SCHC" [SCHC_DATA_MODEL] encoded in JSON as 116 specified in [RFC7951]. If the encoding is asymetrical, the 117 initiator of the session is considered downstream, playing the role 118 of the device in an LPWAN network. 120 4. Security Considerations 122 This draft enables to use the SCHC compression and fragmentation over 123 PPP and therefore Ethernet and Wi-Fi with PPPoE. It inherits the 124 possible threats against SCHC listed in the "Security considerations" 125 section of [SCHC]. 127 5. IANA Considerations 129 This document requests the allocation of a new value in the registry 130 "IPv6-Compression-Protocol Types" for "SCHC". A suggested value is 131 proposed in Table 1: 133 +-------+------------------------------------------+---------------+ 134 | Value | Description | Reference | 135 +=======+==========================================+===============+ 136 | 4 | Static Context Header Compression (SCHC) | This document | 137 +-------+------------------------------------------+---------------+ 139 Table 1: IP Header Compression Configuration Option Suboption Types 141 6. Acknowledgments 143 7. Normative References 145 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 146 Requirement Levels", BCP 14, RFC 2119, 147 DOI 10.17487/RFC2119, March 1997, 148 . 150 [RFC2516] Mamakos, L., Lidl, K., Evarts, J., Carrel, D., Simone, D., 151 and R. Wheeler, "A Method for Transmitting PPP Over 152 Ethernet (PPPoE)", RFC 2516, DOI 10.17487/RFC2516, 153 February 1999, . 155 [RFC5072] Varada, S., Ed., Haskins, D., and E. Allen, "IP Version 6 156 over PPP", RFC 5072, DOI 10.17487/RFC5072, September 2007, 157 . 159 [RFC5172] Varada, S., Ed., "Negotiation for IPv6 Datagram 160 Compression Using IPv6 Control Protocol", RFC 5172, 161 DOI 10.17487/RFC5172, March 2008, 162 . 164 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 165 Resource Identifier (URI): Generic Syntax", STD 66, 166 RFC 3986, DOI 10.17487/RFC3986, January 2005, 167 . 169 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 170 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 171 May 2017, . 173 [SCHC] Minaburo, A., Toutain, L., Gomez, C., Barthel, D., and J. 174 Zuniga, "Static Context Header Compression (SCHC) and 175 fragmentation for LPWAN, application to UDP/IPv6", Work in 176 Progress, Internet-Draft, draft-ietf-lpwan-ipv6-static- 177 context-hc-23, 28 November 2019, 178 . 181 8. Informative References 183 [SCHC_DATA_MODEL] 184 Minaburo, A. and L. Toutain, "Data Model for Static 185 Context Header Compression (SCHC)", Work in Progress, 186 Internet-Draft, draft-ietf-lpwan-schc-yang-data-model-00, 187 23 April 2019, . 190 [RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG", 191 RFC 7951, DOI 10.17487/RFC7951, August 2016, 192 . 194 Author's Address 196 Pascal Thubert (editor) 197 Cisco Systems, Inc 198 Building D, 45 Allee des Ormes - BP1200 199 06254 Mougins - Sophia Antipolis 200 France 202 Phone: +33 497 23 26 34 203 Email: pthubert@cisco.com