Multicast Control Extensions for ANCP

draft-ietf-ancp-mc-extensions-01F. Le Faucheur, Cisco

R. Maglione, Telecom ItaliaT. Taylor, Huawei

Francois Le Faucheurflefauch@cisco.com

Summary of Changes 0001

Structured capabilities into 4 separate Capabilites that can be individually negotiated (instead of 3 incremental capabilities):

Refined Admission Control operations Result CodeUse of Generic ResponseEditorials

4 Separate CapabilitiesEach Capability is allocated a separate

capability type (and thus can be negotiated individually): NAS-initiated replication (capability type 0x05); Conditional access with white and black lists

(capability type 0x06); Conditional access with grey lists (capability type

0x07); Bandwidth delegation (capability type 0x08).

4 Separate CapabilitiesFor each Capability:

Required Protocol Support (Message types and TLVs)

Full description of procedures:ProvisioningMulticast handling (including conditional access and

admission control)

4 Separate CapabilitiesFor each combination of Capabilities:

Description of procedures (in particular any change against behavior of individual Capability due to Capability interactions)

Admission Control Operations

Activation of admission control on AN is explicitly controlled through Provisioning

Separate activation of admission control by AN: For IGMP Joins for White-List For ANCP Multicast Replication Control “Adds”

Admission control activation at AN-level (not port-level, not flow-level)

New TLVs: White-List-CAC TLV: indicates that the NAS wishes the

AN to do admission control for White-listed flows. MRepCtl-CAC TL: indicates that the NAS wishes the AN

to do admission control for flows added by the Multicast Replication Control message.

Admission Control Examples:

Capability={NAS-initiated Replication}

AN NAS

Provisioning (MRepCtl-CAC) Admission control

performed by AN

Multicast Replication Control (“Add”)

Multicast Replication Control (“Add”)

AN NAS

Provisioning ()

Multicast Replication Control (“Add”)Multicast Replication

Control (“Add”)

Admission control performed by NAS

Port Management (Bandwidth Allocation)

Port Management ()

Admission control decision

Admission Control Examples:

Capability={Conditional Access White/Black}

AN NAS

Provisioning (Multicast Service Profile, White-List-CAC)

Admission control performed by AN

IGMP Join

No Admission control

Port Management (Multicast-Service-Profile-Name, Bandwidth Allocation)

IGMP Join

AN NAS

Provisioning (Multicast Service Profile,)

IGMP Join

IGMP Join

Port Management (Multicast-Service-Profile-Name)

Admission control decision

Change in Use of Result Code

Till previous version, agreed approach was that for any multicast-related request message: Result-Code set to 0x00=“Ignore” Receiver behavior for responding specified as

part of message definition In this version, Result Codes 0x2=“AckAll” and

0x1=“Nack” (with their semantics) reintroduced for a few messages with matching behavior (e.g. Multicast Replication Control)

Is this OK for WG?

Use of new Generic Response

In accordance with list discussions: ancp-protocol-07 introduced the Generic

Response message ancp-mc-extensions-01 makes use of the Generic

Response :E.g. instead of Multicast-Status message in

response to Multicast Replication Control (with a Status-Info TLV including Command number TLV & failed Command TLV)

E.g. sent by AN in case of processing error of Provisioning message (with a Status-Info TLV)

New White/Black/Grey List Structure

Framework document calls for ability to modify White/Black/Grey lists incrementally.

To implement this, replaced monolithic list structure with a set of "list actions".

Each action is a three-level tuple: {action, W/G/B, {IP version, {list of flows}}}

Can have IPv4 list or IPv6 list or both in same action.

Action can be add/delete/replace, where "delete" removes specified flows from a pre-existing list.

Simplified Reset Procedure

Bandwidth delegation had a complex reset procedure if inconsistency was detected.

Probably over-specified in the first place, going beyond requirements for interoperability.

Replaced by much simpler rules. Basic principle: NAS/Policy Server is master end.

Added ability for AN to send Delegated Bandwidth Query as part of procedure.

Removed Committed-Bandwidth TLV, since it is meaningless if responder is NAS.

EditorialsFor every message type, separated discussion

on sender behavior and receiver behavior in separate sub-sections

Moved “Example messages & call flows” to an Appendix

…

Next StepsReflect agreement from 27-29 Oct thread “Re:

[ANCP] [Fwd: I-D ACTION:draft-ietf-ancp-mc-extensions-01.txt]” between Tom & Francois: Remove R-flag In 6.3.3 ("White/Black + Grey + Bandwidth-

Delegation”), distribution/control of admission control should work the same as when we have "White/Black + Grey

In 6.2.1 & 6.2.3.1 , add sentences to make explicit the case of admission control on NAS

Address editorials sent by Francois to Tom

Next StepsAddress feedback from group on recent

changes