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

Leeyoung <leeyoung@huawei.com> Mon, 04 August 2014 20:29 UTC

Return-Path: <leeyoung@huawei.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 DF3DA1A02FF for <ccamp@ietfa.amsl.com>; Mon, 4 Aug 2014 13:29:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.202
X-Spam-Level:
X-Spam-Status: No, score=-3.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 hXLXT_MEd00R for <ccamp@ietfa.amsl.com>; Mon, 4 Aug 2014 13:29:22 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5440E1A0201 for <ccamp@ietf.org>; Mon, 4 Aug 2014 13:29:21 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BKW59718; Mon, 04 Aug 2014 20:29:19 +0000 (GMT)
Received: from DFWEML703-CHM.china.huawei.com (10.193.5.130) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 4 Aug 2014 21:29:18 +0100
Received: from DFWEML706-CHM.china.huawei.com ([169.254.8.145]) by dfweml703-chm.china.huawei.com ([169.254.5.198]) with mapi id 14.03.0158.001; Mon, 4 Aug 2014 13:29:05 -0700
From: Leeyoung <leeyoung@huawei.com>
To: Lou Berger <lberger@labn.net>, CCAMP <ccamp@ietf.org>, "draft-ietf-ccamp-wson-signaling@tools.ietf.org" <draft-ietf-ccamp-wson-signaling@tools.ietf.org>
Thread-Topic: [CCAMP] Still have issues in WSON Processing HOP Attribute Encoding in draft-ietf-ccamp-wson-signaling-08
Thread-Index: AQHPrmaoHNVf7qg6iEe4xgIIIKwAz5vA5iOA
Date: Mon, 4 Aug 2014 20:29:04 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E1729C08671@dfweml706-chm.china.huawei.com>
References: <53DD040A.6000809@labn.net>
In-Reply-To: <53DD040A.6000809@labn.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.192.11.102]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/ccamp/p6o8W8aegqou2AtR_237ZGXsjR4
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:29:25 -0000

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

-----Original Message-----
From: CCAMP [mailto:ccamp-bounces@ietf.org] On Behalf Of Lou Berger
Sent: Saturday, August 02, 2014 10:30 AM
To: CCAMP; draft-ietf-ccamp-wson-signaling@tools.ietf.org
Subject: [CCAMP] Still have issues in WSON Processing HOP Attribute Encoding in draft-ietf-ccamp-wson-signaling-08

All, (WG, Authors, Young, Giovanni),
	It looks like an unintended encoding change made it into -08 of the draft, or there remains some confusion in the intended encoding.  The topic traces back to a discussion in March, see http://www.ietf.org/mail-archive/web/ccamp/current/msg15894.html.  To move forward, I'd like to ensure that the authors and any other interested party, i.e., existing and future implementors, are on the same page.

I'd like to focus on the intent and the what document should says as opposed to how we got here, i.e., past confusion.  We need to ensure that the draft accurately documents the Authors/WG intent.  I am not trying to propose any technical changes at this very late date.

YOUNG>> Agree. 

The area of the document in question is sections 4.2-4.4 and relates to how the so called sub-TLVs are encoded and processed.  The key text in question, from rev -07 is:
   To target a specific node, this section defines a WSON_Processing
   object as part of the LSP_REQUIRED_ATTRIBUTE and follows procedures
   defined in [RSVP-RO].

Looking back on the -07 and the March mail thread, the "sub-TLVs"
defined in Section 4.3 and 4.4 should be carried as Attribute TLVs in LSP_REQUIRED_ATTRIBUTES Objects, and not in ERO_HOP_ATTRIBUTE Subobjects. Also that there actually is no WSON_Processing object carried on the wire.

Authors, Young, Giovanni:

    Please confirm if this is correct.  If not, please clarify what was
    intended in the -07 rev of the document.

YOUNG>> Correct. It looks like there was a confusion between [RFC5420] and [RSVP-RO]. It seems that it makes no sense associating LSP_REQUIRED_ATTRIBUTES Object with [RSVP-RO] as [RSVP-RO] talks only about ERO_HOP_ATTRIBUTE subobject which is completely irrelevant with LSP_REQUIRED_ATTRIBUTES object. 

Assuming it is correct I think it remains unclear what it means for a LSP_REQUIRED_ATTRIBUTES Object (and not an ERO_HOP_ATTRIBUTE subobject) to "follows procedures defined in [RSVP-RO]."

YOUNG>> Yes. Please see my comment below. 

Authors, Young, Giovanni:

   Can you clarify what specific procedures defined in [RSVP-RO] are
   to be applied to the LSP_REQUIRED_ATTRIBUTES Objects?

I think it should be possible to align the draft text fairly easily once the intent is clear, and I'm happy/plan to propose specific text.

YOUNG>> Replacing [RSVP-RO] with [RFC5420] will solve the problem discussed here. 


Thanks,
Lou

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