1. Sanjay Wadhwa Juniper Networks
ANCP protocol draft updates draft-wadhwa-gsmp-l2control-configuration-01.txt ANCP WG IETF-66
Sanjay Wadhwa
Juniper Networks

2. Draft-01 Updates
Added section 3.2 for general characterization of ethernet aggregation networks (N:1 and 1:1 VLAN models).
Access-Loop-Circuit-ID format clarified to indicate “Access-Node- Identifier” as mandatory.
‘‘Access-Node-Identifier atm slot/port:vpi.vci
DSL line attributes sent by the AN (access-node) to the NAS extended with an optional sub-TLV to convey “data link” and “encapsulation” of the access-loop.
Useful for accurate shaping of traffic on the NAS.
If local loop is cell based NAS can account for cell-tax.
NAS can account for byte difference in encapsulation used on the local loop and aggregation network.
When the sub-TLV is present, data link is mandatory, encaps is optional.
IETF 66 (ANCP WG)

3. Draft-01 Updates A new optional TLV for “acess-loop-remote- ID” added.
Operator configured string to identify user on the local-loop.
Typically inserted by AN when it acts as “signalling relay agent” (DHCP relay agent or PPPoE IA).
OAM error codes extended.
More reviewers acknowledged.
IETF 66 (ANCP WG)

4. Draft-02 (forthcoming) Use agreed upon WG naming convention.
ANCP instead of L2C
NAS instead of BRAS or BNG
Fix TLV numbering
IETF 66 (ANCP WG)

5. Thank You
IETF 66 (ANCP WG)

6. Sanjay Wadhwa Juniper Networks
ANCP Control Plane Graceful Restart Extensions draft-wadhwa-ancp-graceful-restart-00.txt ANCP WG IETF-66
Sanjay Wadhwa
Juniper Networks

7. ANCP Graceful Restart Motivation Make ANCP carrier grade
Immune to disruptions due to control plane resets on NAS or AN.
Without Graceful Restart, on loss of ANCP adjacency all state corresponding to restarting ANCP element removed by its peer.
Graceful restart protocol extensions to ANCP proposed.
Provide support for non-disruptive planned or unplanned ANCP adjacency reset.
Graceful state re-synchronization on Adjacency re- establishment.
IETF 66 (ANCP WG)

8. ANCP Graceful Restart
Forwarding plane on restarting element continues to use information learnt from the ANCP peer.
State leanrt from the restarting element by ANCP peer continues to be used till an agreed upon amount of time.
When the restarting element’s control plane restarts ANCP adjacency is re-established.
State needs to be re-synchronized between ANCP peers (in non-disruptive fashion).
Resources related to information learnt from peer that is no longer valid needs to be recliamed.
IETF 66 (ANCP WG)

9. ANCP Graceful Restart State resynchronization Mechanism
Restarting element marks all the learnt information from its peers as “STALE”.
ANCP peer(s) of restarting element marks all the learnt state associated with restarting peer as “STALE”.
Both ANCP peers re-originate all information owned by them.
Each element learns and updates its state. “STALE” marking is reset for updated state.
After re-originating its entire information, each element sends an “END-OF-STATE” adjacency message to its peer.
On receiving “END-OF-STATE” each element removes all state still marked “STALE”. The associated resources are released and corresponding state reverts to default values.
IETF 66 (ANCP WG)

10. ANCP Graceful Restart
ANCP element capable of “graceful restart” advertises “graceful restart” capability in adjacency messages.
ANCP element that supports helping a restarting peer advertises “graceful restart helper” capability in adjacency message.
Restarting element advertises “restart time” in the capability. This is the time for which ANCP peer continues to use information originated by the restarting element prior to restart.
IETF 66 (ANCP WG)

11. Thank You
IETF 66 (ANCP WG)