Re: [CCAMP] Network Assigned Upstream Label - Draft Update

Vishnu Pavan Beeram <vishnupavan@gmail.com> Fri, 28 February 2014 14:16 UTC

Return-Path: <vishnupavan@gmail.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BBBF1A0214 for <ccamp@ietfa.amsl.com>; Fri, 28 Feb 2014 06:16:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jb8-Nob96TIV for <ccamp@ietfa.amsl.com>; Fri, 28 Feb 2014 06:16:12 -0800 (PST)
Received: from mail-ee0-x22e.google.com (mail-ee0-x22e.google.com [IPv6:2a00:1450:4013:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 5C7811A01B4 for <ccamp@ietf.org>; Fri, 28 Feb 2014 06:16:12 -0800 (PST)
Received: by mail-ee0-f46.google.com with SMTP id d49so2215423eek.5 for <ccamp@ietf.org>; Fri, 28 Feb 2014 06:16:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6ZKXYHFGc/fGjAEGT23gwW9NCuDJeJTE8xX9uUqzY8w=; b=S6sPbaRxJuNSN0/qg4JJ6N2KmtwLGhJUbZYab1Vczz8K5Jm4q0Zl2mvyWrcky+89Ld 8Z7YFfVWris2FdeGHUdCDavsuquh7XchgAg9qUfxckae01Uyyrco9wJzYDfgshXEX878 qEEOZtJG6NZZP9XW6PDb7qXrbKfcv/O7Sx2QpzLHQRGkOHB9mFx2iSHy+4lUKu8rViGz E/3ZRtystpKSnM56nXPbeuzPFeIhKiK7zWCxVHhpQW3QwvRVZaUSqYW2/NtZVyP3RHrM 2ekZ5lYx+VwbKfEWzlT53y2i4ppjPwGUzeOOJG3CXiYmLsmWE7P5snj1YZzDb54ALTLu VMNQ==
MIME-Version: 1.0
X-Received: by 10.204.73.2 with SMTP id o2mr5223bkj.55.1393596969746; Fri, 28 Feb 2014 06:16:09 -0800 (PST)
Received: by 10.204.64.68 with HTTP; Fri, 28 Feb 2014 06:16:09 -0800 (PST)
In-Reply-To: <9EF94792-38EE-4671-833A-D5FC1F7FFE3C@cisco.com>
References: <CA+YzgTuUQzfjnjTWdya7xgpytB+nBvY_d-Sx4faqUJY3Md9h5Q@mail.gmail.com> <CF323F23.9C8CD%zali@cisco.com> <CA+YzgTtxz-aQXx8d5EV0kP05DV9NCAdUdbAmV0pK7nECo+KvFw@mail.gmail.com> <9EF94792-38EE-4671-833A-D5FC1F7FFE3C@cisco.com>
Date: Fri, 28 Feb 2014 09:16:09 -0500
Message-ID: <CA+YzgTvd+U9o69k2b+yW6PTK+0FPN1HNEZTt3zoHH=6aHmSsjQ@mail.gmail.com>
From: Vishnu Pavan Beeram <vishnupavan@gmail.com>
To: "Giovanni Martinelli (giomarti)" <giomarti@cisco.com>
Content-Type: multipart/alternative; boundary="047d7b874e4c57a7fa04f37814a9"
Archived-At: http://mailarchive.ietf.org/arch/msg/ccamp/_hR2mRx8Fgqv11YMY8XqlHgmeWA
Cc: "ccamp@ietf.org" <ccamp@ietf.org>
Subject: Re: [CCAMP] Network Assigned Upstream Label - Draft Update
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 28 Feb 2014 14:16:14 -0000

Giovanni, Hi!

Can you please elaborate on why you think the LABEL_SET having good labels
help in this context/argument? If the upstream-node doesn't guess right
(when picking the upstream-label), you'll get a PATH-ERR back with the
ACCEPTABLE_LABEL_SET. And this would happen for every setup request.
Wouldn't you call this a compromised solution?

Regards,
-Pavan


On Fri, Feb 28, 2014 at 7:54 AM, Giovanni Martinelli (giomarti) <
giomarti@cisco.com> wrote:

>  Hi Vishnu,
>
>  On 28 Feb 2014, at 13:26, Vishnu Pavan Beeram <vishnupavan@gmail.com>
> wrote:
>
>  (2) The use of Label-Set/Acceptable Label-Set was meant to be used for
> exceptions. Using it always for every setup request is a compromised
> solution.
>
>
>  At the time we discussed the wson signaling (
> http://tools.ietf.org/html/draft-ietf-ccamp-wson-signaling-06), the
> acceptable label set was considered good enough. Not sure it comes into
> play at every request since your label_set should have reasonably good
> labels.
>
>  Cheers
> G
>