Re: [mpls] Mirja Kühlewind's No Objection on draft-ietf-mpls-flow-ident-06: (with COMMENT)

Stewart Bryant <stewart.bryant@gmail.com> Thu, 01 March 2018 19:55 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 2D0D512FA82; Thu, 1 Mar 2018 11:55:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 GyL840wVi3f3; Thu, 1 Mar 2018 11:55:21 -0800 (PST)
Received: from mail-wr0-x236.google.com (mail-wr0-x236.google.com [IPv6:2a00:1450:400c:c0c::236]) (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 D820B12FAC3; Thu, 1 Mar 2018 11:55:19 -0800 (PST)
Received: by mail-wr0-x236.google.com with SMTP id k9so7817897wre.9; Thu, 01 Mar 2018 11:55:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=3fsW5AczBiB1f5mo7cWwTqWFDwsobQ1zX+MuZQZnryY=; b=QOJtqxG2LOYpZgox8kL/qnQCz71wKbNFk+y6qzOHihuyjRcDUjArYjo12Z0pCPhdOD 8FUk7Lmp9MPKHUlgMKDJAu4lrxXiaaa4PdzRHdim63162sOKOE0UE8grKitWSEJ/vl47 3+1S/UCs7Cen+xB25D/Hr/OXJ354cJ8BVD7YLvpUjCB2TZRLcreVw/z/0cocOZXHyQ1M 9km7bOkXj0wIRIwvp0HNv/3EdZI/bctSjiOnKAdTbaX/QxH5kKbloUEcvuawZUZ6tPfB Xi2PTNe6JqCI75LQ49sh95cjOAj8mnP5YVHweqHYPpqocus1Yh2HGKE6JJJXPPLtHVEb bP6w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=3fsW5AczBiB1f5mo7cWwTqWFDwsobQ1zX+MuZQZnryY=; b=p+iTIRJvtmrxaBTNh/eJBNhfvIesEGQmlFf18S50f/JGx/ufED4TCQ2U6RcFm5mYfe LOfDgOe9XDz1pndouWIXe4qEMGKGitOi+cSNcwuI2i5Us/B/W+fl5VtFtKPwoZjB4P3D /ZrRIw4GCwDZxMeD1v6695DSqllNV6YtOJNBPRbZwtR3vtIQZ5kcSqfnZiyuFJYT0A2B uT3JY8BjVkvgQoGtdqAiL1Gl+lohbnSXwCKeA1w+Y93GWvhbIxLr2umIIDjYSXMNy9W4 3JChh1EnqU3LL/aTgPcofNvr1sLyc7x41TMlrrbbd3Sbe8iaTOGUJBr1QL4KfMzJc1cF 4U0A==
X-Gm-Message-State: APf1xPBBe/VR0QVR2WE3KKt7PGnAEPqSHzlMDhEi+iBWnmn0uL/YCOK/ yiyRZbBs2iE+xkzjfsTeso/XBG/u
X-Google-Smtp-Source: AG47ELv6yYCu8pMENFs0cBPMKXoEY7XqjR35DwrN1SO99J5md22Vz4V/Hel2mzO3yiauugBZvLL4ow==
X-Received: by 10.223.208.132 with SMTP id y4mr2644194wrh.185.1519934118160; Thu, 01 Mar 2018 11:55:18 -0800 (PST)
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 o94sm7825850wrc.7.2018.03.01.11.55.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Mar 2018 11:55:17 -0800 (PST)
To: =?UTF-8?Q?Mirja_K=c3=bchlewind?= <ietf@kuehlewind.net>, The IESG <iesg@ietf.org>
Cc: draft-ietf-mpls-flow-ident@ietf.org, mpls-chairs@ietf.org, Loa Andersson <loa@pi.nu>, mpls@ietf.org
References: <151508265598.23798.2546185048264995512.idtracker@ietfa.amsl.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <abcc329c-571c-02f8-b0c7-ad04698af4c3@gmail.com>
Date: Thu, 1 Mar 2018 19:55:16 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <151508265598.23798.2546185048264995512.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/QdOWZLkaeeNmwB6tJ3alYS-lhCA>
Subject: Re: [mpls] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-?= =?utf-8?q?ietf-mpls-flow-ident-06=3A_=28with_COMMENT=29?=
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
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, 01 Mar 2018 19:55:35 -0000

Hi Mirja,

Thank you for these comments.

MPLS engineers tends to use the terms application in a wider context 
than just application layer applications.

However the clarification is useful, so I have updated the text accordingly.

Best Regards

Stewart


On 04/01/2018 16:17, Mirja Kühlewind wrote:
> Mirja Kühlewind has entered the following ballot position for
> draft-ietf-mpls-flow-ident-06: No Objection
>
> 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-flow-ident/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> I'm uncertain about the archival value of this document in the RFC series as
> the document seems to be written rather for wg-internal consumption only;
> however, I will not object to its publication.
>
> One additional minor comment in section 5:
> CURRENT:
> "An example of such a fine grained case might be traffic
>     from a specific application, or from a specific application from a
>     specific source, particularly if matters related to service level
>     agreement or application performance were being investigated."
>
> Besides the duplication nit, I would like to suggest the following small change:
> PROPOSED:
> "An example of such a fine grained case might be traffic
>     belonging to a certain service or from a
>     specific source, particularly if matters related to service level
>     agreement or application performance were being investigated."
>
> I'd say "service" is less specific than "application" and includes such things
> like e.g. a video service that is offered by the ISP.
>
>