idnits 2.17.1 draft-ietf-pim-proxy-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1.a on line 18. -- Found old boilerplate from RFC 3978, Section 5.5 on line 280. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 257. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 264. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 270. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: This document is an Internet-Draft and is subject to all provisions of Section 3 of RFC 3667. By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 () is 739385 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) == Missing Reference: 'R1' is mentioned on line 113, but not defined == Missing Reference: 'S' is mentioned on line 116, but not defined == Missing Reference: 'R2' is mentioned on line 119, but not defined == Outdated reference: A later version (-12) exists of draft-ietf-pim-sm-v2-new-11 Summary: 7 errors (**), 0 flaws (~~), 6 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 PIM WG A. Boers 3 Internet-Draft IJ. Wijnands 4 Expires: August 5, 2005 E. Rosen 5 Cisco Systems, Inc. 6 february 2005 8 Format for using PIM proxies 9 draft-ietf-pim-proxy-00 11 Status of this Memo 13 This document is an Internet-Draft and is subject to all provisions 14 of Section 3 of RFC 3667. By submitting this Internet-Draft, each 15 author represents that any applicable patent or other IPR claims of 16 which he or she is aware have been or will be disclosed, and any of 17 which he or she become aware will be disclosed, in accordance with 18 RFC 3668. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as 23 Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on August 5, 2005. 38 Copyright Notice 40 Copyright (C) The Internet Society (2005). 42 Abstract 44 This document describes a generic TLV encoding format to be added to 45 PIM. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 50 2. Use of the Proxy Field in Join Messages . . . . . . . . . . . 3 51 2.1 Proxy join . . . . . . . . . . . . . . . . . . . . . . . . 3 52 2.2 Transitive proxies . . . . . . . . . . . . . . . . . . . . 3 53 2.3 Proxy Hello Option . . . . . . . . . . . . . . . . . . . . 3 54 2.4 Conflicting Proxies . . . . . . . . . . . . . . . . . . . 3 55 2.5 Proxy Convergence . . . . . . . . . . . . . . . . . . . . 4 56 2.6 Multiple Proxies . . . . . . . . . . . . . . . . . . . . . 4 57 3. PIM Proxy packet format . . . . . . . . . . . . . . . . . . . 5 58 3.1 PIM Join packet format . . . . . . . . . . . . . . . . . . 5 59 3.2 PIM Proxy Hello option . . . . . . . . . . . . . . . . . . 5 60 4. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6 61 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 62 5.1 Normative References . . . . . . . . . . . . . . . . . . . 6 63 5.2 Informative References . . . . . . . . . . . . . . . . . . 6 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 6 65 Intellectual Property and Copyright Statements . . . . . . . . 7 67 1. Introduction 69 It is sometimes convenient to add additional information to PIM join 70 messages. The generic PIM encoding format is not allways optimal 71 todo this. This document defines a new field in the PIM Join 72 message, called the "Proxy" field. The contents and purpose of this 73 proxy field is not outside the scope of this document, only the 74 generic encoding format is described here. 76 2. Use of the Proxy Field in Join Messages 78 2.1 Proxy join 80 Proxy fields are defined similar to the PIM source encoding type as 81 defined in [I-D.ietf-pim-sm-v2-new]. A source address without any 82 additional TLV's should be processed identically to a source address 83 in the default source encoding. 85 Multiple TLV's from the same or different type are permitted in a 86 single source address in any order. 88 2.2 Transitive proxies 90 It may be desired to have routers that understand the generic proxy 91 format, forward the proxies regardless if they understand the TLV's 92 encoded in the proxy not. For this the first bit in the Type field 93 is reserved. If this bit is set then the TLV is forwarded upstream 94 in case the router does not understand that type. 96 2.3 Proxy Hello Option 98 A new PIM source type has been defined to include the Proxy field. 99 This source type is included in a normal PIM Join. Each router on a 100 connected network needs to be able to understand and parse the Join 101 message. Therefore we include a new PIM hello option to advertise 102 our capability to parse and process the new source type. We can only 103 send a PIM Join which includes a Proxy if ALL routers on the network 104 support the new option. (Even a router which is not the upstream 105 neighbor must be able parse the packet in order to do Join 106 suppression or overriding.) Option value TBD. 108 2.4 Conflicting Proxies 110 It's possible that a router receives conflicting proxy information 111 from different downstream routers. See Figure 2. 113 ( Edge A1 ) ( Edge B1 )---- [R1] 114 / \ / 115 / \ / 116 [S] ( Core ) 117 \ / \ 118 \ / \ 119 ( Edge A2 ) ( Edge B2 )---- [R2] 121 Figure 2 123 There are 2 receivers for the same group connected to Edge B1 and B2. 124 Suppose that edge router B1 prefers A1 as the exit point and B2 125 prefers A2 as exit point to reach the source S. If both Edge B1 and 126 B2 send a Join including a Proxy to prefer their exit router in the 127 network and they cross the same core router, the core router will get 128 conflicting proxy information for the source. If this happens we use 129 the Proxy from the PIM adjacency with the numerically smallest IP 130 address. The Proxies from other sending routers may be kept around 131 in case the best Proxy gets pruned or expires, we are able to 132 immediately use the second best Proxy and converge quickly without 133 waiting for the next periodic update. If a TLV has its own 134 definition for conflict resolution is is preferred over the conflict 135 resolution above. 137 2.5 Proxy Convergence 139 A Proxy is included in a PIM Join message together with the source 140 information. If the Proxy for this source is changed, we trigger a 141 new PIM Join message to the upstream router. This causes the new 142 Proxy to be propagated. This new Proxy implicitly removes the old 143 Proxy upstream. If processing the new Proxy results in a change in 144 the distribution tree, a PIM Prune message may be sent. This PIM 145 Prune does not need to carry any Proxy, the sender of the prune and 146 the source and group information is enough to identify the entry. 147 The proxy information is removed immediately and possibly a new proxy 148 is chosen from the database if available. 150 2.6 Multiple Proxies 152 A PIM Join can contain multiple Proxies. The Proxies are encoded as 153 TLVs associated with a new PIM source type in the PIM message. When 154 a PIM Join with multiple Proxies is received, the first Proxy is 155 processed, and the action taken depends upon the Proxy type. This 156 may or may not result in the processing of the next Proxy. Proxies 157 not processed are passed upstream unchanged. 159 3. PIM Proxy packet format 161 3.1 PIM Join packet format 163 There is no space in the default PIM source encoding to include a 164 Proxy field. Therefore we introduce a new source encoding type. The 165 proxies are formatted as TLV's. The new Encoded source address looks 166 like this: 168 0 1 2 3 169 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 170 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 171 | Addr Family | Encoding Type | TLV # |S|W|R| Mask Len | 172 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 173 | Source Address | 174 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 175 |F| Type | Length | Value 176 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+..... 177 |F| Type | Length | Value 178 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+..... 179 . . . 180 . . . 182 TLV # gives the number of TLV's that are included with this source. 183 With the 5 bits we can include a maximum of 31 TLV's 185 F bit, Forward Unknown TLV bit. If this bit is set the TLV is 186 forwarded regardless if the router understands the Type. 188 Type field of the TLV is 7 bits. 190 Length field of the TLV is 1 byte. 192 The other fields are the same as described in the PIM spec. 193 [I-D.ietf-pim-sm-v2-new]. 195 The source TLV encoding type: TBD. 197 3.2 PIM Proxy Hello option 199 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 200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 201 | OptionType = XX | OptionLength = 0 | 202 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 204 Option type: TBD. 206 4. Acknowledgments 208 The authors would like to thank James Lingard for his comments on 209 this topic. 211 5. References 213 5.1 Normative References 215 [I-D.ietf-pim-sm-v2-new] 216 Fenner, B., Handley, M., Holbrook, H. and I. Kouvelas, 217 "Protocol Independent Multicast - Sparse Mode PIM-SM): 218 Protocol Specification (Revised)", 219 Internet-Draft draft-ietf-pim-sm-v2-new-11, October 2004. 221 5.2 Informative References 223 Authors' Addresses 225 Arjen Boers 226 Cisco Systems, Inc. 227 Avda. Diagonal, 682 228 Barcelona 08034 229 Spain 231 Email: aboers@cisco.com 233 IJsbrand Wijnands 234 Cisco Systems, Inc. 235 De kleetlaan 6a 236 Diegem 1831 237 Belgium 239 Email: ice@cisco.com 241 Eric Rosen 242 Cisco Systems, Inc. 243 1414 Massachusetts Avenue 244 Boxborough, Ma 01719 246 Email: erosen@cisco.com 248 Intellectual Property Statement 250 The IETF takes no position regarding the validity or scope of any 251 Intellectual Property Rights or other rights that might be claimed to 252 pertain to the implementation or use of the technology described in 253 this document or the extent to which any license under such rights 254 might or might not be available; nor does it represent that it has 255 made any independent effort to identify any such rights. Information 256 on the procedures with respect to rights in RFC documents can be 257 found in BCP 78 and BCP 79. 259 Copies of IPR disclosures made to the IETF Secretariat and any 260 assurances of licenses to be made available, or the result of an 261 attempt made to obtain a general license or permission for the use of 262 such proprietary rights by implementers or users of this 263 specification can be obtained from the IETF on-line IPR repository at 264 http://www.ietf.org/ipr. 266 The IETF invites any interested party to bring to its attention any 267 copyrights, patents or patent applications, or other proprietary 268 rights that may cover technology that may be required to implement 269 this standard. Please address the information to the IETF at 270 ietf-ipr@ietf.org. 272 Disclaimer of Validity 274 This document and the information contained herein are provided on an 275 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 276 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 277 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 278 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 279 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 280 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 282 Copyright Statement 284 Copyright (C) The Internet Society (2005). This document is subject 285 to the rights, licenses and restrictions contained in BCP 78, and 286 except as set forth therein, the authors retain all their rights. 288 Acknowledgment 290 Funding for the RFC Editor function is currently provided by the 291 Internet Society.