Re: [Int-area] Alissa Cooper's No Objection on draft-ietf-intarea-frag-fragile-16: (with COMMENT)

Joe Touch <touch@strayalpha.com> Mon, 09 September 2019 00:15 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB836120086; Sun, 8 Sep 2019 17:15:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.218
X-Spam-Level:
X-Spam-Status: No, score=-1.218 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 If4RyyOyv4fu; Sun, 8 Sep 2019 17:15:19 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 122F5120059; Sun, 8 Sep 2019 17:15:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=q/6sL0zWIMJqly1Q9M5jqNcOXQ/cBD1mkApXrDH3fPg=; b=Uu7xXF/wA7q45cpayIrmO7bNx Pb80rwat5FNzeuTNTJ+AJ08VJ5AOrqF0T1QFon8R/YhUeklqnRqL62obS/5N6Wp1zP9UPk3Kr/ZWX 01UbUoYAxD6vJQw3N3vUEuaz7zyzXpWExmu871GflOqIPDIEV9YbO6tuSGX/6CjaAkfSQKSHMsVGS G+FqhJgd/MGzC2sqQiz2bt3yYZtaj+E41UhHHTwFweL9JnxKbLsWo3Gh+QhCOjJAlKXDBWiyjG1pY UsUqEo/BJtAUC05W3fh7FJ/6eiHVbAAhRaqfc7h/BRz2veQbaup1YOcPIBO/Pe+xOoGA5DiwnhE9B 8+lW5UNzw==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:63189 helo=[192.168.1.10]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1i77Kr-002YMQ-JB; Sun, 08 Sep 2019 20:15:18 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_077636DB-0E7D-4B03-9FB4-611216512844"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <f8b2e7e6-e73b-bf90-6fe5-fe18e5a206f0@gmail.com>
Date: Sun, 8 Sep 2019 17:15:12 -0700
Cc: Fred Baker <fredbaker.ietf@gmail.com>, Joel Halpern <joel.halpern@ericsson.com>, "draft-ietf-intarea-frag-fragile@ietf.org" <draft-ietf-intarea-frag-fragile@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>
Message-Id: <3F248D34-9A3D-44AB-811D-CA025D15B818@strayalpha.com>
References: <156751558566.9632.10416223948753711891.idtracker@ietfa.amsl.com> <B7C5DF29-92B2-477B-9C30-F47E338038EE@strayalpha.com> <efabc7c9f72c4cd9a31f56de24669640@boeing.com> <9331E721-F7F8-4C22-9BE4-E266726B3702@gmail.com> <7bfbaf5fa12c4a9bac3e46ece5dfdcde@boeing.com> <0BF34BFA-5F30-4EE1-9F5E-18D9ECA8D424@gmail.com> <CALx6S37xhhS5ezhJu6-HQmftwY9cBzuCxeaW9thTbKBa2hizcw@mail.gmail.com> <A8A10E03-6EEC-4F60-A213-7D66084BA754@gmail.com> <09d0dc428430407f8154f40d47a417dc@boeing.com> <67823455-8FCB-4C9E-8B78-41F2E99BDC21@employees.org> <1f5edd49236649929599820764dedb4e@boeing.com> <D80F747F-6F23-45C9-AE8B-5C059C5AC8DE@employees.org> <47aafc6dbef24b2ba76b81f95dbbedcb@boeing.com> <4461d66b-797c-4a14-b721-b6089221f1e1@si6networks.com> <CALx6S34hZX+OdT5yyw3Jh-iHZ3mRNsFuHXsaZnpZHevGaGifrg@mail.gmail.com> <86BA423E-AB96-44E1-9D3D-A792450F8563@gmail.com> <B0DA91E4-867A-424E-BB70-D1C5DF939AAE@strayalpha.com> <f8b2e7e6-e73b-bf90-6fe5-fe18e5a206f0@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/yWCrAweIeYPeBYLkgyNJN49bj2Q>
Subject: Re: [Int-area] Alissa Cooper's No Objection on draft-ietf-intarea-frag-fragile-16: (with COMMENT)
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Sep 2019 00:15:21 -0000


> On Sep 8, 2019, at 1:26 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
>>> 
>>> Wouldn't that require the middle box to become an architectural element?
>> 
>> Yes, but not just “an” (one):
>> 
>> Touch, J: Middlebox Models Compatible with the Internet. USC/ISI (ISI-TR-711), 2016. (Type: Technical Report | Links | BibTeX)
>> 
>>  * https://www.strayalpha.com/pubs/isi-tr-711.pdf <https://www.strayalpha.com/pubs/isi-tr-711.pdf>
> 
> I'll take the liberty of pointing out that we've known for many years that
> there are multiple types of middleboxes and they have multiple facets:
> https://tools.ietf.org/html/rfc3234 <https://tools.ietf.org/html/rfc3234>

Facets are just properties. That doc makes no attempt to describe them as architectural roles.

> 
> So far, we haven't added them to any formal architectural description of
> the Internet, probably because we don't have one.

RFC1122, RFC1123, RFC1812 as standards.

I (and IMO those RFCs) disagree with the position you took in RFC1958, FWIW.

Joe