idnits 2.17.1 draft-perkins-manet-using-rfc6621-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 (March 3, 2016) is 2975 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) == Outdated reference: A later version (-16) exists of draft-ietf-manet-aodvv2-13 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Mobile Ad Hoc Networks [manet] C. Perkins 3 Internet-Draft Futurewei 4 Intended status: Standards Track March 3, 2016 5 Expires: September 4, 2016 7 Using Layer 3 Multicast Suppression Protocols Above Layer 3 8 draft-perkins-manet-using-rfc6621-00.txt 10 Abstract 12 This document specifies how protocols operating at layers above layer 13 3 can use the multicast suppression algorithms, for instance the 14 algorithms specified in RFC 6621. 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on September 4, 2016. 33 Copyright Notice 35 Copyright (c) 2016 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 51 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 52 3. Use of multicast suppression algorithms above Layer 3 . . . . 3 53 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 54 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 55 6. Informative References . . . . . . . . . . . . . . . . . . . 3 56 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 58 1. Introduction 60 Limiting the number of multicast forwarders provides performance 61 benefits when used with a protocol that relies on flooding messages 62 throughout a network. Some good multicast suppression methods for 63 limiting the number of multicast forwarders while maintaining 64 complete network coverage are specified in RFC 6621 [RFC6621]. 65 Routing protocols that use multicast can offer much greater 66 performance using multicast suppression algorithms. Such algorithms 67 do not affect the origination of multicast messages, but only 68 determine whether a node needs to forward incoming multicast messages 69 that are intended to flood the network. Enabling performance 70 benefits for reactive manet routing protocols was a strong motivating 71 factor in the development and publication of RFC 6621. 73 RFC 6621 multicast suppression algorithms are specified to operate at 74 layer 3. Manet routing protocols use RFC 5444 [RFC5444] as a message 75 bundling layer; they operate above layer 3. Such protocols specify 76 that incoming multicast control messages have to be processed before 77 regeneration; in other words, the incoming multicast message is not 78 forwarded at all. Manet control messages are sent with the IP 79 destination address set to the link-local multicast address LL-MANET- 80 Routers [RFC5498] unless otherwise specified. This document 81 specifies a way to use layer 3 multicast suppression algorithms at a 82 layer above layer 3 so that algorithms that require network-wide 83 flooding can reap the benefits of layer-3 multicast suppression 84 algorithms. 86 2. Terminology 88 This document defines the following terminology: 90 Forwarding Node 91 A node that currently forwards incoming multicast messages to its 92 neighbors, based on the results of running a multicast suppression 93 algorithm. 95 Multicast Suppression Algorithm 96 An algorithm that determines which multicast routers are required 97 for complete coverage of a multicast group; retransmission by 98 other multicast routers for the multicast group is unnecessary. 100 Regeneration 101 Transmission of a message formed by processing and modification of 102 an incoming message for an operation requiring the attention of 103 members of a multicast group. 105 3. Use of multicast suppression algorithms above Layer 3 107 If the node is not currently a multicast forwarding node, then the 108 node does not regenerate multicast messages even if the conditions 109 for regeneration are satisfied. 111 For example, if an AODVv2 [I-D.ietf-manet-aodvv2] router is not 112 currently a multicast forwarding node, then it does not regenerate 113 multicast messages (e.g., RREQ or RERR) even if the conditions for 114 regeneration are satisfied. This restriction only applies for 115 regeneration, and does not apply for multicast RREQ or RERR messages 116 originated by the node. 118 4. Security Considerations 120 This document does not introduce any security mechanisms, and does 121 not have any impact on existing security mechanisms. 123 5. IANA Considerations 125 This document does not specify any IANA actions. 127 6. Informative References 129 [I-D.ietf-manet-aodvv2] 130 Perkins, C., Ratliff, S., Dowdell, J., Steenbrink, L., and 131 V. Mercieca, "Ad Hoc On-demand Distance Vector Version 2 132 (AODVv2) Routing", draft-ietf-manet-aodvv2-13 (work in 133 progress), January 2016. 135 [RFC5444] Clausen, T., Dearlove, C., Dean, J., and C. Adjih, 136 "Generalized Mobile Ad Hoc Network (MANET) Packet/Message 137 Format", RFC 5444, DOI 10.17487/RFC5444, February 2009, 138 . 140 [RFC5498] Chakeres, I., "IANA Allocations for Mobile Ad Hoc Network 141 (MANET) Protocols", RFC 5498, DOI 10.17487/RFC5498, March 142 2009, . 144 [RFC6621] Macker, J., Ed., "Simplified Multicast Forwarding", 145 RFC 6621, DOI 10.17487/RFC6621, May 2012, 146 . 148 Author's Address 150 Charles E. Perkins 151 Futurewei Inc. 152 2330 Central Expressway 153 Santa Clara, CA 95050 154 USA 156 Phone: +1-408-330-4586 157 Email: charliep@computer.org