idnits 2.17.1 draft-ietf-ancp-mc-extensions-12.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 (Using the creation date from RFC6320, updated by this document, for RFC5378 checks: 2007-03-06) -- 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 (November 19, 2013) is 3812 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'PIMreg' Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ANCP F. Le Faucheur 3 Internet-Draft Cisco 4 Updates: 6320 (if approved) R. Maglione 5 Intended status: Standards Track Cisco Systems 6 Expires: May 23, 2014 T. Taylor 7 Huawei 8 November 19, 2013 10 Multicast Control Extensions for ANCP 11 draft-ietf-ancp-mc-extensions-12.txt 13 Abstract 15 This document specifies the extensions to the Access Node Control 16 Protocol required for support of the multicast use cases defined in 17 the Access Node Control Protocol framework document and one 18 additional use case described in this document. These use cases are 19 organized into the following ANCP capabilities: 21 o NAS-initiated multicast replication; 23 o conditional access with white and black lists; 25 o conditional access with grey lists; 27 o bandwidth delegation; 29 o committed bandwidth reporting. 31 These capabilities may be combined according to the rules given in 32 this specification. 34 This document updates RFC 6320 by assigning capability type 3 to a 35 capability specified in this document and by changing the starting 36 point for IANA allocation of result codes determined by IETF 37 Consensus from 0x100 to 0x64. 39 Status of This Memo 41 This Internet-Draft is submitted in full conformance with the 42 provisions of BCP 78 and BCP 79. 44 Internet-Drafts are working documents of the Internet Engineering 45 Task Force (IETF). Note that other groups may also distribute 46 working documents as Internet-Drafts. The list of current Internet- 47 Drafts is at http://datatracker.ietf.org/drafts/current/. 49 Internet-Drafts are draft documents valid for a maximum of six months 50 and may be updated, replaced, or obsoleted by other documents at any 51 time. It is inappropriate to use Internet-Drafts as reference 52 material or to cite them other than as "work in progress." 54 This Internet-Draft will expire on May 23, 2014. 56 Copyright Notice 58 Copyright (c) 2013 IETF Trust and the persons identified as the 59 document authors. All rights reserved. 61 This document is subject to BCP 78 and the IETF Trust's Legal 62 Provisions Relating to IETF Documents 63 (http://trustee.ietf.org/license-info) in effect on the date of 64 publication of this document. Please review these documents 65 carefully, as they describe your rights and restrictions with respect 66 to this document. Code Components extracted from this document must 67 include Simplified BSD License text as described in Section 4.e of 68 the Trust Legal Provisions and are provided without warranty as 69 described in the Simplified BSD License. 71 Table of Contents 73 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 74 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 75 3. Multicast Use Cases . . . . . . . . . . . . . . . . . . . . . 6 76 3.1. NAS Initiated Multicast Replication Control Use Case . . 7 77 3.1.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 7 78 3.1.2. Message Flow . . . . . . . . . . . . . . . . . . . . 7 79 3.2. Conditional Access and Admission Control Use Case . . . . 8 80 3.2.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 8 81 3.2.2. Message Flow . . . . . . . . . . . . . . . . . . . . 8 82 3.3. Multicast Flow Reporting Use Case . . . . . . . . . . . . 9 83 3.3.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 9 84 3.3.2. Message Flow . . . . . . . . . . . . . . . . . . . . 9 85 3.4. Committed Bandwidth Reporting Use Case . . . . . . . . . 10 86 3.4.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 10 87 3.4.2. Message Flow . . . . . . . . . . . . . . . . . . . . 10 88 4. ANCP Messages . . . . . . . . . . . . . . . . . . . . . . . . 11 89 4.1. Provisioning Message . . . . . . . . . . . . . . . . . . 11 90 4.1.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 12 91 4.1.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 13 92 4.2. Port Management Message . . . . . . . . . . . . . . . . . 14 93 4.2.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 15 94 4.2.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 15 95 4.3. Multicast Replication Control Message . . . . . . . . . . 16 96 4.3.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 19 97 4.3.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 20 98 4.4. Multicast Admission Control Message . . . . . . . . . . . 22 99 4.4.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 23 100 4.4.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 24 101 4.5. Bandwidth Reallocation Request Message . . . . . . . . . 25 102 4.5.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 25 103 4.5.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 26 104 4.6. Bandwidth Transfer Message . . . . . . . . . . . . . . . 29 105 4.6.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 30 106 4.6.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 30 107 4.7. Delegated Bandwidth Query Request Message . . . . . . . . 31 108 4.7.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 31 109 4.7.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 31 110 4.8. Delegated Bandwidth Query Response Message . . . . . . . 32 111 4.8.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 32 112 4.8.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 32 113 4.9. Multicast Flow Query Request and Response Messages . . . 33 114 4.9.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 34 115 4.9.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 34 116 4.10. Committed Bandwidth Report Message . . . . . . . . . . . 36 117 4.10.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 36 118 4.10.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 36 119 5. ANCP TLVs For Multicast . . . . . . . . . . . . . . . . . . . 37 120 5.1. Multicast-Service-Profile TLV . . . . . . . . . . . . . . 37 121 5.2. Multicast-Service-Profile-Name TLV . . . . . . . . . . . 38 122 5.3. List-Action TLV . . . . . . . . . . . . . . . . . . . . . 39 123 5.4. Sequence-Number TLV . . . . . . . . . . . . . . . . . . . 41 124 5.5. Bandwidth-Allocation TLV . . . . . . . . . . . . . . . . 42 125 5.6. White-List-CAC TLV . . . . . . . . . . . . . . . . . . . 42 126 5.7. MRepCtl-CAC TLV . . . . . . . . . . . . . . . . . . . . . 43 127 5.8. Bandwidth-Request TLV . . . . . . . . . . . . . . . . . . 43 128 5.9. Request-Source-IP TLV . . . . . . . . . . . . . . . . . . 44 129 5.10. Request-Source-MAC TLV . . . . . . . . . . . . . . . . . 44 130 5.11. Multicast-Flow TLV . . . . . . . . . . . . . . . . . . . 45 131 5.12. Report-Buffering-Time TLV . . . . . . . . . . . . . . . . 46 132 5.13. Committed-Bandwidth TLV . . . . . . . . . . . . . . . . . 47 133 6. Multicast Capabilities . . . . . . . . . . . . . . . . . . . 47 134 6.1. Required Protocol Support . . . . . . . . . . . . . . . . 48 135 6.1.1. Protocol Requirements For NAS-Initiated Replication . 48 136 6.1.2. Protocol Requirements For Committed Multicast 137 Bandwidth Reporting . . . . . . . . . . . . . . . . . 49 138 6.1.3. Protocol Requirements For Conditional Access With 139 White and Black Lists . . . . . . . . . . . . . . . . 50 140 6.1.4. Protocol Requirements For Conditional Access With 141 Grey Lists . . . . . . . . . . . . . . . . . . . . . 50 142 6.1.5. Protocol Requirements For Delegated Bandwidth . . . . 52 143 6.2. Capability-Specific Procedures for Providing Multicast 144 Service . . . . . . . . . . . . . . . . . . . . . . . . . 52 146 6.2.1. Procedures For NAS-Initiated Replication . . . . . . 52 147 6.2.2. Procedures For Committed Bandwidth Reporting . . . . 53 148 6.2.3. Procedures For Conditional Access With Black and 149 White Lists . . . . . . . . . . . . . . . . . . . . . 54 150 6.2.4. Procedures For Conditional Access With Grey Lists . . 56 151 6.2.5. Procedures For Delegated Bandwidth . . . . . . . . . 57 152 6.3. Combinations of Multicast Capabilities . . . . . . . . . 58 153 6.3.1. Combination of Conditional Access With White and 154 Black Lists and Conditional Access With Grey Lists . 58 155 6.3.2. Combination of Conditional Access With Delegated 156 Bandwidth . . . . . . . . . . . . . . . . . . . . . . 60 157 6.3.3. Combination of NAS-Initiated Replication with Other 158 Capabilities . . . . . . . . . . . . . . . . . . . . 60 159 6.3.4. Combinations of Committed Bandwidth Reporting with 160 Other Multicast Capabilities . . . . . . . . . . . . 61 161 7. Security Considerations . . . . . . . . . . . . . . . . . . . 61 162 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61 163 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 64 164 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 64 165 10.1. Normative References . . . . . . . . . . . . . . . . . . 64 166 10.2. Informative References . . . . . . . . . . . . . . . . . 64 167 Appendix A. Example of Messages and Message Flows . . . . . . . 65 168 A.1. Provisioning Phase . . . . . . . . . . . . . . . . . . . 65 169 A.2. Handling a Grey-Listed Flow . . . . . . . . . . . . . . . 70 170 A.3. Handling White-Listed Flows . . . . . . . . . . . . . . . 75 171 A.4. Handling Of Black-Listed Join Requests . . . . . . . . . 79 172 A.5. Handling Of Requests To Join and Leave the On-Line Game . 79 173 A.6. Example Flow For Multicast Flow Reporting . . . . . . . . 81 174 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 84 176 1. Introduction 178 [RFC5851] defines a framework and requirements for an Access Node 179 control mechanism between a Network Access Server (NAS) and an Access 180 Node (e.g. a Digital Subscriber Line Access Multiplexer (DSLAM)) in a 181 multi-service reference architecture in order to perform QoS-related, 182 service-related and subscriber-related operations. [RFC6320] 183 specifies a protocol for Access Node Control in broadband networks in 184 line with this framework. 186 [RFC6320] supports three use cases defined in [RFC5851], specifically 187 for DSL access: the DSL Topology Discovery use case, the DSL Line 188 Configuration use case and the DSL Remote Connectivity Test use case. 189 However, it does not support the multicast use cases defined in 190 [RFC5851]. The present document specifies the extensions to the 191 Access Node Control Protocol required for support of these multicast 192 use cases. In addition, it supports the Committed Bandwidth 193 Reporting use case, described below. In terms of the ANCP protocol, 194 these use cases are organized into five capabilities: 196 o NAS-initiated multicast replication; 198 o conditional access with white and black lists; 200 o conditional access with grey lists; 202 o bandwidth delegation; 204 o committed bandwidth reporting. 206 NAS-initiated multicast replication assumes that multicast "join" and 207 "leave" requests are terminated on the NAS, or that the NAS receives 208 requests to establish multicast sessions through other means (e.g., 209 application-level signalling). The NAS sends commands to the AN to 210 start or stop replication of specific multicast flows on specific 211 subscriber ports. This use case is described briefly in the next-to- 212 last paragraph of Section 3.4 of [RFC5851]. 214 Conditional access is described in Section 3.4.1 and Section 3.4.2.3 215 of [RFC5851], with the latter section particularly applicable to 216 operation with white and black lists only. In case of "conditional 217 access with white and black lists", multicast join and leave requests 218 are terminated at the AN and accepted or ignored in accordance with 219 the direction provided by white and black lists respectively. The 220 white and black lists are provisioned per port at startup time and 221 may be modified thereafter. The NAS may enable admission control of 222 white-listed flows by appropriate provisioning. 224 Conditional access with grey lists is similar to conditional access 225 with white lists, except that before accepting any request matching a 226 grey list entry, the AN sends a request to the NAS for permission to 227 replicate the flow. Again, the NAS can enable admission control of 228 grey-listed flows at the AN. 230 Bandwidth delegation is described in Section 3.4.2.1 of [RFC5851]. 231 It allows flexible sharing of total video bandwidth on an access line 232 between the AN and the NAS. One application of such bandwidth 233 sharing is where the AN does multicast admission control, while the 234 NAS or Policy Server does unicast admission control. In that case, 235 bandwidth delegation allows dynamic sharing of bandwidth between 236 unicast and multicast video traffic on each access line. 238 Committed bandwidth reporting is described below, in Section 3.4. 239 The AN reports the amount of multicast bandwidth it has granted to a 240 given access line each time that value changes. These reports may be 241 buffered for a NAS-provisionable interval so that reports for 242 multiple access lines can be bundled into the same message. 244 The formal specification of the behaviours associated with each of 245 these capabilities, singly and in combination, is given in Section 6. 247 In addition to the multicast service processing behaviour just 248 sketched, the definition of each capability includes support for the 249 multicast accounting and reporting services described in 250 Section 3.4.3 of [RFC5851]. Because of this common content and 251 because of other protocol overlaps between the different 252 capabilities, the protocol descriptions for the multicast extensions 253 specified in this document are merged into a single non-redundant 254 narrative. Tables in Section 6 then indicate the specific sub- 255 sections of the protocol description that have to be implemented to 256 support each capability. 258 This document updates RFC 6320 by assigning capability type 3 to the 259 NAS-initiated multicast replication capability and by changing the 260 starting point for IANA allocation of result codes determined by IETF 261 Consensus from 0x100 to 0x64. 263 2. Terminology 265 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 266 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 267 document are to be interpreted as described in [RFC2119]. 269 The expression "delegated bandwidth" is used as a shorter way of 270 saying: "the total amount of video bandwidth delegated to the AN for 271 multicast admission control". 273 3. Multicast Use Cases 275 Quoting from [RFC5851]: 277 "... the Access Node, aggregation node(s) and the NAS must all be 278 involved in the multicast replication process. This avoids that 279 several copies of the same stream are sent within the access/ 280 aggregation network. In case of an Ethernet-based access/aggregation 281 network, this may, for example, be achieved by means of IGMP snooping 282 or IGMP proxy in the Access Node and aggregation node(s). By 283 introducing IGMP processing in the access/aggregation nodes, the 284 multicast replication process is now divided between the NAS, the 285 aggregation node(s) and Access Nodes. In order to ensure backward 286 compatibility with the ATM-based model, the NAS, aggregation node and 287 Access Node need to behave as a single logical device. This logical 288 device must have exactly the same functionality as the NAS in the ATM 289 access/aggregation network. The Access Node Control Mechanism can be 290 used to make sure that this logical/functional equivalence is 291 achieved by exchanging the necessary information between the Access 292 Node and the NAS." 294 [RFC5851] describes the use cases for ANCP associated with such 295 multicast operations, and identifies the associated ANCP 296 requirements. The present section describes a subset of these use 297 cases as background to facilitate reading of this document, but the 298 reader is refered to [RFC5851] for a more exhaustive description of 299 the ANCP multicast use cases. Detailed example message flows can 300 also be found in Appendix A. 302 3.1. NAS Initiated Multicast Replication Control Use Case 304 3.1.1. Goals 306 One option for multicast handling is for the subscriber to 307 communicate the "join/leave" information to the NAS. This can be 308 done for instance by terminating all subscriber IGMP ([RFC3376]) or 309 MLD ([RFC2710], [RFC3810]) signaling on the NAS. Another example 310 could be a subscriber using some form of application level signaling, 311 which is redirected to the NAS. In any case, this option is 312 transparent to the access and aggregation network. In this scenario, 313 the NAS uses ANCP to create and remove replication state in the AN 314 for efficient multicast replication. Thus, the NAS only sends a 315 single copy of the multicast stream towards the AN, which in turn 316 performs replication to multiple subscribers as instructed by the NAS 317 via ANCP. The NAS first performs conditional access and multicast 318 admission control when processing multicast join requests, and only 319 creates replication state in the AN if admission succeeds. 321 3.1.2. Message Flow 323 With the NAS-initiated use case, a Multicast Replication Control 324 Message is sent by the NAS to the AN with a directive to either join 325 or leave one (or more) multicast flow(s). In the example message 326 flow, the AN uses a Generic Response message to convey the outcome of 327 the directive. Figure 1 illustrates such an ANCP message exchange as 328 well as the associated AN behavior. 330 +----------+ +-------+ +-----+ ANCP +-----+ 331 |Subscriber| | Home | | AN |<-------------------->| NAS | 332 +----------+ |Gateway| +-----+ +-----+ 333 | +-------+ | | 334 | | | (*) 335 | | | Multicast-Replication-Crl | 336 | | | (Target,add, Flow 1) | 337 | | |<--------------------------| 338 | Mcast Flow 1 | | 339 |<==========================+ | 340 | | | Generic Response | 341 | | |-------------------------->| 342 | | | | 343 | | | | 344 ~ ~ ~ ~ 345 | | | | 346 | | | Multicast-Replication-Crl | 347 | | | (Target,delete, Flow 1) | 348 | | |<--------------------------| 349 | | | | 350 | | Generic Response | 352 | | |-------------------------->| 354 (*) The NAS may optionally seek direction from an external 355 Authorization/Policy Server before admitting the flow. 357 Figure 1: NAS Initiated Multicast Replication Control 359 3.2. Conditional Access and Admission Control Use Case 361 3.2.1. Goals 363 One option for multicast handling is for the access/aggregation nodes 364 to participate in IGMP/MLD processing (e.g. via IGMP/MLD snooping). 365 In this scenario, on detecting a join/leave request from an end user 366 for a multicast flow (in the grey list), the AN uses ANCP to request 367 a conditional access and admission control decision from the NAS. In 368 turn, after conditional access and admission control checks, the NAS 369 uses ANCP to instruct the AN to change the replication states 370 accordingly. 372 3.2.2. Message Flow 374 For support of the conditional access and admission control use case, 375 on detection of an IGMP/MLD Join, the AN sends an Admission Control 376 message to the NAS to request a conditional access and admission 377 control check. In the case of a positive outcome, the NAS sends a 378 Multicast Replication Control Message to the AN with a directive to 379 replicate the multicast flow to the corresponding user. Similarly on 380 detection of an IGMP/MLD leave, an Admission Control message is sent 381 by the AN to the NAS to keep the NAS aware of user departure for the 382 flow. This message flow is illustrated in Figure 2. 384 +----------+ +-------+ +-----+ ANCP +-----+ 385 |Subscriber| | Home | | AN |<------------------->| NAS | 386 +----------+ |Gateway| +-----+ +-----+ 387 | +-------+ | | 388 | | | | 389 | Join(Gr-Flow1) | Admission-Control | 390 |------------+---------->| (Target,add,Gr-Flow1) | 391 | | |-------------------------->| 392 | | | (*) 393 | | | Multicast-Replication-Crl | 394 | | | (Target,add,Gr-Flow1) | 395 | | |<--------------------------| 396 | Mcast Gr-Flow1 | | 397 |<=======================+ | 398 | | | | 399 ~ ~ ~ ~ 400 | | | | 401 | Leave(Gr-Flow1) | Admission-Control | 402 |------------+---------->| (Target,delete,Gr-Flow1) | 403 | | |-------------------------->| 404 | | | 406 | | | | 408 Gr-Flow1: a multicast flow matching the grey list for that port 410 (*) The NAS may optionally seek direction from an external 411 Authorization/Policy Server before admitting the flow. 413 Figure 2: Multicast Conditional Access and Admission Control 415 3.3. Multicast Flow Reporting Use Case 417 3.3.1. Goals 419 The Multicast flow reporting use case allows the NAS to 420 asynchronously query the AN to obtain an instantaneous status report 421 related to multicast flows currently replicated by the AN. 423 3.3.2. Message Flow 424 The NAS sends a Multicast Flow Query Request message to the AN in 425 order to query the AN about information such as which multicast flows 426 are currently active on a given AN port or which ports are currently 427 replicating a given multicast flow. The AN conveys the requested 428 information to the NAS in a Multicast Flow Query Response message. 429 This message flow is illustrated in Figure 3. 431 +----------+ +-------+ +-----+ ANCP +-----+ 432 |Subscriber| | Home | | AN |<---------->| NAS | 433 +----------+ |Gateway| +-----+ +-----+ 434 | +-------+ | | 435 | | | Multicast Flow | 436 | | | Query Request | 437 | | |<------------------| 438 | | | | 439 | | | Multicast Flow | 440 | | | Query Response | 441 | | |------------------>| 442 | | | | 443 | | | | 445 Figure 3: Multicast Flow Reporting 447 3.4. Committed Bandwidth Reporting Use Case 449 3.4.1. Goals 451 The committed bandwidth reporting use case allows the NAS to maintain 452 current awareness of how much multicast bandwidth the AN has 453 committed to a given access line, so that the NAS can adjust its 454 forwarding scheduler to ensure the associated QoS. Note that this 455 involves a finer level of detail than provided by bandwidth 456 delegation, since the amount of delegated bandwidth is an upper limit 457 on the amount of bandwidth committed rather than an actual value. To 458 reduce the volume of messaging, reports from the AN may be buffered 459 so that one message reports on changes for multiple access lines. 461 3.4.2. Message Flow 463 The message flow associated with this use case is shown in Figure 4. 464 The figure assumes that a non-zero buffering interval was previously 465 provisioned on the AN. 467 +-----+ +-------+ +-----+ ANCP +-----+ 468 |Subs |+ | Home |+ | AN |<---------->| NAS | 469 |1,2 || |GW 1,2 || +-----+ +-----+ 470 +-----+| +-------+| | | 471 +|----+ +|------+ | | 472 | | | | | | 473 | |Join(Subs1, Ch1) | | 474 |----------+--------------->| Start buffering | 475 | | | Multicast flow | timer. Create | 476 |<==========================| message with | 477 | | | | | initial contents | 478 | | | | | reporting new | 479 | | | | | Subs1 bandwidth. | 480 | | Join(Subs2, Ch2) | | 481 | |----------+------------->| Add report for | 482 | | | Multicast flow | new Subs2 b/w. | 483 | |<========================| | 484 | | | | | | 485 | |Leave(Subs1, Ch1) | | 486 |----------+--------------->| Replace report | 487 | | | | | for Subs1 with | 488 | | Stop replication X new value (which | 489 | | | | | happens to be | 490 | | | | | the same as the | 491 | | | | | starting value. | 492 | | | | | | 493 | | | | >|< TIMER expires | 494 | | | | | | 495 | | | | |Committed | 496 | | | | | Bandwidth Report | 497 | | | | |------------------>| 498 | | | | | (for latest | 499 | | | | | Subs1 and Subs2 | 500 | | | | | bandwidth) | 501 | | | | | | 503 Figure 4: Message Flow For Committed Bandwidth Reporting 505 4. ANCP Messages 507 This section defines new ANCP messages and new usage of existing ANCP 508 messages as well as procedures associated with the use of these 509 messages. 511 4.1. Provisioning Message 513 Section 4.1 of [RFC6320] defines the Provisioning message that is 514 sent by the NAS to the AN to provision information in the AN. 516 The present document specifies that the Provisioning message MAY be 517 used by the NAS to provision multicast-related information (e.g., 518 multicast service profiles). The ANCP Provisioning message payload 519 MAY contain: 521 o one or more instances of the Multicast-Service-Profile TLV. The 522 Multicast-Service-Profile TLV is defined in the present document 523 in Section 5.1. Each instance of the Multicast-Service-Profile 524 TLV contains a multicast service profile name and one or more list 525 actions. A list action consists of an action (add, delete, 526 replace), a list type (white, black, or grey), and list content 527 (multicast source and group addresses). 529 o an instance of the White-List-CAC TLV. The White-List-CAC TLV is 530 defined in Section 5.6. If present, this TLV indicates that the 531 AN is required to do admission control before replicating white- 532 listed flows. 534 o an instance of the MRepCtl-CAC TLV. The MRepCtl-CAC TLV is 535 defined in Section 5.7. If present, this TLV indicates that the 536 AN is required to do admission control before replicating flows 537 specified in Multicast Replication Control messages. 539 o an instance of the Report-Buffering-Time TLV. The Report- 540 Buffering-Time TLV is defined in Section 5.12. If present, this 541 TLV indicates Committed Bandwidth Report messages should be 542 buffered for the amount of time given by the TLV before being 543 transmitted to the NAS. 545 See Section 6 for information on which multicast capabilities require 546 support of these TLVs in the Provisioning message. 548 4.1.1. Sender Behaviour 550 When directed by the Policy Server or by management action, the NAS 551 sends the Provisioning message to initially provision or to update 552 the white, black, and/or grey multicast channel lists associated with 553 a set of named multicast service profiles, or to enable the AN to 554 perform admission control for specific classes of flows. 556 To provision or update a multicast service profile, the NAS MUST 557 include within the message one or more instances of the Multicast- 558 Service-Profile TLV specifying the content to be provisioned or 559 updated. The NAS SHOULD NOT include any list type (white, black, or 560 grey) that is not supported by the set of multicast capabilities 561 negotiated between the NAS and the AN. The NAS MUST NOT use the 562 Provisioning message to send instances of the Multicast-Service- 563 Profile TLV to the AN unless the Multicast-Service-Profile TLV is 564 supported by the set of multicast capabilities negotiated between the 565 NAS and the AN. 567 To require admission control to be performed at the AN on white- 568 listed flows, the NAS MUST include a copy of the White-List-CAC TLV 569 in the Provisioning message. The White-List-CAC TLV MUST NOT be 570 provided unless the negotiated set of capabilities includes 571 conditional access with white and black lists. 573 To require admission control to be performed at the AN on grey-listed 574 flows or on NAS-initiated flows, the NAS MUST include a copy of the 575 MRepCtl-CAC TLV in the Provisioning message. The MRepCtl-CAC TLV 576 MUST NOT be provided unless the negotiated set of capabilities 577 includes NAS-initiated replication control or conditional access with 578 grey lists. 580 To require buffering of Committed Bandwidth Report messages so that 581 reports for multiple access lines can be included in the same 582 message, the NAS MUST include a copy of the Report-Buffering-Time TLV 583 containing a non-zero time value in a Provisioning message sent to 584 the AN. The Report-Buffering-Time TLV MUST NOT be provided unless 585 the negotiated set of capabilities includes committed bandwidth 586 reporting. 588 4.1.2. Receiver Behaviour 590 The receiving AN provisions/updates the white, black, and/or grey 591 lists associated with the multicast service profile names contained 592 in the Multicast-Service-Profile TLV instances within the message 593 according to the contents of the associated List-Action TLVs. The AN 594 MUST process List-Action TLVs in the order in which they appear 595 within the message. The AN MUST ignore instances of the List-Action 596 TLV referring to any list type (white, black, or grey) that is not 597 supported by the set of multicast capabilities negotiated between the 598 NAS and the AN. 600 When a new multicast service profile is identified by a Multicast- 601 Service-Profile TLV, the initial state of all lists associated with 602 that profile according to the negotiated set of multicast 603 capabilities is empty until changed by the contents of Multicast- 604 Service-Profile TLVs. 606 The receipt of a Provisioning message containing updates to an 607 existing multicast service profile subsequent to startup will cause 608 the AN to review the status of active flows on all ports to which 609 that profile has been assigned. For further details, see Section 6. 611 If the White-List-CAC and/or MRepCtl-CAC TLV is present in the 612 Provisioning message and the respective associated capabilities have 613 been negotiated, the AN prepares (or continues) to do connection 614 admission control on the indicated class(es) of flow. If one or both 615 of these TLVs was present in an earlier Provisioning message but is 616 absent in the latest message received, the AN ceases to do connection 617 admission control on the indicated class(es) of flow. 619 The buffering time specified in an instance of the Report-Buffering- 620 Time TLV applies to only to Committed Bandwidth Report messages 621 initiated after the new buffering time is received at the AN, not to 622 any message already in the process of accumulation. 624 As indicated in [RFC6320], the AN MUST NOT reply to the Provisioning 625 message if it processed it successfully. If an error prevents 626 successful processing of the message content, the AN MUST return a 627 Generic Response message as defined in [RFC6320], containing a 628 Status-Info TLV with the appropriate content describing the error. 629 For this purpose, the presence of a list type in a Multicast-Service- 630 Profile TLV which was ignored because it was not supported by the 631 negotiated set of capabilities is not considered to be an error. 633 4.2. Port Management Message 635 As specified in [RFC6320], the NAS may send DSL line configuration 636 information to the AN ("ANCP based DSL Line Configuration" use case) 637 using ANCP Port Management messages. See Section 7.3 of [RFC6320] 638 for the format of the Port Management message in that usage. 640 This document specifies that the Port Management message MAY be used 641 to convey either or both of the following TLVs: 643 o Multicast-Service-Profile-Name TLV (defined in Section 5.2). This 644 TLV associates a Multicast Service Profile with the Access Port 645 specified by the extension block. 647 o Bandwidth-Allocation TLV (defined in Section 5.5). This TLV 648 specifies the total multicast bandwidth available to the AN for 649 admission control at the Access Port. 651 When the Port Management message is used for this purpose: 653 o the Function field in the Port Management message MUST be set to 654 8, "Configure Connection Service Data". 656 o the message MUST include TLV(s) to identify the access line 657 concerned. If the access line is a DSL loop, the line-identifying 658 TLV(s) MUST be as specified in Section 5.1.2 of [RFC6320]. For 659 non-DSL access lines, the appropriate alternative line-identifying 660 TLV(s) MUST be present. Line configuration data other than the 661 two TLVs listed in the previous paragraph MAY be present. 663 4.2.1. Sender Behaviour 665 The NAS sends the Port Management message at startup time to 666 initialize parameters associated with the Access Port specified in 667 the message and with the multicast capabilities negotiated between 668 the NAS and the AN. The NAS MAY send additional Port Management 669 messages subsequent to startup, to update or, in the case of the 670 Bandwidth-Allocation TLV, reset these parameters. If the NAS 671 includes a Multicast-Service-Profile-Name TLV in the Port Management 672 message, the name MUST match a profile name provided in a Multicast- 673 Service-Profile TLV in a prior Provisioning message. The NAS MUST 674 NOT include a TLV unless it is supported by the set of multicast 675 capabilities negotiated between the NAS and the AN. See Section 6 676 for further information. 678 4.2.2. Receiver Behaviour 680 If the Port Management message contains a Multicast-Service-Profile- 681 Name TLV, the AN associates the named profile with the specified 682 Access Port. This association replaces any previous association. 683 That is, a given Access Port is associated with at most one multicast 684 service profile. The replacement of one multicast service profile 685 with another will cause the AN to review the status of all active 686 flows on the target port. For further details see Section 6. 688 If the Port Management message contains a Bandwidth-Allocation TLV, 689 the AN adopts this as the current value of its total multicast 690 bandwidth limit for the target port. If the AN has already committed 691 multicast bandwidth exceeding the amount given in the Bandwidth- 692 Allocation TLV, the AN SHOULD NOT discontinue any multicast streams 693 in order to bring bandwidth down to within the new limit. However, 694 the AN MUST NOT admit new multicast streams that are subject to 695 admission control until it can do so within the limit specified by 696 the Bandwidth-Allocation TLV. 698 If the Port Management request cannot be processed due to error and 699 the Result field of the request is Nack (0x1) or AckAll (0x2), the AN 700 SHOULD add a Status-Info TLV to the Extension Value field in its 701 reply if this will provide useful information beyond what is provided 702 by the Result Code value returned in the response header. In 703 particular, if the name within the Multicast-Service-Profile-Name TLV 704 does not match a profile name given in a prior Provisioning message, 705 the AN SHOULD return a reply where the Result Code field in the 706 header indicates 0x55, "Invalid TLV contents", the Error Message 707 field in the Status-Info TLV contains the text "Multicast profile 708 name not provisioned", and the Status-Info TLV contains a copy of the 709 Multicast-Service-Profile-Name TLV. 711 4.3. Multicast Replication Control Message 713 This section defines a new message called the Multicast Replication 714 Control message. The Multicast Replication Control message is sent 715 by the NAS to the AN with one or more directives to add (join) or 716 delete (leave) a multicast flow on a target object identified in the 717 content of the message. 719 The Message Type for the Multicast Replication Control message is 720 144. 722 The ANCP Multicast Replication Control message payload contains the 723 following TLVs: 725 o Target TLV: The Target TLV is defined in Section 4.3 of [RFC6320]. 726 It MUST appear once and only once. It is encoded as specified in 727 [RFC6320] or extensions and identifies the AN port subject to the 728 request for admission or release. 730 o Command TLV: The Command TLV is defined in Section 4.4 of 731 [RFC6320]. It MUST be present. It MAY appear multiple times. 733 As [RFC6320] indicates, the contents of the Command Info field within 734 the Command TLV are specific to the message in which the TLV occurs. 735 For the Multicast Replication Control Message, these contents consist 736 of: 738 o a Command Code field; 740 o an Accounting field; 742 o an instance of the Multicast-Flow TLV. 744 Figure 5 illustrates the complete Command TLV with the contents 745 specific to the Multicast Replication Control message. 747 1 2 3 748 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 749 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 750 | TLV Type = Command | Command-TLV Length | 751 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 752 |Command Code | Accounting | Reserved | 753 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 754 | Multicast-Flow TLV | 755 | ... | 756 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 757 | Other embedded TLV Type | Other embedded TLV Length | 758 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 759 | | 760 ~ Other embedded TLV data ~ 761 | | 762 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 764 Figure 5: Contents of the Command TLV in the Multicast Replication 765 Control Message 767 Command Code: 768 Command directive: 770 1 - Add; 772 2 - Delete; 774 3 - Delete All; 776 4 - Admission Control Reject; 778 5 - Conditional Access Reject; 780 6 - Admission Control and Conditional Access Reject. 782 Directives 4 through 6 are used as described in 783 Section 4.4.2. 785 Accounting: 786 Meaningful only when the Command Code is "Add" (1). In 787 that case, 0x00 indicates no flow accounting, 0x01 788 indicates that octet accounting for the flow is to 789 commence. The Accounting field MUST be set to 0x00 for 790 other Command Code values. 792 Reserved: 793 Reserved for future use. MUST be set to 0x0000 by the 794 sender and ignored by the receiver. 796 Multicast-Flow TLV: 797 An instance of the Multicast-Flow TLV (Section 5.11) 798 specifying the flow to be added or deleted. The Multicast- 799 Flow TLV MUST be omitted if the Command Code has value 800 "Delete All" (3). 802 Other embedded TLV: 804 No other embedded TLVs are currently specified within the 805 Multicast Replication Control message/Command TLV. 806 However, see the description of the Multicast Admission 807 Control message (Section 4.4). Unrecognized embedded TLVs 808 SHOULD be silently discarded. 810 The figure below is an example of a Multicast Replication Control 811 message that would result in a swap from multicast Source-Specific 812 Multicast (SSM) flows 2001:DB8::1, FF34::2, to 2001:DB8::2, FF34::3 813 on the Target identified by the "Access Loop Circuit ID": 815 1 2 3 816 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 817 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 818 | Type (0x880C) | Length | 819 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 820 | Version | MsgType=144 | 0x02 | Result Code | 821 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 822 | Partition ID | Transaction Identifier = 0001 | 823 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 824 |I| SubMessage Number | Length | 825 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 826 | Type = Target 0x1000 | Target TLV Length | 827 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 828 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | 829 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 830 | | 831 ~ Access Loop Circuit ID ~ 832 | | 833 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 834 | Type = Command TLV | Command-TLV Length = 0x0014 | 835 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 836 | Cmd Code=2 |Acctg = 0x00 | Reserved = 0x0000 | 837 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 838 |TLV Type = Multicast-Flow | TLV Length = 0x000C | 839 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 840 |Flow Type=0x02 |AddrFam = 0x02 | Reserved = 0x0000 | 841 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 842 | | 843 ~ Multicast Group Address ~ 844 | = FF34::2 | 845 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 846 | | 847 ~ Source Address ~ 848 | = 2001:DB8::1 | 849 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 850 | Type = Command-TLV | Command-TLV Length = 0x0014 | 851 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 852 | Cmd Code=1 |Acctg = 0x01 | Reserved = 0x0000 | 853 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 854 |TLV Type = Multicast-Flow | TLV Length = 0x000C | 855 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 856 |Flow Type=0x02 |AddrFam = 0x02 | Reserved = 0x0000 | 857 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 858 | Multicast Group Address = FF34::3 | 859 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 860 | Source Address = 2001:DB8::2 | 861 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 862 | | 863 ~ Multicast Group Address ~ 864 | = FF34::3 | 865 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 866 | | 867 ~ Source Address ~ 868 | = 2001:DB8::2 | 869 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 871 4.3.1. Sender Behaviour 873 The NAS MAY issue a Multicast Replication Control message to the AN 874 to convey one or more directives to add (join) or delete (leave) one 875 or more multicast flows. 877 The NAS MAY send this message on its own initiative to support the 878 NAS initiated Multicast Control use case presented in [RFC5851] and 879 summarized in Section 3.1. In that case, the NAS MUST set the Result 880 field to AckAll (0x2) or Nack (0x1) according to its requirements. 882 The NAS MAY also send this message in response to a Multicast 883 Admission Control message (defined in Section 4.4) received from the 884 AN to support the conditional access and admission control use case 885 presented in [RFC5851] and summarized in Section 3.2. In that case, 886 the NAS MUST set the Result field to NAck (0x1). 888 In either case, the sender MUST populate the Result Code field with 889 the value 0x000 and the ANCP Transaction Identifier field with a 890 unique value, as described in Section 3.6.1.6 of [RFC6320]. 892 Each Multicast Replication Control Message MUST contain one or more 893 commands, each encapsulated in its own Command TLV. The sender MUST 894 use a separate Command TLV for each distinct multicast flow. 896 When the order of processing of two commands does not matter, the 897 commands MUST be transmitted in separate Multicast Replication 898 Control messages. 900 4.3.2. Receiver Behaviour 902 When successive commands (in the same or different messages) relate 903 to the same Target and multicast flow, the state of each feature 904 controlled or affected by attributes received in the Multicast 905 Replication Control message, SHALL be as set by the last command or 906 message referring to that target and flow and containing the 907 controlling attribute. As an example, successive Multicast 908 Replication Control messages containing add commands for a given port 909 and flow, but differing only in the Accounting field setting SHALL be 910 interpreted to mean that the state of the accounting feature is as 911 set in the final command received, but all other features are as set 912 in the initial message. 914 If more than one Command TLV is present in a Multicast Replication 915 Control message, the AN MUST act on the commands in the order in 916 which they are presented in the message. The AN SHALL assign a 917 sequence number to each command in a given Multicast Replication 918 Control message, starting from 0x01 for the first command. 920 If a Command TLV adds a flow and the AN is performing admission 921 control for Multicast Replication Control messages, then the AN MUST 922 perform admission control before replicating the flow. If the 923 admission control check fails, the AN MUST treat the failure as an 924 error as described below. The appropriate Result Code value for the 925 response is 0x013 "Out of resources". 927 If the AN processes the complete Multicast Replication Control 928 message successfully and the Result field of the Multicast 929 Replication Control message was set to AckAll (0x2), the AN MUST 930 respond with a Generic Response message where the Result field is set 931 to Success (0x3), the Result Code field is set to 0x000, and the 932 Transaction Identifier field is copied from the Multicast Replication 933 Control message. The body of the response MAY be empty or MAY be 934 copied from the Multicast Replication Control message. 936 If the AN processes the complete Multicast Replication Control 937 message successfully and the Result field of the Multicast 938 Replication Control message was set to Nack (0x1), the AN MUST NOT 939 respond to the message. 941 The processing/execution of multiple commands contained in a single 942 Multicast Control message MUST be interrupted at the first error 943 encountered, and the remaining commands in the Multicast Replication 944 Control message discarded. 946 If the AN detects an error in a received Multicast Replication 947 Control message and the Result field in that message was set to Nack 948 (0x1) or AckAll(0x2), the AN MUST generate a Generic Response message 949 providing error information to the NAS. This specification 950 identifies the following new Result Code values beyond those 951 specified in [RFC6320], which MAY be used in a Generic Response sent 952 in reply to a Multicast Replication Control message: 954 0x64 Command error. 956 Where detected: ANCP agent at the AN. 958 Further description: an invalid command code has been received. 960 Required additional information in the message: see below. 962 Target: ANCP agent at the NAS. 964 Action RECOMMENDED for the receiving ANCP agent: Correct the 965 error and re-send the request, if possible. Otherwise, report 966 the error to the control application with an indication of the 967 erroneous information associated with the invalid TLV(s). 969 0x65 Invalid flow address. 971 Where detected: ANCP agent at the AN. 973 Further description: either inconsistent flow address 974 information has been provided or the address family is 975 unsupported. 977 Required additional information in the message: see below. 979 Target: ANCP agent at the NAS. 981 Action RECOMMENDED for the receiving ANCP agent: correct the 982 error and re-send the request, if possible. Otherwise, report 983 the error to the control application with an indication of the 984 erroneous information associated with the invalid TLV(s). 986 0x66 Multicast flow does not exist. 988 Where detected: control application at the AN. 990 Further description: the NAS has attempted to delete a flow 991 that is not active on the given access line. 993 Required additional information in the message: see below. 995 Target: control application at the NAS. 997 Action RECOMMENDED for the receiving ANCP agent: report the 998 error to the control application with an indication of the 999 erroneous information associated with the invalid TLV(s). 1001 A Generic Response message responding to the Multicast Replication 1002 Control message and containing one of the above Result Code values 1003 MUST include a Status-Info TLV which includes one or two embedded 1004 TLVs as follows: 1006 o a Sequence-Number TLV as described in Section 5.4, giving the 1007 sequence number of the failed command, MUST be included; 1009 o the failed Command TLV itself SHOULD be included. 1011 Note that the Error Message field of the Status-Info TLV MAY be 1012 used to report more details than implied by the Result Code value 1013 in the message header. For example, the Result Code value could 1014 be 0x65 and the Error Message field could contain the text: 1015 "Source address present for ASM flow". 1017 4.4. Multicast Admission Control Message 1019 This section defines a new message called the Multicast Admission 1020 Control message. The Multicast Admission Control message is sent by 1021 the AN to the NAS to request admission of a multicast flow, or to 1022 notify of the removal of a multicast flow, for a given target. 1024 The Message Type for the Multicast Admission Control message is 145. 1026 The ANCP Multicast Admission Control message payload contains two 1027 TLVs: 1029 o Target TLV: The Target TLV is defined in [RFC6320]. It MUST 1030 appear once and only once in the Multicast Admission Control 1031 message. It is encoded as specified in [RFC6320] or extensions 1032 and identifies the AN port subject to the request for admission or 1033 release. 1035 o Command TLV: The Command TLV is defined in [RFC6320]. It MUST be 1036 present. If it appears more than once, only the first instance is 1037 considered meaningful in the present version of this specification 1038 and the other instances are ignored. 1040 Note: 1042 In the future, the specification of the Admission Control message 1043 may be extended to allow transport of more than a single directive 1044 (e.g., to carry both a leave from one group and a join to another 1045 group for the same Target). It is expected that this would 1046 support a similar notion of strict sequenced processing as 1047 currently defined for handling multiple directives in the 1048 Multicast Replication Control message whereby all directives 1049 following the first directive that can not be executed are not 1050 executed either. When the strict sequenced processing of the 1051 directives is not required the directives are distributed across 1052 separate messages. 1054 The Command TLV has the same contents as were described above for the 1055 Multicast Replication Control message, with the following additions: 1057 o a Request-Source-IP TLV MAY be appended to the Command TLV as an 1058 additional embedded TLV; 1060 o similarly, a Request-Source-MAC TLV MAY be appended to the Command 1061 TLV as an additional embedded TLV. 1063 Note that the Command TLV length includes the length of any embedded 1064 TLVs, including the embedded TLV headers. 1066 4.4.1. Sender Behaviour 1068 The AN sending the Multicast Admission Control message MUST set the 1069 Result field to Ignore (0x0). 1071 The AN MUST populate the ANCP Transaction Identifier field with a 1072 unique value, as described in Section 3.6.1.6 of [RFC6320]. 1074 The AN MUST encode the Command TLV as specified in Section 4.3 with 1075 the following additional rules: 1077 o the Accounting field MUST be set to 0; 1079 o the Command Code field MUST be set to "1 - Add" when the message 1080 conveys a Join , to "2 - Delete" when the message conveys a Leave 1081 and to "3 - Delete All" when the message conveys a Leave of all 1082 channels (on the target); 1084 o The Multicast-Flow TLV within the Command TLV identifies the 1085 multicast flow subject to the request for admission or release. 1086 When the Command Code is 3, the Multicast-Flow TLV is meaningless 1087 and MUST be omitted. 1089 o the Request-Source-IP embedded TLV MAY be included by the AN to 1090 convey the IP address of the sender of the join/leave message 1091 (e.g., IGMP/MLD Join/Leave) that triggered the AN to include the 1092 corresponding Command TLV in the Admission Control message. If it 1093 appears more than once, only the first instance is considered 1094 meaningful and the other instances are ignored. 1096 o the Request-Source-MAC embedded TLV MAY be included by the AN to 1097 convey the MAC address of the sender of the join/leave message 1098 (e.g., IGMP/MLD Join/Leave) that triggered the AN to include the 1099 corresponding Command TLV in the Admission Control message. If it 1100 appears more than once, only the first instance is considered 1101 meaningful and the other instances are ignored. 1103 4.4.2. Receiver Behaviour 1105 On receipt of an Multicast Admission Control message, the NAS: 1107 o MUST ignore the Result field; 1109 o if the directive in the Multicast Admission Control message is "2 1110 - Delete" or "3 - Delete All" and is processed correctly by the 1111 NAS, the NAS MUST NOT generate any ANCP message in response to the 1112 Multicast Admission Control message; 1114 o if the directive in the Multicast Admission Control message is "1 1115 - Add" and is accepted by the NAS, the NAS MUST generate a 1116 Multicast Replication Control in response to the Multicast 1117 Admission Control message. The Multicast Replication Control 1118 message: 1120 * MUST contain a Result set to Nack (0x1); 1122 * MUST contain a Transaction ID with a unique value, as described 1123 in Section 3.6.1.6 of [RFC6320]; 1125 * MUST contain the directive as accepted by the NAS. The NAS MAY 1126 modify the Accounting field if flow accounting is required. 1128 o if the directive in the Multicast Admission Control message is "1 1129 - Add", is processed correctly but not accepted by the NAS (i.e., 1130 it does not pass the admission control or conditional access 1131 check), the NAS MAY generate a Multicast Replication Control 1132 message in response to the Multicast Admission Control message. 1133 This optional message can be used by the AN to maintain statistics 1134 about admission control rejections. When used in this situation, 1135 the Multicast Replication Control message: 1137 * MUST contain a Result set to 0x0; 1139 * MUST contain a Transaction ID with a unique value, as described 1140 in Section 3.6.1.6 of [RFC6320]; 1142 * MUST contain the directive rejected by the NAS (i.e., Target 1143 TLV and Command TLV) but with a Command Code set to "4 - 1144 Admission Control Reject", "5 - Conditional Access Reject", or 1145 "6 - Admission Control and Conditional Access Reject" as 1146 applicable. 1148 o if the Multicast Admission Control message cannot be processed 1149 correctly by the NAS (e.g. the message is malformed, the multicast 1150 flow does not exist etc.), the NAS MUST generate a Generic 1151 Response message (defined in Section 4.2 of [RFC6320]) with 1152 appropriate content indicating the reason for the failure. 1154 4.5. Bandwidth Reallocation Request Message 1156 The Bandwidth Reallocation Request message is used when the bandwidth 1157 delegation capability is included in the negotiated set. It MAY be 1158 sent either by the NAS or by the AN to request an adjustment in the 1159 amount of delegated bandwidth. It will be sent by the NAS typically 1160 to reduce the multicast bandwidth allocated to the AN in order for 1161 the NAS to satisfy a request to add one or more flows. Conversely, 1162 the AN will send a Bandwidth Reallocation Request to obtain 1163 additional bandwidth to satisfy a request to add a multicast channel. 1164 In each case, the requestor has a minimum requirement for additional 1165 bandwidth, and MAY ask for additional bandwidth beyond this amount 1166 (e.g., to handle anticipated future requests). 1168 The Bandwidth Reallocation Request message contains two TLVs: 1170 o the Target TLV (Section 4.3 of [RFC6320] or an extension), 1171 specifying a single access line; 1173 o the Bandwidth-Request TLV (Section 5.8), specifying the required 1174 and preferred amounts of delegated bandwidth. 1176 The Message Type for the Bandwidth Reallocation Request message is 1177 146. 1179 4.5.1. Sender Behaviour 1181 The Result field in the header of the Bandwidth Reallocation Request 1182 message is not used and the sender MUST set it to Ignore (0x0). 1184 The bandwidth values in the Bandwidth-Request TLV are expressed in 1185 terms of total multicast bandwidth allocated to the AN. 1187 The choice of "total bandwidth" rather than "incremental 1188 bandwidth" was made so that it would be easier for the AN and NAS 1189 to keep their respective views of the current amount of delegated 1190 bandwidth synchronized. 1192 Because the values are totals rather than desired increments/ 1193 decrements, the relationship between the required amount and the 1194 preferred amount will differ depending on whether the Bandwidth 1195 Reallocation Request message is issued by the NAS or the AN. 1197 o If the NAS is making the request, the preferred amount MUST be 1198 less than or equal to the required amount. The required amount 1199 MUST be less than the current amount of delegated bandwidth. 1201 o If the AN is making the request, the preferred amount MUST be 1202 greater than or equal to the required amount. The required amount 1203 MUST be greater than the current amount of delegated bandwidth. 1205 4.5.2. Receiver Behaviour 1207 When the peer receives a valid Bandwidth Reallocation Request 1208 message, it SHOULD determine whether it can satisfy the request from 1209 its existing allocation of unused video bandwidth. If it decides 1210 that it can reallocate bandwidth to the peer, it MAY choose to return 1211 any amount between the required and the preferred amounts indicated 1212 in the Bandwidth Reallocation Request message. 1214 The peer MUST return a Bandwidth Transfer message (Section 4.6) 1215 indicating its decision. If the request is met, the Result field of 1216 the Bandwidth Transfer message MUST be set to Success (0x3), the 1217 Result Code field MUST be set to 0x000, and the Bandwidth-Allocation 1218 TLV (Section 5.5) MUST contain the new value of total multicast 1219 bandwidth. This new value MUST lie between the required and 1220 preferred values, inclusive, from the request message. If the 1221 request is not met, the Result field of the Bandwidth Transfer 1222 message MUST be set to Failure (0x4), the Result Code field MUST be 1223 set to 0x000, and the Bandwidth Allocation TLV MUST contain the value 1224 of the currently allocated amount of delegated bandwidth as the 1225 responder views it. 1227 The following cases indicate that the sender holds a different view 1228 of the amount of delegated bandwidth from the receiver: 1230 o the NAS receives a request where the required amount is less than 1231 its view of the current amount of delegated bandwidth; 1233 o the AN receives a request where the required amount is greater 1234 than its view of the current amount of delegated bandwidth. 1236 If one of these cases occurs, the receiver with one exception MUST 1237 send a Bandwidth Transfer message indicating Success. 1239 o If the NAS received the request, the allocated amount in the NAS's 1240 response MUST be at least equal to NAS's view of the current 1241 amount of delegated bandwidth. 1243 o If the AN received the request, the allocated amount in the AN's 1244 response MUST be no greater than the AN's view of the current 1245 amount of delegated bandwidth. 1247 The exception is when the NAS receives a request while it has a 1248 request of its own outstanding. Handling of that case is described 1249 below. 1251 While the cases just described are an error condition, the success 1252 response achieves a graceful recovery. 1254 To avoid deadlock due to race conditions, the following rules MUST be 1255 applied: 1257 a. If the NAS receives a Bandwidth Reallocation Request message 1258 while it has a Bandwidth Reallocation Request message of its own 1259 outstanding for the same access line, the NAS MUST provide an 1260 immediate failure response to the request from the AN, with a 1261 Result Code value set to 0x68 "Inconsistent views of delegated 1262 bandwidth amount" or 0x69 "Bandwidth request conflict" as 1263 applicable. (See below for more information). 1265 b. If the AN receives a Bandwidth Reallocation Request message while 1266 it has a Bandwidth Reallocation Request message of its own 1267 outstanding for the same access line, the AN MUST release any 1268 bandwidth it has already committed to an outstanding Join request 1269 while it is awaiting a response from the NAS. It MUST decide 1270 upon and send its response to the NAS taking the released 1271 bandwidth into account. 1273 If the receiver is unable to process the Bandwidth Reallocation 1274 Request message due to an error, then the receiver MUST return a 1275 Bandwidth Transfer message where: 1277 o the Result field is set to Failure (0x4), 1279 o the Result Code field is set appropriately to indicate the type of 1280 error that was detected, 1282 o the Bandwidth Allocation TLV contains the value of the current 1283 amount of delegated bandwidth as the responder views it, and 1285 o a Status-Info TLV MAY follow the Bandwidth Allocation TLV giving 1286 further information about the error. 1288 This specification provides three new Result Code values applicable 1289 specifically to the contents of the Bandwidth-Request TLV. These 1290 Result Code values by their nature MUST only be used when the error 1291 is being reported in a Bandwidth Transfer message rather than a 1292 Generic Response message. 1294 0x67 Invalid preferred bandwidth amount. 1296 Where detected: control application at the receiver of the 1297 Bandwidth Reallocation Request message. 1299 Further description: the preferred and required amounts of 1300 bandwidth in the TLV do not have the numerical relationship 1301 described above. 1303 Required additional information in the message: as described 1304 above. 1306 Target: control application at the sender of the Bandwidth 1307 Reallocation Request message. 1309 Action RECOMMENDED for the receiving ANCP agent: report the 1310 error to the control application with the returned value of the 1311 Bandwidth-Allocation TLV. See also Section 4.6.2.2. 1313 0x68 Inconsistent views of delegated bandwidth amount. 1315 Where detected: control application at the NAS. 1317 Further description: the NAS has an outstanding Bandwidth 1318 Reallocation Request, so it is rejecting a similar request from 1319 the AN. In the AN request, the required amount was less than 1320 the NAS's view of the current amount of delegated bandwidth. 1322 Required additional information in the message: as described 1323 above. 1325 Target: control application at the AN. 1327 Action RECOMMENDED for the receiving ANCP agent: report the 1328 error to the AN control application with the returned value of 1329 the Bandwidth-Allocation TLV. See also Section 4.6.2.2. 1331 0x69 Bandwidth request conflict. 1333 Where detected: control application at the NAS. 1335 Further description: the NAS has an outstanding Bandwidth 1336 Reallocation Request, so it is rejecting a similar, valid 1337 request from the AN. 1339 Required additional information in the message: as described 1340 above. 1342 Target: control application at the AN. 1344 Action RECOMMENDED for the receiving ANCP agent: report the 1345 error to the AN control application with the returned value of 1346 the Bandwidth-Allocation TLV. See also Section 4.6.2.2. 1348 4.6. Bandwidth Transfer Message 1350 The Bandwidth Transfer message is used to transfer video bandwidth 1351 from the sender to the peer for a specific access line. This message 1352 MAY be sent either from the AN or from the NAS. As described in the 1353 previous section, it is the required response to a valid Bandwidth 1354 Reallocation Request message. 1356 The Bandwidth Transfer message MAY also be used to transfer bandwidth 1357 autonomously from one peer to another. One example of this usage is 1358 to release bandwidth borrowed earlier by means of the Bandwidth 1359 Reallocation Request message. When the message is used in this way, 1360 the Result field in the Bandwidth Transfer message MUST be set to 1361 Ignore (0x0). 1363 This allows the receiver to distinguish between an autonomous 1364 transfer and a response to a previous Bandwidth Reallocation 1365 Request, for purposes of validation. 1367 The Message Type for the Bandwidth Transfer message is 147. The 1368 Bandwidth Transfer message contains the following TLVs: 1370 o the Target TLV, designating the access line concerned; 1372 o an instance of the Bandwidth-Allocation TLV (Section 5.5). The 1373 bandwidth value in the Bandwidth-Allocation TLV is the new amount 1374 of delegated bandwidth allocated to the target. 1376 4.6.1. Sender Behaviour 1378 When sending a Bandwidth Transfer message where the Result value is 1379 Ignore (0x0) or Success (0x3), the following relationships MUST hold: 1381 o if the message is sent by the NAS, the bandwidth value in the 1382 Bandwidth-Allocation TLV MUST be greater than or equal to the 1383 sender's view of the current amount of delegated bandwidth for the 1384 access line concerned; 1386 o if the message is sent by the AN, the bandwidth value in the 1387 Bandwidth-Allocation TLV MUST be less than or equal to the 1388 sender's view of the current amount of delegated bandwidth for the 1389 access line concerned. 1391 Further sender behaviour is specified above, in Section 4.5.2. 1393 4.6.2. Receiver Behaviour 1395 4.6.2.1. Behaviour of the NAS 1397 If the amount of delegated bandwidth provided in the Bandwidth- 1398 Allocation TLV is not greater than the NAS's view of the current 1399 amount of delegated bandwidth, the NAS MUST update its view of the 1400 current amount of delegated bandwidth to the amount indicated in the 1401 Bandwidth Transfer message. This is required regardless of whether 1402 the Result field of that message indicates Success or Failure. 1404 If the amount of delegated bandwidth provided in the Bandwidth- 1405 Allocation TLV is greater than the NAS's view of the current amount 1406 of delegated bandwidth, the NAS MAY accept the given value as its new 1407 value of delegated bandwidth. Alternatively, the NAS MAY force the 1408 AN to modify its view of the amount of delegated bandwidth to that 1409 held by the NAS, by sending a Port Management message for the target 1410 access line concerned, containing a Bandwidth-Allocation TLV with a 1411 value equal to the amount of delegated bandwidth the NAS wishes to 1412 enforce. 1414 4.6.2.2. Behaviour of the AN 1416 If the amount of delegated bandwidth provided in the Bandwidth- 1417 Allocation TLV of the Bandwidth Transfer message differs from the 1418 AN's view of the current amount of delegated bandwidth, the AN MUST 1419 update its view of the current amount of delegated bandwidth to the 1420 amount indicated in the Bandwidth Transfer message. This is required 1421 with the exception of a Bandwidth Transfer message with a Result 1422 field equal to Failure (0x4) and a Result Code field equal to 0x68 1423 "Inconsistent views of delegated bandwidth amount" or 0x69 "Bandwidth 1424 request conflict". If Result Code value 0x68 is received, the AN 1425 MUST issue a Delegated Bandwidth Query Request message to determine 1426 the NAS's current view of the amount of delegated bandwidth. The AN 1427 MUST update its own view based on the value returned in the Delegated 1428 Bandwidth Query Response. If Result Code value 0x69 is received, the 1429 AN SHOULD carry out this procedure unless it can account for the 1430 discrepancy as a result of a transfer of bandwidth to the NAS that 1431 was carried out just before the incoming Bandwidth Transfer message 1432 was processed. 1434 The two Result Code values indicate a race condition where the AN 1435 may have just completed a transfer of bandwidth to the NAS. As a 1436 result, the value given in the Bandwidth Transfer message may be 1437 outdated, and the AN needs to query the NAS to find its latest 1438 view. The procedure assumes that ordering is preserved between 1439 the Bandwidth Transfer message sent by the AN in response to the 1440 NAS's request and the subsequent Delegated Bandwidth Query Request 1441 message. 1443 If as the result of the procedures just described the AN determines 1444 that it has over-committed multicast bandwidth, it MUST NOT terminate 1445 any currently-active programs, but MUST NOT honour any more "join" 1446 requests until it is possible to do so within the limit set by its 1447 current value of delegated bandwidth. 1449 4.7. Delegated Bandwidth Query Request Message 1451 The Message Type for the Delegated Bandwidth Query Request (and 1452 Response) messages is 148. 1454 The Delegated Bandwidth Query Request message MAY be sent either by 1455 the NAS or by the AN to retrieve the peer's view of the amount of 1456 delegated bandwidth. The request contains one TLV: 1458 o a Target TLV designating the access line for which the information 1459 is requested. 1461 4.7.1. Sender Behaviour 1463 The sender MUST set the Result field in the header of the Delegated 1464 Bandwidth Query Request message to AckAll (0x2). The Result Code 1465 value MUST be set to 0x000. The sender MUST populate the ANCP 1466 Transaction Identifier field with a unique value, as described in 1467 Section 3.6.1.6 of [RFC6320]. 1469 4.7.2. Receiver Behaviour 1470 If the AN or NAS receives a valid Delegated Bandwidth Query Request 1471 message, it MUST respond with a Delegated Bandwidth Query Response 1472 message. The Result field in the header of the response MUST be set 1473 to Success (0x3). The Result Code field MUST be set to 0x000. The 1474 Transaction-Id field MUST be copied from the request message. The 1475 body of the response MUST contain the Target TLV, copied from the 1476 request message. Finally, the body of the response MUST contain a 1477 Bandwidth-Allocation TLV, containing the current amount of delegated 1478 bandwidth from the point of view of the receiver of the request. 1480 If the contents of the Delegated Bandwidth Query Request message are 1481 in error, the receiver MUST return a Delegated Bandwidth Query 1482 Response message with the Result field in the header set to Failure 1483 (0x3). The Result Code field MUST be set to the value that indicates 1484 the nature of the error (e.g., 0x500 "One or more of the specified 1485 ports do not exist"). The Transaction-Id field MUST be copied from 1486 the request. The body of the response MUST contain the Target TLV 1487 copied from the request. This MAY be followed by a Status-Info TLV 1488 giving further information about the error. 1490 4.8. Delegated Bandwidth Query Response Message 1492 The Delegated Bandwidth Query Response message is sent in reply to a 1493 Delegated Bandwidth Query Request. The response to a valid request 1494 contains two TLVs: 1496 o the Target TLV, copied from the request; 1498 o a Bandwidth-Allocation TLV, giving the responder's view of the 1499 current amount of multicast bandwidth delegated to the AN. 1501 The Message Type for the Delegated Bandwidth Query Response message 1502 is 148. 1504 4.8.1. Sender Behaviour 1506 Sender behaviour for the Delegated Bandwidth Query Response message 1507 is specified in Section 4.7.2. 1509 4.8.2. Receiver Behaviour 1511 If the Delegated Bandwidth Query Response message indicates Success 1512 (0x3), the following actions apply. 1514 4.8.2.1. Behaviour at the NAS 1516 If the amount of delegated bandwidth provided in the Bandwidth- 1517 Allocation TLV is less than the NAS's view of the current amount of 1518 delegated bandwidth, the NAS MUST update its view of the current 1519 amount of delegated bandwidth to the amount indicated in the 1520 Delegated Bandwidth Query Response message. 1522 If the amount of delegated bandwidth provided in the Bandwidth- 1523 Allocation TLV is greater than the NAS's view of the current amount 1524 of delegated bandwidth, the NAS MAY accept the given value as its new 1525 value of delegated bandwidth. Alternatively, the NAS MAY force the 1526 AN to modify its view of the amount of delegated bandwidth to that 1527 held by the NAS, by sending a Port Management message for the target 1528 access line concerned, containing a Bandwidth-Allocation TLV with a 1529 value equal to the amount of delegated bandwidth the NAS wishes to 1530 enforce. 1532 4.8.2.2. Behaviour at the AN 1534 The AN SHOULD accept the value returned in the Bandwidth-Allocation 1535 TLV of the Delegated Bandwidth Query Response message as the correct 1536 value of the current amount of delegated bandwidth. If the AN has 1537 currently committed more than this amount to active programs, it MUST 1538 NOT cease replicating the flows concerned, but MUST NOT honour any 1539 more Join requests until possible to do so within the new limit. 1541 A race condition is possible, where the AN sends a query, the NAS 1542 requests more bandwidth, then receives and responds to the query, 1543 then receives the Bandwidth Transfer message responding to its 1544 request. It is up to the AN to take appropriate action in this 1545 case. The best action appears to be not to act on the result of 1546 the first query, but to repeat the query after sending the 1547 Bandwidth Transfer message. Similar considerations apply to a 1548 race between queries from both sides. 1550 4.9. Multicast Flow Query Request and Response Messages 1552 This section defines two new messages called the Multicast Flow Query 1553 Request and Multicast Flow Query Response. The Multicast Flow Query 1554 Request is sent by the NAS to request information about the multicast 1555 flows that are active on the AN. The Multicast Flow Query Response 1556 is sent in response by the AN to provide the requested information to 1557 the NAS. 1559 The Message Type for the Multicast Flow Query Request and Multicast 1560 Flow Query Response messages is 149. 1562 The contents of the Multicast Flow Query Request and Response depend 1563 on the nature of the query, as described below. 1565 4.9.1. Sender Behaviour 1567 The sender of a Multicast Flow Query Request message MUST set the 1568 Result field to AckAll (0x2). The Result Code field MUST be set to 1569 0x000. The sender MUST populate the ANCP Transaction Identifier 1570 field with a unique value, as described in section 3.6.1.6 of 1571 [RFC6320]. 1573 The Multicast Flow Query Request MAY be used by the NAS to retrieve: 1575 o the AN's view of which multicast flows are currently active on a 1576 specified set of access ports; or 1578 o the AN's view of the access ports on which a specified set of 1579 multicast flows are currently active; or 1581 o the AN's view of all the multicast flows currently active on each 1582 access port of the AN. 1584 To retrieve the AN's view of which multicast flows are currently 1585 active on a given port of the AN, the NAS MUST include a Target TLV 1586 in the Multicast Flow Query Request payload identifying that port. 1587 The Target TLV is encoded as specified in [RFC6320]. 1589 To retrieve the AN's view of the ports currently receiving a given 1590 multicast flow, the NAS MUST include a Multicast-Flow TLV in the 1591 Multicast Flow Query Request payload identifying that flow. The 1592 Multicast-Flow TLV is encoded as specified in Section 5.11. 1594 The NAS MAY include multiple Target TLVs or multiple Multicast-Flow 1595 TLVs in the Multicast Flow Query Request, but MUST NOT include both 1596 Target and Multicast-Flow TLVs in the same message. 1598 To retrieve the AN's view of all of the multicast flows currently 1599 active on each port of the AN, the NAS MUST send a Multicast Flow 1600 Query Request which does not contain any instance of the Target TLV 1601 or the Multicast-Flow TLV. 1603 4.9.2. Receiver Behaviour 1605 The AN MUST respond to a Multicast Flow Query Request message that 1606 has a valid format and a valid content with a Multicast Flow Query 1607 Response message. The Result field in the response MUST be set to 1608 Success (0x3). The Result Code field MUST be set to 0x000. The 1609 Transaction-Id field MUST be copied from the request. 1611 If the Multicast Flow Query Request contained one (or more) Target 1612 TLVs, the AN MUST include, for each of these Target TLVs, the 1613 following set of TLVs: 1615 o Target TLV. This MUST be identical to the Target TLV in the 1616 received Multicast Flow Query Request message. 1618 o Multicast-Flow TLV(s). The Multicast-Flow TLV MUST appear once 1619 per multicast flow that is currently active on the AN port 1620 identified in the preceding Target TLV. 1622 The Target TLVs MUST appear in the response from the AN in the same 1623 order as in the query from the NAS. 1625 If the Multicast Flow Query Request contained one (or more) 1626 Multicast-Flow TLVs, the AN MUST include, for each of these 1627 Multicast-Flow TLVs, the following set of TLVs: 1629 o Multicast-Flow TLV. This MUST be identical to the Multicast-Flow 1630 TLV in the received Multicast Flow Query Request message. 1632 o Target TLV(s). The Target TLV MUST appear once per AN port on 1633 which the multicast flow identified in the preceding Multicast- 1634 Flow TLV is active. 1636 The Multicast-Flow TLVs MUST appear in the response from the AN in 1637 the same order as in the query from the NAS. 1639 If the Multicast Flow Query Request contained no Target TLV and no 1640 Multicast Flow TLV, the AN MUST include, for each AN port currently 1641 receiving multicast flow(s), the following set of TLVs: 1643 o Target TLV. This MUST identify one AN port. 1645 o Multicast-Flow TLV(s). The Multicast-Flow TLV MUST appear once 1646 per Multicast Flow that is currently active on the AN port 1647 identified in the preceding Target TLV. 1649 If the contents of the Multicast Flow Query Request are in error, the 1650 AN MUST reply with a Multicast Flow Query Response message with the 1651 Result field set to Failure (0x4) and the Result Code field set to 1652 indicate the nature of the error. If the request contained multiple 1653 instances of the Target TLV or the Multicast-Flow TLV and one of 1654 these is in error, the response message MUST contain the results for 1655 the preceding instances of the TLV as if there had been no error. 1656 These successful results MUST be followed by the TLV in error, copied 1657 from the request. The AN MUST NOT do further processing of the 1658 request. The AN MAY add a Status-Info TLV to provide further 1659 information on the nature of the error. 1661 4.10. Committed Bandwidth Report Message 1663 This section describes the Committed Bandwidth Report message, which 1664 is sent from the AN to the NAS to report the most recent amount of 1665 multicast bandwidth usage committed to one or more access lines. 1667 The Message Type for the Committed Bandwidth Report message is 150. 1669 The Committed Bandwidth Report message contains one or more instances 1670 of the Committed-Bandwidth TLV, as described in Section 5.13. 1672 4.10.1. Sender Behaviour 1674 The sender of a Committed Bandwidth Report message MUST set the 1675 Result field to Ignore (0x0). The Result Code field MUST be set to 1676 0x000. The sender MUST populate the ANCP Transaction Identifier 1677 field with a unique value, as described in section 3.6.1.6 of 1678 [RFC6320]. 1680 Each instance of the Committed-Bandwidth TLV included in the message 1681 MUST identify an access line for which the amount of committed 1682 multicast bandwidth has changed since the previous Committed 1683 Bandwidth Report message was sent and MUST report the latest amount 1684 of multicast bandwidth committed to that line. There MUST be only 1685 one instance of the Committed-Bandwidth TLV present in the message 1686 for any given access line. The message MUST include an instance of 1687 the Committed-Bandwidth TLV for every access line for which committed 1688 multicast bandwidth has changed since the previous Committed 1689 Bandwidth Report message was sent. 1691 Further behaviour at the AN is specified in Section 6.2.2. 1693 4.10.2. Receiver Behaviour 1695 The usage of the contents of a Committed Bandwidth Report message 1696 received by the NAS is implementation-dependent. One example is that 1697 the NAS uses the reports of multicast bandwidth commitments to adjust 1698 its forwarding scheduler operation to provide the intended level of 1699 QoS. 1701 The NAS MUST NOT reply to a valid Committed Bandwidth Report message. 1702 The NAS MAY send a Generic Response message indicating the nature of 1703 any errors detected in a Committed Bandwidth Report message that it 1704 has received. 1706 5. ANCP TLVs For Multicast 1708 This section defines new ANCP TLVs for the control of multicast 1709 flows. 1711 5.1. Multicast-Service-Profile TLV 1713 This document defines the new Multicast-Service-Profile TLV. 1715 The Multicast-Service-Profile TLV MAY be included in a Provisioning 1716 message as specified in Section 4.1. 1718 The Multicast-Service-Profile TLV is illustrated in Figure 6. It 1719 consists of a TLV header encapsulating a single instance of the 1720 Multicast-Service-Profile-Name TLV and one or more instances of the 1721 List-Action TLV. 1723 1 2 3 1724 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 1725 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1726 |TLV Type = Mcast Serv Profile | TLV Length | 1727 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1728 | Multicast-Service-Profile-Name TLV | 1729 | | 1730 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1731 | List-Action TLV | 1732 | | 1733 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1734 | ... | 1735 | | 1736 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1737 | List-Action TLV | 1738 | | 1739 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1741 Figure 6: Multicast-Service-Profile TLV 1743 The Multicast-Service-Profile TLV has the following fields: 1745 o The Multicast-Service-Profile TLV Type is 0x0013. 1747 o The TLV length is determined by the contents following the TLV 1748 header. 1750 o The Multicast-Service-Profile-Name TLV is described in 1751 Section 5.2. The Multicast-Service-Profile-Name TLV MUST contain 1752 an identifier which is unique over all profiles provisioned to the 1753 same AN partition. This identifier will be used to refer to the 1754 profile when activating it for a given target within a Port 1755 Management message (see Section 4.2). 1757 o The List-Action TLV is described in Section 5.3. The List-Action 1758 TLV(s) provide the content of a newly defined multicast service 1759 profile or modify the existing content. If more than one List- 1760 Action TLV is present, the order of the TLVs may be significant, 1761 since List-Action TLVs are processed in the order in whch they 1762 appear. 1764 5.2. Multicast-Service-Profile-Name TLV 1766 The Multicast-Service-Profile-Name TLV carries the identifier of a 1767 multicast service profile provisioned on the AN. It is illustrated 1768 in Figure 7. 1770 1 2 3 1771 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 1772 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1773 |TLV Type = MSP Name | TLV Length | 1774 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1775 | Multicast service profile identifier | 1776 | | 1777 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1779 Figure 7: Multicast-Service-Profile-Name TLV 1781 The Multicast-Service-Profile-Name TLV has the following fields: 1783 o The Multicast-Service-Profile-Name TLV Type is 0x0018. 1785 o TLV Length: up to 255 octets. 1787 o Multicast service profile identifier: an opaque sequence of octets 1788 identifying a specific multicast service profile. 1790 The identifier could have the form of human-readable text or an 1791 arbitrary binary value, depending on the operator's practices. 1793 5.3. List-Action TLV 1795 The List-Action TLV identifies multicast flows to be added to or 1796 removed from a list of white-, black-, or grey-listed flows. It is 1797 meaningful only in association with a Multicast-Service-Profile-Name 1798 TLV identifying the profile to which the List-Action TLV applies. 1799 Such an association can be achieved by placing both TLVs in the same 1800 base message payload or as embedded TLVs of another TLV such as the 1801 Multicast-Service-Profile. The List-Action TLV is shown in Figure 8. 1803 1 2 3 1804 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 1805 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1806 | TLV Type = List-Action TLV | TLV Length | 1807 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1808 | Operation | List Type | Reserved | 1809 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1810 | Address Family | Number of flow fields | 1811 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1812 | Multicast flow fields | 1813 ...... 1814 | | 1815 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1816 | Address Family | Number of flow fields | 1817 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1818 | Multicast flow fields | 1819 ...... 1820 | | 1821 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1823 Figure 8: List-Action TLV 1825 The List-Action TLV contains the following fields: 1827 o The List-Action TLV Type is 0x0021. 1829 o TLV Length: length of the subsequent contents. 1831 o Operation: operation to be performed upon the white, black, or 1832 grey list identified by the List Type field within the profile 1833 identified by the associated Multicast-Service-Profile-Name 1834 embedded TLV. The possible values are: 1836 * Add (0x01): the multicast flow fields are to be added to the 1837 list. 1839 * Delete (0x02): the multicast flow fields are to be removed from 1840 the list. Each multicast flow field in the List-Action MUST 1841 match exactly an existing entry in the list concerned. Thus to 1842 remove part of the range provided by a wildcarded list entry, 1843 it is necessary to remove the entire entry and add back the 1844 remaining partial range(s). 1846 * Replace (0x03): the multicast flow fields replace the existing 1847 contents of the list. 1849 o List Type: the list type being modified by this List-Action. The 1850 possible values are White (0x01), Black (0x02), or Grey (0x03). 1852 o Reserved: a sender MUST set this field to 0x0000. A receiver MUST 1853 ignore the contents of this field. 1855 o Address Family: the IP version of the set of multicast flow fields 1856 that follow, encoded according to [PIMreg]. Possible values are 1857 0x0001 (IPv4) or 0x0002 (IPv6). Either an IPv4 list or an IPv6 1858 list or both MAY be present in the List-Action TLV. 1860 o Number of flow fields: the number of multicast flow fields of the 1861 given address family which follow. 1863 o Multicast flow field: a field identifying one or more multicast 1864 flows. It consists of an 8-bit group address prefix length, an 1865 8-bit source address prefix length, a 0-16 octet group prefix, and 1866 a 0-16 octet source prefix, as shown in Figure 9. 1868 Each multicast flow field refers either to a Source-Specific 1869 Multicast (SSM) channel or to an Any Source Multicast (ASM) group. 1870 The scope of the designation may be broadened to multiple channels or 1871 groups through use of prefix length values smaller than the total 1872 address length for the given address family. Multicast flow fields 1873 MUST be placed consecutively within the embedded TLV without 1874 intervening padding except to round out individual addresses to the 1875 nearest octet boundary. 1877 A multicast flow field consists of two single-octet prefix lengths 1878 followed by zero to two prefix values as shown in Figure 9: 1880 +-+-+-+-+-+-+-+-+ 1881 | Group PrefLen | 1882 +-+-+-+-+-+-+-+-+ 1883 | Source PrefLen| 1884 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1885 | Group Prefix (multicast) (0 to 16 octets) | 1886 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1887 | Source Prefix (unicast, SSM only) (0 to 16 octets) | 1888 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1889 Figure 9: Organization of a Single Multicast Flow Field 1891 The prefix length has its usual meaning. It is the number of most- 1892 significant bits specified within the corresponding prefix. The 1893 prefix length MAY vary from 0 to 32 in the IPv4 sub-list, and from 0 1894 to 128 in the IPv6 sub-list. 1896 A value of 0x00 for either the Group PrefLen (prefix length) or the 1897 Source PrefLen indicates that any value of the corresponding address 1898 will match (wild card). If the value 0x00 is provided for a 1899 particular prefix length, the corresponding prefix MUST be omitted 1900 from the field contents. 1902 The length of a Source or Group Prefix field is equal to (PrefLen + 1903 7)/8 octets, truncated to the nearest integer. Unused bits at the 1904 end of the prefix MUST be set to zeroes. 1906 5.4. Sequence-Number TLV 1908 The Sequence-Number TLV conveys a sequence number of some sort. The 1909 specific meaning of the sequence number is message-specific. Within 1910 this specification, the Sequence-Number TLV is used as a embedded TLV 1911 in a Status-Info TLV, in a Generic Response reporting a failed 1912 command in a Multicast Replication Control or Multicast Admission 1913 Request message. It identifies the sequence number within the 1914 message of the command that failed. 1916 The Sequence-Number TLV has the format shown in Figure 10. 1918 1 2 3 1919 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 1920 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1921 |TLV Type = Sequence-Number | TLV Length = 4 | 1922 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1923 | Sequence number | 1924 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1926 Figure 10: Sequence-Number TLV 1928 The Sequence-Number TLV has the following fields: 1930 o The Sequence-Number TLV Type is 0x0022. 1932 o TLV length is 0x0004. 1934 o Sequence number: the sequence number of a specific entity within a 1935 series, where numbering starts from 1 for the first entity in the 1936 series. Represented as a 32-bit binary number, most significant 1937 bit first. 1939 5.5. Bandwidth-Allocation TLV 1941 The Bandwidth-Allocation TLV is used to indicate the total amount of 1942 video bandwidth delegated to the AN for multicast admission control 1943 for a given access line, in kilobits per second. The TLV has the 1944 format shown in Figure 11. 1946 1 2 3 1947 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 1948 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1949 |TLV Type = BW-Allocation | TLV Length = 4 | 1950 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1951 | Delegated amount (kbits/s) | 1952 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1954 Figure 11: The Bandwidth-Allocation TLV 1956 The Bandwidth-Allocation TLV has the following fields: 1958 o The Bandwidth-Allocation TLV Type is 0x0015. 1960 o TLV length is 4. 1962 o Delegated amount: the bandwidth amount delegated to the AN for 1963 admission of multicast video on a given port, kilobits per second. 1964 Presented as a 32-bit binary value, most significant bit first. 1966 5.6. White-List-CAC TLV 1968 The White-List-CAC TLV is used to indicate that the NAS wishes the AN 1969 to do admission control for white-listed flows. Details on when the 1970 White-List-CAC TLV may be provisioned are specified in Section 6. 1971 The White-List-CAC TLV is illustrated in Figure 12. 1973 1 2 3 1974 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 1975 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1976 |TLV Type = White-List-CAC | TLV Length = 0 | 1977 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1979 Figure 12: White-List-CAC TLV 1981 The White-List-CAC TLV contains the following fields: 1983 o The White-List-CAC TLV Type is 0x0024. 1985 o TLV length is 0, since the TLV contains no data other than the TLV 1986 header. 1988 5.7. MRepCtl-CAC TLV 1990 The MRepCtl-CAC TLV is used to indicate that the NAS wishes the AN to 1991 do admission control for flows added by the Multicast Replication 1992 Control message. Details on when the MRepCtl-CAC TLV may be 1993 provisioned are specified in Section 6. The MRepCtl-CAC TLV is 1994 illustrated in Figure 13. 1996 1 2 3 1997 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 1998 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1999 |TLV Type = MRepCtl-CAC | TLV Length = 0 | 2000 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2002 Figure 13: MRepCtl-CAC TLV 2004 The MRepCtl-CAC TLV contains the following fields: 2006 o The MRepCtl-CAC TLV Type is 0x0025. 2008 o TLV length is 0, since the TLV contains no data other than the TLV 2009 header. 2011 5.8. Bandwidth-Request TLV 2013 The Bandwidth-Request TLV is used to request an adjustment of the 2014 total amount of video bandwidth allocated to the AN for multicast 2015 admission control for a given line. The "Required amount" field 2016 indicates the minimum adjustment required to meet the request. The 2017 "Preferred amount" field indicates the adjustment the requestor would 2018 prefer to have, if possible. Section 4.5 discusses the required 2019 relationships between the "Required amount", "Preferred amount", and 2020 current values of total bandwidth allocated to the AN. 2022 The Bandwidth-Request TLV has the format shown in Figure 14. 2024 1 2 3 2025 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 2026 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2027 |TLV Type = Bandwidth-Request | TLV Length = 8 | 2028 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2029 | Required amount (kbits/s) | 2030 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2031 | Preferred amount (kbits/s) | 2032 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2034 Figure 14: The Bandwidth-Request TLV 2036 The Bandwidth-Request TLV has the following fields: 2038 o The Bandwidth-Request TLV Type is 0x0016. 2040 o The TLV length is 8 octets. 2042 o Required amount: the minimum or maximum amount, depending on 2043 whether the sender is the AN or the NAS respectively, of delegated 2044 video bandwidth that is being requested, in kilobits per second. 2045 Presented as a 32-bit binary value, most significant bit first. 2047 o Preferred amount: the preferred amount of delegated video 2048 bandwidth that is being requested, in kilobits per second. 2049 Presented as a 32-bit binary value, most significant bit first. 2051 5.9. Request-Source-IP TLV 2053 The Request-Source-IP TLV provides the IP address of the entity that 2054 originated a specific request to join or leave a multicast channel. 2055 The TLV is illustrated in Figure 15. 2057 1 2 3 2058 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 2059 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2060 | TLV Type = Request-Source-IP | TLV length = 4 or 16 | 2061 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2062 | Unicast Address | 2063 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2065 Figure 15: Request-Source-IP TLV 2067 The Request-Source-IP TLV contains the following fields: 2069 o The Request-Source-IP TLV Type is 0x0092. 2071 o TLV length is 4 for an IPv4 address or 16 for an IPv6 address. 2073 o Unicast address: IP address of the source of a multicast flow join 2074 request, in network byte order. 2076 5.10. Request-Source-MAC TLV 2077 The Request-Source-MAC TLV provides the MAC address of the entity 2078 that originated a specific request to join or leave a multicast 2079 channel. The TLV is illustrated in Figure 16. 2081 1 2 3 2082 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 2083 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2084 |TLV Type=Request-Source-MAC | TLV Length = 6 or 8 | 2085 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2086 | | 2087 +-+-+- IEEE MAC Address +-+-+-+ 2088 | | 2089 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2091 Figure 16: Request-Source-MAC TLV 2093 The Request-Source-MAC TLV contains the following fields: 2095 o The Request-Source-MAC TLV Type is 0x0093. 2097 o TLV length is either 6 octets (MAC-48 or EUI-48) or 8 octets 2098 (EUI-64). 2100 o IEEE MAC Address: MAC address of the device originating the 2101 request to join a multicast flow. Within the address, bytes and 2102 bits respectively shall be ordered from most to least significant, 2103 consistently with [IEEE48] for MAC-48 and EUI-48, and with 2104 [IEEE64] for EUI-64. 2106 EUI-48 and EUI-64 are registered trademarks of the IEEE. 2108 5.11. Multicast-Flow TLV 2110 The Multicast-Flow TLV specifies a multicast flow in terms of its 2111 multicast group address and, if applicable, its unicast source 2112 address. It is illustrated in Figure 17. 2114 1 2 3 2115 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 2116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2117 |TLV Type = Multicast-Flow | TLV Length | 2118 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2119 | Flow Type | Addr Family | Reserved | 2120 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2121 | Multicast Group Address | 2122 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 2123 | Unicast Source Address (for SSM flows only) | 2124 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2125 Figure 17: Multicast-Flow TLV 2127 The Multicast-Flow TLV has the following fields: 2129 o The Multicast-Flow TLV Type is 0x0019. 2131 o TLV Length: ranges from a minimum of 8 (for an ASM IPv4 flow) to 2132 36 (for an IPv6 SSM flow). 2134 o Flow Type: 0x01 for Any Source Multicast (ASM), 0x02 for Source- 2135 Specific Multicast (SSM). 2137 o Addr Family: address family of the multicast source and group 2138 addresses, encoded in accordance with the IANA PIM Address Family 2139 registry ([PIMreg]). 0x01 indicates IPv4, 0x02 indicates IPv6. 2141 o Reserved: MUST be set to 0x0000 by the sender and MUST be ignored 2142 by the receiver. 2144 One possible use for this field in the future is to indicate 2145 the presence of PIM Join attributes attached to the source 2146 address (see [RFC5384]). The applicability of PIM attributes 2147 in the context of ANCP is for further study. 2149 o Multicast Group Address: a multicast group address within the 2150 given address family. The group address MUST always be present. 2152 o Unicast Source Address: unicast address within the given address 2153 family. If the Flow Type is 0x01 (ASM), a source address MUST NOT 2154 be present. If the Flow Type is 0x02 (SSM), a source address MUST 2155 be present. 2157 5.12. Report-Buffering-Time TLV 2159 The Report-Buffering-Time TLV provides the time for which a Committed 2160 Bandwidth Report message must be held with the intention of 2161 accumulating multiple reports of changed committed multicast 2162 bandwidth in one report, to reduce the volume of messages sent to the 2163 NAS. For further information see Section 6.2.2. The TLV is 2164 illustrated in Figure 18. 2166 1 2 3 2167 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 2168 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2169 |TLV Type=Report-Buffering-Time | TLV Length = 4 | 2170 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2171 | Buffering Time (ms) | 2172 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2173 Figure 18: Report-Buffering-Time TLV 2175 The Report-Buffering-Time TLV contains the following fields: 2177 o The Report-Buffering-Time TLV Type is 0x0094. 2179 o TLV length is 4 octets. 2181 o Buffering Time is a 32-bit unsigned integer containing a time 2182 value in ms. 2184 5.13. Committed-Bandwidth TLV 2186 The Committed-Bandwidth TLV identifies an access line and provides 2187 the current amount of multicast bandwidth that the AN has committed 2188 to it. The TLV is illustrated in Figure 19. 2190 1 2 3 2191 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 2192 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2193 |TLV Type=Committed-Bandwidth | TLV Length (variable) | 2194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2195 | Committed Multicast Bandwidth (kbits/s) | 2196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2197 | | 2198 +-+-+- Target TLV +-+-+-+ 2199 | | 2200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2202 Figure 19: Committed-Bandwidth TLV 2204 The Committed-Bandwidth TLV contains the following fields: 2206 o The Committed-Bandwidth TLV Type is 0x0095. 2208 o TLV length is 4 octets plus the length of the Target TLV including 2209 its header and any padding. 2211 o Committed Multicast Bandwidth is a 32-bit unsigned integer 2212 providing a bandwidth amount in kbits/s. 2214 o The Target TLV identifies the access line to which this amount of 2215 multicast bandwidth is currently committed. 2217 6. Multicast Capabilities 2218 Section 3.5 of [RFC6320] defines a capability negotiation mechanism 2219 as well as a number of capabilities. This section defines five new 2220 capabilities in support of different modes of multicast operation: 2222 o NAS-initiated replication (capability type 3); 2224 o committed multicast bandwidth reporting (capability type 5); 2226 o conditional access with white and black lists (capability type 6); 2228 o conditional access with grey lists (capability type 7); 2230 o bandwidth delegation (capability type 8). 2232 The "Capability Data" field within the Capability TLV for all of 2233 these capabilities is empty. All of these capabilities are 2234 independent of the access technology. 2236 The remainder of this section consists of three sub-sections. 2237 Section 6.1 specifies the protocol elements that must be implemented 2238 in order to support each capability. Section 6.2 specifies the 2239 procedures that apply to each capability on its own. Section 6.3 2240 specifies how the capabilities interact if more than one multicast 2241 capability is included in the set of capabilities negotiated between 2242 the AN and the NAS. 2244 Note that if a request contains content that is not supported 2245 (according to the tables in Section 6.1) by the negotiated set of 2246 multicast capabilities, the appropriate response is to return a 2247 Generic Response message indicating Failure (0x4) with an appropriate 2248 code value. The body of the message MUST contain a Status-Info TLV. 2249 See Sections 4.2 and 4.5 in [RFC6320] for more details. 2251 6.1. Required Protocol Support 2253 This section specifies the protocol elements that MUST be implemented 2254 to support each of the four multicast capabilities. Support of 2255 multiple multicast capabilities requires implementation of the union 2256 of the sets of protocol elements applying to each of the individual 2257 capabilities in the supported set. 2259 In addition to the elements listed below, implementation of the 2260 Target TLV (Section 4.3 of [RFC6320]) is REQUIRED for all of the 2261 capabilities specified in this document. 2263 6.1.1. Protocol Requirements For NAS-Initiated Replication 2264 Table 1 specifies the protocol elements within Section 4 and 2265 Section 5 that MUST be implemented to support the NAS-initiated 2266 replication multicast capability. Additionally, implementation of 2267 the Multicast Replication Control message requires implementation of 2268 the Command TLV (Section 4.4 of [RFC6320] with additional details in 2269 Section 4.3 of this document). 2271 +-----------------+-------------------------------------------------+ 2272 | Reference | Protocol Element | 2273 +-----------------+-------------------------------------------------+ 2274 | Section 4.1 | Provisioning message with MRepCtl-CAC TLV | 2275 | | | 2276 | Section 4.2 | Port Management message with Bandwidth- | 2277 | | Allocation TLV. | 2278 | | | 2279 | Section 4.3 | Multicast Replication Control message | 2280 | | | 2281 | Section 4.9 | Multicast Flow Query Request and Response | 2282 | | messages | 2283 | | | 2284 | Section 5.4 | Sequence Number TLV | 2285 | | | 2286 | Section 5.5 | Bandwidth-Allocation TLV | 2287 | | | 2288 | Section 5.7 | MRepCtl-CAC TLV | 2289 | | | 2290 | Section 5.11 | Multicast-Flow TLV | 2291 +-----------------+-------------------------------------------------+ 2293 Table 1: Protocol Requirements For NAS-Initiated Replication 2295 6.1.2. Protocol Requirements For Committed Multicast Bandwidth 2296 Reporting 2298 Table 2 specifies the protocol elements within Section 4 and 2299 Section 5 that MUST be implemented to support the committed multicast 2300 bandwidth reporting capability. 2302 +-----------------+-------------------------------------------------+ 2303 | Reference | Protocol Element | 2304 +-----------------+-------------------------------------------------+ 2305 | Section 4.1 | Provisioning message with Report-Buffering-Time | 2306 | | TLV | 2307 | | | 2308 | Section 4.10 | Committed Bandwidth Report message | 2309 | | | 2310 | Section 4.9 | Multicast Flow Query Request and Response | 2311 | | messages | 2312 | | | 2313 | Section 5.12 | Report-Buffering-Timer TLV | 2314 | | | 2315 | Section 5.13 | Committed-Bandwidth TLV | 2316 | | | 2317 | Section 5.11 | Multicast-Flow TLV | 2318 +-----------------+-------------------------------------------------+ 2320 Table 2: Protocol Requirements For Committed Multicast Bandwidth 2321 Reporting 2323 6.1.3. Protocol Requirements For Conditional Access With White and 2324 Black Lists 2326 Table 3 specifies the protocol elements within Section 4 and 2327 Section 5 that MUST be implemented to support the conditional access 2328 with white and black lists multicast capability. 2330 +--------------+----------------------------------------------------+ 2331 | Reference | Protocol Element | 2332 +--------------+----------------------------------------------------+ 2333 | Section 4.1 | Provisioning message with Multicast-Service- | 2334 | | Profile TLV, white and black lists only, and | 2335 | | White-List-CAC TLV | 2336 | | | 2337 | Section 4.2 | Port Management message with Multicast-Service- | 2338 | | Profile-Name and Bandwidth-Allocation TLVs. | 2339 | | | 2340 | Section 4.9 | Multicast Flow Query Request and Response messages | 2341 | | | 2342 | Section 5.1 | Multicast-Service-Profile TLV | 2343 | | | 2344 | Section 5.2 | Multicast-Service-Profile-Name TLV | 2345 | | | 2346 | Section 5.3 | List-Action TLV, white and black lists only | 2347 | | | 2348 | Section 5.5 | Bandwidth-Allocation TLV | 2349 | | | 2350 | Section 5.6 | White-List-CAC TLV | 2351 | | | 2352 | Section 5.11 | Multicast-Flow TLV | 2353 +--------------+----------------------------------------------------+ 2355 Table 3: Protocol Requirements For Conditional Access with White and 2356 Black Lists 2358 6.1.4. Protocol Requirements For Conditional Access With Grey Lists 2359 Table 4 specifies the protocol elements within Section 4 and 2360 Section 5 that MUST be implemented to support the conditional access 2361 with grey lists multicast capability. Additionally, implementation 2362 of the Multicast Replication Control message requires implementation 2363 of the Command TLV (Section 4.4 of [RFC6320] with additional details 2364 in Section 4.3 of this document). 2366 +--------------+----------------------------------------------------+ 2367 | Reference | Protocol Element | 2368 +--------------+----------------------------------------------------+ 2369 | Section 4.1 | Provisioning message with Multicast-Service- | 2370 | | Profile TLV, grey lists only, and MRepCtl-CAC TLV | 2371 | | | 2372 | Section 4.2 | Port Management message with Multicast-Service- | 2373 | | Profile-Name and Bandwidth-Allocation TLVs. | 2374 | | | 2375 | Section 4.3 | Multicast Replication Control message | 2376 | | | 2377 | Section 4.4 | Multicast Admission Control Message | 2378 | | | 2379 | Section 4.9 | Multicast Flow Query Request and Response messages | 2380 | | | 2381 | Section 5.1 | Multicast-Service-Profile TLV, grey lists only | 2382 | | | 2383 | Section 5.2 | Multicast-Service-Profile-Name TLV | 2384 | | | 2385 | Section 5.3 | List-Action TLV, grey lists only | 2386 | | | 2387 | Section 5.4 | Sequence Number TLV | 2388 | | | 2389 | Section 5.5 | Bandwidth-Allocation TLV | 2390 | | | 2391 | Section 5.7 | MRepCtl-CAC TLV | 2392 | | | 2393 | Section 5.9 | Request-Source-IP TLV | 2394 | | | 2395 | Section 5.10 | Request-Source-MAC TLV | 2396 | | | 2397 | Section 5.11 | Multicast-Flow TLV | 2398 +--------------+----------------------------------------------------+ 2400 Table 4: Protocol Requirements For Conditional Access with Grey Lists 2402 6.1.5. Protocol Requirements For Delegated Bandwidth 2404 Table 5 specifies the protocol elements within Section 4 and 2405 Section 5 that MUST be implemented to support the delegated bandwidth 2406 multicast capability. 2408 +-----------------+-------------------------------------------------+ 2409 | Reference | Protocol Element | 2410 +-----------------+-------------------------------------------------+ 2411 | Section 4.2 | Port Management message with Bandwidth- | 2412 | | Allocation TLV. | 2413 | | | 2414 | Section 4.5 | Bandwidth Reallocation Request Message | 2415 | | | 2416 | Section 4.6 | Bandwidth Transfer Message | 2417 | | | 2418 | Section 4.7 | Delegated Bandwidth Query Request Message | 2419 | | | 2420 | Section 4.8 | Delegated Bandwidth Query Response Message | 2421 | | | 2422 | Section 4.9 | Multicast Flow Query Request and Response | 2423 | | messages | 2424 | | | 2425 | Section 5.5 | Bandwidth-Allocation TLV | 2426 | | | 2427 | Section 5.8 | Bandwidth-Request TLV | 2428 | | | 2429 | Section 5.11 | Multicast-Flow TLV | 2430 +-----------------+-------------------------------------------------+ 2432 Table 5: Protocol Requirements For Delegated Bandwidth 2434 6.2. Capability-Specific Procedures for Providing Multicast Service 2436 This section describes multicast service procedures for each 2437 capability as if it were the only multicast capability within the 2438 negotiated set. Procedures involving combinations of multicast 2439 capabilities are described in Section 6.3. 2441 The use of the Multicast Flow Query Request and Response messages to 2442 determine the association between multicast flows and ports is common 2443 to all multicast capabilities. No additional text is required here, 2444 beyond that already given in Section 4.9 to describe the use of those 2445 messages. 2447 6.2.1. Procedures For NAS-Initiated Replication 2448 NAS-initiated replication may be negotiated to support a mode of 2449 operation where IGMP/MLD requests are terminated on the NAS. 2450 Alternatively, it may be negotiated to allow the NAS to respond to 2451 requests sent by other means (e.g., through application signalling) 2452 that require the replication of multicast channels to a given access 2453 line. 2455 6.2.1.1. Provisioning 2457 The NAS MAY perform admission control for NAS-initiated replication. 2458 In this case, it MUST NOT include the MRepCtl-CAC TLV in a 2459 Provisioning message sent to the AN. Alternatively, the NAS MAY 2460 enable admission control at the AN for NAS-initiated replication. To 2461 do this, it MUST include the MRepCtl-CAC TLV in a Provisioning 2462 message sent to the AN and it MUST also include a Bandwidth- 2463 Allocation TLV in a Port Management message for each access line. 2465 6.2.1.2. Multicast Service Procedures 2467 The procedures associated with NAS-initiated replication are 2468 straightforward. To initiate replication, the NAS MUST send a 2469 Multicast Replication Control message to the AN, containing one or 2470 more commands adding flows, as described in Section 4.3.1. To 2471 terminate replication the NAS MUST send a Multicast Replication 2472 Control message where the commands delete instead of adding the 2473 flows. The AN acts upon these messages as specified in 2474 Section 4.3.2. 2476 6.2.2. Procedures For Committed Bandwidth Reporting 2478 Committed bandwidth reporting may be negotiated if the NAS requires 2479 current knowledge of the amount of multicast bandwidth committed to 2480 each access line and cannot obtain this information by other means. 2482 6.2.2.1. Provisioning 2484 The default buffering time when committed bandwidth reporting is 2485 enabled is zero (immediate reporting). To change this, the NAS MAY 2486 send an instance of the Report-Buffering-Time TLV containing a non- 2487 zero time value to the AN in a Provisioning message. If the NAS 2488 subsequently wishes to change the buffering time again, it MAY do so 2489 in another Provisioning message. 2491 6.2.2.2. Multicast Service Procedures 2493 If the buffering time for committed bandwidth reporting is zero, the 2494 AN MUST send a Committed Bandwidth Report message to the NAS each 2495 time the amount of multicast bandwidth committed to any access line 2496 under its control changes. 2498 If a non-zero value is provided in the Report-Buffering-Time TLV, the 2499 AN at any given moment is in one of two states: not-buffering, or 2500 buffering. The AN enters buffering state if it is in not-buffering 2501 state and the multicast bandwidth amount committed to some access 2502 line changes. It leaves buffering state when the AN sends a 2503 Committed Bandwidth Report. 2505 Upon entry to the buffering state, the AN MUST start a buffering 2506 timer and create a Committed Bandwidth Report message containing a 2507 Committed-Bandwidth TLV for the triggering access line, but MUST NOT 2508 send it. If a multicast bandwidth change occurs for another access 2509 line, the AN MUST add a new Committed-Bandwidth TLV to the message 2510 for that additional line. If a multicast bandwidth change occurs for 2511 a line for which a Committed-Bandwidth TLV is already present in the 2512 buffered report, the AN MUST update the corresponding Committed- 2513 Bandwidth TLV to contain the new bandwidth value, rather than adding 2514 another Committed-Bandwidth TLV for the same access line. 2516 The buffering timer expires after the period provided by the Report- 2517 Buffering-Time TLV. When it expires, the AN MUST send the Committed 2518 Bandwidth Report message that it has been accumulating to the NAS. 2519 Exceptionally, the AN MAY choose to send the message before the timer 2520 expires, in which case it MUST clear the buffering timer when the 2521 message is sent. In either case, the AN enters the not-buffering 2522 state as a result. 2524 Report buffering implies that NAS reaction to changes in multicast 2525 bandwidth usage is delayed by the amount of the buffering period. 2526 The choice of buffering period must take this into consideration. 2528 6.2.3. Procedures For Conditional Access With Black and White Lists 2530 6.2.3.1. Provisioning 2532 The NAS provisions named multicast service profiles containing white 2533 and black lists on the AN using the Provisioning message containing 2534 one or more Multicast-Service-Profile TLVs. The NAS MAY update the 2535 contents of these profiles from time to time as required, by sending 2536 additional Provisioning messages with Multicast-Service-Profile TLVs 2537 containing incremental modifications to the existing white and black 2538 lists or replacements for them. 2540 The NAS assigns a specific multicast service profile to an individual 2541 access line using the Port Management message containing a Multicast- 2542 Service-Profile-Name TLV. The NAS MAY change the multicast service 2543 profile for a given access line at any time by sending a Port 2544 Management message identifying a new multicast service profile. 2546 The NAS MAY choose to enable admission control at the AN for white- 2547 listed flows. To do this, it MUST send a Provisioning message as 2548 described in Section 4.1, which includes the White-List-CAC TLV and 2549 it MUST provide a multicast bandwidth allocation for each access line 2550 by including a Bandwidth-Allocation TLV in a Port Management message. 2552 6.2.3.2. Multicast Service Procedures 2554 The conditional access with white and black lists capability assumes 2555 that IGMP/MLD requests are terminated on the AN. When the AN 2556 receives a "join" request, it MUST check to see whether the requested 2557 flow is white-listed or black-listed as described below. Requests 2558 for black-listed flows MUST be discarded. If the NAS has enabled 2559 admission control on the AN as described in the previous section, but 2560 a white-listed flow would cause the amount of committed multicast 2561 bandwidth to exceed the provisioned limit, the request MUST be 2562 discarded. The AN replicates flows passing these checks to the 2563 access line. 2565 To determine if a requested flow is white-listed, the AN searches for 2566 a best match to the flow in the applicable multicast service profile. 2567 Matching is done on the prefixes specified in the profile, ignoring 2568 the address bits of lower order than those in the prefix. 2570 If the requested multicast flow matches multiple lists associated 2571 with the access line, then the most specific match will be considered 2572 by the AN. If the most specific match occurs in multiple lists, the 2573 black list entry takes precedence over the white list. In this 2574 context, the most specific match is defined as: 2576 o first, most specific match (longest prefix length) on the 2577 multicast group address (i.e., on G of ) 2579 o then, most specific match (longest prefix length) on the unicast 2580 source address (i.e. on S of ) 2582 If the requested multicast flow is not part of any list, the join 2583 message SHOULD be discarded by the AN. This default behavior can 2584 easily be changed by means of a "catch-all" statement in the white 2585 list. For instance, adding () in the white List would make 2586 the default behavior to accept join messages for a multicast flow 2587 that has no other match on any list. 2589 When the AN receives a "leave" request, it terminates replication of 2590 the multicast flow. 2592 If the AN receives a Provisioning message which updates an existing 2593 multicast service profile, the AN MUST review the status of active 2594 flows on all ports to which the updated profile is currently 2595 assigned. Similarly, if a Port Management message assigns a new 2596 multicast service profile to a given port, the AN MUST review all 2597 active flows on that port. If the most specific match for any flow 2598 is a black list entry, the flow MUST be terminated immediately. If 2599 any of the remaining flows do not match an entry in the white list, 2600 they also MUST be terminated immediately. White listed flows MUST be 2601 allowed to continue. 2603 6.2.4. Procedures For Conditional Access With Grey Lists 2605 6.2.4.1. Provisioning 2607 The NAS provisions named multicast service profiles containing grey 2608 lists on the AN using the Provisioning message containing one or more 2609 Multicast-Service-Profile TLVs. The NAS MAY update the contents of 2610 these profiles from time to time as required, by sending additional 2611 Provisioning messages with Multicast-Service-Profile TLVs containing 2612 incremental modifications to the existing grey lists or replacements 2613 for them. 2615 The NAS assigns a specific multicast service profile to an individual 2616 access line using the Port Management message containing a Multicast- 2617 Service-Profile-Name TLV. The NAS MAY change profiles on the line by 2618 sending a subsequent Port Management message identifying a new 2619 profile. 2621 The NAS MAY perform admission control for grey-listed flows. In that 2622 case, the NAS MUST NOT include the MRepCtl-CAC TLV in a Provisioning 2623 message sent to the AN. Alternatively, the NAS MAY enable admission 2624 control at the AN for grey-listed flows. To do this, it MUST include 2625 the MRepCtl-CAC TLV in a Provisioning message sent to the AN and MUST 2626 also provide a Bandwidth-Allocation TLV in a Port Management message 2627 for each access line. 2629 6.2.4.2. Multicast Service Procedures 2631 The conditional access with grey lists capability assumes that IGMP/ 2632 MLD requests are terminated on the AN. When the AN receives a "join" 2633 request, it MUST determine whether there is a match to the requested 2634 flow in the grey list of the multicast service profile provisioned 2635 against the given access line. If there is no match, the request is 2636 discarded. Otherwise, the AN MUST send a Multicast Admission Control 2637 message to the NAS with content identifying the access line and the 2638 multicast flow to be added. As indicated in Section 4.4, the AN MAY 2639 add information identifying the requestor by IP address and/or MAC 2640 address. 2642 If the NAS decides to enable the flow, it MUST send a Multicast 2643 Replication Control request to the AN to replicate the flow to the 2644 access line with the Result field set to Nack (0x1), as described in 2645 Section 4.3.1. 2647 When the AN receives the Multicast Replication Control request, it 2648 performs admission control if admission control has been enabled as 2649 described in the previous section. If admitting the flow would cause 2650 the committed multicast bandwidth at the access line to exceed the 2651 provisioned limit, the AN reports an error to the NAS as described in 2652 Section 4.3.2. Otherwise it replicates the multicast flow as 2653 requested. 2655 If the NAS decides not to permit the flow, it MAY send a Multicast 2656 Replication Control message in response to the Multicast Admission 2657 Control message to allow the AN to update its internal records. The 2658 content of this message is described in Section 4.4.2. 2660 When the AN receives a "leave" request, it MUST terminate replication 2661 of the flow to the access line. It MUST then send a Multicast 2662 Admission Control message to the NAS indicating the deletion. The 2663 NAS updates its internal records but MUST NOT respond to the message. 2665 If the AN receives a Provisioning message which updates an existing 2666 multicast service profile, the AN MUST review the status of active 2667 flows on all ports to which the updated profile has been assigned. 2668 Similarly, if a Port Management message that assigns a new profile to 2669 a given port, the AN MUST review all active flows on that port. In 2670 either case, if any flow does not match an entry in the grey list, it 2671 MUST be terminated immediately. 2673 6.2.5. Procedures For Delegated Bandwidth 2675 6.2.5.1. Provisioning 2677 The NAS SHOULD provision an initial amount of delegated multicast 2678 bandwidth for each access line using the Port Management message 2679 containing the Bandwidth-Allocation TLV. 2681 If it fails to do so and a value has not been provisioned on the 2682 AN by other means, the AN will be forced to request a bandwidth 2683 allocation as soon as it receives a "join" request. 2685 The NAS MAY at any time force an update of the amount of delegated 2686 bandwidth by the same means. 2688 6.2.5.2. Multicast Service Procedures 2690 The delegated bandwidth capability assumes that IGMP/MLD requests are 2691 terminated on the AN. When the AN receives a "join" request, it 2692 checks whether it has sufficient remaining uncommitted multicast 2693 bandwidth on the access line to accommodate the new multicast flow. 2694 If not, it MAY send a request to the NAS for an increased allocation 2695 of delegated bandwidth, using the Bandwidth Reallocation Request 2696 message. The NAS MUST return a Bandwidth Transfer message indicating 2697 whether it has granted the request, and if so, what is the new amount 2698 of delegated bandwidth. 2700 If the AN has sufficient uncommitted multicast capacity to admit the 2701 request, either originally or as the result of a successful request 2702 to the NAS, it replicates the requested flow to the access line. 2703 Otherwise it discards the request. 2705 When the AN receives a "leave" request for an active flow, it ceases 2706 replication. 2708 The NAS or AN MAY at some point detect that their respective views of 2709 the amount of delegated bandwidth are inconsistent. If so, they can 2710 recover using procedures described in Section 4.5 and Section 4.6. 2711 As a further aid to synchronization, either the NAS or the AN MAY 2712 from time to time check the peer's view of the amount of delegated 2713 bandwidth using the Delegated Bandwidth Query message. 2715 The NAS or AN MAY at any time release bandwidth to the peer using an 2716 autonomous Bandwidth Transfer message. The contents of this message 2717 are described in Section 4.6. 2719 6.3. Combinations of Multicast Capabilities 2721 6.3.1. Combination of Conditional Access With White and Black Lists and 2722 Conditional Access With Grey Lists 2724 If conditional access with white and black lists is combined with 2725 conditional access with grey lists, provisioning of the multicast 2726 service profiles is as described in Section 6.2.3.1 except that 2727 multicast service profiles will also include grey lists. Admission 2728 control is enabled independently on the AN for white lists by 2729 including the White-List-CAC TLV in the Provisioning message and for 2730 grey lists by including the MRepCtl-CAC TLV in the Provisioning 2731 message. The Bandwidth-Allocation TLV provisions an amount that 2732 applies to both white- and grey- listed flows if admission control is 2733 enabled for both. 2735 With regard to multicast service procedures, one point of difference 2736 from the individual capabilities must be noted. This is an 2737 interaction during the profile matching procedure. The AN MUST seek 2738 the best match amongst multiple lists as described in 2739 Section 6.2.3.2. However, if there are multiple matches of equal 2740 precision, the order of priority is black list first, grey list 2741 second, and white list last. 2743 Once profile matching has been completed, processing of a "join" 2744 request is as described in Section 6.2.3.2 for white or black listed 2745 flows or Section 6.2.4.2 for grey listed flows. Requests that do not 2746 match any list SHOULD be discarded. 2748 When the AN receives a "leave" request, it MUST terminate replication 2749 of the flow to the access line. If the flow was grey-listed, the AN 2750 MUST then send a Multicast Admission Control message to the NAS 2751 indicating the deletion. Thus the AN needs to retain the fact that 2752 the flow was grey-listed for the life of the flow. 2754 If the AN receives a Provisioning message which updates an existing 2755 multicast service profile, the AN MUST review the status of active 2756 flows on all ports to which the updated profile is currently 2757 assigned. Similarly, if a Port Management message assigns a new 2758 multicast service profile to a given port, the AN MUST review all 2759 active flows on that port. If any flow has its most specific match 2760 in a black list entry, it MUST be terminated immediately. If any of 2761 the remaining flows do not match an entry in the white or grey list, 2762 they MUST also be terminated immediately. Finally, if any remaining 2763 flows were originally admitted because they were white-listed, but 2764 after the change they are grey-listed, the AN MUST generate a 2765 Multicast Flow Query response message autonomously as if it were 2766 responding to a Multicast Flow Query request, listing all such flows. 2767 These flows MUST be allowed to continue until the NAS or the 2768 subscriber terminates them. Flows with their most specific match in 2769 the white list MUST be allowed to continue. 2771 The autonomously-generated Multicast Flow Query response message MUST 2772 be formatted as if it were a successful response to a request 2773 containing no Target and no Multicast-Flow TLV, as described in 2774 Section 4.9.2, with the exception that the Transaction-Id MUST be set 2775 to all zeroes. 2777 6.3.2. Combination of Conditional Access With Delegated Bandwidth 2779 The provisioning and bandwidth management procedures of Section 6.2.5 2780 apply in addition to the procedures in Section 6.2.3, Section 6.2.4, 2781 or Section 6.3.1 as applicable. Admission control follows the rules 2782 for conditional access in terms of matching flows against white and 2783 black and/or grey lists and performing or not performing bandwidth 2784 checks at the AN, but the amount of bandwidth used by the AN to 2785 perform admission control is negotiable as described in 2786 Section 6.2.5.2. 2788 6.3.3. Combination of NAS-Initiated Replication with Other Capabilities 2790 NAS-initiated replication can coexist with the other capabilities, 2791 but some means must exist to prevent double replication of flows. 2792 The simplest way to do this is to terminate all IGMP/MLD requests on 2793 the AN, so that NAS-initiated replication is stimulated only by 2794 signalling through other channels. Other arrangements are possible, 2795 but need not be discussed here. 2797 Assuming the necessary separation of responsibilities, the only point 2798 of interaction between NAS-initiated replication and the other 2799 multicast capabilities is in the area of admission control. 2800 Specifically, if the AN is to do admission control for flows added by 2801 Multicast Replication Control messages, regardless of whether they 2802 are part of NAS-initiated replication or grey list multicast service 2803 processing, the NAS includes the MRepCtl-CAC TLV in a Provisioning 2804 message and the Bandwidth-Allocation TLV in a Port Management 2805 message. If instead the NAS will do admission control for flows 2806 added by Multicast Replication Control messages, regardless of 2807 whether they are part of NAS-initiated replication or grey list 2808 multicast service processing, it does not send the MRepCtl-CAC TLV in 2809 a Provisioning messages to the AN. The NAS can independently enable 2810 Admission Control for white flows on the AN by including the White- 2811 List-CAC TLV in the Provisioning message. 2813 6.3.4. Combinations of Committed Bandwidth Reporting with Other 2814 Multicast Capabilities 2816 Committed bandwidth reporting can take place independently of which 2817 other multicast capabilities have been negotiated. However, some 2818 combinations do not make sense because of redundancy. In particular, 2819 the NAS obtains the same information that committed bandwidth 2820 reporting gives if the only other capabilities operating are NAS- 2821 initiated replication and/or conditional access with grey lists. 2823 7. Security Considerations 2825 The security considerations of ANCP are discussed in [RFC6320] and in 2826 [RFC5713]. Multicast does not in principle introduce any new 2827 security considerations, although it does increase the attractiveness 2828 of the ANCP protocol as a means of denial of service (e.g., through 2829 direction of multicast streams onto the target) or theft of service. 2831 8. IANA Considerations 2833 IANA NOTE: Please replace XXXX with the RFC number of this document. 2835 This document defines the following additional values within the ANCP 2836 Message Type Name Space registry: 2838 +--------------+--------------------------------+-----------+ 2839 | Message Type | Message Name | Reference | 2840 +--------------+--------------------------------+-----------+ 2841 | 144 | Multicast Replication Control | RFC XXXX | 2842 | | | | 2843 | 145 | Multicast Admission Control | RFC XXXX | 2844 | | | | 2845 | 146 | Bandwidth Reallocation Request | RFC XXXX | 2846 | | | | 2847 | 147 | Bandwidth Transfer | RFC XXXX | 2848 | | | | 2849 | 148 | Delegated Bandwidth Query | RFC XXXX | 2850 | | | | 2851 | 149 | Multicast Flow Query | RFC XXXX | 2852 | | | | 2853 | 150 | Committed Bandwidth Report | RFC XXXX | 2854 +--------------+--------------------------------+-----------+ 2856 This document defines the following additional values for the ANCP 2857 Result Code registry. In support of these assignments, IANA is 2858 requested to change the lower limit of 0x100 specified by [RFC6320] 2859 for assignments by IETF Consensus to 0x64. 2861 +--------------+------------------------------------+---------------+ 2862 | Result Code | One-Line Description | Reference | 2863 +--------------+------------------------------------+---------------+ 2864 | 0x64 | Command error. | RFC XXXX | 2865 | | | | 2866 | 0x65 | Invalid flow address. | RFC XXXX | 2867 | | | | 2868 | 0x66 | Multicast flow does not exist. | RFC XXXX | 2869 | | | | 2870 | 0x67 | Invalid preferred bandwidth | RFC XXXX | 2871 | | amount. | | 2872 | | | | 2873 | 0x68 | Inconsistent views of delegated | RFC XXXX | 2874 | | bandwidth amount. | | 2875 | | | | 2876 | 0x69 | Bandwidth request conflict. | RFC XXXX | 2877 +--------------+------------------------------------+---------------+ 2879 This document defines the following additional values for the ANCP 2880 Command Code registry: 2882 +-----------------+---------------------------------+---------------+ 2883 | Command Code | Command Code Directive Name | Reference | 2884 | Value | | | 2885 +-----------------+---------------------------------+---------------+ 2886 | 1 | Add | RFC XXXX | 2887 | | | | 2888 | 2 | Delete | RFC XXXX | 2889 | | | | 2890 | 3 | Delete All | RFC XXXX | 2891 | | | | 2892 | 4 | Admission Control Reject | RFC XXXX | 2893 | | | | 2894 | 5 | Conditional Access Reject | RFC XXXX | 2895 | | | | 2896 | 6 | Admission Control and | RFC XXXX | 2897 | | Conditional Access Reject | | 2898 +-----------------+---------------------------------+---------------+ 2900 This document defines the following additional values within the ANCP 2901 TLV Type Registry: 2903 +-----------+--------------------------------+-----------+ 2904 | Type Code | TLV Name | Reference | 2905 +-----------+--------------------------------+-----------+ 2906 | 0x0013 | Multicast-Service-Profile | RFC XXXX | 2907 | | | | 2908 | 0x0015 | Bandwidth-Allocation | RFC XXXX | 2909 | | | | 2910 | 0x0016 | Bandwidth-Request | RFC XXXX | 2911 | | | | 2912 | 0x0018 | Multicast-Service-Profile-Name | RFC XXXX | 2913 | | | | 2914 | 0x0019 | Multicast-Flow | RFC XXXX | 2915 | | | | 2916 | 0x0021 | List-Action | RFC XXXX | 2917 | | | | 2918 | 0x0022 | Sequence-Number | RFC XXXX | 2919 | | | | 2920 | 0x0024 | White-List-CAC | RFC XXXX | 2921 | | | | 2922 | 0x0025 | MRepCtl-CAC | RFC XXXX | 2923 | | | | 2924 | 0x0092 | Request-Source-IP | RFC XXXX | 2925 | | | | 2926 | 0x0093 | Request-Source-MAC | RFC XXXX | 2927 | | | | 2928 | 0x0094 | Report-Buffering-Time | RFC XXXX | 2929 | | | | 2930 | 0x0095 | Committed-Bandwidth | RFC XXXX | 2931 +-----------+--------------------------------+-----------+ 2933 This document defines the following additional values for the ANCP 2934 Capability Type registry: 2936 +-------+---------------------+--------+--------------+-------------+ 2937 | Value | Capability Type | Tech | Capability | Reference | 2938 | | Name | Type | Data? | | 2939 +-------+---------------------+--------+--------------+-------------+ 2940 | 3 | NAS-Initiated | 0 | No | RFC XXXX | 2941 | | Replication | | | | 2942 | | | | | | 2943 | 5 | Committed Bandwidth | 0 | No | RFC XXXX | 2944 | | Reporting | | | | 2945 | | | | | | 2946 | 6 | Conditional Access | 0 | No | RFC XXXX | 2947 | | With White and | | | | 2948 | | Black Lists | | | | 2949 | | | | | | 2950 | 7 | Conditional Access | 0 | No | RFC XXXX | 2951 | | With Grey Lists | | | | 2952 | | | | | | 2953 | 8 | Bandwidth | 0 | No | RFC XXXX | 2954 | | Delegation | | | | 2955 +-------+---------------------+--------+--------------+-------------+ 2957 9. Acknowledgements 2959 The authors would like to acknowledge Wojciech Dec for providing 2960 useful input to this document, Robert Rennison for his help in 2961 shaping the definition of the Multicast-Service-Profile TLV, Shridhar 2962 Rao for his comments and suggestions and Aniruddha A for his proposal 2963 that formed the base of the Multicast Flow Reporting solution. 2964 Philippe Champagne, Sanjay Wadhwa and Stefaan De Cnodder provided 2965 substantial contributions on the solution for the NAS initiated 2966 multicast control use case. Kristian Poscic provided the committed 2967 bandwidth reporting use case. 2969 10. References 2971 10.1. Normative References 2973 [PIMreg] IANA, "http://www.iana.org/assignments/pim-parameters/pim- 2974 parameters.xhtml", 2005. 2976 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2977 Requirement Levels", BCP 14, RFC 2119, March 1997. 2979 [RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast 2980 Listener Discovery (MLD) for IPv6", RFC 2710, October 2981 1999. 2983 [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. 2984 Thyagarajan, "Internet Group Management Protocol, Version 2985 3", RFC 3376, October 2002. 2987 [RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery 2988 Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. 2990 [RFC6320] Wadhwa, S., Moisand, J., Haag, T., Voigt, N., and T. 2991 Taylor, "Protocol for Access Node Control Mechanism in 2992 Broadband Networks", RFC 6320, October 2011. 2994 10.2. Informative References 2996 [IEEE48] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/ 2997 EUI48.html", 2010. 2999 [IEEE64] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/ 3000 EUI64.html", 2010. 3002 [RFC5384] Boers, A., Wijnands, I., and E. Rosen, "The Protocol 3003 Independent Multicast (PIM) Join Attribute Format", RFC 3004 5384, November 2008. 3006 [RFC5713] Moustafa, H., Tschofenig, H., and S. De Cnodder, "Security 3007 Threats and Security Requirements for the Access Node 3008 Control Protocol (ANCP)", RFC 5713, January 2010. 3010 [RFC5851] Ooghe, S., Voigt, N., Platnic, M., Haag, T., and S. 3011 Wadhwa, "Framework and Requirements for an Access Node 3012 Control Mechanism in Broadband Multi-Service Networks", 3013 RFC 5851, May 2010. 3015 Appendix A. Example of Messages and Message Flows 3017 This appendix provides an example in which most of the possible 3018 message flows for multicast control are illustrated. This appendix 3019 is for informational purposes only. In case of discrepancy with text 3020 of the body of this document, the text in the body of the document is 3021 to be considered as the normative text. 3023 Assume the following, for a given access port: 3025 o The basic subscribed service is white-listed. The AN will be 3026 responsible for admission control for this service. 3028 o Some premium services are available, but requests for these 3029 services must be referred to the policy server for proper credit 3030 processing. For this reason they are grey-listed. The NAS will 3031 be responsible for admission control for these services. 3033 o The subscriber has asked that certain services be blocked so that 3034 his children cannot view them. These services are black-listed. 3036 o All of the above services are Source-Specific Multicast (SSM). In 3037 addition, by means which bypass the AN, the subscriber can signal 3038 intent to join an on-line game service which is Any Source 3039 Multicast (ASM). The NAS is responsible for admission control for 3040 this service. 3042 o Bandwidth delegation is in effect to share video bandwidth between 3043 the AN and the NAS. 3045 The stated conditions require the use of four of the five 3046 capabilities specified in this memo. 3048 A.1. Provisioning Phase 3050 Assume that capability negotiation has been completed between the AN 3051 and NAS and that the set of negotiated capabilities includes the 3052 following four multicast capabilities: NAS-initiated replication, 3053 conditional access with white and black list, conditional access with 3054 grey list, and bandwidth delegation. At this point, the NAS can 3055 provision the service profiles on the AN and enable admission control 3056 at the AN for white-listed flows. To do this, the NAS sends the AN a 3057 Provisioning message containing this information. An example message 3058 providing the profile for our assumed subscriber is shown in Figure 3059 20. The message has the following contents: 3061 o Message type is 93. 3063 o The Result and Result Code fields in the header are set to zeroes, 3064 as specified [RFC6320]. 3066 o A Transaction identifier is assigned by the NAS. 3068 o The Multicast-Service-Profile TLV (of which typically there would 3069 be multiple instances) contains a Multicast-Service-Profile-Name 3070 TLV (with a length of 20 octets assumed for the example) and three 3071 List-Action TLVs, one each for the white, grey, and black lists 3072 within the profile. The white list flows come in two sets of 3073 group addresses: 233.252.0.0/29, coming from a server at 3074 192.0.2.15, and 233.252.0.32/29, coming from a server at 3075 192.0.2.16. The grey-listed flows are in the band 233.252.0.64/ 3076 29, coming from a server at 192.0.2.21. Finally, the black list 3077 flows are two individual flows that happen to overlap with the 3078 grey list band: 233.252.0.65, and 233.252.0.69, also with source 3079 192.0.2.21. 3081 o The White-List-CAC TLV indicates that the AN does admission 3082 control on white-listed flows. 3084 1 2 3 3085 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 3086 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3087 | Type (0x880C) | Length = 132 | 3088 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3089 | Version | Msg Type = 93 | 0x00 | Result Code = 0x000 | 3090 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3091 | Partition ID | Transaction Identifier | 3092 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3093 |I| SubMessage Number | Length = 132 | 3094 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3095 | M-Serv-Prof TLV Type = 0x13 | TLV Length = 112 | 3096 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3097 | M-S-Prof-Name TLV Type = 0x18 | Embedded TLV Length = 20 | 3098 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3099 | Multicast service profile name | 3100 ~ = "Cust 0127-53681-0003" ~ 3101 | | 3102 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3103 | List-Action TLV Type = 0x21 | Embedded TLV Length = 28 | 3104 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3105 | Oper = 0x01 |Lst Typ = 0x01 | Reserved = 0x0000 | 3106 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3107 | Address Family = 0x01 | List Length = 20 | 3108 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3109 | G Preflen = 29| S Preflen = 32| Group prefix = | 3110 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3111 | 233.252.0.0 | Source prefix = | 3112 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3113 | 192.0.2.15 | G Preflen = 29| S Preflen = 32| 3114 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3115 | Group prefix = 233.252.0.32 | 3116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3117 | Source prefix = 192.0.2.15 | 3118 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3119 | List-Action TLV Type = 0x21 | Embedded TLV Length = 18 | 3120 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3121 | Oper = 0x01 |Lst Typ = 0x03 | Reserved = 0x0000 | 3122 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3123 | Address Family = 0x01 | List Length = 10 | 3124 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3125 | G Preflen = 29| S Preflen = 32| Group prefix = / 3126 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3127 / 233.252.0.64 | Source prefix = / 3128 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3129 / 192.0.2.21 | Padding = 0x0000 | 3130 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3131 | List-Action TLV Type = 0x21 | Embedded TLV Length = 28 | 3132 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3133 | Oper = 0x01 |Lst Typ = 0x02 | Reserved = 0x0000 | 3134 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3135 | Address Family = 0x01 | List Length = 20 | 3136 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3137 | G Preflen = 32| S Preflen = 32| Group prefix = / 3138 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3139 / 233.252.0.65 | Source prefix = / 3140 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3141 / 192.0.2.21 | G Preflen = 32| S Preflen = 32| 3142 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3143 | Group prefix = 233.252.0.69 | 3144 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3145 | Source prefix = 192.0.2.21 | 3146 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3147 |White-List-CAC TLV Type = 0x24 | TLV Length = 0 | 3148 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3149 Figure 20: Example Provisioning Message 3151 TLV lengths in the figure are given in decimal for easier 3152 understanding. Note that the padding after the middle List-Action 3153 TLV is counted as part of length of the Multicast-Service-Profile 3154 TLV, but is not included in the length of that List-Action TLV. Note 3155 also that the Length field in the message header, unlike those in the 3156 TLVs, includes the message header itself, as required by [RFC6320]. 3157 Finally, note that the Provisioning message does not include a 3158 MRepCtl-CAC TLV since in our example admission control for grey 3159 listed flows and for NAS-initiated replication is performed by the 3160 NAS. 3162 As soon as the AN port comes up, the AN sends an ANCP PORT_UP message 3163 to the NAS specifying the Access Loop Circuit ID. The NAS replies 3164 with an ANCP Port Management message that, together with the other 3165 parameters, includes the multicast service profile name to be 3166 associated to that port along with the initial amount of delegated 3167 bandwidth. The corresponding message flow is illustrated in Figure 3168 21. 3170 +----------+ +---------+ +-----+ +-----+ 3171 |Subscriber| | Home | | AN | | NAS | 3172 +----------+ | Gateway | +-----+ +-----+ 3173 | +---------+ | | 3174 | | | | 3175 | | | | 3176 | | DSL Synch. | | 3177 | |---------------->| | 3178 | | |(M1)PORT_UP(Port ID) | 3179 | | |-------------------->| 3180 | | | (*) 3181 | | |(M2) PORT_MNGT | 3182 | | | (Port ID, | 3183 | | |Mcast S Profile Name,| 3184 | | |Bandwidth Allocation)| 3185 | | |<--------------------| 3187 (*) The NAS may optionally seek direction from an external 3188 Autorization/Policy Server 3190 Figure 21: Configuring an AN Port With Multicast Service Profile ID 3191 and Delegated Bandwidth Amount 3193 The Port Management message will typically contain other TLVs but our 3194 example (Figure 22) just shows the Target, Multicast-Service-Profile- 3195 Name, and Bandwidth-Allocation TLVs. The Target TLV identifies the 3196 subscriber line, the Multicast-Service-Profile-Name TLV is identical 3197 to the one contained in the Provisioning message, and the Bandwidth- 3198 Allocation TLV provides just enough bandwidth (2000 kbits/s) for one 3199 channel to start with. 3201 The following fields in the Port Management message header are shown 3202 with specific values either as directed by the base protocol document 3203 or for the sake of our example: 3205 o Message Type is 32. 3207 o Result is set to Nack (0x01) for this example. 3209 o Result Code is 0x000. 3211 o Port is set to 0. 3213 o Event Sequence Number, the R flag and the other bits marked x, 3214 Duration, the Event Flags, and the Flow Control Flags are all 3215 irrelevant for this function and are set to 0. 3217 o Function is set to 0x8, "Configure Connection Service Data". 3219 o X-Function is set to 0. 3221 o Tech Type is 0x05 (DSL). 3223 o Block lengths are calculated assuming a Circuit-Id length of 4 in 3224 our example. Recall that the example Multicast-Service-Profile- 3225 Name TLV length is 20. 3227 1 2 3 3228 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 3229 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3230 | Type (0x880C) | Length = 84 | 3231 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3232 | Version | Msg Type = 32 | 0x01 | Result Code = 0x000 | 3233 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3234 | Partition ID | Transaction Identifier | 3235 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3236 |I| SubMessage Number | Length = 84 | 3237 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3238 | Port = 0 | 3239 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3240 | Port Session Number | 3241 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3242 | Event Sequence Number = 0 | 3243 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3244 |R|x|x|x|x|x|x|x| Duration = 0 | Function = 0x8| X-Function = 0| 3245 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3246 | Event Flags | Flow Control Flags | 3247 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3248 |x|x|x|x|x|x|x|x| Msg Type = 32 |Tech Type=0x05 | Blk Len = 56 | 3249 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3250 | # of TLVs = 3 | Extension Block length = 44 | 3251 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3252 | Target TLV Type = 0x1000 | Target TLV Length = 8 | 3253 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3254 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3255 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3256 | Access Loop Circuit ID | 3257 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3258 | M-S-Prof-Name TLV Type = 0x18 | TLV Length = 20 | 3259 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3260 | Multicast service profile name | 3261 ~ = "Cust 0127-53681-0003" ~ 3262 | | 3263 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3264 | BW Alloc TLV Type = 0x15 | TLV Length = 4 | 3265 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3266 | Bandwidth value = 0x000007D0 (2000 kbits/s) | 3267 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3269 Figure 22: Example Port Management Message 3271 A.2. Handling a Grey-Listed Flow 3273 Suppose now that the subscriber chooses to watch the premium channel 3274 characterized by source 192.0.2.21, group 233.252.0.67. Upon 3275 receiving the Join request, the AN matches it against the multicast 3276 service profile for the port and determines that it is a grey-listed 3277 flow. Figure 23 illustrates the resulting ANCP message flow for the 3278 case of a simple join and leave, when admission control for grey- 3279 listed flows is not activated on the AN. 3281 To start the flow, the AN sends a Multicast Admission Control request 3282 (M1) to the NAS. The NAS decides whether flow can be admitted, 3283 applying both policy and bandwidth criteria. It returns its decision 3284 (positive in this example) in a Multicast Replication Control message 3285 (M2). Later, when the subscriber leaves the flow, the AN informs the 3286 NAS by sending another Multicast Admission Control message. 3288 +----------+ +-------+ +-----+ ANCP +-----+ 3289 |Subscriber| | Home | | AN |<---------->| NAS | 3290 +----------+ |Gateway| +-----+ +-----+ 3291 | +-------+ | | 3292 | | | Multicast | 3293 | Join(Grey-Fl) | Admission | 3294 |-----------+---------->| Control (M1) | 3295 | | |------------------>| 3296 | | | | (NAS performs 3297 | | | Multicast | admission 3298 | | | Replication (*) control) 3299 | | | Control (M2) | 3300 | Mcast Grey Flow |<------------------| 3301 |<======================+ | 3302 | | | | 3303 ~ ~ ~ ~ 3304 | | | Multicast | 3305 | Leave(Grey-Fl) | Admission | 3306 |-----------+---------->| Control (M3) | 3307 | | |------------------>| 3308 | | | | 3310 Grey-Fl : Multicast Flow matching an entry in grey List 3312 (*) The NAS may optionally seek direction from an external 3313 Authorization/Policy Server 3315 Figure 23: Successful Join/Leave Operations, Grey-Listed Flow 3317 The Multicast Admission Control message M1 contains: 3319 o an ANCP Header with: 3321 * Message-Type = 145 - Multicast Admission Control; 3323 * Result= 0x0 (Ignore); 3325 * Transaction-ID = Transaction-ID maintained by AN; 3327 o a Target TLV identifying the AN Port 3329 o a Command TLV containing: 3331 * Command Code = Add (1); 3333 * Accounting = 0; 3335 * a Multicast-Flow embedded TLV indicating the SSM multicast flow 3336 (Flow Type = 0x02) for which the AN received the IGMP Join: 3337 IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) Source 3338 Address = 192.0.2.21; 3340 * a Request-Source-IP embedded TLV containing the IGMP join 3341 source IP (192.0.2.100). 3343 The Multicast Admission Control message M1 is illustrated in Figure 3344 24: 3346 1 2 3 3347 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 3348 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3349 | Type (0x880C) | Length = 98 | 3350 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3351 | Version | Msg Type=145 | 0x0 | Result Code = 0x000 | 3352 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3353 | Partition ID | Transaction Identifier | 3354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3355 |I| SubMessage Number | Length = 98 | 3356 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3357 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3358 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3359 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3360 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3361 | Access Loop Circuit ID | 3362 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3363 | Command TLV Type = 0x11 | TLV Length = 28 | 3364 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3365 | Cmd Code=0x01 |Acctg = 0x00 | Reserved = 0x0000 | 3366 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3367 |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | 3368 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3369 |Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | 3370 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3371 | Multicast Group Address = 233.252.0.67 | 3372 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3373 | Unicast Source Address = 192.0.2.21 | 3374 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 3375 | Req-Src-IP TLV Type = 0x92 | Embedded TLV length = 4 | 3376 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3377 | Unicast Address = 192.0.2.100 | 3378 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3380 Figure 24: Multicast Admission Control Message Seeking To Add A Flow 3382 The Multicast Replication Control message M2 contains: 3384 o an ANCP Header with: 3386 * Message Type = 144 - Multicast Replication Control; 3387 * Result= 0x1 (NAck); 3389 * Transaction-ID = Transaction-ID maintained by NAS; 3391 o a Target TLV identifying the AN Port; 3393 o a Command TLV containing: 3395 * Command Code = Add (1); 3397 * Accounting = 1 (begin flow accounting), since in our example 3398 the operator wants accounting on this flow. 3400 * a Multicast-Flow embedded TLV indicating the SSM multicast flow 3401 (Flow Type = 0x02) that the NAS is admitting for this access 3402 port: IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) 3403 Source Address = 192.0.2.21. 3405 The Multicast Admission Control message M2 is illustrated in Figure 3406 25. 3408 1 2 3 3409 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 3410 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3411 | Type (0x880C) | Length = 48 | 3412 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3413 | Version | Msg Type=144 | 0x1 | Result Code = 0x000 | 3414 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3415 | Partition ID | Transaction Identifier | 3416 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3417 |I| SubMessage Number | Length = 48 | 3418 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3419 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3420 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3421 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3423 | Access Loop Circuit ID | 3424 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3425 | Command TLV Type = 0x11 | TLV Length = 20 | 3426 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3427 | Cmd Code=0x01 | Acctg = 0x01 | Reserved = 0x0000 | 3428 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3429 |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | 3430 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3431 |Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | 3432 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3433 | Multicast Group Address = 233.252.0.67 | 3434 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3435 | Unicast Source Address = 192.0.2.21 | 3436 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3438 Figure 25: Multicast Replication Control Message Admitting A Flow 3440 The Multicast Admission Control message M3 advising the NAS that the 3441 flow has been terminated contains: 3443 o an ANCP Header with: 3445 * Message-Type = 145 - Multicast Admission Control 3447 * Result= 0x0 (Ignore) 3449 * Transaction-ID = Transaction-ID maintained by AN 3451 o a Target TLV identifying the AN Port 3453 o a Command TLV containing: 3455 * a Command Code = Delete (2); 3457 * Accounting = 0; 3459 * a Multicast-Flow embedded TLV indicating the SSM multicast flow 3460 (Flow Type = 0x02) for which the AN received the IGMP leave: 3461 IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) Source 3462 Address = 192.0.2.21. 3464 * a Request-Source-IP embedded TLV containing the IGMP leave 3465 request source, IPv4 (0x01) address 192.0.2.100. 3467 The Multicast Admission Control message M3 is illustrated in Figure 3468 26. 3470 1 2 3 3471 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 3472 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3473 | Type (0x880C) | Length | 3474 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3475 | Version | Msg Type=145 | 0x0 | Result Code = 0x000 | 3476 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3477 | Partition ID | Transaction Identifier | 3478 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3479 |I| SubMessage Number | Length | 3480 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3481 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3482 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3483 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3484 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3485 | Access Loop Circuit ID | 3486 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3487 | Command TLV Type = 0x11 | TLV Length = 28 | 3488 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3489 | Cmd Code=0x02 |Acctg = 0x00 | Reserved = 0x0000 | 3490 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3491 |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | 3492 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3493 |Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | 3494 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3495 | Multicast Group Address = 233.252.0.67 | 3496 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3497 | Unicast Source Address = 192.0.2.21 | 3498 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3499 | Req-Src-IP TLV Type = 0x92 | Embedded TLV length = 4 | 3500 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3501 | Unicast Address = 192.0.2.100 | 3502 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3504 Figure 26: Multicast Admission Control Message Signalling Flow 3505 Termination 3507 A.3. Handling White-Listed Flows 3509 The NAS has enabled white list admission control on the AN, and the 3510 bandwidth delegation capability has been negotiated. White listed 3511 flows in themselves require no messages to the NAS, either upon 3512 admission or upon termination, but the AN may request an increase in 3513 the amount of delegated bandwidth if it needs the increase to admit a 3514 flow. 3516 Consider an example where the AN has already admitted one white- 3517 listed flow, thereby using up the initially provisioned amount of 3518 delegated bandwidth (2000 kbits/s). A request is received to join a 3519 new flow in the white list range. The AN chooses to send a Bandwidth 3520 Reallocation Request message to the NAS, requesting that the 3521 delegated bandwidth allocation be increased to 4000 kbits/s at a 3522 minimum, and preferably to 6000 kbits/s. 3524 In our example, the NAS is managing bandwidth tightly, as witnessed 3525 by its minimal initial allocation of just enough for one flow. It is 3526 willing to provide the minimum additional amount only, and therefore 3527 returns a Bandwidth Transfer message where the delegated bandwidth 3528 value is given as 4000 kbits/s. With this amount, the AN is able to 3529 admit the second white-listed flow. The AN could send a similar 3530 Bandwidth Transfer message back to the NAS bringing the delegated 3531 bandwidth amount back down to 2000 kbits/s when one of the flows is 3532 terminated, but this shows nothing new and is omitted. 3534 As one more point of illustration, suppose that the NAS chooses to 3535 audit the current amount of delegated bandwidth to ensure it is 3536 synchronized with the AN. It sends a Delegated Bandwidth Query 3537 request message to the AN, and receives a Delegated Bandwidth Query 3538 response message with the current allocation as the AN sees it. 3540 The complete message flow is shown in Figure 27. 3542 +----------+ +-------+ +-----+ ANCP +-----+ 3543 |Subscriber| | Home | | AN |<---------->| NAS | 3544 +----------+ |Gateway| +-----+ +-----+ 3545 | +-------+ | | 3546 | | | | 3547 | Join(White-F1) | | 3548 |-----------+---------->| | 3549 | | |AN performs | 3550 | Mcast White Flow 1 | admission control | 3551 |<======================+ | 3552 | | | | 3553 | Join(White-F2) | | 3554 |-----------+---------->|No bandwidth left | 3555 | | | | 3556 | | |Bandwidth | 3557 | | | Reallocation Req | 3558 | | |------------------>|(M1) 3559 | | | | 3560 | | | (*) 3561 | | |Bandwidth Transfer | 3562 | AN can now |<------------------|(M2) 3563 | admit flow | | 3564 | Mcast White Flow 2 | | 3565 |<======================+ | 3566 | | | | 3567 ~ ~ ~ ~ 3568 | | |Delegated Bandwidth| 3569 | | | Query request | 3570 | | |<------------------|(M3) 3571 | | | | 3572 | | |Delegated Bandwidth| 3573 | | | Query response | 3574 | | |------------------>|(M4) 3575 | | | | 3577 (*) The NAS may optionally seek direction from an external 3578 Authorization/Policy Server 3579 Figure 27: Successful Join/Leave Operations, White-Listed Flow 3581 The Bandwidth Reallocation Request message (M1) is shown in Figure 3582 28. The contents require little explanation. The Message Type for 3583 the Bandwidth Reallocation Request is 146. The Result field is set 3584 to 0x0 (Ignore). Besides the Target, the message has one other TLV, 3585 the Bandwidth-Request, with a TLV Type of 0x16. The TLV contains 3586 Required Amount and Preferred Amount fields, set to 4000 and 6000 3587 kbits/s respectively. 3589 1 2 3 3590 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 3591 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3592 | Type (0x880C) | Length = 36 | 3593 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3594 | Version | Msg Type=146 | 0x0 | Result Code = 0x000 | 3595 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3596 | Partition ID | Transaction Identifier | 3597 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3598 |I| SubMessage Number | Length = 36 | 3599 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3600 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3601 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3602 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3603 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3604 | Access Loop Circuit ID | 3605 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3606 |Bandwidth-Req TLV Type = 0x16 | TLV Length = 8 | 3607 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3608 | Required Amount = 0x00000FA0 (4000 kbits/s) | 3609 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3610 | Preferred Amount = 0x00001770 (6000 kbits/s) | 3611 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3613 Figure 28: Bandwidth Reallocation Request Message 3615 The Bandwidth Transfer message (M2) is shown in Figure 29. Again, 3616 the contents are easily understood. The Message Type for the 3617 Bandwidth Transfer message is 147. The Result field is set to 3618 Success (0x3). The message contains the Target TLV and the 3619 Bandwidth-Allocation TLV. The latter has a TLV Type of 0x15 and 3620 contains a Delegated Amount field, set to 4000 kbits/s. 3622 1 2 3 3623 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 3624 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3625 | Type (0x880C) | Length = 32 | 3626 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3627 | Version | Msg Type=147 | 0x3 | Result Code = 0x000 | 3628 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3629 | Partition ID | Transaction Identifier | 3630 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3631 |I| SubMessage Number | Length = 32 | 3632 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3633 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3634 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3635 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3636 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3637 | Access Loop Circuit ID | 3638 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3639 |BW-Allocation TLV Type = 0x15 | TLV Length = 4 | 3640 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3641 | Delegated Amount = 0x00000FA0 (4000 kbits/s) | 3642 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3644 Figure 29: NAS Response, Bandwidth Transfer Message 3646 The Delegated Bandwidth Query request message (M3) is shown in Figure 3647 30. The Message Type for the Delegated Bandwidth Query request 3648 message is 148. The Result field is set to AckAll (0x2). The 3649 message contains the Target TLV only. 3651 1 2 3 3652 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 3653 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3654 | Type (0x880C) | Length = 24 | 3655 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3656 | Version | Msg Type=148 | 0x2 | Result Code = 0x000 | 3657 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3658 | Partition ID | Transaction Identifier | 3659 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3660 |I| SubMessage Number | Length = 24 | 3661 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3662 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3663 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3664 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3665 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3666 | Access Loop Circuit ID | 3667 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3669 Figure 30: Delegated Bandwidth Query Request Message 3671 Finally, the Delegated Bandwidth Query response message (M4) is shown 3672 in Figure 31. The Message Type for the Delegated Bandwidth Query 3673 response message is 148. The Result field is set to Success (0x3). 3674 The message contains the Target TLV and the Bandwidth-Allocation TLV 3675 with the Delegated Amount field set to 4000 kbits/s. 3677 1 2 3 3678 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 3679 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3680 | Type (0x880C) | Length = 32 | 3681 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3682 | Version | Msg Type=148 | 0x3 | Result Code = 0x000 | 3683 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3684 | Partition ID | Transaction Identifier (copied from request) | 3685 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3686 |I| SubMessage Number | Length = 32 | 3687 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3688 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3689 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3690 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3691 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3692 | Access Loop Circuit ID | 3693 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3694 |BW-Allocation TLV Type = 0x15 | TLV Length = 4 | 3695 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3696 | Delegated Amount = 0x00000FA0 (4000 kbits/s) | 3697 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3699 Figure 31: Delegated Bandwidth Query Response Message 3701 A.4. Handling Of Black-Listed Join Requests 3703 This section introduces no new messages, since requests for flows in 3704 the black list are simply ignored. The one thing to point out is the 3705 overlap in our example between the set of flows in the grey list and 3706 the flows in the black list. This does not create any ambiguity, 3707 since not only does the black list have priority for equally good 3708 matches, but also the black list entries are more specific (group 3709 prefix lengths of 32 versus 29 in the grey list) than the grey list 3710 flow prefixes. 3712 A.5. Handling Of Requests To Join and Leave the On-Line Game 3714 The final class of multicast control actions in our example allows 3715 the subscriber to enter and leave the on-line game. As described at 3716 the beginning of this example, the game uses Any Source Multicast 3717 (ASM). Subscriber signalling bypasses the AN, going directly to the 3718 NAS (e.g., through a web interface). 3720 When the subscriber requests to join the game, the NAS (after 3721 applying policy and bandwidth checks) sends a Multicast Replication 3722 Control message to the AN to enable the flow on the port concerned. 3723 The AN knows not to apply admission control, since it has not 3724 received an MRepCtl-CAC TLV in the Provisioning message. When the 3725 subscriber leaves, the NAS sends another Multicast Replication 3726 Control message to delete the flow. This message sequence is shown 3727 in Figure 32. 3729 It is possible that the NAS finds that there is not enough bandwidth 3730 available to accommodate the subscriber's request. In this case, the 3731 NAS could send a Bandwidth Reallocation Request message to the AN, 3732 asking it to release some of the bandwidth delegated to it. This is 3733 not shown in the present example, since the messages are the same as 3734 those already presented with the exception that the Preferred Amount 3735 in the request will be *less than* or equal to the Required amount, 3736 rather than *greater than* or equal to it. 3738 +----------+ +-------+ +-----+ ANCP +-----+ 3739 |Subscriber| | Home | | AN |<---------->| NAS | 3740 +----------+ |Gateway| +-----+ +-----+ 3741 | +-------+ | | 3742 | | | | 3743 | Join game | | 3744 |-----------+------------------------------>| 3745 | | | Multicast | NAS performs 3746 | | | Replication (*) admission 3747 | | | Control (M1) | control 3748 | Mcast Game Flow |<------------------| 3749 |<=====================>+ | 3750 | | | | 3751 ~ ~ ~ ~ 3752 | | | | 3753 | Leave game | | 3754 |-----------+------------------------------>| 3755 | | | Multicast | 3756 | | | Replication | 3757 | | | Control (M2) | 3758 | Mcast Game Flow |<------------------| 3759 | discontinued | | 3760 | | | | 3762 (*) The NAS may optionally seek direction from an external 3763 Authorization/Policy Server 3765 Figure 32: NAS-Initiated Flows For On-Line Gaming 3767 Multicast Replication Control message (M1) in Figure 33 looks like 3768 the message in Figure 25 with two exceptions. The first is that the 3769 NAS has the option to set the Result field to AckAll (0x02) if it 3770 needs positive reassurance that the flow has been enabled. This was 3771 not done here to save having to depict a response differing only in 3772 the Result field. The larger difference in this example is that the 3773 flow description in the Multicast-Flow embedded TLV is that of an ASM 3774 multicast group (Flow Type = 0x01) with IPv4 (0x01) group address 3775 233.252.0.100. 3777 1 2 3 3778 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 3779 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3780 | Type (0x880C) | Length = 44 | 3781 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3782 | Version | Msg Type=144 | 0x1 | Result Code = 0x000 | 3783 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3784 | Partition ID | Transaction Identifier | 3785 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3786 |I| SubMessage Number | Length = 44 | 3787 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3788 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3789 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3790 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3791 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3792 | Access Loop Circuit ID | 3793 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3794 | Command TLV Type = 0x11 | TLV Length = 16 | 3795 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3796 | Cmd Code=0x01 | Acctg = 0x01 | Reserved = 0x0000 | 3797 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3798 |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 8 | 3799 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3800 |Flow Type=0x01 |Addr Fam =0x01 | Reserved = 0x0000 | 3801 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3802 | Multicast Group Address = 233.252.0.100 | 3803 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 3805 Figure 33: Enabling The Subscriber To Join An On-Line Game 3807 Message M2 terminating the flow when the subscriber leaves the game 3808 looks the same as the message in Figure 33 with two exceptions: the 3809 Command Code becomes Delete (2), and Accounting is set to 0 to turn 3810 off flow accounting. Of course, the Transaction Identifier values 3811 will differ between the two messages. 3813 A.6. Example Flow For Multicast Flow Reporting 3814 The example in this section is independent of the example in the 3815 preceding sections. 3817 Figure 34 illustrates a message flow in a case where the NAS queries 3818 the AN about which multicast flows are active on port 10, on port 11 3819 and on port 20 of the AN. 3821 +----------+ +-------+ +-----+ ANCP +-----+ 3822 |Subscriber| | Home | | AN |<---------->| NAS | 3823 +----------+ |Gateway| +-----+ +-----+ 3824 | +-------+ | | 3825 | | | Multicast Flow | 3826 | | | Query Request | 3827 | | | (M1) | 3828 | | |<------------------| 3829 | | | | 3830 | | | Multicast Flow | 3831 | | | Query Response | 3832 | | | (M2) | 3833 | | |------------------>| 3834 | | | | 3835 | | | | 3837 Figure 34: Per-Port Multicast Flow Reporting 3839 The Multicast Flow Query Request message (M1) is illustrated in 3840 Figure 35. The Message Type is 149. The Result field is set to 3841 AckAll (0x2). Three Target TLVs are present, identifying port 10, 3842 port 20, and port 11 respectively. 3844 0 1 2 3 3845 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 3846 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3847 | Type (0x880C) | Length | 3848 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3849 | Version | Msg Type = 149|Rslt=2 | Result Code = 0 | 3850 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3851 | Partition ID | Transaction Identifier | 3852 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3853 |I| SubMessage Number | Length | 3854 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3855 | Type = 0x1000 (Target) | Target TLV Length | 3856 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3857 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | 3858 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3859 | | 3860 ~ Access Loop Circuit ID (port10) ~ 3861 | | 3862 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3863 | Type = 0x1000 (Target) | Target TLV Length | 3864 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3865 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | 3866 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3867 | | 3868 ~ Access Loop Circuit ID (port20) ~ 3869 | | 3870 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3871 | Type = 0x1000 (Target) | Target TLV Length | 3872 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3873 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | 3874 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3875 | | 3876 ~ Access Loop Circuit ID (port11) ~ 3877 | | 3878 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3880 Figure 35: Multicast Flow Query Request Message For Per-Port 3881 Multicast Flow Reporting 3883 The Multicast Flow Query Response message (M2) is illustrated in 3884 Figure 36. It indicates that there is one active multicast flow 3885 [(192.0.2.1, 233.252.0.4)] on port 10, no active multicast flow on 3886 port 20 and two active multicast flows [(192.0.2.1, 233.252.0.4) and 3887 (192.0.2.2, 233.252.0.10)] on port 11. 3889 0 1 2 3 3890 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 3891 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3892 | Type (0x880C) | Length | 3893 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3894 | Version | Msg Type = 149|Rslt=3 | Result Code = 0 | 3895 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3896 | Partition ID | Transaction Identifier | 3897 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3898 |I| SubMessage Number | Length | 3899 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3900 | Type = 0x1000 (Target) | Target TLV Length | 3901 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3902 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | 3903 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3904 | | 3905 ~ Access Loop Circuit ID (port10) ~ 3906 | | 3907 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3908 |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | 3909 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3910 |Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | 3911 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3912 | Multicast Group Address = 233.252.0.4 | 3913 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3914 | Unicast Source Address = 192.0.2.1 | 3915 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 3916 | Type = 0x1000 (Target) | Target TLV Length | 3917 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3918 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | 3919 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3920 | | 3921 ~ Access Loop Circuit ID (port20) ~ 3922 | | 3923 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3924 | Type = 0x1000 (Target) | Target TLV Length | 3925 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3926 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | 3927 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3928 | | 3929 ~ Access Loop Circuit ID (port11) ~ 3930 | | 3931 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3932 |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | 3933 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3934 |Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | 3935 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3936 | Multicast Group Address = 233.252.0.4 | 3937 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3938 | Unicast Source Address = 192.0.2.1 | 3939 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 3940 |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | 3941 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3942 |Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | 3943 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3944 | Multicast Group Address: 233.252.0.10 | 3945 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3946 | Unicast Source Address = 192.0.2.2 | 3947 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 3949 Figure 36: Multicast Flow Query Response message For Per-Port 3950 Multicast Flow Reporting 3952 Authors' Addresses 3953 Francois Le Faucheur 3954 Cisco Systems 3955 Greenside, 400 Avenue de Roumanille 3956 Sophia Antipolis 06410 3957 France 3959 Phone: +33 4 97 23 26 19 3960 Email: flefauch@cisco.com 3962 Roberta Maglione 3963 Cisco Systems 3964 181 Bay Street 3965 Toronto, ON M5J 2T3 3966 Canada 3968 Email: robmgl@cisco.com 3970 Tom Taylor 3971 Huawei Technologies 3972 Ottawa 3973 Canada 3975 Email: tom.taylor.stds@gmail.com