Re: [Pce] Martin Vigoureux's Discuss on draft-ietf-pce-gmpls-pcep-extensions-14: (with DISCUSS)

"Adrian Farrel" <adrian@olddog.co.uk> Thu, 11 April 2019 12:01 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D380120131; Thu, 11 Apr 2019 05:01:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 WKfGs503a2jW; Thu, 11 Apr 2019 05:01:06 -0700 (PDT)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6464D120048; Thu, 11 Apr 2019 05:01:06 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta6.iomartmail.com (8.14.4/8.14.4) with ESMTP id x3BC14fd021631; Thu, 11 Apr 2019 13:01:04 +0100
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 004922203D; Thu, 11 Apr 2019 13:01:04 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs1.iomartmail.com (Postfix) with ESMTPS id E5E992203B; Thu, 11 Apr 2019 13:01:03 +0100 (BST)
Received: from LAPTOPK7AS653V ([87.114.253.143]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id x3BC12b5026106 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 11 Apr 2019 13:01:03 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Martin Vigoureux' <martin.vigoureux@nokia.com>, 'The IESG' <iesg@ietf.org>
Cc: draft-ietf-pce-gmpls-pcep-extensions@ietf.org, 'Julien Meuric' <julien.meuric@orange.com>, pce-chairs@ietf.org, pce@ietf.org
References: <155498207568.12802.3705482162496355990.idtracker@ietfa.amsl.com>
In-Reply-To: <155498207568.12802.3705482162496355990.idtracker@ietfa.amsl.com>
Date: Thu, 11 Apr 2019 13:01:03 +0100
Organization: Old Dog Consulting
Message-ID: <045201d4f05e$3cddfc00$b699f400$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AQHOSuRYJrQnCtmOG6vq75PF1vNWxqZEJkng
X-Originating-IP: 87.114.253.143
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-24544.007
X-TM-AS-Result: No--5.265-10.0-31-10
X-imss-scan-details: No--5.265-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24544.007
X-TMASE-Result: 10--5.265500-10.000000
X-TMASE-MatchedRID: QW5G6BKkLTrxIbpQ8BhdbL0dPFETpBAH56ZiKymUcU7b6Y+fnTZUL34M 2QICXpHjMXEn4M+GcWvPDExIjNkthnnEICAqqFlBlVHM/F6YkvSsBP5mv7Dua4KwF4K/wIz9MC0 ++gksI5BXlG+b8fa+cOuPA2P8B67NwpNb3yM/DA3N+qWlu2ZxaKwxCUEjPydtd6RFRE7vKfHvjh geV9O8lNeiPxhabPECyvkBV2KfhrWqYtZoSKdB4fi9hrAKwILaC3HuWcgyQCZaW2Ktn+I8/lN/2 7EBZW0V585VzGMOFzCWc/0wwBlx2lOm2gN+nomsxEHRux+uk8jHUU+U0ACZwE51q2/dMDfIWAbK 7E5/iE7wE5GOLkKW7tmUWd2JR9wxnqg/VrSZEiM=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/HtLjmYtuqwV5ogTTfNJ8CyQ0YHc>
Subject: Re: [Pce] Martin Vigoureux's Discuss on draft-ietf-pce-gmpls-pcep-extensions-14: (with DISCUSS)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Apr 2019 12:01:10 -0000

Hi Martin,

It was a general policy during the development of PCEP to make space for flags in the various objects, and this has turned out to be useful in some cases.
So, I think the authors were continuing that approach.

But I agree, if you make the field, you should make the registry.

Thanks,
Adrian

-----Original Message-----
From: Martin Vigoureux via Datatracker <noreply@ietf.org> 
Sent: 11 April 2019 12:28
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-pce-gmpls-pcep-extensions@ietf.org; Julien Meuric <julien.meuric@orange.com>; pce-chairs@ietf.org; julien.meuric@orange.com; pce@ietf.org
Subject: Martin Vigoureux's Discuss on draft-ietf-pce-gmpls-pcep-extensions-14: (with DISCUSS)

Martin Vigoureux has entered the following ballot position for
draft-ietf-pce-gmpls-pcep-extensions-14: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pce-gmpls-pcep-extensions/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Hi,

thanks for this document. I have a discuss point that shouldn't be difficult to resolve:

Why do you define a flag field in the GMPLS-CAPABILITY TLV if you don't have any flag?
I guess the easy answer is that there might be some in the future.
If so, I tend to think that creating a registry for that field would be a good thing to do now.

-m