Re: [Pals] Mirja Kühlewind's Discuss on draft-ietf-pals-mpls-tp-pw-over-bidir-lsp-08: (with DISCUSS and COMMENT)

Stewart Bryant <stewart.bryant@gmail.com> Wed, 06 July 2016 11:50 UTC

Return-Path: <stewart.bryant@gmail.com>
X-Original-To: pals@ietfa.amsl.com
Delivered-To: pals@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 446E712D626; Wed, 6 Jul 2016 04:50:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 9qgQvBGiHZ4C; Wed, 6 Jul 2016 04:50:46 -0700 (PDT)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1340912B02D; Wed, 6 Jul 2016 04:50:46 -0700 (PDT)
Received: by mail-wm0-x231.google.com with SMTP id z126so108602692wme.0; Wed, 06 Jul 2016 04:50:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=eF2K/xuH70fwaeg3FFtBw4RiwlnP7OU+ZXbhpPZ6vxQ=; b=hIui3IPlIdICCP2D+D0xaca/Cknir51MF5OM4zad7sJFtKCz1/BX3qaKMF0uQMkm1s QG9tDYl2u6GVUn31kP/jswKetOvAuyNuL7lfCAWwD/Ghd2Pn0CGxvK2saZhkq2OM2MXu 5JN/rXp2pKTTfa68ATJlN8mxp5U1RkmJX8YkcdSPmi+x5iB/5Mgi39EsvXgyatYhKjIj tGdBmdmMHLc2tvU1LdVellJ/oyHYvO1oMiVMweC7LQe6L0Mvk7mHNL6FRMsYWTatdr7x UAWAXjs1pe2YW6slxAVx32094i0cIr1z63+GlvWqgKp1s3Tdnl8BgE8xsMyaNyQKsxlS J5gw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=eF2K/xuH70fwaeg3FFtBw4RiwlnP7OU+ZXbhpPZ6vxQ=; b=Jvuy57/bGL3JqNv8jlBdqv2WtGmdnJZ+ou+OzDGFViiH33I3Tw6FWvj65kXn7Pek+5 tPynZBIacMyGprX/IMK0eSt9zZR3e00UJYtfK5g3AcH1/yo5El4IRA8NcutxBIQS7TRh ow5tJhGzAhQ8a8uAD3ZFKm15jdJPXGT7gFTKIhATsA1opNfSnvZWNkBwHbnzPOYo/wCw zeTluzpTKNmQsHo3YCJlbcotBlWU2mZdeI6giC1WQucGvY4k3ffZp5YF0H5AEPFTCubE VnEBqGOdEp+Hj7np66r+v4HcUFiQWlAACOSfyZaj+qeJCy8jBDFDhcGMyi8EkOkLwyJY ZoHg==
X-Gm-Message-State: ALyK8tIkCDH3ZM2QhiJq+OQJ/b5vhsM1F5cYitsLFApAfBoXJ7tORo/ECxDmMDby8to2OA==
X-Received: by 10.194.157.162 with SMTP id wn2mr22317956wjb.103.1467805844502; Wed, 06 Jul 2016 04:50:44 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id ib10sm5835920wjb.31.2016.07.06.04.50.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jul 2016 04:50:42 -0700 (PDT)
To: Mirja Kuehlewind <ietf@kuehlewind.net>, The IESG <iesg@ietf.org>
References: <20160705163846.22350.79584.idtracker@ietfa.amsl.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <ac40c272-8513-fc14-fa95-4a3ddc7231f1@gmail.com>
Date: Wed, 06 Jul 2016 12:50:36 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <20160705163846.22350.79584.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/pals/ojs15dROHvPzlCi7uQgD4FhWbbI>
Cc: pals-chairs@ietf.org, draft-ietf-pals-mpls-tp-pw-over-bidir-lsp@ietf.org, pals@ietf.org
Subject: Re: [Pals] Mirja Kühlewind's Discuss on draft-ietf-pals-mpls-tp-pw-over-bidir-lsp-08: (with DISCUSS and COMMENT)
X-BeenThere: pals@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Pseudowire And LDP-enabled Services dicussion list." <pals.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pals>, <mailto:pals-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pals/>
List-Post: <mailto:pals@ietf.org>
List-Help: <mailto:pals-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pals>, <mailto:pals-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2016 11:50:48 -0000

Mirja,

I would like to pick up a couple of points related to your discuss and 
comments.

On 05/07/2016 17:38, Mirja Kuehlewind wrote:
> Mirja Kühlewind has entered the following ballot position for
> draft-ietf-pals-mpls-tp-pw-over-bidir-lsp-08: 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-pals-mpls-tp-pw-over-bidir-lsp/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> I think the protocol specification is not complete:
>
> - What happens if none of the two S and C bits are set?
Since the text specifically states that they are mutually exclusive, 
that would be
an implementation error. I don't think that it is within the scope of 
this draft to
state what should happen when there is an implementation error.

>
> - What happens if more the one sub-TLV is present?
As Mach says later in the thread that is an allowable construct. If the TLVs
conflict with each other that is also a protocol implementation error and
out of scope of the document.

>
> Actually I think that the protocol design is more complicated than needed
> and simplifying it would resolve these error cases. But as that's not a
> DISCUSS reason, please see more detailed comments below!

The PALS WG was satisfied with the original design, which is perfectly 
viable.

As you say that is not a valid reason to issue a discuss.


>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> A few questions/comments:
>
> 1) The shepherd writeup says: "An IPR discolusure has been filed and the
> WG has not remarked on this."
>      Does this mean the wg is not aware of it or it is aware and nobody
> commented?

Our standard process is to ask the authors (requiring an explicit reply 
from each)
and to ask the WG (with no reply within a certain time an implicit 
negative) if they
need to declare any IPR that has not been already declared. This was 
last done here:

https://www.ietf.org/mail-archive/web/pals/current/msg00621.html

When IPR is disclosed secretariat notify the WG if the draft is a WG draft.

The Chairs do not point out correctly disclosed IPR, we assume that people
will read the list or check the datatracker.

The shepherd's note indicates that as far as I am aware, no one 
expressed any concern
about the IPR disclosure, either on list or to direct to a chair.

Best regards

Stewart