draft-ietf-ancp-protocol-11.txt   draft-ietf-ancp-protocol-12.txt 
Network Working Group S. Wadhwa Network Working Group S. Wadhwa
Internet-Draft J. Moisand Internet-Draft J. Moisand
Intended status: Standards Track Juniper Networks Intended status: Standards Track Juniper Networks
Expires: February 24, 2011 T. Haag Expires: February 25, 2011 T. Haag
Deutsche Telekom Deutsche Telekom
N. Voigt N. Voigt
Nokia Siemens Networks Nokia Siemens Networks
T. Taylor, Ed. T. Taylor, Ed.
Huawei Technologies Huawei Technologies
August 23, 2010 August 24, 2010
Protocol for Access Node Control Mechanism in Broadband Networks Protocol for Access Node Control Mechanism in Broadband Networks
draft-ietf-ancp-protocol-11 draft-ietf-ancp-protocol-12
Abstract Abstract
This document describes the Access Node Control Protocol (ANCP). This document describes the Access Node Control Protocol (ANCP).
ANCP operates between a Network Access Server (NAS) and an Access ANCP operates between a Network Access Server (NAS) and an Access
Node (e.g. a Digital Subscriber Line Access Multiplexer (DSLAM)) in a Node (e.g. a Digital Subscriber Line Access Multiplexer (DSLAM)) in a
multi-service reference architecture in order to perform QoS-related, multi-service reference architecture in order to perform QoS-related,
service-related and subscriber- related operations. Use cases for service-related and subscriber- related operations. Use cases for
ANCP are documented in RFC 5851. As well as describing the base ANCP ANCP are documented in RFC 5851. As well as describing the base ANCP
protocol, this document specifies capabilities for Digital Subscriber protocol, this document specifies capabilities for Digital Subscriber
skipping to change at page 2, line 4 skipping to change at page 2, line 4
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 24, 2011. This Internet-Draft will expire on February 25, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 15, line 49 skipping to change at page 15, line 49
Capability Data : NULL Capability Data : NULL
For the detailed protocol specification of this capability see For the detailed protocol specification of this capability see
Section 5.4. Section 5.4.
4.5.2. ANCP Adjacency Procedures 4.5.2. ANCP Adjacency Procedures
The NAS MUST set the M-flag in the SYN message (signifying it is the The NAS MUST set the M-flag in the SYN message (signifying it is the
master). Once the adjacency is established, periodic adjacency master). Once the adjacency is established, periodic adjacency
messages (type ACK) MUST be exchanged. The default for the ACK messages (type ACK) MUST be exchanged. The default for the ACK
interval to be advertised in the adjacency messages is 10 seconds for interval to be advertised in the adjacency messages is 25 seconds for
ANCP. The actual value SHOULD be configurable and is an ANCP. The actual value SHOULD be configurable and is an
implementation choice. It is RECOMMENDED that both ends specify the implementation choice. It is RECOMMENDED that both ends specify the
same timer value; to achieve this, each end SHOULD compare the timer same timer value; to achieve this, each end SHOULD compare the timer
value in the first adjacency message it receives with its own value in the first adjacency message it receives with its own
preferred value and agree to use the higher of the two values. That preferred value and agree to use the higher of the two values. That
is, the node that receives a higher timer value than its own SHOULD is, the node that receives a higher timer value than its own SHOULD
reply in its subsequent adjacency messages (such as SYNACK, ACK) with reply in its subsequent adjacency messages (such as SYNACK, ACK) with
the higher timer value. the higher timer value.
In the adjacency protocol the version and sub-version fields are used In the adjacency protocol the version and sub-version fields are used
 End of changes. 5 change blocks. 
5 lines changed or deleted 5 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/