idnits 2.17.1 draft-ietf-ancp-mc-extensions-10.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 : ---------------------------------------------------------------------------- ** There are 16 instances of too long lines in the document, the longest one being 3 characters in excess of 72. == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. == There are 8 instances of lines with multicast IPv4 addresses in the document. If these are generic example addresses, they should be changed to use the 233.252.0.x range defined in RFC 5771 Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 22, 2013) is 3900 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) == Unused Reference: 'RFC4601' is defined on line 3011, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE48' -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE64' -- Obsolete informational reference (is this intentional?): RFC 4601 (Obsoleted by RFC 7761) Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 4 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 Intended status: Standards Track R. Maglione 5 Expires: February 23, 2014 Cisco Systems 6 T. Taylor 7 Huawei 8 August 22, 2013 10 Multicast Control Extensions for ANCP 11 draft-ietf-ancp-mc-extensions-10.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 Status of This Memo 36 This Internet-Draft is submitted in full conformance with the 37 provisions of BCP 78 and BCP 79. 39 Internet-Drafts are working documents of the Internet Engineering 40 Task Force (IETF). Note that other groups may also distribute 41 working documents as Internet-Drafts. The list of current Internet- 42 Drafts is at http://datatracker.ietf.org/drafts/current/. 44 Internet-Drafts are draft documents valid for a maximum of six months 45 and may be updated, replaced, or obsoleted by other documents at any 46 time. It is inappropriate to use Internet-Drafts as reference 47 material or to cite them other than as "work in progress." 48 This Internet-Draft will expire on February 23, 2014. 50 Copyright Notice 52 Copyright (c) 2013 IETF Trust and the persons identified as the 53 document authors. All rights reserved. 55 This document is subject to BCP 78 and the IETF Trust's Legal 56 Provisions Relating to IETF Documents 57 (http://trustee.ietf.org/license-info) in effect on the date of 58 publication of this document. Please review these documents 59 carefully, as they describe your rights and restrictions with respect 60 to this document. Code Components extracted from this document must 61 include Simplified BSD License text as described in Section 4.e of 62 the Trust Legal Provisions and are provided without warranty as 63 described in the Simplified BSD License. 65 This document may contain material from IETF Documents or IETF 66 Contributions published or made publicly available before November 67 10, 2008. The person(s) controlling the copyright in some of this 68 material may not have granted the IETF Trust the right to allow 69 modifications of such material outside the IETF Standards Process. 70 Without obtaining an adequate license from the person(s) controlling 71 the copyright in such materials, this document may not be modified 72 outside the IETF Standards Process, and derivative works of it may 73 not be created outside the IETF Standards Process, except to format 74 it for publication as an RFC or to translate it into languages other 75 than English. 77 Table of Contents 79 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 80 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 81 3. Multicast Use Cases . . . . . . . . . . . . . . . . . . . . . 6 82 3.1. NAS Initiated Multicast Replication Control Use Case . . 7 83 3.1.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 7 84 3.1.2. Message Flow . . . . . . . . . . . . . . . . . . . . 7 85 3.2. Conditional Access and Admission Control Use Case . . . . 8 86 3.2.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 8 87 3.2.2. Message Flow . . . . . . . . . . . . . . . . . . . . 8 88 3.3. Multicast Flow Reporting Use Case . . . . . . . . . . . . 9 89 3.3.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 9 90 3.3.2. Message Flow . . . . . . . . . . . . . . . . . . . . 9 91 3.4. Committed Bandwidth Reporting Use Case . . . . . . . . . 10 92 3.4.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 10 93 3.4.2. Message Flow . . . . . . . . . . . . . . . . . . . . 10 94 4. ANCP Messages . . . . . . . . . . . . . . . . . . . . . . . . 11 95 4.1. Provisioning Message . . . . . . . . . . . . . . . . . . 11 96 4.1.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 12 97 4.1.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 13 98 4.2. Port Management Message . . . . . . . . . . . . . . . . . 14 99 4.2.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 15 100 4.2.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 15 101 4.3. Multicast Replication Control Message . . . . . . . . . . 16 102 4.3.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 19 103 4.3.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 20 104 4.4. Multicast Admission Control Message . . . . . . . . . . . 22 105 4.4.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 23 106 4.4.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 24 107 4.5. Bandwidth Reallocation Request Message . . . . . . . . . 25 108 4.5.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 25 109 4.5.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 26 110 4.6. Bandwidth Transfer Message . . . . . . . . . . . . . . . 29 111 4.6.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 30 112 4.6.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 30 113 4.7. Delegated Bandwidth Query Request Message . . . . . . . . 31 114 4.7.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 31 115 4.7.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 31 116 4.8. Delegated Bandwidth Query Response Message . . . . . . . 32 117 4.8.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 32 118 4.8.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 32 119 4.9. Multicast Flow Query Request and Response Messages . . . 33 120 4.9.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 34 121 4.9.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 34 122 4.10. Committed Bandwidth Report Message . . . . . . . . . . . 36 123 4.10.1. Sender Behaviour . . . . . . . . . . . . . . . . . . 36 124 4.10.2. Receiver Behaviour . . . . . . . . . . . . . . . . . 36 125 5. ANCP TLVs For Multicast . . . . . . . . . . . . . . . . . . . 37 126 5.1. Multicast-Service-Profile TLV . . . . . . . . . . . . . . 37 127 5.2. Multicast-Service-Profile-Name TLV . . . . . . . . . . . 38 128 5.3. List-Action TLV . . . . . . . . . . . . . . . . . . . . . 39 129 5.4. Sequence-Number TLV . . . . . . . . . . . . . . . . . . . 41 130 5.5. Bandwidth-Allocation TLV . . . . . . . . . . . . . . . . 42 131 5.6. White-List-CAC TLV . . . . . . . . . . . . . . . . . . . 42 132 5.7. MRepCtl-CAC TLV . . . . . . . . . . . . . . . . . . . . . 43 133 5.8. Bandwidth-Request TLV . . . . . . . . . . . . . . . . . . 43 134 5.9. Request-Source-IP TLV . . . . . . . . . . . . . . . . . . 44 135 5.10. Request-Source-MAC TLV . . . . . . . . . . . . . . . . . 44 136 5.11. Multicast-Flow TLV . . . . . . . . . . . . . . . . . . . 45 137 5.12. Report-Buffering-Time TLV . . . . . . . . . . . . . . . . 46 138 5.13. Committed-Bandwidth TLV . . . . . . . . . . . . . . . . . 47 139 6. Multicast Capabilities . . . . . . . . . . . . . . . . . . . 47 140 6.1. Required Protocol Support . . . . . . . . . . . . . . . . 48 141 6.1.1. Protocol Requirements For NAS-Initiated Replication . 48 142 6.1.2. Protocol Requirements For Committed Multicast 143 Bandwidth Reporting . . . . . . . . . . . . . . . . . 49 145 6.1.3. Protocol Requirements For Conditional Access With 146 White and Black Lists . . . . . . . . . . . . . . . . 50 147 6.1.4. Protocol Requirements For Conditional Access With 148 Grey Lists . . . . . . . . . . . . . . . . . . . . . 50 149 6.1.5. Protocol Requirements For Delegated Bandwidth . . . . 52 150 6.2. Capability-Specific Procedures for Providing Multicast 151 Service . . . . . . . . . . . . . . . . . . . . . . . . . 52 152 6.2.1. Procedures For NAS-Initiated Replication . . . . . . 52 153 6.2.2. Procedures For Committed Bandwidth Reporting . . . . 53 154 6.2.3. Procedures For Conditional Access With Black and 155 White Lists . . . . . . . . . . . . . . . . . . . . . 54 156 6.2.4. Procedures For Conditional Access With Grey Lists . . 56 157 6.2.5. Procedures For Delegated Bandwidth . . . . . . . . . 57 158 6.3. Combinations of Multicast Capabilities . . . . . . . . . 58 159 6.3.1. Combination of Conditional Access With White and 160 Black Lists and Conditional Access With Grey Lists . 58 161 6.3.2. Combination of Conditional Access With Delegated 162 Bandwidth . . . . . . . . . . . . . . . . . . . . . . 60 163 6.3.3. Combination of NAS-Initiated Replication with Other 164 Capabilities . . . . . . . . . . . . . . . . . . . . 60 165 6.3.4. Combinations of Committed Bandwidth Reporting with 166 Other Multicast Capabilities . . . . . . . . . . . . 61 167 7. Security Considerations . . . . . . . . . . . . . . . . . . . 61 168 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61 169 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 64 170 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 64 171 10.1. Normative References . . . . . . . . . . . . . . . . . . 64 172 10.2. Informative References . . . . . . . . . . . . . . . . . 64 173 Appendix A. Example of Messages and Message Flows . . . . . . . 65 174 A.1. Provisioning Phase . . . . . . . . . . . . . . . . . . . 66 175 A.2. Handling a Grey-Listed Flow . . . . . . . . . . . . . . . 70 176 A.3. Handling White-Listed Flows . . . . . . . . . . . . . . . 75 177 A.4. Handling Of Black-Listed Join Requests . . . . . . . . . 79 178 A.5. Handling Of Requests To Join and Leave the On-Line Game . 80 179 A.6. Example Flow For Multicast Flow Reporting . . . . . . . . 82 180 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 85 182 1. Introduction 184 [RFC5851] defines a framework and requirements for an Access Node 185 control mechanism between a Network Access Server (NAS) and an Access 186 Node (e.g. a Digital Subscriber Line Access Multiplexer (DSLAM)) in a 187 multi-service reference architecture in order to perform QoS-related, 188 service-related and subscriber-related operations. [RFC6320] 189 specifies a protocol for Access Node Control in broadband networks in 190 line with this framework. 192 [RFC6320] supports three use cases defined in [RFC5851], specifically 193 for DSL access: the DSL Topology Discovery use case, the DSL Line 194 Configuration use case and the DSL Remote Connectivity Test use case. 195 However, it does not support the multicast use cases defined in 196 [RFC5851]. The present document specifies the extensions to the 197 Access Node Control Protocol required for support of these multicast 198 use cases. In addition, it supports the Committed Bandwidth 199 Reporting use case, described below. In terms of the ANCP protocol, 200 these use cases are organized into five capabilities: 202 o NAS-initiated multicast replication; 204 o conditional access with white and black lists; 206 o conditional access with grey lists; 208 o bandwidth delegation; 210 o committed bandwidth reporting. 212 NAS-initiated multicast replication assumes that multicast "join" and 213 "leave" requests are terminated on the NAS, or that the NAS receives 214 requests to establish multicast sessions through other means (e.g., 215 application-level signalling). The NAS sends commands to the AN to 216 start or stop replication of specific multicast flows on specific 217 subscriber ports. This use case is described briefly in the next-to- 218 last paragraph of Section 3.4 of [RFC5851]. 220 Conditional access is described in Sections 3.4.1 and 3.4.2.3 of 221 [RFC5851], with the latter section particularly applicable to 222 operation with white and black lists only. In case of "conditional 223 access with white and black lists", multicast join and leave requests 224 are terminated at the AN and accepted or ignored in accordance with 225 the direction provided by white and black lists respectively. The 226 white and black lists are provisioned per port at startup time and 227 may be modified thereafter. The NAS may enable admission control of 228 white-listed flows by appropriate provisioning. 230 Conditional access with grey lists is similar to conditional access 231 with white lists, except that before accepting any request matching a 232 grey list entry, the AN sends a request to the NAS for permission to 233 replicate the flow. Again, the NAS can enable admission control of 234 grey-listed flows at the AN. 236 Bandwidth delegation is described in Section 3.4.2.1 of [RFC5851]. 237 It allows flexible sharing of total video bandwidth on an access line 238 between the AN and the NAS. One application of such bandwidth 239 sharing is where the AN does multicast admission control, while the 240 NAS or Policy Server does unicast admission control. In that case, 241 bandwidth delegation allows dynamic sharing of bandwidth between 242 unicast and multicast video traffic on each access line. 244 Committed bandwidth reporting is described below, in Section 3.4. 245 The AN reports the amount of multicast bandwidth it has granted to a 246 given access line each time that value changes. These reports may be 247 buffered for a NAS-provisionable interval so that reports for 248 multiple access lines can be bundled into the same message. 250 The formal specification of the behaviours associated with each of 251 these capabilities, singly and in combination, is given in Section 6. 253 In addition to the multicast service processing behaviour just 254 sketched, the definition of each capability includes support for the 255 multicast accounting and reporting services described in 256 Section 3.4.3 of [RFC5851]. Because of this common content and 257 because of other protocol overlaps between the different 258 capabilities, the protocol descriptions for the multicast extensions 259 specified in this document are merged into a single non-redundant 260 narrative. Tables in Section 6 then indicate the specific sub- 261 sections of the protocol description that have to be implemented to 262 support each capability. 264 2. Terminology 266 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 267 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 268 document are to be interpreted as described in [RFC2119]. 270 The expression "delegated bandwidth" is used as a shorter way of 271 saying: "the total amount of video bandwidth delegated to the AN for 272 multicast admission control". 274 3. Multicast Use Cases 276 Quoting from [RFC5851]: 278 "... the Access Node, aggregation node(s) and the NAS must all be 279 involved in the multicast replication process. This avoids that 280 several copies of the same stream are sent within the access/ 281 aggregation network. In case of an Ethernet-based access/aggregation 282 network, this may, for example, be achieved by means of IGMP snooping 283 or IGMP proxy in the Access Node and aggregation node(s). By 284 introducing IGMP processing in the access/aggregation nodes, the 285 multicast replication process is now divided between the NAS, the 286 aggregation node(s) and Access Nodes. In order to ensure backward 287 compatibility with the ATM-based model, the NAS, aggregation node and 288 Access Node need to behave as a single logical device. This logical 289 device must have exactly the same functionality as the NAS in the ATM 290 access/aggregation network. The Access Node Control Mechanism can be 291 used to make sure that this logical/functional equivalence is 292 achieved by exchanging the necessary information between the Access 293 Node and the NAS." 295 [RFC5851] describes the use cases for ANCP associated with such 296 multicast operations, and identifies the associated ANCP 297 requirements. The present section describes a subset of these use 298 cases as background to facilitate reading of this document, but the 299 reader is refered to [RFC5851] for a more exhaustive description of 300 the ANCP multicast use cases. Detailed example message flows can 301 also be found in Appendix A. 303 3.1. NAS Initiated Multicast Replication Control Use Case 305 3.1.1. Goals 307 One option for multicast handling is for the subscriber to 308 communicate the "join/leave" information to the NAS. This can be 309 done for instance by terminating all subscriber IGMP ([RFC3376]) or 310 MLD ([RFC2710], [RFC3810]) signaling on the NAS. Another example 311 could be a subscriber using some form of application level signaling, 312 which is redirected to the NAS. In any case, this option is 313 transparent to the access and aggregation network. In this scenario, 314 the NAS uses ANCP to create and remove replication state in the AN 315 for efficient multicast replication. Thus, the NAS only sends a 316 single copy of the multicast stream towards the AN, which in turn 317 performs replication to multiple subscribers as instructed by the NAS 318 via ANCP. The NAS first performs conditional access and multicast 319 admission control when processing multicast join requests, and only 320 creates replication state in the AN if admission succeeds. 322 3.1.2. Message Flow 324 With the NAS-initiated use case, a Multicast Replication Control 325 Message is sent by the NAS to the AN with a directive to either join 326 or leave one (or more) multicast flow(s). In the example message 327 flow, the AN uses a Generic Response message to convey the outcome of 328 the directive. Figure 1 illustrates such an ANCP message exchange as 329 well as the associated AN behavior. 331 +----------+ +-------+ +-----+ ANCP +-----+ 332 |Subscriber| | Home | | AN |<-------------------->| NAS | 333 +----------+ |Gateway| +-----+ +-----+ 334 | +-------+ | | 335 | | | (*) 336 | | | Multicast-Replication-Crl | 337 | | | (Target,add, Flow 1) | 338 | | |<--------------------------| 339 | Mcast Flow 1 | | 340 |<==========================+ | 341 | | | Generic Response | 342 | | |-------------------------->| 343 | | | | 344 | | | | 345 ~ ~ ~ ~ 346 | | | | 347 | | | Multicast-Replication-Crl | 348 | | | (Target,delete, Flow 1) | 349 | | |<--------------------------| 350 | | | | 351 | | Generic Response | 353 | | |-------------------------->| 355 (*) The NAS may optionally seek direction from an external 356 Authorization/Policy Server before admitting the flow. 358 Figure 1: NAS Initiated Multicast Replication Control 360 3.2. Conditional Access and Admission Control Use Case 362 3.2.1. Goals 364 One option for multicast handling is for the access/aggregation nodes 365 to participate in IGMP/MLD processing (e.g. via IGMP/MLD snooping). 366 In this scenario, on detecting a join/leave request from an end user 367 for a multicast flow (in the grey list), the AN uses ANCP to request 368 a conditional access and admission control decision from the NAS. In 369 turn, after conditional access and admission control checks, the NAS 370 uses ANCP to instruct the AN to change the replication states 371 accordingly. 373 3.2.2. Message Flow 375 For support of the conditional access and admission control use case, 376 on detection of an IGMP/MLD Join, the AN sends an Admission Control 377 message to the NAS to request a conditional access and admission 378 control check. In the case of a positive outcome, the NAS sends a 379 Multicast Replication Control Message to the AN with a directive to 380 replicate the multicast flow to the corresponding user. Similarly on 381 detection of an IGMP/MLD leave, an Admission Control message is sent 382 by the AN to the NAS to keep the NAS aware of user departure for the 383 flow. This message flow is illustrated in Figure 2. 385 +----------+ +-------+ +-----+ ANCP +-----+ 386 |Subscriber| | Home | | AN |<------------------->| NAS | 387 +----------+ |Gateway| +-----+ +-----+ 388 | +-------+ | | 389 | | | | 390 | Join(Gr-Flow1) | Admission-Control | 391 |------------+---------->| (Target,add,Gr-Flow1) | 392 | | |-------------------------->| 393 | | | (*) 394 | | | Multicast-Replication-Crl | 395 | | | (Target,add,Gr-Flow1) | 396 | | |<--------------------------| 397 | Mcast Gr-Flow1 | | 398 |<=======================+ | 399 | | | | 400 ~ ~ ~ ~ 401 | | | | 402 | Leave(Gr-Flow1) | Admission-Control | 403 |------------+---------->| (Target,delete,Gr-Flow1) | 404 | | |-------------------------->| 405 | | | 407 | | | | 409 Gr-Flow1: a multicast flow matching the grey list for that port 411 (*) The NAS may optionally seek direction from an external 412 Authorization/Policy Server before admitting the flow. 414 Figure 2: Multicast Conditional Access and Admission Control 416 3.3. Multicast Flow Reporting Use Case 418 3.3.1. Goals 420 The Multicast flow reporting use case allows the NAS to 421 asynchronously query the AN to obtain an instantaneous status report 422 related to multicast flows currently replicated by the AN. 424 3.3.2. Message Flow 426 The NAS sends a Multicast Flow Query Request message to the AN in 427 order to query the AN about information such as which multicast flows 428 are currently active on a given AN port or which ports are currently 429 replicating a given multicast flow. The AN conveys the requested 430 information to the NAS in a Multicast Flow Query Response message. 431 This message flow is illustrated in Figure 3. 433 +----------+ +-------+ +-----+ ANCP +-----+ 434 |Subscriber| | Home | | AN |<---------->| NAS | 435 +----------+ |Gateway| +-----+ +-----+ 436 | +-------+ | | 437 | | | Multicast Flow | 438 | | | Query Request | 439 | | |<------------------| 440 | | | | 441 | | | Multicast Flow | 442 | | | Query Response | 443 | | |------------------>| 444 | | | | 445 | | | | 447 Figure 3: Multicast Flow Reporting 449 3.4. Committed Bandwidth Reporting Use Case 451 3.4.1. Goals 453 The committed bandwidth reporting use case allows the NAS to maintain 454 current awareness of how much multicast bandwidth the AN has 455 committed to a given access line, so that the NAS can adjust its 456 forwarding scheduler to ensure the associated QoS. Note that this 457 involves a finer level of detail than provided by bandwidth 458 delegation, since the amount of delegated bandwidth is an upper limit 459 on the amount of bandwidth committed rather than an actual value. To 460 reduce the volume of messaging, reports from the AN may be buffered 461 so that one message reports on changes for multiple access lines. 463 3.4.2. Message Flow 465 The message flow associated with this use case is shown in Figure 4. 466 The figure assumes that a non-zero buffering interval was previously 467 provisioned on the AN. 469 +-----+ +-------+ +-----+ ANCP +-----+ 470 |Subs |+ | Home |+ | AN |<---------->| NAS | 471 |1,2 || |GW 1,2 || +-----+ +-----+ 472 +-----+| +-------+| | | 473 +|----+ +|------+ | | 474 | | | | | | 475 | |Join(Subs1, Ch1) | | 476 |----------+--------------->| Start buffering | 477 | | | Multicast flow | timer. Create | 478 |<==========================| message with | 479 | | | | | initial contents | 480 | | | | | reporting new | 481 | | | | | Subs1 bandwidth. | 482 | | Join(Subs2, Ch2) | | 483 | |----------+------------->| Add report for | 484 | | | Multicast flow | new Subs2 b/w. | 485 | |<========================| | 486 | | | | | | 487 | |Leave(Subs1, Ch1) | | 488 |----------+--------------->| Replace report | 489 | | | | | for Subs1 with | 490 | | Stop replication X new value (which | 491 | | | | | happens to be | 492 | | | | | the same as the | 493 | | | | | starting value. | 494 | | | | | | 495 | | | | >|< TIMER expires | 496 | | | | | | 497 | | | | |Committed | 498 | | | | | Bandwidth Report | 499 | | | | |------------------>| 500 | | | | | (for latest | 501 | | | | | Subs1 and Subs2 | 502 | | | | | bandwidth) | 503 | | | | | | 505 Figure 4: Message Flow For Committed Bandwidth Reporting 507 4. ANCP Messages 509 This section defines new ANCP messages and new usage of existing ANCP 510 messages as well as procedures associated with the use of these 511 messages. 513 4.1. Provisioning Message 515 Section 4.1 of [RFC6320] defines the Provisioning message that is 516 sent by the NAS to the AN to provision information in the AN. 518 The present document specifies that the Provisioning message MAY be 519 used by the NAS to provision multicast-related information (e.g., 520 multicast service profiles). The ANCP Provisioning message payload 521 MAY contain: 523 o one or more instances of the Multicast-Service-Profile TLV. The 524 Multicast-Service-Profile TLV is defined in the present document 525 in Section 5.1. Each instance of the Multicast-Service-Profile 526 TLV contains a multicast service profile name and one or more list 527 actions. A list action consists of an action (add, delete, 528 replace), a list type (white, black, or grey), and list content 529 (multicast source and group addresses). 531 o an instance of the White-List-CAC TLV. The White-List-CAC TLV is 532 defined in Section 5.6. If present, this TLV indicates that the 533 AN is required to do admission control before replicating white- 534 listed flows. 536 o an instance of the MRepCtl-CAC TLV. The MRepCtl-CAC TLV is 537 defined in Section 5.7. If present, this TLV indicates that the 538 AN is required to do admission control before replicating flows 539 specified in Multicast Replication Control messages. 541 o an instance of the Report-Buffering-Time TLV. The Report- 542 Buffering-Time TLV is defined in Section 5.12. If present, this 543 TLV indicates Committed Bandwidth Report messages should be 544 buffered for the amount of time given by the TLV before being 545 transmitted to the NAS. 547 See Section 6 for information on which multicast capabilities require 548 support of these TLVs in the Provisioning message. 550 4.1.1. Sender Behaviour 552 When directed by the Policy Server or by management action, the NAS 553 sends the Provisioning message to initially provision or to update 554 the white, black, and/or grey multicast channel lists associated with 555 a set of named multicast service profiles, or to enable the AN to 556 perform admission control for specific classes of flows. 558 To provision or update a multicast service profile, the NAS MUST 559 include within the message one or more instances of the Multicast- 560 Service-Profile TLV specifying the content to be provisioned or 561 updated. The NAS SHOULD NOT include any list type (white, black, or 562 grey) that is not supported by the set of multicast capabilities 563 negotiated between the NAS and the AN. The NAS MUST NOT use the 564 Provisioning message to send instances of the Multicast-Service- 565 Profile TLV to the AN unless the Multicast-Service-Profile TLV is 566 supported by the set of multicast capabilities negotiated between the 567 NAS and the AN. 569 To require admission control to be performed at the AN on white- 570 listed flows, the NAS MUST include a copy of the White-List-CAC TLV 571 in the Provisioning message. The White-List-CAC TLV MUST NOT be 572 provided unless the negotiated set of capabilities includes 573 conditional access with white and black lists. 575 To require admission control to be performed at the AN on grey-listed 576 flows or on NAS-initiated flows, the NAS MUST include a copy of the 577 MRepCtl-CAC TLV in the Provisioning message. The MRepCtl-CAC TLV 578 MUST NOT be provided unless the negotiated set of capabilities 579 includes NAS-initiated replication control or conditional access with 580 grey lists. 582 To require buffering of Committed Bandwidth Report messages so that 583 reports for multiple access lines can be included in the same 584 message, the NAS MUST include a copy of the Report-Buffering-Time TLV 585 containing a non-zero time value in a Provisioning message sent to 586 the AN. The Report-Buffering-Time TLV MUST NOT be provided unless 587 the negotiated set of capabilities includes committed bandwidth 588 reporting. 590 4.1.2. Receiver Behaviour 592 The receiving AN provisions/updates the white, black, and/or grey 593 lists associated with the multicast service profile names contained 594 in the Multicast-Service-Profile TLV instances within the message 595 according to the contents of the associated List-Action TLVs. The AN 596 MUST process List-Action TLVs in the order in which they appear 597 within the message. The AN MUST ignore instances of the List-Action 598 TLV referring to any list type (white, black, or grey) that is not 599 supported by the set of multicast capabilities negotiated between the 600 NAS and the AN. 602 When a new multicast service profile is identified by a Multicast- 603 Service-Profile TLV, the initial state of all lists associated with 604 that profile according to the negotiated set of multicast 605 capabilities is empty until changed by the contents of Multicast- 606 Service-Profile TLVs. 608 The receipt of a Provisioning message containing updates to an 609 existing multicast service profile subsequent to startup will cause 610 the AN to review the status of active flows on all ports to which 611 that profile has been assigned. For further details, see Section 6. 613 If the White-List-CAC and/or MRepCtl-CAC TLV is present in the 614 Provisioning message and the respective associated capabilities have 615 been negotiated, the AN prepares (or continues) to do connection 616 admission control on the indicated class(es) of flow. If one or both 617 of these TLVs was present in an earlier Provisioning message but is 618 absent in the latest message received, the AN ceases to do connection 619 admission control on the indicated class(es) of flow. 621 The buffering time specified in an instance of the Report-Buffering- 622 Time TLV applies to only to Committed Bandwidth Report messages 623 initiated after the new buffering time is received at the AN, not to 624 any message already in the process of accumulation. 626 As indicated in [RFC6320], the AN MUST NOT reply to the Provisioning 627 message if it processed it successfully. If an error prevents 628 successful processing of the message content, the AN MUST return a 629 Generic Response message as defined in [RFC6320], containing a 630 Status-Info TLV with the appropriate content describing the error. 631 For this purpose, the presence of a list type in a Multicast-Service- 632 Profile TLV which was ignored because it was not supported by the 633 negotiated set of capabilities is not considered to be an error. 635 4.2. Port Management Message 637 As specified in [RFC6320], the NAS may send DSL line configuration 638 information to the AN ("ANCP based DSL Line Configuration" use case) 639 using ANCP Port Management messages. See Section 7.3 of [RFC6320] 640 for the format of the Port Management message in that usage. 642 This document specifies that the Port Management message MAY be used 643 to convey either or both of the following TLVs: 645 o Multicast-Service-Profile-Name TLV (defined in Section 5.2). This 646 TLV associates a Multicast Service Profile with the Access Port 647 specified by the extension block. 649 o Bandwidth-Allocation TLV (defined in Section 5.5). This TLV 650 specifies the total multicast bandwidth available to the AN for 651 admission control at the Access Port. 653 When the Port Management message is used for this purpose: 655 o the Function field in the Port Management message MUST be set to 656 8, "Configure Connection Service Data". 658 o the message MUST include TLV(s) to identify the access line 659 concerned. If the access line is a DSL loop, the line-identifying 660 TLV(s) MUST be as specified in Section 5.1.2 of [RFC6320]. For 661 non-DSL access lines, the appropriate alternative line-identifying 662 TLV(s) MUST be present. Line configuration data other than the 663 two TLVs listed in the previous paragraph MAY be present. 665 4.2.1. Sender Behaviour 667 The NAS sends the Port Management message at startup time to 668 initialize parameters associated with the Access Port specified in 669 the message and with the multicast capabilities negotiated between 670 the NAS and the AN. The NAS MAY send additional Port Management 671 messages subsequent to startup, to update or, in the case of the 672 Bandwidth-Allocation TLV, reset these parameters. If the NAS 673 includes a Multicast-Service-Profile-Name TLV in the Port Management 674 message, the name MUST match a profile name provided in a Multicast- 675 Service-Profile TLV in a prior Provisioning message. The NAS MUST 676 NOT include a TLV unless it is supported by the set of multicast 677 capabilities negotiated between the NAS and the AN. See Section 6 678 for further information. 680 4.2.2. Receiver Behaviour 682 If the Port Management message contains a Multicast-Service-Profile- 683 Name TLV, the AN associates the named profile with the specified 684 Access Port. This association replaces any previous association. 685 That is, a given Access Port is associated with at most one multicast 686 service profile. The replacement of one multicast service profile 687 with another will cause the AN to review the status of all active 688 flows on the target port. For further details see Section 6. 690 If the Port Management message contains a Bandwidth-Allocation TLV, 691 the AN adopts this as the current value of its total multicast 692 bandwidth limit for the target port. If the AN has already committed 693 multicast bandwidth exceeding the amount given in the Bandwidth- 694 Allocation TLV, the AN SHOULD NOT discontinue any multicast streams 695 in order to bring bandwidth down to within the new limit. However, 696 the AN MUST NOT admit new multicast streams that are subject to 697 admission control until it can do so within the limit specified by 698 the Bandwidth-Allocation TLV. 700 If the Port Management request cannot be processed due to error and 701 the Result field of the request is Nack (0x1) or AckAll (0x2), the AN 702 SHOULD add a Status-Info TLV to the Extension Value field in its 703 reply if this will provide useful information beyond what is provided 704 by the Result Code value returned in the response header. In 705 particular, if the name within the Multicast-Service-Profile-Name TLV 706 does not match a profile name given in a prior Provisioning message, 707 the AN SHOULD return a reply where the Result Code field in the 708 header indicates 0x55, "Invalid TLV contents", the Error Message 709 field in the Status-Info TLV contains the text "Multicast profile 710 name not provisioned", and the Status-Info TLV contains a copy of the 711 Multicast-Service-Profile-Name TLV. 713 4.3. Multicast Replication Control Message 715 This section defines a new message called the Multicast Replication 716 Control message. The Multicast Replication Control message is sent 717 by the NAS to the AN with one or more directives to add (join) or 718 delete (leave) a multicast flow on a target object identified in the 719 content of the message. 721 The Message Type for the Multicast Replication Control message is 722 144. 724 The ANCP Multicast Replication Control message payload contains the 725 following TLVs: 727 o Target TLV: The Target TLV is defined in Section 4.3 of [RFC6320]. 728 It MUST appear once and only once. It is encoded as specified in 729 [RFC6320] or extensions and identifies the AN port subject to the 730 request for admission or release. 732 o Command TLV: The Command TLV is defined in Section 4.4 of 733 [RFC6320]. It MUST be present. It MAY appear multiple times. 735 As [RFC6320] indicates, the contents of the Command Info field within 736 the Command TLV are specific to the message in which the TLV occurs. 737 For the Multicast Replication Control Message, these contents consist 738 of: 740 o a Command Code field; 742 o an Accounting field; 744 o an instance of the Multicast-Flow TLV. 746 Figure 5 illustrates the complete Command TLV with the contents 747 specific to the Multicast Replication Control message. 749 1 2 3 750 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 751 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 752 | TLV Type = Command | Command-TLV Length | 753 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 754 |Command Code | Accounting | Reserved | 755 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 756 | Multicast-Flow TLV | 757 | ... | 758 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 759 | Other embedded TLV Type | Other embedded TLV Length | 760 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 761 | | 762 ~ Other embedded TLV data ~ 763 | | 764 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 766 Figure 5: Contents of the Command TLV in the Multicast Replication 767 Control Message 769 Command Code: 770 Command directive: 772 1 - Add; 774 2 - Delete; 776 3 - Delete All; 778 4 - Admission Control Reject; 780 5 - Conditional Access Reject; 782 6 - Admission Control and Conditional Access Reject. 784 Directives 4 through 6 are used as described in 785 Section 4.4.2. 787 Accounting: 788 Meaningful only when the Command Code is "Add" (1). In 789 that case, 0x00 indicates no flow accounting, 0x01 790 indicates that octet accounting for the flow is to 791 commence. The Accounting field MUST be set to 0x00 for 792 other Command Code values. 794 Reserved: 795 Reserved for future use. MUST be set to 0x0000 by the 796 sender and ignored by the receiver. 798 Multicast-Flow TLV: 799 An instance of the Multicast-Flow TLV (Section 5.11) 800 specifying the flow to be added or deleted. The Multicast- 801 Flow TLV MUST be omitted if the Command Code has value 802 "Delete All" (3). 804 Other embedded TLV: 806 No other embedded TLVs are currently specified within the 807 Multicast Replication Control message/Command TLV. 808 However, see the description of the Multicast Admission 809 Control message (Section 4.4). Unrecognized embedded TLVs 810 SHOULD be silently discarded. 812 The figure below is an example of a Multicast Replication Control 813 message that would result in a swap from multicast Source-Specific 814 Multicast (SSM) flows 2001:DB8::1, FF34::2, to 2001:DB8::2, FF34::3 815 on the Target identified by the "Access Loop Circuit ID": 817 1 2 3 818 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 819 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 820 | Type (0x880C) | Length | 821 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 822 | Version | MsgType=144 | 0x02 | Result Code | 823 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 824 | Partition ID | Transaction Identifier = 0001 | 825 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 826 |I| SubMessage Number | Length | 827 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 828 | Type = Target 0x1000 | Target TLV Length | 829 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 830 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | 831 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 832 | | 833 ~ Access Loop Circuit ID ~ 834 | | 835 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 836 | Type = Command TLV | Command-TLV Length = 0x0014 | 837 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 838 | Cmd Code=2 |Acctg = 0x00 | Reserved = 0x0000 | 839 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 840 |TLV Type = Multicast-Flow | TLV Length = 0x000C | 841 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 842 |Flow Type=0x02 |AddrFam = 0x02 | Reserved = 0x0000 | 843 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 844 | | 845 ~ Multicast Group Address ~ 846 | = FF34::2 | 847 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 848 | | 849 ~ Source Address ~ 850 | = 2001:DB8::1 | 851 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 852 | Type = Command-TLV | Command-TLV Length = 0x0014 | 853 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 854 | Cmd Code=1 |Acctg = 0x01 | Reserved = 0x0000 | 855 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 856 |TLV Type = Multicast-Flow | TLV Length = 0x000C | 857 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 858 |Flow Type=0x02 |AddrFam = 0x02 | Reserved = 0x0000 | 859 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 860 | Multicast Group Address = FF34::3 | 861 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 862 | Source Address = 2001:DB8::2 | 863 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 864 | | 865 ~ Multicast Group Address ~ 866 | = FF34::3 | 867 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 868 | | 869 ~ Source Address ~ 870 | = 2001:DB8::2 | 871 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 873 4.3.1. Sender Behaviour 875 The NAS MAY issue a Multicast Replication Control message to the AN 876 to convey one or more directives to add (join) or delete (leave) one 877 or more multicast flows. 879 The NAS MAY send this message on its own initiative to support the 880 NAS initiated Multicast Control use case presented in [RFC5851] and 881 summarized in Section 3.1. In that case, the NAS MUST set the Result 882 field to AckAll (0x2) or Nack (0x1) according to its requirements. 884 The NAS MAY also send this message in response to a Multicast 885 Admission Control message (defined in Section 4.4) received from the 886 AN to support the conditional access and admission control use case 887 presented in [RFC5851] and summarized in Section 3.2. In that case, 888 the NAS MUST set the Result field to NAck (0x1). 890 In either case, the sender MUST populate the Result Code field with 891 the value 0x000 and the ANCP Transaction Identifier field with a 892 unique value, as described in Section 3.6.1.6 of [RFC6320]. 894 Each Multicast Replication Control Message MUST contain one or more 895 commands, each encapsulated in its own Command TLV. The sender MUST 896 use a separate Command TLV for each distinct multicast flow. 898 When the order of processing of two commands does not matter, the 899 commands MUST be transmitted in separate Multicast Replication 900 Control messages. 902 4.3.2. Receiver Behaviour 904 When successive commands (in the same or different messages) relate 905 to the same Target and multicast flow, the state of each feature 906 controlled or affected by attributes received in the Multicast 907 Replication Control message, SHALL be as set by the last command or 908 message referring to that target and flow and containing the 909 controlling attribute. As an example, successive Multicast 910 Replication Control messages containing add commands for a given port 911 and flow, but differing only in the Accounting field setting SHALL be 912 interpreted to mean that the state of the accounting feature is as 913 set in the final command received, but all other features are as set 914 in the initial message. 916 If more than one Command TLV is present in a Multicast Replication 917 Control message, the AN MUST act on the commands in the order in 918 which they are presented in the message. The AN SHALL assign a 919 sequence number to each command in a given Multicast Replication 920 Control message, starting from 0x01 for the first command. 922 If a Command TLV adds a flow and the AN is performing admission 923 control for Multicast Replication Control messages, then the AN MUST 924 perform admission control before replicating the flow. If the 925 admission control check fails, the AN MUST treat the failure as an 926 error as described below. The appropriate Result Code value for the 927 response is 0x013 "Out of resources". 929 If the AN processes the complete Multicast Replication Control 930 message successfully and the Result field of the Multicast 931 Replication Control message was set to AckAll (0x2), the AN MUST 932 respond with a Generic Response message where the Result field is set 933 to Success (0x3), the Result Code field is set to 0x000, and the 934 Transaction Identifier field is copied from the Multicast Replication 935 Control message. The body of the response MAY be empty or MAY be 936 copied from the Multicast Replication Control message. 938 If the AN processes the complete Multicast Replication Control 939 message successfully and the Result field of the Multicast 940 Replication Control message was set to Nack (0x1), the AN MUST NOT 941 respond to the message. 943 The processing/execution of multiple commands contained in a single 944 Multicast Control message MUST be interrupted at the first error 945 encountered, and the remaining commands in the Multicast Replication 946 Control message discarded. 948 If the AN detects an error in a received Multicast Replication 949 Control message and the Result field in that message was set to Nack 950 (0x1) or AckAll(0x2), the AN MUST generate a Generic Response message 951 providing error information to the NAS. This specification 952 identifies the following new Result Code values beyond those 953 specified in [RFC6320], which MAY be used in a Generic Response sent 954 in reply to a Multicast Replication Control message: 956 0x64 Command error. 958 Where detected: ANCP agent at the AN. 960 Further description: an invalid command code has been received. 962 Required additional information in the message: see below. 964 Target: ANCP agent at the NAS. 966 Action RECOMMENDED for the receiving ANCP agent: Correct the 967 error and re-send the request, if possible. Otherwise, report 968 the error to the control application with an indication of the 969 erroneous information associated with the invalid TLV(s). 971 0x65 Invalid flow address. 973 Where detected: ANCP agent at the AN. 975 Further description: either inconsistent flow address 976 information has been provided or the address family is 977 unsupported. 979 Required additional information in the message: see below. 981 Target: ANCP agent at the NAS. 983 Action RECOMMENDED for the receiving ANCP agent: correct the 984 error and re-send the request, if possible. Otherwise, report 985 the error to the control application with an indication of the 986 erroneous information associated with the invalid TLV(s). 988 0x66 Multicast flow does not exist. 990 Where detected: control application at the AN. 992 Further description: the NAS has attempted to delete a flow 993 that is not active on the given access line. 995 Required additional information in the message: see below. 997 Target: control application at the NAS. 999 Action RECOMMENDED for the receiving ANCP agent: report the 1000 error to the control application with an indication of the 1001 erroneous information associated with the invalid TLV(s). 1003 A Generic Response message responding to the Multicast Replication 1004 Control message and containing one of the above Result Code values 1005 MUST include a Status-Info TLV which includes one or two embedded 1006 TLVs as follows: 1008 o a Sequence-Number TLV as described in Section 5.4, giving the 1009 sequence number of the failed command, MUST be included; 1011 o the failed Command TLV itself SHOULD be included. 1013 Note that the Error Message field of the Status-Info TLV MAY be 1014 used to report more details than implied by the Result Code value 1015 in the message header. For example, the Result Code value could 1016 be 0x65 and the Error Message field could contain the text: 1017 "Source address present for ASM flow". 1019 4.4. Multicast Admission Control Message 1021 This section defines a new message called the Multicast Admission 1022 Control message. The Multicast Admission Control message is sent by 1023 the AN to the NAS to request admission of a multicast flow, or to 1024 notify of the removal of a multicast flow, for a given target. 1026 The Message Type for the Multicast Admission Control message is 145. 1028 The ANCP Multicast Admission Control message payload contains two 1029 TLVs: 1031 o Target TLV: The Target TLV is defined in [RFC6320]. It MUST 1032 appear once and only once in the Multicast Admission Control 1033 message. It is encoded as specified in [RFC6320] or extensions 1034 and identifies the AN port subject to the request for admission or 1035 release. 1037 o Command TLV: The Command TLV is defined in [RFC6320]. It MUST be 1038 present. If it appears more than once, only the first instance is 1039 considered meaningful in the present version of this specification 1040 and the other instances are ignored. 1042 Note: 1044 In the future, the specification of the Admission Control message 1045 may be extended to allow transport of more than a single directive 1046 (e.g., to carry both a leave from one group and a join to another 1047 group for the same Target). It is expected that this would 1048 support a similar notion of strict sequenced processing as 1049 currently defined for handling multiple directives in the 1050 Multicast Replication Control message whereby all directives 1051 following the first directive that can not be executed are not 1052 executed either. When the strict sequenced processing of the 1053 directives is not required the directives are distributed across 1054 separate messages. 1056 The Command TLV has the same contents as were described above for the 1057 Multicast Replication Control message, with the following additions: 1059 o a Request-Source-IP TLV MAY be appended to the Command TLV as an 1060 additional embedded TLV; 1062 o similarly, a Request-Source-MAC TLV MAY be appended to the Command 1063 TLV as an additional embedded TLV. 1065 Note that the Command TLV length includes the length of any embedded 1066 TLVs, including the embedded TLV headers. 1068 4.4.1. Sender Behaviour 1070 The AN sending the Multicast Admission Control message MUST set the 1071 Result field to Ignore (0x0). 1073 The AN MUST populate the ANCP Transaction Identifier field with a 1074 unique value, as described in Section 3.6.1.6 of [RFC6320]. 1076 The AN MUST encode the Command TLV as specified in Section 4.3 with 1077 the following additional rules: 1079 o the Accounting field MUST be set to 0; 1081 o the Command Code field MUST be set to "1 - Add" when the message 1082 conveys a Join , to "2 - Delete" when the message conveys a Leave 1083 and to "3 - Delete All" when the message conveys a Leave of all 1084 channels (on the target); 1086 o The Multicast-Flow TLV within the Command TLV identifies the 1087 multicast flow subject to the request for admission or release. 1088 When the Command Code is 3, the Multicast-Flow TLV is meaningless 1089 and MUST be omitted. 1091 o the Request-Source-IP embedded TLV MAY be included by the AN to 1092 convey the IP address of the sender of the join/leave message 1093 (e.g., IGMP/MLD Join/Leave) that triggered the AN to include the 1094 corresponding Command TLV in the Admission Control message. If it 1095 appears more than once, only the first instance is considered 1096 meaningful and the other instances are ignored. 1098 o the Request-Source-MAC embedded TLV MAY be included by the AN to 1099 convey the MAC address of the sender of the join/leave message 1100 (e.g., IGMP/MLD Join/Leave) that triggered the AN to include the 1101 corresponding Command TLV in the Admission Control message. If it 1102 appears more than once, only the first instance is considered 1103 meaningful and the other instances are ignored. 1105 4.4.2. Receiver Behaviour 1107 On receipt of an Multicast Admission Control message, the NAS: 1109 o MUST ignore the Result field; 1111 o if the directive in the Multicast Admission Control message is "2 1112 - Delete" or "3 - Delete All" and is processed correctly by the 1113 NAS, the NAS MUST NOT generate any ANCP message in response to the 1114 Multicast Admission Control message; 1116 o if the directive in the Multicast Admission Control message is "1 1117 - Add" and is accepted by the NAS, the NAS MUST generate a 1118 Multicast Replication Control in response to the Multicast 1119 Admission Control message. The Multicast Replication Control 1120 message: 1122 * MUST contain a Result set to Nack (0x1); 1124 * MUST contain a Transaction ID with a unique value, as described 1125 in Section 3.6.1.6 of [RFC6320]; 1127 * MUST contain the directive as accepted by the NAS. The NAS MAY 1128 modify the Accounting field if flow accounting is required. 1130 o if the directive in the Multicast Admission Control message is "1 1131 - Add", is processed correctly but not accepted by the NAS (i.e., 1132 it does not pass the admission control or conditional access 1133 check), the NAS MAY generate a Multicast Replication Control 1134 message in response to the Multicast Admission Control message. 1135 This optional message can be used by the AN to maintain statistics 1136 about admission control rejections. 1138 In the future, the AN may be able to notify the subscriber that 1139 the request was rejected (e.g., using 1140 [I-D.morin-mboned-igmpmld-error-feedback]). 1142 When used in this situation, the Multicast Replication Control 1143 message: 1145 * MUST contain a Result set to 0x0; 1147 * MUST contain a Transaction ID with a unique value, as described 1148 in Section 3.6.1.6 of [RFC6320]; 1150 * MUST contain the directive rejected by the NAS (i.e., Target 1151 TLV and Command TLV) but with a Command Code set to "4 - 1152 Admission Control Reject", "5 - Conditional Access Reject", or 1153 "6 - Admission Control and Conditional Access Reject" as 1154 applicable. 1156 o if the Multicast Admission Control message cannot be processed 1157 correctly by the NAS (e.g. the message is malformed, the multicast 1158 flow does not exist etc.), the NAS MUST generate a Generic 1159 Response message (defined in Section 4.2 of [RFC6320]) with 1160 appropriate content indicating the reason for the failure. 1162 4.5. Bandwidth Reallocation Request Message 1164 The Bandwidth Reallocation Request message is used when the bandwidth 1165 delegation capability is included in the negotiated set. It MAY be 1166 sent either by the NAS or by the AN to request an adjustment in the 1167 amount of delegated bandwidth. It will be sent by the NAS typically 1168 to reduce the multicast bandwidth allocated to the AN in order for 1169 the NAS to satisfy a request to add one or more flows. Conversely, 1170 the AN will send a Bandwidth Reallocation Request to obtain 1171 additional bandwidth to satisfy a request to add a multicast channel. 1172 In each case, the requestor has a minimum requirement for additional 1173 bandwidth, and MAY ask for additional bandwidth beyond this amount 1174 (e.g., to handle anticipated future requests). 1176 The Bandwidth Reallocation Request message contains two TLVs: 1178 o the Target TLV (Section 4.3 of [RFC6320] or an extension), 1179 specifying a single access line; 1181 o the Bandwidth-Request TLV (Section 5.8), specifying the required 1182 and preferred amounts of delegated bandwidth. 1184 The Message Type for the Bandwidth Reallocation Request message is 1185 146. 1187 4.5.1. Sender Behaviour 1188 The Result field in the header of the Bandwidth Reallocation Request 1189 message is not used and the sender MUST set it to Ignore (0x0). 1191 The bandwidth values in the Bandwidth-Request TLV are expressed in 1192 terms of total multicast bandwidth allocated to the AN. 1194 The choice of "total bandwidth" rather than "incremental 1195 bandwidth" was made so that it would be easier for the AN and NAS 1196 to keep their respective views of the current amount of delegated 1197 bandwidth synchronized. 1199 Because the values are totals rather than desired increments/ 1200 decrements, the relationship between the required amount and the 1201 preferred amount will differ depending on whether the Bandwidth 1202 Reallocation Request message is issued by the NAS or the AN. 1204 o If the NAS is making the request, the preferred amount MUST be 1205 less than or equal to the required amount. The required amount 1206 MUST be less than the current amount of delegated bandwidth. 1208 o If the AN is making the request, the preferred amount MUST be 1209 greater than or equal to the required amount. The required amount 1210 MUST be greater than the current amount of delegated bandwidth. 1212 4.5.2. Receiver Behaviour 1214 When the peer receives a valid Bandwidth Reallocation Request 1215 message, it SHOULD determine whether it can satisfy the request from 1216 its existing allocation of unused video bandwidth. If it decides 1217 that it can reallocate bandwidth to the peer, it MAY choose to return 1218 any amount between the required and the preferred amounts indicated 1219 in the Bandwidth Reallocation Request message. 1221 The peer MUST return a Bandwidth Transfer message (Section 4.6) 1222 indicating its decision. If the request is met, the Result field of 1223 the Bandwidth Transfer message MUST be set to Success (0x3), the 1224 Result Code field MUST be set to 0x000, and the Bandwidth-Allocation 1225 TLV (Section 5.5) MUST contain the new value of total multicast 1226 bandwidth. This new value MUST lie between the required and 1227 preferred values, inclusive, from the request message. If the 1228 request is not met, the Result field of the Bandwidth Transfer 1229 message MUST be set to Failure (0x4), the Result Code field MUST be 1230 set to 0x000, and the Bandwidth Allocation TLV MUST contain the value 1231 of the currently allocated amount of delegated bandwidth as the 1232 responder views it. 1234 The following cases indicate that the sender holds a different view 1235 of the amount of delegated bandwidth from the receiver: 1237 o the NAS receives a request where the required amount is less than 1238 its view of the current amount of delegated bandwidth; 1240 o the AN receives a request where the required amount is greater 1241 than its view of the current amount of delegated bandwidth. 1243 If one of these cases occurs, the receiver with one exception MUST 1244 send a Bandwidth Transfer message indicating Success. 1246 o If the NAS received the request, the allocated amount in the NAS's 1247 response MUST be at least equal to NAS's view of the current 1248 amount of delegated bandwidth. 1250 o If the AN received the request, the allocated amount in the AN's 1251 response MUST be no greater than the AN's view of the current 1252 amount of delegated bandwidth. 1254 The exception is when the NAS receives a request while it has a 1255 request of its own outstanding. Handling of that case is described 1256 below. 1258 While the cases just described are an error condition, the success 1259 response achieves a graceful recovery. 1261 To avoid deadlock due to race conditions, the following rules MUST be 1262 applied: 1264 a. If the NAS receives a Bandwidth Reallocation Request message 1265 while it has a Bandwidth Reallocation Request message of its own 1266 outstanding for the same access line, the NAS MUST provide an 1267 immediate failure response to the request from the AN, with a 1268 Result Code value set to 0x68 "Inconsistent views of delegated 1269 bandwidth amount" or 0x69 "Bandwidth request conflict" as 1270 applicable. (See below for more information). 1272 b. If the AN receives a Bandwidth Reallocation Request message while 1273 it has a Bandwidth Reallocation Request message of its own 1274 outstanding for the same access line, the AN MUST release any 1275 bandwidth it has already committed to an outstanding Join request 1276 while it is awaiting a response from the NAS. It MUST decide 1277 upon and send its response to the NAS taking the released 1278 bandwidth into account. 1280 If the receiver is unable to process the Bandwidth Reallocation 1281 Request message due to an error, then the receiver MUST return a 1282 Bandwidth Transfer message where: 1284 o the Result field is set to Failure (0x4), 1285 o the Result Code field is set appropriately to indicate the type of 1286 error that was detected, 1288 o the Bandwidth Allocation TLV contains the value of the current 1289 amount of delegated bandwidth as the responder views it, and 1291 o a Status-Info TLV MAY follow the Bandwidth Allocation TLV giving 1292 further information about the error. 1294 This specification provides three new Result Code values applicable 1295 specifically to the contents of the Bandwidth-Request TLV. These 1296 Result Code values by their nature MUST only be used when the error 1297 is being reported in a Bandwidth Transfer message rather than a 1298 Generic Response message. 1300 0x67 Invalid preferred bandwidth amount. 1302 Where detected: control application at the receiver of the 1303 Bandwidth Reallocation Request message. 1305 Further description: the preferred and required amounts of 1306 bandwidth in the TLV do not have the numerical relationship 1307 described above. 1309 Required additional information in the message: as described 1310 above. 1312 Target: control application at the sender of the Bandwidth 1313 Reallocation Request message. 1315 Action RECOMMENDED for the receiving ANCP agent: report the 1316 error to the control application with the returned value of the 1317 Bandwidth-Allocation TLV. See also Section 4.6.2.2. 1319 0x68 Inconsistent views of delegated bandwidth amount. 1321 Where detected: control application at the NAS. 1323 Further description: the NAS has an outstanding Bandwidth 1324 Reallocation Request, so it is rejecting a similar request from 1325 the AN. In the AN request, the required amount was less than 1326 the NAS's view of the current amount of delegated bandwidth. 1328 Required additional information in the message: as described 1329 above. 1331 Target: control application at the AN. 1333 Action RECOMMENDED for the receiving ANCP agent: report the 1334 error to the AN control application with the returned value of 1335 the Bandwidth-Allocation TLV. See also Section 4.6.2.2. 1337 0x69 Bandwidth request conflict. 1339 Where detected: control application at the NAS. 1341 Further description: the NAS has an outstanding Bandwidth 1342 Reallocation Request, so it is rejecting a similar, valid 1343 request from the AN. 1345 Required additional information in the message: as described 1346 above. 1348 Target: control application at the AN. 1350 Action RECOMMENDED for the receiving ANCP agent: report the 1351 error to the AN control application with the returned value of 1352 the Bandwidth-Allocation TLV. See also Section 4.6.2.2. 1354 4.6. Bandwidth Transfer Message 1356 The Bandwidth Transfer message is used to transfer video bandwidth 1357 from the sender to the peer for a specific access line. This message 1358 MAY be sent either from the AN or from the NAS. As described in the 1359 previous section, it is the required response to a valid Bandwidth 1360 Reallocation Request message. 1362 The Bandwidth Transfer message MAY also be used to transfer bandwidth 1363 autonomously from one peer to another. One example of this usage is 1364 to release bandwidth borrowed earlier by means of the Bandwidth 1365 Reallocation Request message. When the message is used in this way, 1366 the Result field in the Bandwidth Transfer message MUST be set to 1367 Ignore (0x0). 1369 This allows the receiver to distinguish between an autonomous 1370 transfer and a response to a previous Bandwidth Reallocation 1371 Request, for purposes of validation. 1373 The Message Type for the Bandwidth Transfer message is 147. The 1374 Bandwidth Transfer message contains the following TLVs: 1376 o the Target TLV, designating the access line concerned; 1378 o an instance of the Bandwidth-Allocation TLV (Section 5.5). The 1379 bandwidth value in the Bandwidth-Allocation TLV is the new amount 1380 of delegated bandwidth allocated to the target. 1382 4.6.1. Sender Behaviour 1384 When sending a Bandwidth Transfer message where the Result value is 1385 Ignore (0x0) or Success (0x3), the following relationships MUST hold: 1387 o if the message is sent by the NAS, the bandwidth value in the 1388 Bandwidth-Allocation TLV MUST be greater than or equal to the 1389 sender's view of the current amount of delegated bandwidth for the 1390 access line concerned; 1392 o if the message is sent by the AN, the bandwidth value in the 1393 Bandwidth-Allocation TLV MUST be less than or equal to the 1394 sender's view of the current amount of delegated bandwidth for the 1395 access line concerned. 1397 Further sender behaviour is specified above, in Section 4.5.2. 1399 4.6.2. Receiver Behaviour 1401 4.6.2.1. Behaviour of the NAS 1403 If the amount of delegated bandwidth provided in the Bandwidth- 1404 Allocation TLV is not greater than the NAS's view of the current 1405 amount of delegated bandwidth, the NAS MUST update its view of the 1406 current amount of delegated bandwidth to the amount indicated in the 1407 Bandwidth Transfer message. This is required regardless of whether 1408 the Result field of that message indicates Success or Failure. 1410 If the amount of delegated bandwidth provided in the Bandwidth- 1411 Allocation TLV is greater than the NAS's view of the current amount 1412 of delegated bandwidth, the NAS MAY accept the given value as its new 1413 value of delegated bandwidth. Alternatively, the NAS MAY force the 1414 AN to modify its view of the amount of delegated bandwidth to that 1415 held by the NAS, by sending a Port Management message for the target 1416 access line concerned, containing a Bandwidth-Allocation TLV with a 1417 value equal to the amount of delegated bandwidth the NAS wishes to 1418 enforce. 1420 4.6.2.2. Behaviour of the AN 1422 If the amount of delegated bandwidth provided in the Bandwidth- 1423 Allocation TLV of the Bandwidth Transfer message differs from the 1424 AN's view of the current amount of delegated bandwidth, the AN MUST 1425 update its view of the current amount of delegated bandwidth to the 1426 amount indicated in the Bandwidth Transfer message. This is required 1427 with the exception of a Bandwidth Transfer message with a Result 1428 field equal to Failure (0x4) and a Result Code field equal to 0x68 1429 "Inconsistent views of delegated bandwidth amount" or 0x69 "Bandwidth 1430 request conflict". If Result Code value 0x68 is received, the AN 1431 MUST issue a Delegated Bandwidth Query Request message to determine 1432 the NAS's current view of the amount of delegated bandwidth. The AN 1433 MUST update its own view based on the value returned in the Delegated 1434 Bandwidth Query Response. If Result Code value 0x69 is received, the 1435 AN SHOULD carry out this procedure unless it can account for the 1436 discrepancy as a result of a transfer of bandwidth to the NAS that 1437 was carried out just before the incoming Bandwidth Transfer message 1438 was processed. 1440 The two Result Code values indicate a race condition where the AN 1441 may have just completed a transfer of bandwidth to the NAS. As a 1442 result, the value given in the Bandwidth Transfer message may be 1443 outdated, and the AN needs to query the NAS to find its latest 1444 view. The procedure assumes that ordering is preserved between 1445 the Bandwidth Transfer message sent by the AN in response to the 1446 NAS's request and the subsequent Delegated Bandwidth Query Request 1447 message. 1449 If as the result of the procedures just described the AN determines 1450 that it has over-committed multicast bandwidth, it MUST NOT terminate 1451 any currently-active programs, but MUST NOT honour any more "join" 1452 requests until it is possible to do so within the limit set by its 1453 current value of delegated bandwidth. 1455 4.7. Delegated Bandwidth Query Request Message 1457 The Message Type for the Delegated Bandwidth Query Request (and 1458 Response) messages is 148. 1460 The Delegated Bandwidth Query Request message MAY be sent either by 1461 the NAS or by the AN to retrieve the peer's view of the amount of 1462 delegated bandwidth. The request contains one TLV: 1464 o a Target TLV designating the access line for which the information 1465 is requested. 1467 4.7.1. Sender Behaviour 1469 The sender MUST set the Result field in the header of the Delegated 1470 Bandwidth Query Request message to AckAll (0x2). The Result Code 1471 value MUST be set to 0x000. The sender MUST populate the ANCP 1472 Transaction Identifier field with a unique value, as described in 1473 Section 3.6.1.6 of [RFC6320]. 1475 4.7.2. Receiver Behaviour 1476 If the AN or NAS receives a valid Delegated Bandwidth Query Request 1477 message, it MUST respond with a Delegated Bandwidth Query Response 1478 message. The Result field in the header of the response MUST be set 1479 to Success (0x3). The Result Code field MUST be set to 0x000. The 1480 Transaction-Id field MUST be copied from the request message. The 1481 body of the response MUST contain the Target TLV, copied from the 1482 request message. Finally, the body of the response MUST contain a 1483 Bandwidth-Allocation TLV, containing the current amount of delegated 1484 bandwidth from the point of view of the receiver of the request. 1486 If the contents of the Delegated Bandwidth Query Request message are 1487 in error, the receiver MUST return a Delegated Bandwidth Query 1488 Response message with the Result field in the header set to Failure 1489 (0x3). The Result Code field MUST be set to the value that indicates 1490 the nature of the error (e.g., 0x500 "One or more of the specified 1491 ports do not exist"). The Transaction-Id field MUST be copied from 1492 the request. The body of the response MUST contain the Target TLV 1493 copied from the request. This MAY be followed by a Status-Info TLV 1494 giving further information about the error. 1496 4.8. Delegated Bandwidth Query Response Message 1498 The Delegated Bandwidth Query Response message is sent in reply to a 1499 Delegated Bandwidth Query Request. The response to a valid request 1500 contains two TLVs: 1502 o the Target TLV, copied from the request; 1504 o a Bandwidth-Allocation TLV, giving the responder's view of the 1505 current amount of multicast bandwidth delegated to the AN. 1507 The Message Type for the Delegated Bandwidth Query Response message 1508 is 148. 1510 4.8.1. Sender Behaviour 1512 Sender behaviour for the Delegated Bandwidth Query Response message 1513 is specified in Section 4.7.2. 1515 4.8.2. Receiver Behaviour 1517 If the Delegated Bandwidth Query Response message indicates Success 1518 (0x3), the following actions apply. 1520 4.8.2.1. Behaviour at the NAS 1522 If the amount of delegated bandwidth provided in the Bandwidth- 1523 Allocation TLV is less than the NAS's view of the current amount of 1524 delegated bandwidth, the NAS MUST update its view of the current 1525 amount of delegated bandwidth to the amount indicated in the 1526 Delegated Bandwidth Query Response message. 1528 If the amount of delegated bandwidth provided in the Bandwidth- 1529 Allocation TLV is greater than the NAS's view of the current amount 1530 of delegated bandwidth, the NAS MAY accept the given value as its new 1531 value of delegated bandwidth. Alternatively, the NAS MAY force the 1532 AN to modify its view of the amount of delegated bandwidth to that 1533 held by the NAS, by sending a Port Management message for the target 1534 access line concerned, containing a Bandwidth-Allocation TLV with a 1535 value equal to the amount of delegated bandwidth the NAS wishes to 1536 enforce. 1538 4.8.2.2. Behaviour at the AN 1540 The AN SHOULD accept the value returned in the Bandwidth-Allocation 1541 TLV of the Delegated Bandwidth Query Response message as the correct 1542 value of the current amount of delegated bandwidth. If the AN has 1543 currently committed more than this amount to active programs, it MUST 1544 NOT cease replicating the flows concerned, but MUST NOT honour any 1545 more Join requests until possible to do so within the new limit. 1547 A race condition is possible, where the AN sends a query, the NAS 1548 requests more bandwidth, then receives and responds to the query, 1549 then receives the Bandwidth Transfer message responding to its 1550 request. It is up to the AN to take appropriate action in this 1551 case. The best action appears to be not to act on the result of 1552 the first query, but to repeat the query after sending the 1553 Bandwidth Transfer message. Similar considerations apply to a 1554 race between queries from both sides. 1556 4.9. Multicast Flow Query Request and Response Messages 1558 This section defines two new messages called the Multicast Flow Query 1559 Request and Multicast Flow Query Response. The Multicast Flow Query 1560 Request is sent by the NAS to request information about the multicast 1561 flows that are active on the AN. The Multicast Flow Query Response 1562 is sent in response by the AN to provide the requested information to 1563 the NAS. 1565 The Message Type for the Multicast Flow Query Request and Multicast 1566 Flow Query Response messages is 149. 1568 The contents of the Multicast Flow Query Request and Response depend 1569 on the nature of the query, as described below. 1571 4.9.1. Sender Behaviour 1573 The sender of a Multicast Flow Query Request message MUST set the 1574 Result field to AckAll (0x2). The Result Code field MUST be set to 1575 0x000. The sender MUST populate the ANCP Transaction Identifier 1576 field with a unique value, as described in section 3.6.1.6 of 1577 [RFC6320]. 1579 The Multicast Flow Query Request MAY be used by the NAS to retrieve: 1581 o the AN's view of which multicast flows are currently active on a 1582 specified set of access ports; or 1584 o the AN's view of the access ports on which a specified set of 1585 multicast flows are currently active; or 1587 o the AN's view of all the multicast flows currently active on each 1588 access port of the AN. 1590 To retrieve the AN's view of which multicast flows are currently 1591 active on a given port of the AN, the NAS MUST include a Target TLV 1592 in the Multicast Flow Query Request payload identifying that port. 1593 The Target TLV is encoded as specified in [RFC6320]. 1595 To retrieve the AN's view of the ports currently receiving a given 1596 multicast flow, the NAS MUST include a Multicast-Flow TLV in the 1597 Multicast Flow Query Request payload identifying that flow. The 1598 Multicast-Flow TLV is encoded as specified in Section 5.11. 1600 The NAS MAY include multiple Target TLVs or multiple Multicast-Flow 1601 TLVs in the Multicast Flow Query Request, but MUST NOT include both 1602 Target and Multicast-Flow TLVs in the same message. 1604 To retrieve the AN's view of all of the multicast flows currently 1605 active on each port of the AN, the NAS MUST send a Multicast Flow 1606 Query Request which does not contain any instance of the Target TLV 1607 or the Multicast-Flow TLV. 1609 4.9.2. Receiver Behaviour 1611 The AN MUST respond to a Multicast Flow Query Request message that 1612 has a valid format and a valid content with a Multicast Flow Query 1613 Response message. The Result field in the response MUST be set to 1614 Success (0x3). The Result Code field MUST be set to 0x000. The 1615 Transaction-Id field MUST be copied from the request. 1617 If the Multicast Flow Query Request contained one (or more) Target 1618 TLVs, the AN MUST include, for each of these Target TLVs, the 1619 following set of TLVs: 1621 o Target TLV. This MUST be identical to the Target TLV in the 1622 received Multicast Flow Query Request message. 1624 o Multicast-Flow TLV(s). The Multicast-Flow TLV MUST appear once 1625 per multicast flow that is currently active on the AN port 1626 identified in the preceding Target TLV. 1628 The Target TLVs MUST appear in the response from the AN in the same 1629 order as in the query from the NAS. 1631 If the Multicast Flow Query Request contained one (or more) 1632 Multicast-Flow TLVs, the AN MUST include, for each of these 1633 Multicast-Flow TLVs, the following set of TLVs: 1635 o Multicast-Flow TLV. This MUST be identical to the Multicast-Flow 1636 TLV in the received Multicast Flow Query Request message. 1638 o Target TLV(s). The Target TLV MUST appear once per AN port on 1639 which the multicast flow identified in the preceding Multicast- 1640 Flow TLV is active. 1642 The Multicast-Flow TLVs MUST appear in the response from the AN in 1643 the same order as in the query from the NAS. 1645 If the Multicast Flow Query Request contained no Target TLV and no 1646 Multicast Flow TLV, the AN MUST include, for each AN port currently 1647 receiving multicast flow(s), the following set of TLVs: 1649 o Target TLV. This MUST identify one AN port. 1651 o Multicast-Flow TLV(s). The Multicast-Flow TLV MUST appear once 1652 per Multicast Flow that is currently active on the AN port 1653 identified in the preceding Target TLV. 1655 If the contents of the Multicast Flow Query Request are in error, the 1656 AN MUST reply with a Multicast Flow Query Response message with the 1657 Result field set to Failure (0x4) and the Result Code field set to 1658 indicate the nature of the error. If the request contained multiple 1659 instances of the Target TLV or the Multicast-Flow TLV and one of 1660 these is in error, the response message MUST contain the results for 1661 the preceding instances of the TLV as if there had been no error. 1662 These successful results MUST be followed by the TLV in error, copied 1663 from the request. The AN MUST NOT do further processing of the 1664 request. The AN MAY add a Status-Info TLV to provide further 1665 information on the nature of the error. 1667 4.10. Committed Bandwidth Report Message 1669 This section describes the Committed Bandwidth Report message, which 1670 is sent from the AN to the NAS to report the most recent amount of 1671 multicast bandwidth usage committed to one or more access lines. 1673 The Message Type for the Committed Bandwidth Report message is 150. 1675 The Committed Bandwidth Report message contains one or more instances 1676 of the Committed-Bandwidth TLV, as described in Section 5.13. 1678 4.10.1. Sender Behaviour 1680 The sender of a Committed Bandwidth Report message MUST set the 1681 Result field to Ignore (0x0). The Result Code field MUST be set to 1682 0x000. The sender MUST populate the ANCP Transaction Identifier 1683 field with a unique value, as described in section 3.6.1.6 of 1684 [RFC6320]. 1686 Each instance of the Committed-Bandwidth TLV included in the message 1687 MUST identify an access line for which the amount of committed 1688 multicast bandwidth has changed since the previous Committed 1689 Bandwidth Report message was sent and MUST report the latest amount 1690 of multicast bandwidth committed to that line. There MUST be only 1691 one instance of the Committed-Bandwidth TLV present in the message 1692 for any given access line. The message MUST include an instance of 1693 the Committed-Bandwidth TLV for every access line for which committed 1694 multicast bandwidth has changed since the previous Committed 1695 Bandwidth Report message was sent. 1697 Further behaviour at the AN is specified in Section 6.2.2. 1699 4.10.2. Receiver Behaviour 1701 The usage of the contents of a Committed Bandwidth Report message 1702 received by the NAS is implementation-dependent. One example is that 1703 the NAS uses the reports of multicast bandwidth commitments to adjust 1704 its forwarding scheduler operation to provide the intended level of 1705 QoS. 1707 The NAS MUST NOT reply to a valid Committed Bandwidth Report message. 1708 The NAS MAY send a Generic Response message indicating the nature of 1709 any errors detected in a Committed Bandwidth Report message that it 1710 has received. 1712 5. ANCP TLVs For Multicast 1714 This section defines new ANCP TLVs for the control of multicast 1715 flows. 1717 5.1. Multicast-Service-Profile TLV 1719 This document defines the new Multicast-Service-Profile TLV. 1721 The Multicast-Service-Profile TLV MAY be included in a Provisioning 1722 message as specified in Section 4.1. 1724 The Multicast-Service-Profile TLV is illustrated in Figure 6. It 1725 consists of a TLV header encapsulating a single instance of the 1726 Multicast-Service-Profile-Name TLV and one or more instances of the 1727 List-Action TLV. 1729 1 2 3 1730 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 1731 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1732 |TLV Type = Mcast Serv Profile | TLV Length | 1733 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1734 | Multicast-Service-Profile-Name TLV | 1735 | | 1736 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1737 | List-Action TLV | 1738 | | 1739 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1740 | ... | 1741 | | 1742 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1743 | List-Action TLV | 1744 | | 1745 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1747 Figure 6: Multicast-Service-Profile TLV 1749 The Multicast-Service-Profile TLV has the following fields: 1751 o The Multicast-Service-Profile TLV Type is 0x0013. 1753 o The TLV length is determined by the contents following the TLV 1754 header. 1756 o The Multicast-Service-Profile-Name TLV is described in 1757 Section 5.2. The Multicast-Service-Profile-Name TLV MUST contain 1758 an identifier which is unique over all profiles provisioned to the 1759 same AN partition. This identifier will be used to refer to the 1760 profile when activating it for a given target within a Port 1761 Management message (see Section 4.2). 1763 o The List-Action TLV is described in Section 5.3. The List-Action 1764 TLV(s) provide the content of a newly defined multicast service 1765 profile or modify the existing content. If more than one List- 1766 Action TLV is present, the order of the TLVs may be significant, 1767 since List-Action TLVs are processed in the order in whch they 1768 appear. 1770 5.2. Multicast-Service-Profile-Name TLV 1772 The Multicast-Service-Profile-Name TLV carries the identifier of a 1773 multicast service profile provisioned on the AN. It is illustrated 1774 in Figure 7. 1776 1 2 3 1777 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 1778 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1779 |TLV Type = MSP Name | TLV Length | 1780 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1781 | Multicast service profile identifier | 1782 | | 1783 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1785 Figure 7: Multicast-Service-Profile-Name TLV 1787 The Multicast-Service-Profile-Name TLV has the following fields: 1789 o The Multicast-Service-Profile-Name TLV Type is 0x0018. 1791 o TLV Length: up to 255 octets. 1793 o Multicast service profile identifier: an opaque sequence of octets 1794 identifying a specific multicast service profile. 1796 The identifier could have the form of human-readable text or an 1797 arbitrary binary value, depending on the operator's practices. 1799 5.3. List-Action TLV 1801 The List-Action TLV identifies multicast flows to be added to or 1802 removed from a list of white-, black-, or grey-listed flows. It is 1803 meaningful only in association with a Multicast-Service-Profile-Name 1804 TLV identifying the profile to which the List-Action TLV applies. 1805 Such an association can be achieved by placing both TLVs in the same 1806 base message payload or as embedded TLVs of another TLV such as the 1807 Multicast-Service-Profile. The List-Action TLV is shown in Figure 8. 1809 1 2 3 1810 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 1811 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1812 | TLV Type = List-Action TLV | TLV Length | 1813 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1814 | Operation | List Type | Reserved | 1815 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1816 | Address Family | Number of flow fields | 1817 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1818 | Multicast flow fields | 1819 ...... 1820 | | 1821 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1822 | Address Family | Number of flow fields | 1823 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1824 | Multicast flow fields | 1825 ...... 1826 | | 1827 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1829 Figure 8: List-Action TLV 1831 The List-Action TLV contains the following fields: 1833 o The List-Action TLV Type is 0x0021. 1835 o TLV Length: length of the subsequent contents. 1837 o Operation: operation to be performed upon the white, black, or 1838 grey list identified by the List Type field within the profile 1839 identified by the associated Multicast-Service-Profile-Name 1840 embedded TLV. The possible values are: 1842 * Add (0x01): the multicast flow fields are to be added to the 1843 list. 1845 * Delete (0x02): the multicast flow fields are to be removed from 1846 the list. Each multicast flow field in the List-Action MUST 1847 match exactly an existing entry in the list concerned. Thus to 1848 remove part of the range provided by a wildcarded list entry, 1849 it is necessary to remove the entire entry and add back the 1850 remaining partial range(s). 1852 * Replace (0x03): the multicast flow fields replace the existing 1853 contents of the list. 1855 o List Type: the list type being modified by this List-Action. The 1856 possible values are White (0x01), Black (0x02), or Grey (0x03). 1858 o Reserved: a sender MUST set this field to 0x0000. A receiver MUST 1859 ignore the contents of this field. 1861 o Address Family: the IP version of the set of multicast flow fields 1862 that follow, encoded according to [PIMreg]. Possible values are 1863 0x0001 (IPv4) or 0x0002 (IPv6). Either an IPv4 list or an IPv6 1864 list or both MAY be present in the List-Action TLV. 1866 o Number of flow fields: the number of multicast flow fields of the 1867 given address family which follow. 1869 o Multicast flow field: a field identifying one or more multicast 1870 flows. It consists of an 8-bit group address prefix length, an 1871 8-bit source address prefix length, a 0-16 octet group prefix, and 1872 a 0-16 octet source prefix, as shown in Figure 9. 1874 Each multicast flow field refers either to a Source-Specific 1875 Multicast (SSM) channel or to an Any Source Multicast (ASM) group. 1876 The scope of the designation may be broadened to multiple channels or 1877 groups through use of prefix length values smaller than the total 1878 address length for the given address family. Multicast flow fields 1879 MUST be placed consecutively within the embedded TLV without 1880 intervening padding except to round out individual addresses to the 1881 nearest octet boundary. 1883 A multicast flow field consists of two single-octet prefix lengths 1884 followed by zero to two prefix values as shown in Figure 9: 1886 +-+-+-+-+-+-+-+-+ 1887 | Group PrefLen | 1888 +-+-+-+-+-+-+-+-+ 1889 | Source PrefLen| 1890 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1891 | Group Prefix (multicast) (0 to 16 octets) | 1892 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1893 | Source Prefix (unicast, SSM only) (0 to 16 octets) | 1894 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1895 Figure 9: Organization of a Single Multicast Flow Field 1897 The prefix length has its usual meaning. It is the number of most- 1898 significant bits specified within the corresponding prefix. The 1899 prefix length MAY vary from 0 to 32 in the IPv4 sub-list, and from 0 1900 to 128 in the IPv6 sub-list. 1902 A value of 0x00 for either the Group PrefLen (prefix length) or the 1903 Source PrefLen indicates that any value of the corresponding address 1904 will match (wild card). If the value 0x00 is provided for a 1905 particular prefix length, the corresponding prefix MUST be omitted 1906 from the field contents. 1908 The length of a Source or Group Prefix field is equal to (PrefLen + 1909 7)/8 octets, truncated to the nearest integer. Unused bits at the 1910 end of the prefix MUST be set to zeroes. 1912 5.4. Sequence-Number TLV 1914 The Sequence-Number TLV conveys a sequence number of some sort. The 1915 specific meaning of the sequence number is message-specific. Within 1916 this specification, the Sequence-Number TLV is used as a embedded TLV 1917 in a Status-Info TLV, in a Generic Response reporting a failed 1918 command in a Multicast Replication Control or Multicast Admission 1919 Request message. It identifies the sequence number within the 1920 message of the command that failed. 1922 The Sequence-Number TLV has the format shown in Figure 10. 1924 1 2 3 1925 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 1926 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1927 |TLV Type = Sequence-Number | TLV Length = 4 | 1928 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1929 | Sequence number | 1930 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1932 Figure 10: Sequence-Number TLV 1934 The Sequence-Number TLV has the following fields: 1936 o The Sequence-Number TLV Type is 0x0022. 1938 o TLV length is 0x0004. 1940 o Sequence number: the sequence number of a specific entity within a 1941 series, where numbering starts from 1 for the first entity in the 1942 series. Represented as a 32-bit binary number, most significant 1943 bit first. 1945 5.5. Bandwidth-Allocation TLV 1947 The Bandwidth-Allocation TLV is used to indicate the total amount of 1948 video bandwidth delegated to the AN for multicast admission control 1949 for a given access line, in kilobits per second. The TLV has the 1950 format shown in Figure 11. 1952 1 2 3 1953 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 1954 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1955 |TLV Type = BW-Allocation | TLV Length = 4 | 1956 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1957 | Delegated amount (kbits/s) | 1958 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1960 Figure 11: The Bandwidth-Allocation TLV 1962 The Bandwidth-Allocation TLV has the following fields: 1964 o The Bandwidth-Allocation TLV Type is 0x0015. 1966 o TLV length is 4. 1968 o Delegated amount: the bandwidth amount delegated to the AN for 1969 admission of multicast video on a given port, kilobits per second. 1970 Presented as a 32-bit binary value, most significant bit first. 1972 5.6. White-List-CAC TLV 1974 The White-List-CAC TLV is used to indicate that the NAS wishes the AN 1975 to do admission control for white-listed flows. Details on when the 1976 White-List-CAC TLV may be provisioned are specified in Section 6. 1977 The White-List-CAC TLV is illustrated in Figure 12. 1979 1 2 3 1980 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 1981 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1982 |TLV Type = White-List-CAC | TLV Length = 0 | 1983 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1985 Figure 12: White-List-CAC TLV 1987 The White-List-CAC TLV contains the following fields: 1989 o The White-List-CAC TLV Type is 0x0024. 1991 o TLV length is 0, since the TLV contains no data other than the TLV 1992 header. 1994 5.7. MRepCtl-CAC TLV 1996 The MRepCtl-CAC TLV is used to indicate that the NAS wishes the AN to 1997 do admission control for flows added by the Multicast Replication 1998 Control message. Details on when the MRepCtl-CAC TLV may be 1999 provisioned are specified in Section 6. The MRepCtl-CAC TLV is 2000 illustrated in Figure 13. 2002 1 2 3 2003 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 2004 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2005 |TLV Type = MRepCtl-CAC | TLV Length = 0 | 2006 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2008 Figure 13: MRepCtl-CAC TLV 2010 The MRepCtl-CAC TLV contains the following fields: 2012 o The MRepCtl-CAC TLV Type is 0x0025. 2014 o TLV length is 0, since the TLV contains no data other than the TLV 2015 header. 2017 5.8. Bandwidth-Request TLV 2019 The Bandwidth-Request TLV is used to request an adjustment of the 2020 total amount of video bandwidth allocated to the AN for multicast 2021 admission control for a given line. The "Required amount" field 2022 indicates the minimum adjustment required to meet the request. The 2023 "Preferred amount" field indicates the adjustment the requestor would 2024 prefer to have, if possible. Section 4.5 discusses the required 2025 relationships between the "Required amount", "Preferred amount", and 2026 current values of total bandwidth allocated to the AN. 2028 The Bandwidth-Request TLV has the format shown in Figure 14. 2030 1 2 3 2031 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 2032 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2033 |TLV Type = Bandwidth-Request | TLV Length = 8 | 2034 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2035 | Required amount (kbits/s) | 2036 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2037 | Preferred amount (kbits/s) | 2038 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2040 Figure 14: The Bandwidth-Request TLV 2042 The Bandwidth-Request TLV has the following fields: 2044 o The Bandwidth-Request TLV Type is 0x0016. 2046 o The TLV length is 8 octets. 2048 o Required amount: the minimum or maximum amount, depending on 2049 whether the sender is the AN or the NAS respectively, of delegated 2050 video bandwidth that is being requested, in kilobits per second. 2051 Presented as a 32-bit binary value, most significant bit first. 2053 o Preferred amount: the preferred amount of delegated video 2054 bandwidth that is being requested, in kilobits per second. 2055 Presented as a 32-bit binary value, most significant bit first. 2057 5.9. Request-Source-IP TLV 2059 The Request-Source-IP TLV provides the IP address of the entity that 2060 originated a specific request to join or leave a multicast channel. 2061 The TLV is illustrated in Figure 15. 2063 1 2 3 2064 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 2065 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2066 | TLV Type = Request-Source-IP | TLV length = 4 or 16 | 2067 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2068 | Unicast Address | 2069 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2071 Figure 15: Request-Source-IP TLV 2073 The Request-Source-IP TLV contains the following fields: 2075 o The Request-Source-IP TLV Type is 0x0092. 2077 o TLV length is 4 for an IPv4 address or 16 for an IPv6 address. 2079 o Unicast address: IP address of the source of a multicast flow join 2080 request, in network byte order. 2082 5.10. Request-Source-MAC TLV 2083 The Request-Source-MAC TLV provides the MAC address of the entity 2084 that originated a specific request to join or leave a multicast 2085 channel. The TLV is illustrated in Figure 16. 2087 1 2 3 2088 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 2089 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2090 |TLV Type=Request-Source-MAC | TLV Length = 6 or 8 | 2091 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2092 | | 2093 +-+-+- IEEE MAC Address +-+-+-+ 2094 | | 2095 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2097 Figure 16: Request-Source-MAC TLV 2099 The Request-Source-MAC TLV contains the following fields: 2101 o The Request-Source-MAC TLV Type is 0x0093. 2103 o TLV length is either 6 octets (MAC-48 or EUI-48) or 8 octets 2104 (EUI-64). 2106 o IEEE MAC Address: MAC address of the device originating the 2107 request to join a multicast flow. Within the address, bytes and 2108 bits respectively shall be ordered from most to least significant, 2109 consistently with [IEEE48] for MAC-48 and EUI-48, and with 2110 [IEEE64] for EUI-64. 2112 EUI-48 and EUI-64 are registered trademarks of the IEEE. 2114 5.11. Multicast-Flow TLV 2116 The Multicast-Flow TLV specifies a multicast flow in terms of its 2117 multicast group address and, if applicable, its unicast source 2118 address. It is illustrated in Figure 17. 2120 1 2 3 2121 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 2122 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2123 |TLV Type = Multicast-Flow | TLV Length | 2124 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2125 | Flow Type | Addr Family | Reserved | 2126 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2127 | Multicast Group Address | 2128 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 2129 | Unicast Source Address (for SSM flows only) | 2130 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2131 Figure 17: Multicast-Flow TLV 2133 The Multicast-Flow TLV has the following fields: 2135 o The Multicast-Flow TLV Type is 0x0019. 2137 o TLV Length: ranges from a minimum of 8 (for an ASM IPv4 flow) to 2138 36 (for an IPv6 SSM flow). 2140 o Flow Type: 0x01 for Any Source Multicast (ASM), 0x02 for Source- 2141 Specific Multicast (SSM). 2143 o Addr Family: address family of the multicast source and group 2144 addresses, encoded in accordance with the IANA PIM Address Family 2145 registry ([PIMreg]). 0x01 indicates IPv4, 0x02 indicates IPv6. 2147 o Reserved: MUST be set to 0x0000 by the sender and MUST be ignored 2148 by the receiver. 2150 One possible use for this field in the future is to indicate 2151 the presence of PIM Join attributes attached to the source 2152 address (see [RFC5384]). The applicability of PIM attributes 2153 in the context of ANCP is for further study. 2155 o Multicast Group Address: a multicast group address within the 2156 given address family. The group address MUST always be present. 2158 o Unicast Source Address: unicast address within the given address 2159 family. If the Flow Type is 0x01 (ASM), a source address MUST NOT 2160 be present. If the Flow Type is 0x02 (SSM), a source address MUST 2161 be present. 2163 5.12. Report-Buffering-Time TLV 2165 The Report-Buffering-Time TLV provides the time for which a Committed 2166 Bandwidth Report message must be held with the intention of 2167 accumulating multiple reports of changed committed multicast 2168 bandwidth in one report, to reduce the volume of messages sent to the 2169 NAS. For further information see Section 6.2.2. The TLV is 2170 illustrated in Figure 18. 2172 1 2 3 2173 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 2174 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2175 |TLV Type=Report-Buffering-Time | TLV Length = 4 | 2176 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2177 | Buffering Time (ms) | 2178 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2179 Figure 18: Report-Buffering-Time TLV 2181 The Report-Buffering-Time TLV contains the following fields: 2183 o The Report-Buffering-Time TLV Type is 0x0094. 2185 o TLV length is 4 octets. 2187 o Buffering Time is a 32-bit unsigned integer containing a time 2188 value in ms. 2190 5.13. Committed-Bandwidth TLV 2192 The Committed-Bandwidth TLV identifies an access line and provides 2193 the current amount of multicast bandwidth that the AN has committed 2194 to it. The TLV is illustrated in Figure 19. 2196 1 2 3 2197 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 2198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2199 |TLV Type=Committed-Bandwidth | TLV Length (variable) | 2200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2201 | Committed Multicast Bandwidth (kbits/s) | 2202 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2203 | | 2204 +-+-+- Target TLV +-+-+-+ 2205 | | 2206 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2208 Figure 19: Committed-Bandwidth TLV 2210 The Committed-Bandwidth TLV contains the following fields: 2212 o The Committed-Bandwidth TLV Type is 0x0095. 2214 o TLV length is 4 octets plus the length of the Target TLV including 2215 its header and any padding. 2217 o Committed Multicast Bandwidth is a 32-bit unsigned integer 2218 providing a bandwidth amount in kbits/s. 2220 o The Target TLV identifies the access line to which this amount of 2221 multicast bandwidth is currently committed. 2223 6. Multicast Capabilities 2224 Section 3.5 of [RFC6320] defines a capability negotiation mechanism 2225 as well as a number of capabilities. This section defines five new 2226 capabilities in support of different modes of multicast operation: 2228 o NAS-initiated replication (capability type 3); 2230 o committed multicast bandwidth reporting (capability type 5); 2232 o conditional access with white and black lists (capability type 6); 2234 o conditional access with grey lists (capability type 7); 2236 o bandwidth delegation (capability type 8). 2238 The "Capability Data" field within the Capability TLV for all of 2239 these capabilities is empty. All of these capabilities are 2240 independent of the access technology. 2242 The remainder of this section consists of three sub-sections. 2243 Section 6.1 specifies the protocol elements that must be implemented 2244 in order to support each capability. Section 6.2 specifies the 2245 procedures that apply to each capability on its own. Section 6.3 2246 specifies how the capabilities interact if more than one multicast 2247 capability is included in the set of capabilities negotiated between 2248 the AN and the NAS. 2250 Note that if a request contains content that is not supported 2251 (according to the tables in Section 6.1) by the negotiated set of 2252 multicast capabilities, the appropriate response is to return a 2253 Generic Response message indicating Failure (0x4) with an appropriate 2254 code value. The body of the message MUST contain a Status-Info TLV. 2255 See Sections 4.2 and 4.5 in [RFC6320] for more details. 2257 6.1. Required Protocol Support 2259 This section specifies the protocol elements that MUST be implemented 2260 to support each of the four multicast capabilities. Support of 2261 multiple multicast capabilities requires implementation of the union 2262 of the sets of protocol elements applying to each of the individual 2263 capabilities in the supported set. 2265 In addition to the elements listed below, implementation of the 2266 Target TLV (Section 4.3 of [RFC6320]) is REQUIRED for all of the 2267 capabilities specified in this document. 2269 6.1.1. Protocol Requirements For NAS-Initiated Replication 2270 Table 1 specifies the protocol elements within Section 4 and 2271 Section 5 that MUST be implemented to support the NAS-initiated 2272 replication multicast capability. Additionally, implementation of 2273 the Multicast Replication Control message requires implementation of 2274 the Command TLV (Section 4.4 of [RFC6320] with additional details in 2275 Section 4.3 of this document). 2277 +-----------------+-------------------------------------------------+ 2278 | Reference | Protocol Element | 2279 +-----------------+-------------------------------------------------+ 2280 | Section 4.1 | Provisioning message with MRepCtl-CAC TLV | 2281 | | | 2282 | Section 4.2 | Port Management message with Bandwidth- | 2283 | | Allocation TLV. | 2284 | | | 2285 | Section 4.3 | Multicast Replication Control message | 2286 | | | 2287 | Section 4.9 | Multicast Flow Query Request and Response | 2288 | | messages | 2289 | | | 2290 | Section 5.4 | Sequence Number TLV | 2291 | | | 2292 | Section 5.5 | Bandwidth-Allocation TLV | 2293 | | | 2294 | Section 5.7 | MRepCtl-CAC TLV | 2295 | | | 2296 | Section 5.11 | Multicast-Flow TLV | 2297 +-----------------+-------------------------------------------------+ 2299 Table 1: Protocol Requirements For NAS-Initiated Replication 2301 6.1.2. Protocol Requirements For Committed Multicast Bandwidth 2302 Reporting 2304 Table 2 specifies the protocol elements within Section 4 and 2305 Section 5 that MUST be implemented to support the committed multicast 2306 bandwidth reporting capability. 2308 +-----------------+-------------------------------------------------+ 2309 | Reference | Protocol Element | 2310 +-----------------+-------------------------------------------------+ 2311 | Section 4.1 | Provisioning message with Report-Buffering-Time | 2312 | | TLV | 2313 | | | 2314 | Section 4.10 | Committed Bandwidth Report message | 2315 | | | 2316 | Section 4.9 | Multicast Flow Query Request and Response | 2317 | | messages | 2318 | | | 2319 | Section 5.12 | Report-Buffering-Timer TLV | 2320 | | | 2321 | Section 5.13 | Committed-Bandwidth TLV | 2322 | | | 2323 | Section 5.11 | Multicast-Flow TLV | 2324 +-----------------+-------------------------------------------------+ 2326 Table 2: Protocol Requirements For Committed Multicast Bandwidth 2327 Reporting 2329 6.1.3. Protocol Requirements For Conditional Access With White and 2330 Black Lists 2332 Table 3 specifies the protocol elements within Section 4 and 2333 Section 5 that MUST be implemented to support the conditional access 2334 with white and black lists multicast capability. 2336 +--------------+----------------------------------------------------+ 2337 | Reference | Protocol Element | 2338 +--------------+----------------------------------------------------+ 2339 | Section 4.1 | Provisioning message with Multicast-Service- | 2340 | | Profile TLV, white and black lists only, and | 2341 | | White-List-CAC TLV | 2342 | | | 2343 | Section 4.2 | Port Management message with Multicast-Service- | 2344 | | Profile-Name and Bandwidth-Allocation TLVs. | 2345 | | | 2346 | Section 4.9 | Multicast Flow Query Request and Response messages | 2347 | | | 2348 | Section 5.1 | Multicast-Service-Profile TLV | 2349 | | | 2350 | Section 5.2 | Multicast-Service-Profile-Name TLV | 2351 | | | 2352 | Section 5.3 | List-Action TLV, white and black lists only | 2353 | | | 2354 | Section 5.5 | Bandwidth-Allocation TLV | 2355 | | | 2356 | Section 5.6 | White-List-CAC TLV | 2357 | | | 2358 | Section 5.11 | Multicast-Flow TLV | 2359 +--------------+----------------------------------------------------+ 2361 Table 3: Protocol Requirements For Conditional Access with White and 2362 Black Lists 2364 6.1.4. Protocol Requirements For Conditional Access With Grey Lists 2365 Table 4 specifies the protocol elements within Section 4 and 2366 Section 5 that MUST be implemented to support the conditional access 2367 with grey lists multicast capability. Additionally, implementation 2368 of the Multicast Replication Control message requires implementation 2369 of the Command TLV (Section 4.4 of [RFC6320] with additional details 2370 in Section 4.3 of this document). 2372 +--------------+----------------------------------------------------+ 2373 | Reference | Protocol Element | 2374 +--------------+----------------------------------------------------+ 2375 | Section 4.1 | Provisioning message with Multicast-Service- | 2376 | | Profile TLV, grey lists only, and MRepCtl-CAC TLV | 2377 | | | 2378 | Section 4.2 | Port Management message with Multicast-Service- | 2379 | | Profile-Name and Bandwidth-Allocation TLVs. | 2380 | | | 2381 | Section 4.3 | Multicast Replication Control message | 2382 | | | 2383 | Section 4.4 | Multicast Admission Control Message | 2384 | | | 2385 | Section 4.9 | Multicast Flow Query Request and Response messages | 2386 | | | 2387 | Section 5.1 | Multicast-Service-Profile TLV, grey lists only | 2388 | | | 2389 | Section 5.2 | Multicast-Service-Profile-Name TLV | 2390 | | | 2391 | Section 5.3 | List-Action TLV, grey lists only | 2392 | | | 2393 | Section 5.4 | Sequence Number TLV | 2394 | | | 2395 | Section 5.5 | Bandwidth-Allocation TLV | 2396 | | | 2397 | Section 5.7 | MRepCtl-CAC TLV | 2398 | | | 2399 | Section 5.9 | Request-Source-IP TLV | 2400 | | | 2401 | Section 5.10 | Request-Source-MAC TLV | 2402 | | | 2403 | Section 5.11 | Multicast-Flow TLV | 2404 +--------------+----------------------------------------------------+ 2406 Table 4: Protocol Requirements For Conditional Access with Grey Lists 2408 6.1.5. Protocol Requirements For Delegated Bandwidth 2410 Table 5 specifies the protocol elements within Section 4 and 2411 Section 5 that MUST be implemented to support the delegated bandwidth 2412 multicast capability. 2414 +-----------------+-------------------------------------------------+ 2415 | Reference | Protocol Element | 2416 +-----------------+-------------------------------------------------+ 2417 | Section 4.2 | Port Management message with Bandwidth- | 2418 | | Allocation TLV. | 2419 | | | 2420 | Section 4.5 | Bandwidth Reallocation Request Message | 2421 | | | 2422 | Section 4.6 | Bandwidth Transfer Message | 2423 | | | 2424 | Section 4.7 | Delegated Bandwidth Query Request Message | 2425 | | | 2426 | Section 4.8 | Delegated Bandwidth Query Response Message | 2427 | | | 2428 | Section 4.9 | Multicast Flow Query Request and Response | 2429 | | messages | 2430 | | | 2431 | Section 5.5 | Bandwidth-Allocation TLV | 2432 | | | 2433 | Section 5.8 | Bandwidth-Request TLV | 2434 | | | 2435 | Section 5.11 | Multicast-Flow TLV | 2436 +-----------------+-------------------------------------------------+ 2438 Table 5: Protocol Requirements For Delegated Bandwidth 2440 6.2. Capability-Specific Procedures for Providing Multicast Service 2442 This section describes multicast service procedures for each 2443 capability as if it were the only multicast capability within the 2444 negotiated set. Procedures involving combinations of multicast 2445 capabilities are described in Section 6.3. 2447 The use of the Multicast Flow Query Request and Response messages to 2448 determine the association between multicast flows and ports is common 2449 to all multicast capabilities. No additional text is required here, 2450 beyond that already given in Section 4.9 to describe the use of those 2451 messages. 2453 6.2.1. Procedures For NAS-Initiated Replication 2454 NAS-initiated replication may be negotiated to support a mode of 2455 operation where IGMP/MLD requests are terminated on the NAS. 2456 Alternatively, it may be negotiated to allow the NAS to respond to 2457 requests sent by other means (e.g., through application signalling) 2458 that require the replication of multicast channels to a given access 2459 line. 2461 6.2.1.1. Provisioning 2463 The NAS MAY perform admission control for NAS-initiated replication. 2464 In this case, it MUST NOT include the MRepCtl-CAC TLV in a 2465 Provisioning message sent to the AN. Alternatively, the NAS MAY 2466 enable admission control at the AN for NAS-initiated replication. To 2467 do this, it MUST include the MRepCtl-CAC TLV in a Provisioning 2468 message sent to the AN and it MUST also include a Bandwidth- 2469 Allocation TLV in a Port Management message for each access line. 2471 6.2.1.2. Multicast Service Procedures 2473 The procedures associated with NAS-initiated replication are 2474 straightforward. To initiate replication, the NAS MUST send a 2475 Multicast Replication Control message to the AN, containing one or 2476 more commands adding flows, as described in Section 4.3.1. To 2477 terminate replication the NAS MUST send a Multicast Replication 2478 Control message where the commands delete instead of adding the 2479 flows. The AN acts upon these messages as specified in 2480 Section 4.3.2. 2482 6.2.2. Procedures For Committed Bandwidth Reporting 2484 Committed bandwidth reporting may be negotiated if the NAS requires 2485 current knowledge of the amount of multicast bandwidth committed to 2486 each access line and cannot obtain this information by other means. 2488 6.2.2.1. Provisioning 2490 The default buffering time when committed bandwidth reporting is 2491 enabled is zero (immediate reporting). To change this, the NAS MAY 2492 send an instance of the Report-Buffering-Time TLV containing a non- 2493 zero time value to the AN in a Provisioning message. If the NAS 2494 subsequently wishes to change the buffering time again, it MAY do so 2495 in another Provisioning message. 2497 6.2.2.2. Multicast Service Procedures 2499 If the buffering time for committed bandwidth reporting is zero, the 2500 AN MUST send a Committed Bandwidth Report message to the NAS each 2501 time the amount of multicast bandwidth committed to any access line 2502 under its control changes. 2504 If a non-zero value is provided in the Report-Buffering-Time TLV, the 2505 AN at any given moment is in one of two states: not-buffering, or 2506 buffering. The AN enters buffering state if it is in not-buffering 2507 state and the multicast bandwidth amount committed to some access 2508 line changes. It leaves buffering state when the AN sends a 2509 Committed Bandwidth Report. 2511 Upon entry to the buffering state, the AN MUST start a buffering 2512 timer and create a Committed Bandwidth Report message containing a 2513 Committed-Bandwidth TLV for the triggering access line, but MUST NOT 2514 send it. If a multicast bandwidth change occurs for another access 2515 line, the AN MUST add a new Committed-Bandwidth TLV to the message 2516 for that additional line. If a multicast bandwidth change occurs for 2517 a line for which a Committed-Bandwidth TLV is already present in the 2518 buffered report, the AN MUST update the corresponding Committed- 2519 Bandwidth TLV to contain the new bandwidth value, rather than adding 2520 another Committed-Bandwidth TLV for the same access line. 2522 The buffering timer expires after the period provided by the Report- 2523 Buffering-Time TLV. When it expires, the AN MUST send the Committed 2524 Bandwidth Report message that it has been accumulating to the NAS. 2525 Exceptionally, the AN MAY choose to send the message before the timer 2526 expires, in which case it MUST clear the buffering timer when the 2527 message is sent. In either case, the AN enters the not-buffering 2528 state as a result. 2530 Report buffering implies that NAS reaction to changes in multicast 2531 bandwidth usage is delayed by the amount of the buffering period. 2532 The choice of buffering period must take this into consideration. 2534 6.2.3. Procedures For Conditional Access With Black and White Lists 2536 6.2.3.1. Provisioning 2538 The NAS provisions named multicast service profiles containing white 2539 and black lists on the AN using the Provisioning message containing 2540 one or more Multicast-Service-Profile TLVs. The NAS MAY update the 2541 contents of these profiles from time to time as required, by sending 2542 additional Provisioning messages with Multicast-Service-Profile TLVs 2543 containing incremental modifications to the existing white and black 2544 lists or replacements for them. 2546 The NAS assigns a specific multicast service profile to an individual 2547 access line using the Port Management message containing a Multicast- 2548 Service-Profile-Name TLV. The NAS MAY change the multicast service 2549 profile for a given access line at any time by sending a Port 2550 Management message identifying a new multicast service profile. 2552 The NAS MAY choose to enable admission control at the AN for white- 2553 listed flows. To do this, it MUST send a Provisioning message as 2554 described in Section 4.1, which includes the White-List-CAC TLV and 2555 it MUST provide a multicast bandwidth allocation for each access line 2556 by including a Bandwidth-Allocation TLV in a Port Management message. 2558 6.2.3.2. Multicast Service Procedures 2560 The conditional access with white and black lists capability assumes 2561 that IGMP/MLD requests are terminated on the AN. When the AN 2562 receives a "join" request, it MUST check to see whether the requested 2563 flow is white-listed or black-listed as described below. Requests 2564 for black-listed flows MUST be discarded. If the NAS has enabled 2565 admission control on the AN as described in the previous section, but 2566 a white-listed flow would cause the amount of committed multicast 2567 bandwidth to exceed the provisioned limit, the request MUST be 2568 discarded. The AN replicates flows passing these checks to the 2569 access line. 2571 To determine if a requested flow is white-listed, the AN searches for 2572 a best match to the flow in the applicable multicast service profile. 2573 Matching is done on the prefixes specified in the profile, ignoring 2574 the address bits of lower order than those in the prefix. 2576 If the requested multicast flow matches multiple lists associated 2577 with the access line, then the most specific match will be considered 2578 by the AN. If the most specific match occurs in multiple lists, the 2579 black list entry takes precedence over the white list. In this 2580 context, the most specific match is defined as: 2582 o first, most specific match (longest prefix length) on the 2583 multicast group address (i.e., on G of ) 2585 o then, most specific match (longest prefix length) on the unicast 2586 source address (i.e. on S of ) 2588 If the requested multicast flow is not part of any list, the join 2589 message SHOULD be discarded by the AN. This default behavior can 2590 easily be changed by means of a "catch-all" statement in the white 2591 list. For instance, adding () in the white List would make 2592 the default behavior to accept join messages for a multicast flow 2593 that has no other match on any list. 2595 When the AN receives a "leave" request, it terminates replication of 2596 the multicast flow. 2598 If the AN receives a Provisioning message which updates an existing 2599 multicast service profile, the AN MUST review the status of active 2600 flows on all ports to which the updated profile is currently 2601 assigned. Similarly, if a Port Management message assigns a new 2602 multicast service profile to a given port, the AN MUST review all 2603 active flows on that port. If the most specific match for any flow 2604 is a black list entry, the flow MUST be terminated immediately. If 2605 any of the remaining flows do not match an entry in the white list, 2606 they also MUST be terminated immediately. White listed flows MUST be 2607 allowed to continue. 2609 6.2.4. Procedures For Conditional Access With Grey Lists 2611 6.2.4.1. Provisioning 2613 The NAS provisions named multicast service profiles containing grey 2614 lists on the AN using the Provisioning message containing one or more 2615 Multicast-Service-Profile TLVs. The NAS MAY update the contents of 2616 these profiles from time to time as required, by sending additional 2617 Provisioning messages with Multicast-Service-Profile TLVs containing 2618 incremental modifications to the existing grey lists or replacements 2619 for them. 2621 The NAS assigns a specific multicast service profile to an individual 2622 access line using the Port Management message containing a Multicast- 2623 Service-Profile-Name TLV. The NAS MAY change profiles on the line by 2624 sending a subsequent Port Management message identifying a new 2625 profile. 2627 The NAS MAY perform admission control for grey-listed flows. In that 2628 case, the NAS MUST NOT include the MRepCtl-CAC TLV in a Provisioning 2629 message sent to the AN. Alternatively, the NAS MAY enable admission 2630 control at the AN for grey-listed flows. To do this, it MUST include 2631 the MRepCtl-CAC TLV in a Provisioning message sent to the AN and MUST 2632 also provide a Bandwidth-Allocation TLV in a Port Management message 2633 for each access line. 2635 6.2.4.2. Multicast Service Procedures 2637 The conditional access with grey lists capability assumes that IGMP/ 2638 MLD requests are terminated on the AN. When the AN receives a "join" 2639 request, it MUST determine whether there is a match to the requested 2640 flow in the grey list of the multicast service profile provisioned 2641 against the given access line. If there is no match, the request is 2642 discarded. Otherwise, the AN MUST send a Multicast Admission Control 2643 message to the NAS with content identifying the access line and the 2644 multicast flow to be added. As indicated in Section 4.4, the AN MAY 2645 add information identifying the requestor by IP address and/or MAC 2646 address. 2648 If the NAS decides to enable the flow, it MUST send a Multicast 2649 Replication Control request to the AN to replicate the flow to the 2650 access line with the Result field set to Nack (0x1), as described in 2651 Section 4.3.1. 2653 When the AN receives the Multicast Replication Control request, it 2654 performs admission control if admission control has been enabled as 2655 described in the previous section. If admitting the flow would cause 2656 the committed multicast bandwidth at the access line to exceed the 2657 provisioned limit, the AN reports an error to the NAS as described in 2658 Section 4.3.2. Otherwise it replicates the multicast flow as 2659 requested. 2661 If the NAS decides not to permit the flow, it MAY send a Multicast 2662 Replication Control message in response to the Multicast Admission 2663 Control message to allow the AN to update its internal records. The 2664 content of this message is described in Section 4.4.2. 2666 When the AN receives a "leave" request, it MUST terminate replication 2667 of the flow to the access line. It MUST then send a Multicast 2668 Admission Control message to the NAS indicating the deletion. The 2669 NAS updates its internal records but MUST NOT respond to the message. 2671 If the AN receives a Provisioning message which updates an existing 2672 multicast service profile, the AN MUST review the status of active 2673 flows on all ports to which the updated profile has been assigned. 2674 Similarly, if a Port Management message that assigns a new profile to 2675 a given port, the AN MUST review all active flows on that port. In 2676 either case, if any flow does not match an entry in the grey list, it 2677 MUST be terminated immediately. 2679 6.2.5. Procedures For Delegated Bandwidth 2681 6.2.5.1. Provisioning 2683 The NAS SHOULD provision an initial amount of delegated multicast 2684 bandwidth for each access line using the Port Management message 2685 containing the Bandwidth-Allocation TLV. 2687 If it fails to do so and a value has not been provisioned on the 2688 AN by other means, the AN will be forced to request a bandwidth 2689 allocation as soon as it receives a "join" request. 2691 The NAS MAY at any time force an update of the amount of delegated 2692 bandwidth by the same means. 2694 6.2.5.2. Multicast Service Procedures 2696 The delegated bandwidth capability assumes that IGMP/MLD requests are 2697 terminated on the AN. When the AN receives a "join" request, it 2698 checks whether it has sufficient remaining uncommitted multicast 2699 bandwidth on the access line to accommodate the new multicast flow. 2700 If not, it MAY send a request to the NAS for an increased allocation 2701 of delegated bandwidth, using the Bandwidth Reallocation Request 2702 message. The NAS MUST return a Bandwidth Transfer message indicating 2703 whether it has granted the request, and if so, what is the new amount 2704 of delegated bandwidth. 2706 If the AN has sufficient uncommitted multicast capacity to admit the 2707 request, either originally or as the result of a successful request 2708 to the NAS, it replicates the requested flow to the access line. 2709 Otherwise it discards the request. 2711 When the AN receives a "leave" request for an active flow, it ceases 2712 replication. 2714 The NAS or AN MAY at some point detect that their respective views of 2715 the amount of delegated bandwidth are inconsistent. If so, they can 2716 recover using procedures described in Section 4.5 and Section 4.6. 2717 As a further aid to synchronization, either the NAS or the AN MAY 2718 from time to time check the peer's view of the amount of delegated 2719 bandwidth using the Delegated Bandwidth Query message. 2721 The NAS or AN MAY at any time release bandwidth to the peer using an 2722 autonomous Bandwidth Transfer message. The contents of this message 2723 are described in Section 4.6. 2725 6.3. Combinations of Multicast Capabilities 2727 6.3.1. Combination of Conditional Access With White and Black Lists and 2728 Conditional Access With Grey Lists 2730 If conditional access with white and black lists is combined with 2731 conditional access with grey lists, provisioning of the multicast 2732 service profiles is as described in Section 6.2.3.1 except that 2733 multicast service profiles will also include grey lists. Admission 2734 control is enabled independently on the AN for white lists by 2735 including the White-List-CAC TLV in the Provisioning message and for 2736 grey lists by including the MRepCtl-CAC TLV in the Provisioning 2737 message. The Bandwidth-Allocation TLV provisions an amount that 2738 applies to both white- and grey- listed flows if admission control is 2739 enabled for both. 2741 With regard to multicast service procedures, one point of difference 2742 from the individual capabilities must be noted. This is an 2743 interaction during the profile matching procedure. The AN MUST seek 2744 the best match amongst multiple lists as described in 2745 Section 6.2.3.2. However, if there are multiple matches of equal 2746 precision, the order of priority is black list first, grey list 2747 second, and white list last. 2749 Once profile matching has been completed, processing of a "join" 2750 request is as described in Section 6.2.3.2 for white or black listed 2751 flows or Section 6.2.4.2 for grey listed flows. Requests that do not 2752 match any list SHOULD be discarded. 2754 When the AN receives a "leave" request, it MUST terminate replication 2755 of the flow to the access line. If the flow was grey-listed, the AN 2756 MUST then send a Multicast Admission Control message to the NAS 2757 indicating the deletion. Thus the AN needs to retain the fact that 2758 the flow was grey-listed for the life of the flow. 2760 If the AN receives a Provisioning message which updates an existing 2761 multicast service profile, the AN MUST review the status of active 2762 flows on all ports to which the updated profile is currently 2763 assigned. Similarly, if a Port Management message assigns a new 2764 multicast service profile to a given port, the AN MUST review all 2765 active flows on that port. If any flow has its most specific match 2766 in a black list entry, it MUST be terminated immediately. If any of 2767 the remaining flows do not match an entry in the white or grey list, 2768 they MUST also be terminated immediately. Finally, if any remaining 2769 flows were originally admitted because they were white-listed, but 2770 after the change they are grey-listed, the AN MUST generate a 2771 Multicast Flow Query response message autonomously as if it were 2772 responding to a Multicast Flow Query request, listing all such flows. 2773 These flows MUST be allowed to continue until the NAS or the 2774 subscriber terminates them. Flows with their most specific match in 2775 the white list MUST be allowed to continue. 2777 The autonomously-generated Multicast Flow Query response message MUST 2778 be formatted as if it were a successful response to a request 2779 containing no Target and no Multicast-Flow TLV, as described in 2780 Section 4.9.2, with the exception that the Transaction-Id MUST be set 2781 to all zeroes. 2783 6.3.2. Combination of Conditional Access With Delegated Bandwidth 2785 The provisioning and bandwidth management procedures of Section 6.2.5 2786 apply in addition to the procedures in Section 6.2.3, Section 6.2.4, 2787 or Section 6.3.1 as applicable. Admission control follows the rules 2788 for conditional access in terms of matching flows against white and 2789 black and/or grey lists and performing or not performing bandwidth 2790 checks at the AN, but the amount of bandwidth used by the AN to 2791 perform admission control is negotiable as described in 2792 Section 6.2.5.2. 2794 6.3.3. Combination of NAS-Initiated Replication with Other Capabilities 2796 NAS-initiated replication can coexist with the other capabilities, 2797 but some means must exist to prevent double replication of flows. 2798 The simplest way to do this is to terminate all IGMP/MLD requests on 2799 the AN, so that NAS-initiated replication is stimulated only by 2800 signalling through other channels. Other arrangements are possible, 2801 but need not be discussed here. 2803 Assuming the necessary separation of responsibilities, the only point 2804 of interaction between NAS-initiated replication and the other 2805 multicast capabilities is in the area of admission control. 2806 Specifically, if the AN is to do admission control for flows added by 2807 Multicast Replication Control messages, regardless of whether they 2808 are part of NAS-initiated replication or grey list multicast service 2809 processing, the NAS includes the MRepCtl-CAC TLV in a Provisioning 2810 message and the Bandwidth-Allocation TLV in a Port Management 2811 message. If instead the NAS will do admission control for flows 2812 added by Multicast Replication Control messages, regardless of 2813 whether they are part of NAS-initiated replication or grey list 2814 multicast service processing, it does not send the MRepCtl-CAC TLV in 2815 a Provisioning messages to the AN. The NAS can independently enable 2816 Admission Control for white flows on the AN by including the White- 2817 List-CAC TLV in the Provisioning message. 2819 6.3.4. Combinations of Committed Bandwidth Reporting with Other 2820 Multicast Capabilities 2822 Committed bandwidth reporting can take place independently of which 2823 other multicast capabilities have been negotiated. However, some 2824 combinations do not make sense because of redundancy. In particular, 2825 the NAS obtains the same information that committed bandwidth 2826 reporting gives if the only other capabilities operating are NAS- 2827 initiated replication and/or conditional access with grey lists. 2829 7. Security Considerations 2831 The security considerations of ANCP are discussed in [RFC6320] and in 2832 [RFC5713]. Multicast does not in principle introduce any new 2833 security considerations, although it does increase the attractiveness 2834 of the ANCP protocol as a means of denial of service (e.g., through 2835 direction of multicast streams onto the target) or theft of service. 2837 8. IANA Considerations 2839 IANA NOTE: Please replace XXXX with the RFC number of this document. 2841 This document defines the following additional values within the ANCP 2842 Message Type Name Space registry: 2844 +--------------+--------------------------------+-----------+ 2845 | Message Type | Message Name | Reference | 2846 +--------------+--------------------------------+-----------+ 2847 | 144 | Multicast Replication Control | RFC XXXX | 2848 | | | | 2849 | 145 | Multicast Admission Control | RFC XXXX | 2850 | | | | 2851 | 146 | Bandwidth Reallocation Request | RFC XXXX | 2852 | | | | 2853 | 147 | Bandwidth Transfer | RFC XXXX | 2854 | | | | 2855 | 148 | Delegated Bandwidth Query | RFC XXXX | 2856 | | | | 2857 | 149 | Multicast Flow Query | RFC XXXX | 2858 | | | | 2859 | 150 | Committed Bandwidth Report | RFC XXXX | 2860 +--------------+--------------------------------+-----------+ 2862 This document defines the following additional values for the ANCP 2863 Result Code registry: 2865 +--------------+------------------------------------+---------------+ 2866 | Result Code | One-Line Description | Reference | 2867 +--------------+------------------------------------+---------------+ 2868 | 0x64 | Command error. | RFC XXXX | 2869 | | | | 2870 | 0x65 | Invalid flow address. | RFC XXXX | 2871 | | | | 2872 | 0x66 | Multicast flow does not exist. | RFC XXXX | 2873 | | | | 2874 | 0x67 | Invalid preferred bandwidth | RFC XXXX | 2875 | | amount. | | 2876 | | | | 2877 | 0x68 | Inconsistent views of delegated | RFC XXXX | 2878 | | bandwidth amount. | | 2879 | | | | 2880 | 0x69 | Bandwidth request conflict. | RFC XXXX | 2881 +--------------+------------------------------------+---------------+ 2883 This document defines the following additional values for the ANCP 2884 Command Code registry: 2886 +-----------------+---------------------------------+---------------+ 2887 | Command Code | Command Code Directive Name | Reference | 2888 | Value | | | 2889 +-----------------+---------------------------------+---------------+ 2890 | 1 | Add | RFC XXXX | 2891 | | | | 2892 | 2 | Delete | RFC XXXX | 2893 | | | | 2894 | 3 | Delete All | RFC XXXX | 2895 | | | | 2896 | 4 | Admission Control Reject | RFC XXXX | 2897 | | | | 2898 | 5 | Conditional Access Reject | RFC XXXX | 2899 | | | | 2900 | 6 | Admission Control and | RFC XXXX | 2901 | | Conditional Access Reject | | 2902 +-----------------+---------------------------------+---------------+ 2904 This document defines the following additional values within the ANCP 2905 TLV Type Registry: 2907 +-----------+--------------------------------+-----------+ 2908 | Type Code | TLV Name | Reference | 2909 +-----------+--------------------------------+-----------+ 2910 | 0x0013 | Multicast-Service-Profile | RFC XXXX | 2911 | | | | 2912 | 0x0015 | Bandwidth-Allocation | RFC XXXX | 2913 | | | | 2914 | 0x0016 | Bandwidth-Request | RFC XXXX | 2915 | | | | 2916 | 0x0018 | Multicast-Service-Profile-Name | RFC XXXX | 2917 | | | | 2918 | 0x0019 | Multicast-Flow | RFC XXXX | 2919 | | | | 2920 | 0x0021 | List-Action | RFC XXXX | 2921 | | | | 2922 | 0x0022 | Sequence-Number | RFC XXXX | 2923 | | | | 2924 | 0x0024 | White-List-CAC | RFC XXXX | 2925 | | | | 2926 | 0x0025 | MRepCtl-CAC | RFC XXXX | 2927 | | | | 2928 | 0x0092 | Request-Source-IP | RFC XXXX | 2929 | | | | 2930 | 0x0093 | Request-Source-MAC | RFC XXXX | 2931 | | | | 2932 | 0x0094 | Report-Buffering-Time | RFC XXXX | 2933 | | | | 2934 | 0x0095 | Committed-Bandwidth | RFC XXXX | 2935 +-----------+--------------------------------+-----------+ 2937 This document defines the following additional values for the ANCP 2938 Capability Type registry: 2940 +-------+---------------------+--------+--------------+-------------+ 2941 | Value | Capability Type | Tech | Capability | Reference | 2942 | | Name | Type | Data? | | 2943 +-------+---------------------+--------+--------------+-------------+ 2944 | 3 | NAS-Initiated | 0 | No | RFC XXXX | 2945 | | Replication | | | | 2946 | | | | | | 2947 | 5 | Committed Bandwidth | 0 | No | RFC XXXX | 2948 | | Reporting | | | | 2949 | | | | | | 2950 | 6 | Conditional Access | 0 | No | RFC XXXX | 2951 | | With White and | | | | 2952 | | Black Lists | | | | 2953 | | | | | | 2954 | 7 | Conditional Access | 0 | No | RFC XXXX | 2955 | | With Grey Lists | | | | 2956 | | | | | | 2957 | 8 | Bandwidth | 0 | No | RFC XXXX | 2958 | | Delegation | | | | 2959 +-------+---------------------+--------+--------------+-------------+ 2961 9. Acknowledgements 2963 The authors would like to acknowledge Wojciech Dec for providing 2964 useful input to this document, Robert Rennison for his help in 2965 shaping the definition of the Multicast-Service-Profile TLV, Shridhar 2966 Rao for his comments and suggestions and Aniruddha A for his proposal 2967 that formed the base of the Multicast Flow Reporting solution. 2968 Philippe Champagne, Sanjay Wadhwa and Stefaan De Cnodder provided 2969 substantial contributions on the solution for the NAS initiated 2970 multicast control use case. Kristian Poscic provided the committed 2971 bandwidth reporting use case. 2973 10. References 2975 10.1. Normative References 2977 [IEEE48] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/ 2978 EUI48.html", 2010. 2980 [IEEE64] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/ 2981 EUI64.html", 2010. 2983 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2984 Requirement Levels", BCP 14, RFC 2119, March 1997. 2986 [RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast 2987 Listener Discovery (MLD) for IPv6", RFC 2710, October 2988 1999. 2990 [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. 2991 Thyagarajan, "Internet Group Management Protocol, Version 2992 3", RFC 3376, October 2002. 2994 [RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery 2995 Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. 2997 [RFC6320] Wadhwa, S., Moisand, J., Haag, T., Voigt, N., and T. 2998 Taylor, "Protocol for Access Node Control Mechanism in 2999 Broadband Networks", RFC 6320, October 2011. 3001 10.2. Informative References 3003 [I-D.morin-mboned-igmpmld-error-feedback] 3004 Morin, T. and B. Haberman, "IGMP/MLD Error Feedback", 3005 draft-morin-mboned-igmpmld-error-feedback-02 (work in 3006 progress), November 2008. 3008 [PIMreg] IANA, "http://www.iana.org/assignments/pim-parameters/pim- 3009 parameters.xhtml", 2005. 3011 [RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, 3012 "Protocol Independent Multicast - Sparse Mode (PIM-SM): 3013 Protocol Specification (Revised)", RFC 4601, August 2006. 3015 [RFC5384] Boers, A., Wijnands, I., and E. Rosen, "The Protocol 3016 Independent Multicast (PIM) Join Attribute Format", RFC 3017 5384, November 2008. 3019 [RFC5713] Moustafa, H., Tschofenig, H., and S. De Cnodder, "Security 3020 Threats and Security Requirements for the Access Node 3021 Control Protocol (ANCP)", RFC 5713, January 2010. 3023 [RFC5851] Ooghe, S., Voigt, N., Platnic, M., Haag, T., and S. 3024 Wadhwa, "Framework and Requirements for an Access Node 3025 Control Mechanism in Broadband Multi-Service Networks", 3026 RFC 5851, May 2010. 3028 Appendix A. Example of Messages and Message Flows 3030 This appendix provides an example in which most of the possible 3031 message flows for multicast control are illustrated. This appendix 3032 is for informational purposes only. In case of discrepancy with text 3033 of the body of this document, the text in the body of the document is 3034 to be considered as the normative text. 3036 Assume the following, for a given access port: 3038 o The basic subscribed service is white-listed. The AN will be 3039 responsible for admission control for this service. 3041 o Some premium services are available, but requests for these 3042 services must be referred to the policy server for proper credit 3043 processing. For this reason they are grey-listed. The NAS will 3044 be responsible for admission control for these services. 3046 o The subscriber has asked that certain services be blocked so that 3047 his children cannot view them. These services are black-listed. 3049 o All of the above services are Source-Specific Multicast (SSM). In 3050 addition, by means which bypass the AN, the subscriber can signal 3051 intent to join an on-line game service which is Any Source 3052 Multicast (ASM). The NAS is responsible for admission control for 3053 this service. 3055 o Bandwidth delegation is in effect to share video bandwidth between 3056 the AN and the NAS. 3058 The stated conditions require the use of four of the five 3059 capabilities specified in this memo. 3061 A.1. Provisioning Phase 3063 Assume that capability negotiation has been completed between the AN 3064 and NAS and that the set of negotiated capabilities includes the 3065 following four multicast capabilities: NAS-initiated replication, 3066 conditional access with white and black list, conditional access with 3067 grey list, and bandwidth delegation. At this point, the NAS can 3068 provision the service profiles on the AN and enable admission control 3069 at the AN for white-listed flows. To do this, the NAS sends the AN a 3070 Provisioning message containing this information. An example message 3071 providing the profile for our assumed subscriber is shown in Figure 3072 20. The message has the following contents: 3074 o Message type is 93. 3076 o The Result and Result Code fields in the header are set to zeroes, 3077 as specified [RFC6320]. 3079 o A Transaction identifier is assigned by the NAS. 3081 o The Multicast-Service-Profile TLV (of which typically there would 3082 be multiple instances) contains a Multicast-Service-Profile-Name 3083 TLV (with a length of 20 octets assumed for the example) and three 3084 List-Action TLVs, one each for the white, grey, and black lists 3085 within the profile. The white list flows come in two sets of 3086 group addresses: 233.252.0.0/29, coming from a server at 3087 192.0.2.15, and 233.252.0.32/29, coming from a server at 3088 192.0.2.16. The grey-listed flows are in the band 233.252.0.64/ 3089 29, coming from a server at 192.0.2.21. Finally, the black list 3090 flows are two individual flows that happen to overlap with the 3091 grey list band: 233.252.0.65, and 233.252.0.69, also with source 3092 192.0.2.21. 3094 o The White-List-CAC TLV indicates that the AN does admission 3095 control on white-listed flows. 3097 1 2 3 3098 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 3099 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3100 | Type (0x880C) | Length = 132 | 3101 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3102 | Version | Msg Type = 93 | 0x00 | Result Code = 0x000 | 3103 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3104 | Partition ID | Transaction Identifier | 3105 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3106 |I| SubMessage Number | Length = 132 | 3107 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3108 | M-Serv-Prof TLV Type = 0x13 | TLV Length = 112 | 3109 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3110 | M-S-Prof-Name TLV Type = 0x18 | Embedded TLV Length = 20 | 3111 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3112 | Multicast service profile name | 3113 ~ = "Cust 0127-53681-0003" ~ 3114 | | 3115 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3116 | List-Action TLV Type = 0x21 | Embedded TLV Length = 28 | 3117 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3118 | Oper = 0x01 |Lst Typ = 0x01 | Reserved = 0x0000 | 3119 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3120 | Address Family = 0x01 | List Length = 20 | 3121 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3122 | G Preflen = 29| S Preflen = 32| Group prefix = | 3123 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3124 | 233.252.0.0 | Source prefix = | 3125 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3126 | 192.0.2.15 | G Preflen = 29| S Preflen = 32| 3127 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3128 | Group prefix = 233.252.0.32 | 3129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3130 | Source prefix = 192.0.2.15 | 3131 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3132 | List-Action TLV Type = 0x21 | Embedded TLV Length = 18 | 3133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3134 | Oper = 0x01 |Lst Typ = 0x03 | Reserved = 0x0000 | 3135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3136 | Address Family = 0x01 | List Length = 10 | 3137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3138 | G Preflen = 29| S Preflen = 32| Group prefix = / 3139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3140 / 233.252.0.64 | Source prefix = / 3141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3142 / 192.0.2.21 | Padding = 0x0000 | 3143 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3144 | List-Action TLV Type = 0x21 | Embedded TLV Length = 28 | 3145 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3146 | Oper = 0x01 |Lst Typ = 0x02 | Reserved = 0x0000 | 3147 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3148 | Address Family = 0x01 | List Length = 20 | 3149 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3150 | G Preflen = 32| S Preflen = 32| Group prefix = / 3151 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3152 / 233.252.0.65 | Source prefix = / 3153 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3154 / 192.0.2.21 | G Preflen = 32| S Preflen = 32| 3155 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3156 | Group prefix = 233.252.0.69 | 3157 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3158 | Source prefix = 192.0.2.21 | 3159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3160 |White-List-CAC TLV Type = 0x24 | TLV Length = 0 | 3161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3163 Figure 20: Example Provisioning Message 3165 TLV lengths in the figure are given in decimal for easier 3166 understanding. Note that the padding after the middle List-Action 3167 TLV is counted as part of length of the Multicast-Service-Profile 3168 TLV, but is not included in the length of that List-Action TLV. Note 3169 also that the Length field in the message header, unlike those in the 3170 TLVs, includes the message header itself, as required by [RFC6320]. 3171 Finally, note that the Provisioning message does not include a 3172 MRepCtl-CAC TLV since in our example admission control for grey 3173 listed flows and for NAS-initiated replication is performed by the 3174 NAS. 3176 As soon as the AN port comes up, the AN sends an ANCP PORT_UP message 3177 to the NAS specifying the Access Loop Circuit ID. The NAS replies 3178 with an ANCP Port Management message that, together with the other 3179 parameters, includes the multicast service profile name to be 3180 associated to that port along with the initial amount of delegated 3181 bandwidth. The corresponding message flow is illustrated in Figure 3182 21. 3184 +----------+ +---------+ +-----+ +-----+ 3185 |Subscriber| | Home | | AN | | NAS | 3186 +----------+ | Gateway | +-----+ +-----+ 3187 | +---------+ | | 3188 | | | | 3189 | | | | 3190 | | DSL Synch. | | 3191 | |--------------------->| | 3192 | | |(M1)PORT_UP(Port ID) | 3193 | | |-------------------->| 3194 | | | (*) 3195 | | |(M2) PORT_MNGT | 3196 | | | (Port ID, | 3197 | | |Mcast S Profile Name,| 3198 | | |Bandwidth Allocation)| 3199 | | |<--------------------| 3201 (*) The NAS may optionally seek direction from an external 3202 Autorization/Policy Server 3204 Figure 21: Configuring an AN Port With Multicast Service Profile ID 3205 and Delegated Bandwidth Amount 3207 The Port Management message will typically contain other TLVs but our 3208 example (Figure 22) just shows the Target, Multicast-Service-Profile- 3209 Name, and Bandwidth-Allocation TLVs. The Target TLV identifies the 3210 subscriber line, the Multicast-Service-Profile-Name TLV is identical 3211 to the one contained in the Provisioning message, and the Bandwidth- 3212 Allocation TLV provides just enough bandwidth (2000 kbits/s) for one 3213 channel to start with. 3215 The following fields in the Port Management message header are shown 3216 with specific values either as directed by the base protocol document 3217 or for the sake of our example: 3219 o Message Type is 32. 3221 o Result is set to Nack (0x01) for this example. 3223 o Result Code is 0x000. 3225 o Port is set to 0. 3227 o Event Sequence Number, the R flag and the other bits marked x, 3228 Duration, the Event Flags, and the Flow Control Flags are all 3229 irrelevant for this function and are set to 0. 3231 o Function is set to 0x8, "Configure Connection Service Data". 3233 o X-Function is set to 0. 3235 o Tech Type is 0x05 (DSL). 3237 o Block lengths are calculated assuming a Circuit-Id length of 4 in 3238 our example. Recall that the example Multicast-Service-Profile- 3239 Name TLV length is 20. 3241 1 2 3 3242 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 3243 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3244 | Type (0x880C) | Length = 84 | 3245 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3246 | Version | Msg Type = 32 | 0x01 | Result Code = 0x000 | 3247 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3248 | Partition ID | Transaction Identifier | 3249 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3250 |I| SubMessage Number | Length = 84 | 3251 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3252 | Port = 0 | 3253 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3254 | Port Session Number | 3255 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3256 | Event Sequence Number = 0 | 3257 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3258 |R|x|x|x|x|x|x|x| Duration = 0 | Function = 0x8| X-Function = 0| 3259 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3260 | Event Flags | Flow Control Flags | 3261 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3262 |x|x|x|x|x|x|x|x| Msg Type = 32 |Tech Type=0x05 | Blk Len = 56 | 3263 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3264 | # of TLVs = 3 | Extension Block length = 44 | 3265 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3266 | Target TLV Type = 0x1000 | Target TLV Length = 8 | 3267 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3268 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3269 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3270 | Access Loop Circuit ID | 3271 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3272 | M-S-Prof-Name TLV Type = 0x18 | TLV Length = 20 | 3273 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3274 | Multicast service profile name | 3275 ~ = "Cust 0127-53681-0003" ~ 3276 | | 3277 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3278 | BW Alloc TLV Type = 0x15 | TLV Length = 4 | 3279 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3280 | Bandwidth value = 0x000007D0 (2000 kbits/s) | 3281 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3283 Figure 22: Example Port Management Message 3285 A.2. Handling a Grey-Listed Flow 3287 Suppose now that the subscriber chooses to watch the premium channel 3288 characterized by source 192.0.2.21, group 233.252.0.67. Upon 3289 receiving the Join request, the AN matches it against the multicast 3290 service profile for the port and determines that it is a grey-listed 3291 flow. Figure 23 illustrates the resulting ANCP message flow for the 3292 case of a simple join and leave, when admission control for grey- 3293 listed flows is not activated on the AN. 3295 To start the flow, the AN sends a Multicast Admission Control request 3296 (M1) to the NAS. The NAS decides whether flow can be admitted, 3297 applying both policy and bandwidth criteria. It returns its decision 3298 (positive in this example) in a Multicast Replication Control message 3299 (M2). Later, when the subscriber leaves the flow, the AN informs the 3300 NAS by sending another Multicast Admission Control message. 3302 +----------+ +-------+ +-----+ ANCP +-----+ 3303 |Subscriber| | Home | | AN |<---------->| NAS | 3304 +----------+ |Gateway| +-----+ +-----+ 3305 | +-------+ | | 3306 | | | Multicast | 3307 | Join(Grey-Fl) | Admission | 3308 |-----------+---------->| Control (M1) | 3309 | | |------------------>| 3310 | | | | (NAS performs 3311 | | | Multicast | admission 3312 | | | Replication (*) control) 3313 | | | Control (M2) | 3314 | Mcast Grey Flow |<------------------| 3315 |<======================+ | 3316 | | | | 3317 ~ ~ ~ ~ 3318 | | | Multicast | 3319 | Leave(Grey-Fl) | Admission | 3320 |-----------+---------->| Control (M3) | 3321 | | |------------------>| 3322 | | | | 3324 Grey-Fl : Multicast Flow matching an entry in grey List 3326 (*) The NAS may optionally seek direction from an external 3327 Authorization/Policy Server 3329 Figure 23: Successful Join/Leave Operations, Grey-Listed Flow 3331 The Multicast Admission Control message M1 contains: 3333 o an ANCP Header with: 3335 * Message-Type = 145 - Multicast Admission Control; 3336 * Result= 0x0 (Ignore); 3338 * Transaction-ID = Transaction-ID maintained by AN; 3340 o a Target TLV identifying the AN Port 3342 o a Command TLV containing: 3344 * Command Code = Add (1); 3346 * Accounting = 0; 3348 * a Multicast-Flow embedded TLV indicating the SSM multicast flow 3349 (Flow Type = 0x02) for which the AN received the IGMP Join: 3350 IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) Source 3351 Address = 192.0.2.21; 3353 * a Request-Source-IP embedded TLV containing the IGMP join 3354 source IP (192.0.2.100). 3356 The Multicast Admission Control message M1 is illustrated in Figure 3357 24: 3359 1 2 3 3360 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 3361 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3362 | Type (0x880C) | Length = 98 | 3363 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3364 | Version | Msg Type=145 | 0x0 | Result Code = 0x000 | 3365 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3366 | Partition ID | Transaction Identifier | 3367 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3368 |I| SubMessage Number | Length = 98 | 3369 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3370 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3371 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3372 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3373 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3374 | Access Loop Circuit ID | 3375 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3376 | Command TLV Type = 0x11 | TLV Length = 28 | 3377 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3378 | Cmd Code=0x01 |Acctg = 0x00 | Reserved = 0x0000 | 3379 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3380 |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | 3381 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3382 |Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | 3383 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3384 | Multicast Group Address = 233.252.0.67 | 3385 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3386 | Unicast Source Address = 192.0.2.21 | 3387 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 3388 | Req-Src-IP TLV Type = 0x92 | Embedded TLV length = 4 | 3389 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3390 | Unicast Address = 192.0.2.100 | 3391 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3393 Figure 24: Multicast Admission Control Message Seeking To Add A Flow 3395 The Multicast Replication Control message M2 contains: 3397 o an ANCP Header with: 3399 * Message Type = 144 - Multicast Replication Control; 3401 * Result= 0x1 (NAck); 3403 * Transaction-ID = Transaction-ID maintained by NAS; 3405 o a Target TLV identifying the AN Port; 3407 o a Command TLV containing: 3409 * Command Code = Add (1); 3411 * Accounting = 1 (begin flow accounting), since in our example 3412 the operator wants accounting on this flow. 3414 * a Multicast-Flow embedded TLV indicating the SSM multicast flow 3415 (Flow Type = 0x02) that the NAS is admitting for this access 3416 port: IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) 3417 Source Address = 192.0.2.21. 3419 The Multicast Admission Control message M2 is illustrated in Figure 3420 25. 3422 1 2 3 3423 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 3424 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3425 | Type (0x880C) | Length = 48 | 3426 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3427 | Version | Msg Type=144 | 0x1 | Result Code = 0x000 | 3428 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3429 | Partition ID | Transaction Identifier | 3430 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3431 |I| SubMessage Number | Length = 48 | 3432 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3433 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3434 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3435 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3436 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3437 | Access Loop Circuit ID | 3438 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3439 | Command TLV Type = 0x11 | TLV Length = 20 | 3440 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3441 | Cmd Code=0x01 | Acctg = 0x01 | Reserved = 0x0000 | 3442 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3443 |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | 3444 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3445 |Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | 3446 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3447 | Multicast Group Address = 233.252.0.67 | 3448 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3449 | Unicast Source Address = 192.0.2.21 | 3450 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3452 Figure 25: Multicast Replication Control Message Admitting A Flow 3454 The Multicast Admission Control message M3 advising the NAS that the 3455 flow has been terminated contains: 3457 o an ANCP Header with: 3459 * Message-Type = 145 - Multicast Admission Control 3461 * Result= 0x0 (Ignore) 3463 * Transaction-ID = Transaction-ID maintained by AN 3465 o a Target TLV identifying the AN Port 3467 o a Command TLV containing: 3469 * a Command Code = Delete (2); 3471 * Accounting = 0; 3473 * a Multicast-Flow embedded TLV indicating the SSM multicast flow 3474 (Flow Type = 0x02) for which the AN received the IGMP leave: 3475 IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) Source 3476 Address = 192.0.2.21. 3478 * a Request-Source-IP embedded TLV containing the IGMP leave 3479 request source, IPv4 (0x01) address 192.0.2.100. 3481 The Multicast Admission Control message M3 is illustrated in Figure 3482 26. 3484 1 2 3 3485 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 3486 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3487 | Type (0x880C) | Length | 3488 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3489 | Version | Msg Type=145 | 0x0 | Result Code = 0x000 | 3490 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3491 | Partition ID | Transaction Identifier | 3492 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3493 |I| SubMessage Number | Length | 3494 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3495 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3496 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3497 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3498 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3499 | Access Loop Circuit ID | 3500 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3501 | Command TLV Type = 0x11 | TLV Length = 28 | 3502 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3503 | Cmd Code=0x02 |Acctg = 0x00 | Reserved = 0x0000 | 3504 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3505 |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | 3506 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3507 |Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | 3508 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3509 | Multicast Group Address = 233.252.0.67 | 3510 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3511 | Unicast Source Address = 192.0.2.21 | 3512 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3513 | Req-Src-IP TLV Type = 0x92 | Embedded TLV length = 4 | 3514 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3515 | Unicast Address = 192.0.2.100 | 3516 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3518 Figure 26: Multicast Admission Control Message Signalling Flow 3519 Termination 3521 A.3. Handling White-Listed Flows 3523 The NAS has enabled white list admission control on the AN, and the 3524 bandwidth delegation capability has been negotiated. White listed 3525 flows in themselves require no messages to the NAS, either upon 3526 admission or upon termination, but the AN may request an increase in 3527 the amount of delegated bandwidth if it needs the increase to admit a 3528 flow. 3530 Consider an example where the AN has already admitted one white- 3531 listed flow, thereby using up the initially provisioned amount of 3532 delegated bandwidth (2000 kbits/s). A request is received to join a 3533 new flow in the white list range. The AN chooses to send a Bandwidth 3534 Reallocation Request message to the NAS, requesting that the 3535 delegated bandwidth allocation be increased to 4000 kbits/s at a 3536 minimum, and preferably to 6000 kbits/s. 3538 In our example, the NAS is managing bandwidth tightly, as witnessed 3539 by its minimal initial allocation of just enough for one flow. It is 3540 willing to provide the minimum additional amount only, and therefore 3541 returns a Bandwidth Transfer message where the delegated bandwidth 3542 value is given as 4000 kbits/s. With this amount, the AN is able to 3543 admit the second white-listed flow. The AN could send a similar 3544 Bandwidth Transfer message back to the NAS bringing the delegated 3545 bandwidth amount back down to 2000 kbits/s when one of the flows is 3546 terminated, but this shows nothing new and is omitted. 3548 As one more point of illustration, suppose that the NAS chooses to 3549 audit the current amount of delegated bandwidth to ensure it is 3550 synchronized with the AN. It sends a Delegated Bandwidth Query 3551 request message to the AN, and receives a Delegated Bandwidth Query 3552 response message with the current allocation as the AN sees it. 3554 The complete message flow is shown in Figure 27. 3556 +----------+ +-------+ +-----+ ANCP +-----+ 3557 |Subscriber| | Home | | AN |<---------->| NAS | 3558 +----------+ |Gateway| +-----+ +-----+ 3559 | +-------+ | | 3560 | | | | 3561 | Join(White-F1) | | 3562 |-----------+---------->| | 3563 | | |AN performs | 3564 | Mcast White Flow 1 | admission control | 3565 |<======================+ | 3566 | | | | 3567 | Join(White-F2) | | 3568 |-----------+---------->|No bandwidth left | 3569 | | | | 3570 | | |Bandwidth | 3571 | | | Reallocation Req | 3572 | | |------------------>|(M1) 3573 | | | | 3574 | | | (*) 3575 | | |Bandwidth Transfer | 3576 | AN can now |<------------------|(M2) 3577 | admit flow | | 3578 | Mcast White Flow 2 | | 3579 |<======================+ | 3580 | | | | 3581 ~ ~ ~ ~ 3582 | | |Delegated Bandwidth| 3583 | | | Query request | 3584 | | |<------------------|(M3) 3585 | | | | 3586 | | |Delegated Bandwidth| 3587 | | | Query response | 3588 | | |------------------>|(M4) 3589 | | | | 3591 (*) The NAS may optionally seek direction from an external 3592 Authorization/Policy Server 3594 Figure 27: Successful Join/Leave Operations, White-Listed Flow 3596 The Bandwidth Reallocation Request message (M1) is shown in Figure 3597 28. The contents require little explanation. The Message Type for 3598 the Bandwidth Reallocation Request is 146. The Result field is set 3599 to 0x0 (Ignore). Besides the Target, the message has one other TLV, 3600 the Bandwidth-Request, with a TLV Type of 0x16. The TLV contains 3601 Required Amount and Preferred Amount fields, set to 4000 and 6000 3602 kbits/s respectively. 3604 1 2 3 3605 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 3606 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3607 | Type (0x880C) | Length = 36 | 3608 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3609 | Version | Msg Type=146 | 0x0 | Result Code = 0x000 | 3610 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3611 | Partition ID | Transaction Identifier | 3612 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3613 |I| SubMessage Number | Length = 36 | 3614 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3615 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3616 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3617 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3618 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3619 | Access Loop Circuit ID | 3620 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3621 |Bandwidth-Req TLV Type = 0x16 | TLV Length = 8 | 3622 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3623 | Required Amount = 0x00000FA0 (4000 kbits/s) | 3624 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3625 | Preferred Amount = 0x00001770 (6000 kbits/s) | 3626 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3628 Figure 28: Bandwidth Reallocation Request Message 3630 The Bandwidth Transfer message (M2) is shown in Figure 29. Again, 3631 the contents are easily understood. The Message Type for the 3632 Bandwidth Transfer message is 147. The Result field is set to 3633 Success (0x3). The message contains the Target TLV and the 3634 Bandwidth-Allocation TLV. The latter has a TLV Type of 0x15 and 3635 contains a Delegated Amount field, set to 4000 kbits/s. 3637 1 2 3 3638 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 3639 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3640 | Type (0x880C) | Length = 32 | 3641 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3642 | Version | Msg Type=147 | 0x3 | Result Code = 0x000 | 3643 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3644 | Partition ID | Transaction Identifier | 3645 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3646 |I| SubMessage Number | Length = 32 | 3647 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3648 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3649 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3650 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3651 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3652 | Access Loop Circuit ID | 3653 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3654 |BW-Allocation TLV Type = 0x15 | TLV Length = 4 | 3655 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3656 | Delegated Amount = 0x00000FA0 (4000 kbits/s) | 3657 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3659 Figure 29: NAS Response, Bandwidth Transfer Message 3661 The Delegated Bandwidth Query request message (M3) is shown in Figure 3662 30. The Message Type for the Delegated Bandwidth Query request 3663 message is 148. The Result field is set to AckAll (0x2). The 3664 message contains the Target TLV only. 3666 1 2 3 3667 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 3668 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3669 | Type (0x880C) | Length = 24 | 3670 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3671 | Version | Msg Type=148 | 0x2 | Result Code = 0x000 | 3672 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3673 | Partition ID | Transaction Identifier | 3674 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3675 |I| SubMessage Number | Length = 24 | 3676 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3677 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3678 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3679 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3680 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3681 | Access Loop Circuit ID | 3682 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3684 Figure 30: Delegated Bandwidth Query Request Message 3686 Finally, the Delegated Bandwidth Query response message (M4) is shown 3687 in Figure 31. The Message Type for the Delegated Bandwidth Query 3688 response message is 148. The Result field is set to Success (0x3). 3689 The message contains the Target TLV and the Bandwidth-Allocation TLV 3690 with the Delegated Amount field set to 4000 kbits/s. 3692 1 2 3 3693 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 3694 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3695 | Type (0x880C) | Length = 32 | 3696 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3697 | Version | Msg Type=148 | 0x3 | Result Code = 0x000 | 3698 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3699 | Partition ID | Transaction Identifier (copied from request) | 3700 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3701 |I| SubMessage Number | Length = 32 | 3702 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3703 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3704 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3705 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3706 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3707 | Access Loop Circuit ID | 3708 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3709 |BW-Allocation TLV Type = 0x15 | TLV Length = 4 | 3710 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3711 | Delegated Amount = 0x00000FA0 (4000 kbits/s) | 3712 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3714 Figure 31: Delegated Bandwidth Query Response Message 3716 A.4. Handling Of Black-Listed Join Requests 3718 This section introduces no new messages, since requests for flows in 3719 the black list are simply ignored. The one thing to point out is the 3720 overlap in our example between the set of flows in the grey list and 3721 the flows in the black list. This does not create any ambiguity, 3722 since not only does the black list have priority for equally good 3723 matches, but also the black list entries are more specific (group 3724 prefix lengths of 32 versus 29 in the grey list) than the grey list 3725 flow prefixes. 3727 A.5. Handling Of Requests To Join and Leave the On-Line Game 3729 The final class of multicast control actions in our example allows 3730 the subscriber to enter and leave the on-line game. As described at 3731 the beginning of this example, the game uses Any Source Multicast 3732 (ASM). Subscriber signalling bypasses the AN, going directly to the 3733 NAS (e.g., through a web interface). 3735 When the subscriber requests to join the game, the NAS (after 3736 applying policy and bandwidth checks) sends a Multicast Replication 3737 Control message to the AN to enable the flow on the port concerned. 3738 The AN knows not to apply admission control, since it has not 3739 received an MRepCtl-CAC TLV in the Provisioning message. When the 3740 subscriber leaves, the NAS sends another Multicast Replication 3741 Control message to delete the flow. This message sequence is shown 3742 in Figure 32. 3744 It is possible that the NAS finds that there is not enough bandwidth 3745 available to accommodate the subscriber's request. In this case, the 3746 NAS could send a Bandwidth Reallocation Request message to the AN, 3747 asking it to release some of the bandwidth delegated to it. This is 3748 not shown in the present example, since the messages are the same as 3749 those already presented with the exception that the Preferred Amount 3750 in the request will be *less than* or equal to the Required amount, 3751 rather than *greater than* or equal to it. 3753 +----------+ +-------+ +-----+ ANCP +-----+ 3754 |Subscriber| | Home | | AN |<---------->| NAS | 3755 +----------+ |Gateway| +-----+ +-----+ 3756 | +-------+ | | 3757 | | | | 3758 | Join game | | 3759 |-----------+------------------------------>| 3760 | | | Multicast | NAS performs 3761 | | | Replication (*) admission 3762 | | | Control (M1) | control 3763 | Mcast Game Flow |<------------------| 3764 |<=====================>+ | 3765 | | | | 3766 ~ ~ ~ ~ 3767 | | | | 3768 | Leave game | | 3769 |-----------+------------------------------>| 3770 | | | Multicast | 3771 | | | Replication | 3772 | | | Control (M2) | 3773 | Mcast Game Flow |<------------------| 3774 | discontinued | | 3775 | | | | 3777 (*) The NAS may optionally seek direction from an external 3778 Authorization/Policy Server 3780 Figure 32: NAS-Initiated Flows For On-Line Gaming 3782 Multicast Replication Control message (M1) in Figure 33 looks like 3783 the message in Figure 25 with two exceptions. The first is that the 3784 NAS has the option to set the Result field to AckAll (0x02) if it 3785 needs positive reassurance that the flow has been enabled. This was 3786 not done here to save having to depict a response differing only in 3787 the Result field. The larger difference in this example is that the 3788 flow description in the Multicast-Flow embedded TLV is that of an ASM 3789 multicast group (Flow Type = 0x01) with IPv4 (0x01) group address 3790 233.252.1.100. 3792 1 2 3 3793 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 3794 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3795 | Type (0x880C) | Length = 44 | 3796 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3797 | Version | Msg Type=144 | 0x1 | Result Code = 0x000 | 3798 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3799 | Partition ID | Transaction Identifier | 3800 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3801 |I| SubMessage Number | Length = 44 | 3802 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3803 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3804 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3805 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3806 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3807 | Access Loop Circuit ID | 3808 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3809 | Command TLV Type = 0x11 | TLV Length = 16 | 3810 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3811 | Cmd Code=0x01 | Acctg = 0x01 | Reserved = 0x0000 | 3812 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3813 |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 8 | 3814 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3815 |Flow Type=0x01 |Addr Fam =0x01 | Reserved = 0x0000 | 3816 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3817 | Multicast Group Address = 233.252.1.100 | 3818 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 3820 Figure 33: Enabling The Subscriber To Join An On-Line Game 3822 Message M2 terminating the flow when the subscriber leaves the game 3823 looks the same as the message in Figure 33 with two exceptions: the 3824 Command Code becomes Delete (2), and Accounting is set to 0 to turn 3825 off flow accounting. Of course, the Transaction Identifier values 3826 will differ between the two messages. 3828 A.6. Example Flow For Multicast Flow Reporting 3830 The example in this section is independent of the example in the 3831 preceding sections. 3833 Figure 34 illustrates a message flow in a case where the NAS queries 3834 the AN about which multicast flows are active on port 10, on port 11 3835 and on port 20 of the AN. 3837 +----------+ +-------+ +-----+ ANCP +-----+ 3838 |Subscriber| | Home | | AN |<---------->| NAS | 3839 +----------+ |Gateway| +-----+ +-----+ 3840 | +-------+ | | 3841 | | | Multicast Flow | 3842 | | | Query Request | 3843 | | | (M1) | 3844 | | |<------------------| 3845 | | | | 3846 | | | Multicast Flow | 3847 | | | Query Response | 3848 | | | (M2) | 3849 | | |------------------>| 3850 | | | | 3851 | | | | 3853 Figure 34: Per-Port Multicast Flow Reporting 3855 The Multicast Flow Query Request message (M1) is illustrated in 3856 Figure 35. The Message Type is 149. The Result field is set to 3857 AckAll (0x2). Three Target TLVs are present, identifying port 10, 3858 port 20, and port 11 respectively. 3860 0 1 2 3 3861 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 3862 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3863 | Type (0x880C) | Length | 3864 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3865 | Version | Msg Type = 149|Rslt=2 | Result Code = 0 | 3866 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3867 | Partition ID | Transaction Identifier | 3868 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3869 |I| SubMessage Number | Length | 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 (port10) ~ 3877 | | 3878 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3879 | Type = 0x1000 (Target) | Target TLV Length | 3880 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3881 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | 3882 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3883 | | 3884 ~ Access Loop Circuit ID (port20) ~ 3885 | | 3886 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3887 | Type = 0x1000 (Target) | Target TLV Length | 3888 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3889 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | 3890 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3891 | | 3892 ~ Access Loop Circuit ID (port11) ~ 3893 | | 3894 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3896 Figure 35: Multicast Flow Query Request Message For Per-Port 3897 Multicast Flow Reporting 3899 The Multicast Flow Query Response message (M2) is illustrated in 3900 Figure 36. It indicates that there is one active multicast flow 3901 [(192.0.2.1, 233.252.2.4)] on port 10, no active multicast flow on 3902 port 20 and two active multicast flows [(192.0.2.1, 233.252.2.4) and 3903 (192.0.2.2, 233.252.2.10)] on port 11. 3905 0 1 2 3 3906 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 3907 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3908 | Type (0x880C) | Length | 3909 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3910 | Version | Msg Type = 149|Rslt=3 | Result Code = 0 | 3911 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3912 | Partition ID | Transaction Identifier | 3913 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3914 |I| SubMessage Number | Length | 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 (port10) ~ 3922 | | 3923 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3924 |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | 3925 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3926 |Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | 3927 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3928 | Multicast Group Address = 233.252.2.4 | 3929 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3930 | Unicast Source Address = 192.0.2.1 | 3931 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 3932 | Type = 0x1000 (Target) | Target TLV Length | 3933 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3934 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | 3935 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3936 | | 3937 ~ Access Loop Circuit ID (port20) ~ 3938 | | 3939 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3940 | Type = 0x1000 (Target) | Target TLV Length | 3941 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3942 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | 3943 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3944 | | 3945 ~ Access Loop Circuit ID (port11) ~ 3946 | | 3947 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3948 |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | 3949 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3950 |Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | 3951 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3952 | Multicast Group Address = 233.252.2.4 | 3953 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3954 | Unicast Source Address = 192.0.2.1 | 3955 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 3956 |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | 3957 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3958 |Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | 3959 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3960 | Multicast Group Address: 233.252.2.10 | 3961 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3962 | Unicast Source Address = 192.0.2.2 | 3963 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 3965 Figure 36: Multicast Flow Query Response message For Per-Port 3966 Multicast Flow Reporting 3968 Authors' Addresses 3970 Francois Le Faucheur 3971 Cisco Systems 3972 Greenside, 400 Avenue de Roumanille 3973 Sophia Antipolis 06410 3974 France 3976 Phone: +33 4 97 23 26 19 3977 Email: flefauch@cisco.com 3979 Roberta Maglione 3980 Cisco Systems 3981 181 Bay Street 3982 Toronto, ON M5J 2T3 3983 Canada 3985 Email: robmgl@cisco.com 3987 Tom Taylor 3988 Huawei Technologies 3989 Ottawa 3990 Canada 3992 Email: tom.taylor.stds@gmail.com