multicast control extensions for ancp
Download
Skip this Video
Download Presentation
Multicast Control Extensions for ANCP

Loading in 2 Seconds...

play fullscreen
1 / 15

Multicast Control Extensions for ANCP - PowerPoint PPT Presentation


  • 100 Views
  • Uploaded on

Multicast Control Extensions for ANCP. draft-ietf-ancp-mc-extensions-01 F. Le Faucheur, Cisco R. Maglione , Telecom Italia T. Taylor, Huawei. Francois Le Faucheur [email protected] Summary of Changes 00 01.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Multicast Control Extensions for ANCP' - tamika


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
multicast control extensions for ancp

Multicast Control Extensions for ANCP

draft-ietf-ancp-mc-extensions-01

F. Le Faucheur, Cisco

R. Maglione, Telecom Italia

T. Taylor, Huawei

Francois Le Faucheur

[email protected]

summary of changes 00 01
Summary of Changes 0001
  • Structured capabilities into 4 separate Capabilites that can be individually negotiated (instead of 3 incremental capabilities):
  • Refined Admission Control operations
  • Result Code
  • Use of Generic Response
  • Editorials
4 separate capabilities
4 Separate Capabilities
  • Each 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 capabilities1
4 Separate Capabilities
  • For each Capability:
    • Required Protocol Support (Message types and TLVs)
    • Full description of procedures:
      • Provisioning
      • Multicast handling (including conditional access and admission control)
4 separate capabilities2
4 Separate Capabilities
  • For each combination of Capabilities:
    • Description of procedures (in particular any change against behavior of individual Capability due to Capability interactions)
admission control operations
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
Admission Control Examples: Capability={NAS-initiated Replication}
  • Admission control performed by AN

Provisioning (MRepCtl-CAC)

AN

NAS

Port Management (Bandwidth Allocation)

Admission control decision

Multicast Replication Control (“Add”)

Multicast Replication Control (“Add”)

  • Admission control performed by NAS

Provisioning ()

AN

NAS

Port Management ()

Multicast Replication Control (“Add”)

Multicast Replication Control (“Add”)

admission control examples capability conditional access white black
Admission Control Examples: Capability={Conditional Access White/Black}
  • Admission control performed by AN

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

IGMP Join

NAS

AN

Admission control decision

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

IGMP Join

  • No Admission control

Provisioning (Multicast Service Profile,)

IGMP Join

NAS

AN

Port Management (Multicast-Service-Profile-Name)

IGMP Join

change in use of result code
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
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
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
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.
editorials
Editorials
  • For every message type, separated discussion on sender behavior and receiver behavior in separate sub-sections
  • Moved “Example messages & call flows” to an Appendix
next steps
Next Steps
  • Reflect 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 steps1
Next Steps
  • Address feedback from group on recent changes
ad