
From nobody Wed Sep  4 17:47:38 2019
Return-Path: <fgont@si6networks.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 7FAA7120CDF for <architecture-discuss@ietfa.amsl.com>; Wed,  4 Sep 2019 17:47:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.878
X-Spam-Level: 
X-Spam-Status: No, score=-0.878 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 SZj7b_11eAvz for <architecture-discuss@ietfa.amsl.com>; Wed,  4 Sep 2019 17:47:28 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EDB721208FA for <architecture-discuss@iab.org>; Wed,  4 Sep 2019 17:47:27 -0700 (PDT)
Received: from [192.168.1.14] (ppp-94-69-228-25.home.otenet.gr [94.69.228.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id C29198591A; Thu,  5 Sep 2019 02:47:25 +0200 (CEST)
References: <a7b5255b-8570-0e4b-da17-7557e7ca18c1@si6networks.com>
Cc: architecture-discuss@iab.org
From: Fernando Gont <fgont@si6networks.com>
Openpgp: preference=signencrypt
X-Forwarded-Message-Id: <a7b5255b-8570-0e4b-da17-7557e7ca18c1@si6networks.com>
Message-ID: <e1895609-e462-e47a-b408-568a5c5363b1@si6networks.com>
Date: Thu, 5 Sep 2019 03:47:21 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <a7b5255b-8570-0e4b-da17-7557e7ca18c1@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/oDCRGM-Al_bvjGjFV_T3-3T-FdY>
Subject: [arch-d] Fiddling with IP packets in the network, IPv6-style (Fwd: Question about SRv6 Insert function)
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, 05 Sep 2019 00:47:37 -0000

Folks,

There seems to be ongoing working group item in the spring wg
(https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-01)
that essentially proposes the insertion of IPv6 Extension Headers by
middle boxes in the middle of the network, which goes against a very
explicit requirement in the IPv6 spec (RFC8200) -- that notes that EHs
cannot be inserted in the middle of the network.

This begs a number of questions (e.g., how come that one wg is working
on something that goes against a spec that is not under its charter).

But given this is an architecture list, I wonder if anybody has a say on
the topic? (including the IAB). Is that the way IPv6 is expected to
work? What can we expect from IPv6?



-------- Forwarded Message --------
Subject: Re: Question about SRv6 Insert function
Date: Thu, 5 Sep 2019 03:34:09 +0300
From: Fernando Gont <fgont@si6networks.com>
To: Ole Troan <otroan@employees.org>, Fernando Gont <fernando@gont.com.ar>
CC: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, spring@ietf.org
<spring@ietf.org>, 6man@ietf.org <6man@ietf.org>, Suresh Krishnan
<suresh.krishnan@gmail.com>, draft-voyer-6man-extension-header-insertion
<draft-voyer-6man-extension-header-insertion@ietf.org>,
draft-ietf-spring-srv6-network-programming
<draft-ietf-spring-srv6-network-programming@ietf.org>

On 4/9/19 09:58, Ole Troan wrote:
> Fernando,
> 
>>>> Since there have been plenty of attempts to do EH insertion or
>>>> leave the IPv6 standard ambiguous in this respect, and the IETF has
>>>> had consensus that EH insertion is not allowed, I think it would be
>>>> bad, wastefull, tricky, and even dangerous to let a document go
>>>> through the whole publication process, and just rely on the AD to
>>>> keep the "DISCUSS" button pressed.
>>>>
>>>> Put another way: what'd be the rationale for having a draft-ietf
>>>> and have the corresponding wg ship the document with something that
>>>> clearly goes against IETF consensus, and that the relevant AD has
>>>> declared that wouldn't let pass?
>>>
>>> In short, this is not the case. I am *not* the relevant AD for the
>>> SRv6 Network Programming draft. If this document was in 6man I would
>>> have flagged it much earlier like I did for the SRH draft.
>>
>> Sorry, what I meant by "relevant AD" is: "one of the responsible ADs for
>> the spec that's being violated".
>>
>> i.e., isn't there in the IETF process -- whether formal or informal --
>> for this sort of thing to be flagged before documents get too far in the
>> publication process?  ("Hey, this document in your area is actually
>> breaking a spec of one of my wgs" sort of thing...)
> 
> I would prefer that we calmed down a bit on the protocol policing.

Sorry, but this has nothing to do with protocol policing. It has to do
with respecting the consensus this wg and the ietf as a whole had on the
topic. i.e., that EHs must not be inserted in the network.

We'd go into an interesting path to insanity if we publish specs, and
subsequently publish conflicting specs that simply ignore previous ietf
consensus.

If folks want to do EH insertion, the #1 step is to publish a document
that updates RFC8200 such that the "EHs must not be inserted..." is
replaced with something else or eliminated.



> We know that header insertion breaks unsuspecting source hosts if done by the network.
> It breaks (at least) PMTUD, ICMP errors and AH.
> 
> What we have said in the past is; explain how those issues are dealt with or do not apply to your proposal.

That's what you and others may have said or thought. But the consensus
is what's in the standard (RFC8200). And the standard says that EHs
cannot be inserted in the network. If you want to do it, the first step
is to update RFC8200.



> And some form of "doing on behalf of" is not necessarily problematic.

It is rightaway problematic specs-wise when it violates a crystal-clear
requirement in RFC8200, that we arrived to after a very heated debate,
and lots of enegery and time from all the involved people.

The fact that after all the long story behind publication of rfc8200 as
standard (and the ongoing srv6 document we're doing here, which was
adopted on the condition that it wouldn't do eh-insertion), we can live
with other wgs violating specs that we produced here with so much effort
and time, is kind of amusing.

If folks want to allow EH-insertion (i.e., formally allowing middleboxes
to fiddle with packets), RFC8200 should be updated, and the work should
be done in 6man.

I don't think it's SPRING's call how the IPv6 protocol works.



> It's the "blind" "Thou shalt not do" that I object to. As opposed to arguing on technical grounds.
> 
> Ensuring interoperability is our purpose. Not protect 8200 as if it's a religious text.

My #1 concern (not that I don't have others) is one related to fairness
of the standardization process. I don't think we should simply
rubberstamp anything a big vendor wants to sell, no matter how big the
vendor is, or how much money may be involved.

And if this working group (and the IETF as a whole) published a spec on
which there was consensus, ignoring the spec and doing whatever one
pleases is not the way to go. Firstly, make e the case for updating
RFC8200. Then come up with the proposal to fiddle with packets in the
network.

P.S.: I've never been into the camp of protecting X (whether rfc8200 or
any other document) as if it was religious text. Quite ironically, I
have experienced such religious opposition in 6man itself (for instance,
your argument of "don't fix slaac-renumbering because ipv6 has not been
designed to support flash renumbering" seems pretty much a religious
argument against work that would not result in any major modifications
to any of the protocols involved -- as opposed to EH insertion).

-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Sep  4 17:59:44 2019
Return-Path: <fgont@si6networks.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 424CD1208DF for <architecture-discuss@ietfa.amsl.com>; Wed,  4 Sep 2019 17:59:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 UCqArpSRJ-97 for <architecture-discuss@ietfa.amsl.com>; Wed,  4 Sep 2019 17:59:40 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A1CA1208D8 for <architecture-discuss@iab.org>; Wed,  4 Sep 2019 17:59:40 -0700 (PDT)
Received: from [192.168.1.14] (ppp-94-69-228-25.home.otenet.gr [94.69.228.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 9F1B085FD2; Thu,  5 Sep 2019 02:59:32 +0200 (CEST)
References: <VE1PR03MB542290761D37661F112B9763EEB80@VE1PR03MB5422.eurprd03.prod.outlook.com>
To: architecture-discuss@iab.org
From: Fernando Gont <fgont@si6networks.com>
Openpgp: preference=signencrypt
X-Forwarded-Message-Id: <VE1PR03MB542290761D37661F112B9763EEB80@VE1PR03MB5422.eurprd03.prod.outlook.com>
Message-ID: <534f9b91-7490-667d-b51b-1e11ad00fa98@si6networks.com>
Date: Thu, 5 Sep 2019 03:59:12 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <VE1PR03MB542290761D37661F112B9763EEB80@VE1PR03MB5422.eurprd03.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/DBJno0rzx_ZwOrbpQKJRgmVSZs8>
Subject: [arch-d] Fwd: Questions about draft-ietf-spring-srv6-networking-programming and draft-filsfils-spring-net-pgm-extension-srv6-usid
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, 05 Sep 2019 00:59:42 -0000

FWIW, this is related to my previous email.

We might soon have questions such as "what is ipv6, anyway?", "what is
an ipv6 address"?




-------- Forwarded Message --------
Subject: 	Questions about draft-ietf-spring-srv6-networking-programming
and draft-filsfils-spring-net-pgm-extension-srv6-usid
Date: 	Wed, 4 Sep 2019 22:17:57 +0000
From: 	Andrew Alston <Andrew.Alston@liquidtelecom.com>
To: 	SPRING WG List <spring@ietf.org>, ipv6@ietf.org <ipv6@ietf.org>



Hi All,

 

The following things in the drafts referenced in the subject line are
questions that I feel need to be addressed – since having gone through
these drafts closely in light of some of the comments on the spring list
and cross referenced and checked a number of things – there are a number
of things that significantly concern me.

 

Firstly – in section 3 of the network programming draft an attempt is
made to define SID syntax and semantics.  Now, when cross referenced
with section 2 of the draft, it states “SID: A segment identifier which
represents a specific segment in the segment routing domain.  The SID
type used in this document is IPv6 address (also referenced as SRv6
Segment or SRv6 SID)”

The semantics specified in the network programming draft state that the
high order bits are a locator, the next bits are a function, and the
next bits are arguments to a function.  (Page 6 paragraph 6, “We
represent an SRv6 SID as LOC:FUNC where LOC (locator) is the L most
significant bits and FUNCT (function) is the 128-L last significant bits.

This is quite clearly a re-definition of the IPv6 address semantics as
specified in RFC4291, which that’s that IPv6 addresses are 128-bit
identifiers for interfaces and sets of interfaces (Section 2 of RFC4291)

Section 2.5 of the RFC4291 also states that IPv6 unicast addresses are
aggregable with prefixes of arbitrary bit-length.  Aggregation of
semantics specified in the network programming draft does not seem
possible.  This also has relevance when we consider that SID’s are
indeed addresses, and we find this in
draft-ietf-6man-segment-routing-header in section 4.2

 

Then we move to section 4.13 and 4.14 of the network programming draft,
which define the END.B6-INSERT and the END.B6.INSERT.RED  SID types. 
These types cause transit nodes to insert SRH’s.  They are explicit in
their statement that they can insert a second SRH in a packet that
already  has an SRH.  This conflicts with RFC8200 section 4 which states
that extension headers, except for hop-hop-hop option headers, are not
processed, inserted or deleted by any node along a packet’s delivery
path, until the packet reaches the node.

Further to this, sections 4.21.1 and 4.21.2, when referencing PSP and
USP flavors of the END, END.X and END.T functions all cause transit
nodes to pop the top most SRH, which again, conflicts with RFC8200
Section 4.

Further to this, section 5.2 and 5.3, which define the T.INSERT and
T.INSERT.RED behaviors will cause transit nodes to insert SRH’s – again
– in conflict with RFC8200 Section 4.

 

Then, the following questions are things I would like to see addressed
as concerns the uSID draft.

 

Firstly, I feel that this draft again redefines the IPv6 address
semantics in ways that are very far removed from what is defined in
RFC4291, and that is concerning.

Secondly, I do not understand how
draft-filsfils-spring-net-pgm-extension-srv6-usid is compatible with the
network programming draft.  Due to the semantics of the addressing
specified in the network programming draft, the moment you start
shifting an address in the way this draft specifies, you start to
effectively break the locator/function semantics – and as such,
programmability is only really possible at the end nodes.  Now, the
argument has been put forward that you can retain the full SID stack
while still shifting the address in the uSID approach – however, my
question then becomes, if you do this to retain compatibility with the
network programming draft, do you not lose any point in actually having
uSID at all – since it was designed to address overhead, and the
overhead has just returned again.

 

I really feel that these things need to be addressed – because while I
understand that there are things which are mandatory, and things which
are optional and in the spirit of a draft,  and while I feel that if
something isn’t specified as mandatory but is clearly in the spirit,
there may be occasions where something may be deviated from, what I see
here is an entire redefinition of the address semantics, and multiple
conflicts with segments of RFC8200 – in a consistent and what I consider
to be an egregious manner.

 

I look forward to hearing responses

 

Thanks

 

Andrew

 


From nobody Wed Sep  4 18:10:12 2019
Return-Path: <stephen.farrell@cs.tcd.ie>
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 5E6E41208D8 for <architecture-discuss@ietfa.amsl.com>; Wed,  4 Sep 2019 18:10:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 HWcFMP1KYrrb for <architecture-discuss@ietfa.amsl.com>; Wed,  4 Sep 2019 18:10:08 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21008120850 for <architecture-discuss@iab.org>; Wed,  4 Sep 2019 18:10:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 4A723BE80; Thu,  5 Sep 2019 02:10:06 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RPLfpWjxcsAl; Thu,  5 Sep 2019 02:10:05 +0100 (IST)
Received: from [10.244.2.138] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id E82ACBE79; Thu,  5 Sep 2019 02:10:01 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1567645804; bh=nG2z1eKBq1HGWSteSgVU/UuY/IPbPMmURQRt8ooBBB4=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=kVqcZ1BYJQiK5gTXC5LObQlo+jNRhpR2wadgEKMSogUpT9y8n8/j1iLKbvXFsJRzx ibo3qPmXs/cgzx1MSsXwD9OWZ/CtEK5EuiGHTTEhqR/mltpKnHzUAkAyK4gSbaHGRx 1ftzGO1nAH3agqOgw89SoGbBRzfH5fRl4CEESOTs=
To: Fernando Gont <fgont@si6networks.com>
Cc: architecture-discuss@iab.org
References: <a7b5255b-8570-0e4b-da17-7557e7ca18c1@si6networks.com> <e1895609-e462-e47a-b408-568a5c5363b1@si6networks.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=5BB5A6EA5765D2C5863CAE275AB2FAF17B172BEA; url=
Autocrypt: addr=stephen.farrell@cs.tcd.ie; prefer-encrypt=mutual; keydata= mQINBFo9UDIBEADUH4ZPcUnX5WWRWO4kEkHea5Y5eEvZjSwe/YA+G0nrTuOU9nemCP5PMvmh 5Cg8gBTyWyN4Z2+O25p9Tja5zUb+vPMWYvOtokRrp46yhFZOmiS5b6kTq0IqYzsEv5HI58S+ QtaFq978CRa4xH9Gi9u4yzUmT03QNIGDXE37honcAM4MOEtEgvw4fVhVWJuyy3w//0F2tzKr EMjmL5VGuD/Q9+G/7abuXiYNNd9ZFjv4625AUWwy+pAh4EKzS1FE7BOZp9daMu9MUQmDqtZU bUv0Q+DnQAB/4tNncejJPz0p2z3MWCp5iSwHiQvytYgatMp34a50l6CWqa13n6vY8VcPlIqO Vz+7L+WiVfxLbeVqBwV+4uL9to9zLF9IyUvl94lCxpscR2kgRgpM6A5LylRDkR6E0oudFnJg b097ZaNyuY1ETghVB5Uir1GCYChs8NUNumTHXiOkuzk+Gs4DAHx/a78YxBolKHi+esLH8r2k 4LyM2lp5FmBKjG7cGcpBGmWavACYEa7rwAadg4uBx9SHMV5i33vDXQUZcmW0vslQ2Is02NMK 7uB7E7HlVE1IM1zNkVTYYGkKreU8DVQu8qNOtPVE/CdaCJ/pbXoYeHz2B1Nvbl9tlyWxn5Xi HzFPJleXc0ksb9SkJokAfwTSZzTxeQPER8la5lsEEPbU/cDTcwARAQABtDJTdGVwaGVuIEZh cnJlbGwgKDIwMTcpIDxzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllPokCQAQTAQgAKgIbAwUJ CZQmAAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAUCWj6jdwIZAQAKCRBasvrxexcr6o7QD/9m x9DPJetmW794RXmNTrbTJ44zc/tJbcLdRBh0KBn9OW/EaAqjDmgNJeCMyJTKr1ywaps8HGUN hLEVkc14NUpgi4/Zkrbi3DmTp25OHj6wXBS5qVMyVynTMEIjOfeFFyxG+48od+Xn7qg6LT7G rHeNf+z/r0v9+8eZ1Ip63kshQDGhhpmRMKu4Ws9ZvTW2ACXkkTFaSGYJj3yIP4R6IgwBYGMz DXFX6nS4LA1s3pcPNxOgrvCyb60AiJZTLcOk/rRrpZtXB1XQc23ZZmrlTkl2HaThL6w3YKdi Ti1NbuMeOxZqtXcUshII45sANm4HuWNTiRh93Bn5bN6ddjgsaXEZBKUBuUaPBl7gQiQJcAlS 3MmGgVS4ZoX8+VaPGpXdQVFyBMRFlOKOC5XJESt7wY0RE2C8PFm+5eywSO/P1fkl9whkMgml 3OEuIQiP2ehRt/HVLMHkoM9CPQ7t6UwdrXrvX+vBZykav8x9U9M6KTgfsXytxUl6Vx5lPMLi 2/Jrsz6Mzh/IVZa3xjhq1OLFSI/tT2ji4FkJDQbO+yYUDhcuqfakDmtWLMxecZsY6O58A/95 8Qni6Xeq+Nh7zJ7wNcQOMoDGj+24di2TX1cKLzdDMWFaWzlNP5dB5VMwS9Wqj1Z6TzKjGjru q8soqohwb2CK9B3wzFg0Bs1iBI+2RuFnxLkCDQRaPVAyARAA+g3R0HzGr/Dl34Y07XqGqzq5 SU0nXIu9u8Ynsxj7gR5qb3HgUWYEWrHW2jHOByXnvkffucf5yzwrsvw8Q8iI8CFHiTYHPpey 4yPVn6R0w/FOMcY70eTIu/k6EEFDlDbs09DtKcrsT9bmN0XoRxITlXwWTufYqUnmS+YkAuk+ TLCtUin7OdaS2uU6Ata3PLQSeM2ZsUQMmYmHPwB9rmf+q2I005AJ9Q1SPQ2KNg/8xOGxo13S VuaSqYRQdpV93RuCOzg4vuXtR+gP0KQrus/P2ZCEPvU9cXF/2MIhXgOz207lv3iE2zGyNXld /n8spvWk+0bH5Zqd9Wcba/rGcBhmX9NKKDARZqjkv/zVEP1X97w1HsNYeUFNcg2lk9zQKb4v l1jx/Uz8ukzH2QNhU4R39dbF/4AwWuSVkGW6bTxHJqGs6YimbfdQqxTzmqFwz3JP0OtXX5q/ 6D4pHwcmJwEiDNzsBLl6skPSQ0Xyq3pua/qAP8MVm+YxCxJQITqZ8qjDLzoe7s9X6FLLC/DA L9kxl5saVSfDbuI3usH/emdtn0NA9/M7nfgih92zD92sl1yQXHT6BDa8xW1j+RU4P+E0wyd7 zgB2UeYgrp2IIcfG+xX2uFG5MJQ/nYfBoiALb0+dQHNHDtFnNGY3Oe8z1M9c5aDG3/s29QbJ +w7hEKKo9YMAEQEAAYkCJQQYAQgADwUCWj1QMgIbDAUJCZQmAAAKCRBasvrxexcr6qwvD/9b Rek3kfN8Q+jGrKl8qwY8HC5s4mhdDJZI/JP2FImf5J2+d5/e8UJ4fcsT79E0/FqX3Z9wZr6h sofPqLh1/YzDsYkZDHTYSGrlWGP/I5kXwUmFnBZHzM3WGrL3S7ZmCYMdudhykxXXjq7M6Do1 oxM8JofrXGtwBTLv5wfvvygJouVCVe87Ge7mCeY5vey1eUi4zSSF1zPpR6gg64w2g4TXM5qt SwkZVOv1g475LsGlYWRuJV8TA67yp1zJI7HkNqCo8KyHX0DPOh9c+Sd9ZX4aqKfqH9HIpnCL AYEgj7vofeix7gM3kQQmwynqq32bQGQBrKJEYp2vfeO30VsVx4dzuuiC5lyjUccVmw5D72J0 FlGrfEm0kw6D1qwyBg0SAMqamKN6XDdjhNAtXIaoA2UMZK/vZGGUKbqTgDdk0fnzOyb2zvXK CiPFKqIPAqKaDHg0JHdGI3KpQdRNLLzgx083EqEc6IAwWA6jSz+6lZDV6XDgF0lYqAYIkg3+ 6OUXUv6plMlwSHquiOc/MQXHfgUP5//Ra5JuiuyCj954FD+MBKIj8eWROfnzyEnBplVHGSDI ZLzL3pvV14dcsoajdeIH45i8DxnVm64BvEFHtLNlnliMrLOrk4shfmWyUqNlzilXN2BTFVFH 4MrnagFdcFnWYp1JPh96ZKjiqBwMv/H0kw==
Message-ID: <366eb210-dbd1-08c3-7dc1-483a4678656d@cs.tcd.ie>
Date: Thu, 5 Sep 2019 02:09:59 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <e1895609-e462-e47a-b408-568a5c5363b1@si6networks.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="t1CLq3ap5oqlNpWYn7Yf3Kk01XPYKfCe2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/V_5Ox8c7XJSOmKhqxply1yAKDpI>
Subject: Re: [arch-d] Fiddling with IP packets in the network, IPv6-style (Fwd: Question about SRv6 Insert function)
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, 05 Sep 2019 01:10:11 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--t1CLq3ap5oqlNpWYn7Yf3Kk01XPYKfCe2
Content-Type: multipart/mixed; boundary="Z58ktCVG6sRJcAbmQbd0dnyBXOxKsDdWp";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Fernando Gont <fgont@si6networks.com>
Cc: architecture-discuss@iab.org
Message-ID: <366eb210-dbd1-08c3-7dc1-483a4678656d@cs.tcd.ie>
Subject: Re: [arch-d] Fiddling with IP packets in the network, IPv6-style
 (Fwd: Question about SRv6 Insert function)
References: <a7b5255b-8570-0e4b-da17-7557e7ca18c1@si6networks.com>
 <e1895609-e462-e47a-b408-568a5c5363b1@si6networks.com>
In-Reply-To: <e1895609-e462-e47a-b408-568a5c5363b1@si6networks.com>

--Z58ktCVG6sRJcAbmQbd0dnyBXOxKsDdWp
Content-Type: multipart/mixed;
 boundary="------------F85BB19188F410BA035A1E1D"
Content-Language: en-GB

This is a multi-part message in MIME format.
--------------F85BB19188F410BA035A1E1D
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hiya,

On 05/09/2019 01:47, Fernando Gont wrote:
> But given this is an architecture list, I wonder if anybody has a say o=
n
> the topic? (including the IAB).

I don't "have a say" but I do have a question...

Given this is a WG document in a chartered IETF WG, I'm
unclear why you're asking the IAB/arch-discuss. I mean,
if the draft is out of the WG's charter or something,
then raising that with the chairs and then responsible
AD etc would be the path to follow. So I'm puzzled as
to why you think IAB members ought spend time on this
(given that I, and I guess other IAB members likely
start out as ignorant when it comes to spring stuff;-)

Ta,
S.

--------------F85BB19188F410BA035A1E1D
Content-Type: application/pgp-keys;
 name="0x5AB2FAF17B172BEA.asc"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
 filename="0x5AB2FAF17B172BEA.asc"

-----BEGIN PGP PUBLIC KEY BLOCK-----

mQINBFo9UDIBEADUH4ZPcUnX5WWRWO4kEkHea5Y5eEvZjSwe/YA+G0nrTuOU9nem
CP5PMvmh5Cg8gBTyWyN4Z2+O25p9Tja5zUb+vPMWYvOtokRrp46yhFZOmiS5b6kT
q0IqYzsEv5HI58S+QtaFq978CRa4xH9Gi9u4yzUmT03QNIGDXE37honcAM4MOEtE
gvw4fVhVWJuyy3w//0F2tzKrEMjmL5VGuD/Q9+G/7abuXiYNNd9ZFjv4625AUWwy
+pAh4EKzS1FE7BOZp9daMu9MUQmDqtZUbUv0Q+DnQAB/4tNncejJPz0p2z3MWCp5
iSwHiQvytYgatMp34a50l6CWqa13n6vY8VcPlIqOVz+7L+WiVfxLbeVqBwV+4uL9
to9zLF9IyUvl94lCxpscR2kgRgpM6A5LylRDkR6E0oudFnJgb097ZaNyuY1ETghV
B5Uir1GCYChs8NUNumTHXiOkuzk+Gs4DAHx/a78YxBolKHi+esLH8r2k4LyM2lp5
FmBKjG7cGcpBGmWavACYEa7rwAadg4uBx9SHMV5i33vDXQUZcmW0vslQ2Is02NMK
7uB7E7HlVE1IM1zNkVTYYGkKreU8DVQu8qNOtPVE/CdaCJ/pbXoYeHz2B1Nvbl9t
lyWxn5XiHzFPJleXc0ksb9SkJokAfwTSZzTxeQPER8la5lsEEPbU/cDTcwARAQAB
tCFTdGVwaGVuIEZhcnJlbGwgPHN0ZXBoZW5AamVsbC5pZT6JAj0EEwEIACcFAlo9
UYwCGwMFCQmUJgAFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQWrL68XsXK+qG
CxAApYHWYgGOIL3G6/OpkejdAkQoCVQAK8LJUSf6vzwost4iVfxIKcKW/3RqKNKk
rRl8beJ7j1CWXAz9+VXAOsE9+zNxXIDgGA7HlvJnhffl+qwibVgiHgUcJFhCSbBr
sjC+1uULaTU8zYEyET//GOGPLF+X+degkE/sesh4zcEAjF7fGPnlncdCCH3tvPZZ
sdTcjwOCRVonKsDgQzBTCMz/RPBfEFX44HZx4g1UQAcCA4xlucY8QkJEyCrSNGpG
nvGK8DcGSmnstl1/a9fnlhpdFxieX3oY2phJ1WKkYTn6Advrek3UP71CKxpgtPmk
d3iUUz/VZa0Cv6YxQXskspRDVEvdCMYSQBtJPQ4y2+5UxVR9GIQXenwYp9AP2niv
Voh+ITsDWWeWnnvYMq07rSDjq0nGdj41MJkNX+Yb2PXVyXItcj5ybE3T2+y3pSBG
FEZYJGuaL4NwtBJFMOdOtBmUOPbetS2971EL3Izxb7ibOZWDwexv+8R6SWYfP1wV
N3p46RyBQuXqJV8ccE11m6vtZTGSYgnLUUFZMRQYH+0hwuYe0T3AA18xDdSYsa8v
ovCCd3l5S4UNzIM2PMChqGrEzKapUpZg7+8ACcxRU3b9Ihd7WYjJ+pQPCoWYKozv
tEvenbNpE/govO/ED3B14e+R2yevRPjRrsN7PJzSf15fQLuJARwEEAEIAAYFAlo9
UqAACgkQLzyHNoBfjaLrSwf+MIHbFRQ4O5cmLYR5sIByWelN3SuRN/gW8rpKo9Ok
Cz6An8uV/iCXy5tNMLzzi0BFl8f22DwBcC5qy9qnlIAdogWam1qWoTAoAD8veEqm
uKhYrqJsCcAyNrKYmK0hP3rpHxx1LySDmKYXmw/8qtBXKHTouMm+5tSsznhykRMT
AAr2p7PSaHgo+hIVaW/rKSspHjDhhZS+G9mtOZad1IH29M6G1Q1NCO0Ywe8krKLQ
IAQlFxtgvOqpPOZNzeKBa/+KbE8TGgMWrkOhC8OeEM5PVzdDhlhD9kPzB/pCKDF5
DofJ/ZRqnDpbKPQ0bsW38AOig3kOc0A27awiBEw3urqR1YkCMwQQAQgAHRYhBH4X
CgRchM9GDit5oBDvedn9g1MSBQJbtyScAAoJEBDvedn9g1MSI/oP/0A9J9nrnBMq
Zpm857lfYWw+rshLK+tyeP4OQeOqnDFvs9jePpcyJLG3DF2r6VbVKPQq+AE6Uf5h
cJBDEN6BjEhRPSbLcqG3A1cz/nNwm8rPmNp+oKhmaBBQGxwciMLmzgynsDydnjPp
MyEs04zvsbsl4vrp2095o105l8KcrrxQrioFjbwveGwHQK9bxJKhx9D+gIk+MouB
ur45UDKTZkMZrr9FGrtkyXCGAxvKdcNC5Oa8z9sj1rcUJfG/OpVAMWhArdlZbFUQ
yoX6pU2Zb1CR2qpWAVerGSfBhmfCyStjARqaKxlftjO+Bj3Jj73Cr5eqej3qB5+V
4BCsPjr4RLvVbYUCPsRdxWc+nBLlfVYkRURu21g1hFm5KFPjgUkyo1s4vjUOY8Dy
I+xLGF7f/IhUBG6l+Vswhpwu7ydalZkeFiPx5xna5NfbEYxvsIf71DvipGvIOaHv
X4egWoFgm8n/9c3rcMxJtpwHPSsUt5dgLsyu6VE0IbvOAc3dN7CWJ355DVFJq9Zg
2YVf0izSpyyzJeGsgkfjW6xpmdvZxuT2UcN4BTcm6vYqueASGrb3lfhzC5gpeVsc
/MoSjTS65vNWbpzONZWMZuLEFraxWJzC0JrDK3NCd0VN3kstqGkVbUIiYOnUm8Vu
4zoVMLlGWzHLIGoPRG2nRezn1YyNfyb5iQGcBBABCgAGBQJbxcflAAoJEGo7ETk8
pK1gE7QL/ApC5P68W5DrI1787WJVZv1u4t/g39vTr7Xer3UMTVQg10vpa7pmqOGh
jIDzDMg3Pe3K3M7fVzfAlUA1qw6ne4RCueVoRKpubeF4AlYbMr0K6hNCPjt5uAxm
bBVuejKTc6pru5rv5gKL0nDbr+Snft5xt7juBLSSimw0/41sZnkjCxo9rF/RA/v6
+uWyK171RKmsEYu8fFtw1eqUNt/Xj792TUixE3pxXheNtQtZGk/9P3W83ChhG4Fh
5EQsn0pIh9wZIAbMRLpgRKyW87fWHZC8/YH8h7afarvn9Thl5pFUldCe22mNJj6K
LChn2aEHQd+PdY1GBpZEcmNEUPuovwzatM0h64hCzTm41eDqRfihZVBT7TbfXQnv
8rywa42Mk756RGzzEZcQEhwQXZcMQUfxIQQ2VyJo0zG36VdZTQF7TF/4Lz7/3cJ5
6jOIm+dwPXtu+C2wAQuD4USOLt4JWPYpqzDfHYJIND/497P9Z9SuQeahr2ez3DRB
g3qsHEjBV7QyU3RlcGhlbiBGYXJyZWxsICgyMDE3KSA8c3RlcGhlbi5mYXJyZWxs
QGNzLnRjZC5pZT6JAkAEEwEIACoCGwMFCQmUJgAFCwkIBwIGFQgJCgsCBBYCAwEC
HgECF4AFAlo+o3cCGQEACgkQWrL68XsXK+qO0A//ZsfQzyXrZlu/eEV5jU620yeO
M3P7SW3C3UQYdCgZ/TlvxGgKow5oDSXgjMiUyq9csGqbPBxlDYSxFZHNeDVKYIuP
2ZK24tw5k6duTh4+sFwUualTMlcp0zBCIzn3hRcsRvuPKHfl5+6oOi0+xqx3jX/s
/69L/fvHmdSKet5LIUAxoYaZkTCruFrPWb01tgAl5JExWkhmCY98iD+EeiIMAWBj
Mw1xV+p0uCwNbN6XDzcToK7wsm+tAIiWUy3DpP60a6WbVwdV0HNt2WZq5U5Jdh2k
4S+sN2CnYk4tTW7jHjsWarV3FLISCOObADZuB7ljU4kYfdwZ+WzenXY4LGlxGQSl
AblGjwZe4EIkCXAJUtzJhoFUuGaF/PlWjxqV3UFRcgTERZTijguVyREre8GNERNg
vDxZvuXssEjvz9X5JfcIZDIJpdzhLiEIj9noUbfx1SzB5KDPQj0O7elMHa1671/r
wWcpGr/MfVPTOik4H7F8rcVJelceZTzC4tvya7M+jM4fyFWWt8Y4atTixUiP7U9o
4uBZCQ0GzvsmFA4XLqn2pA5rVizMXnGbGOjufAP/efEJ4ul3qvjYe8ye8DXEDjKA
xo/tuHYtk19XCi83QzFhWls5TT+XQeVTMEvVqo9Wek8yoxo67qvLKKqIcG9givQd
8MxYNAbNYgSPtkbhZ8SJARwEEAEIAAYFAlo9UqAACgkQLzyHNoBfjaLzHAgAlWT6
NXEGtw/r1miKNGcopzvzILQ9oB8rKI9U9EL6tOf/y2V5oYee/GyQDb3ZdoPxxYYc
Jf+RyiH1nMoqUIZiZJaf3bJXinDZ5+AdfE++UR2NBvqaNyC6u3r24jo1B/sagKbY
tWgsYtRqHLD4IWi37MZrVyjBuF7u14Q07+uhjq6mX2O/tHpCYw/Q82tbeTRPyUf1
WQOAfD1kfBpW9PvAva5Iw9FWeXpCXRzwxnCZhYfGfqtuSw6CPBYLdbikqML6FZ7E
DuTBb/8um1wK7Y9bgeIQC+CYjhYB5RXa1tDJRab2Js4luCvSR0w/CgHw26293tlv
e2Q6UTrmHxP5U22DlokCPQQTAQgAJwUCWj1QMgIbAwUJCZQmAAULCQgHAgYVCAkK
CwIEFgIDAQIeAQIXgAAKCRBasvrxexcr6tJpD/4rrILH+meP07vrx8wW5eYuqCiP
GYnh/CXxIF8eLrfbe5d4QRgtq+w6UeQPMyzKRIRiCoBXB2oJLBZHyxBPxZlg33dT
MrEGn8QWKx2iNuz9rZMXyOSWFetuO01d/aUPd5BnbLbIyK5of8xCQlXM6KH8bc+9
gQ7edR9mfLTdvBf2FR522hg8BRBM1imKc3vO8v39+qIHHRjuiwxBBCAOhHtHRsZX
ripS0uFA07dM46Oi/E8osjx6fQt/lH5z/PN+2adxYSrLSAXfr1oD3RxYNhuWgyGF
L64/VCQb1YGjf0Z5MBPnWm9jgUoOY5K9eNSS0L83WeJjlF5+Q/WOgB+rb49Prm2D
Feo9+S9f2V53Llz1WIspXJg6f+n9lmHE94MfQj1GAHCzI0FeL19lvM+LhD8jJSCb
hrC3+yobyy/AUOs5Z3E+njjX1FF/VCVAs6iOa6i+XG+Y1hh3ir2y1kckJ5auT10M
SU8GEZu9ayU4M3o3N9yxOjaoP0NuQ4MMLL/n/u4u94AeZaHPNBXn/hVfVRRmpRXt
GKvJtFAEppGEYezB+bLKIm6XlpPkhnwYzleLZ7AMEco2C6QM8QPB3g3JpS3sqRhA
5rEP4lL16BmijmF+CHoPE/zwgKZbKpyVDqvIW5IDgvfIC2X4pbZDRvGIUKaGSB4+
ksZgUUnNyvfQr2p7jokCMwQQAQgAHRYhBH4XCgRchM9GDit5oBDvedn9g1MSBQJb
tySbAAoJEBDvedn9g1MSeKkQAJm44jt1kwHgQgeDBKdjdvl0AjE0xVEQxriZ6lP/
l//34YT0auFfzsYIrChSpQXAEtobBAr4Ohw1Us+BZe+H5P8vm6LRuPwozC3SjwfX
4Iec8+9ot6tIVg4sbedDSgb/CCFVjsmIGcQ1P73JLJTBJ6mxYCV/gn3QC6bwDOFo
7kD9FDHCjRN8XfhHQ4Q9cYyt06uF31qG/aumgWYC9geCGgAwiHgwxNYb9GoJ0iZj
CROwbYvLTcQgsVUW2bTmsVR13UVKDsdl02sRV7qcVYW6R0a3Ra8KudX+nt25H5DR
Gd382KZ5W8pydsy/viTvD9z6v0ulChBYxAedIvGIClrhbxlLEPmIg4ImVOLGqsUg
Vm32J95WOjEkk4PEZ12xSDBtwhSJqmJNboWlfmw43KdIbY8zNhffIO3N6O7FsdGx
mqyHeLoTpqY+ySVUPpbuyW8ujnI/J//+6hdTZ9dQsEJQlWngKuWOQ5ma58MPSN88
zllsqhZAFQjNxqnkSzL6ZQ+v/jvuRRe16B80AeO55DsmbWsMv/YLLD1mSi7+Khy2
EtMBhgojWwrGMvdLN6X3mnzNJEscYyLxM9tSk+iySP2sLthK0BVgpAzBSdaf/ezI
z60P+neHDzteNFf8Mn7lmgYk1amvZoJ29s5+n2HwxyRL5dVMyMdyQmntubbctfqr
Z0tIiQGcBBABCgAGBQJbxcflAAoJEGo7ETk8pK1gnCYMAJY4FeIYjlIXGghFWzsB
4fYwK1+iaFpU3fSto5qcrqVtVPjXpwqczqBWeXGyQxiB0kan4OVAXydIeaP8EAuF
CA7paP3s9STLJBO3KurkwyRkPW5zo0X7xVqaVToRsX2Ul98KVJoHYQD1KdezEtwl
vpNwiiBr42AYR751Vm6JBVAbQXuFpB3c8bUV0OkkRxNFtL8/2PieHar58n5dntGk
bPlPkztahsFqktgacIgXHX5vaT+7YeeZ1DWLOYjGO0wNhkOSeroCmxwJUikU7joB
p823L7r5KfpqWTPpSCzVstQKZUGmmoE1qCswY/Ud5wvp9SccpIILkRXj0rZRtfnE
5MpL3hjmtNzfDd9qIsJtBJlSB2hZwAsVm1l+EWN9hG3tqyA43niUMy2n6q690of3
berSiQ+kvY/aC9Hx8I+bKzOV9/J2VUTqfaPZa4Uy2rVX5Q2p69n/PMj7mEer0rCL
3j9V16J9c+s0BSkXoKdtYdB0TWVhBgUybd9qtYcwHWvhP7QuU3RlcGhlbiBGYXJy
ZWxsIDxzdGVwaGVuQHRvbGVyYW50bmV0d29ya3MuY29tPokCPQQTAQgAJwUCWj1R
WgIbAwUJCZQmAAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRBasvrxexcr6jsc
EADEcB0WQEZn2AkrzDs1RhL0Lp6cZi0BigofkbcGfdhJyMSs19C0dhvncrAFClVI
6/Udw3yFtDyYtOCf2W3M3A1K6/RfEizCLzTsdFIhni9gOJLlUpXViQtgrlstjk7h
qVV3Ooz4BlCqS4cG7rfqf4LQQPpTAuFUEV9I28FBUB2irqC+v4gTysIgpMw0bA1y
BU9sX5jE/tRkzqnuzZrkwiobDtRFJ9qp+7O2JtcY4EsVtLAsaodJKc5cF8R4OvB1
n66vxxcgg9Eh4JNWZ47xsaCmAGo1Bcb2jIY35OtgAL7gCGLRSMKTtAaPy1/fEgIq
hCljJ9x40Fkn/3r2BX21WC9HFSPFTBz2RluLRzxdgxOrkYK8EiHUPoE5b1AEzZKw
2AbeXfr57f5zYsN3IqfbQLUjMYtUN1wK3Pjb+idD972wyXMWt8uOzlI7b9Ocu+nY
m2whBfJv9Pmp3QYTmPz+LB9lH65VNVUSxSXVr5iWXO3qx1HtEiGEqkporMQCTh3T
5Ud3PvMSRBFFKNs9WhJ/Lxz+SV30WLwG6dr5mQqlzAhb4Phc/zekZyXRdS/oDKrB
LUucS36O//49JeyRi1QvOfxnfmIqRIAf/k3PoYJmTo5E82//r5Qj3YGlRu78ba0H
Arxs+ACD6AnEHHcbswpbtVEKYzlSu0Ar0Dc7vRWM/IyQdIkBHAQQAQgABgUCWj1S
oAAKCRAvPIc2gF+NosIsB/9f/29FNla3BJfGIEIDnhrqGD0i9bSa89SqBd++uG06
TQgW5wsqtNcrwn81yZTq6XE6i9VtD4GKfqC0d4KZJr9bnbeD81cI64VOdL8zJWJs
0vj5EIXCobKyX74Kb4uePUyZqwT2Q74I116u/HwA9/FXsPo5isbh4ZqD4t0VHpWk
mfq1FPT9a/JPyX46qKqB2Fce/7Qy+SQP1NfkuUlbhUH/JG9aSSYvk3lznNiH41x9
M+FDlL106itXOubrl3oi2fT3fsSedq7uzt+IV0DQEeNaoQAUuwEhdB8IWOMqN2wo
DjGVKJftfsSWY9ilZrnDBNDrp0vRqcx33LUMkIw4d7iBiQIzBBABCAAdFiEEfhcK
BFyEz0YOK3mgEO952f2DUxIFAlu3JJwACgkQEO952f2DUxJjuw/6ApHSsVTWD4a0
H6FJ23A9Ftpy+aXZ4vYlzkSrfsn2ECrEfK3lXQh/uzwjJUDYZeB1/BQsFZtcYNQO
JSSHbQ49BFRLwb1J/wBZG4bbmrkLxnNbKDKQvzxEpclkMW0Dj0J6o7kGrmzIGGrh
B+JJN99AcineHRug8ZSFIERRCmigxdhAKU0BFD7P+5HNHltSL3DF1c2fFOf2JrgB
KVoE+9RhMZjWNbYetFFLCkjXb5Rpay9zeMm1DxfSTGAnuOwUXW6qq4hnl5+VC/48
ceDZElLLfu7RQUZv44pkSTOWZs+iQoJiHMFHk9wPqyB2Vok1yJ2a2j27WhXrJlPw
nZbgJO5RyWDG3p/eVmpl5Uuc2dsfIpR17KnAuWpghK6V+cyFncDoGCl/YG2Mvool
sW08FiZh3Ej4dnJjj25TZkeFG74JJDXLvMYpJfSBGnmETv4Dhcm2xPqVMuFuL1qJ
lMbVLrMo2GXeo03OzNyvbs+u8WLIaGm5hC7N1CXY8wZs4jo6OJ/expvnc07dEuws
4zT3AiWv3nIouWReRStZy9QkavDocqbyPmilcdPCYk4BsOlzpwwO74hNG7iyl0Kd
AlwTxGQ7y0rJou6HYa1TmRhIEr3vKvlW+JfUUrqtjXgsuacTXo4+Ira2JUErL2cY
zQMq1j4r1ZyhFnuz93s7Rsx/Nw0+0YuJAZwEEAEKAAYFAlvFx+UACgkQajsROTyk
rWCJqwv+NLVPE4sD4sDA2/6Ek7UsRIUkg+S39fhqWsLc4rtw/mDunv8Un61I3K04
fZ2Ry4nF9hZM0a710UvXFbStvrzRJO3EAAcdJR9LTCd19e8UeruQbIee3YT91U4N
kC9JMpecfq62/teOAU2e5P3fWYaLs5ZX7zCLwWuBcW2l3SyoljQczM85HhJ3XHm+
FnwQ6D9xRle+lvWTcuC9d1yAyUb8IOospcL2lJTmy8e3r79R24hPlSB4LDe0wEN8
AXbagrcAQZjwyaHyWxjJbTwZ0b43WGdfIqZ1ElOeoffbketPGRmWvx5xUvb2ALFB
BdETzV270gs5XDJgJ1SIIKOyDADxwvroTe2jD8C/841eEql5QSow3s/U3zRqk3mt
tto8Qw/DN71aeh6dmYSsvd2UjsHw/vofOPRBGxZLEkKTEvMnhmMW9hiKPkPia+Qg
evYE020qpKSxLEdWA8nprHwxmGiDNesCfXSC6vm1qfyj5g8HzxSckq9ZaMhKMCo7
vxflUEDuuQINBFo9UDIBEAD6DdHQfMav8OXfhjTteoarOrlJTSdci727xiezGPuB
HmpvceBRZgRasdbaMc4HJee+R9+5x/nLPCuy/DxDyIjwIUeJNgc+l7LjI9WfpHTD
8U4xxjvR5Mi7+ToQQUOUNuzT0O0pyuxP1uY3RehHEhOVfBZO59ipSeZL5iQC6T5M
sK1SKfs51pLa5ToC1rc8tBJ4zZmxRAyZiYc/AH2uZ/6rYjTTkAn1DVI9DYo2D/zE
4bGjXdJW5pKphFB2lX3dG4I7ODi+5e1H6A/QpCu6z8/ZkIQ+9T1xcX/YwiFeA7Pb
TuW/eITbMbI1eV3+fyym9aT7Rsflmp31Zxtr+sZwGGZf00ooMBFmqOS//NUQ/Vf3
vDUew1h5QU1yDaWT3NApvi+XWPH9TPy6TMfZA2FThHf11sX/gDBa5JWQZbptPEcm
oazpiKZt91CrFPOaoXDPck/Q61dfmr/oPikfByYnASIM3OwEuXqyQ9JDRfKrem5r
+oA/wxWb5jELElAhOpnyqMMvOh7uz1foUssL8MAv2TGXmxpVJ8Nu4je6wf96Z22f
Q0D38zud+CKH3bMP3ayXXJBcdPoENrzFbWP5FTg/4TTDJ3vOAHZR5iCunYghx8b7
Ffa4UbkwlD+dh8GiIAtvT51Ac0cO0Wc0Zjc57zPUz1zloMbf+zb1Bsn7DuEQoqj1
gwARAQABiQIlBBgBCAAPBQJaPVAyAhsMBQkJlCYAAAoJEFqy+vF7FyvqrC8P/1tF
6TeR83xD6MasqXyrBjwcLmziaF0Mlkj8k/YUiZ/knb53n97xQnh9yxPv0TT8Wpfd
n3BmvqGyh8+ouHX9jMOxiRkMdNhIauVYY/8jmRfBSYWcFkfMzdYasvdLtmYJgx25
2HKTFdeOrszoOjWjEzwmh+tca3AFMu/nB++/KAmi5UJV7zsZ7uYJ5jm97LV5SLjN
JIXXM+lHqCDrjDaDhNczmq1LCRlU6/WDjvkuwaVhZG4lXxMDrvKnXMkjseQ2oKjw
rIdfQM86H1z5J31lfhqop+of0cimcIsBgSCPu+h96LHuAzeRBCbDKeqrfZtAZAGs
okRina9947fRWxXHh3O66ILmXKNRxxWbDkPvYnQWUat8SbSTDoPWrDIGDRIAypqY
o3pcN2OE0C1chqgDZQxkr+9kYZQpupOAN2TR+fM7JvbO9coKI8Uqog8CopoMeDQk
d0YjcqlB1E0svODHTzcSoRzogDBYDqNLP7qVkNXpcOAXSVioBgiSDf7o5RdS/qmU
yXBIeq6I5z8xBcd+BQ/n/9Frkm6K7IKP3ngUP4wEoiPx5ZE5+fPIScGmVUcZIMhk
vMvem9XXh1yyhqN14gfjmLwPGdWbrgG8QUe0s2WeWIyss6uTiyF+ZbJSo2XOKVc3
YFMVUUfgyudqAV1wWdZinUk+H3pkqOKoHAy/8fST
=3DYzQY
-----END PGP PUBLIC KEY BLOCK-----

--------------F85BB19188F410BA035A1E1D--

--Z58ktCVG6sRJcAbmQbd0dnyBXOxKsDdWp--

--t1CLq3ap5oqlNpWYn7Yf3Kk01XPYKfCe2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEW7Wm6ldl0sWGPK4nWrL68XsXK+oFAl1wYGcACgkQWrL68XsX
K+r5NQ/9Gwrkw8L5acx9vKBeNt6XKjsUafPWlrTitxjhdEhP+p0FXNtII6YqhpW4
8SDr/n9m/DEhsxLoQg24ByF6DsUehNwLW1ShjNjPP5c/Nmv0EUmR3RB+mHWfOX6n
6xjVfea33YqkuYVMgBZIjRbbQGbv07NtUqUrG7dglpeayUslyhw+2htz7EjiH2t0
CYYs8Yq2HGGMTFdXLF/NPrONisnfXdVyCunKkpjsr+qbmeMiaRfI9RZXkJXAG/jn
65xJFDI0srfomh0MqbzkdFOPum8SsU0BMbGAmcHkoE33p1kOXj37120EfaE0HFMz
65Ea8IQSayfwRH7EgMRh9uO0dm+QYHMcGnyJrkkA3oUWFcXLg7iBcd7xdsNev/9B
F1JB8lLMA44RaU8BWrmv55iif0WTT+8Ai11SMGfyqB7tfU0e1geVavmcKiH2cFCL
8WqvqGPzpICZjLnCmUOoseaTCp6H2FqtC3PK8joKKb0GOCQW6ef4ykKaZVvvI40N
GlG3U37SLGi4mHOZIHM9Z3dg6aZLGaDSKl4rZAjZmpS1PVjNLvfCG8SnDgRMiWLt
1/zDDN760wvkxEPPSrRMR7n7yXHkFkvXV20BOe/f4W7tZCjE3Ni5h6EeNIxX6foP
MI4kUg8rW8ziZW1Q4mc+NrDuFiz1ttvoB6J35RKwh8F2/JQUm+0=
=pitL
-----END PGP SIGNATURE-----

--t1CLq3ap5oqlNpWYn7Yf3Kk01XPYKfCe2--


From nobody Wed Sep  4 18:30:46 2019
Return-Path: <fgont@si6networks.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 5EF681208D8 for <architecture-discuss@ietfa.amsl.com>; Wed,  4 Sep 2019 18:30:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 NpWtZmmFBiQl for <architecture-discuss@ietfa.amsl.com>; Wed,  4 Sep 2019 18:30:43 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6B7712004C for <architecture-discuss@iab.org>; Wed,  4 Sep 2019 18:30:42 -0700 (PDT)
Received: from [192.168.1.14] (ppp-94-69-228-25.home.otenet.gr [94.69.228.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 2D6F786147; Thu,  5 Sep 2019 03:30:39 +0200 (CEST)
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: architecture-discuss@iab.org
References: <a7b5255b-8570-0e4b-da17-7557e7ca18c1@si6networks.com> <e1895609-e462-e47a-b408-568a5c5363b1@si6networks.com> <366eb210-dbd1-08c3-7dc1-483a4678656d@cs.tcd.ie>
From: Fernando Gont <fgont@si6networks.com>
Openpgp: preference=signencrypt
Message-ID: <ae5ccbc2-d344-2dea-7954-ecb4c5b8ba26@si6networks.com>
Date: Thu, 5 Sep 2019 04:30:20 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <366eb210-dbd1-08c3-7dc1-483a4678656d@cs.tcd.ie>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/fDn5XPJHEU6-Sym9zsvuF2E84TI>
Subject: Re: [arch-d] Fiddling with IP packets in the network, IPv6-style (Fwd: Question about SRv6 Insert function)
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, 05 Sep 2019 01:30:45 -0000

On 5/9/19 04:09, Stephen Farrell wrote:
> 
> Hiya,
> 
> On 05/09/2019 01:47, Fernando Gont wrote:
>> But given this is an architecture list, I wonder if anybody has a say on
>> the topic? (including the IAB).
> 
> I don't "have a say" but I do have a question...
> 
> Given this is a WG document in a chartered IETF WG, I'm
> unclear why you're asking the IAB/arch-discuss. I mean,
> if the draft is out of the WG's charter or something,
> then raising that with the chairs and then responsible
> AD etc would be the path to follow. So I'm puzzled as
> to why you think IAB members ought spend time on this
> (given that I, and I guess other IAB members likely
> start out as ignorant when it comes to spring stuff;-)

Besides procedural issues, the ultimate implications of this is that
we're formally introducing middle-boxes that fiddle with packets in the
middle of the network.

Isn't this within the kind of stuff the IAB has interest on?
If so, better to tackle this now, than to publish an RFC5902-style
document when the cat is already out of the box.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Wed Sep  4 18:37:55 2019
Return-Path: <tony1athome@gmail.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 C17CC1208E4 for <architecture-discuss@ietfa.amsl.com>; Wed,  4 Sep 2019 18:37:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 JaUvC8M5AcjH for <architecture-discuss@ietfa.amsl.com>; Wed,  4 Sep 2019 18:37:52 -0700 (PDT)
Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (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 F377412004C for <architecture-discuss@iab.org>; Wed,  4 Sep 2019 18:37:51 -0700 (PDT)
Received: by mail-pg1-x530.google.com with SMTP id n9so449346pgc.1 for <architecture-discuss@iab.org>; Wed, 04 Sep 2019 18:37:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=kNYyEFmqKa88dNNEc4c4qpjM4wSXyel/QS3mlf7hHX8=; b=hykGScnziZxWUq43P9eFLZYZeE49mx2Jamq3LhU86dQZiefbBNDXY/uKVR4MDc6vfx yqpea2hE2bJJP5Stb2PdONE7wKc84FicyXgqr4/Dn2duOHmiy54F/x70VG4OmIyQi+MR e7zGLRXjn65rY1ypSNXb/9cYIOY2OH6WQV49DxTh+zEGQWZ9ZQPFxQhAuhWe9qGvONcf j945nqpRpUnFecgqxqfktS1OaBsrJRGSrwHkeDUu1T8cQMExxIO6kB7MRjlT9YFVLrzQ LA25Z/vOJFVzPhYcVxFDKjQwpYp4xBB7yr2LB4pIKs0Dh62fnBl8G6bl4vj8qM3cqyLT EzNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=kNYyEFmqKa88dNNEc4c4qpjM4wSXyel/QS3mlf7hHX8=; b=JbpXx59WhFlJhdRle7R1Bl4N8mIOLVMyo6QPYjjbRkl+BCe7nCXcHtC5IthUifqlVm QsrBc3gKGYf+dDiLRYfHLPRICwiB5o3JzIq8cbOZuVKeV9K/1B2Pbm3aepKFu1BQyZW5 kexk1Us0G+k10p8AD0dLmTsYl2CJDAxf4Zj95Ao6LPzhoozEVnsH6UPE7hUgJsy7Eoni ogQY9oeMGVJZxR35Wi19yhO8wWiPbE+Bo6P7gK785I5ojHLkB1VYnQokoDBZFphFiqvr tMGRXgrIqlN9O/s66y3FQeHz9rWC1MgaBuvxQfilgQvUyTX/bIshfuV+lByu9y3JTU4a KGDw==
X-Gm-Message-State: APjAAAW8gDXIySuxHY9GwssKq+Fkh2ErabsAHe4TcnWsW0WYyF0udkNs z+mDLJ3CN0YLo170IK+W3tvT+2+9
X-Google-Smtp-Source: APXvYqwbUSWRmm6BWEfAlR9cQZhIsgxJyj/CcYJ5cxTJLyJi8Sd+0GfCM5jIiRNOdUAG2AxH/XzMhg==
X-Received: by 2002:a17:90a:340d:: with SMTP id o13mr1135325pjb.19.1567647471181;  Wed, 04 Sep 2019 18:37:51 -0700 (PDT)
Received: from [172.22.228.115] ([162.210.130.3]) by smtp.gmail.com with ESMTPSA id q4sm352236pfh.115.2019.09.04.18.37.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Sep 2019 18:37:50 -0700 (PDT)
From: Tony Li <tony1athome@gmail.com>
Message-Id: <C31553B4-1B25-48E1-8A79-92B96FAB08C7@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7EDC80CD-43BA-4644-90A8-541B2353838A"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Wed, 4 Sep 2019 18:37:47 -0700
In-Reply-To: <ae5ccbc2-d344-2dea-7954-ecb4c5b8ba26@si6networks.com>
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, architecture-discuss@iab.org
To: Fernando Gont <fgont@si6networks.com>
References: <a7b5255b-8570-0e4b-da17-7557e7ca18c1@si6networks.com> <e1895609-e462-e47a-b408-568a5c5363b1@si6networks.com> <366eb210-dbd1-08c3-7dc1-483a4678656d@cs.tcd.ie> <ae5ccbc2-d344-2dea-7954-ecb4c5b8ba26@si6networks.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/anYGCa-8pqPp9ia1TGYSu_bHbrs>
Subject: Re: [arch-d] Fiddling with IP packets in the network, IPv6-style (Fwd: Question about SRv6 Insert function)
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, 05 Sep 2019 01:37:54 -0000

--Apple-Mail=_7EDC80CD-43BA-4644-90A8-541B2353838A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> Besides procedural issues, the ultimate implications of this is that
> we're formally introducing middle-boxes that fiddle with packets in =
the
> middle of the network.


Didn=E2=80=99t we have this same discussion 25 years ago on NAT boxes?

The fact of the matter is that the IETF is completely helpless to =
prevent such things.=20
True, it can block standardization, but if the market wants it, the =
market will drive it
and all that the IETF does is to make itself irrelevant to the process.


> Isn't this within the kind of stuff the IAB has interest on?


If it were, the first complaint would be about SRv6 itself.

The IAB=E2=80=99s only role is that of genteel education and it=E2=80=99s =
a target rich environment.

Tony


--Apple-Mail=_7EDC80CD-43BA-4644-90A8-541B2353838A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D""><span=
 style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">Besides procedural issues, the =
ultimate implications of this is that</span><br style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">we're formally introducing middle-boxes that fiddle with =
packets in the</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">middle of the network.</span><br style=3D"caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""></div></blockquote><div><br =
class=3D""></div><div><br class=3D""></div>Didn=E2=80=99t we have this =
same discussion 25 years ago on NAT boxes?</div><div><br =
class=3D""></div><div>The fact of the matter is that the IETF is =
completely helpless to prevent such things.&nbsp;</div><div>True, it can =
block standardization, but if the market wants it, the market will drive =
it</div><div>and all that the IETF does is to make itself irrelevant to =
the process.</div><div><br class=3D""></div><div><br =
class=3D""></div><div><blockquote type=3D"cite" class=3D""><div =
class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">Isn't this =
within the kind of stuff the IAB has interest on?</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""></div></blockquote></div><br class=3D""><div class=3D""><br =
class=3D""></div><div class=3D"">If it were, the first complaint would =
be about SRv6 itself.</div><div class=3D""><br class=3D""></div><div =
class=3D"">The IAB=E2=80=99s only role is that of genteel education and =
it=E2=80=99s a target rich environment.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Tony</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_7EDC80CD-43BA-4644-90A8-541B2353838A--


From nobody Wed Sep  4 20:02:19 2019
Return-Path: <huitema@huitema.net>
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 1A277120DDF for <architecture-discuss@ietfa.amsl.com>; Wed,  4 Sep 2019 20:02:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 sC78A5JM9P8q for <architecture-discuss@ietfa.amsl.com>; Wed,  4 Sep 2019 20:02:08 -0700 (PDT)
Received: from mx36-out10.antispamcloud.com (mx36-out10.antispamcloud.com [209.126.121.30]) (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 1B8B3120E0B for <architecture-discuss@iab.org>; Wed,  4 Sep 2019 20:02:08 -0700 (PDT)
Received: from xse471.mail2web.com ([66.113.197.217] helo=xse.mail2web.com) by mx62.antispamcloud.com with esmtp (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1i5i2A-000CTT-82 for architecture-discuss@iab.org; Thu, 05 Sep 2019 05:02:06 +0200
Received: from xsmtp21.mail2web.com (unknown [10.100.68.60]) by xse.mail2web.com (Postfix) with ESMTPS id 46P57x1WLzz1vpf for <architecture-discuss@iab.org>; Wed,  4 Sep 2019 20:02:05 -0700 (PDT)
Received: from [10.5.2.49] (helo=xmail11.myhosting.com) by xsmtp21.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1i5i29-0002kK-2h for architecture-discuss@iab.org; Wed, 04 Sep 2019 20:02:05 -0700
Received: (qmail 25279 invoked from network); 5 Sep 2019 03:02:01 -0000
Received: from unknown (HELO [172.16.5.52]) (Authenticated-user:_huitema@huitema.net@[207.32.165.175]) (envelope-sender <huitema@huitema.net>) by xmail11.myhosting.com (qmail-ldap-1.03) with ESMTPA for <architecture-discuss@iab.org>; 5 Sep 2019 03:02:01 -0000
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Christian Huitema <huitema@huitema.net>
X-Mailer: iPhone Mail (16G77)
In-Reply-To: <C31553B4-1B25-48E1-8A79-92B96FAB08C7@gmail.com>
Date: Wed, 4 Sep 2019 20:02:01 -0700
Cc: Fernando Gont <fgont@si6networks.com>, architecture-discuss@iab.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <68FC52EA-1BB7-441D-B344-B9413BC6B955@huitema.net>
References: <a7b5255b-8570-0e4b-da17-7557e7ca18c1@si6networks.com> <e1895609-e462-e47a-b408-568a5c5363b1@si6networks.com> <366eb210-dbd1-08c3-7dc1-483a4678656d@cs.tcd.ie> <ae5ccbc2-d344-2dea-7954-ecb4c5b8ba26@si6networks.com> <C31553B4-1B25-48E1-8A79-92B96FAB08C7@gmail.com>
To: Tony Li <tony1athome@gmail.com>
X-Originating-IP: 66.113.197.217
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.197.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.197.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0duM4P579sYYbdH8Mt+sPVWpSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDeW3+HZ7LK0h6oEMb2VkOa5vM xCtZSe87wnSOA0YTnlDnx8yeplRO3sLIqUlSH7OGTpqaL8zlH8KaV23/70DmuYMlhcTgOXSCz8qb ysTVYVkMDlXDa3aVnxGK2HywWN/nvIW9ZcR3XQbVnH55e8ZfsJnckpWaLvahyBjmQxBKOztp0ugt Zlkw9p/AQdIE0knw7cPlLc4mPp21O6mudLBF4/IRL+spW60mrWiAEnQcn/qslg3CoCHsPz6pr/Ao kdAPhX8u3xIOOtB59sWJ1mr0rcswIlm249d1OOo21hSM9tXB1/2M1shZO++tsIV90EPuboZD5vPF e84pJQGk5dfbFPdfcXgLzsY3kBHC+ZTZl3RnfVPTqI4dkGNDDD1o0bE1YTJl/Vbyro+qbGZaEKoG AcB9K/tfe8pLmJg0fcGy9gwRLqjTJeBPrTCjLL/wN7uMRUcRfS0hzbGRZdtpa0UZ/x9JJ5TIDkE1 afsdX6NhD5s+bbELvUd76WgDJEwO4EyqCZ4Be6yUIHlk4xeVfxBr0V/B1pxjLApe66BOTXP4Ht0T vLtGoOPovZCzlvXEZ2pHbtpV/VNFP455az8OafIpvIDOcg83LXH4GksgCfTIQ57WXGH5SDG2kyRs dcYPy9Stx9d4+4VDAiGCNUIFAyUJ5CcAnpQIMSNxxOCOU1F642ZCx7Uc+3YZOTTBTwEhSCnY0147 mfyTrH2pRQdqGedsYWbjO41FyBEqIaDudcVplPGqyJKLfi+FFFIrQ/adkOMzG+qjU1hb0NL74mnd qtcQ8dn2uWfCTMr7dqLRWHiVeRBJeOaBZ3QGltM4cLXJcDSyE4kswb7YzKhySm3KCdywFmvDK3PK rieG7T6bf9hS7hQx0S1sh0LPt0VUPewpiDOvFiQeKRnvGKxB4wV2/L1ZF2Hf4ys44rg2B8/9FmK9 a1Nwex3yoyNXmDWGgOLq9vyL
X-Report-Abuse-To: spam@quarantine9.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/WUvQmAiOeDkW-GVMePcyd6qipu8>
Subject: Re: [arch-d] Fiddling with IP packets in the network, IPv6-style (Fwd: Question about SRv6 Insert function)
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, 05 Sep 2019 03:02:18 -0000

=20

> On Sep 4, 2019, at 6:37 PM, Tony Li <tony1athome@gmail.com> wrote:
>=20
> Didn=E2=80=99t we have this same discussion 25 years ago on NAT boxes?
>=20
> The fact of the matter is that the IETF is completely helpless to prevent s=
uch things.=20
> True, it can block standardization, but if the market wants it, the market=
 will drive it
> and all that the IETF does is to make itself irrelevant to the process.

The flip side of that is end to end encryption, which pretty much ensures th=
at "a bit is a bit". And we sre seeing most of traffic being encrypted, pret=
ty much armored against shenanigans in the middle. Given that, stuff like SR=
v6 is mostly useful for traffic engineering, which seems like something we w=
ould want.

-- Christian Huitema=20=


From nobody Thu Sep  5 01:53:17 2019
Return-Path: <sm@afrinic.net>
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 01657120CDF for <architecture-discuss@ietfa.amsl.com>; Thu,  5 Sep 2019 01:53:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 or2D1hh9nql3 for <architecture-discuss@ietfa.amsl.com>; Thu,  5 Sep 2019 01:53:13 -0700 (PDT)
Received: from board.afrinic.net (board.afrinic.net [IPv6:2001:42d0:0:404::83]) (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 C81B4120CAA for <architecture-discuss@iab.org>; Thu,  5 Sep 2019 01:53:12 -0700 (PDT)
Received: from [102.115.170.8] (port=54191 helo=DESKTOP-K6V9C2L.afrinic.net) by board.afrinic.net with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.84_2) (envelope-from <sm@afrinic.net>) id 1i5nVp-0005vp-P6; Thu, 05 Sep 2019 12:53:06 +0400
Message-Id: <6.2.5.6.2.20190905013002.11e9acd0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 05 Sep 2019 01:52:37 -0700
To: Fernando Gont <fgont@si6networks.com>,architecture-discuss@iab.org
From: "S. Moonesamy" <sm+sdo@afrinic.net>
In-Reply-To: <e1895609-e462-e47a-b408-568a5c5363b1@si6networks.com>
References: <a7b5255b-8570-0e4b-da17-7557e7ca18c1@si6networks.com> <e1895609-e462-e47a-b408-568a5c5363b1@si6networks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/2b8Hopo3x5hH0ssu-3DwLZIa5CA>
Subject: Re: [arch-d] Fiddling with IP packets in the network, IPv6-style (Fwd: Question about SRv6 Insert function)
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, 05 Sep 2019 08:53:15 -0000

Dear Fernando,
At 05:47 PM 04-09-2019, Fernando Gont wrote:
>There seems to be ongoing working group item in the spring wg
>(https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-01)
>that essentially proposes the insertion of IPv6 Extension Headers by
>middle boxes in the middle of the network, which goes against a very
>explicit requirement in the IPv6 spec (RFC8200) -- that notes that EHs
>cannot be inserted in the middle of the network.
>
>This begs a number of questions (e.g., how come that one wg is working
>on something that goes against a spec that is not under its charter).

That would be an IETF process question instead of one about architecture.

>But given this is an architecture list, I wonder if anybody has a say on
>the topic? (including the IAB). Is that the way IPv6 is expected to
>work? What can we expect from IPv6?

The participants in that discussion have a say in the (existing or 
proposed) standards.  There is a discussion of extensions headers in 
RFC 7045.  There is the address allocation aspect which is also 
discussed in other venues, e.g. RIR venues.  There are the security 
and privacy aspects.  At this stage, it may be better to have the 
working group discuss the issues before requesting wider input.

Regards,
S. Moonesamy 


From nobody Thu Sep  5 02:08:14 2019
Return-Path: <alexandre.petrescu@gmail.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 BBFCA120DAD for <architecture-discuss@ietfa.amsl.com>; Thu,  5 Sep 2019 02:08:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level: 
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 v4i1Qtbwhxmy for <architecture-discuss@ietfa.amsl.com>; Thu,  5 Sep 2019 02:08:09 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 203B7120CF2 for <architecture-discuss@ietf.org>; Thu,  5 Sep 2019 02:08:08 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x85987IZ027102 for <architecture-discuss@ietf.org>; Thu, 5 Sep 2019 11:08:07 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5A5092048A3 for <architecture-discuss@ietf.org>; Thu,  5 Sep 2019 11:08:07 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 4FCAD204897 for <architecture-discuss@ietf.org>; Thu,  5 Sep 2019 11:08:07 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x85987De025384 for <architecture-discuss@ietf.org>; Thu, 5 Sep 2019 11:08:07 +0200
To: architecture-discuss@ietf.org
References: <a7b5255b-8570-0e4b-da17-7557e7ca18c1@si6networks.com> <e1895609-e462-e47a-b408-568a5c5363b1@si6networks.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <4a9df8af-c19d-42f7-0760-4e23d15d12d0@gmail.com>
Date: Thu, 5 Sep 2019 11:08:07 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <e1895609-e462-e47a-b408-568a5c5363b1@si6networks.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/O-KHRKiFmCVNc9wI9G0rp_sAAdI>
Subject: Re: [arch-d] Fiddling with IP packets in the network, IPv6-style (Fwd: Question about SRv6 Insert function)
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, 05 Sep 2019 09:08:12 -0000

Le 05/09/2019 Ã  02:47, Fernando Gont a Ã©critÂ :
> Folks,
> 
> There seems to be ongoing working group item in the spring wg
> (https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-01)
> that essentially proposes the insertion of IPv6 Extension Headers by
> middle boxes in the middle of the network, which goes against a very
> explicit requirement in the IPv6 spec (RFC8200) -- that notes that EHs
> cannot be inserted in the middle of the network.
> 
> This begs a number of questions (e.g., how come that one wg is working
> on something that goes against a spec that is not under its charter).
> 
> But given this is an architecture list, I wonder if anybody has a say on
> the topic? (including the IAB). Is that the way IPv6 is expected to
> work? What can we expect from IPv6?

Can we expect IP at large to touch headers of end user packets?  No. 
Can we expect it in a 'limited-domain'?  Yes, and I'd say INFORMATIONALly.

Alex

> 
> 
> 
> -------- Forwarded Message --------
> Subject: Re: Question about SRv6 Insert function
> Date: Thu, 5 Sep 2019 03:34:09 +0300
> From: Fernando Gont <fgont@si6networks.com>
> To: Ole Troan <otroan@employees.org>, Fernando Gont <fernando@gont.com.ar>
> CC: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, spring@ietf.org
> <spring@ietf.org>, 6man@ietf.org <6man@ietf.org>, Suresh Krishnan
> <suresh.krishnan@gmail.com>, draft-voyer-6man-extension-header-insertion
> <draft-voyer-6man-extension-header-insertion@ietf.org>,
> draft-ietf-spring-srv6-network-programming
> <draft-ietf-spring-srv6-network-programming@ietf.org>
> 
> On 4/9/19 09:58, Ole Troan wrote:
>> Fernando,
>>
>>>>> Since there have been plenty of attempts to do EH insertion or
>>>>> leave the IPv6 standard ambiguous in this respect, and the IETF has
>>>>> had consensus that EH insertion is not allowed, I think it would be
>>>>> bad, wastefull, tricky, and even dangerous to let a document go
>>>>> through the whole publication process, and just rely on the AD to
>>>>> keep the "DISCUSS" button pressed.
>>>>>
>>>>> Put another way: what'd be the rationale for having a draft-ietf
>>>>> and have the corresponding wg ship the document with something that
>>>>> clearly goes against IETF consensus, and that the relevant AD has
>>>>> declared that wouldn't let pass?
>>>>
>>>> In short, this is not the case. I am *not* the relevant AD for the
>>>> SRv6 Network Programming draft. If this document was in 6man I would
>>>> have flagged it much earlier like I did for the SRH draft.
>>>
>>> Sorry, what I meant by "relevant AD" is: "one of the responsible ADs for
>>> the spec that's being violated".
>>>
>>> i.e., isn't there in the IETF process -- whether formal or informal --
>>> for this sort of thing to be flagged before documents get too far in the
>>> publication process?  ("Hey, this document in your area is actually
>>> breaking a spec of one of my wgs" sort of thing...)
>>
>> I would prefer that we calmed down a bit on the protocol policing.
> 
> Sorry, but this has nothing to do with protocol policing. It has to do
> with respecting the consensus this wg and the ietf as a whole had on the
> topic. i.e., that EHs must not be inserted in the network.
> 
> We'd go into an interesting path to insanity if we publish specs, and
> subsequently publish conflicting specs that simply ignore previous ietf
> consensus.
> 
> If folks want to do EH insertion, the #1 step is to publish a document
> that updates RFC8200 such that the "EHs must not be inserted..." is
> replaced with something else or eliminated.
> 
> 
> 
>> We know that header insertion breaks unsuspecting source hosts if done by the network.
>> It breaks (at least) PMTUD, ICMP errors and AH.
>>
>> What we have said in the past is; explain how those issues are dealt with or do not apply to your proposal.
> 
> That's what you and others may have said or thought. But the consensus
> is what's in the standard (RFC8200). And the standard says that EHs
> cannot be inserted in the network. If you want to do it, the first step
> is to update RFC8200.
> 
> 
> 
>> And some form of "doing on behalf of" is not necessarily problematic.
> 
> It is rightaway problematic specs-wise when it violates a crystal-clear
> requirement in RFC8200, that we arrived to after a very heated debate,
> and lots of enegery and time from all the involved people.
> 
> The fact that after all the long story behind publication of rfc8200 as
> standard (and the ongoing srv6 document we're doing here, which was
> adopted on the condition that it wouldn't do eh-insertion), we can live
> with other wgs violating specs that we produced here with so much effort
> and time, is kind of amusing.
> 
> If folks want to allow EH-insertion (i.e., formally allowing middleboxes
> to fiddle with packets), RFC8200 should be updated, and the work should
> be done in 6man.
> 
> I don't think it's SPRING's call how the IPv6 protocol works.
> 
> 
> 
>> It's the "blind" "Thou shalt not do" that I object to. As opposed to arguing on technical grounds.
>>
>> Ensuring interoperability is our purpose. Not protect 8200 as if it's a religious text.
> 
> My #1 concern (not that I don't have others) is one related to fairness
> of the standardization process. I don't think we should simply
> rubberstamp anything a big vendor wants to sell, no matter how big the
> vendor is, or how much money may be involved.
> 
> And if this working group (and the IETF as a whole) published a spec on
> which there was consensus, ignoring the spec and doing whatever one
> pleases is not the way to go. Firstly, make e the case for updating
> RFC8200. Then come up with the proposal to fiddle with packets in the
> network.
> 
> P.S.: I've never been into the camp of protecting X (whether rfc8200 or
> any other document) as if it was religious text. Quite ironically, I
> have experienced such religious opposition in 6man itself (for instance,
> your argument of "don't fix slaac-renumbering because ipv6 has not been
> designed to support flash renumbering" seems pretty much a religious
> argument against work that would not result in any major modifications
> to any of the protocols involved -- as opposed to EH insertion).
> 


From nobody Thu Sep  5 05:06:25 2019
Return-Path: <fgont@si6networks.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 088191200C1 for <architecture-discuss@ietfa.amsl.com>; Thu,  5 Sep 2019 05:06:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 ZfJ2q12YGP9c for <architecture-discuss@ietfa.amsl.com>; Thu,  5 Sep 2019 05:06:22 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 673FF1200A1 for <architecture-discuss@ietf.org>; Thu,  5 Sep 2019 05:06:22 -0700 (PDT)
Received: from [192.168.1.14] (ppp-94-69-228-25.home.otenet.gr [94.69.228.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 828DB861CC; Thu,  5 Sep 2019 14:06:19 +0200 (CEST)
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, architecture-discuss@ietf.org
References: <a7b5255b-8570-0e4b-da17-7557e7ca18c1@si6networks.com> <e1895609-e462-e47a-b408-568a5c5363b1@si6networks.com> <4a9df8af-c19d-42f7-0760-4e23d15d12d0@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Openpgp: preference=signencrypt
Message-ID: <e61034c3-6d6c-51da-9252-17e53ebbfbd4@si6networks.com>
Date: Thu, 5 Sep 2019 15:06:11 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <4a9df8af-c19d-42f7-0760-4e23d15d12d0@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/3-a7DkuSPv1qdbY4MdnvNHjAVgw>
Subject: Re: [arch-d] Fiddling with IP packets in the network, IPv6-style (Fwd: Question about SRv6 Insert function)
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, 05 Sep 2019 12:06:24 -0000

On 5/9/19 12:08, Alexandre Petrescu wrote:
> 
> 
> Le 05/09/2019 Ã  02:47, Fernando Gont a Ã©critÂ :
>> Folks,
>>
>> There seems to be ongoing working group item in the spring wg
>> (https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-01)
>>
>> that essentially proposes the insertion of IPv6 Extension Headers by
>> middle boxes in the middle of the network, which goes against a very
>> explicit requirement in the IPv6 spec (RFC8200) -- that notes that EHs
>> cannot be inserted in the middle of the network.
>>
>> This begs a number of questions (e.g., how come that one wg is working
>> on something that goes against a spec that is not under its charter).
>>
>> But given this is an architecture list, I wonder if anybody has a say on
>> the topic? (including the IAB). Is that the way IPv6 is expected to
>> work? What can we expect from IPv6?
> 
> Can we expect IP at large to touch headers of end user packets?Â  No. Can
> we expect it in a 'limited-domain'?Â  Yes, and I'd say INFORMATIONALly.

Spoiler: You can't guarantee with 100% certainty that packets will not
leak out from a "limited domain".


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Thu Sep  5 06:05:17 2019
Return-Path: <fgont@si6networks.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 CBBD9120091 for <architecture-discuss@ietfa.amsl.com>; Thu,  5 Sep 2019 06:05:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 SiCILK_bFJFK for <architecture-discuss@ietfa.amsl.com>; Thu,  5 Sep 2019 06:05:14 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE5B4120026 for <architecture-discuss@iab.org>; Thu,  5 Sep 2019 06:05:13 -0700 (PDT)
Received: from [192.168.1.14] (ppp-94-69-228-25.home.otenet.gr [94.69.228.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id CBE8B861C5; Thu,  5 Sep 2019 15:05:11 +0200 (CEST)
To: Tony Li <tony1athome@gmail.com>
Cc: architecture-discuss@iab.org
References: <a7b5255b-8570-0e4b-da17-7557e7ca18c1@si6networks.com> <e1895609-e462-e47a-b408-568a5c5363b1@si6networks.com> <366eb210-dbd1-08c3-7dc1-483a4678656d@cs.tcd.ie> <ae5ccbc2-d344-2dea-7954-ecb4c5b8ba26@si6networks.com> <C31553B4-1B25-48E1-8A79-92B96FAB08C7@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Openpgp: preference=signencrypt
Message-ID: <4073e87f-94fe-8f5c-5009-23a2249eac65@si6networks.com>
Date: Thu, 5 Sep 2019 16:04:59 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <C31553B4-1B25-48E1-8A79-92B96FAB08C7@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/DpWHRQNu8Ih11N0mhrmIg_ZT8K0>
Subject: Re: [arch-d] Fiddling with IP packets in the network, IPv6-style (Fwd: Question about SRv6 Insert function)
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, 05 Sep 2019 13:05:16 -0000

On 5/9/19 04:37, Tony Li wrote:
>> Besides procedural issues, the ultimate implications of this is that
>> we're formally introducing middle-boxes that fiddle with packets in the
>> middle of the network.
> 
> 
> Didnâ€™t we have this same discussion 25 years ago on NAT boxes?
> 
> The fact of the matter is that the IETF is completely helpless to
> prevent such things.Â 
> True, it can block standardization, but if the market wants it, the
> market will drive it
> and all that the IETF does is to make itself irrelevant to the process.

Or it could at least push for the cleaner options: e.g., I see no reason
for doing eh-insertion as opposed to encapsulating the packet into a new
ipv6 packet, and create that packets with the headers you need.




>> Isn't this within the kind of stuff the IAB has interest on?
> 
> 
> If it were, the first complaint would be about SRv6 itself.
> 
> The IABâ€™s only role is that of genteel education and itâ€™s a target rich
> environment.

So... who cares about architecture, then?

Thanks!

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Mon Sep  9 08:26:02 2019
Return-Path: <vittorio.bertola@open-xchange.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 448ED1201EA for <architecture-discuss@ietfa.amsl.com>; Mon,  9 Sep 2019 08:26:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level: 
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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=open-xchange.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 xA9mIeMv_oBr for <architecture-discuss@ietfa.amsl.com>; Mon,  9 Sep 2019 08:25:58 -0700 (PDT)
Received: from mx4.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (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 0EA23120819 for <Architecture-discuss@ietf.org>; Mon,  9 Sep 2019 08:25:51 -0700 (PDT)
Received: from open-xchange.com (imap.open-xchange.com [10.20.30.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx4.open-xchange.com (Postfix) with ESMTPS id 883206A262 for <Architecture-discuss@ietf.org>; Mon,  9 Sep 2019 17:25:47 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1568042747; bh=EHa2PykbQGmdAEcyqtgi9v6ICyWFo9XiIqHIqhYcPJ4=; h=Date:From:Reply-To:To:Subject:From; b=ihOoT3AAZP9okgegyoA++eegOBVJViy29XAmXcNKGdEt1fbFRnuO0a7n68UjwGR0h VAZorY/8oDD59W/x9ahNIYuNI92soc9KZl6gS76ynGFJUfa95Zs7Jr9aJvBCVpVG3e QnMPObrolM+KTAPnvaUM0Lx6RTXwjYJ9eSR+bjWAy2YSsgsNJuyLygly9ZjoC0d3SQ GGt1cza6J4KHnnXNrXv2yDvzDtXHkNrdDmB5OglRAiuKr660kkSyE6c0++U/vpy5W3 0bfbKa3+jrrfw+PF0L2KBScZM5WIXIPZl1f+/i1dGqS10dAhp0fo8BSw01lPqgtTsw 6PaBylVd9nNtQ==
Received: from appsuite-gw2.open-xchange.com (appsuite-gw2.open-xchange.com [10.20.28.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by open-xchange.com (Postfix) with ESMTPSA id 7DBBB3C0191 for <Architecture-discuss@ietf.org>; Mon,  9 Sep 2019 17:25:47 +0200 (CEST)
Date: Mon, 9 Sep 2019 17:25:47 +0200 (CEST)
From: Vittorio Bertola <vittorio.bertola@open-xchange.com>
Reply-To: Vittorio Bertola <vittorio.bertola@open-xchange.com>
To: "Architecture-discuss@ietf.org" <Architecture-discuss@ietf.org>
Message-ID: <1690075590.4837.1568042747417@appsuite-gw2.open-xchange.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.2-Rev12
X-Originating-Client: open-xchange-appsuite
Autocrypt: addr=vittorio.bertola@open-xchange.com; prefer-encrypt=mutual; keydata= mQENBFhFR+UBCACfoywFKBRfzasiiR9/6dwY36eLePXcdScumDMR8qoXvRS55QYDjp5bs+yMq41qWV9 xp/cqryY9jnvHbeF3TsE5yEazpD1dleRbkpElUBpPwXqkrSP8uXO9KkS9KoX6gdml6M4L+F82WpqYC1 uTzOE6HPmhmQ4cGSgoia2jolxAhRpzoYN99/BwpvoZeTSLP5K6yPlMPYkMev/uZlAkMMhelli9IN6yA yxcC0AeHSnOAcNKUr13yXyMlTyi1cdMJ4sk88zIbefxwg3PAtYjkz3wgvP96cNVwAgSt4+j/ZuVaENP pgVuM512m051j9SlspWDHtzrci5pBKKFsibnTelrABEBAAG0NUJlcnRvbGEsIFZpdHRvcmlvIDx2aXR 0b3Jpby5iZXJ0b2xhQG9wZW4teGNoYW5nZS5jb20+iQFABBMBAgAqBAsJCAcGFQoJCAsCBRYCAwEAAp 4BAhsDBYkSzAMABQMAAAAABYJYRUflAAoJEIU2cHmzj8qNaG0H/ROY+suCP86hoN+9RIV66Ej8b3sb8 UgwFJOJMupZfeb9yTIJwE4VQT5lTt146CcJJ5jvxD6FZn1Htw9y4/45pPAF7xLE066jg3OqRvzeWRZ3 IDUfJJIiM5YGk1xWxDqppSwhnKcMOuI72iioWxX0nGQrWxpnWJsjt08IEEwuYucDkul1PHsrLJbTd58 fiMKLVwag+IE1SPHOwkPF6arZQZIfB5ThtOZV+36Jn8Hok9XfeXWBVyPkiWCQYVX39QsIbr0JNR9kQy 4g2ZFexOcTe8Jo12jPRL7V8OqStdDes3cje9lWFLnX05nrfLuE0l0JKWEg8akN+McFXc+oV68h7nu5A Q0EWEVH5QEIAIDKanNBe1uRfk8AjLirflZO291VNkOAeUu+dIhecGnZeQW6htlDinlYOnXhtsY1mK9W PUu+xshDq7lXn2G0LxldYwyJYZaJtDgIKqVqwxfA34Lj27oqPuXwcvGhdCgt0SW/YcalRdAi0/AzUCu 5GSaj2kaGUSnBYYUP4szGJXjaK2psP5toQSCtx2pfSXQ6MaqPK9Zzy+D5xc6VWQRp/iRImodAcPf8fg JJvRyJ8Jla3lKWyvBBzJDg6MOf6Fts78bJSt23X0uPp93g7GgbYkuRMnFI4RGoTVkxjD/HBEJ0CNg22 hoHJondhmKnZVrHEluFuSnW0wBEIYomcPSPB+cAEQEAAYkBMQQYAQIAGwUCWEVH5QIbDAQLCQgHBhUK CQgLAgUJEswDAAAKCRCFNnB5s4/KjdO8B/wNpvWtOpLdotR/Xh4fu08Fd63nnNfbIGIETWsVi0Sbr8i E5duuGaaWIcMmUvgKe/BM0Fpj9X01Zjm90uoPrlVVuQWrf+vFlbalUYVZr51gl5UyUFHk+iAZCAA0WB rsmACKvuV1P7GuiX3UV9b59T9taYJxN3dNFuftrEuvsqHimFtlekUjUwoCekTJdncFusBhwz2OrKhHr WWrEsXkfh0+pURWYAlKlTxvXuI7gAfHEQM+6OnrWvXYtlhd0M1sBPnCjbyG63Qws7Rek9bEWKtH6dA6 dmT2FQT+g1S9Mdf0WkPTQNX0x24dm8IoHuD3KYwX7Svx43Xa17aZnXqUjtj1
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/yZzU3COA1IFeGT3O6BH9IdX6DQQ>
Subject: [arch-d] IAB statement on "Avoiding Unintended Harm to Internet Infrastructure"
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: Mon, 09 Sep 2019 15:26:00 -0000

Hello,

after a brief discussion on ietf@ietf.org, it was suggested that this is the appropriate list to discuss the recent IAB statement on "Avoiding Unintended Harm to Internet Infrastructure" ( https://www.iab.org/documents/correspondence-reports-documents/2019-2/avoiding-unintended-harm-to-internet-infrastructure/ ) - if not, please redirect me to the appropriate place.

It is unclear to me what prompted the IAB to release this statement at this point in time, so possibly I miss parts of the picture. Also I do not know if it has been discussed with the community and where. Still, I found it surprising in several points, and confusing in others.

In the DNS section, it is disheartening to read the IAB stating that "[a DNS resolver] returning the wrong (or no) address breaks the trust that users have in this infrastructure", after having spent months on the ADD list and elsewhere to explain that there are indeed lots of use cases in which users expect, or even actively request, that their resolver applies filters to the responses. In some cases it is actually the opposite - if I acquire a DNS-based service to prevent any accidental connection to malware-infected websites and then I get malware, that's when I lose trust in my DNS resolver; same for parental controls.

More generally, the entire document sounds like a claim that the Internet's infrastructure and those who run it need to be exempt from cooperation with law enforcement activities, and totally unregulated. However, there is some incoherence between the considerations in most of the text and the final recommendations.

For example, the second bullet in the recommendations asks to exempt *communication* between network operators/DNS operators/PKI vendors from any law enforcement requirements, i.e. "do not break encryption". 

However, the main text argues against other possible requests from law enforcement, such as CAs being asked to "issue a certificate improperly", or network operators redirecting traffic to law enforcement agencies. These practices are not related to communication between network operators, but to the actions of each single operator, so it is unclear whether the IAB in the end recommends against them or not; in the recommendations, it then mentions "endpoint-focused interventions" only to suggest that those who are subject to them should be listed explicitly in the regulation (which, by the way, is not how a law can work).

Similarly, the section titled "Impact on Internet evolution" seems to argue against regulation of the Internet, but in the final section there is no recommendation against regulation, just a request to involve all stakeholders when discussing it.

It would be nice if we could understand better what is the objective that the IAB wants to achieve with this statement and what does it actually recommend, before commenting further.

Thanks,
-- 
Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
vittorio.bertola@open-xchange.com 
Office @ Via Treviso 12, 10144 Torino, Italy


From nobody Tue Sep 10 09:43:11 2019
Return-Path: <execd@iab.org>
X-Original-To: architecture-discuss@ietf.org
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E2D01120115 for <architecture-discuss@ietf.org>; Tue, 10 Sep 2019 09:43:08 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IAB Executive Administrative Manager <execd@iab.org>
To: <architecture-discuss@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: architecture-discuss@ietf.org
Message-ID: <156813378885.27612.103959718007882643.idtracker@ietfa.amsl.com>
Date: Tue, 10 Sep 2019 09:43:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/NlURhrtNNml9ruccwo4QoejGmQ8>
Subject: [arch-d] IAB Adoption of draft-thomson-escape-report-00
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 10 Sep 2019 16:43:09 -0000

The IAB will discuss adoption of draft-thomson-escape-report-00 (Report 
from the IAB Workshop on Exploring Synergy between Content Aggregation 
and the Publisher Ecosystem (ESCAPE)) at its meeting on 2019-09-18.

The draft can be found here: 
https://datatracker.ietf.org/doc/draft-thomson-escape-report/

The agenda for the meeting will be posted 48 hours ahead of the meeting 
here: https://www.iab.org/wiki/index.php/Agenda

Feedback about this draft can be sent in response to this mail on 
architecture-discuss@ietf.org, or to the IAB directly at iab@iab.org.


From nobody Tue Sep 10 19:04:55 2019
Return-Path: <brian.e.carpenter@gmail.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 00739120088 for <architecture-discuss@ietfa.amsl.com>; Tue, 10 Sep 2019 19:04:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 jTMy32KLSUFs for <architecture-discuss@ietfa.amsl.com>; Tue, 10 Sep 2019 19:04:51 -0700 (PDT)
Received: from mail-pg1-x544.google.com (mail-pg1-x544.google.com [IPv6:2607:f8b0:4864:20::544]) (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 750BF1207FE for <architecture-discuss@ietf.org>; Tue, 10 Sep 2019 19:04:51 -0700 (PDT)
Received: by mail-pg1-x544.google.com with SMTP id n4so10701388pgv.2 for <architecture-discuss@ietf.org>; Tue, 10 Sep 2019 19:04:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=l00ETzA9TeQycUvFHX1UL7u6VIy6ZJkxCLHJhygPr8o=; b=E+V8poLMCY5q7kI8KqU9ZZHP25Z3MTdKgSRINJvhT0L0CBR8tUn8IxpIylke6yCXN0 piMZiNsriOhRuzrrA0vY/Vts1NKhUe8A5OMoAqDjRF6Jrp8NUHa2dTIF0RsL0PWatwfj TOP7CUdqND36wK+TqJnZ+cHa0mR7Yz+EWWExTTZeMqyD7YhI9F363SUF5PJdsd5T0gOb jASE5i4sbbogSzqsKr056uWqImcZ7u3TBHIHp+jcla7V29hvEVvCKF0mCVlwLyvCk96j X2QKD8mHt2oRBy/5UWvfftqt1keTAfF10GasHzbu4lh26rAOF7usF3pQru3tqqWJOwbC YPlA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=l00ETzA9TeQycUvFHX1UL7u6VIy6ZJkxCLHJhygPr8o=; b=Pzua/dqKrtCv7pF+GvAJljrD7PKcMKMSy2pHq/lnfmfi99R0EiU6AXAggVwdnT9ZIp OFryxICibLAokWTTfCx5Mu3+XCaU8ZHS1zlrAn1SuxBB9cgJovvZzI4Cpy5z4wILHWKi gaWAauPR/qWaBQDwW6hKTphBGORDJruLGpoC2XtJIqSUaWO2ZRGaaIf88y5xPHmBLnQK XHOMG8eIbKcZZlhLXwQvzMoXFoQPY9ox1hhXGgoIOsaglWXUVZRxkcOkSD3nroRc/BCJ aHT3i9pDruqsc/4cctdftaC3LehsYVVi3SMUlRxOgwjbQ00JfwB9qBtv4E/NyRShqF27 NyIw==
X-Gm-Message-State: APjAAAUHAgUKzS8BSUvc9ISA2IjhdttbRQ+Lh4g5gD2DXXEzJR5AdMbc wfjapXP5N/DV18N/WGqMos6LYUYy
X-Google-Smtp-Source: APXvYqxqliX+JsbZo+o5vMSOEuYydpAlWofczciKLkGMutr9Y1j96hYpRsNddGJ4OXPOEhINGfFxQw==
X-Received: by 2002:a17:90a:9749:: with SMTP id i9mr2843476pjw.42.1568167490839;  Tue, 10 Sep 2019 19:04:50 -0700 (PDT)
Received: from [192.168.178.30] (82.206.69.111.dynamic.snap.net.nz. [111.69.206.82]) by smtp.gmail.com with ESMTPSA id l124sm18412928pgl.54.2019.09.10.19.04.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Sep 2019 19:04:50 -0700 (PDT)
To: architecture-discuss@ietf.org, iab@iab.org
References: <156763077985.22753.8206505094680303304.idtracker@ietfa.amsl.com>
Cc: RFC Interest <rfc-interest@rfc-editor.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <20e11a4f-26d6-24e3-f82e-b3a2bc8d1eec@gmail.com>
Date: Wed, 11 Sep 2019 14:04:46 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <156763077985.22753.8206505094680303304.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/pRCWT_bYP7y3TauytctxNT6SDyE>
Subject: Re: [arch-d] Call for Comment: <draft-ietf-iasa2-rfc6635bis-03> (RFC Editor Model (Version 2))
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: Wed, 11 Sep 2019 02:04:54 -0000

Hi,

I believe this draft does represent the consensus of the IASA2 WG and cleans up some loose ends from the IAOC to IETF LLC transition. However, I believe that it should not be published as an RFC. The discussions that will soon start about the future of the RFC Editor model make that rather pointless.

Regards
   Brian Carpenter

On 05-Sep-19 08:59, IAB Executive Administrative Manager wrote:
> This is an announcement of an IETF-wide Call for Comment on 
> draft-ietf-iasa2-rfc6635bis-03.
> 
> The document is being considered for publication as an Informational RFC 
> within the IAB stream, and is available for inspection at:
> <https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc6635bis/>
> 
> The Call for Comment will last until 2019-10-02. Please send comments to
> architecture-discuss@ietf.org and iab@iab.org.
> 
> Abstract
> 
>    The RFC Editor model described in this document divides the
>    responsibilities for the RFC Series into three functions: the RFC
>    Series Editor, the RFC Production Center, and the RFC Publisher.
>    Internet Architecture Board (IAB) oversight via the RFC Series
>    Oversight Committee (RSOC) is described, as is the relationship
>    between the IETF Administration Limited Liability Company and the
>    RSOC.  This document reflects the experience gained with "RFC Editor
>    Model (Version 1)", documented in RFC 5620; and obsoletes RFC 6635 to
>    replace all references to the IASA and related structures with those
>    defined by the IASA 2.0 Model.
> 
>    [RFC Editor: Please remove the following paragraph prior to
>    publication.]
> 
>    The IASA2 WG requests that the IAB publish this replacement for RFC
>    6635.
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
> 


From nobody Tue Sep 10 19:06:39 2019
Return-Path: <brian.e.carpenter@gmail.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 8200A1200E0 for <architecture-discuss@ietfa.amsl.com>; Tue, 10 Sep 2019 19:06:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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_HELO_NONE=0.001, 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 VmrHuVQTinFI for <architecture-discuss@ietfa.amsl.com>; Tue, 10 Sep 2019 19:06:33 -0700 (PDT)
Received: from mail-pf1-x431.google.com (mail-pf1-x431.google.com [IPv6:2607:f8b0:4864:20::431]) (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 5D5E11200C4 for <architecture-discuss@ietf.org>; Tue, 10 Sep 2019 19:06:33 -0700 (PDT)
Received: by mail-pf1-x431.google.com with SMTP id y22so12667905pfr.3 for <architecture-discuss@ietf.org>; Tue, 10 Sep 2019 19:06:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=2HAwgEbYHRDBnsTEdoGI/mqAHpaXFGBCKbggwLXy9xw=; b=l88SvyTsZD4khY+N248UrPy5b30xQeFAyxM0/ss1k9S/Tf2E/wb+Gzy+hLLxRyFjPV 2wQmVXytK+S02m+XsjMYDYaPLuncnDlC4q5L4TNyAEEW6w3nhuaCowwDsonhbY5ewSgX Ey1w82XwmPZrqJpgXbKvS6/ZJs+52hrXWRQxLWraiPA8wYoowaqF9AAUlS1+pCB9UVa0 tlHYlavvmAGRnvkJlVIYoR/lYyZxplD76GtCmtBEuzg6dYZ3Ts0czWAlx26v/HF6yNyX /qT4+nenWbMqZffTiOY8JH4gy6c0O5Xsc3eX+/7jpCrDuuMMWfxIp6WjAvzQBnPBRUzM xKLQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=2HAwgEbYHRDBnsTEdoGI/mqAHpaXFGBCKbggwLXy9xw=; b=MwPBYTH1pgV+L8vOG60ovEKfOq7BPopkmQV1obsnK09NE0tVtrlhjhiwpzHUsBylVn OxKK9lqWgBmlAA7/zVlJYFe3s0We1h+uvgOCyj+XUcwfPoPFe70VOLp+L5QB3tILmELs Tt9yU8jS82svKQWxloOcGZY4P3tTBwogC/AyP13ACVbNlE/3dFAM9KjxSeiTNOVvEepj QA87MX6xD9RQ/Zfo7aSkhyaKGAEXdZpwaqKKIAvTDRLLnkpGENPviwCFwLmpIep3DrAq 70RBtni5YtIpor3HqT730wK0RtsUq5snbeyFAqyNaJd6ISazKCr+4ZnswEjgExtQxDUs 0BJw==
X-Gm-Message-State: APjAAAVFeRc6KU9okvX1xyHeBOijBjSEwcYxX6bHRsqm3zu+VOjrhiil N0gPsNramyeZIX4RTG16U+E=
X-Google-Smtp-Source: APXvYqx6Z3mVnWXxjkRRgvynjFezE5APDbUaG4T7vis02d1OkJh78t6T+aX8PP944PjcDS8MyRsG9Q==
X-Received: by 2002:a62:2b4d:: with SMTP id r74mr8410775pfr.30.1568167592958;  Tue, 10 Sep 2019 19:06:32 -0700 (PDT)
Received: from [192.168.178.30] (82.206.69.111.dynamic.snap.net.nz. [111.69.206.82]) by smtp.gmail.com with ESMTPSA id p68sm34638300pfp.9.2019.09.10.19.06.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Sep 2019 19:06:32 -0700 (PDT)
To: architecture-discuss@ietf.org, iab@iab.org
References: <156763101565.22770.5246009160641276406.idtracker@ietfa.amsl.com>
Cc: RFC Interest <rfc-interest@rfc-editor.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <f67a89c9-20be-cd2d-0d5b-2b288268baaa@gmail.com>
Date: Wed, 11 Sep 2019 14:06:28 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <156763101565.22770.5246009160641276406.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/XTdiMJvJe99sQOhWQgoyfW-rDUI>
Subject: Re: [arch-d] Call for Comment: <draft-ietf-iasa2-rfc4844-bis-02> (The RFC Series and RFC Editor)
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: Wed, 11 Sep 2019 02:06:36 -0000

Hi,

I believe this draft does represent the consensus of the IASA2 WG and cleans up some loose ends from the IAOC to IETF LLC transition. However, I believe that it should not be published as an RFC. The discussions that will soon start about the future of the RFC Editor model make that rather pointless.

Regards
   Brian Carpenter
On 05-Sep-19 09:03, IAB Executive Administrative Manager wrote:
> This is an announcement of an IETF-wide Call for Comment on 
> draft-ietf-iasa2-rfc4844-bis-02.
> 
> The document is being considered for publication as an Informational RFC 
> within the IAB stream, and is available for inspection at:
> <https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc4844-bis/>
> 
> The Call for Comment will last until 2019-10-02. Please send comments to
> architecture-discuss@ietf.org and iab@iab.org.
> 
> Abstract
> 
>    This document describes the framework for an RFC Series and an RFC
>    Editor function that incorporate the principles of organized
>    community involvement and accountability that has become necessary as
>    the Internet technical community has grown, thereby enabling the RFC
>    Series to continue to fulfill its mandate.
> 
>    Cover Note:
> 
>    {{ RFC Editor: Please remove this cover note prior to publication. }}
> 
>    The IASA2 WG asks the IAB to publish this replacement for RFC 4844.
>    The document is changed for alignment with the new structure for the
>    IETF Administrative Support Activity (IASA), eliminating all
>    references to the IETF Administrative Oversight Committee (IAOC).
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
> 


From nobody Tue Sep 10 23:24:20 2019
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 D27C5120814; Tue, 10 Sep 2019 23:24:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.276
X-Spam-Level: 
X-Spam-Status: No, score=0.276 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DEAR_SOMETHING=1.973, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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=opendkim.org header.b=TKG1JeCb; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=3Pc0gQM8
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 uQhNzvh7PLGd; Tue, 10 Sep 2019 23:24:16 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id BDA1512026E; Tue, 10 Sep 2019 23:24:16 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.186.197]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id x8B6O4S5004767 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Sep 2019 23:24:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1568183055; x=1568269455; bh=6j2L22cpL4Hc+nMGi22XvxZ7eVQ2qOoTVsDjhfQmoD8=; h=Date:To:From:Subject:In-Reply-To:References; b=TKG1JeCbC4+iG0jkixrz/XAFF7KqKl3OQeHGoj3R3BuS1Lw4Z/s0YIRTU4LzVC3rS SzFj1m115fQVKbpGa0cItGcKaUo5WK0teSrmV2yCJHlu8CZzqMtmhfEizpAaAuHFoY MvA4h5SYKNORPb0XHjhBy+M1MRzThnMDD4xDCbqo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1568183055; x=1568269455; i=@elandsys.com; bh=6j2L22cpL4Hc+nMGi22XvxZ7eVQ2qOoTVsDjhfQmoD8=; h=Date:To:From:Subject:In-Reply-To:References; b=3Pc0gQM8DtLy1y7aHhqFl82f6AY4HvMZy/3m4VJdimRZAMHCadBl7keTaX7WlDd4h nBcgRi2R54/XM2DcZC6D9oWqZJl13lPI2aal+Yr76fKsRJ5WPz5Why5MI7ccYfHpn9 mEuSABOwSPxCZVEWlcJ2sMpDAbDlV7bM+A3YszfY=
Message-Id: <6.2.5.6.2.20190910225210.0b9b30a0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 10 Sep 2019 23:22:43 -0700
To: architecture-discuss@ietf.org, iab@iab.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <156763077985.22753.8206505094680303304.idtracker@ietfa.ams l.com>
References: <156763077985.22753.8206505094680303304.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/2k3ChHHYioWo7K0lawS965DQYfE>
Subject: Re: [arch-d] Call for Comment: <draft-ietf-iasa2-rfc6635bis-03> (RFC Editor Model (Version 2))
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: Wed, 11 Sep 2019 06:24:18 -0000

Dear Internet Architecture Board,
At 01:59 PM 04-09-2019, IAB Executive Administrative Manager wrote:
>This is an announcement of an IETF-wide Call for Comment on
>draft-ietf-iasa2-rfc6635bis-03.
>
>The document is being considered for publication as an Informational RFC
>within the IAB stream, and is available for inspection at:
><https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc6635bis/>
>
>The Call for Comment will last until 2019-10-02. Please send comments to
>architecture-discuss@ietf.org and iab@iab.org.

The is a misspelled word in last sentence at the bottom of Page 3 of the draft.

There has been a significant discussion of the RFC Editor Model since 
July.  Section 2.1.5 of draft-ietf-iasa2-rfc6635bis-03 was not 
adhered to since several years.  The qualification described in 
Section 2.1.6 does not reflect what would be sought in a person to 
fulfill the role of RFC Series Editor.  The description of the 
oversight role of the RFC Series Oversight Committee, described in 
Section 3.1, is not aligned with what could be envisioned for the RFC Series.

Given the above, it is not judicious to publish 
draft-ietf-iasa2-rfc6635bis-03 as a RFC without an adequate review of 
the draft.

Regards,
S. Moonesamy





From nobody Wed Sep 25 10:26:34 2019
Return-Path: <alissa@cooperw.in>
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 1538C120124 for <architecture-discuss@ietfa.amsl.com>; Wed, 25 Sep 2019 10:26:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=cooperw.in header.b=h36XBb5d; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=A79mOty3
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 eUZxbnbKo8A3 for <architecture-discuss@ietfa.amsl.com>; Wed, 25 Sep 2019 10:26:30 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D63012008A for <architecture-discuss@ietf.org>; Wed, 25 Sep 2019 10:26:22 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 95D472247C; Wed, 25 Sep 2019 13:26:21 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 25 Sep 2019 13:26:21 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= from:content-type:content-transfer-encoding:mime-version:subject :date:references:to:in-reply-to:message-id; s=fm1; bh=aDu8JvPqUO 8CJCHZ3GFaJqDsvoUeDrzgiKeM1Mc9WWU=; b=h36XBb5dxJAetZOzWMOxTpO6Q7 o1S6XDPl0JuezXv8CkbFcmPDMUBsgz6IPpAC8zy4la2zVGJZ2iXdQKEYPgu+rWsG jHQsAJZlCVL0282/8NpvCZcGhzJH1qVoEQgBan3AMwHUhnA1FYxSa/4dTPKulen8 Z3h1WbCQ7Imvve3bqgaUePgJWGT28zfhbv/sNcqtEFZZ7mNbGX/SV8ZO3nx0gwf4 B4TD6Fm3YqgIK493hSHjxSehLQOWzNokH3ygeu0mtQ8Q5EOaxu4ogmPLksLplxlc ezgWXbYIbqNt+y4p4yHtDLvrEOEp1fwNwpI2dkYeBvtcwrNOKtDvPnDIiofA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=aDu8JvPqUO8CJCHZ3GFaJqDsvoUeDrzgiKeM1Mc9W WU=; b=A79mOty32XAg+DTk+Y2AtKRbslc0zn7lEjpBPekTYs5ua+MPifGLepri2 RBHysiB5wrL5XTDcU3y5R1qohtKLtQh+/Dp4LKbg9a5cfHw9x//Evfb4vnF/vUW5 vwrCJiuu8biUXUVUkf9HmqSFAk00BVVOzhD6Jiy+NnCmdaF1/s9dgr9VBsG7Z/og TXXzbwMnjSkaiUasN6F6mRzZlGktr4f6Bk/USAUW3jrn49P0WAOHPciOcYd1cJkk cMnjHyjzsHRxdrladoqgT8jya0OwtsFhQoIh1wI17L4qxQvRHOHzhGLAbesd3yLn 2eALB8qZ7ft4MTbQvfyQ3dc+4MFjA==
X-ME-Sender: <xms:PaOLXYyNgHi5Y2nYKofKU6rTj33S36sczhoOlElqfVVQNuy6WVvnSQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrfedvgdduudefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhtgfgggfuffhfvfgjkffosehtqh hmtdhhtddvnecuhfhrohhmpeetlhhishhsrgcuvehoohhpvghruceorghlihhsshgrsegt ohhophgvrhifrdhinheqnecuffhomhgrihhnpehivghtfhdrohhrghenucfkphepkedtrd dvhedurdduiedvrdduieegnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhishhsrges tghoohhpvghrfidrihhnnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:PaOLXRgW98Hc6Kjh4YyzJ6FqdMB3IQ8ggjDmTu0qbWtxSbachbw1eQ> <xmx:PaOLXcCXwZoxrgNLSietiUCyEnVTYtBCJHHiHfFeAEI92rs-PBUNmQ> <xmx:PaOLXesSDWw8RZRo9FmX_uGLTDW5EM2ImWlx2U0vmKHE1MP-xAfGPQ> <xmx:PaOLXcdkYFFrF_6Tk2t0pMWvrFoVTIy5OfpmcVoqyYtxtpIePnm-wQ>
Received: from [172.16.56.213] (unknown [80.251.162.164]) by mail.messagingengine.com (Postfix) with ESMTPA id 96D0C8005A; Wed, 25 Sep 2019 13:26:20 -0400 (EDT)
From: Alissa Cooper <alissa@cooperw.in>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Wed, 25 Sep 2019 18:26:18 +0100
References: <156763101565.22770.5246009160641276406.idtracker@ietfa.amsl.com>
To: architecture-discuss@ietf.org, iab@iab.org
In-Reply-To: <156763101565.22770.5246009160641276406.idtracker@ietfa.amsl.com>
Message-Id: <281D3BF8-CE5E-46D3-B4F4-F0289606C308@cooperw.in>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/qlx-BoTweYTTvy6mZxEnA2GnhBY>
Subject: Re: [arch-d] Call for Comment: <draft-ietf-iasa2-rfc4844-bis-02> (The RFC Series and RFC Editor)
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: Wed, 25 Sep 2019 17:26:32 -0000

Hi,

I have a few comments on this document.

Section 3.3:

The first paragraph of this section fails to mention the IAB and RSOC, =
which according to RFC 6635 have oversight roles. It seems incorrect to =
claim that operational oversight is solely the responsibility of IASA.

The second paragraph is superfluous since the roles of the LLC Board and =
ED are defined in rfc4071bis, so I think for clarity it should be =
removed.

The resulting changes could appear as follows:

OLD=20
The IETF Administration Limited Liability Company (IETF LLC), as part of =
the IETF Administrative Support Activity (IASA), is responsible for =
administrative and financial matters for the IETF, the IAB, and the =
Internet Research Task Force (IRTF) [I-D.ietf-iasa2-rfc4071bis]. The =
IASA is tasked with providing the funding for and operational oversight =
of the RFC Editor.

The IETF LLC Board provides oversight of the IASA, and the IETF =
Executive Director is the chief actor for the IASA.

The IETF Executive Director works with the IAB to identify suitable =
persons or entities to fulfill the mandate of the RFC Editor.

NEW=20
The IETF Administration Limited Liability Company (IETF LLC), as part of =
the IETF Administrative Support Activity (IASA), is responsible for =
administrative and financial matters for the IETF, the IAB, and the =
Internet Research Task Force (IRTF) [I-D.ietf-iasa2-rfc4071bis].The IASA =
is tasked with providing the funding for the RFC Editor. The IASA, the =
IAB, and the RFC Series Oversight Committee (RSOC) provide operational =
oversight of the RFC Editor.

The IETF Executive Director works with the IAB to identify suitable =
persons or entities to fulfill the mandate of the RFC Editor.


Section 7:

I would suggest the following to make the text consistent with =
rfc4071bis Sec. 4.2:

OLD
   Under the new structure, the IETF LLC performs the tasks that were
   previously assigned to the IETF Administrative Oversight Committee
   (IAOC) under the old structure.

NEW
   Under the new structure, the IETF LLC performs the tasks related to =
IASA that were
   previously assigned to the IETF Administrative Director and to the =
Internet Society.


Thanks,
Alissa


> On Sep 4, 2019, at 10:03 PM, IAB Executive Administrative Manager =
<execd@iab.org> wrote:
>=20
> This is an announcement of an IETF-wide Call for Comment on=20
> draft-ietf-iasa2-rfc4844-bis-02.
>=20
> The document is being considered for publication as an Informational =
RFC=20
> within the IAB stream, and is available for inspection at:
> <https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc4844-bis/>
>=20
> The Call for Comment will last until 2019-10-02. Please send comments =
to
> architecture-discuss@ietf.org and iab@iab.org.
>=20
> Abstract
>=20
>   This document describes the framework for an RFC Series and an RFC
>   Editor function that incorporate the principles of organized
>   community involvement and accountability that has become necessary =
as
>   the Internet technical community has grown, thereby enabling the RFC
>   Series to continue to fulfill its mandate.
>=20
>   Cover Note:
>=20
>   {{ RFC Editor: Please remove this cover note prior to publication. =
}}
>=20
>   The IASA2 WG asks the IAB to publish this replacement for RFC 4844.
>   The document is changed for alignment with the new structure for the
>   IETF Administrative Support Activity (IASA), eliminating all
>   references to the IETF Administrative Oversight Committee (IAOC).
>=20
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce


From nobody Fri Sep 27 06:34:12 2019
Return-Path: <alissa@cooperw.in>
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 CF0E0120073 for <architecture-discuss@ietfa.amsl.com>; Fri, 27 Sep 2019 06:34:10 -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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=UTNifDTd; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ugrwPvqB
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 P6mejHDz95nK for <architecture-discuss@ietfa.amsl.com>; Fri, 27 Sep 2019 06:34:07 -0700 (PDT)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9520B120043 for <architecture-discuss@ietf.org>; Fri, 27 Sep 2019 06:34:07 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 120DA6D5; Fri, 27 Sep 2019 09:34:07 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Fri, 27 Sep 2019 09:34:07 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= from:content-type:content-transfer-encoding:mime-version:subject :date:references:to:in-reply-to:message-id; s=fm1; bh=JMKL/NhvSJ CSPpclbq8tL5VQsx/g7ZM9tmaLG+qXFd0=; b=UTNifDTdkodLcvPZVhLeQnP1cO tZzQSqf6FnBkPUREaKu0cQ3c0irU2ZMH6KwdTvafJD6Td5aCmemrgvCTPK8NjBMK zdhi3Khf0KhNaruG9nnkeqZr/6b3Nu/tYsWxcutSn0qRZqBTbKvFaIu8HcfzP7N9 UBQLcUlIdJjDcQQXDpwh0YcUT4iZ/Bd/J96Mr6em/x+9UGclYLy9K1eiyZzmB9vp X9i+e7UwvvntkvAkNxc1/zPMmdqpesjrtBtipECk7jJK6LZ7nDFM+OtTmErJcS9d 3jernEDB6bXlhmfLPhc08+Ece6Ai/m/Toxg2fQYrsWrL6gK29+jI3oRMvt2g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=JMKL/NhvSJCSPpclbq8tL5VQsx/g7ZM9tmaLG+qXF d0=; b=ugrwPvqBCC6KTBMNJAXDn6fHMdQL6szKEMdQW6ZScqv8g0hNLaQy/azoi HwF6WOEQ9xwzCClKmuvWYCWoVrsnFwNrQGtxGyAJkb8gxXcx45nCfa3wKFzjFBhR n3C09cJAUalLEDtJiXjjXfZNcOex2oZg5UxzswsMExG7AlmYVGmjB0bumonbb82A //w3UBZ5ihYK2lEnhHiM40JPx4JjP1DTAaBpPrntat0JsSuu9CDM6aDzlVl1G437 MEaHs3G1YcZNDt2kT7ErPT1vLKVpOFUBdmEJX+LpdrfWPlhdKe1F01awhaEwdn+b 8sCoxkAFfdTB0XyjuqGYO5+QfL07Q==
X-ME-Sender: <xms:zg-OXdkBT03mf7T7XKqtNy3hWQRdAUvedcn20k3uP0VFZufUofV75A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrfeeigdeigecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephfgtgfgguffffhfvjgfkofesthhqmh dthhdtvdenucfhrhhomheptehlihhsshgrucevohhophgvrhcuoegrlhhishhsrgestgho ohhpvghrfidrihhnqeenucffohhmrghinhepghhithhhuhgsrdgtohhmpdhivghtfhdroh hrghenucfkphepfeekrdelkedrfeejrddufeegnecurfgrrhgrmhepmhgrihhlfhhrohhm pegrlhhishhsrgestghoohhpvghrfidrihhnnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:zg-OXa4CLRjtaF610Qbm7m_jGry8TkTqFSiH-FtS9YRksl_U6MzXDA> <xmx:zg-OXRx-z5DW6NJb8vXr28jilrIi2r-7Ml08gpwKIoNJN4DvB_2xZw> <xmx:zg-OXShOS0lJLQTmjDnI-UJ3P8TC7KEJ9-cDxnVXdHH2gLyoa9qSwQ> <xmx:zg-OXSRP6Fn1AL75VJBpA2AJ-sQVql5m04QHRgoWd48qf5X-zwm9Kw>
Received: from [172.19.249.225] (unknown [38.98.37.134]) by mail.messagingengine.com (Postfix) with ESMTPA id 190E880064; Fri, 27 Sep 2019 09:34:02 -0400 (EDT)
From: Alissa Cooper <alissa@cooperw.in>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Fri, 27 Sep 2019 14:33:55 +0100
References: <156763077985.22753.8206505094680303304.idtracker@ietfa.amsl.com>
To: architecture-discuss@ietf.org, The IAB <iab@iab.org>
In-Reply-To: <156763077985.22753.8206505094680303304.idtracker@ietfa.amsl.com>
Message-Id: <A212688E-FDE7-43EF-9244-BBE8B27AA2D4@cooperw.in>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/YXPHUHd5eaG9vpgGiXqoVdtkEok>
Subject: Re: [arch-d] Call for Comment: <draft-ietf-iasa2-rfc6635bis-03> (RFC Editor Model (Version 2))
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: Fri, 27 Sep 2019 13:34:11 -0000

Hi,

I have some comments on this document.


Section 1:

s/The IAB maintains it's/The IAB maintains its/

s/Internet Administrative Oversight Committee (IAOC)/IETF Administrative =
Oversight Committee (IAOC)/


Section 2.1:

"The RSE is expected to cooperate closely with the LLC Board and the
   stream managers."

Given that the LLC Board is an oversight body operating at a strategic =
level, I think this would make more sense if it said "LLC" (which =
includes LLC staff and contractors, including tools people) rather than =
"LLC Board."


Section 2.1.7:

The LLC is in the process of adopting a conflict of interest policy that =
will apply to all staff, contractors, and board directors =
<https://github.com/ietf-llc/policies-consultation/blob/master/Conflict-of=
-Interest-00.md>. Since the RSE will be bound by that policy, I think =
Section 2.1.7 should be removed to avoid confusion about which policy =
applies.


Section 3.1:

"For all decisions that affect the RSE individually (e.g., hiring and
 firing), the RSOC prepares recommendations for the IAB, but the final
 decision is the responsibility of the IAB."

Since the LLC is the contract holder, it needs to have final decisional =
authority about hiring and firing, e.g. if it is unable to negotiate =
suitable contract terms with a candidate. I would suggest the following =
edit:

"For all decisions that affect the RSE individually (e.g., hiring and =
firing), the RSOC prepares recommendations for the IAB, but approval of =
these recommendations is the responsibility of the IAB."


Section 4.2:

"The RFC Series portion of the LLC budget shall include entries for
   the RSOC, RSE, RFC Production Center, and the RFC Publisher.  The LLC
   budget shall also include entries for the streams, including the
   independent stream."

Since RFC 6635 was published I can't recall seeing a budget that had a =
line item for RSOC or for "the streams," so this text has seemingly not =
matched actual practice for some time. More generally, allowing the LLC =
some flexibility about how the line items appear seems warranted given =
that the LLC has this flexibility for the rest of the budget. I would =
suggest the following edit:

"The LLC budget shall include funding to support the RSOC, RSE, RFC =
Production Center, the RFC Publisher, and the Independent Submissions =
Editor."


Section 4.4:

   "If a disagreement or decision has immediate or future contractual
   consequences, it falls under [I-D.ietf-iasa2-rfc4071bis]; thus, the
   RSE must identify the issue and provide his or her advice to the LLC;
   additionally, if the RSOC has provided advice, forward that advice as
   well."

This sentence is not grammatically correct. I'm not sure what to suggest =
as it seems to be stating something obvious, but perhaps I'm not able to =
understand the point being made.


Thanks,
Alissa

=20


> On Sep 4, 2019, at 9:59 PM, IAB Executive Administrative Manager =
<execd@iab.org> wrote:
>=20
> This is an announcement of an IETF-wide Call for Comment on=20
> draft-ietf-iasa2-rfc6635bis-03.
>=20
> The document is being considered for publication as an Informational =
RFC=20
> within the IAB stream, and is available for inspection at:
> <https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc6635bis/>
>=20
> The Call for Comment will last until 2019-10-02. Please send comments =
to
> architecture-discuss@ietf.org and iab@iab.org.
>=20
> Abstract
>=20
>   The RFC Editor model described in this document divides the
>   responsibilities for the RFC Series into three functions: the RFC
>   Series Editor, the RFC Production Center, and the RFC Publisher.
>   Internet Architecture Board (IAB) oversight via the RFC Series
>   Oversight Committee (RSOC) is described, as is the relationship
>   between the IETF Administration Limited Liability Company and the
>   RSOC.  This document reflects the experience gained with "RFC Editor
>   Model (Version 1)", documented in RFC 5620; and obsoletes RFC 6635 =
to
>   replace all references to the IASA and related structures with those
>   defined by the IASA 2.0 Model.
>=20
>   [RFC Editor: Please remove the following paragraph prior to
>   publication.]
>=20
>   The IASA2 WG requests that the IAB publish this replacement for RFC
>   6635.
>=20
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce


From nobody Fri Sep 27 13:16:15 2019
Return-Path: <brian.e.carpenter@gmail.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 02418120A7B for <architecture-discuss@ietfa.amsl.com>; Fri, 27 Sep 2019 13:16:07 -0700 (PDT)
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_HELO_NONE=0.001, 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 2ByhsAf0VOfD for <architecture-discuss@ietfa.amsl.com>; Fri, 27 Sep 2019 13:16:05 -0700 (PDT)
Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) (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 119B312013D for <architecture-discuss@ietf.org>; Fri, 27 Sep 2019 13:16:05 -0700 (PDT)
Received: by mail-pf1-x434.google.com with SMTP id 205so2187337pfw.2 for <architecture-discuss@ietf.org>; Fri, 27 Sep 2019 13:16:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=fx1fHHtXTVfswIMzDeCvNhX5GvM5jRFbeilFpoau20w=; b=C4mFxaCcRrbeoPwcZvKr7q/bXU2oHAm06BKNzsCgQ2TdqsfqfwS4LxZO6rL03wuzuT erobvFVcg3E2VhAQ5Be7NgI5v0rNOZJZRDPWxZ7rdwS9ArnK20Ey4AJ20tTBdgQtJb/q grYeX4jFzZsYuiwIXfOAlJEe6iSuPxhdGfRi+nA0T2+yTtBcA4iLAib2TYmhFv27yGvd BtlWYELBz7XEApMKCST51jODzFJIN90AX1iILQtHYIkL9/BjYmfngfwxzVwVfcD2dKf6 NjzLEPBXPcrYdgJHnUgaaAkhnlpwSJgyhFwfqww02LKCbuQW9JomwT7Dp4AaV/E7WPvO zdIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=fx1fHHtXTVfswIMzDeCvNhX5GvM5jRFbeilFpoau20w=; b=gxY/7A+9oRxfNn/Kwo/jFzLCV/ZtCf2rdzHTmiLICR9uX0TAEmnZaIj6wEDeE4DCRU LjKg3ZGhajeQjVxkbxppBRAS0c7HmOW3L/zT+X44UPQT0MDpBs+xhQ4ldLEhn//XAqPE bLoTPcX2qagmgT8BqiLqud+QEAab2RDXm6K0V/JqQksMV708tQcdn8HHLMgP8TBs/+kq j+PXTHvDfrqV0IjfKiuxpSCEdugopFkXOpK6m+ZEwtOdd3vZhq9i0trzvPB1bIw9Q8cK tCyxrllll9EkpfuPKjOePjP0qhaYMpu/pUUJ2nU6bsYvCotb3orarl5GH4PV+ypkwd7p J1yg==
X-Gm-Message-State: APjAAAWh+IPZUeC8d6Yv55NWnjJmxOY9jjYwO0eQu1OBlK+q8HB5gS/2 qpHcKGAJ3hFYk7Xt1XU9ikscZnL5
X-Google-Smtp-Source: APXvYqx6ZXyT3TiwDHzwMJFor8lxgZbVgjR5y/MhnlPaIi5GSR1zAPRzGGy5E7Kasr6qiMG9UInq6w==
X-Received: by 2002:a17:90a:b001:: with SMTP id x1mr12292533pjq.114.1569615364446;  Fri, 27 Sep 2019 13:16:04 -0700 (PDT)
Received: from [192.168.178.30] (82.206.69.111.dynamic.snap.net.nz. [111.69.206.82]) by smtp.gmail.com with ESMTPSA id d76sm7169690pga.80.2019.09.27.13.16.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Sep 2019 13:16:03 -0700 (PDT)
To: Alissa Cooper <alissa@cooperw.in>, architecture-discuss@ietf.org, The IAB <iab@iab.org>
References: <156763077985.22753.8206505094680303304.idtracker@ietfa.amsl.com> <A212688E-FDE7-43EF-9244-BBE8B27AA2D4@cooperw.in>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <d43cb2f8-9a24-aaae-5aef-dc941f99c381@gmail.com>
Date: Sat, 28 Sep 2019 08:16:00 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <A212688E-FDE7-43EF-9244-BBE8B27AA2D4@cooperw.in>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/o-jrQ9KBadyyYrqncM2czIN-H9A>
Subject: Re: [arch-d] Call for Comment: <draft-ietf-iasa2-rfc6635bis-03> (RFC Editor Model (Version 2))
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: Fri, 27 Sep 2019 20:16:14 -0000

Hi Alissa,

One general comment is that I suppose that this is really "RFC Editor Model (Version 2.1)" since it's a small variant on Version 2, and I imagine we'll be having a Version 3 in not very long, with more fundamental changes. In any case I think the title really should be slightly updated.

On 28-Sep-19 01:33, Alissa Cooper wrote:
...
> Section 2.1.7:
> 
> The LLC is in the process of adopting a conflict of interest policy that will apply to all staff, contractors, and board directors <https://github.com/ietf-llc/policies-consultation/blob/master/Conflict-of-Interest-00.md>. Since the RSE will be bound by that policy, I think Section 2.1.7 should be removed to avoid confusion about which policy applies.

I think that completely removing the section would be a mistake, since it makes a fairly important statement about the RSE's neutrality (something I think we will be boosting when it comes time for Version 3, so this section is also a placeholder). But of course you are correct that we don't want any inconsistency with the LLC policy. Could I suggest that the section is reduced to:

2.1.7.  Conflict of Interest

   The RSE is expected to avoid even the appearance of conflict of
   interest or judgment in performing these roles.  To ensure this,
   the RSE will be subject to a conflict of interest policy
   established by the LLC.

Regards
    Brian


From nobody Fri Sep 27 16:46:00 2019
Return-Path: <bob.hinden@gmail.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 87EE812004E for <architecture-discuss@ietfa.amsl.com>; Fri, 27 Sep 2019 16:45:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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_HELO_NONE=0.001, 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 wcUHvOrQCqv5 for <architecture-discuss@ietfa.amsl.com>; Fri, 27 Sep 2019 16:45:56 -0700 (PDT)
Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (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 8B8DC120071 for <architecture-discuss@ietf.org>; Fri, 27 Sep 2019 16:45:56 -0700 (PDT)
Received: by mail-wm1-x32b.google.com with SMTP id p7so7608036wmp.4 for <architecture-discuss@ietf.org>; Fri, 27 Sep 2019 16:45:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=yTXpGlEcKTerFz0VuUbwO1SD4jQzRknLYfTGKbtwL7A=; b=B0VET+uTJMT8pEmNUO1HqSWmLXCU+xP5eD8hw8o8tuLtOZYLuLme5OFqTs2vMNAV3G NgpeKk+xrADuBSgUyeSBdQXn9gsUsZ1gtWCCw+75z4gVVaqGmahjNN0wC0oF4bLX2ATu P8nvUKBgtp72gBIZJnpDw5aRMR6QKPEvwr3bpzo8CsWKvhUGwbB/IfLbmY8vm2VpML69 1I5soZpAYOtAhJwKwj/LtTINoXK/l0Tdbv+JYEeIEthRP06/JCk61YEPIv0rXzmyu6I7 LN+Ymd7QmQEUFG5bpOEiTUIUegGSP2BRbAYntJlJahEUJBeEk8Ty0g56zz66YQSigHSm xi9Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=yTXpGlEcKTerFz0VuUbwO1SD4jQzRknLYfTGKbtwL7A=; b=IKDgbL3OzuZK/m7aoOV2AZBRdo33Z3vupxE4Fj1He63qUsZwpzluiBSE48QaOiCJDI OmS9RnoIXI644zEWgYNnbeUdueCjGdeDc4KT1zeAqY6xw/RR8xL3Z4RCZcQh808Iu/8k oHYfcHecsf/yjDdyKdg6MZcdus53fCB5dvYrfENMff0yBeb8FdiCHKQHti9yXCj03QlP 4qHlypOPNnHNuAhqyAkL26/hj7zrLJFtT4NPg+RjAKRoaC/b6Bg8kKqf/1588pw8gmtS OMIDb0D1kMjiHBdHOZtv1+lEZw+WGlBB16JG61ZtLvLD4NJj0dKJGoqq2G+jVpfqZHyn YQoA==
X-Gm-Message-State: APjAAAXGI4v37JaNex4JfFelJ7e4X4RAC1bESHBQBy5f/5S5GgSr7Zok v1Qk0y/u3YCEgN2mFebA3GI=
X-Google-Smtp-Source: APXvYqwKcp6dyRWYAzJz9eOLq7sWS2EAxo4Bh7I4GTBpf3UCVmSf8wXSsmIZ7Lw3ZLB1BUdRYQh3SQ==
X-Received: by 2002:a1c:4b10:: with SMTP id y16mr8661354wma.54.1569627954983;  Fri, 27 Sep 2019 16:45:54 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:ef0b:c13b:9b80:9c0b:6d08? ([2601:647:5a00:ef0b:c13b:9b80:9c0b:6d08]) by smtp.gmail.com with ESMTPSA id k9sm7595316wrd.7.2019.09.27.16.45.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Sep 2019 16:45:54 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <52117344-9D35-4F1C-8DF9-EC0DCE0A5337@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_B2FC26D7-B7BE-4FA9-8613-9969E1E39396"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Fri, 27 Sep 2019 16:45:49 -0700
In-Reply-To: <A212688E-FDE7-43EF-9244-BBE8B27AA2D4@cooperw.in>
Cc: Bob Hinden <bob.hinden@gmail.com>, architecture-discuss@ietf.org, The IAB <iab@iab.org>
To: Alissa Cooper <alissa@cooperw.in>
References: <156763077985.22753.8206505094680303304.idtracker@ietfa.amsl.com> <A212688E-FDE7-43EF-9244-BBE8B27AA2D4@cooperw.in>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/Zuq5O2kRsgd2bdOHzGCSW50sEzs>
Subject: Re: [arch-d] Call for Comment: <draft-ietf-iasa2-rfc6635bis-03> (RFC Editor Model (Version 2))
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: Fri, 27 Sep 2019 23:45:59 -0000

--Apple-Mail=_B2FC26D7-B7BE-4FA9-8613-9969E1E39396
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Alissa,

> On Sep 27, 2019, at 6:33 AM, Alissa Cooper <alissa@cooperw.in> wrote:
>=20
> Hi,
>=20
> I have some comments on this document.

Thanks for reviewing the document.

>=20
>=20
> Section 1:
>=20
> s/The IAB maintains it's/The IAB maintains its/
>=20
> s/Internet Administrative Oversight Committee (IAOC)/IETF =
Administrative Oversight Committee (IAOC)/

Good

>=20
>=20
> Section 2.1:
>=20
> "The RSE is expected to cooperate closely with the LLC Board and the
>   stream managers."
>=20
> Given that the LLC Board is an oversight body operating at a strategic =
level, I think this would make more sense if it said "LLC" (which =
includes LLC staff and contractors, including tools people) rather than =
"LLC Board.=E2=80=9D
>=20

That is fixed in -03.


> Section 2.1.7:
>=20
> The LLC is in the process of adopting a conflict of interest policy =
that will apply to all staff, contractors, and board directors =
<https://github.com/ietf-llc/policies-consultation/blob/master/Conflict-of=
-Interest-00.md>. Since the RSE will be bound by that policy, I think =
Section 2.1.7 should be removed to avoid confusion about which policy =
applies.
>=20

As Brian Carpenter said, I think it would be a mistake to not say =
anything.  His proposed text seems reasonable to me, it is:

  The RSE is expected to avoid even the appearance of conflict of
  interest or judgment in performing these roles.  To ensure this,
  the RSE will be subject to a conflict of interest policy
  established by the LLC.


>=20
> Section 3.1:
>=20
> "For all decisions that affect the RSE individually (e.g., hiring and
> firing), the RSOC prepares recommendations for the IAB, but the final
> decision is the responsibility of the IAB."
>=20
> Since the LLC is the contract holder, it needs to have final =
decisional authority about hiring and firing, e.g. if it is unable to =
negotiate suitable contract terms with a candidate. I would suggest the =
following edit:
>=20
> "For all decisions that affect the RSE individually (e.g., hiring and =
firing), the RSOC prepares recommendations for the IAB, but approval of =
these recommendations is the responsibility of the IAB.=E2=80=9D

I think that is an improvement on the text.


> Section 4.2:
>=20
> "The RFC Series portion of the LLC budget shall include entries for
>   the RSOC, RSE, RFC Production Center, and the RFC Publisher.  The =
LLC
>   budget shall also include entries for the streams, including the
>   independent stream."
>=20
> Since RFC 6635 was published I can't recall seeing a budget that had a =
line item for RSOC or for "the streams," so this text has seemingly not =
matched actual practice for some time. More generally, allowing the LLC =
some flexibility about how the line items appear seems warranted given =
that the LLC has this flexibility for the rest of the budget. I would =
suggest the following edit:
>=20
> "The LLC budget shall include funding to support the RSOC, RSE, RFC =
Production Center, the RFC Publisher, and the Independent Submissions =
Editor.=E2=80=9D

I don=E2=80=99t read this as requiring line items in a published budget, =
for example, like the one at:

=
https://www.ietf.org/media/documents/IETF_2019_Budget_Public_2018-12-19.pd=
f

I think it was saying the LLC should be budgeting and tracking these =
activities, how it reports this to the community is a different matter.  =
That said, I think your text is clearer, but I think it=E2=80=99s a =
mistake to call out the RSOC here, as that is clearly part of the IAB.  =
So I suggest:

OLD:

   The RFC Series portion of the LLC budget shall include entries for
   the RSOC, RSE, RFC Production Center, and the RFC Publisher.  The LLC
   budget shall also include entries for the streams, including the
   independent stream.

NEW:

   The RFC Series portion of the LLC budget shall include funding to =
support
   the RSE, RFC Production Center, RFC Publisher, and the Independent =
Stream.


>=20
>=20
> Section 4.4:
>=20
>   "If a disagreement or decision has immediate or future contractual
>   consequences, it falls under [I-D.ietf-iasa2-rfc4071bis]; thus, the
>   RSE must identify the issue and provide his or her advice to the =
LLC;
>   additionally, if the RSOC has provided advice, forward that advice =
as
>   well."
>=20
> This sentence is not grammatically correct. I'm not sure what to =
suggest as it seems to be stating something obvious, but perhaps I'm not =
able to understand the point being made.

That is quite a sentence, too many editors here :-)

How about:

   If a disagreement or decision has immediate or future contractual
   consequences, it falls under [I-D.ietf-iasa2-rfc4071bis].  If this =
happens
   the RSE must identify the issue and provide advice to the LLC.
   Additionally, if the RSOC has also developed advice, it should =
forward that
   advice to the LLC.

   The LLC must notify the RSOC and IAB regarding the action it
   concludes is required to resolve the issue based on its applicable
   procedures and provisions in the relevant contracts.

Thanks,
Bob


>=20
>=20
> Thanks,
> Alissa
>=20
>=20
>=20
>=20
>> On Sep 4, 2019, at 9:59 PM, IAB Executive Administrative Manager =
<execd@iab.org> wrote:
>>=20
>> This is an announcement of an IETF-wide Call for Comment on
>> draft-ietf-iasa2-rfc6635bis-03.
>>=20
>> The document is being considered for publication as an Informational =
RFC
>> within the IAB stream, and is available for inspection at:
>> <https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc6635bis/>
>>=20
>> The Call for Comment will last until 2019-10-02. Please send comments =
to
>> architecture-discuss@ietf.org and iab@iab.org.
>>=20
>> Abstract
>>=20
>>  The RFC Editor model described in this document divides the
>>  responsibilities for the RFC Series into three functions: the RFC
>>  Series Editor, the RFC Production Center, and the RFC Publisher.
>>  Internet Architecture Board (IAB) oversight via the RFC Series
>>  Oversight Committee (RSOC) is described, as is the relationship
>>  between the IETF Administration Limited Liability Company and the
>>  RSOC.  This document reflects the experience gained with "RFC Editor
>>  Model (Version 1)", documented in RFC 5620; and obsoletes RFC 6635 =
to
>>  replace all references to the IASA and related structures with those
>>  defined by the IASA 2.0 Model.
>>=20
>>  [RFC Editor: Please remove the following paragraph prior to
>>  publication.]
>>=20
>>  The IASA2 WG requests that the IAB publish this replacement for RFC
>>  6635.
>>=20
>> _______________________________________________
>> IETF-Announce mailing list
>> IETF-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-announce
>=20
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss


--Apple-Mail=_B2FC26D7-B7BE-4FA9-8613-9969E1E39396
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEm0rfRsOCoyamPexGrut0EXfnu6gFAl2Ony0ACgkQrut0EXfn
u6ielwf8DQp2EsMyKaFT6vwDU0W6N8Z4TZCjFa0dMN8FEaq8aZHb88sMrpP30qmj
5Y6iCwK+566qVKnJ83PyBD8G38Ls1fhixnnG2JgOVb0I6ANscaLUCClPKeUanAt6
0KSrjP7NPtYGRt2H2rkBklSKSZKAemOdBNtIThwPT/K19TdITZkMpSb30bbR5h91
Glcm2+bJpTLPMgRRlysORvBzUVtnDsYnCZJvlioBDxj48w4zcS6Eo+QoN6+d9TXN
o5f3N3GsH174ado/zrOcIsUw5MfSsgeJ8z/3Gt4L/bkg31J0l45GIGGdXGL9xRKc
ZM5USM58BRDUDfO+xS/yikki8fi67w==
=ljyf
-----END PGP SIGNATURE-----

--Apple-Mail=_B2FC26D7-B7BE-4FA9-8613-9969E1E39396--


From nobody Fri Sep 27 17:01:26 2019
Return-Path: <bob.hinden@gmail.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 423B4120058 for <architecture-discuss@ietfa.amsl.com>; Fri, 27 Sep 2019 17:01:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.025
X-Spam-Level: 
X-Spam-Status: No, score=-0.025 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DEAR_SOMETHING=1.973, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 dif0EoFh2Rv3 for <architecture-discuss@ietfa.amsl.com>; Fri, 27 Sep 2019 17:01:23 -0700 (PDT)
Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (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 5E583120026 for <architecture-discuss@ietf.org>; Fri, 27 Sep 2019 17:01:23 -0700 (PDT)
Received: by mail-wr1-x432.google.com with SMTP id a11so4963950wrx.1 for <architecture-discuss@ietf.org>; Fri, 27 Sep 2019 17:01:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=L48ebC/91654iifziLsn0OZw1QWJfdrOaxfYQUu4o7U=; b=UR7aCGO/LwQL0lISQM2w7wTxbnjBJTRWADnS3rIDaAruKRsI6M5l7CP6FapNbPmpkd knyEU5tQjJPvS7SHyQBl7Z0yFA+UjyEM3fZ5OzpNL9lP09W/zfWBKUt6KzMEe22sxDVU G+iC+l97bwbfTtAFF38xgU8ZoAPdpWfA1dc3KKiRivQs3xrIJCee1y6LO/LYBf1FmB5N 1Xx7H9Tv1AhPzYiyrtHpzAjSuQulkFoTEezqmR+cbsqoMVyp+je9NFI9bT0np4OHCsXg kd/S23dIhlKshj3Hr0nQFyV9uJDoIvJP2Cl4w036WRoPdk6NM2UJAdBwehpWvspJw6e/ S55A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=L48ebC/91654iifziLsn0OZw1QWJfdrOaxfYQUu4o7U=; b=JP8yc59u/h+Ft/apqtqw1u7wJN8to7sP6m/JeO23u7wtdmrYB0N/haBraX1U/c/WHr +mB1TsjYdHIBDQEuQDU1EUJIlRq3CQJyy9LBTOXUhkzLljXrbDumI4y2V4Me5mx1uMei tcq01nYf/ls6lEXMrTux+/6eAe/cB8c62py+lG6jQaS50TxU71GIhoIL8hcSuERmQURg rybihZB50wHwctvyzXdfOIIRkyOo/OZk/iohj1G59MFh15xUDMq1A5iGd2eqbY70m8DO slnVGqWKFgvgeDop5l3NkJhvEg7zPuDSNAwb6UXUADhT0FFl5xdEY9I7Yn3s0dCxIWML LwxA==
X-Gm-Message-State: APjAAAXYhW0k/ZLDxBV2856N1UpXMWqbxKFugQQ1vhAqjVqIMEYIBzmP AGgzBTL0GwkeQWzq5607DTZKjF++
X-Google-Smtp-Source: APXvYqxuC9KFJXrM2RemiNlAfMq6zWDbh5e7qHPRB89PuJs61lcKxx0EHaR4EDwRYplQHzZ+/HJWJQ==
X-Received: by 2002:adf:f404:: with SMTP id g4mr4623292wro.353.1569628881913;  Fri, 27 Sep 2019 17:01:21 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:ef0b:c13b:9b80:9c0b:6d08? ([2601:647:5a00:ef0b:c13b:9b80:9c0b:6d08]) by smtp.gmail.com with ESMTPSA id n18sm5238816wmi.20.2019.09.27.17.01.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Sep 2019 17:01:21 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <F7DA2F14-1A40-4397-A6AB-51B7E5284CF8@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_C4D15426-7F0D-4E56-B31B-7C58A781E4E7"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Fri, 27 Sep 2019 17:01:17 -0700
In-Reply-To: <6.2.5.6.2.20190910225210.0b9b30a0@elandnews.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, architecture-discuss@ietf.org, iab@iab.org
To: S Moonesamy <sm+ietf@elandsys.com>
References: <156763077985.22753.8206505094680303304.idtracker@ietfa.amsl.com> <6.2.5.6.2.20190910225210.0b9b30a0@elandnews.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/jw4XxyCqMg0q3a-aAhqgmAL2m2o>
Subject: Re: [arch-d] Call for Comment: <draft-ietf-iasa2-rfc6635bis-03> (RFC Editor Model (Version 2))
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: Sat, 28 Sep 2019 00:01:25 -0000

--Apple-Mail=_C4D15426-7F0D-4E56-B31B-7C58A781E4E7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

I am the document editor for this version of the document.

> On Sep 10, 2019, at 11:22 PM, S Moonesamy <sm+ietf@elandsys.com> =
wrote:
>=20
> Dear Internet Architecture Board,
> At 01:59 PM 04-09-2019, IAB Executive Administrative Manager wrote:
>> This is an announcement of an IETF-wide Call for Comment on
>> draft-ietf-iasa2-rfc6635bis-03.
>>=20
>> The document is being considered for publication as an Informational =
RFC
>> within the IAB stream, and is available for inspection at:
>> <https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc6635bis/>
>>=20
>> The Call for Comment will last until 2019-10-02. Please send comments =
to
>> architecture-discuss@ietf.org and iab@iab.org.
>=20
> The is a misspelled word in last sentence at the bottom of Page 3 of =
the draft.

I will fix in the next version.

>=20
> There has been a significant discussion of the RFC Editor Model since =
July.  Section 2.1.5 of draft-ietf-iasa2-rfc6635bis-03 was not adhered =
to since several years.  The qualification described in Section 2.1.6 =
does not reflect what would be sought in a person to fulfill the role of =
RFC Series Editor.  The description of the oversight role of the RFC =
Series Oversight Committee, described in Section 3.1, is not aligned =
with what could be envisioned for the RFC Series.
>=20
> Given the above, it is not judicious to publish =
draft-ietf-iasa2-rfc6635bis-03 as a RFC without an adequate review of =
the draft.
>=20

The direction on this draft was to only change parts of the document =
that related to the change from the IAOC to LLC.

The larger issues with the RFC Editor need to be resolved, but I don=E2=80=
=99t think the LLC related changes should be delayed until that is =
complete.   It=E2=80=99s going to take a while in my view.

Thanks,
Bob





> Regards,
> S. Moonesamy
>=20
>=20
>=20
>=20
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss


--Apple-Mail=_C4D15426-7F0D-4E56-B31B-7C58A781E4E7
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEm0rfRsOCoyamPexGrut0EXfnu6gFAl2Oos0ACgkQrut0EXfn
u6hMSwf9FaZZpVwVviUQjMLucTN5tyd5FX+4h/22D0CWYv0WQwL8Qc+Yesb4+uxc
guvY7MA3XLdcG7EKrC+TLtjHwdOy02yArZg14bt9YQNvKU+uHRG63T69zetKJZSO
+TrxBNoDh83D8JyMO1TcZ0MZ/Fa+S+V5UdTLLu0K88VmCxFfUFzWIP2xsslTe79B
ACP6szhfn5yG0URUyA19LHCw7cJ7sIUXh9vnrMIIuKwZHi8SRG5c75g4lcXPobfL
GWCkKMMoOATOAdsAW975Dl25bCpcCQ8mQRymro6sHr9TI99MquI+l1CiOmoFhkD8
qEIWR/whpLF69TU2qS/n3VGzyuhOnA==
=Uv59
-----END PGP SIGNATURE-----

--Apple-Mail=_C4D15426-7F0D-4E56-B31B-7C58A781E4E7--


From nobody Mon Sep 30 06:01:25 2019
Return-Path: <alissa@cooperw.in>
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 2DA7C120236 for <architecture-discuss@ietfa.amsl.com>; Mon, 30 Sep 2019 06:01:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=ik9W7c3u; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=A5iV/jQN
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 dQTbkXuF2hpv for <architecture-discuss@ietfa.amsl.com>; Mon, 30 Sep 2019 06:01:21 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53F09120289 for <architecture-discuss@ietf.org>; Mon, 30 Sep 2019 06:01:21 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 82FF3206FC; Mon, 30 Sep 2019 09:01:20 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Mon, 30 Sep 2019 09:01:20 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=I Alq/vXyWIE6Q6Jw+6o+NZ3kZQklNsOjCae2kNjsXSY=; b=ik9W7c3up/751Spwf fwHmyHtmykgROoJEl5TwTwLXdcPyztfJLueJnlZNnFfzm9IQ1yyV7fgSfHrBSgWG fZQ1Y5gPD9Bt7M/wn9YT1irVwpDSCzsKn/qJcl8RNmcghuxLTZ78M24ebiJFTe+H YCm8C8SWSzXsGdxFR/eP870wHILT+GcQrSUEBPXRzsZDdH1rHah0/hPR9Y3LRMGY Lco9cBxMIRBKr8zkLiuvlvufJ6HKz08K+ltXMBLK+gks21PHl+plgpi0yshUrzK7 /fl+XgSvb6TD+oy1OKJ+nlYr0Za+KICkd4op/VlX1nAq0732XZ1fUyn6ZTERgVDp oaBMg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=IAlq/vXyWIE6Q6Jw+6o+NZ3kZQklNsOjCae2kNjsX SY=; b=A5iV/jQNUyT97qdnN8EKxqMhldFHrKnPfX2rYJOHnt44PiZ6V8Wtv6R++ PAuM1vZ0SddsZ8ELRVbW4YNPdJSkesA/sDHvvf2cx8OhIbp8E7BUl2cy6sht66nB aQ18j0YchNhQXwA/wCBbjYwVko+cY7PgpUrtC8gdJJL/5FScNum1FM0rHunMW5WU KWzZ6afaSEieduZEXtkZcje4OABy2N5bNfkLkENikyw51LY54wLnlUXTlgN0dOWN /A1i+3lIJPa/PXRoxGmoRBo9+M/Z34Xg1iKrDx/c+KaLm6EmjE6OVMD7+fiwEw/+ T24WRJxFgI5NULtWT79NLTCwNDZqw==
X-ME-Sender: <xms:n_yRXfmZamYJ9R0dq3UKhjq9xW5p2n6OSfNX5_VhqNn4bstEBqGPJg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrgedvgdehhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeetlhhishhs rgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecuffhomhgrih hnpehgihhthhhusgdrtghomhdpihgvthhfrdhorhhgnecukfhppedujeefrdefkedruddu jedrkedunecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhishhsrgestghoohhpvghrfi drihhnnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:n_yRXerMllUfGjU-4vGH59rD9pdKZABh4T5HM7_0_O_j9WZCgPaB6A> <xmx:n_yRXbK5jaDAOX4uYZ7YsEoTpFflt0eNAV2NHwQjFCqaLXlk6GsjNA> <xmx:n_yRXaAYQrO33OumyaXl-4FvXVsqjLhsaWXeggW6H7m5Um7ZSd7qkw> <xmx:oPyRXTLFrAlBhGx3Lv1pkzRwVR-UPEvIeMzesLUzohd9sKJYutKSjw>
Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.81]) by mail.messagingengine.com (Postfix) with ESMTPA id 3ED3A80063; Mon, 30 Sep 2019 09:01:19 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <52117344-9D35-4F1C-8DF9-EC0DCE0A5337@gmail.com>
Date: Mon, 30 Sep 2019 09:01:17 -0400
Cc: architecture-discuss@ietf.org, The IAB <iab@iab.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <189750DA-3C62-4198-9A31-1AF2589C4A83@cooperw.in>
References: <156763077985.22753.8206505094680303304.idtracker@ietfa.amsl.com> <A212688E-FDE7-43EF-9244-BBE8B27AA2D4@cooperw.in> <52117344-9D35-4F1C-8DF9-EC0DCE0A5337@gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/SExTDAVvLKflg9WzzZdxnrJhzaE>
Subject: Re: [arch-d] Call for Comment: <draft-ietf-iasa2-rfc6635bis-03> (RFC Editor Model (Version 2))
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: Mon, 30 Sep 2019 13:01:24 -0000

Hi Bob,

All sounds good to me.

Thanks,
Alissa


> On Sep 27, 2019, at 7:45 PM, Bob Hinden <bob.hinden@gmail.com> wrote:
>=20
> Alissa,
>=20
>> On Sep 27, 2019, at 6:33 AM, Alissa Cooper <alissa@cooperw.in> wrote:
>>=20
>> Hi,
>>=20
>> I have some comments on this document.
>=20
> Thanks for reviewing the document.
>=20
>>=20
>>=20
>> Section 1:
>>=20
>> s/The IAB maintains it's/The IAB maintains its/
>>=20
>> s/Internet Administrative Oversight Committee (IAOC)/IETF =
Administrative Oversight Committee (IAOC)/
>=20
> Good
>=20
>>=20
>>=20
>> Section 2.1:
>>=20
>> "The RSE is expected to cooperate closely with the LLC Board and the
>>  stream managers."
>>=20
>> Given that the LLC Board is an oversight body operating at a =
strategic level, I think this would make more sense if it said "LLC" =
(which includes LLC staff and contractors, including tools people) =
rather than "LLC Board.=E2=80=9D
>>=20
>=20
> That is fixed in -03.
>=20
>=20
>> Section 2.1.7:
>>=20
>> The LLC is in the process of adopting a conflict of interest policy =
that will apply to all staff, contractors, and board directors =
<https://github.com/ietf-llc/policies-consultation/blob/master/Conflict-of=
-Interest-00.md>. Since the RSE will be bound by that policy, I think =
Section 2.1.7 should be removed to avoid confusion about which policy =
applies.
>>=20
>=20
> As Brian Carpenter said, I think it would be a mistake to not say =
anything.  His proposed text seems reasonable to me, it is:
>=20
>  The RSE is expected to avoid even the appearance of conflict of
>  interest or judgment in performing these roles.  To ensure this,
>  the RSE will be subject to a conflict of interest policy
>  established by the LLC.
>=20
>=20
>>=20
>> Section 3.1:
>>=20
>> "For all decisions that affect the RSE individually (e.g., hiring and
>> firing), the RSOC prepares recommendations for the IAB, but the final
>> decision is the responsibility of the IAB."
>>=20
>> Since the LLC is the contract holder, it needs to have final =
decisional authority about hiring and firing, e.g. if it is unable to =
negotiate suitable contract terms with a candidate. I would suggest the =
following edit:
>>=20
>> "For all decisions that affect the RSE individually (e.g., hiring and =
firing), the RSOC prepares recommendations for the IAB, but approval of =
these recommendations is the responsibility of the IAB.=E2=80=9D
>=20
> I think that is an improvement on the text.
>=20
>=20
>> Section 4.2:
>>=20
>> "The RFC Series portion of the LLC budget shall include entries for
>>  the RSOC, RSE, RFC Production Center, and the RFC Publisher.  The =
LLC
>>  budget shall also include entries for the streams, including the
>>  independent stream."
>>=20
>> Since RFC 6635 was published I can't recall seeing a budget that had =
a line item for RSOC or for "the streams," so this text has seemingly =
not matched actual practice for some time. More generally, allowing the =
LLC some flexibility about how the line items appear seems warranted =
given that the LLC has this flexibility for the rest of the budget. I =
would suggest the following edit:
>>=20
>> "The LLC budget shall include funding to support the RSOC, RSE, RFC =
Production Center, the RFC Publisher, and the Independent Submissions =
Editor.=E2=80=9D
>=20
> I don=E2=80=99t read this as requiring line items in a published =
budget, for example, like the one at:
>=20
> =
https://www.ietf.org/media/documents/IETF_2019_Budget_Public_2018-12-19.pd=
f
>=20
> I think it was saying the LLC should be budgeting and tracking these =
activities, how it reports this to the community is a different matter.  =
That said, I think your text is clearer, but I think it=E2=80=99s a =
mistake to call out the RSOC here, as that is clearly part of the IAB.  =
So I suggest:
>=20
> OLD:
>=20
>   The RFC Series portion of the LLC budget shall include entries for
>   the RSOC, RSE, RFC Production Center, and the RFC Publisher.  The =
LLC
>   budget shall also include entries for the streams, including the
>   independent stream.
>=20
> NEW:
>=20
>   The RFC Series portion of the LLC budget shall include funding to =
support
>   the RSE, RFC Production Center, RFC Publisher, and the Independent =
Stream.
>=20
>=20
>>=20
>>=20
>> Section 4.4:
>>=20
>>  "If a disagreement or decision has immediate or future contractual
>>  consequences, it falls under [I-D.ietf-iasa2-rfc4071bis]; thus, the
>>  RSE must identify the issue and provide his or her advice to the =
LLC;
>>  additionally, if the RSOC has provided advice, forward that advice =
as
>>  well."
>>=20
>> This sentence is not grammatically correct. I'm not sure what to =
suggest as it seems to be stating something obvious, but perhaps I'm not =
able to understand the point being made.
>=20
> That is quite a sentence, too many editors here :-)
>=20
> How about:
>=20
>   If a disagreement or decision has immediate or future contractual
>   consequences, it falls under [I-D.ietf-iasa2-rfc4071bis].  If this =
happens
>   the RSE must identify the issue and provide advice to the LLC.
>   Additionally, if the RSOC has also developed advice, it should =
forward that
>   advice to the LLC.
>=20
>   The LLC must notify the RSOC and IAB regarding the action it
>   concludes is required to resolve the issue based on its applicable
>   procedures and provisions in the relevant contracts.
>=20
> Thanks,
> Bob
>=20
>=20
>>=20
>>=20
>> Thanks,
>> Alissa
>>=20
>>=20
>>=20
>>=20
>>> On Sep 4, 2019, at 9:59 PM, IAB Executive Administrative Manager =
<execd@iab.org> wrote:
>>>=20
>>> This is an announcement of an IETF-wide Call for Comment on
>>> draft-ietf-iasa2-rfc6635bis-03.
>>>=20
>>> The document is being considered for publication as an Informational =
RFC
>>> within the IAB stream, and is available for inspection at:
>>> <https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc6635bis/>
>>>=20
>>> The Call for Comment will last until 2019-10-02. Please send =
comments to
>>> architecture-discuss@ietf.org and iab@iab.org.
>>>=20
>>> Abstract
>>>=20
>>> The RFC Editor model described in this document divides the
>>> responsibilities for the RFC Series into three functions: the RFC
>>> Series Editor, the RFC Production Center, and the RFC Publisher.
>>> Internet Architecture Board (IAB) oversight via the RFC Series
>>> Oversight Committee (RSOC) is described, as is the relationship
>>> between the IETF Administration Limited Liability Company and the
>>> RSOC.  This document reflects the experience gained with "RFC Editor
>>> Model (Version 1)", documented in RFC 5620; and obsoletes RFC 6635 =
to
>>> replace all references to the IASA and related structures with those
>>> defined by the IASA 2.0 Model.
>>>=20
>>> [RFC Editor: Please remove the following paragraph prior to
>>> publication.]
>>>=20
>>> The IASA2 WG requests that the IAB publish this replacement for RFC
>>> 6635.
>>>=20
>>> _______________________________________________
>>> IETF-Announce mailing list
>>> IETF-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>=20
>> _______________________________________________
>> Architecture-discuss mailing list
>> Architecture-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/architecture-discuss
>=20


From nobody Mon Sep 30 08:35:52 2019
Return-Path: <bob.hinden@gmail.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 4A5851200EC for <architecture-discuss@ietfa.amsl.com>; Mon, 30 Sep 2019 08:35:50 -0700 (PDT)
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_HELO_NONE=0.001, 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 aXB168x_8G9a for <architecture-discuss@ietfa.amsl.com>; Mon, 30 Sep 2019 08:35:47 -0700 (PDT)
Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) (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 2127912081B for <architecture-discuss@ietf.org>; Mon, 30 Sep 2019 08:35:47 -0700 (PDT)
Received: by mail-wr1-x434.google.com with SMTP id r5so11841478wrm.12 for <architecture-discuss@ietf.org>; Mon, 30 Sep 2019 08:35:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=ujyA2DWDaHtVTdVISbAO8GVIKP2ZTrDDEkKtmZ0qQ38=; b=pZZYj+zFtZGDwU/PSveQ7s9YacmS5LrmyiVcCK2k0hqhK9LKGje2yMdhzQ9rEeInlg hR5DthMfaRAfqJwKZCUr2a4t2gpmaIebHRRRI5wXtFriZ8KZFzTo/MDXOwJgs4xw5hwj KkStTogw2jA6b0NePwEH4nbAsoDc0YdaV95bWosC61zv3YLsQp556/Jf6bDYtcnDUD1c bQ/VtMvwjTIP6yh6PnSJl2PqXvcoEZdR89WoDmvqm/vzYP4mWTP6ecGHVLJuTHRfmnbt k5ybsIBHB9aD4NGrp7bcS9xng9om76KQ0pSeId+u56UpgQ6UoqlZb5ksGbndkyOrCF/e KRQA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=ujyA2DWDaHtVTdVISbAO8GVIKP2ZTrDDEkKtmZ0qQ38=; b=p03H+24QnbhQBJW75pi4+zDSkOUQCjneSZ6JSZbP0p5ojKITqJDgSJ+Y2da3eib2LE 0BACshakQ3o4qjHrTJS3xkW0Yyl2mLpBgYXCY8JsxKHKE8rWmw++gNo+8hCCEIBXyjMT UHkC51+bQms1Hv2g8mBR+KISEnfXmM4kCL0O0FiSvsopNaZeS/VwVc/W4O05gKldRcWp Ja8Bj3OAWG7D2zaj9bZDicZ5UwdQDTozsevyODD8onvPNKHo3xUKwmPSEouEEx2weQA8 Ni+xMcfCvJe9FuQAup+SH6ftQxe6plb1XjlfKyBUW/HDlYMTNiPQvW/cZs75XNbGBU7Z 7UeQ==
X-Gm-Message-State: APjAAAWDOrePfhHPk4IF9orrJV7xf+DwxQIv/xc+MabVp87rtOwqH/MZ slH4PCcmqejfVYqeakf9KtoJI84T
X-Google-Smtp-Source: APXvYqyibEUXRzQoi0aKraoFXsMf7K8RoNgCuyUYPnq0IyY5c1CLJr/2QgDor3iVyHxGeyHhLF1Vkw==
X-Received: by 2002:adf:e292:: with SMTP id v18mr529292wri.232.1569857745466;  Mon, 30 Sep 2019 08:35:45 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:ef0b:944d:9d98:6dcb:5730? ([2601:647:5a00:ef0b:944d:9d98:6dcb:5730]) by smtp.gmail.com with ESMTPSA id w125sm41138929wmg.32.2019.09.30.08.35.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Sep 2019 08:35:44 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <71DF4217-A53A-4D0A-ABDF-B75E59B4168F@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_2357E333-2888-41F0-91F4-8F025B1377C9"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Mon, 30 Sep 2019 08:35:41 -0700
In-Reply-To: <189750DA-3C62-4198-9A31-1AF2589C4A83@cooperw.in>
Cc: Bob Hinden <bob.hinden@gmail.com>, architecture-discuss@ietf.org, The IAB <iab@iab.org>
To: Alissa Cooper <alissa@cooperw.in>
References: <156763077985.22753.8206505094680303304.idtracker@ietfa.amsl.com> <A212688E-FDE7-43EF-9244-BBE8B27AA2D4@cooperw.in> <52117344-9D35-4F1C-8DF9-EC0DCE0A5337@gmail.com> <189750DA-3C62-4198-9A31-1AF2589C4A83@cooperw.in>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/qJnMxDfYFKpTdwurlLSE1cxZaNE>
Subject: Re: [arch-d] Call for Comment: <draft-ietf-iasa2-rfc6635bis-03> (RFC Editor Model (Version 2))
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: Mon, 30 Sep 2019 15:35:50 -0000

--Apple-Mail=_2357E333-2888-41F0-91F4-8F025B1377C9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Thanks, I will plan a new version with these changes after the last call =
ends on 2019-10-02.

Bob


> On Sep 30, 2019, at 6:01 AM, Alissa Cooper <alissa@cooperw.in> wrote:
>=20
> Hi Bob,
>=20
> All sounds good to me.
>=20
> Thanks,
> Alissa
>=20
>=20
>> On Sep 27, 2019, at 7:45 PM, Bob Hinden <bob.hinden@gmail.com> wrote:
>>=20
>> Alissa,
>>=20
>>> On Sep 27, 2019, at 6:33 AM, Alissa Cooper <alissa@cooperw.in> =
wrote:
>>>=20
>>> Hi,
>>>=20
>>> I have some comments on this document.
>>=20
>> Thanks for reviewing the document.
>>=20
>>>=20
>>>=20
>>> Section 1:
>>>=20
>>> s/The IAB maintains it's/The IAB maintains its/
>>>=20
>>> s/Internet Administrative Oversight Committee (IAOC)/IETF =
Administrative Oversight Committee (IAOC)/
>>=20
>> Good
>>=20
>>>=20
>>>=20
>>> Section 2.1:
>>>=20
>>> "The RSE is expected to cooperate closely with the LLC Board and the
>>> stream managers."
>>>=20
>>> Given that the LLC Board is an oversight body operating at a =
strategic level, I think this would make more sense if it said "LLC" =
(which includes LLC staff and contractors, including tools people) =
rather than "LLC Board.=E2=80=9D
>>>=20
>>=20
>> That is fixed in -03.
>>=20
>>=20
>>> Section 2.1.7:
>>>=20
>>> The LLC is in the process of adopting a conflict of interest policy =
that will apply to all staff, contractors, and board directors =
<https://github.com/ietf-llc/policies-consultation/blob/master/Conflict-of=
-Interest-00.md>. Since the RSE will be bound by that policy, I think =
Section 2.1.7 should be removed to avoid confusion about which policy =
applies.
>>>=20
>>=20
>> As Brian Carpenter said, I think it would be a mistake to not say =
anything.  His proposed text seems reasonable to me, it is:
>>=20
>> The RSE is expected to avoid even the appearance of conflict of
>> interest or judgment in performing these roles.  To ensure this,
>> the RSE will be subject to a conflict of interest policy
>> established by the LLC.
>>=20
>>=20
>>>=20
>>> Section 3.1:
>>>=20
>>> "For all decisions that affect the RSE individually (e.g., hiring =
and
>>> firing), the RSOC prepares recommendations for the IAB, but the =
final
>>> decision is the responsibility of the IAB."
>>>=20
>>> Since the LLC is the contract holder, it needs to have final =
decisional authority about hiring and firing, e.g. if it is unable to =
negotiate suitable contract terms with a candidate. I would suggest the =
following edit:
>>>=20
>>> "For all decisions that affect the RSE individually (e.g., hiring =
and firing), the RSOC prepares recommendations for the IAB, but approval =
of these recommendations is the responsibility of the IAB.=E2=80=9D
>>=20
>> I think that is an improvement on the text.
>>=20
>>=20
>>> Section 4.2:
>>>=20
>>> "The RFC Series portion of the LLC budget shall include entries for
>>> the RSOC, RSE, RFC Production Center, and the RFC Publisher.  The =
LLC
>>> budget shall also include entries for the streams, including the
>>> independent stream."
>>>=20
>>> Since RFC 6635 was published I can't recall seeing a budget that had =
a line item for RSOC or for "the streams," so this text has seemingly =
not matched actual practice for some time. More generally, allowing the =
LLC some flexibility about how the line items appear seems warranted =
given that the LLC has this flexibility for the rest of the budget. I =
would suggest the following edit:
>>>=20
>>> "The LLC budget shall include funding to support the RSOC, RSE, RFC =
Production Center, the RFC Publisher, and the Independent Submissions =
Editor.=E2=80=9D
>>=20
>> I don=E2=80=99t read this as requiring line items in a published =
budget, for example, like the one at:
>>=20
>> =
https://www.ietf.org/media/documents/IETF_2019_Budget_Public_2018-12-19.pd=
f
>>=20
>> I think it was saying the LLC should be budgeting and tracking these =
activities, how it reports this to the community is a different matter.  =
That said, I think your text is clearer, but I think it=E2=80=99s a =
mistake to call out the RSOC here, as that is clearly part of the IAB.  =
So I suggest:
>>=20
>> OLD:
>>=20
>>  The RFC Series portion of the LLC budget shall include entries for
>>  the RSOC, RSE, RFC Production Center, and the RFC Publisher.  The =
LLC
>>  budget shall also include entries for the streams, including the
>>  independent stream.
>>=20
>> NEW:
>>=20
>>  The RFC Series portion of the LLC budget shall include funding to =
support
>>  the RSE, RFC Production Center, RFC Publisher, and the Independent =
Stream.
>>=20
>>=20
>>>=20
>>>=20
>>> Section 4.4:
>>>=20
>>> "If a disagreement or decision has immediate or future contractual
>>> consequences, it falls under [I-D.ietf-iasa2-rfc4071bis]; thus, the
>>> RSE must identify the issue and provide his or her advice to the =
LLC;
>>> additionally, if the RSOC has provided advice, forward that advice =
as
>>> well."
>>>=20
>>> This sentence is not grammatically correct. I'm not sure what to =
suggest as it seems to be stating something obvious, but perhaps I'm not =
able to understand the point being made.
>>=20
>> That is quite a sentence, too many editors here :-)
>>=20
>> How about:
>>=20
>>  If a disagreement or decision has immediate or future contractual
>>  consequences, it falls under [I-D.ietf-iasa2-rfc4071bis].  If this =
happens
>>  the RSE must identify the issue and provide advice to the LLC.
>>  Additionally, if the RSOC has also developed advice, it should =
forward that
>>  advice to the LLC.
>>=20
>>  The LLC must notify the RSOC and IAB regarding the action it
>>  concludes is required to resolve the issue based on its applicable
>>  procedures and provisions in the relevant contracts.
>>=20
>> Thanks,
>> Bob
>>=20
>>=20
>>>=20
>>>=20
>>> Thanks,
>>> Alissa
>>>=20
>>>=20
>>>=20
>>>=20
>>>> On Sep 4, 2019, at 9:59 PM, IAB Executive Administrative Manager =
<execd@iab.org> wrote:
>>>>=20
>>>> This is an announcement of an IETF-wide Call for Comment on
>>>> draft-ietf-iasa2-rfc6635bis-03.
>>>>=20
>>>> The document is being considered for publication as an =
Informational RFC
>>>> within the IAB stream, and is available for inspection at:
>>>> <https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc6635bis/>
>>>>=20
>>>> The Call for Comment will last until 2019-10-02. Please send =
comments to
>>>> architecture-discuss@ietf.org and iab@iab.org.
>>>>=20
>>>> Abstract
>>>>=20
>>>> The RFC Editor model described in this document divides the
>>>> responsibilities for the RFC Series into three functions: the RFC
>>>> Series Editor, the RFC Production Center, and the RFC Publisher.
>>>> Internet Architecture Board (IAB) oversight via the RFC Series
>>>> Oversight Committee (RSOC) is described, as is the relationship
>>>> between the IETF Administration Limited Liability Company and the
>>>> RSOC.  This document reflects the experience gained with "RFC =
Editor
>>>> Model (Version 1)", documented in RFC 5620; and obsoletes RFC 6635 =
to
>>>> replace all references to the IASA and related structures with =
those
>>>> defined by the IASA 2.0 Model.
>>>>=20
>>>> [RFC Editor: Please remove the following paragraph prior to
>>>> publication.]
>>>>=20
>>>> The IASA2 WG requests that the IAB publish this replacement for RFC
>>>> 6635.
>>>>=20
>>>> _______________________________________________
>>>> IETF-Announce mailing list
>>>> IETF-Announce@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>>=20
>>> _______________________________________________
>>> Architecture-discuss mailing list
>>> Architecture-discuss@ietf.org
>>> https://www.ietf.org/mailman/listinfo/architecture-discuss
>>=20
>=20


--Apple-Mail=_2357E333-2888-41F0-91F4-8F025B1377C9
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEm0rfRsOCoyamPexGrut0EXfnu6gFAl2SIM0ACgkQrut0EXfn
u6gj+gf/ecp2eqHUvOHL/MpW3N/nDJsnL1oZ2sVVz0WWVsybTGtWB6BjVrsuZvr7
Y+XBpKp8o2ugEo1qAAvcgy2ySZsno+wYIrO/2KNkILnSR31Z5XeZXuz4KgnUPjGO
PfjH+MXBgfKWh0IUByz1/ZYDMxcfm7P1lNNo89pcdhiFHqPuU9qn7PXAeZk3/sly
2UI/yvHtOu0OPz84f8RdIjsPxqsPVJaj/gsRGa72323Eur+qR7Np76wDvjKaP2dd
d6Lcygb7K94nQEn5ob/6xPxsywjKwWJrW6yfqPxBmVwrWKrb4F3GB9hYMKpSWxA5
/UgDeynLJ/5pFU5hN/YMATuY8UrW2Q==
=YeId
-----END PGP SIGNATURE-----

--Apple-Mail=_2357E333-2888-41F0-91F4-8F025B1377C9--

