Re: [CCAMP] Comment on compatibility in draft-takacs-ccamp-revertive-ps

"Zafar Ali (zali)" <zali@cisco.com> Tue, 12 November 2013 19:02 UTC

Return-Path: <zali@cisco.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA65621E80CF for <ccamp@ietfa.amsl.com>; Tue, 12 Nov 2013 11:02:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.001
X-Spam-Level:
X-Spam-Status: No, score=-10.001 tagged_above=-999 required=5 tests=[AWL=0.597, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D-geV8y7eZcu for <ccamp@ietfa.amsl.com>; Tue, 12 Nov 2013 11:01:59 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id C95F421F9F1B for <ccamp@ietf.org>; Tue, 12 Nov 2013 11:01:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=29905; q=dns/txt; s=iport; t=1384282916; x=1385492516; h=from:to:cc:subject:date:message-id:in-reply-to: mime-version; bh=iJWcYPvB0Tnbv9WUNGqbFneGNScSa6PnPyMtMwUgJys=; b=Glv5OUAVnz9AK7ZT0X7fI88WuARjOt5hM2wFqblIwHkd4//ula5UDuWT 9ZhCUEz8fL7jhDbZNFi3Uk4/N86pska0s+96heifONbqbwQjadQX1aVPf w/OO6oi8nnwE8KQHFRXULy5WeuVbECMQyOs3tyysckP76VPwnwHhJ9NEk I=;
X-Files: Corporate-sig-logo.jpg : 5715
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFAAV6glKtJV2c/2dsb2JhbABagkNEOFOCdalqkjgYgRIWdIIlAQEBBAEBAQIeC0ALDAIEAQgRAwECBgEBAQoDEgMCBBUBAwsBCxQJCAIEDgQBBgMFh3MNrEeSZgSMWoFIgQ4QCgwFBwIEBIJhgUYDkDCBMYYukgqDJoFxOQ
X-IronPort-AV: E=Sophos; i="4.93,686,1378857600"; d="jpg'145?scan'145,208,217,145"; a="283651126"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-1.cisco.com with ESMTP; 12 Nov 2013 19:01:56 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id rACJ1u75009421 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 12 Nov 2013 19:01:56 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.50]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0123.003; Tue, 12 Nov 2013 13:01:55 -0600
From: "Zafar Ali (zali)" <zali@cisco.com>
To: Dieter Beller <Dieter.Beller@alcatel-lucent.com>
Thread-Topic: [CCAMP] Comment on compatibility in draft-takacs-ccamp-revertive-ps
Thread-Index: AQHO3Ci6h09KE7p+Tk6NZ+uJgecEF5obgDiAgANocoCAAyMoAA==
Date: Tue, 12 Nov 2013 19:01:55 +0000
Message-ID: <CEA7E0C8.82EA8%zali@cisco.com>
In-Reply-To: <527F9325.1050502@alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.82.242.117]
Content-Type: multipart/mixed; boundary="_004_CEA7E0C882EA8zaliciscocom_"
MIME-Version: 1.0
Cc: CCAMP <ccamp@ietf.org>
Subject: Re: [CCAMP] Comment on compatibility in draft-takacs-ccamp-revertive-ps
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Nov 2013 19:02:04 -0000

Hi Dieter:

The default parameter value in data plan is deficient for the following reasons:

  1.  We cannot differentiate between revertive and non-revertive behavior using default value of wait-to-restore timer. E.g., as far as I remember default value for WRT is 0, which means protection is non-revertive. So this default does not work for revertive protection. I.e., the data plan default cannot cover both revertive and non-revertive cases.
  2.  Correct setting for wait-to-restore and hold-off timers need to account for differential delays between working and protection paths.

In summary, default values cannot cover all use cases. Hence, SP typically wants to set revertive vs. non-revertive behavior, wait-to-restore and hold-off timers on per connection basis.

Thanks

Regards … Zafar

From: Dieter Beller <Dieter.Beller@alcatel-lucent.com<mailto:Dieter.Beller@alcatel-lucent.com>>
Organization: Alcatel-Lucent
Date: Sunday, November 10, 2013 9:07 AM
To: zali <zali@cisco.com<mailto:zali@cisco.com>>
Cc: "lberger@labn.net<mailto:lberger@labn.net>" <lberger@labn.net<mailto:lberger@labn.net>>, "ccamp@ietf.org<mailto:ccamp@ietf.org>" <ccamp@ietf.org<mailto:ccamp@ietf.org>>
Subject: Re: [CCAMP] Comment on compatibility in draft-takacs-ccamp-revertive-ps

Hi Zafar,

this draft is defining signaling extensions for the hold-off time as well as the wait-to-restore time for protected LSPs
where applicable.

There are default values set for these timers in the data plane and signaling them in the control plane makes only
sense if the timer values shall differ from the default values. Do you see a need for that? IMO, operators typically
use the defaults and do not set these values on a per connection basis.


Thanks,
Dieter


On 08.11.2013 22:11, Zafar Ali (zali) wrote:

Hi Lou-

You are right, the ctype is TBD, like I mentioned during the meeting that
we are using different ctype.

We would like to take this opportunity to solicit comments from the WG on
this draft.

Thanks

Regards Š Zafar

-----Original Message-----
From: "lberger@labn.net"<mailto:lberger@labn.net> <lberger@labn.net><mailto:lberger@labn.net>
Date: Thursday, November 7, 2013 6:17 PM
To: zali <zali@cisco.com><mailto:zali@cisco.com>, "ccamp@ietf.org"<mailto:ccamp@ietf.org> <ccamp@ietf.org><mailto:ccamp@ietf.org>
Subject: Comment on compatibility in draft-takacs-ccamp-revertive-ps



Zafar,
        My comment in today's session was that you are redefining the format of
an existing object (by adding TLVs) this breaks compatibility.  You
stated that this wasn't the case.

FWIW:

Your document says:

   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
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |            Length             | Class-Num(37) |   C-Type(2)   |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |S|P|N|O| Reserved  | LSP Flags |      Reserved     | Link Flags|
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |I|R|   Reserved    | Seg.Flags |           Reserved            |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                                                               |
  ~                           sub-TLVs                            ~
  |                                                               |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


RFC4872 says
     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
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |            Length             | Class-Num(37) | C-Type (2)    |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |S|P|N|O| Reserved  | LSP Flags |     Reserved      | Link Flags|
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                           Reserved                            |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Perhaps you meant C-Type(TBD).  You should address compatibility
explicitly in any case.

Lou


_______________________________________________
CCAMP mailing list
CCAMP@ietf.org<mailto:CCAMP@ietf.org>https://www.ietf.org/mailman/listinfo/ccamp

--
[cid:part1.06010706.00080409@alcatel-lucent.com]
DIETER BELLER
ALCATEL-LUCENT DEUTSCHLAND AG
PROJECT MANAGER ASON/GMPLS CONTROL PLANE
IP ROUTING AND TRANSPORT BL
IP TRANSPORT BU

Lorenzstrasse 10
70435 Stuttgart, Germany
Phone: +49 711 821 43125
Mobil: +49 175 7266874
Dieter.Beller@alcatel-lucent.com<mailto:Dieter.Beller@alcatel-lucent.com>

Alcatel-Lucent Deutschland AG
Domicile of the Company: Stuttgart · Local Court Stuttgart HRB 4026
Chairman of the Supervisory Board: Michael Oppenhoff
Board of Management: Wilhelm Dresselhaus (Chairman) · Hans-Jörg Daub · Andreas Gehe

This e-mail and its attachments, if any, may contain confidential information.
If you have received this e-mail in error, please notify us and delete or destroy the e-mail and its attachments, if any, immediately.
If you have received this e-mail in error, you must not forward or make use of the e-mail and its attachments, if any.