Re: [CCAMP] Still have issues in WSON Processing HOP Attribute Encoding in draft-ietf-ccamp-wson-signaling-08

Lou Berger <lberger@labn.net> Mon, 04 August 2014 20:43 UTC

Return-Path: <lberger@labn.net>
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 0D4561A0318 for <ccamp@ietfa.amsl.com>; Mon, 4 Aug 2014 13:43:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 V1ESLUnTxvC2 for <ccamp@ietfa.amsl.com>; Mon, 4 Aug 2014 13:43:22 -0700 (PDT)
Received: from gproxy7-pub.mail.unifiedlayer.com (gproxy7-pub.mail.unifiedlayer.com [70.40.196.235]) by ietfa.amsl.com (Postfix) with SMTP id A2AE81A02F4 for <ccamp@ietf.org>; Mon, 4 Aug 2014 13:43:22 -0700 (PDT)
Received: (qmail 21141 invoked by uid 0); 4 Aug 2014 20:43:20 -0000
Received: from unknown (HELO cmgw4) (10.0.90.85) by gproxy7.mail.unifiedlayer.com with SMTP; 4 Aug 2014 20:43:20 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw4 with id aqjC1o00d2SSUrH01qjFlC; Mon, 04 Aug 2014 20:43:18 -0600
X-Authority-Analysis: v=2.1 cv=OcELUHjY c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=WrhVjQHxoPwA:10 a=KAMjFvWR21EA:10 a=kC4BAXwS1W4A:10 a=HFCU6gKsb0MA:10 a=8nJEP1OIZ-IA:10 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=XX4cy0OB9ZlMihc3UogA:9 a=wPNLvfGTeEIA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID; bh=FrQyhlsFjhBlgil5NujhrHU87tXirxEr7zkQho9rfIo=; b=JWwPmkTNZ6Ucpivcof5rEKqsH8sEc5RocTHSSph2Gu8ojk4ja+6RUmjRrMdQoJu3PX0vkgnHV5STTgonF9fQupeMRYWxC01n9um90JcYsgTWyL3zMziJRs2UOtbofDRc;
Received: from box313.bluehost.com ([69.89.31.113]:59372 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.82) (envelope-from <lberger@labn.net>) id 1XEP69-0008L9-TI; Mon, 04 Aug 2014 14:43:13 -0600
Message-ID: <53DFF088.70506@labn.net>
Date: Mon, 04 Aug 2014 16:43:52 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Leeyoung <leeyoung@huawei.com>, CCAMP <ccamp@ietf.org>, "draft-ietf-ccamp-wson-signaling@tools.ietf.org" <draft-ietf-ccamp-wson-signaling@tools.ietf.org>
References: <53DD040A.6000809@labn.net> <7AEB3D6833318045B4AE71C2C87E8E1729C08671@dfweml706-chm.china.huawei.com>
In-Reply-To: <7AEB3D6833318045B4AE71C2C87E8E1729C08671@dfweml706-chm.china.huawei.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: http://mailarchive.ietf.org/arch/msg/ccamp/CT1kWx9pnlXpz0ombIe-aaokY0U
Subject: Re: [CCAMP] Still have issues in WSON Processing HOP Attribute Encoding in draft-ietf-ccamp-wson-signaling-08
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: Mon, 04 Aug 2014 20:43:24 -0000

Young,
   
On 8/4/2014 4:29 PM, Leeyoung wrote:
> Hi,
>
> Lou, here's my comment on your comment. In a nutshell replacing [RSVP-RO] with [RFC5420] will solve the confusion. 
>
> Please see in-line for details.
>
> Thanks,
>
> Young
So you are saying that Resource Block Information and Wavelength
Assignment Method are encoded end-to-end and *never* have
hop/node/interface specific meaning (as they are each encoded as an
Attribute TLV in an LSP_REQUIRED_ATTRIBUTE object), is this correct?

ARE YOU SURE?  

How do you envision the LSP_REQUIRED_ATTRIBUTE object conveying per-hop
information? (As discussed in section 3.2 and the first paragraph on
section 4.2.)

Lou
....