iGMP
- Issues observed with existing implementation
- Sample Issue
- Sample resolution 1
- Sample resolution 2
- RESOLVED: Agreed resolution
- Work Breakdown
- links to JIRAS with owners
- Need to forward IGMP requests as well as snoop
- Update ONOS IGMP app to enable forwarding packets upstream on a configurable VLAN
- RESOLVED: TBD
- Need to set per subscriber information when forwarding packets upstream
- Augment IGMP configuration to specify per subscriber information
- Introduce as service through which per-subscriber /OLT values can be obtained
- Default implementation could read from netcfg augmentation
- Provide "REST" callout implementation that would make / cache REST calls to external (site specific) service end point
- RESOLVED: TBD
- Sample Issue
AAA
- Issues observed with existing implementation
- Sample Issue
- Sample resolution 1
- Sample resolution 2
- RESOLVED: Agreed resolution
- Work Breakdown
- links to JIRAS with owners
- Need to forward AAA packets on specific VLAN
- Add configuration and logic to forward packets to upstream AAA server
- RESOLVED: TBD
- Need to insert subscriber specific information into AAA packets
- Augment AAA configuration with per subscriber information
- Introduce as service through which per-subscriber /OLT values can be obtained
- Default implementation could read from netcfg augmentation
- Provide "REST" callout implementation that would make / cache REST calls to external (site specific) service end point
- RESOLVED: TBD
- Need to be able to map from AAA packets to/from subscriber authentication state machine
- Augment AAA for mapping, limited by packet identifier of 1 byte (256)
- RESOLVED: TBD
- Sample Issue
DHCP Relay
- Issues observed with existing implementation
- Sample Issue
- Sample resolution 1
- Sample resolution 2
- RESOLVED: Agreed resolution
- Work Breakdown
- links to JIRAS with owners
- Need to forward DHCP packets on specific VLAN
- Add configuration and logic to forward packets to upstream DHCP server
- RESOLVED: TBD
- Need to insert subscriber specific information into DHCP (option 82) packets
- Augment DHCP configuration with per subscriber information
- Introduce as service through which per-subscriber /OLT values can be obtained
- Default implementation could read from netcfg augmentation
- Provide "REST" callout implementation that would make / cache REST calls to external (site specific) service end point
- RESOLVED: TBD
- Sample Issue