Re: [arch-d] New Version Notification for draft-iab-for-the-users-01.txt

S Moonesamy <sm+ietf@elandsys.com> Thu, 23 January 2020 11:28 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A310C12003E for <architecture-discuss@ietfa.amsl.com>; Thu, 23 Jan 2020 03:28:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 8r5uIkLBBZlI for <architecture-discuss@ietfa.amsl.com>; Thu, 23 Jan 2020 03:28:34 -0800 (PST)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id C5FBD12001E for <architecture-discuss@ietf.org>; Thu, 23 Jan 2020 03:28:34 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.1.174]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 00NBSKjl003112 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Jan 2020 03:28:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1579778912; x=1579865312; i=@elandsys.com; bh=BpIVQTTqUro+XsJ5VldEWcbOPmCzMScFNl0XA/4cTY0=; h=Date:To:From:Subject:In-Reply-To:References; b=USe1MsisKes9r3Lb+GRgEfMyKdS34G6Gz4AUSScq75kJSlN9PcRSDa4PSR4ZyAL+F oFCfDdW488RzV3KeoNAC8ZxUbapVAb7oOdx3GG78CLucAgpMQkPvCBn1Wthopa7lz1 Sfw6R/zDPt+hiur5Nf+fm+0ck4UKjM6JjSyu8ReA=
Message-Id: <6.2.5.6.2.20200123013903.0be41930@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 23 Jan 2020 03:25:55 -0800
To: Mark Nottingham <mnot@mnot.net>, architecture-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <61975615-0DB9-4683-84B5-A4BB5441C467@mnot.net>
References: <157403781873.6404.6154827441040413193.idtracker@ietfa.amsl.com> <01246A3C-31EC-4B7B-841D-F799EEFADCB8@mnot.net> <227662299.12784.1575991106819@appsuite-gw2.open-xchange.com> <C74D5288-709B-46E3-B9F9-4FDE0234C451@fugue.com> <429195684.13066.1575996064551@appsuite-gw2.open-xchange.com> <0C729385-1361-460C-9C16-E1BE1680A3E6@fugue.com> <1100636076.15285.1576072588087@appsuite-gw2.open-xchange.com> <4A034991-E5C8-4797-B6BF-9484BB2FA614@fugue.com> <31473650-0872-4EFE-A99C-E3DD4CDBC700@cisco.com> <alpine.LRH.2.21.1912130913480.8529@bofh.nohats.ca> <326C92A0-5F29-411D-99DE-7C785CF73EE7@cisco.com> <6.2.5.6.2.20191214065306.11c9aa98@elandnews.com> <61975615-0DB9-4683-84B5-A4BB5441C467@mnot.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/8HJrAsflFrUXg3UFU9x5cFiDbjY>
Subject: Re: [arch-d] New Version Notification for draft-iab-for-the-users-01.txt
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2020 11:28:36 -0000

Hi Mark,
At 06:13 PM 19-01-2020, Mark Nottingham wrote:
>Well spotted.
>
>I've modified the text in my copy:
>
>"Even before the IETF was established, the Internet technical 
>community has focused on user needs since at least {{?RFC0001}}, 
>which stated..."

Thanks for the feedback.

I took a look at -02.  I would like to clarify my opinion is not 
representative of the views of the users from any region.

There is an ongoing discussion in an IRTF Research Group about the 
third paragraph in Section 1 (re. it has unavoidably become 
profoundly political ...)

Section 3 adds a question mark on RFC 3935.

Section 4.1 uses the terms "broader Internet community" and "greater 
Internet community".  Do those qualifiers change the meaning of 
"Internet community"?  If so, why are they not used in Section 4?

There is the following text in Section 4.1: "Government 
representatives sometimes participate in the IETF community."  When 
are those representatives representative of end-users?

There is the following near the end of Section 4.1: "we should 
remember that the RFC series are Requests For Comments".  I requested 
that my comments on a draft be ignored as an IETF Area Director gave 
me a very original response.  If that were to reflect the Internet 
Engineering Steering Group's position on comments, I doubt that IETF 
Stream could be viewed as conducive for request for comments.

I agree that merely saying that something is harmful (Section 4.3) is 
not a convincing argument.  However, is it reasonable to expect an 
end-user to explain how the technical specification causes, or might 
cause, "harm"?

Regards,
S. Moonesamy