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 12:58 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 3F03512D5AB; Wed, 6 Jul 2016 05:58:34 -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 5ht5RsnkBPIZ; Wed, 6 Jul 2016 05:58:32 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (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 61A9412D1A5; Wed, 6 Jul 2016 05:58:32 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id f126so172733627wma.1; Wed, 06 Jul 2016 05:58:32 -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=VQzCZkpEPhTfLUJf7nWlZAPAbubn3TWRCwdQJOx9KR8=; b=cFGngQV2GTXuwKMj4BySRMl/7Z+wUP+MRfBXOKSm6cUR6S3WcsVGC85H/fnQxIWQji xAgsqDtUskiooC/MXE8gWvd5aDTHYJ96Zs8ly8oJsyBRqLC3e2/DhUIMqw1hqAZ31r69 iGGJBK1k13FeHiCapuSdtXaux9tbjF/fYkzfwCpKy6OSl82DHmuFvdxVIwXJqbYevEAQ yzfUrrTvV6AGRC+Y1tIzXphG5Bo21mqYNr1psgpdZJZEmGNpuI8GeFn5niD8OKy3uq1w 0KK2C1j7hQum2jm3V2ko46l5JRMGwxgvhgWTxnmxebV/z704KIj7dwkQaZBwj2nwEXzL HmZA==
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=VQzCZkpEPhTfLUJf7nWlZAPAbubn3TWRCwdQJOx9KR8=; b=jIIKXn5LYjr0KLRxNhExD8S8XyesebZjwwh3RqTBp8V8DBp0xJB1Vju8VE5N1H27m3 X1T2KipaG3AtOL2KL68kIlwo4wBlUfegJ2OA1yqljvsXwWSf7Tdq3oLDuzcoH2IIRXs9 v2jtqjE+ovkjdfCv1aMVJGYlVnbuejAFJnImOB5N+UCBb2XgXc0LdBHY06WsI3vf+bV+ spWcp3bCU6mLk11h5RQ2Q9p9DJLjLNVq5DecGQmYFGi5Oqdq25tp6ZwRBaf7Qx3mxZbE VzO2Lj/pX5S53q2ox6Lov06NCvrp+t2JD6wDXHWmSxXef5jcAo2A8oZwRIN5RLNXpW4I eV5Q==
X-Gm-Message-State: ALyK8tLmuo7+oJgqJage2UiN4PCQD4jpRMbBPMT3AHFTbY8UZMzUoE6uBIjEWVa/EWbo3w==
X-Received: by 10.28.226.138 with SMTP id z132mr20186833wmg.97.1467809910434; Wed, 06 Jul 2016 05:58:30 -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 b187sm384427wmg.15.2016.07.06.05.58.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jul 2016 05:58:29 -0700 (PDT)
To: Mirja Kuehlewind <ietf@kuehlewind.net>, The IESG <iesg@ietf.org>
References: <20160705163846.22350.79584.idtracker@ietfa.amsl.com> <ac40c272-8513-fc14-fa95-4a3ddc7231f1@gmail.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <7b9f5b06-0c05-bda2-75ec-ebee6210ba60@gmail.com>
Date: Wed, 06 Jul 2016 13:58:25 +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: <ac40c272-8513-fc14-fa95-4a3ddc7231f1@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/pals/VUwt9YxpnLR14khciGy7S4uZ1Ho>
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 12:58:34 -0000


>>
>> ----------------------------------------------------------------------
>> 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.

Thinking about this some more, we could say:

    Either the C-bit or the S-bit MUST be set.
    the C-bit and S-bit are mutually exclusive from each other, and 
cannot be
    set in the same message.  Otherwise, a Label Release message with
    status code set to "The C-bit and S-bit can not both be set" (TBD5)
    MUST be replied, and the PW will not be established.

We could introduce an additional error message, but it's probably 
adequate to
say:

    Either the C-bit or the S-bit MUST be set.
    The C-bit and S-bit are mutually exclusive from each other, and 
cannot be
    set in the same message.  In the case of either error, a Label 
Release message with
    status code set to "The C-bit and S-bit error" (TBD5)
    MUST be replied, and the PW will not be established.

If parametrised messages are allowed I would say:

"The C-bit and S-bit error [<C-bit>, <S-bit>]"

Since zero or two bits are clearly an implementation error, I am not
convinced that we need to do more than flag it up sufficiently that
the an implementer can figure out what they got wrong.

Stewart