idnits 2.17.1 draft-ietf-ancp-mc-extensions-06.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 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 -- The document has examples using IPv4 documentation addresses according to RFC6890, but does not use any IPv6 documentation addresses. Maybe there should be IPv6 examples, too? 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 (December 5, 2011) is 4524 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 2920, 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: 0 errors (**), 0 flaws (~~), 5 warnings (==), 5 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: June 7, 2012 Telecom Italia 6 T. Taylor 7 Huawei 8 December 5, 2011 10 Multicast Control Extensions for ANCP 11 draft-ietf-ancp-mc-extensions-06.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 June 7, 2012. 50 Copyright Notice 52 Copyright (c) 2011 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 . . . . . . . . . . . . . . . . . . . . . . . . . 6 80 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 8 81 3. Multicast Use Cases . . . . . . . . . . . . . . . . . . . . . 9 82 3.1. NAS Initiated Multicast Replication Control Use Case . . . 9 83 3.1.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 9 84 3.1.2. Message Flow . . . . . . . . . . . . . . . . . . . . . 10 85 3.2. Conditional Access and Admission Control Use Case . . . . 10 86 3.2.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 10 87 3.2.2. Message Flow . . . . . . . . . . . . . . . . . . . . . 11 88 3.3. Multicast Flow Reporting Use Case . . . . . . . . . . . . 12 89 3.3.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 12 90 3.3.2. Message Flow . . . . . . . . . . . . . . . . . . . . . 12 91 3.4. Committed Bandwidth Reporting Use Case . . . . . . . . . . 13 92 3.4.1. Goals . . . . . . . . . . . . . . . . . . . . . . . . 13 93 3.4.2. Message Flow . . . . . . . . . . . . . . . . . . . . . 13 94 4. ANCP Messages . . . . . . . . . . . . . . . . . . . . . . . . 15 95 4.1. Provisioning Message . . . . . . . . . . . . . . . . . . . 15 96 4.1.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 15 97 4.1.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 16 98 4.2. Port Management Message . . . . . . . . . . . . . . . . . 17 99 4.2.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 18 100 4.2.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 18 101 4.3. Multicast Replication Control Message . . . . . . . . . . 19 102 4.3.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 23 103 4.3.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 23 104 4.4. Multicast Admission Control Message . . . . . . . . . . . 25 105 4.4.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 26 106 4.4.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 27 107 4.5. Bandwidth Reallocation Request Message . . . . . . . . . . 28 108 4.5.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 28 109 4.5.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 29 110 4.6. Bandwidth Transfer Message . . . . . . . . . . . . . . . . 31 111 4.6.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 32 112 4.6.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 32 113 4.7. Delegated Bandwidth Query Request Message . . . . . . . . 33 114 4.7.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 33 115 4.7.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 34 116 4.8. Delegated Bandwidth Query Response Message . . . . . . . . 34 117 4.8.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 34 118 4.8.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 34 119 4.9. Multicast Flow Query Request and Response Messages . . . . 35 120 4.9.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 36 121 4.9.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 36 122 4.10. Committed Bandwidth Report Message . . . . . . . . . . . . 38 123 4.10.1. Sender Behaviour . . . . . . . . . . . . . . . . . . . 38 124 4.10.2. Receiver Behaviour . . . . . . . . . . . . . . . . . . 38 126 5. ANCP TLVs For Multicast . . . . . . . . . . . . . . . . . . . 39 127 5.1. Multicast-Service-Profile TLV . . . . . . . . . . . . . . 39 128 5.2. Multicast-Service-Profile-Name TLV . . . . . . . . . . . . 40 129 5.3. List-Action TLV . . . . . . . . . . . . . . . . . . . . . 40 130 5.4. Sequence-Number TLV . . . . . . . . . . . . . . . . . . . 43 131 5.5. Bandwidth-Allocation TLV . . . . . . . . . . . . . . . . . 44 132 5.6. White-List-CAC TLV . . . . . . . . . . . . . . . . . . . . 44 133 5.7. MRepCtl-CAC TLV . . . . . . . . . . . . . . . . . . . . . 45 134 5.8. Bandwidth-Request TLV . . . . . . . . . . . . . . . . . . 45 135 5.9. Request-Source-IP TLV . . . . . . . . . . . . . . . . . . 46 136 5.10. Request-Source-MAC TLV . . . . . . . . . . . . . . . . . . 46 137 5.11. Multicast-Flow TLV . . . . . . . . . . . . . . . . . . . . 47 138 5.12. Report-Buffering-Time TLV . . . . . . . . . . . . . . . . 48 139 5.13. Committed-Bandwidth TLV . . . . . . . . . . . . . . . . . 49 140 6. Multicast Capabilities . . . . . . . . . . . . . . . . . . . . 50 141 6.1. Required Protocol Support . . . . . . . . . . . . . . . . 50 142 6.1.1. Protocol Requirements For NAS-initiated Replication . 51 143 6.1.2. Protocol Requirements For Committed Multicast 144 Bandwidth Reporting . . . . . . . . . . . . . . . . . 51 145 6.1.3. Protocol Requirements For Conditional Access With 146 White and Black Lists . . . . . . . . . . . . . . . . 52 147 6.1.4. Protocol Requirements For Conditional Access With 148 Grey Lists . . . . . . . . . . . . . . . . . . . . . . 53 149 6.1.5. Protocol Requirements For Delegated Bandwidth . . . . 54 150 6.2. Capability-Specific Procedures for Providing Multicast 151 Service . . . . . . . . . . . . . . . . . . . . . . . . . 55 152 6.2.1. Procedures For NAS-Initiated Replication . . . . . . . 55 153 6.2.2. Procedures For Committed Bandwidth Reporting . . . . 56 154 6.2.3. Procedures For Conditional Access With Black and 155 White Lists . . . . . . . . . . . . . . . . . . . . . 57 156 6.2.4. Procedures For Conditional Access With Grey Lists . . 59 157 6.2.5. Procedures For Delegated Bandwidth . . . . . . . . . . 60 158 6.3. Combinations of Multicast Capabilities . . . . . . . . . . 61 159 6.3.1. Combination of Conditional Access With White and 160 Black Lists and Conditional Access With Grey Lists . . 61 161 6.3.2. Combination of Conditional Access With Delegated 162 Bandwidth . . . . . . . . . . . . . . . . . . . . . . 62 163 6.3.3. Combination of NAS-Initiated Replication with 164 Other Capabilities . . . . . . . . . . . . . . . . . . 62 165 6.3.4. Combinations of Committed Bandwidth Reporting with 166 Other Multicast Capabilities . . . . . . . . . . . . . 63 167 7. Security Considerations . . . . . . . . . . . . . . . . . . . 64 168 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 65 169 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 69 170 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 70 171 10.1. Normative References . . . . . . . . . . . . . . . . . . . 70 172 10.2. Informative References . . . . . . . . . . . . . . . . . . 70 173 Appendix A. Example of Messages and Message Flows . . . . . . . . 72 174 A.1. Provisioning Phase . . . . . . . . . . . . . . . . . . . . 72 175 A.2. Handling a Grey-Listed Flow . . . . . . . . . . . . . . . 78 176 A.3. Handling White-Listed Flows . . . . . . . . . . . . . . . 83 177 A.4. Handling Of Black-Listed Join Requests . . . . . . . . . . 88 178 A.5. Handling Of Requests To Join and Leave the On-Line Game . 88 179 A.6. Example Flow For Multicast Flow Reporting . . . . . . . . 91 180 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 95 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 Section 256 3.4.3 of [RFC5851]. Because of this common content and because of 257 other protocol overlaps between the different capabilities, the 258 protocol descriptions for the multicast extensions specified in this 259 document are merged into a single non-redundant narrative. Tables in 260 Section 6 then indicate the specific sub-sections of the protocol 261 description that have to be implemented to support each capability. 263 2. Terminology 265 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 266 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 267 document are to be interpreted as described in [RFC2119]. 269 The expression "delegated bandwidth" is used as a shorter way of 270 saying: "the total amount of video bandwidth delegated to the AN for 271 multicast admission control". 273 3. Multicast Use Cases 275 Quoting from [RFC5851]: 277 "... the Access Node, aggregation node(s) and the NAS must all be 278 involved in the multicast replication process. This avoids that 279 several copies of the same stream are sent within the access/ 280 aggregation network. In case of an Ethernet-based access/aggregation 281 network, this may, for example, be achieved by means of IGMP snooping 282 or IGMP proxy in the Access Node and aggregation node(s). By 283 introducing IGMP processing in the access/aggregation nodes, the 284 multicast replication process is now divided between the NAS, the 285 aggregation node(s) and Access Nodes. In order to ensure backward 286 compatibility with the ATM-based model, the NAS, aggregation node and 287 Access Node need to behave as a single logical device. This logical 288 device must have exactly the same functionality as the NAS in the ATM 289 access/aggregation network. The Access Node Control Mechanism can be 290 used to make sure that this logical/functional equivalence is 291 achieved by exchanging the necessary information between the Access 292 Node and the NAS. " 294 [RFC5851] describes the use cases for ANCP associated with such 295 multicast operations, and identifies the associated ANCP 296 requirements. The present section describes a subset of these use 297 cases as background to facilitate reading of this document, but the 298 reader is refered to [RFC5851] for a more exhaustive description of 299 the ANCP multicast use cases. Detailed example message flows can 300 also be found in Appendix A. 302 3.1. NAS Initiated Multicast Replication Control Use Case 304 3.1.1. Goals 306 One option for multicast handling is for the subscriber to 307 communicate the "join/leave" information to the NAS. This can be 308 done for instance by terminating all subscriber IGMP ([RFC3376]) or 309 MLD ([RFC2710], [RFC3810]) signaling on the NAS. Another example 310 could be a subscriber using some form of application level signaling, 311 which is redirected to the NAS. In any case, this option is 312 transparent to the access and aggregation network. In this scenario, 313 the NAS uses ANCP to create and remove replication state in the AN 314 for efficient multicast replication. Thus, the NAS only sends a 315 single copy of the multicast stream towards the AN, which in turn 316 performs replication to multiple subscribers as instructed by the NAS 317 via ANCP. The NAS first performs conditional access and multicast 318 admission control when processing multicast join requests, and only 319 creates replication state in the AN if admission succeeds. 321 3.1.2. Message Flow 323 With the NAS-initiated use case, a Multicast Replication Control 324 Message is sent by the NAS to the AN with a directive to either join 325 or leave one (or more) multicast flow(s). In the example message 326 flow, the AN uses a Generic Response message to convey the outcome of 327 the directive. Figure 1 illustrates such an ANCP message exchange as 328 well as the associated AN behavior. 330 +----------+ +-------+ +-----+ ANCP +-----+ 331 |Subscriber| | Home | | AN |<-------------------->| NAS | 332 +----------+ |Gateway| +-----+ +-----+ 333 | +-------+ | | 334 | | | (*) 335 | | | Multicast-Replication-Crl | 336 | | | (Target,add, Flow 1) | 337 | | |<--------------------------| 338 | Mcast Flow 1 | | 339 |<==========================+ | 340 | | | Generic Response | 341 | | |-------------------------->| 342 | | | | 343 | | | | 344 ~ ~ ~ ~ 345 | | | | 346 | | | Multicast-Replication-Crl | 347 | | | (Target,delete, Flow 1) | 348 | | |<--------------------------| 349 | | | | 350 | | Generic Response | 352 | | |-------------------------->| 354 (*) The NAS may optionally seek direction from an external 355 Authorization/Policy Server before admitting the flow. 357 Figure 1: NAS Initiated Multicast Replication Control 359 3.2. Conditional Access and Admission Control Use Case 361 3.2.1. Goals 363 One option for multicast handling is for the access/aggregation nodes 364 to participate in IGMP/MLD processing (e.g. via IGMP/MLD snooping). 365 In this scenario, on detecting a join/leave request from an enduser 366 for a multicast flow (in the grey list), the AN uses ANCP to request 367 conditional access and admission control decision from the NAS. In 368 turn, after conditional access and admission control checks, the NAS 369 uses ANCP to instruct the AN to change the replication states 370 accordingly. 372 3.2.2. Message Flow 374 For support of the conditional access and admission control use case, 375 on detection of an IGMP/MLD Join, the AN sends an Admission Control 376 message to the NAS to request conditional access and admission 377 control check. In case of positive outcome, the NAS sends a 378 Multicast Replication Control Message to the AN with a directive to 379 replicate the multicast flow to the corresponding user. Similarly on 380 detection of an IGMP/MLD leave, an Admission Control message is sent 381 by the AN to the NAS to keep the NAS aware of user departure for the 382 flow. This message flow is illustrated in Figure 2. 384 +----------+ +-------+ +-----+ ANCP +-----+ 385 |Subscriber| | Home | | AN |<------------------->| NAS | 386 +----------+ |Gateway| +-----+ +-----+ 387 | +-------+ | | 388 | | | | 389 | Join(Gr-Flow1) | Admission-Control | 390 |------------+---------->| (Target,add,Gr-Flow1) | 391 | | |-------------------------->| 392 | | | (*) 393 | | | Multicast-Replication-Crl | 394 | | | (Target,add,Gr-Flow 1) | 395 | | |<--------------------------| 396 | Mcast Gr-Flow1 | | 397 |<=======================+ | 398 | | | | 399 ~ ~ ~ ~ 400 | | | | 401 | Leave(Gr-Flow1) | Admission-Control | 402 |------------+---------->| (Target,delete,Gr-Flow1) | 403 | | |-------------------------->| 404 | | | 406 | | | | 408 Gr-Flow1: a multicast flow matching the grey list for that port 410 (*) The NAS may optionally seek direction from an external 411 Authorization/Policy Server before admitting the flow. 413 Figure 2: Multicast Conditional Access and Admission Control 415 3.3. Multicast Flow Reporting Use Case 417 3.3.1. Goals 419 The Multicast flow reporting use case allows the NAS to 420 asynchronously query the AN to obtain an instantaneous status report 421 related to multicast flows currently replicated by the AN. 423 3.3.2. Message Flow 425 The NAS sends a Multicast Flow Query Request message to the AN in 426 order to query the AN about information such as which multicast flows 427 are currently active on a given AN port or which ports are currently 428 replicating a given multicast flow. The AN conveys the requested 429 information to the NAS in a Multicast Flow Query Response message. 430 This message flow is illustrated in Figure 3. 432 +----------+ +-------+ +-----+ ANCP +-----+ 433 |Subscriber| | Home | | AN |<---------->| NAS | 434 +----------+ |Gateway| +-----+ +-----+ 435 | +-------+ | | 436 | | | Multicast Flow | 437 | | | Query Request | 438 | | |<------------------| 439 | | | | 440 | | | Multicast Flow | 441 | | | Query Response | 442 | | |------------------>| 443 | | | | 444 | | | | 446 Figure 3: Multicast Flow Reporting 448 3.4. Committed Bandwidth Reporting Use Case 450 3.4.1. Goals 452 The committed bandwidth reporting use case allows the NAS to maintain 453 current awareness of how much multicast bandwidth the AN has 454 committed to a given access line, so that the NAS can adjust its 455 forwarding scheduler to ensure the associated QoS. Note that this 456 involves a finer level of detail than provided by bandwidth 457 delegation, since the amount of delegated bandwidth is an upper limit 458 on the amount of bandwidth committed rather than an actual value. To 459 reduce the volume of messaging, reports from the AN may be buffered 460 so that one message reports on changes for multiple access lines. 462 3.4.2. Message Flow 464 The message flow associated with this use case is shown in Figure 4. 465 The figure assumes that a non-zero buffering interval was previously 466 provisioned on the AN. 468 +-----+ +-------+ +-----+ ANCP +-----+ 469 |Subs |+ | Home |+ | AN |<---------->| NAS | 470 |1,2 || |GW 1,2 || +-----+ +-----+ 471 +-----+| +-------+| | | 472 +|----+ +|------+ | | 473 | | | | | | 474 | |Join(Subs1, Ch1) | | 475 |----------+--------------->| Start buffering | 476 | | | Multicast flow | timer. Create | 477 |<==========================| message with | 478 | | | | | initial contents | 479 | | | | | reporting new | 480 | | | | | Subs1 bandwidth. | 481 | | Join(Subs2, Ch2) | | 482 | |----------+------------->| Add report for | 483 | | | Multicast flow | new Subs2 b/w. | 484 | |<========================| | 485 | | | | | | 486 | |Leave(Subs1, Ch1) | | 487 |----------+--------------->| Replace report | 488 | | | | | for Subs1 with | 489 | | Stop replication X new value (which | 490 | | | | | happens to be | 491 | | | | | the same as the | 492 | | | | | starting value. | 493 | | | | | | 494 | | | | >|< TIMER expires | 495 | | | | | | 496 | | | | |Committed | 497 | | | | | Bandwidth Report | 498 | | | | |------------------>| 499 | | | | | (for latest | 500 | | | | | Subs1 and Subs2 | 501 | | | | | bandwidth) | 502 | | | | | | 504 Figure 4: Message Flow For Committed Bandwidth Reporting 506 4. ANCP Messages 508 This section defines new ANCP messages and new usage of existing ANCP 509 messages as well as procedures associated with the use of these 510 messages. 512 4.1. Provisioning Message 514 Section 4.1 of [RFC6320] defines the Provisioning message that is 515 sent by the NAS to the AN to provision information in the AN. 517 The present document specifies that the Provisioning message MAY be 518 used by the NAS to provision multicast-related information (e.g. 519 multicast service profiles). The ANCP Provisioning message payload 520 MAY contain: 522 o one or more instances of the Multicast-Service-Profile TLV. The 523 Multicast- Service-Profile TLV is defined in the present document 524 in Section 5.1. Each instance of the Multicast-Service-Profile 525 TLV contains a multicast service profile name and one or more list 526 actions. A list action consists of an action (add, delete, 527 replace), a list type (White, Black, or Grey), and list content 528 (multicast source and group addresses). 530 o an instance of the White-List-CAC TLV. The White-List-CAC TLV is 531 defined in Section 5.6. If present, this TLV indicates that the 532 AN is required to do admission control before replicating White- 533 listed flows. 535 o an instance of the MRepCtl-CAC TLV. The MRepCtl-CAC TLV is 536 defined in Section 5.7. If present, this TLV indicates that the 537 AN is required to do admission control before replicating flows 538 specified in Multicast Replication Control messages. 540 o an instance of the Report-Buffering-Time TLV. The Report- 541 Buffering-Time TLV is defined in Section 5.12. If present, this 542 TLV indicates Committed Bandwidth Report messages should be 543 buffered for the amount of time given by the TLV before being 544 transmitted to the NAS. 546 See Section 6 for information on which multicast capabilities require 547 support of these TLVs in the Provisioning message. 549 4.1.1. Sender Behaviour 551 When directed by the Policy Server or by management action, the NAS 552 sends the Provisioning message to initially provision or to update 553 the White, Black, and/or Grey multicast channel lists associated with 554 a set of named multicast service profiles, or to enable the AN to 555 perform admission control for specific classes of flows. 557 To provision or update a multicast service profile, the NAS MUST 558 include within the message one or more instances of the Multicast- 559 Service-Profile TLV specifying the content to be provisioned or 560 updated. The NAS SHOULD NOT include any list type (White, Black, or 561 Grey) that is not supported by the set of multicast capabilities 562 negotiated between the NAS and the AN. The NAS MUST NOT use the 563 Provisioning message to send instances of the Multicast-Service- 564 Profile TLV to the AN unless the Multicast-Service-Profile TLV is 565 supported by the set of multicast capabilities negotiated between the 566 NAS and the AN. 568 To require admission control to be performed at the AN on White- 569 listed flows, the NAS MUST include a copy of the White-List-CAC TLV 570 in the Provisioning message. The White-List-CAC TLV MUST NOT be 571 provided unless the negotiated set of capabilities includes 572 conditional access with White and Black lists. 574 To require admission control to be performed at the AN on Grey-listed 575 flows or on NAS-initiated flows, the NAS MUST include a copy of the 576 MRepCtl-CAC TLV in the Provisioning message. The MRepCtl-CAC TLV 577 MUST NOT be provided unless the negotiated set of capabilities 578 includes NAS-initiated replication control or conditional access with 579 Grey lists. 581 To require buffering of Committed Bandwidth Report messages so that 582 reports for multiple access lines can be included in the same 583 message, the NAS MUST include a copy of the Report-Buffering-Time TLV 584 containing a non-zero time value in a Provisioning message sent to 585 the AN. The Report-Buffering-Time TLV MUST NOT be provided unless 586 the negotiated set of capabilities includes committed bandwidth 587 reporting. 589 4.1.2. Receiver Behaviour 591 The receiving AN provisions/updates the White, Black, and/or Grey 592 lists associated with the multicast service profile names contained 593 in the Multicast-Service-Profile TLV instances within the message 594 according to the contents of the associated List-Action TLVs. The AN 595 MUST process List-Action TLVs in the order in which they appear 596 within the message. The AN MUST ignore instances of the List-Action 597 TLV referring to any list type (White, Black, or Grey) that is not 598 supported by the set of multicast capabilities negotiated between the 599 NAS and the AN. 601 When a new multicast service profile is identified by a Multicast- 602 Service-Profile TLV, the initial state of all lists associated with 603 that profile according to the negotiated set of multicast 604 capabilities is empty until changed by the contents of Multicast- 605 Service-Profile TLVs. 607 The receipt of a Provisioning message containing updates to an 608 existing multicast service profile subsequent to startup will cause 609 the AN to review the status of active flows on all ports to which 610 that profile has been assigned. For further details, see Section 6. 612 If the White-List-CAC and/or MRepCtl-CAC TLV is present in the 613 Provisioning message and the respective associated capabilities have 614 been negotiated, the AN prepares (or continues) to do connection 615 admission control on the indicated class(es) of flow. If one or both 616 of these TLVs was present in an earlier Provisioning message but is 617 absent in the latest message received, the AN ceases to do connection 618 admission control on the indicated class(es) of flow. 620 The buffering time specified in an instance of the Report-Buffering- 621 Time TLV applies to only to Committed Bandwidth Report messages 622 initiated after the new buffering time is received at the AN, not to 623 any message already in the process of accumulation. 625 As indicated in [RFC6320], the AN MUST NOT reply to the Provisioning 626 message if it processed it successfully. If an error prevents 627 successful processing of the message content, the AN MUST return a 628 Generic Response message as defined in [RFC6320], containing a 629 Status-Info TLV with the appropriate content describing the error. 630 For this purpose, the presence of a list type in a Multicast-Service- 631 Profile TLV which was ignored because it was not supported by the 632 negotiated set of capabilities is not considered to be an error. 634 4.2. Port Management Message 636 As specified in [RFC6320], the NAS may send DSL line configuration 637 information to the AN ("ANCP based DSL Line Configuration" use case) 638 using ANCP Port Management messages. See Section 7.3 of [RFC6320] 639 for the format of the Port Management message in that usage. 641 This document specifies that the Port Management message MAY be used 642 to convey either or both of the following TLVs: 644 o Multicast-Service-Profile-Name TLV (defined in Section 5.2). This 645 TLV associates a Multicast Service Profile with the Access Port 646 specified by the extension block. 648 o Bandwidth-Allocation TLV (defined in Section 5.5). This TLV 649 specifies the total multicast bandwidth available to the AN for 650 admission control at the Access Port. 652 When used for this purpose, the Port Management message MUST include 653 TLV(s) to identify the access line concerned. If the access line is 654 a DSL loop, the line-identifying TLV(s) MUST be as specified in 655 Section 5.1.2 of [RFC6320]. For non-DSL access lines, the 656 appropriate alternative line-identifying TLV(s) MUST be present. 657 Line configuration data other than the two TLVs listed in the 658 previous paragraph MAY be present. 660 4.2.1. Sender Behaviour 662 The NAS sends the Port Management message at startup time to 663 initialize parameters associated with the Access Port specified in 664 the message and with the multicast capabilities negotiated between 665 the NAS and the AN. The NAS MAY send additional Port Management 666 messages subsequent to startup, to update or, in the case of the 667 Bandwidth-Allocation TLV, reset these parameters. If the NAS 668 includes a Multicast-Service-Profile-Name TLV in the Port Management 669 message, the name MUST match a profile name provided in a Multicast- 670 Service-Profile TLV in a prior Provisioning message. The NAS MUST 671 NOT include a TLV unless it is supported by the set of multicast 672 capabilities negotiated between the NAS and the AN. See Section 6 673 for further information. 675 4.2.2. Receiver Behaviour 677 If the Port Management message contains a Multicast-Service-Profile- 678 Name TLV, the AN associates the named profile with the specified 679 Access Port. This association replaces any previous association. 680 That is, a given Access Port is associated with at most one multicast 681 service profile. The replacement of one multicast service profile 682 with another will cause the AN to review the status of all active 683 flows on the target port. For further details see Section 6. 685 If the Port Management message contains a Bandwidth-Allocation TLV, 686 the AN adopts this as the current value of its total multicast 687 bandwidth limit for the target port. If the AN has already committed 688 multicast bandwidth exceeding the amount given in the Bandwidth- 689 Allocation TLV, the AN SHOULD NOT discontinue any multicast streams 690 in order to bring bandwidth down to within the new limit. However, 691 the AN MUST NOT admit new multicast streams that are subject to 692 admission control until it can do so within the limit specified by 693 the Bandwidth-Allocation TLV. 695 If the Port Management request cannot be processed due to error and 696 the Result field of the request is Nack (0x1) or AckAll (0x2), the AN 697 SHOULD add a Status-Info TLV to the Extension Value field in its 698 reply if this will provide useful information beyond what is provided 699 by the Result Code value returned in the response header. In 700 particular, if the name within the Multicast-Service-Profile-Name TLV 701 does not match a profile name given in a prior Provisioning message, 702 the AN SHOULD return a reply where the Result Code field in the 703 header indicates "Invalid TLV value" (85), the Error Message field in 704 the Status-Info TLV contains the text "Multicast profile name not 705 provisioned", and the Status-Info TLV contains a copy of the 706 Multicast-Service-Profile-Name TLV. 708 4.3. Multicast Replication Control Message 710 This section defines a new message called the Multicast Replication 711 Control message. The Multicast Replication Control message is sent 712 by the NAS to the AN with one or more directives to add (join) or 713 delete (leave) a multicast flow on a target object identified in the 714 content of the message. 716 The Message Type for the Multicast Replication Control message is 717 144. 719 The ANCP Multicast Replication Control message payload contains the 720 following TLVs: 722 o Target TLV: The Target TLV is defined in Section 4.3 of [RFC6320]. 723 It MUST appear once and only once. It is encoded as specified in 724 [RFC6320] or extensions and identifies the AN port subject to the 725 request for admission or release. 727 o Command TLV: The Command TLV is defined in Section 4.4 of 728 [RFC6320]. It MUST be present. It MAY appear multiple times. 730 As [RFC6320] indicates, the contents of the Command Info field within 731 the Command TLV are specific to the message in which the TLV occurs. 732 For the Multicast Replication Control Message, these contents consist 733 of: 735 o a Command Code field; 737 o an Accounting field; 739 o an instance of the Multicast-Flow TLV. 741 Figure 5 illustrates the complete Command TLV with the contents 742 specific to the Multicast Replication Control message. 744 1 2 3 745 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 746 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 747 | TLV Type = Command | Command-TLV Length | 748 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 749 |Command Code | Accounting | Reserved | 750 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 751 | Multicast-Flow TLV | 752 | ... | 753 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 754 | Other embedded TLV Type | Other embedded TLV Length | 755 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 756 | | 757 ~ Other embedded TLV data ~ 758 | | 759 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 761 Figure 5: Contents of the Command TLV in the Multicast Replication 762 Control Message 764 Command Code: 765 Command directive: 767 0x01 - Add; 769 0x02 - Delete; 771 0x03 - Delete All; 773 0x04 - Admission Control Reject; 775 0x05 - Conditional Access Reject; 777 0x06 - Admission Control and Conditional Access 778 Reject. 780 Directives 0x04 through 0x06 are used as described in 781 Section 4.4.2 783 Accounting: 784 Meaningful only when the Command Code is "Add" (0x01). In 785 that case, 0x00 indicates no flow accounting, 0x01 786 indicates that octet accounting for the flow is to 787 commence. The Accounting field MUST be set to 0x00 for 788 other Command Code values. 790 Reserved: 791 Reserved for future use. MUST be set to 0x0000 by the 792 sender and ignored by the receiver. 794 Multicast-Flow TLV: 795 An instance of the Multicast-Flow TLV (Section 5.11) 796 specifying the flow to be added or deleted. The Multicast- 797 Flow TLV MUST be omitted if the Command Code has value 798 "Delete All" (0x03). 800 Other embedded TLV: 801 No other embedded TLVs are currently specified within the 802 Multicast Replication Control message/Command TLV. 803 Unrecognized embedded TLVs SHOULD be silently discarded. 805 The figure below is an example of a Multicast Replication Control 806 message that would result in a swap from multicast SSM flows 807 192.0.2.1, 233.252.0.2, to 192.0.2.2, 233.252.0.3 on the Target 808 identified by the "Access Loop Circuit ID": 810 1 2 3 811 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 812 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 813 | Type (0x88-0C) | Length | 814 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 815 | Vers | Sub |MessageType=144| 0x02 | Result Code | 816 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 817 | Partition ID | Transaction Identifier = 0001 | 818 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 819 |I| SubMessage Number | Length | 820 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 821 | Type = Target 0x1000 | Target TLV Length | 822 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 823 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | 824 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 825 | | 826 ~ Access Loop Circuit ID ~ 827 | | 828 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 829 | Type = Command TLV | Command-TLV Length = 0x0014 | 830 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 831 | Cmd Code=0x02 |Acctg = 0x00 | Reserved = 0x0000 | 832 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 833 |TLV Type = Multicast-Flow | TLV Length = 0x000C | 834 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 835 |Flow Type=0x02 |AddrFam = 0x01 | Reserved = 0x0000 | 836 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 837 | Multicast Group Address: 233.252.0.2 | 838 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 839 | Source Address = 192.0.2.1 | 840 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 841 | Type = Command-TLV | Command-TLV Length = 0x0014 | 842 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 843 | Cmd Code=0x01 |Acctg = 0x01 | Reserved = 0x0000 | 844 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 845 |TLV Type = Multicast-Flow | TLV Length = 0x000C | 846 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 847 |Flow Type=0x02 |AddrFam = 0x01 | Reserved = 0x0000 | 848 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 849 | Multicast Group Address = 233.252.0.3 | 850 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 851 | Source Address = 192.0.2.2 | 852 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 854 4.3.1. Sender Behaviour 856 The NAS MAY issue a Multicast Replication Control message to the AN 857 to convey one or more directives to add (join) or delete (leave) one 858 or more multicast flows. 860 The NAS MAY send this message on its own initiative to support the 861 NAS initiated Multicast Control use case presented in [RFC5851] and 862 summarized in Section 3.1. In that case, the NAS MUST set the Result 863 field to AckAll (0x2) or Nack (0x1) according to its requirements. 865 The NAS MAY also send this message in response to a Multicast 866 Admission Control message (defined in Section 4.4) received from the 867 AN to support the conditional access and admission control use case 868 presented in [RFC5851] and summarized in Section 3.2. In that case, 869 the NAS MUST set the Result field to NAck (0x1). 871 In either case, the sender MUST populate the Result Code field with 872 the value 0x000 and the ANCP Transaction Identifier field with a 873 unique value, as described in Section 3.6.1.6 of [RFC6320]. 875 Each Multicast Replication Control Message MUST contain one or more 876 commands, each encapsulated in its own Command TLV. The sender MUST 877 use a separate Command TLV for each distinct multicast flow. 879 When the order of processing of two commands does not matter, the 880 commands MUST be transmitted in separate Multicast Replication 881 Control messages. 883 4.3.2. Receiver Behaviour 885 When successive commands (in the same or different messages) relate 886 to the same Target and multicast flow, the state of each feature 887 controlled or affected by attributes received in the Multicast 888 Replication Control message, SHALL be as set by the last command or 889 message referring to that target and flow and containing the 890 controlling attribute. As an example, successive Multicast 891 Replication Control messages containing add commands for a given port 892 and flow, but differing only in the Accounting field setting SHALL be 893 interpreted to mean that the state of the accounting feature is as 894 set in the final command received, but all other features are as set 895 in the initial message. 897 If more than one Command TLV is present in a Multicast Replication 898 Control message, the AN MUST act on the commands in the order in 899 which they are presented in the message. The AN SHALL assign a 900 sequence number to each command in a given Multicast Replication 901 Control message, starting from 0x01 for the first command. 903 If a Command TLV adds a flow and the AN is performing admission 904 control for Multicast Replication Control messages, then the AN MUST 905 perform admission control before replicating the flow. If the 906 admission control check fails, the AN MUST treat the failure as an 907 error as described below. The appropriate Result Code value for the 908 response is 18 (0x012) "Insufficient resources". 910 If the AN processes the complete Multicast Replication Control 911 message successfully and the Result field of the Multicast 912 Replication Control message was set to AckAll (0x2), the AN MUST 913 respond with a Generic Response message where the Result field is set 914 to Success (0x3), the Result Code field is set to 0x000, and the 915 Transaction Identifier field is copied from the Multicast Replication 916 Control message. The body of the response MAY be empty or MAY be 917 copied from the Multicast Replication Control message. 919 If the AN processes the complete Multicast Replication Control 920 message successfully and the Result field of the Multicast 921 Replication Control message was set to Nack (0x1), the AN MUST NOT 922 respond to the message. 924 The processing/execution of multiple commands contained in a single 925 Multicast Control message MUST be interrupted at the first error 926 encountered, and the remaining commands in the Multicast Replication 927 Control message discarded. 929 If the AN detects an error in a received Multicast Replication 930 Control message and the Result field in that message was set to Nack 931 (0x1) or AckAll(0x2), the AN MUST generate a Generic Response message 932 providing error information to the NAS. This specification 933 identifies the following new Result Code values beyond those 934 specified in [RFC6320], which MAY be used in a Generic Response sent 935 in reply to a Multicast Replication Control message: 937 100 Command error. This SHOULD be reported for the case that an 938 invalid command code has been received. 940 101 Bad flow address. This SHOULD be reported for the following 941 cases: 943 * unsupported address family; 945 * source address present for an ASM flow, or absent for an SSM 946 flow. 948 102 Multicast flow does not exist. This SHOULD be reported if the 949 NAS attempts to delete a flow that is not enabled. 951 A Generic Response message responding to the Multicast Replication 952 Control message and containing one of the above Result Code values 953 MUST include a Status-Info TLV which includes one or two embedded 954 TLVs as follows: 956 o a Sequence-Number TLV as described in Section 5.4, giving the 957 sequence number of the failed command, MUST be included; 959 o the failed Command TLV itself SHOULD be included. 961 Note that the Error Message field of the Status-Info TLV MAY be 962 used to report more details than implied by the Result Code value 963 in the message header. For example, the Result Code value could 964 be 101 and the Error Message field could contain the text: "Source 965 address present for ASM flow". 967 4.4. Multicast Admission Control Message 969 This section defines a new message called the Multicast Admission 970 Control message. The Multicast Admission Control message is sent by 971 the AN to the NAS to request admission of a multicast flow, or to 972 notify of the removal of a multicast flow, for a given target. 974 The Message Type for the Multicast Admission Control message is 145. 976 The ANCP Multicast Admission Control message payload contains two 977 TLVs: 979 o Target TLV: The Target TLV is defined in [RFC6320]. It MUST 980 appear once and only once in the Multicast Admission Control 981 message. It is encoded as specified in [RFC6320] or extensions 982 and identifies the AN port subject to the request for admission or 983 release. 985 o Command TLV: The Command TLV is defined in [RFC6320]. It MUST be 986 present. If it appears more than once, only the first instance is 987 considered meaningful in the present version of this specification 988 and the other instances are ignored. 990 Informative note: 992 In the future, the specification of the Admission Control message 993 may be extended to allow transport of more than a single directive 994 (e.g. to carry both a leave from one group and a join to another 995 group for the same Target). It is expected that this would 996 support a similar notion of strict sequenced processing as 997 currently defined for handling multiple directives in the 998 Multicast Replication Control message whereby all directives 999 following the first directive that can not be executed are not 1000 executed either. When the strict sequenced processing of the 1001 directives is not required the directives are distributed across 1002 separate messages. 1004 The Command TLV has the same contents as were described above for the 1005 Multicast Replication Control message, with the following additions: 1007 o a Request-Source-IP TLV MAY be appended to the Command TLV as an 1008 additional embedded TLV; 1010 o similarly, a Request-Source-MAC TLV MAY be appended to the Command 1011 TLV as an additional embedded TLV. 1013 Note that the Command TLV length includes the length of any embedded 1014 TLVs, including the embedded TLV headers. 1016 4.4.1. Sender Behaviour 1018 The AN sending the Multicast Admission Control message MUST set the 1019 Result field to Ignore (0x0). 1021 The AN MUST populate the ANCP Transaction Identifier field with a 1022 unique value, as described in Section 3.6.1.6 of [RFC6320] . 1024 The AN MUST encode the Command TLV as specified in Section 4.3 with 1025 the following additional rules: 1027 o the Accounting field MUST be set to 0; 1029 o the Command Code field MUST be set to "0x01 - Add" when the 1030 message conveys a Join , to "0x02 - Delete" when the message 1031 conveys a Leave and to "0x03 - Delete All" when the message 1032 conveys a Leave of all channels (on the target); 1034 o The Multicast-Flow TLV within the Command TLV identifies the 1035 multicast flow subject to the request for admission or release. 1036 When the Command Code is 0x03, the Multicast-Flow TLV is 1037 meaningless and MUST be omitted. 1039 o the Request-Source-IP embedded TLV MAY be included by the AN to 1040 convey the IP address of the sender of the join/leave message 1041 (e.g. IGMP/MLD Join/Leave) that triggered the AN to include the 1042 corresponding Command TLV in the Admission Control message. If it 1043 appears more than once, only the first instance is considered 1044 meaningful and the other instances are ignored. 1046 o the Request-Source-MAC embedded TLV MAY be included by the AN to 1047 convey the MAC address of the sender of the join/leave message 1048 (e.g. IGMP/MLD Join/Leave) that triggered the AN to include the 1049 corresponding Command TLV in the Admission Control message. If it 1050 appears more than once, only the first instance is considered 1051 meaningful and the other instances are ignored. 1053 4.4.2. Receiver Behaviour 1055 On receipt of an Multicast Admission Control message, the NAS: 1057 o MUST ignore the Result field; 1059 o if the directive in the Multicast Admission Control message is 1060 "0x02 - Delete" or "0x03 - Delete All" and is processed correctly 1061 by the NAS, the NAS MUST NOT generate any ANCP message in response 1062 to the Multicast Admission Control message; 1064 o if the directive in the Multicast Admission Control message is 1065 "0x01 - Add" and is accepted by the NAS, the NAS MUST generate a 1066 Multicast Replication Control in response to the Multicast 1067 Admission Control message. The Multicast Replication Control 1068 message: 1070 * MUST contain a Result set to Nack (0x1); 1072 * MUST contain a Transaction ID generated by the NAS (distinct 1073 non-zero, and linearly incremented by NAS for each request per 1074 adjacency); 1076 * MUST contain the directive as accepted by the NAS. The NAS MAY 1077 modify the Accounting field if flow accounting is required. 1079 o if the directive in the Multicast Admission Control message is 1080 "0x01 - Add", is processed correctly but not accepted by the NAS 1081 (i.e. it does not pass the admission control or conditional access 1082 check), the NAS MAY generate a Multicast Replication Control 1083 message in response to the Multicast Admission Control message. 1084 This optional message can be used by the AN to maintain statistics 1085 about admission control rejections. 1087 In the future, the AN may be able to notify the subscriber that 1088 the request was rejected (e.g. using 1089 [I-D.morin-mboned-igmpmld-error-feedback]). 1091 When used in this situation, the Multicast Replication Control 1092 message: 1094 * MUST contain a Result set to 0x0; 1096 * MUST contain a Transaction ID generated by the NAS (distinct 1097 non-zero, and linearly incremented by NAS for each request per 1098 adjacency); 1100 * MUST contain the directive rejected by the NAS (i.e. Target 1101 TLV and Command TLV) but with a Command Code set to "0x04 - 1102 Admission Control Reject", "0x05 - Conditional Access Reject", 1103 or "0x06 - Admission Control and Conditional Access Reject". 1105 o if the Multicast Admission Control message cannot be processed 1106 correctly by the NAS (e.g. the message is malformed, the multicast 1107 flow does not exist etc.), the NAS MUST generate a Generic 1108 Response message (defined in Section 4.2 of [RFC6320]) with 1109 appropriate content indicating the reason for the failure. 1111 4.5. Bandwidth Reallocation Request Message 1113 The Bandwidth Reallocation Request message is used when the bandwidth 1114 delegation capability is included in the negotiated set. It MAY be 1115 sent either by the NAS or by the AN to request an adjustment in the 1116 amount of delegated bandwidth. It will be sent by the NAS typically 1117 to reduce the multicast bandwidth allocated to the AN in order for 1118 the NAS to satisfy a request to add one or more flows. Conversely, 1119 the AN will send a Bandwidth Reallocation Request to obtain 1120 additional bandwidth to satisfy a request to add a multicast channel. 1121 In each case, the requestor has a minimum requirement for additional 1122 bandwidth, and MAY ask for additional bandwidth beyond this amount 1123 (e.g., to handle anticipated future requests). 1125 The Bandwidth Reallocation Request message contains two TLVs: 1127 o the Target TLV (Section 4.3 of [RFC6320] or an extension), 1128 specifying a single access line; 1130 o the Bandwidth-Request TLV (Section 5.8), specifying the required 1131 and preferred amounts of delegated bandwidth. 1133 The Message Type for the Bandwidth Reallocation Request message is 1134 146. 1136 4.5.1. Sender Behaviour 1138 The Result field in the header of the Bandwidth Reallocation Request 1139 message is not used and the sender MUST set it to Ignore (0x0). 1141 The bandwidth values in the Bandwidth-Request TLV are expressed in 1142 terms of total multicast bandwidth allocated to the AN. 1144 The choice of "total bandwidth" rather than "incremental 1145 bandwidth" was made so that it would be easier for the AN and NAS 1146 to keep their respective views of the current amount of delegated 1147 bandwidth synchronized. 1149 Because the values are totals rather than desired increments/ 1150 decrements, the relationship between the required amount and the 1151 preferred amount will differ depending on whether the Bandwidth 1152 Reallocation Request message is issued by the NAS or the AN. 1154 o If the NAS is making the request, the preferred amount MUST be 1155 less than or equal to the required amount. The required amount 1156 MUST be less than the currently amount of delegated bandwidth. 1158 o If the AN is making the request, the preferred amount MUST be 1159 greater than or equal to the required amount. The required amount 1160 MUST be greater than the currently amount of delegated bandwidth. 1162 4.5.2. Receiver Behaviour 1164 When the peer receives a valid Bandwidth Reallocation Request 1165 message, it SHOULD determine whether it can satisfy the request from 1166 its existing allocation of unused video bandwidth. If it decides 1167 that it can reallocate bandwidth to the peer, it MAY choose to return 1168 any amount between the required and the preferred amounts indicated 1169 in the Bandwidth Reallocation Request message. 1171 The peer MUST return a Bandwidth Transfer message Section 4.6 1172 indicating its decision. If the request is met, the Result field of 1173 the Bandwidth Transfer message MUST be set to Success (0x3), the 1174 Result Code field MUST be set to 0x000, and the Bandwidth-Allocation 1175 TLV (Section 5.5) MUST contain the new value of total multicast 1176 bandwidth. This new value MUST lie between the required and 1177 preferred values, inclusive, from the request message. If the 1178 request is not met, the Result field of the Bandwidth Transfer 1179 message MUST be set to Failure (0x4), the Result Code field MUST be 1180 set to 0x000, and the Bandwidth Allocation TLV MUST contain the value 1181 of the currently allocated amount of delegated bandwidth as the 1182 responder views it. 1184 The following cases indicate that the sender holds a different view 1185 of the amount of delegated bandwidth from the receiver: 1187 o the NAS receives a request where the required amount is less than 1188 its view of the current amount of delegated bandwidth; 1190 o the AN receives a request where the required amount is greater 1191 than its view of the current amount of delegated bandwidth. 1193 If one of these cases occurs, the receiver with one exception MUST 1194 send a Bandwidth Transfer message indicating Success. 1196 o If the NAS received the request, the allocated amount in the NAS's 1197 response MUST be at least equal to NAS's view of the current 1198 amount of delegated bandwidth. 1200 o If the AN received the request, the allocated amount in the AN's 1201 response MUST be no greater than the AN's view of the current 1202 amount of delegated bandwidth. 1204 The exception is when the NAS receives a request while it has a 1205 request of its own outstanding. Handling of that case is described 1206 below. 1208 While the cases just described are an error condition, the success 1209 response achieves a graceful recovery. 1211 To avoid deadlock due to race conditions, the following rules MUST be 1212 applied: 1214 a. If the NAS receives a Bandwidth Reallocation Request message 1215 while it has a Bandwidth Reallocation Request message of its own 1216 outstanding for the same access line, the NAS MUST provide an 1217 immediate failure response to the request from the AN, with a 1218 Result Code value set to 105 "Bandwidth request conflict". 1220 b. If the AN receives a Bandwidth Reallocation Request message while 1221 it has a Bandwidth Reallocation Request message of its own 1222 outstanding for the same access line, the AN MUST release any 1223 bandwidth it has already committed to an outstanding Join request 1224 while it is awaiting a response from the NAS. It MUST decide 1225 upon and send its response to the NAS taking the released 1226 bandwidth into account. 1228 If the receiver is unable to process the Bandwidth Reallocation 1229 Request message due to an error, then the receiver MUST return a 1230 Bandwidth Transfer message where: 1232 o the Result field is set to Failure (0x4), 1234 o the Result Code field is set appropriately to indicate the type of 1235 error that was detected, 1237 o the Bandwidth Allocation TLV contains the value of the current 1238 amount of delegated bandwidth as the responder views it, and 1240 o a Status-Info TLV MAY follow the Bandwidth Allocation TLV giving 1241 further information about the error. 1243 This specification provides three new Result Code values applicable 1244 specifically to the contents of the Bandwidth-Request TLV. These 1245 Result Code values by their nature MUST only be used when the error 1246 is being reported in a Bandwidth Transfer message rather than a 1247 Generic Response message. 1249 103 invalid preferred bandwidth amount. This indicates that the 1250 preferred and required amounts of bandwidth in the TLV do not have 1251 the numerical relationship described in the previous section. 1253 104 inconsistent views of delegated bandwidth amount. This will 1254 appear only in a Bandwidth Transfer message from the NAS to the AN 1255 in the case where the NAS has an outstanding Bandwidth 1256 Reallocation Request. The recommended procedure for recovery is 1257 described in Section 4.6.2. 1259 105 bandwidth request conflict. The NAS has rejected the AN's 1260 request for more bandwidth because the NAS has an outstanding 1261 bandwidth request. 1263 4.6. Bandwidth Transfer Message 1265 The Bandwidth Transfer message is used to transfer video bandwidth 1266 from the sender to the peer for a specific access line. This message 1267 MAY be sent either from the AN or from the NAS. As described in the 1268 previous section, it is the required response to a valid Bandwidth 1269 Reallocation Request message. 1271 The Bandwidth Transfer message MAY also be used to transfer bandwidth 1272 autonomously from one peer to another. One example of this usage is 1273 to release bandwidth borrowed earlier by means of the Bandwidth 1274 Reallocation Request message. When the message is used in this way, 1275 the Result field in the Bandwidth Transfer message MUST be set to 1276 Ignore (0x0). 1278 This allows the receiver to distinguish between an autonomous 1279 transfer and a response to a previous Bandwidth Reallocation 1280 Request, for purposes of validation. 1282 The Message Type for the Bandwidth Transfer message is 147. The 1283 Bandwidth Transfer message contains the following TLVs: 1285 o the Target TLV, designating the access line concerned; 1287 o an instance of the Bandwidth-Allocation TLV (Section 5.5). The 1288 bandwidth value in the Bandwidth-Allocation TLV is the new amount 1289 of delegated bandwidth allocated to the target. 1291 4.6.1. Sender Behaviour 1293 When sending a Bandwidth Transfer message where the Result value is 1294 Ignore (0x0) or Success (0x3), the following relationships MUST hold: 1296 o if the message is sent by the NAS, the bandwidth value in the 1297 Bandwidth-Allocation TLV MUST be greater than or equal to the 1298 sender's view of the current amount of delegated bandwidth for the 1299 access line concerned; 1301 o if the message is sent by the AN, the bandwidth value in the 1302 Bandwidth-Allocation TLV MUST be less than or equal to the 1303 sender's view of the current amount of delegated bandwidth for the 1304 access line concerned. 1306 Further sender behaviour is specified above, in Section 4.5.2. 1308 4.6.2. Receiver Behaviour 1310 4.6.2.1. Behaviour of the NAS 1312 If the amount of delegated bandwidth provided in the Bandwidth- 1313 Allocation TLV is not greater than the NAS's view of the current 1314 amount of delegated bandwidth, the NAS MUST update its view of the 1315 current amount of delegated bandwidth to the amount indicated in the 1316 Bandwidth Transfer message. This is required regardless of whether 1317 the Result field of that message indicates Success or Failure. 1319 If the amount of delegated bandwidth provided in the Bandwidth- 1320 Allocation TLV is greater than the NAS's view of the current amount 1321 of delegated bandwidth, the NAS MAY accept the given value as its new 1322 value of delegated bandwidth. Alternatively, the NAS MAY force the 1323 AN to modify its view of the amount of delegated bandwidth to that 1324 held by the NAS, by sending a Port Management message for the target 1325 access line concerned, containing a Bandwidth-Allocation TLV with a 1326 value equal to the amount of delegated bandwidth the NAS wishes to 1327 enforce. 1329 4.6.2.2. Behaviour of the AN 1331 If the amount of delegated bandwidth provided in the Bandwidth- 1332 Allocation TLV of the Bandwidth Transfer message differs from the 1333 AN's view of the current amount of delegated bandwidth, the AN MUST 1334 update its view of the current amount of delegated bandwidth to the 1335 amount indicated in the Bandwidth Transfer message. This is required 1336 with the exception of a Bandwidth Transfer message with a Result 1337 field equal to Failure (0x4) and a Result Code field equal to 104 1338 "Inconsistent views of delegated bandwidth amount" or 105 "Bandwidth 1339 request conflict". If Result Code value 104 is received, the AN MUST 1340 issue a Delegated Bandwidth Query Request message to determine the 1341 NAS's current view of the amount of delegated bandwidth. The AN MUST 1342 update its own view based on the value returned in the Delegated 1343 Bandwidth Query Response. If Result Code value 105 is received, the 1344 AN SHOULD carry out this procedure unless it can account for the 1345 discrepancy as a result of a transfer of bandwidth to the NAS that 1346 was carried out just before the incoming Bandwidth Transfer message 1347 was processed. 1349 The two Result Code values indicate a race condition where the AN 1350 may have just completed a transfer of bandwidth to the NAS. As a 1351 result, the value given in the Bandwidth Transfer message may be 1352 outdated, and the AN needs to query the NAS to find its latest 1353 view. The procedure assumes that ordering is preserved between 1354 the Bandwidth Transfer message sent by the AN in response to the 1355 NAS's request and the subsequent Delegated Bandwidth Query Request 1356 message. 1358 If as the result of the procedures just described the AN determines 1359 that it has over-committed multicast bandwidth, it MUST NOT terminate 1360 any currently-active programs, but MUST NOT honour any more "join" 1361 requests until it is possible to do so within the limit set by its 1362 current value of delegated bandwidth. 1364 4.7. Delegated Bandwidth Query Request Message 1366 The Message Type for the Delegated Bandwidth Query Request (and 1367 Response) messages is 148. 1369 The Delegated Bandwidth Query Request message MAY be sent either by 1370 the NAS or by the AN to retrieve the peer's view of the amount of 1371 delegated bandwidth. The request contains one TLV: 1373 o a Target TLV designating the access line for which the information 1374 is requested. 1376 4.7.1. Sender Behaviour 1378 The sender MUST set the Result field in the header of the Delegated 1379 Bandwidth Query Request message to AckAll (0x2). The Result Code 1380 value MUST be set to 0x000. The sender MUST populate the ANCP 1381 Transaction Identifier field with a unique value, as described in 1382 Section 3.6.1.6 of [RFC6320]. 1384 4.7.2. Receiver Behaviour 1386 If the AN or NAS receives a valid Delegated Bandwidth Query Request 1387 message, it MUST respond with a Delegated Bandwidth Query Response 1388 message. The Result field in the header of the response MUST be set 1389 to Success (0x3). The Result Code field MUST be set to 0x000. The 1390 Transaction-Id field MUST be copied from the request message. The 1391 body of the response MUST contain the Target TLV, copied from the 1392 request message. Finally, the body of the response MUST contain a 1393 Bandwidth-Allocation TLV, containing the current amount of delegated 1394 bandwidth from the point of view of the receiver of the request. 1396 If the contents of the Delegated Bandwidth Query Request message are 1397 in error, the receiver MUST return a Delegated Bandwidth Query 1398 Response message with the Result field in the header set to Failure 1399 (0x3). The Result Code field MUST be set to the value that indicates 1400 the nature of the error (e.g., 4 "Unrecognized target"). The 1401 Transaction-Id field MUST be copied from the request. The body of 1402 the response MUST contain the Target TLV copied from the request. 1403 This MAY be followed by a Status-Info TLV giving further information 1404 about the error. 1406 4.8. Delegated Bandwidth Query Response Message 1408 The Delegated Bandwidth Query Response message is sent in reply to a 1409 Delegated Bandwidth Query Request. The response to a valid request 1410 contains two TLVs: 1412 o the Target TLV, copied from the request; 1414 o a Bandwidth-Allocation TLV, giving the responder's view of the 1415 current amount of multicast bandwidth delegated to the AN. 1417 The Message Type for the Delegated Bandwidth Query Response message 1418 is 148. 1420 4.8.1. Sender Behaviour 1422 Sender behaviour for the Delegated Bandwidth Query Response message 1423 is specified in Section 4.7.2. 1425 4.8.2. Receiver Behaviour 1427 If the Delegated Bandwidth Query Response message indicates Success 1428 (0x3), the following actions apply. 1430 4.8.2.1. Behaviour at the NAS 1432 If the amount of delegated bandwidth provided in the Bandwidth- 1433 Allocation TLV is less than the NAS's view of the current amount of 1434 delegated bandwidth, the NAS MUST update its view of the current 1435 amount of delegated bandwidth to the amount indicated in the 1436 Delegated Bandwidth Query Response message. 1438 If the amount of delegated bandwidth provided in the Bandwidth- 1439 Allocation TLV is greater than the NAS's view of the current amount 1440 of delegated bandwidth, the NAS MAY accept the given value as its new 1441 value of delegated bandwidth. Alternatively, the NAS MAY force the 1442 AN to modify its view of the amount of delegated bandwidth to that 1443 held by the NAS, by sending a Port Management message for the target 1444 access line concerned, containing a Bandwidth-Allocation TLV with a 1445 value equal to the amount of delegated bandwidth the NAS wishes to 1446 enforce. 1448 4.8.2.2. Behaviour at the AN 1450 The AN SHOULD accept the value returned in the Bandwidth-Allocation 1451 TLV of the Delegated Bandwidth Query Response message as the correct 1452 value of the current amount of delegated bandwidth. If the AN has 1453 currently committed more than this amount to active programs, it MUST 1454 NOT cease replicating the flows concerned, but MUST NOT honour any 1455 more Join requests until possible to do so within the new limit. 1457 A race condition is possible, where the AN sends a query, the NAS 1458 requests more bandwidth, then receives and responds to the query, 1459 then receives the Bandwidth Transfer message responding to its 1460 request. It is up to the AN to take appropriate action in this 1461 case. The best action appears to be not to act on the result of 1462 the first query, but to repeat the query after sending the 1463 Bandwidth Transfer message. Similar considerations apply to a 1464 race between queries from both sides. 1466 4.9. Multicast Flow Query Request and Response Messages 1468 This section defines two new messages called the Multicast Flow Query 1469 Request and Multicast Flow Query Response. The Multicast Flow Query 1470 Request is sent by the NAS to request information about the multicast 1471 flows that are active on the AN. The Multicast Flow Query Response 1472 is sent in response by the AN to provide the requested information to 1473 the NAS. 1475 The Message Type for the Multicast Flow Query Request and Multicast 1476 Flow Query Response messages is 149. 1478 The contents of the Multicast Flow Query Request and Response depend 1479 on the nature of the query, as described below. 1481 4.9.1. Sender Behaviour 1483 The sender of a Multicast Flow Query Request message MUST set the 1484 Result field to AckAll (0x2). The Result Code field MUST be set to 1485 0x000. The sender MUST populate the ANCP Transaction Identifier 1486 field with a unique value, as described in section 3.6.1.6 of 1487 [RFC6320]. 1489 The Multicast Flow Query Request MAY be used by the NAS to retrieve: 1491 o the AN's view of which multicast flows are currently active on a 1492 specified set of access ports; or 1494 o the AN's view of the access ports on which a specified set of 1495 multicast flows are currently active; or 1497 o the AN's view of all the multicast flows currently active on each 1498 and every port of the AN. 1500 To retrieve the AN's view of which multicast flows are currently 1501 active on a given port of the AN, the NAS MUST include a Target TLV 1502 in the Multicast Flow Query Request payload identifying that port. 1503 The Target TLV is encoded as specified in [RFC6320]. 1505 To retrieve the AN's view of the ports currently receiving a given 1506 multicast flow, the NAS MUST include a Multicast-Flow TLV in the 1507 Multicast Flow Query Request payload identifying that flow. The 1508 Multicast-Flow TLV is encoded as specified in Section 5.11. 1510 The NAS MAY include multiple Target TLVs or multiple Multicast-Flow 1511 TLVs in the Multicast Flow Query Request, but MUST NOT include both 1512 Target and Multicast-Flow TLVs in the same message. 1514 To retrieve the AN's view of all of the multicast flows currently 1515 active on each port of the AN, the NAS MUST send a Multicast Flow 1516 Query Request which does not contain any instance of the Target TLV 1517 or the Multicast-Flow TLV. 1519 4.9.2. Receiver Behaviour 1521 The AN MUST respond to a Multicast Flow Query Request message that 1522 has a valid format and a valid content with a Multicast Flow Query 1523 Response message. The Result field in the response MUST be set to 1524 Success (0x3). The Result Code field MUST be set to 0x000. The 1525 Transaction-Id field MUST be copied from the request. 1527 If the Multicast Flow Query Request contained one (or more) Target 1528 TLVs, the AN MUST include, for each of these Target TLVs, the 1529 following set of TLVs: 1531 o Target TLV. This MUST be identical to the Target TLV in the 1532 received Multicast Flow Query Request message. 1534 o Multicast-Flow TLV(s). The Multicast-Flow TLV MUST appear once 1535 per multicast flow that is currently active on the AN port 1536 identified in the preceding Target TLV. 1538 The Target TLVs MUST appear in the response from the AN in the same 1539 order as in the query from the NAS. 1541 If the Multicast Flow Query Request contained one (or more) 1542 Multicast-Flow TLVs, the AN MUST include, for each of these 1543 Multicast-Flow TLVs, the following set of TLVs: 1545 o Multicast-Flow TLV. This MUST be identical to the Multicast- Flow 1546 TLV in the received Multicast Flow Query Request message. 1548 o Target TLV(s). The Target TLV MUST appear once per AN port on 1549 which the multicast flow identified in the preceding Multicast 1550 Flow TLV is active. 1552 The Multicast-Flow TLVs MUST appear in the response from the AN in 1553 the same order as in the query from the NAS. 1555 If the Multicast Flow Query Request contained no Target TLV and no 1556 Multicast Flow TLV, the AN MUST include, for each AN port currently 1557 receiving multicast flow(s), the following set of TLVs: 1559 o Target TLV. This MUST identify one AN port. 1561 o Multicast-Flow TLV(s). The Multicast-Flow TLV MUST appear once 1562 per Multicast Flow that is currently active on the AN port 1563 identified in the preceding Target TLV. 1565 If the contents of the Multicast Flow Query Request are in error, the 1566 AN MUST reply with a Multicast Flow Query Response message with the 1567 Result field set to Failure (0x4) and the Result Code field set to 1568 indicate the nature of the error. If the request contained multiple 1569 instances of the Target TLV or the Multicast-Flow TLV and one of 1570 these is in error, the response message MUST contain the results for 1571 the preceding instances of the TLV as if there had been no error. 1572 These successful results MUST be followed by the TLV in error, copied 1573 from the request. The AN MUST NOT do further processing of the 1574 request. The AN MAY add a Status-Info TLV to provide further 1575 information on the nature of the error. 1577 4.10. Committed Bandwidth Report Message 1579 This section describes the Committed Bandwidth Report message, which 1580 is sent from the AN to the NAS to report the most recent amount of 1581 multicast bandwidth usage committed to one or more access lines. 1583 The Message Type for the Committed Bandwidth Report message is 150. 1585 The Committed Bandwidth Report message contains one or more instances 1586 of the Committed-Bandwidth TLV, as described in Section 5.13. 1588 4.10.1. Sender Behaviour 1590 The sender of a Committed Bandwidth Report message MUST set the 1591 Result field to Ignore (0x0). The Result Code field MUST be set to 1592 0x000. The sender MUST populate the ANCP Transaction Identifier 1593 field with a unique value, as described in section 3.6.1.6 of 1594 [RFC6320]. 1596 Each instance of the Committed-Bandwidth TLV included in the message 1597 MUST identify an access line for which the amount of committed 1598 multicast bandwidth has changed since the previous Committed 1599 Bandwidth Report message was sent and MUST report the latest amount 1600 of multicast bandwidth committed to that line. There MUST be only 1601 one instance of the Committed-Bandwidth TLV present in the message 1602 for any given access line. The message MUST include an instance of 1603 the Committed-Bandwidth TLV for every access line for which committed 1604 multicast bandwidth has changed since the previous Committed 1605 Bandwidth Report message was sent. 1607 Further behaviour at the AN is specified in Section 6.2.2. 1609 4.10.2. Receiver Behaviour 1611 The usage of the contents of a Committed Bandwidth Report message 1612 received by the NAS is implementation-dependent. One example is that 1613 the NAS uses the reports of multicast bandwidth commitments to adjust 1614 its forwarding scheduler operation to provide the intended level of 1615 QoS. 1617 The NAS MUST NOT reply to a valid Committed Bandwidth Report message. 1618 The NAS MAY send a Generic Response message indicating the nature of 1619 any errors detected in a Committed Bandwidth Report message that it 1620 has received. 1622 5. ANCP TLVs For Multicast 1624 This section defines new ANCP TLVs for the control of multicast 1625 flows. 1627 5.1. Multicast-Service-Profile TLV 1629 This document defines the new Multicast-Service-Profile TLV. 1631 The Multicast-Service-Profile TLV MAY be included in a Provisioning 1632 message as specified in Section 4.1. 1634 The Multicast-Service-Profile TLV is illustrated in Figure 6. It 1635 consists of a TLV header encapsulating a single instance of the 1636 Multicast-Service- Profile-Name TLV and one or more instances of the 1637 List-Action TLV. 1639 1 2 3 1640 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 1641 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1642 |TLV Type = Mcast Serv Profile | TLV Length | 1643 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1644 | Multicast-Service-Profile-Name TLV | 1645 | | 1646 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1647 | List-Action TLV | 1648 | | 1649 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1650 | ... | 1651 | | 1652 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1653 | List-Action TLV | 1654 | | 1655 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1657 Figure 6: Multicast-Service-Profile TLV 1659 The Multicast-Service-Profile TLV has the following fields: 1661 o The Multicast-Service-Profile TLV Type is 0x13. 1663 o The TLV length is determined by the contents following the TLV 1664 header. 1666 o The Multicast-Service-Profile-Name TLV is described in 1667 Section 5.2. The Multicast-Service-Profile-Name TLV MUST contain 1668 an identifier which is unique over all profiles provisioned to the 1669 same AN partition. This identifier will be used to refer to the 1670 profile when activating it for a given target within a Port 1671 Management message (see Section 4.2). 1673 o The List-Action TLV is described in Section 5.3. The List-Action 1674 TLV(s) provide the content of a newly defined multicast service 1675 profile or modify the existing content. If more than one List- 1676 Action TLV is present, the order of the TLVs may be significant, 1677 since List- Action TLVs are processed in the order in whch they 1678 appear. 1680 5.2. Multicast-Service-Profile-Name TLV 1682 The Multicast-Service-Profile-Name TLV carries the identifier of a 1683 multicast service profile provisioned on the AN. It is illustrated 1684 in Figure 7. 1686 1 2 3 1687 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 1688 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1689 |TLV Type = MSP Name | TLV Length | 1690 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1691 | Multicast service profile identifier | 1692 | | 1693 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1695 Figure 7: Multicast-Service-Profile-Name TLV 1697 The Multicast-Service-Profile-Name TLV has the following fields: 1699 o The Multicast-Service-Profile-Name TLV Type is 0x18. 1701 o TLV Length: up to 255 octets. 1703 o Multicast service profile identifier: an opaque sequence of bits 1704 identifying a specific multicast service profile. 1706 The identifier could have the form of human-readable text or an 1707 arbitrary binary value, depending on the operator's practices. 1709 5.3. List-Action TLV 1711 The List-Action TLV identifies multicast flows to be added to or 1712 removed from a list of White-, Black-, or Grey-listed flows. It is 1713 meaningful only in association with a Multicast-Service-Profile-Name 1714 TLV identifying the profile to which the List-Action TLV applies. 1715 Such an association can be achieved by placing both TLVs in the same 1716 base message payload or as embedded TLVs of another TLV such as the 1717 Multicast-Service-Profile. The List-Action TLV is shown in Figure 8. 1719 1 2 3 1720 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 1721 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1722 | TLV Type = List-Action TLV | TLV Length | 1723 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1724 | Operation | List Type | Reserved | 1725 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1726 | Address Family | Number of flow fields | 1727 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1728 | Multicast flow fields | 1729 ...... 1730 | | 1731 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1732 | Address Family | Number of flow fields | 1733 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1734 | Multicast flow fields | 1735 ...... 1736 | | 1737 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1739 Figure 8: List-Action TLV 1741 The List-Action TLV contains the following fields: 1743 o The List-Action TLV Type is 0x21. 1745 o TLV Length: length of the subsequent contents. 1747 o Operation: operation to be performed upon the White, Black, or 1748 Grey list identified by the List Type field within the profile 1749 identified by the associated Multicast-Service-Profile-Name 1750 embedded TLV. The possible values are: 1752 * Add (0x01): the multicast flow fields are to be added to the 1753 list. 1755 * Delete (0x02): the multicast flow fields are to be removed from 1756 the list. Each multicast flow field in the List-Action MUST 1757 match exactly an existing entry in the list concerned. Thus to 1758 remove part of the range provided by a wildcarded list entry, 1759 it is necessary to remove the entire entry and add back the 1760 remaining partial range(s). 1762 * Replace (0x03): the multicast flow fields replace the existing 1763 contents of the list. 1765 o List Type: the list type being modified by this List-Action. The 1766 possible values are White (0x01), Black (0x02), or Grey (0x03). 1768 o Reserved: a sender MUST set this field to 0x0000. A receiver MUST 1769 ignore the contents of this field. 1771 o Address Family: the IP version of the set of multicast flow fields 1772 that follow, encoded according to [PIMreg]. Possible values are 1773 0x0001 (IPv4) or 0x0002 (IPv6). Either an IPv4 list or an IPv6 1774 list or both MAY be present in the List-Action TLV. 1776 o Number of flow fields: the number of multicast flow fields of the 1777 given address family which follow. 1779 o Multicast flow field: a field identifying one or more multicast 1780 flows. It consists of an 8-bit group address prefix length, an 1781 8-bit source address prefix length, a 0-16 octet group prefix, and 1782 a 0-16 octet source prefix, as shown in Figure 9. 1784 Each multicast flow field refers either to a Source-Specific 1785 Multicast (SSM) channel or to an Any Source Multicast (ASM) group. 1786 The scope of the designation may be broadened to multiple channels or 1787 groups through use of prefix length values smaller than the total 1788 address length for the given address family. Multicast flow fields 1789 MUST be placed consecutively within the embedded TLV without 1790 intervening padding except to round out individual addresses to the 1791 nearest octet boundary. 1793 A multicast flow field consists of two single-octet prefix lengths 1794 followed by zero to two prefix values as shown in Figure 9: 1796 +-+-+-+-+-+-+-+-+ 1797 | Group PrefLen | 1798 +-+-+-+-+-+-+-+-+ 1799 | Source PrefLen| 1800 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1801 | Group Prefix (multicast) (0 to 16 octets) | 1802 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1803 | Source Prefix (unicast, SSM only) (0 to 16 octets) | 1804 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1806 Figure 9: Organization of a Single Multicast Flow Field 1808 The prefix length has its usual meaning. It is the number of most- 1809 significant bits specified within the corresponding prefix. The 1810 prefix length MAY vary from 0 to 32 in the IPv4 sub-list, and from 0 1811 to 128 in the IPv6 sub-list. 1813 A value of 0x00 for either the Group PrefLen (prefix length) or the 1814 Source PrefLen indicates that any value of the corresponding address 1815 will match (wild card). If the value 0x00 is provided for a 1816 particular prefix length, the corresponding prefix MUST be omitted 1817 from the field contents. In particular, a value of 0x00 for the 1818 Source PrefLen indicates an ASM multicast entry, and the Source 1819 Prefix will be absent. 1821 The length of a Source or Group Prefix field is equal to (PrefLen + 1822 7)/8 octets, truncated to the nearest integer. Unused bits at the 1823 end of the prefix MUST be set to zeroes. 1825 5.4. Sequence-Number TLV 1827 The Sequence-Number TLV conveys a sequence number of some sort. The 1828 specific meaning of the sequence number is message-specific. Within 1829 this specification, the Sequence-Number TLV is used as a embedded TLV 1830 within a Status-Info TLV, in a Generic Response reporting a failed 1831 command within a Multicast Replication Control or Multicast Admission 1832 Request message. It identifies the sequence number within the 1833 message of the command that failed. 1835 The Sequence-Number TLV has the format shown in Figure 10. 1837 1 2 3 1838 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 1839 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1840 |TLV Type = Sequence-Number | TLV Length = 4 | 1841 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1842 | Sequence number | 1843 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1845 Figure 10: Sequence-Number TLV 1847 The Sequence-Number TLV has the following fields: 1849 o The Sequence-Number TLV Type is 0x22. 1851 o TLV length is 0x0004. 1853 o Sequence number: the sequence number of a specific entity within a 1854 series, where numbering starts from 1 for the first entity in the 1855 series. Represented as a 32-bit binary number, most significant 1856 bit first. 1858 5.5. Bandwidth-Allocation TLV 1860 The Bandwidth-Allocation TLV is used to indicate the total amount of 1861 video bandwidth delegated to the AN for multicast admission control 1862 for a given access line, in kilobits per second. The TLV has the 1863 format shown in Figure 11. 1865 1 2 3 1866 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 1867 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1868 |TLV Type = BW-Allocation | TLV Length = 4 | 1869 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1870 | Delegated amount (kbits/s) | 1871 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1873 Figure 11: The Bandwidth-Allocation TLV 1875 The Bandwidth-Allocation TLV has the following fields: 1877 o The Bandwidth-Allocation TLV Type is 0x15. 1879 o TLV length is 4. 1881 o Delegated amount: the bandwidth amount delegated to the AN for 1882 admission of multicast video on a given port, kilobits per second. 1883 Presented as a 32-bit binary value, most significant bit first. 1885 5.6. White-List-CAC TLV 1887 The White-List-CAC TLV is used to indicate that the NAS wishes the AN 1888 to do admission control for White-listed flows. Details on when the 1889 White-List-CAC TLV may be provisioned are specified in Section 6. 1890 The White- List-CAC TLV is illustrated in Figure 12. 1892 1 2 3 1893 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 1894 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1895 |TLV Type = White-List-CAC | TLV Length = 0 | 1896 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1898 Figure 12: White-List-CAC TLV 1900 The White-List-CAC TLV contains the following fields: 1902 o The White-List-CAC TLV Type is 0x24. 1904 o TLV length is 0, since the TLV contains no data other than the TLV 1905 header. 1907 5.7. MRepCtl-CAC TLV 1909 The MRepCtl-CAC TLV is used to indicate that the NAS wishes the AN to 1910 do admission control for flows added by the Multicast Replication 1911 Control message. Details on when the MRepCtl-CAC TLV may be 1912 provisioned are specified in Section 6. The MRepCtl-CAC TLV is 1913 illustrated in Figure 13. 1915 1 2 3 1916 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 1917 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1918 |TLV Type = MRepCtl-CAC | TLV Length = 0 | 1919 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1921 Figure 13: MRepCtl-CAC TLV 1923 The MRepCtl-CAC TLV contains the following fields: 1925 o The MRepCtl-CAC TLV Type is 0x25. 1927 o TLV length is 0, since the TLV contains no data other than the TLV 1928 header. 1930 5.8. Bandwidth-Request TLV 1932 The Bandwidth-Request TLV is used to request an adjustment of the 1933 total amount of video bandwidth allocated to the AN for multicast 1934 admission control for a given line. The "Required amount" field 1935 indicates the minimum adjustment required to meet the request. The 1936 "Preferred amount" field indicates the adjustment the requestor would 1937 prefer to have, if possible. Section 4.5 discusses the required 1938 relationships between the "Required amount", "Preferred amount", and 1939 current values of total bandwidth allocated to the AN. 1941 The Bandwidth-Request TLV has the format shown in Figure 14. 1943 1 2 3 1944 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 1945 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1946 |TLV Type = Bandwidth-Request | TLV Length = 8 | 1947 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1948 | Required amount (kbits/s) | 1949 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1950 | Preferred amount (kbits/s) | 1951 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1953 Figure 14: The Bandwidth-Request TLV 1955 The Bandwidth-Request TLV has the following fields: 1957 o The Bandwidth-Request TLV Type is 0x16. 1959 o The TLV length is 8 octets. 1961 o Required amount: the minimum or maximum amount, depending on 1962 whether the sender is the AN or the NAS respectively, of delegated 1963 video bandwidth that is being requested, in kilobits per second. 1964 Presented as a 32-bit binary value, most significant bit first. 1966 o Preferred amount: the preferred amount of delegated video 1967 bandwidth that is being requested, in kilobits per second. 1968 Presented as a 32-bit binary value, most significant bit first. 1970 5.9. Request-Source-IP TLV 1972 The Request-Source-IP TLV provides the IP address of the entity that 1973 originated a specific request to join or leave a multicast channel. 1974 The TLV is illustrated in Figure 15. 1976 1 2 3 1977 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 1978 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1979 | TLV Type = Request-Source-IP | TLV length = 4 or 16 | 1980 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1981 | Unicast Address | 1982 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1984 Figure 15: Request-Source-IP TLV 1986 The Request-Source-IP TLV contains the following fields: 1988 o The Request-Source-IP TLV Type is 0x92. 1990 o TLV length is 4 for an IPv4 address or 16 for an IPv6 address. 1992 o Unicast address: IP address of the source of a multicast flow join 1993 request, in network byte order. 1995 5.10. Request-Source-MAC TLV 1997 The Request-Source-MAC TLV provides the MAC address of the entity 1998 that originated a specific request to join or leave a multicast 1999 channel. The TLV is illustrated in Figure 16. 2001 1 2 3 2002 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 2003 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2004 |TLV Type=Request-Source-MAC | TLV Length = 6 or 8 | 2005 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2006 | | 2007 +-+-+- IEEE MAC Address +-+-+-+ 2008 | | 2009 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2011 Figure 16: Request-Source-MAC TLV 2013 The Request-Source-MAC TLV contains the following fields: 2015 o The Request-Source-MAC TLV Type is 0x93. 2017 o TLV length is either 6 octets (MAC-48 or EUI-48) or 8 octets 2018 (EUI-64). 2020 o IEEE MAC Address: MAC address of the device originating the 2021 request to join a multicast flow. Within the address, bytes and 2022 bits respectively shall be ordered from most to least significant, 2023 consistently with [IEEE48] for MAC-48 and EUI-48, and with 2024 [IEEE64] for EUI-64. 2026 EUI-48 and EUI-64 are registered trademarks of the IEEE. 2028 5.11. Multicast-Flow TLV 2030 The Multicast-Flow TLV specifies a multicast flow in terms of its 2031 multicast group address and, if applicable, its unicast source 2032 address. It is illustrated in Figure 17. 2034 1 2 3 2035 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 2036 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2037 |TLV Type = Multicast-Flow | TLV Length | 2038 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2039 | Flow Type | Addr Family | Reserved | 2040 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2041 | Multicast Group Address | 2042 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 2043 | Unicast Source Address (for SSM flows only) | 2044 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2046 Figure 17: Multicast-Flow TLV 2048 The Multicast-Flow TLV has the following fields: 2050 o The Multicast-Flow TLV Type is 0x19. 2052 o TLV Length: ranges from a minimum of 8 (for an ASM IPv4 flow) to 2053 36 (for an IPv6 SSM flow. 2055 o Flow Type: 0x01 for Any Source Multicast (ASM), 0x02 for Specific- 2056 Source Multicast (SSM). 2058 o Addr Family: address family of the multicast source and group 2059 addresses, encoded in accordance with the IANA PIM Address Family 2060 registry ([PIMreg]). 0x01 indicates IPv4, 0x02 indicates IPv6. 2062 o Reserved: MUST be set to 0x0000 by the sender and MUST be ignored 2063 by the receiver. 2065 One possible use for this field in the future is to indicate 2066 the presence of PIM Join attributes attached to the source 2067 address (see [RFC5384]). The applicability of PIM attributes 2068 in the context of ANCP is for further study. 2070 o Multicast Group Address: a multicast group address within the 2071 given address family. The group address MUST always be present. 2073 o Unicast Source Address: unicast address within the given address 2074 family. If the Flow Type is 0x01 (ASM), a source address MUST NOT 2075 be present. If the Flow Type is 0x02 (SSM), a source address MUST 2076 be present. 2078 5.12. Report-Buffering-Time TLV 2080 The Report-Buffering-Time TLV provides the time for which a Committed 2081 Bandwidth Report message must be held with the intention of 2082 accumulating multiple reports of changed committed multicast 2083 bandwidth in one report, to reduce the volume of messages sent to the 2084 NAS. For further information see Section 6.2.2. The TLV is 2085 illustrated in Figure 18. 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=Report-Buffering-Time | TLV Length = 4 | 2091 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2092 | Buffering Time (ms) | 2093 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2095 Figure 18: Report-Buffering-Time TLV 2097 The Report-Buffering-Time TLV contains the following fields: 2099 o The Report-Buffering-Time TLV Type is 0x94. 2101 o TLV length is 4 octets. 2103 o Buffering Time is a 32-bit unsigned integer containing a time 2104 value in ms. 2106 5.13. Committed-Bandwidth TLV 2108 The Committed-Bandwidth TLV identifies an access line and provides 2109 the current amount of multicast bandwidth that the AN has committed 2110 to it. The TLV is illustrated in Figure 19. 2112 1 2 3 2113 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 2114 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2115 |TLV Type=Committed-Bandwidth | TLV Length (variable) | 2116 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2117 | Committed Multicast Bandwidth (kbits/s) | 2118 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2119 | | 2120 +-+-+- Target TLV +-+-+-+ 2121 | | 2122 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2124 Figure 19: Committed-Bandwidth TLV 2126 The Committed-Bandwidth TLV contains the following fields: 2128 o The Committed-Bandwidth TLV Type is 0x95. 2130 o TLV length is 4 octets plus the length of the Target TLV including 2131 its header and any padding. 2133 o Committed Multicast Bandwidth is a 32-bit unsigned integer 2134 providing a bandwidth amount in kbits/s. 2136 o The Target TLV identifies the access line to which this amount of 2137 multicast bandwidth is currently committed. 2139 6. Multicast Capabilities 2141 Section 3.5 of [RFC6320] defines a capability negotiation mechanism 2142 as well as a number of capabilities. This section defines five new 2143 capabilities in support of different modes of multicast operation: 2145 o NAS-initiated replication (capability type 0x03); 2147 o committed multicast bandwidth reporting (capability type 0x05); 2149 o conditional access with white and black lists (capability type 2150 0x06); 2152 o conditional access with grey lists (capability type 0x07); 2154 o bandwidth delegation (capability type 0x08). 2156 The "Capability Data" field within the Capability TLV for all of 2157 these capabilities is empty. All of these capabilities are 2158 independent of the access technology. 2160 The remainder of this section consists of three sub-sections. 2161 Section 6.1 specifies the protocol elements that must be implemented 2162 in order to support each capability. Section 6.2 specifies the 2163 procedures that apply to each capability on its own. Section 6.3 2164 specifies how the capabilities interact if more than one multicast 2165 capability is included in the set of capabilities negotiated between 2166 the AN and the NAS. 2168 Note that if a request contains content that is not supported 2169 (according to the tables in Section 6.1) by the negotiated set of 2170 multicast capabilities, the appropriate response is to return a 2171 Generic Response message indicating Failure (0x4) with an appropriate 2172 code value (e.g., 84 "TLV or value not supported by negotiated 2173 capability set"). The body of the message MUST contain a Status-Info 2174 TLV. See Sections 4.2 and 4.5 in [RFC6320] for more details. 2176 6.1. Required Protocol Support 2178 This section specifies the protocol elements that MUST be implemented 2179 to support each of the four multicast capabilities. Support of 2180 multiple multicast capabilities requires implementation of the union 2181 of the sets of protocol elements applying to each of the individual 2182 capabilities in the supported set. 2184 6.1.1. Protocol Requirements For NAS-initiated Replication 2186 Table 1 specifies the protocol elements within Section 4 and 2187 Section 5 that MUST be implemented to support the NAS-initiated 2188 replication multicast capability. 2190 +--------------+----------------------------------------------------+ 2191 | Reference | Protocol Element | 2192 +--------------+----------------------------------------------------+ 2193 | Section 4.1 | Provisioning message with MRepCtl-CAC TLV | 2194 | | | 2195 | Section 4.2 | Port Management message with Bandwidth-Allocation | 2196 | | TLV. | 2197 | | | 2198 | Section 4.3 | Multicast Replication Control message | 2199 | | | 2200 | Section 4.9 | Multicast Flow Query Request and Response messages | 2201 | | | 2202 | Section 5.4 | Command Number TLV | 2203 | | | 2204 | Section 5.7 | MRepCtl-CAC TLV | 2205 | | | 2206 | Section 5.11 | Multicast-Flow TLV | 2207 +--------------+----------------------------------------------------+ 2209 Table 1: Protocol Requirements For NAS-initiated Replication 2211 6.1.2. Protocol Requirements For Committed Multicast Bandwidth 2212 Reporting 2214 Table 2 specifies the protocol elements within Section 4 and 2215 Section 5 that MUST be implemented to support the NAS-initiated 2216 replication multicast capability. 2218 +--------------+----------------------------------------------------+ 2219 | Reference | Protocol Element | 2220 +--------------+----------------------------------------------------+ 2221 | Section 4.1 | Provisioning message with Report-Buffering-Time | 2222 | | TLV | 2223 | | | 2224 | Section 4.10 | Committed Bandwidth Report message | 2225 | | | 2226 | Section 4.9 | Multicast Flow Query Request and Response messages | 2227 | | | 2228 | Section 5.12 | Report-Buffering-Timer TLV | 2229 | | | 2230 | Section 5.13 | Committed-Bandwidth TLV | 2231 | | | 2232 | Section 5.11 | Multicast-Flow TLV | 2233 +--------------+----------------------------------------------------+ 2235 Table 2: Protocol Requirements For Committed Multicast Bandwidth 2236 Reporting 2238 6.1.3. Protocol Requirements For Conditional Access With White and 2239 Black Lists 2241 Table 3 specifies the protocol elements within Section 4 and 2242 Section 5 that MUST be implemented to support the conditional access 2243 with white and black lists multicast capability. 2245 +--------------+----------------------------------------------------+ 2246 | Reference | Protocol Element | 2247 +--------------+----------------------------------------------------+ 2248 | Section 4.1 | Provisioning message with | 2249 | | Multicast-Service-Profile TLV, White and Black | 2250 | | lists only, and White-List-CAC TLV | 2251 | | | 2252 | Section 4.2 | Port Management message with | 2253 | | Multicast-Service-Profile-Name and | 2254 | | Bandwidth-Allocation TLVs. | 2255 | | | 2256 | Section 4.9 | Multicast Flow Query Request and Response messages | 2257 | | | 2258 | Section 5.1 | Multicast-Service-Profile TLV | 2259 | | | 2260 | Section 5.2 | Multicast-Service-Profile-Name TLV | 2261 | | | 2262 | Section 5.3 | List-Action TLV, White and Black lists only | 2263 | | | 2264 | Section 5.5 | Bandwidth-Allocation TLV | 2265 | | | 2266 | Section 5.6 | White-List-CAC TLV | 2267 | | | 2268 | Section 5.11 | Multicast-Flow TLV | 2269 +--------------+----------------------------------------------------+ 2271 Table 3: Protocol Requirements For Conditional Access with White and 2272 Black Lists 2274 6.1.4. Protocol Requirements For Conditional Access With Grey Lists 2276 Table 4 specifies the protocol elements within Section 4 and 2277 Section 5 that MUST be implemented to support the conditional access 2278 with grey lists multicast capability. 2280 +--------------+----------------------------------------------------+ 2281 | Reference | Protocol Element | 2282 +--------------+----------------------------------------------------+ 2283 | Section 4.1 | Provisioning message with | 2284 | | Multicast-Service-Profile TLV, Grey lists only, | 2285 | | and MRepCtl-CAC TLV | 2286 | | | 2287 | Section 4.2 | Port Management message with | 2288 | | Multicast-Service-Profile-Name and | 2289 | | Bandwidth-Allocation TLVs. | 2290 | | | 2291 | Section 4.3 | Multicast Replication Control message | 2292 | | | 2293 | Section 4.4 | Multicast Admission Control Message | 2294 | | | 2295 | Section 4.9 | Multicast Flow Query Request and Response messages | 2296 | | | 2297 | Section 5.1 | Multicast-Service-Profile TLV, Grey lists only | 2298 | | | 2299 | Section 5.2 | Multicast-Service-Profile-Name TLV | 2300 | | | 2301 | Section 5.3 | List-Action TLV, Grey lists only | 2302 | | | 2303 | Section 5.4 | Command Number TLV | 2304 | | | 2305 | Section 5.5 | Bandwidth-Allocation TLV | 2306 | | | 2307 | Section 5.7 | MRepCtl-CAC TLV | 2308 | | | 2309 | Section 5.9 | Request-Source-IP TLV | 2310 | | | 2311 | Section 5.10 | Request-Source-MAC TLV | 2312 | | | 2313 | Section 5.11 | Multicast-Flow TLV | 2314 +--------------+----------------------------------------------------+ 2316 Table 4: Protocol Requirements For Conditional Access with Grey Lists 2318 6.1.5. Protocol Requirements For Delegated Bandwidth 2320 Table 5 specifies the protocol elements within Section 4 and 2321 Section 5 that MUST be implemented to support the delegated bandwidth 2322 multicast capability. 2324 +--------------+----------------------------------------------------+ 2325 | Reference | Protocol Element | 2326 +--------------+----------------------------------------------------+ 2327 | Section 4.2 | Port Management message with Bandwidth-Allocation | 2328 | | TLV. | 2329 | | | 2330 | Section 4.5 | Bandwidth Reallocation Request Message | 2331 | | | 2332 | Section 4.6 | Bandwidth Transfer Message | 2333 | | | 2334 | Section 4.7 | Delegated Bandwidth Query Request Message | 2335 | | | 2336 | Section 4.8 | Delegated Bandwidth Query Response Message | 2337 | | | 2338 | Section 4.9 | Multicast Flow Query Request and Response messages | 2339 | | | 2340 | Section 5.5 | Bandwidth-Allocation TLV | 2341 | | | 2342 | Section 5.8 | Bandwidth-Request TLV | 2343 | | | 2344 | Section 5.11 | Multicast-Flow TLV | 2345 +--------------+----------------------------------------------------+ 2347 Table 5: Protocol Requirements For Delegated Bandwidth 2349 6.2. Capability-Specific Procedures for Providing Multicast Service 2351 This section describes multicast service procedures for each 2352 capability as if it were the only multicast capability within the 2353 negotiated set. Procedures involving combinations of multicast 2354 capabilities are described in Section 6.3. 2356 The use of the Multicast Flow Query Request and Response messages to 2357 determine the association between multicast flows and ports is common 2358 to all multicast capabilities. No additional text is required here, 2359 beyond that already given in Section 4.9 to describe the use of those 2360 messages. 2362 6.2.1. Procedures For NAS-Initiated Replication 2364 NAS-initiated replication MAY be negotiated to support a mode of 2365 operation where IGMP/MLD requests are terminated on the NAS. 2366 Alternatively, it MAY be negotiated to allow the NAS to respond to 2367 requests sent by other means (e.g., through application signalling) 2368 that require the replication of multicast channels to a given access 2369 line. 2371 6.2.1.1. Provisioning 2373 The NAS MAY perform admission control for NAS-initiated replication. 2374 In this case, it MUST NOT include the MRepCtl-CAC TLV in a 2375 Provisioning message sent to the AN. Alternatively, the NAS MAY 2376 enable admission control at the AN for NAS-initiated replication. To 2377 do this, it MUST include the MRepCtl-CAC TLV in a Provisioning 2378 message sent to the AN and it MUST also include a Bandwidth- 2379 Allocation TLV in a Port Management message for each access line. 2381 6.2.1.2. Multicast Service Procedures 2383 The procedures associated with NAS-initiated replication are 2384 straightforward. To initiate replication, the NAS MUST send a 2385 Multicast Replication Control message to the AN, containing one or 2386 more commands adding flows, as described in Section 4.3.1. To 2387 terminate replication the NAS MUST send a Multicast Replication 2388 Control message where the commands delete instead of adding the 2389 flows. The AN acts upon these messages as specified in 2390 Section 4.3.2. 2392 6.2.2. Procedures For Committed Bandwidth Reporting 2394 Committed bandwidth reporting MAY be negotiated if the NAS requires 2395 current knowledge of the amount of multicast bandwidth committed to 2396 each access line and cannot obtain this information by other means. 2398 6.2.2.1. Provisioning 2400 The default buffering time when committed bandwidth reporting is 2401 enabled is zero (immediate reporting). To change this, the NAS MAY 2402 send an instance of the Report-Buffering-Time TLV containing a non- 2403 zero time value to the AN in a Provisioning message. If the NAS 2404 subsequently wishes to change the buffering time again, it MAY do so 2405 in another Provisioning message. 2407 6.2.2.2. Multicast Service Procedures 2409 If the buffering time for committed bandwidth reporting is zero, the 2410 AN MUST send a Committed Bandwidth Report message to the NAS each 2411 time the amount of multicast bandwidth committed to any access line 2412 under its control changes. 2414 If a non-zero value is provided in the Report-Buffering-Time TLV, the 2415 AN at any given moment is in one of two states: not-buffering, or 2416 buffering. The AN enters buffering state if it is in not-buffering 2417 state and the multicast bandwidth amount committed to some access 2418 line changes. It leaves buffering state when the AN sends a 2419 Committed Bandwidth Report. 2421 Upon entry to the buffering state, the AN MUST start a buffering 2422 timer and create a Committed Bandwidth Report message containing a 2423 Committed-Bandwidth TLV for the triggering access line, but MUST NOT 2424 send it. If a multicast bandwidth change occurs for another access 2425 line, the AN MUST add a new Committed-Bandwidth TLV to the message 2426 for that additional line. If a multicast bandwidth change occurs for 2427 a line for which a Committed-Bandwidth TLV is already present in the 2428 buffered report, the AN MUST update the Committed-Bandwidth TLV to 2429 contain the new bandwidth value, rather than adding another 2430 Committed-Bandwidth TLV for the same access line. 2432 The buffering timer expires after the period provided by the Report- 2433 Buffering-Time TLV. When it expires, the AN MUST send the Committed 2434 Bandwidth Report message that it has been accumulating to the NAS. 2435 Exceptionally, the AN MAY choose to send the message before the timer 2436 expires, in which case it MUST clear the buffering timer when the 2437 message is sent. In either case, the AN enters the not-buffering 2438 state as a result. 2440 Report buffering implies that NAS reaction to changes in multicast 2441 bandwidth usage is delayed by the amount of the buffering period. 2442 The choice of buffering period must take this into consideration. 2444 6.2.3. Procedures For Conditional Access With Black and White Lists 2446 6.2.3.1. Provisioning 2448 The NAS provisions named multicast service profiles containing White 2449 and Black lists on the AN using the Provisioning message containing 2450 one or more Multicast-Service-Profile TLVs. The NAS MAY update the 2451 contents of these profiles from time to time as required, by sending 2452 additional Provisioning messages with Multicast-Service-Profile TLVs 2453 containing incremental modifications to the existing White and Black 2454 lists or replacements for them. 2456 The NAS assigns a specific multicast service profile to an individual 2457 access line using the Port Management message containing a Multicast- 2458 Service-Profile-Name TLV. The NAS MAY change the multicast service 2459 profile for a given access line at any time by sending a Port 2460 Management message identifying a new multicast service profile. 2462 The NAS MAY choose to enable admission control at the AN for White- 2463 listed flows. To do this, it MUST send a Provisioning message as 2464 described in Section 4.1, which includes the White-List-CAC TLV and 2465 it MUST provide a multicast bandwidth allocation for each access line 2466 by including a Bandwidth-Allocation TLV in a Port Management message. 2468 6.2.3.2. Multicast Service Procedures 2470 The conditional access with White and Black lists capability assumes 2471 that IGMP/MLD requests are terminated on the AN. When the AN 2472 receives a "join" request, it MUST check to see whether the requested 2473 flow is White-listed or Black-listed as described below. Requests 2474 for Black-listed flows MUST be discarded. If the NAS has enabled 2475 admission control on the AN as described in the previous section, but 2476 a White-listed flow would cause the amount of committed multicast 2477 bandwidth to exceed the provisioned limit, the request MUST be 2478 discarded. The AN replicates flows passing these checks to the 2479 access line. 2481 To determine if a requested flow is White-listed, the AN searches for 2482 a best match to the flow in the applicable multicast service profile. 2483 Matching is done on the prefixes specified in the profile, ignoring 2484 the address bits of lower order than those in the prefix. 2486 If the requested multicast flow matches multiple lists associated 2487 with the access line, then the most specific match will be considered 2488 by the AN. If the most specific match occurs in multiple lists, the 2489 Black list entry takes precedence over the White list. In this 2490 context, the most specific match is defined as: 2492 o first, most specific match (longest prefix length) on the 2493 multicast flow address (i.e., on G of ) 2495 o then, most specific match (longest prefix length) on the unicast 2496 source address (i.e. on S of ) 2498 If the requested multicast flow is not part of any list, the join 2499 message SHOULD be discarded by the AN. This default behavior can 2500 easily be changed by means of a "catch-all" statement in the White 2501 list. For instance, adding () in the White List would make 2502 the default behavior to accept join messages for a multicast flow 2503 that has no other match on any list. 2505 When the AN receives a "leave" request, it terminates replication of 2506 the multicast flow. 2508 If the AN receives a Provisioning message which updates an existing 2509 multicast service profile, the AN MUST review the status of active 2510 flows on all ports to which the updated profile is currently 2511 assigned. Similarly, if a Port Management message assigns a new 2512 multicast service profile to a given port, the AN MUST review all 2513 active flows on that port. If the most specific match for any flow 2514 is a Black list entry, the flow MUST be terminated immediately. If 2515 any of the remaining flows do not match an entry in the White list, 2516 they also MUST be terminated immediately. White listed flows MUST be 2517 allowed to continue. 2519 6.2.4. Procedures For Conditional Access With Grey Lists 2521 6.2.4.1. Provisioning 2523 The NAS provisions named multicast service profiles containing Grey 2524 lists on the AN using the Provisioning message containing one or more 2525 Multicast-Service-Profile TLVs. The NAS MAY update the contents of 2526 these profiles from time to time as required, by sending additional 2527 Provisioning messages with Multicast-Service-Profile TLVs containing 2528 incremental modifications to the existing Grey lists or replacements 2529 for them. 2531 The NAS assigns a specific multicast service profile to an individual 2532 access line using the Port Management message containing a Multicast- 2533 Service-Profile-Name TLV. The NAS MAY change profiles on the line by 2534 sending a subsequent Port Management message identifying a new 2535 profile. 2537 The NAS MAY perform admission control for grey-listed flows. In that 2538 case, the NAS MUST NOT include the MRepCtl-CAC TLV in a Provisioning 2539 message sent to the AN. Alternatively, the NAS MAY enable admission 2540 control at the AN for Grey-listed flows. To do this, it MUST include 2541 the MRepCtl-CAC TLV in a Provisioning message sent to the AN and MUST 2542 also provide a Bandwidth- Allocation TLV in a Port Management message 2543 for each access line. 2545 6.2.4.2. Multicast Service Procedures 2547 The conditional access with Grey lists capability assumes that IGMP/ 2548 MLD requests are terminated on the AN. When the AN receives a "join" 2549 request, it MUST determine whether there is a match to the requested 2550 flow in the Grey list of the multicast service profile provisioned 2551 against the given access line. If there is no match, the request is 2552 discarded. Otherwise, the AN MUST send a Multicast Admission Control 2553 message to the NAS with content identifying the access line and the 2554 multicast flow to be added. As indicated in Section 4.4, the AN MAY 2555 add information identifying the requestor by IP address and/or MAC 2556 address. 2558 If the NAS decides to enable the flow, it MUST send a Multicast 2559 Replication Control request to the AN to replicate the flow to the 2560 access line with the Result field set to Nack (0x1), as described in 2561 Section 4.3.1. 2563 When the AN receives the Multicast Replication Control request, it 2564 performs admission control if admission control has been enabled as 2565 described in the previous section. If admitting the flow would cause 2566 the committed multicast bandwidth at the access line to exceed the 2567 provisioned limit, the AN reports an error to the NAS as described in 2568 Section 4.3.2. Otherwise it replicates the multicast flow as 2569 requested. 2571 If the NAS decides not to permit the flow, it MAY send a Multicast 2572 Replication Control message in response to the Multicast Admission 2573 Control message to allow the AN to update its internal records. The 2574 content of this message is described in Section 4.4.2. 2576 When the AN receives a "leave" request, it MUST terminate replication 2577 of the flow to the access line. It MUST then send a Multicast 2578 Admission Control message to the NAS indicating the deletion. The 2579 NAS updates its internal records but MUST NOT respond to the message. 2581 If the AN receives a Provisioning message which updates an existing 2582 multicast service profile, the AN MUST review the status of active 2583 flows on all ports to which the updated profile has been assigned. 2584 Similarly, if a Port Management message that assigns a new profile to 2585 a given port, the AN MUST review all active flows on that port. In 2586 either case, if any flow does not match an entry in the Grey list, it 2587 MUST be terminated immediately. 2589 6.2.5. Procedures For Delegated Bandwidth 2591 6.2.5.1. Provisioning 2593 The NAS SHOULD provision an initial amount of delegated multicast 2594 bandwidth for each access line using the Port Management message 2595 containing the Bandwidth-Allocation TLV. 2597 If it fails to do so and a value has not been provisioned on the 2598 AN by other means, the AN will be forced to request a bandwidth 2599 allocation as soon as it receives a "join" request. 2601 The NAS MAY at any time force an update of the amount of delegated 2602 bandwidth by the same means. 2604 6.2.5.2. Multicast Service Procedures 2606 The delegated bandwidth capability assumes that IGMP/MLD requests are 2607 terminated on the AN. When the AN receives a "join" request, it 2608 checks whether it has sufficient remaining uncommitted multicast 2609 bandwidth on the access line to accommodate the new multicast flow. 2610 If not, it MAY send a request to the NAS for an increased allocation 2611 of delegated bandwidth, using the Bandwidth Reallocation Request 2612 message. The NAS MUST return a Bandwidth Transfer message indicating 2613 whether it has granted the request, and if so, what is the new amount 2614 of delegated bandwidth. 2616 If the AN has sufficient uncommitted multicast capacity to admit the 2617 request, either originally or as the result of a successful request 2618 to the NAS, it replicates the requested flow to the access line. 2619 Otherwise it discards the request. 2621 When the AN receives a "leave" request for an active flow, it ceases 2622 replication. 2624 The NAS or AN MAY at some point detect that their respective views of 2625 the amount of delegated bandwidth are inconsistent. If so, they can 2626 recover using procedures described in Section 4.5 and Section 4.6. 2627 As a further aid to synchronization, either the NAS or the AN MAY 2628 from time to time check the peer's view of the amount of delegated 2629 bandwidth using the Delegated Bandwidth Query message. 2631 The NAS or AN MAY at any time release bandwidth to the peer using an 2632 autonomous Bandwidth Transfer message. The contents of this message 2633 are described in Section 4.6. 2635 6.3. Combinations of Multicast Capabilities 2637 6.3.1. Combination of Conditional Access With White and Black Lists and 2638 Conditional Access With Grey Lists 2640 If conditional access with White and Black lists is combined with 2641 conditional access with Grey lists, provisioning of the multicast 2642 service profiles is as described in Section 6.2.3.1 except that 2643 multicast service profiles will also include Grey lists. Admission 2644 control is enabled independently on the AN for White lists by 2645 including the White-list-CAC TLV in the Provisioning message and for 2646 Grey lists by including the MRepCtl-CAC TLV in the Provisioning 2647 message. The Bandwidth-Allocation TLV provisions an amount that 2648 applies to both White- and Grey- listed flows if admission control is 2649 enabled for both. 2651 With regard to multicast service procedures, one point of difference 2652 from the individual capabilities must be noted. This is an 2653 interaction during the profile matching procedure. The AN MUST seek 2654 the best match amongst multiple lists as described in 2655 Section 6.2.3.2. However, if there are multiple matches of equal 2656 precision, the order of priority is Black list first, Grey list 2657 second, and White list last. 2659 Once profile matching has been completed, processing of a "join" 2660 request is as described in Section 6.2.3.2 for White or Black listed 2661 flows or Section 6.2.4.2 for Grey listed flows. Requests that do not 2662 match any list SHOULD be discarded. 2664 When the AN receives a "leave" request, it MUST terminate replication 2665 of the flow to the access line. If the flow was Grey-listed, the AN 2666 MUST then send a Multicast Admission Control message to the NAS 2667 indicating the deletion. Thus the AN needs to retain the fact that 2668 the flow was Grey-listed for the life of the flow. 2670 If the AN receives a Provisioning message which updates an existing 2671 multicast service profile, the AN MUST review the status of active 2672 flows on all ports to which the updated profile is currently 2673 assigned. Similarly, if a Port Management message assigns a new 2674 multicast service profile to a given port, the AN MUST review all 2675 active flows on that port. If any flow has its most specific match 2676 in a Black list entry, it MUST be terminated immediately. If any of 2677 the remaining flows do not match an entry in the White or Grey list, 2678 they MUST also be terminated immediately. Finally, if any remaining 2679 flows were originally admitted because they were White-listed, but 2680 after the change they are Grey- listed, the AN MUST generate a 2681 Multicast Flow Query response message autonomously as if it were 2682 responding to a Multicast Flow Query request, listing all such flows. 2683 These flows MUST be allowed to continue until the NAS or the 2684 subscriber terminates them. Flows with their most specific match in 2685 the White list MUST be allowed to continue. 2687 The autonomously-generated Multicast Flow Query response message MUST 2688 be formatted as if it were a successful response to a request 2689 containing no Target and no Multicast-Flow TLV, as described in 2690 Section 4.9.2, with the exception that the Transaction-Id MUST be set 2691 to all zeroes. 2693 6.3.2. Combination of Conditional Access With Delegated Bandwidth 2695 The provisioning and bandwidth management procedures of Section 6.2.5 2696 apply in addition to the procedures in Section 6.2.3, Section 6.2.4, 2697 or Section 6.3.1 as applicable. Admission control follows the rules 2698 for conditional access in terms of matching flows against White and 2699 Black and/or Grey lists and performing or not performing bandwidth 2700 checks at the AN, but the amount of bandwidth used by the AN to 2701 perform admission control is negotiable as described in 2702 Section 6.2.5.2. 2704 6.3.3. Combination of NAS-Initiated Replication with Other Capabilities 2706 NAS-initiated replication can coexist with the other capabilities, 2707 but some means must exist to prevent double replication of flows. 2709 The simplest way to do this is to terminate all IGMP/MLD requests on 2710 the AN, so that NAS-initiated replication is stimulated only by 2711 signalling through other channels. Other arrangements are possible, 2712 but need not be discussed here. 2714 Assuming the necessary separation of responsibilities, the only point 2715 of interaction between NAS-initiated replication and the other 2716 multicast capabilities is in the area of admission control. 2717 Specifically, inclusion of the MRepCtl-CAC TLV in a Provisioning 2718 message and the Bandwidth-Allocation TLV in a Port Management message 2719 enables admission control by the AN for flows added by Multicast 2720 Replication Control messages, regardless of whether they are part of 2721 NAS-initiated replication or Grey list multicast service processing. 2722 Conversely, non inclusion of the MRepCtl-CAC TLV in Provisioning 2723 messages to the AN enables admission control by the NAS for flows 2724 added by Multicast Replication Control messages, regardless of 2725 whether they are part of NAS- initiated replication or Grey list 2726 multicast service processing. Admission Control for white flows can 2727 also be enabled independently on the AN by inclusion by the NAS of 2728 the White-List-CAC TLV in the Provisioning message. 2730 6.3.4. Combinations of Committed Bandwidth Reporting with Other 2731 Multicast Capabilities 2733 Committed bandwidth reporting can take independently of which other 2734 multicast capabilities have been negotiated. However, some 2735 combinations do not make sense because of redundancy. In particular, 2736 the NAS obtains the same information that committed bandwidth 2737 reporting gives if the only other capabilities operating are NAS- 2738 initiated replication and/or conditional access with Grey lists. 2740 7. Security Considerations 2742 The security considerations of ANCP are discussed in [RFC6320] and in 2743 [RFC5713]. 2745 8. IANA Considerations 2747 IANA NOTE: Please replace XXXX with the RFC number of this document. 2749 This document defines the following additional values within the ANCP 2750 Message Type Name Space registry: 2752 +--------------+--------------------------------+-----------+ 2753 | Message Type | Message Name | Reference | 2754 +--------------+--------------------------------+-----------+ 2755 | 144 | Multicast Replication Control | RFC XXXX | 2756 | | | | 2757 | 145 | Multicast Admission Control | RFC XXXX | 2758 | | | | 2759 | 146 | Bandwidth Reallocation Request | RFC XXXX | 2760 | | | | 2761 | 147 | Bandwidth Transfer | RFC XXXX | 2762 | | | | 2763 | 148 | Delegated Bandwidth Query | RFC XXXX | 2764 | | | | 2765 | 149 | Multicast Flow Query | RFC XXXX | 2766 | | | | 2767 | 150 | Committed Bandwidth Report | RFC XXXX | 2768 +--------------+--------------------------------+-----------+ 2770 This document defines the following additional values for the ANCP 2771 Result Code registry: 2773 +------------+------------------------------------------+-----------+ 2774 | Result | One-Line Description | Reference | 2775 | Code | | | 2776 +------------+------------------------------------------+-----------+ 2777 | 0x64 | Command error. | RFC XXXX | 2778 | | | | 2779 | 0x65 | Bad flow address. | RFC XXXX | 2780 | | | | 2781 | 0x66 | Multicast flow does not exist. | RFC XXXX | 2782 | | | | 2783 | 0x67 | Invalid preferred bandwidth amount. | RFC XXXX | 2784 | | | | 2785 | 0x68 | Inconsistent views of delegated | RFC XXXX | 2786 | | bandwidth amount. | | 2787 | | | | 2788 | 0x69 | Bandwidth request conflict. | RFC XXXX | 2789 +------------+------------------------------------------+-----------+ 2791 This document defines the following additional values for the ANCP 2792 Command Code registry: 2794 +----------------+--------------------------------------+-----------+ 2795 | Command Code | Command Code Directive Name | Reference | 2796 | Value | | | 2797 +----------------+--------------------------------------+-----------+ 2798 | 1 | Add | RFC XXXX | 2799 | | | | 2800 | 2 | Delete | RFC XXXX | 2801 | | | | 2802 | 3 | Delete All | RFC XXXX | 2803 | | | | 2804 | 4 | Admission Control Reject | RFC XXXX | 2805 | | | | 2806 | 5 | Conditional Access Reject | RFC XXXX | 2807 | | | | 2808 | 6 | Admission Control and Conditional | RFC XXXX | 2809 | | Access Reject | | 2810 +----------------+--------------------------------------+-----------+ 2812 This document defines the following additional values within the ANCP 2813 TLV Type Registry: 2815 +-----------+--------------------------------+-----------+ 2816 | Type Code | TLV Name | Reference | 2817 +-----------+--------------------------------+-----------+ 2818 | 0x13 | Multicast-Service-Profile | RFC XXXX | 2819 | | | | 2820 | 0x15 | Bandwidth-Allocation | RFC XXXX | 2821 | | | | 2822 | 0x16 | Bandwidth-Request | RFC XXXX | 2823 | | | | 2824 | 0x18 | Multicast-Service-Profile-Name | RFC XXXX | 2825 | | | | 2826 | 0x19 | Multicast-Flow | RFC XXXX | 2827 | | | | 2828 | 0x21 | List-Action | RFC XXXX | 2829 | | | | 2830 | 0x22 | Sequence-Number | RFC XXXX | 2831 | | | | 2832 | 0x24 | White-List-CAC | RFC XXXX | 2833 | | | | 2834 | 0x25 | MRepCtl-CAC | RFC XXXX | 2835 | | | | 2836 | 0x92 | Request-Source-IP | RFC XXXX | 2837 | | | | 2838 | 0x93 | Request-Source-MAC | RFC XXXX | 2839 | | | | 2840 | 0x94 | Report-Buffering-Time | RFC XXXX | 2841 | | | | 2842 | 0x95 | Committed-Bandwidth | RFC XXXX | 2843 +-----------+--------------------------------+-----------+ 2845 This document defines the following additional values for the ANCP 2846 Capability Type registry: 2848 +-------+-------------------------+--------+------------+-----------+ 2849 | Value | Capability Type Name | Tech | Capability | Reference | 2850 | | | Type | Data? | | 2851 +-------+-------------------------+--------+------------+-----------+ 2852 | 3 | NAS-Initiated | 0 | No | RFC XXXX | 2853 | | Replication | | | | 2854 | | | | | | 2855 | 5 | Committed Bandwidth | 0 | No | RFC XXXX | 2856 | | Reporting | | | | 2857 | | | | | | 2858 | 6 | Conditional Access With | 0 | No | RFC XXXX | 2859 | | White and Black Lists | | | | 2860 | | | | | | 2861 | 7 | Conditional Access With | 0 | No | RFC XXXX | 2862 | | Grey Lists | | | | 2863 | 8 | Bandwidth Delegation | 0 | No | RFC XXXX | 2864 +-------+-------------------------+--------+------------+-----------+ 2866 9. Acknowledgements 2868 The authors would like to acknowledge Wojciech Dec for providing 2869 useful input to this document, Robert Rennison for his help in 2870 shaping the definition of the Multicast-Service-Profile TLV, Shridhar 2871 Rao for his comments and suggestions and Aniruddha A for his proposal 2872 that formed the base of the Multicast Flow Reporting solution. 2873 Philippe Champagne, Sanjay Wadhwa and Stefaan De Cnodder provided 2874 substantial contributions on the solution for the NAS initiated 2875 multicast control use case. Kristian Poscic provided the committed 2876 bandwidth reporting use case. 2878 10. References 2880 10.1. Normative References 2882 [IEEE48] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/ 2883 EUI48.html", 2010. 2885 [IEEE64] IEEE, "http://standards.ieee.org/regauth/oui/tutorials/ 2886 EUI64.html", 2010. 2888 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2889 Requirement Levels", BCP 14, RFC 2119, March 1997. 2891 [RFC2710] Deering, S., Fenner, W., and B. Haberman, "Multicast 2892 Listener Discovery (MLD) for IPv6", RFC 2710, 2893 October 1999. 2895 [RFC3292] Doria, A., Hellstrand, F., Sundell, K., and T. Worster, 2896 "General Switch Management Protocol (GSMP) V3", RFC 3292, 2897 June 2002. 2899 [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. 2900 Thyagarajan, "Internet Group Management Protocol, Version 2901 3", RFC 3376, October 2002. 2903 [RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery 2904 Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. 2906 [RFC6320] Wadhwa, S., Moisand, J., Haag, T., Voigt, N., and T. 2907 Taylor, "Protocol for Access Node Control Mechanism in 2908 Broadband Networks", RFC 6320, October 2011. 2910 10.2. Informative References 2912 [I-D.morin-mboned-igmpmld-error-feedback] 2913 Morin, T. and B. Haberman, "IGMP/MLD Error Feedback", 2914 draft-morin-mboned-igmpmld-error-feedback-02 (work in 2915 progress), November 2008. 2917 [PIMreg] IANA, "http://www.iana.org/assignments/pim-parameters/pim- 2918 parameters.xhtml", 2005. 2920 [RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, 2921 "Protocol Independent Multicast - Sparse Mode (PIM-SM): 2922 Protocol Specification (Revised)", RFC 4601, August 2006. 2924 [RFC5384] Boers, A., Wijnands, I., and E. Rosen, "The Protocol 2925 Independent Multicast (PIM) Join Attribute Format", 2926 RFC 5384, November 2008. 2928 [RFC5713] Moustafa, H., Tschofenig, H., and S. De Cnodder, "Security 2929 Threats and Security Requirements for the Access Node 2930 Control Protocol (ANCP)", RFC 5713, January 2010. 2932 [RFC5851] Ooghe, S., Voigt, N., Platnic, M., Haag, T., and S. 2933 Wadhwa, "Framework and Requirements for an Access Node 2934 Control Mechanism in Broadband Multi-Service Networks", 2935 RFC 5851, May 2010. 2937 Appendix A. Example of Messages and Message Flows 2939 This appendix provides an example in which most of the possible 2940 message flows for multicast control are illustrated. This appendix 2941 is for informational purposes only. In case of discrepancy with text 2942 of the body of this document, the text in the body of the document is 2943 to be considered as the normative text. 2945 Assume the following, for a given access port: 2947 o The basic subscribed service is white-listed. The AN will be 2948 responsible for admission control for this service. 2950 o Some premium services are available, but requests for these 2951 services must be referred to the policy server for proper credit 2952 processing. For this reason they are grey-listed. The NAS will 2953 be responsible for admission control for these services. 2955 o The subscriber has asked that certain services be blocked so that 2956 his children cannot view them. These services are black-listed. 2958 o All of the above services are Source-Specific Multicast (SSM). In 2959 addition, by means which bypass the AN, the subscriber can signal 2960 intent to join an on- line game service which is Any-Source 2961 Multicast (ASM). The NAS is responsible for admission control for 2962 this service. 2964 o Bandwidth delegation is in effect to share video bandwidth between 2965 the AN and the NAS. 2967 The stated conditions require the use of four of the five 2968 capabilities specified in this memo. 2970 A.1. Provisioning Phase 2972 Assume that capability negotiation has been completed between the AN 2973 and NAS and that the set of negotiated capabilities includes the 2974 following four multicast capabilities: NAS-initiated replication, 2975 conditional access with white and black list, conditional access with 2976 grey list, and bandwidth delegation. At this point, the NAS can 2977 provision the service profiles on the AN and enable admission control 2978 at the AN for white-listed flows. To do this, the NAS sends the AN a 2979 Provisioning message containing this information. An example message 2980 providing the profile for our assumed subscriber is shown in 2981 Figure 20. The message has the following contents: 2983 o Message type is 93. 2985 o The Result and Result Code fields in the header are set to zeroes, 2986 as specified in the ANCP base protocol document. 2988 o A Transaction identifier is assigned by the NAS. 2990 o The Multicast-Service-Profile TLV (of which typically there would 2991 be multiple instances) contains a Multicast-Service-Profile-Name 2992 TLV (with a length of 20 octets assumed for the example) and three 2993 List-Action TLVs, one each for the White, Grey, and Black lists 2994 within the profile. The White list flows come in two sets of 2995 group addresses: 233.252.0.0/29, coming from a server at 2996 192.0.2.15, and 233.252.0.32/29, coming from a server at 2997 192.0.2.16. The Grey listed flows are in the band 2998 233.252.0.64/29, coming from a server at 192.0.2.21. Finally, the 2999 Black list flows are two individual flows that happen to overlap 3000 with the Grey list band: 233.252.0.65, and 233.252.0.69, also with 3001 source 192.0.2.21. 3003 o The White-List-CAC TLV indicates that the AN does admission 3004 control on White-listed flows. 3006 1 2 3 3007 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 3008 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3009 | Type (0x88-0C) | Length = 132 | 3010 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3011 | Vers | Sub | Msg Type = 93 | 0x00 | Result Code = 0x000 | 3012 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3013 | Partition ID | Transaction Identifier | 3014 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3015 |I| SubMessage Number | Length = 132 | 3016 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3017 | M-Serv-Prof TLV Type = 0x13 | TLV Length = 112 | 3018 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3019 | M-S-Prof-Name TLV Type = 0x18 | Embedded TLV Length = 20 | 3020 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3021 | Multicast service profile name | 3022 ~ = "Cust 0127-53681-0003" ~ 3023 | | 3024 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3025 | List-Action TLV Type = 0x21 | Embedded TLV Length = 28 | 3026 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3027 | Oper = 0x01 |Lst Typ = 0x01 | Reserved = 0x0000 | 3028 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3029 | Address Family = 0x01 | List Length = 20 | 3030 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3031 | G Preflen = 29| S Preflen = 32| Group prefix = | 3032 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3033 | 233.252.0.0 | Source prefix = | 3034 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3035 | 192.0.2.15 | G Preflen = 29| S Preflen = 32| 3036 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3037 | Group prefix = 233.252.0.32 | 3038 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3039 | Source prefix = 192.0.2.15 | 3040 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3041 | List-Action TLV Type = 0x21 | Embedded TLV Length = 18 | 3042 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3043 | Oper = 0x01 |Lst Typ = 0x03 | Reserved = 0x0000 | 3044 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3045 | Address Family = 0x01 | List Length = 10 | 3046 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3047 | G Preflen = 29| S Preflen = 32| Group prefix = / 3048 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3049 / 233.252.0.64 | Source prefix = / 3050 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3051 / 192.0.2.21 | Padding = 0x0000 | 3052 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3053 | List-Action TLV Type = 0x21 | Embedded TLV Length = 28 | 3054 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3055 | Oper = 0x01 |Lst Typ = 0x02 | Reserved = 0x0000 | 3056 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3057 | Address Family = 0x01 | List Length = 20 | 3058 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3059 | G Preflen = 32| S Preflen = 32| Group prefix = / 3060 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3061 / 233.252.0.65 | Source prefix = / 3062 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3063 / 192.0.2.21 | G Preflen = 32| S Preflen = 32| 3064 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3065 | Group prefix = 233.252.0.69 | 3066 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3067 | Source prefix = 192.0.2.21 | 3068 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3069 |White-List-CAC TLV Type = 0x24 | TLV Length = 0 | 3070 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3072 TLV lengths are given in decimal for easier understanding. Note that 3073 the padding after the middle List-Action TLV is counted as part of 3074 length of the Multicast-Service-Profile TLV, but is not included in 3075 the length of that List-Action TLV. Note also that the Length field 3076 in the message header, unlike those in the TLVs, includes the message 3077 header itself, as required by [RFC3292]. Finally, note that the 3078 Provisioning message does not include a MRepCtl-CAC TLV since in our 3079 example admission control for Grey listed flows and for NAS-initiated 3080 replication is performed by the NAS. 3082 Figure 20: Example Provisioning Message 3084 As soon as the AN port comes up, the AN sends an ANCP PORT_UP message 3085 to the NAS specifying the Access Loop Circuit ID. The NAS replies 3086 with an ANCP Port Management message that, together with the other 3087 parameters, includes the multicast service profile name to be 3088 associated to that port along with the initial amount of delegated 3089 bandwidth. The corresponding message flow is illustrated in 3090 Figure 21. 3092 +----------+ +---------+ +--- 3093 --+ +-----+ 3094 |Subscriber| | Home | | AN | | NAS | 3095 +----------+ | Gateway | +-----+ +-----+ 3096 | +---------+ | | 3097 | | | | 3098 | | | | 3099 | | DSL Synch. | | 3100 | |--------------------->| | 3101 | | |(M1)PORT_UP(Port ID) | 3102 | | |-------------------->| 3103 | | | (*) 3104 | | |(M2) PORT_MNGT | 3105 | | | (Port ID, | 3106 | | |Mcast S Profile Name,| 3107 | | |Bandwidth Allocation)| 3108 | | |<--------------------| 3110 (*) The NAS may optionally seek direction from an external 3111 Autorization/Policy Server 3113 Figure 21: Configuring an AN Port With Multicast Service Profile ID 3114 and Delegated Bandwidth amount 3116 The Port Management message will typically contain other TLVs but our 3117 example (Figure 22) just shows the Target, Multicast- Service- 3118 Profile-Name, and Bandwidth-Allocation TLVs. The Target TLV 3119 identifies the subscriber line, the Multicast-Service-Profile-Name 3120 TLV is identical to the one contained in the Provisioning message, 3121 and the Bandwidth-Allocation TLV provides just enough bandwidth (2000 3122 kbits/s) for one channel to start with. 3124 The following fields in the Port Management message header are shown 3125 with specific values either as directed by the base protocol document 3126 or for the sake of our example: 3128 o Message Type is 32. 3130 o Result is set to Nack (0x01) for this example. 3132 o Result Code is 0x000. 3134 o Port is set to 0. 3136 o Event Sequence Number, the R flag and the other bits marked x, 3137 Duration, the Event Flags, and the Flow Control Flags are all 3138 irrelevant for this function and are set to 0. 3140 o Function is set to 0x8, "Configure Connection Service Data". 3142 o X-Function is set to 0. 3144 o Tech Type is 0x05 (DSL). 3146 o Block lengths are calculated assuming a Circuit-Id length of 4 in 3147 our example. Recall that the example Multicast-Service-Profile- 3148 Name TLV length is 20. 3150 1 2 3 3151 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 3152 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3153 | Type (0x88-0C) | Length = 84 | 3154 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3155 | Vers | Sub | Msg Type = 32 | 0x01 | Result Code = 0x000 | 3156 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3157 | Partition ID | Transaction Identifier | 3158 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3159 |I| SubMessage Number | Length = 84 | 3160 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3161 | Port = 0 | 3162 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3163 | Port Session Number | 3164 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3165 | Event Sequence Number = 0 | 3166 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3167 |R|x|x|x|x|x|x|x| Duration = 0 | Function = 0x8| X-Function = 0| 3168 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3169 | Event Flags | Flow Control Flags | 3170 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3171 |x|x|x|x|x|x|x|x| Msg Type = 32 |Tech Type=0x05 | Blk Len = 56 | 3172 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3173 | # of TLVs = 3 | Extension Block length = 44 | 3174 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3175 | Target TLV Type = 0x1000 | Target TLV Length = 8 | 3176 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3177 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3178 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3179 | Access Loop Circuit ID | 3180 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3181 | M-S-Prof-Name TLV Type = 0x18 | TLV Length = 20 | 3182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3183 | Multicast service profile name | 3184 ~ = "Cust 0127-53681-0003" ~ 3185 | | 3186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3187 | BW Alloc TLV Type = 0x15 | TLV Length = 4 | 3188 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3189 | Bandwidth value = 0x000007D0 (2000 kbits/s) | 3190 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3192 Figure 22: Example Port Management Message 3194 A.2. Handling a Grey-Listed Flow 3196 Suppose now that the subscriber chooses to watch the premium channel 3197 characterized by source 192.0.2.21, group 233.252.0.67. Upon 3198 receiving the Join request, the AN matches it against the multicast 3199 service profile for the port and determines that it is a Grey-listed 3200 flow. Figure 23 illustrates the resulting ANCP message flow for the 3201 case of a simple join and leave, when admission control for Grey- 3202 listed flows is not activated on the AN. To start the flow, the AN 3203 sends a Multicast Admission Control request (M1) to the NAS. The NAS 3204 decides whether flow can be admitted, applying both policy and 3205 bandwidth criteria. It returns its decision (positive in this 3206 example) in a Multicast Replication Control message (M2). Later, 3207 when the subscriber leaves the flow, the AN informs the NAS by 3208 sending another Multicast Admission Control message. 3210 +----------+ +-------+ +-----+ ANCP +-----+ 3211 |Subscriber| | Home | | AN |<---------->| NAS | 3212 +----------+ |Gateway| +-----+ +-----+ 3213 | +-------+ | | 3214 | | | Multicast | 3215 | Join(Grey-Fl) | Admission | 3216 |-----------+---------->| Control (M1) | 3217 | | |------------------>| 3218 | | | | (NAS performs 3219 | | | Multicast | admission 3220 | | | Replication (*) control) 3221 | | | Control (M2) | 3222 | Mcast Grey Flow |<------------------| 3223 |<======================+ | 3224 | | | | 3225 ~ ~ ~ ~ 3226 | | | Multicast | 3227 | Leave(Grey-Fl) | Admission | 3228 |-----------+---------->| Control (M3) | 3229 | | |------------------>| 3230 | | | | 3232 Grey-Fl : Multicast Flow matching an entry in Grey List 3234 (*) The NAS may optionally seek direction from an external 3235 Authorization/Policy Server 3237 Figure 23: Successful Join/Leave Operations, Grey- Listed Flow 3239 The Multicast Admission Control message M1 contains: 3241 o an ANCP Header with: 3243 * Message-Type = 145 - Multicast Admission Control; 3245 * Result= 0x0 (Ignore); 3247 * Transaction-ID = Transaction-ID maintained by AN; 3249 o a Target TLV identifying the AN Port 3251 o a Command TLV containing: 3253 * Command Code = Add (0x01); 3255 * Accounting = 0; 3257 * a Multicast-Flow embedded TLV indicating the SSM multicast flow 3258 (Flow Type = 0x02) for which the AN received the IGMP Join: 3259 IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) Source 3260 Address = 192.0.2.21; 3262 * a Request-Source-IP embedded TLV containing the IGMP join 3263 source IP (192.0.2.100). 3265 The Multicast Admission Control message M1 is illustrated below: 3267 1 2 3 3268 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 3269 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3270 | Type (0x88-0C) | Length = 98 | 3271 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3272 | Vers | Sub | Msg Type=145 | 0x0 | Result Code = 0x000 | 3273 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3274 | Partition ID | Transaction Identifier | 3275 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3276 |I| SubMessage Number | Length = 98 | 3277 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3278 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3279 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3280 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3281 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3282 | Access Loop Circuit ID | 3283 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3284 | Command TLV Type = 0x11 | TLV Length = 28 | 3285 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3286 | Cmd Code=0x01 |Acctg = 0x00 | Reserved = 0x0000 | 3287 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3288 |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | 3289 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3290 |Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | 3291 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3292 | Multicast Group Address = 233.252.0.67 | 3293 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3294 | Unicast Source Address = 192.0.2.21 | 3295 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 3296 | Req-Src-IP TLV Type = 0x92 | Embedded TLV length = 4 | 3297 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3298 | Unicast Address = 192.0.2.100 | 3299 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3301 Multicast Admission Control Message Seeking To Add A Flow 3303 The Multicast Replication Control message M2 contains: 3305 o an ANCP Header with: 3307 * Message Type = 144 - Multicast Replication Control; 3309 * Result= 0x1 (NAck); 3311 * Transaction-ID = Transaction-ID maintained by NAS; 3313 o a Target TLV identifying the AN Port; 3315 o a Command TLV containing: 3317 * Command Code = Add (0x01); 3319 * Accounting = 1 (begin flow accounting), since in our example 3320 the operator wants accounting on this flow. 3322 * a Multicast-Flow embedded TLV indicating the SSM multicast flow 3323 (Flow Type = 0x02) that the NAS is admitting for this access 3324 port: IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) 3325 Source Address = 192.0.2.21. 3327 The Multicast Admission Control message M2 is illustrated below. 3329 1 2 3 3330 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 3331 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3332 | Type (0x88-0C) | Length = 48 | 3333 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3334 | Vers | Sub | Msg Type=144 | 0x1 | Result Code = 0x000 | 3335 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3336 | Partition ID | Transaction Identifier | 3337 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3338 |I| SubMessage Number | Length = 48 | 3339 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3340 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3341 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3342 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3343 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3344 | Access Loop Circuit ID | 3345 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3346 | Command TLV Type = 0x11 | TLV Length = 20 | 3347 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3348 | Cmd Code=0x01 | Acctg = 0x01 | Reserved = 0x0000 | 3349 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3350 |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | 3351 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3352 |Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | 3353 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3354 | Multicast Group Address = 233.252.0.67 | 3355 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3356 | Unicast Source Address = 192.0.2.21 | 3357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3359 Figure 24: Multicast Replication Control Message Admitting A Flow 3361 The Multicast Admission Control message M3 advising the NAS that the 3362 flow has been terminated contains: 3364 o an ANCP Header with: 3366 * Message-Type = 145 - Multicast Admission Control 3368 * Result= 0x0 (Ignore) 3370 * Transaction-ID = Transaction-ID maintained by AN 3372 o a Target TLV identifying the AN Port 3374 o a Command TLV containing: 3376 * a Command Code = Delete (0x02); 3378 * Accounting = 0; 3380 * a Multicast-Flow embedded TLV indicating the SSM multicast flow 3381 (Flow Type = 0x02) for which the AN received the IGMP leave: 3382 IPv4 (0x01) Group address= 233.252.0.67, IPv4 (0x01) Source 3383 Address = 192.0.2.21. 3385 * a Request-Source-IP embedded TLV containing the IGMP leave 3386 request source, IPv4 (0x01) address 192.0.2.100. 3388 The Multicast Admission Control message M3 is illustrated below. 3390 1 2 3 3391 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 3392 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3393 | Type (0x88-0C) | Length | 3394 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3395 | Vers | Sub | Msg Type=145 | 0x0 | Result Code = 0x000 | 3396 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3397 | Partition ID | Transaction Identifier | 3398 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3399 |I| SubMessage Number | Length | 3400 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3401 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3402 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3403 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3404 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3405 | Access Loop Circuit ID | 3406 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3407 | Command TLV Type = 0x11 | TLV Length = 28 | 3408 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3409 | Cmd Code=0x02 |Acctg = 0x00 | Reserved = 0x0000 | 3410 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3411 |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | 3412 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3413 |Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | 3414 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3415 | Multicast Group Address = 233.252.0.67 | 3416 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3417 | Unicast Source Address = 192.0.2.21 | 3418 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3419 | Req-Src-IP TLV Type = 0x92 | Embedded TLV length = 4 | 3420 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3421 | Unicast Address = 192.0.2.100 | 3422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3424 Multicast Admission Control Message Signalling flow Termination 3426 A.3. Handling White-Listed Flows 3428 The NAS has enabled White list admission control on the AN, and the 3429 bandwidth delegation capability has been negotiated. White listed 3430 flows in themselves require no messages to the NAS, either upon 3431 admission or upon termination, but the AN may request an increase in 3432 the amount of delegated bandwidth if it needs the increase to admit a 3433 flow. 3435 Consider an example where the AN has already admitted one White- 3436 listed flow, thereby using up the initially provisioned amount of 3437 delegated bandwidth (2000 kbits/s). A request is received to join a 3438 new flow in the White list range. The AN chooses to send a Bandwidth 3439 Reallocation Request message to the NAS, requesting that the 3440 delegated bandwidth allocation be increased to 4000 kbits/s at a 3441 minimum, and preferably to 6000 kbits/s. 3443 In our example, the NAS is managing bandwidth tightly, as witnessed 3444 by its minimal initial allocation of just enough for one flow. It is 3445 willing to provide the minimum additional amount only, and therefore 3446 returns a Bandwidth Transfer message where the delegated bandwidth 3447 value is given as 4000 kbits/s. With this amount, the AN is able to 3448 admit the second White-listed flow. The AN could send a similar 3449 Bandwidth Transfer message back to the NAS bringing the delegated 3450 bandwidth amount back down to 2000 kbits/s when one of the flows is 3451 terminated, but this shows nothing new and is omitted. 3453 As one more point of illustration, suppose that the NAS chooses to 3454 audit the current amount of delegated bandwidth to ensure it is 3455 synchronized with the AN. It sends a Delegated Bandwidth Query 3456 request message to the AN, and receives a Delegated Bandwidth Query 3457 response message with the current allocation as the AN sees it. 3459 The complete message flow is shown in Figure 25. 3461 +----------+ +-------+ +-----+ ANCP +-----+ 3462 |Subscriber| | Home | | AN |<---------->| NAS | 3463 +----------+ |Gateway| +-----+ +-----+ 3464 | +-------+ | | 3465 | | | | 3466 | Join(White-F1) | | 3467 |-----------+---------->| | 3468 | | |AN performs | 3469 | Mcast White Flow 1 | admission control | 3470 |<======================+ | 3471 | | | | 3472 | Join(White-F2) | | 3473 |-----------+---------->|No bandwidth left | 3474 | | | | 3475 | | |Bandwidth | 3476 | | | Reallocation Req | 3477 | | |------------------>|(M1) 3478 | | | | 3479 | | | (*) 3480 | | |Bandwidth Transfer | 3481 | AN can now |<------------------|(M2) 3482 | admit flow | | 3483 | Mcast White Flow 2 | | 3484 |<======================+ | 3485 | | | | 3486 ~ ~ ~ ~ 3487 | | |Delegated Bandwidth| 3488 | | | Query request | 3489 | | |<------------------|(M3) 3490 | | | | 3491 | | |Delegated Bandwidth| 3492 | | | Query response | 3493 | | |------------------>|(M4) 3494 | | | | 3496 (*) The NAS may optionally seek direction from an external 3497 Authorization/Policy Server 3499 Figure 25: Successful Join/Leave Operations, Grey-Listed Flow 3501 The Bandwidth Reallocation Request message (M1) is shown in 3502 Figure 26. The contents require little explanation. The Message 3503 Type for the Bandwidth Reallocation Request is 146. The Result field 3504 is set to 0x0 (Ignore). Besides the Target, the message has one 3505 other TLV, the Bandwidth- Request, with a TLV Type of 0x16. The TLV 3506 contains Required Amount and Preferred Amount fields, set to 4000 and 3507 6000 kbits/s respectively. 3509 1 2 3 3510 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 3511 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3512 | Type (0x88-0C) | Length = 36 | 3513 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3514 | Vers | Sub | Msg Type=146 | 0x0 | Result Code = 0x000 | 3515 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3516 | Partition ID | Transaction Identifier | 3517 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3518 |I| SubMessage Number | Length = 36 | 3519 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3520 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3521 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3522 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3523 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3524 | Access Loop Circuit ID | 3525 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3526 |Bandwidth-Req TLV Type = 0x16 | TLV Length = 8 | 3527 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3528 | Required Amount = 0x00000FA0 (4000 kbits/s) | 3529 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3530 | Preferred Amount = 0x00001770 (6000 kbits/s) | 3531 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3533 Figure 26: Bandwidth Reallocation Request Message 3535 The Bandwidth Transfer message (M2) is shown in Figure 27. Again, 3536 the contents are easily understood. The Message Type for the 3537 Bandwidth Transfer message is 147. The Result field is set to 3538 Success (0x3). The message contains the Target TLV and the 3539 Bandwidth- Allocation TLV. The latter has a TLV Type of 0x15 and 3540 contains a Delegated Amount field, set to 4000 kbits/s. 3542 1 2 3 3543 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 3544 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3545 | Type (0x88-0C) | Length = 32 | 3546 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3547 | Vers | Sub | Msg Type=147 | 0x3 | Result Code = 0x000 | 3548 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3549 | Partition ID | Transaction Identifier | 3550 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3551 |I| SubMessage Number | Length = 32 | 3552 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3553 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3554 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3555 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3556 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3557 | Access Loop Circuit ID | 3558 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3559 |BW-Allocation TLV Type = 0x15 | TLV Length = 4 | 3560 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3561 | Delegated Amount = 0x00000FA0 (4000 kbits/s) | 3562 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3564 Figure 27: NAS Response, Bandwidth Transfer Message 3566 The Delegated Bandwidth Query request message (M3) is shown in 3567 Figure 28. The Message Type for the Delegated Bandwidth Query 3568 request message is 148. The Result field is set to AckAll (0x2). 3569 The message contains the Target TLV only. 3571 1 2 3 3572 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 3573 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3574 | Type (0x88-0C) | Length = 24 | 3575 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3576 | Vers | Sub | Msg Type=148 | 0x2 | Result Code = 0x000 | 3577 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3578 | Partition ID | Transaction Identifier | 3579 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3580 |I| SubMessage Number | Length = 24 | 3581 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3582 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3583 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3584 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3585 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3586 | Access Loop Circuit ID | 3587 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3589 Figure 28: Delegated Bandwidth Query Request Message 3591 Finally, the Delegated Bandwidth Query response message (M4) is shown 3592 in Figure 29. The Message Type for the Delegated Bandwidth Query 3593 response message is 148. The Result field is set to Success (0x3). 3594 The message contains the Target TLV and the Bandwidth-Allocation TLV 3595 with the Delegated Amount field set to 4000 kbits/s. 3597 1 2 3 3598 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 3599 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3600 | Type (0x88-0C) | Length = 32 | 3601 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3602 | Vers | Sub | Msg Type=148 | 0x3 | Result Code = 0x000 | 3603 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3604 | Partition ID | Transaction Identifier (copied from request) | 3605 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3606 |I| SubMessage Number | Length = 32 | 3607 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3608 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3609 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3610 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3611 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3612 | Access Loop Circuit ID | 3613 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3614 |BW-Allocation TLV Type = 0x15 | TLV Length = 4 | 3615 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3616 | Delegated Amount = 0x00000FA0 (4000 kbits/s) | 3617 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3619 Figure 29: Delegated Bandwidth Query Response Message 3621 A.4. Handling Of Black-Listed Join Requests 3623 This section introduces no new messages, since requests for flows in 3624 the Black list are simply ignored. The one thing to point out is the 3625 overlap in our example between the set of flows in the Grey list and 3626 the flows in the Black list. This does not create any ambiguity, 3627 since not only does the Black list have priority for equally good 3628 matches, but also the Black list entries are more specific (group 3629 prefix lengths of 32 versus 29 in the Grey list) than the Grey list 3630 flow prefixes. 3632 A.5. Handling Of Requests To Join and Leave the On-Line Game 3634 The final class of multicast control actions in our example allows 3635 the subscriber to enter and leave the on-line game. As described at 3636 the beginning of this example, the game uses Any Source Multicast 3637 (ASM). Subscriber signalling bypasses the AN, going directly to the 3638 NAS (e.g., through a web interface). 3640 When the subscriber requests to join the game, the NAS (after 3641 applying policy and bandwidth checks) sends a Multicast Replication 3642 Control message to the AN to enable the flow on the port concerned. 3643 The AN knows not to apply admission control, since it has not 3644 received an MRepCtl-CAC TLV in the Provisioning message. When the 3645 subscriber leaves, the NAS sends another Multicast Replication 3646 Control message to delete the flow. This message sequence is shown 3647 in Figure 30. 3649 It is possible that the NAS finds that there is not enough bandwidth 3650 available to accommodate the subscriber's request. In this case, the 3651 NAS could send a Bandwidth Reallocation Request message to the AN, 3652 asking it to release some of the bandwidth delegated to it. This is 3653 not shown in the present example, since the messages are the same as 3654 those already presented with the exception that the Preferred Amount 3655 in the request will be *less than* or equal to the Required amount, 3656 rather than *greater than* or equal to it. 3658 +----------+ +-------+ +-----+ ANCP +-----+ 3659 |Subscriber| | Home | | AN |<---------->| NAS | 3660 +----------+ |Gateway| +-----+ +-----+ 3661 | +-------+ | | 3662 | | | | 3663 | Join game | | 3664 |-----------+------------------------------>| 3665 | | | Multicast | NAS performs 3666 | | | Replication (*) admission 3667 | | | Control (M1) | control 3668 | Mcast Game Flow |<------------------| 3669 |<=====================>+ | 3670 | | | | 3671 ~ ~ ~ ~ 3672 | | | | 3673 | Leave game | | 3674 |-----------+------------------------------>| 3675 | | | Multicast | 3676 | | | Replication | 3677 | | | Control (M2) | 3678 | Mcast Game Flow |<------------------| 3679 | discontinued | | 3680 | | | | 3682 (*) The NAS may optionally seek direction from an external 3683 Authorization/Policy Server 3685 Figure 30: NAS-Initiated Flows For On-Line Gaming 3687 Multicast Replication Control message (M1) in Figure 31 looks like 3688 the message in Figure 24 with two exceptions. The first is that the 3689 NAS has the option to set the Result field to AckAll (0x02) if it 3690 needs positive reassurance that the flow has been enabled. This was 3691 not done here to save having to depict a response differing only in 3692 the Result field. The larger difference in this example is that the 3693 flow description in the Multicast-Flow embedded TLV is that of an ASM 3694 multicast group (Flow Type = 0x01) with IPv4 (0x01) group address 3695 233.252.1.100. 3697 1 2 3 3698 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 3699 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3700 | Type (0x88-0C) | Length = 44 | 3701 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3702 | Vers | Sub | Msg Type=144 | 0x1 | Result Code = 0x000 | 3703 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3704 | Partition ID | Transaction Identifier | 3705 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3706 |I| SubMessage Number | Length = 44 | 3707 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3708 | Type = 0x1000 (Target) | Target TLV Length = 8 | 3709 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3710 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length = 4 | 3711 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3712 | Access Loop Circuit ID | 3713 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3714 | Command TLV Type = 0x11 | TLV Length = 16 | 3715 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3716 | Cmd Code=0x01 | Acctg = 0x01 | Reserved = 0x0000 | 3717 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3718 |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 8 | 3719 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3720 |Flow Type=0x01 |Addr Fam =0x01 | Reserved = 0x0000 | 3721 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3722 | Multicast Group Address = 233.252.1.100 | 3723 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 3725 Figure 31: Enabling The Subscriber To Join An On- Line Game 3727 Message M2 terminating the flow when the subscriber leaves the game 3728 looks the same as the message in Figure 31 with two exceptions: the 3729 Command Code becomes Delete (0x02), and Accounting is set to 0 to 3730 turn off flow accounting. Of course, the Transaction Identifier 3731 values will differ between the two messages. 3733 A.6. Example Flow For Multicast Flow Reporting 3735 The example in this section is independent of the example in the 3736 preceding sections. 3738 Figure 32 illustrates a message flow in a case where the NAS queries 3739 the AN about which multicast flows are active on port 10, on port 20 3740 and on port 11 of the AN. 3742 +----------+ +-------+ +-----+ ANCP 3743 +-----+ 3744 |Subscriber| | Home | | AN |<---------->| NAS | 3745 +----------+ |Gateway| +-----+ +-----+ 3746 | +-------+ | | 3747 | | | Multicast Flow | 3748 | | | Query Request | 3749 | | | (M1) | 3750 | | |<------------------| 3751 | | | | 3752 | | | Multicast Flow | 3753 | | | Query Response | 3754 | | | (M2) | 3755 | | |------------------>| 3756 | | | | 3757 | | | | 3759 Figure 32: Per Port Multicast Flow Reporting 3761 The Multicast Flow Query Request message (M1) is illustrated in 3762 Figure 33. The Message Type is 149. The Result field is set to 3763 AckAll (0x2). Three Target TLVs are present, identifying port 10, 3764 port 20, and port 11 respectively. 3766 0 1 2 3 3767 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 3768 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3769 | Type (0x88-0C) | Length | 3770 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3771 | Vers | Sub | Msg Type = 149|Rslt=2 | Result Code = 0 | 3772 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3773 | Partition ID | Transaction Identifier | 3774 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3775 |I| SubMessage Number | Length | 3776 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3777 | Type = 0x1000 (Target) | Target TLV Length | 3778 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3779 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | 3780 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3781 | | 3782 ~ Access Loop Circuit ID (port10) ~ 3783 | | 3784 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3785 | Type = 0x1000 (Target) | Target TLV Length | 3786 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3787 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | 3788 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3789 | | 3790 ~ Access Loop Circuit ID (port20) ~ 3791 | | 3792 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3793 | Type = 0x1000 (Target) | Target TLV Length | 3794 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3795 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | 3796 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3797 | | 3798 ~ Access Loop Circuit ID (port11) ~ 3799 | | 3800 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3802 Figure 33: Multicast Flow Query Request Message For Per-Port 3803 Multicast Flow Reporting 3805 The Multicast Flow Query Response message (M2) is illustrated in 3806 Figure 34. It indicates that there is one active multicast flow 3807 [(192.0.2.1, 233.252.2.4)] on port 10, no active multicast flow on 3808 port 20 and two active multicast flows [(192.0.2.1, 233.252.2.4) and 3809 (192.0.2.2, 233.252.2.10)] on port 11. 3811 0 1 2 3 3812 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 3814 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3815 | Type (0x88-0C) | Length | 3816 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3817 | Vers | Sub | Msg Type = 149|Rslt=3 | Result Code = 0 | 3818 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3819 | Partition ID | Transaction Identifier | 3820 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3821 |I| SubMessage Number | Length | 3822 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3823 | Type = 0x1000 (Target) | Target TLV Length | 3824 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3825 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | 3826 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3827 | | 3828 ~ Access Loop Circuit ID (port10) ~ 3829 | | 3830 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3831 |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | 3832 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3833 |Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | 3834 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3835 | Multicast Group Address = 233.252.2.4 | 3836 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3837 | Unicast Source Address = 192.0.2.1 | 3838 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 3839 | Type = 0x1000 (Target) | Target TLV Length | 3840 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3841 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | 3842 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3843 | | 3844 ~ Access Loop Circuit ID (port20) ~ 3845 | | 3846 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3847 | Type = 0x1000 (Target) | Target TLV Length | 3848 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3849 | Access-Loop-Circuit-ID 0x0001 | Circuit-ID Length | 3850 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3851 | | 3852 ~ Access Loop Circuit ID (port11) ~ 3853 | | 3854 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3855 |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | 3856 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3857 |Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | 3858 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3859 | Multicast Group Address = 233.252.2.4 | 3860 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3861 | Unicast Source Address = 192.0.2.1 | 3862 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 3863 |Multicast-Flow TLV Type = 0x19 | Embedded TLV Length = 12 | 3864 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3865 |Flow Type=0x02 |Addr Fam =0x01 | Reserved = 0x0000 | 3866 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3867 | Multicast Group Address: 233.252.2.10 | 3868 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3869 | Unicast Source Address = 192.0.2.2 | 3870 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+--+ 3872 Figure 34: Multicast Flow Query Response message for per-port 3873 Mulicast Flow Reporting 3875 Authors' Addresses 3877 Francois Le Faucheur 3878 Cisco Systems 3879 Greenside, 400 Avenue de Roumanille 3880 Sophia Antipolis 06410 3881 France 3883 Phone: +33 4 97 23 26 19 3884 Email: flefauch@cisco.com 3886 Roberta Maglione 3887 Telecom Italia 3888 Via Reiss Romoli 274 3889 Torino 10148 3890 Italy 3892 Phone: 3893 Email: roberta.maglione@telecomitalia.it 3895 Tom Taylor 3896 Huawei Technologies 3897 Ottawa 3898 Canada 3900 Email: tom111.taylor@bell.net