--- 1/draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-09.txt 2012-10-11 18:14:12.729509318 +0200 +++ 2/draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-10.txt 2012-10-11 18:14:12.769511020 +0200 @@ -1,25 +1,25 @@ CCAMP Working Group E. Bellagamba, Ed. Internet-Draft L. Andersson, Ed. Intended status: Standards Track Ericsson -Expires: April 10, 2013 P. Skoldstrom, Ed. +Expires: April 14, 2013 P. Skoldstrom, Ed. Acreo AB D. Ward Juniper A. Takacs Ericsson - October 7, 2012 + October 11, 2012 Configuration of Pro-Active Operations, Administration, and Maintenance (OAM) Functions for MPLS-based Transport Networks using RSVP-TE - draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-09 + draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-10 Abstract This specification describes the configuration of pro-active MPLS-TP Operations, Administration, and Maintenance (OAM) Functions for a given LSP using a set of TLVs that are carried by the RSVP-TE protocol. This document is a product of a joint Internet Engineering Task Force (IETF) / International Telecommunication Union Telecommunication @@ -35,21 +35,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on April 10, 2013. + This Internet-Draft will expire on April 14, 2013. Copyright Notice Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect @@ -668,31 +668,31 @@ default it is set to 1. - B: Octet (byte) count. When set to 1, indicates that the Counter 1-4 fields represent octet counts. When set to 0, indicates that the Counter 1-4 fields represent packet counts. By default it is set to 0. Reserved: Reserved for future specification and set to 0 on transmission and ignored when received. - Measurement Interval: the time interval (in microseconds) at which + Measurement Interval: the time interval (in milliseconds) at which Loss Measurement query messages MUST be sent on both directions. If the edge LSR receiving the Path message can not support such value, it can reply back with a higher interval. By default it is set to - (TBD). + (100) as per [RFC6375]. Test Interval: test messages interval as described in [RFC6374]. By - default it is set to (TBD). + default it is set to (10) as per [RFC6375]. Loss Threshold: the threshold value of lost packets over which - protections MUST be triggered. By default it is set to (TBD). + protections MUST be triggered. By default it is set to (200). 3.4.2. MPLS OAM PM Delay sub-TLV The "MPLS OAM PM Delay sub-TLV" depicted below is carried as a sub- TLV of the "OAM Functions TLV". 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | PM Delay Type (2) (IANA) | Length | @@ -723,32 +723,32 @@ default it is set to 1. - B: Octet (byte) count. When set to 1, indicates that the Counter 1-4 fields represent octet counts. When set to 0, indicates that the Counter 1-4 fields represent packet counts. By default it is set to 0. Reserved: Reserved for future specification and set to 0 on transmission and ignored when received. - Measurement Interval: the time interval (in microseconds) at which + Measurement Interval: the time interval (in milliseconds) at which Delay Measurement query messages MUST be sent on both directions. If the edge LSR receiving the Path message can not support such value, it can reply back with a higher interval. By default it is set to - (TBD). + (1) as per [RFC6375]. - Test Interval: test messages interval as described in [RFC6374]. By - default it is set to (TBD). + Test Interval: test messages interval (in milliseconds) as described + in [RFC6374]. By default it is set to (10) as per [RFC6375]. Delay Threshold: the threshold value of measured delay (in - microseconds) over which protections MUST be triggered. By default - it is set to (TBD). + milliseconds) over which protections MUST be triggered. By default + it is set to (2). 3.5. MPLS OAM FMS sub-TLV The "MPLS OAM FMS sub-TLV" depicted below is carried as a sub-TLV of the "OAM Configuration sub-TLV". When both working and protection paths are signaled, both LSPs SHOULD be signaled with identical settings of the E flag, T flag, and the refresh timer. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 @@ -775,22 +775,23 @@ - S: Indicate to a server MEP that its should transmit AIS and LKR signals on the client LSP. Default value is 0 (disabled). - T: Set timer value, enabled the configuration of a specific timer value. Default value is 0 (disabled). - Remaining bits: Reserved for future specification and set to 0. Refresh Timer: indicates the refresh timer of fault indication - messages. If the edge LSR receiving the Path message can not support - such value, it can reply back with a higher interval. + messages, in seconds. The range is 1 to 20 seconds. If the edge LSR + receiving the Path message can not support the value it can reply + back with a higher interval. - PHB: identifies the per-hop behavior of packets with fault management information. 4. IANA Considerations This document specifies the following new TLV types: - "BFD Configuration" type: 3;