IETF Logo Mail Archive

Re: [mpls] Alia Atlas' Yes on draft-ietf-mpls-rfc6374-udp-return-path-04: (with COMMENT)

Stewart Bryant <stewart.bryant@gmail.com> Thu, 07 April 2016 12:12 UTC

Return-Path: <stewart.bryant@gmail.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C59C512D84E; Thu, 7 Apr 2016 05:12:11 -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 oym2yucYe7Ap; Thu, 7 Apr 2016 05:12:10 -0700 (PDT)
Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (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 88C3A12D83C; Thu, 7 Apr 2016 05:12:05 -0700 (PDT)
Received: by mail-wm0-x241.google.com with SMTP id n3so20958003wmn.1; Thu, 07 Apr 2016 05:12:05 -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=3Mp4IRzYDTk4chvFxdc9VTVvecpu8DtW0bvMw69BUJw=; b=CiAGmMZ0zE72Kstnam1S/JBg1f/9vQMUJ4pYui+WjiN77QRepKT3wywCj2SzpUXefL f72Y0FZp4qbSjdVVkwZEdcaVzb+uu3DxtdLYLjiyecdl9AzRvbuBBre+w6wt3ORDfiZD Bksh91CkLTgzDKeuxWy0ZkJfPqW0hETH95k6ZMFHR721MwMXDPSqn98rwaVmF/pkcAo5 x4B10WSpPXC5NxNyzaZvPggM0axHxVKQ1zZ5B5Huui1aOJCdfQEQCHvldgRCvXF1nLmT QjFJ/PewH66QbaW6F3jm8Cexn3/p9BeyncTu7miJKorM4060c1Jyq9wQQLwnzk66HU19 noIA==
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=3Mp4IRzYDTk4chvFxdc9VTVvecpu8DtW0bvMw69BUJw=; b=CDTmvnizRGGwf19BFD3S3lB1SFgECX0ImymiFybt5KmtWssMh31CvGLUGxNNp7NKOO 5DyWAnIZk90jN1el6zYdxcR3dP5YJP+91cqFd0lZpTz4RFUTW1ZnVEDR+uamdSQPBcSf gtclWbXx5Ii1+i0NPH3qYN6XMqdd9GY3gkP1Rd886m3b0KPauLeR/Ccin7R7dx5TDCXa 4cGg3UzMTjk0yzQeWUtoOMLvSsEHwM5Aqh1rZQC1lM6nmwO7dKvpA+KHW5w9CyrkBlvs oBX4uWmISjsSrHlj2SbYEMwWArz18wWDRjNJy99Whq4UyTsRDqWr2JdwhagXiTQDuM+g h8ng==
X-Gm-Message-State: AD7BkJKeVe5K/GWA1FwyY8Yaru1ymuOue6D6QPFKaOowNv9muFfVZvU8fIH8Wd0vvUCOaQ==
X-Received: by 10.28.125.8 with SMTP id y8mr30852649wmc.87.1460031124130; Thu, 07 Apr 2016 05:12:04 -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 m134sm8678123wmd.14.2016.04.07.05.12.02 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 07 Apr 2016 05:12:03 -0700 (PDT)
To: Alia Atlas <akatlas@gmail.com>, The IESG <iesg@ietf.org>
References: <20160105163714.22863.53937.idtracker@ietfa.amsl.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <57064E91.2090609@gmail.com>
Date: Thu, 07 Apr 2016 13:12:01 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <20160105163714.22863.53937.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/IGxHKr3I996EHcE7agzvdvSMIcQ>
Cc: mpls@ietf.org, draft-ietf-mpls-rfc6374-udp-return-path@ietf.org, mpls-chairs@ietf.org
Subject: Re: [mpls] Alia Atlas' Yes on draft-ietf-mpls-rfc6374-udp-return-path-04: (with COMMENT)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2016 12:12:12 -0000

I have worked through the RFC2119 language and think it is now right.

I interpret a SHOULD as a caveated MUST so when the caveats are provided in
one part of the text it can be (with a MUST) I think it is safe to use 
SHOULD
elsewhere. Anyway I have had another go at making the intent clearer.

Stewart

On 05/01/2016 16:37, Alia Atlas wrote:
> Alia Atlas has entered the following ballot position for
> draft-ietf-mpls-rfc6374-udp-return-path-04: Yes
>
> 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-mpls-rfc6374-udp-return-path/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> The introduction uses a MUST for the receiver to use the URO, but the
> later text uses SHOULD.
> Could you please clarify and make them the same?
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

v2.23.0 | Report a Bug | By Email