Re: [arch-d] Proposed IAB program: Evolvability, Deployability, & Maintainability.

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 07 July 2020 03:37 UTC

To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Tommy Pauly <tpauly@apple.com>, "architecture-discuss@iab.org" <architecture-discuss@iab.org>
References: <087DBE75-7103-4D82-8878-59F1E53592C8@apple.com> <a09f3c82-42cd-752f-f071-359ed117fdec@gmail.com> <393e63e8-85db-755b-4e11-509670ed6332@cs.tcd.ie>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <f8811bcf-72f3-b489-e893-949fd5f7ab45@gmail.com>
Date: Tue, 07 Jul 2020 15:36:58 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <393e63e8-85db-755b-4e11-509670ed6332@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/beQ6ToXWM1QSMKcHU8rICf-qOSE>
Subject: Re: [arch-d] Proposed IAB program: Evolvability, Deployability, & Maintainability.
Precedence: list

On 07-Jul-20 13:14, Stephen Farrell wrote:
> 
> Hi Brian,
> 
> (Maybe not directly a question for you but...)

No, there are many people more qualified to answer than me for the SMTP
case. I'm pretty sure IPv6 would have gone more smoothly with 6-monthly
issues of "Node Requirements", though. There are too many interlocking
pieces and developers were left to make their own choices.

   Brian

> 
> On 06/07/2020 23:05, Brian E Carpenter wrote:
>> SMTP has been the classical example for many years, and I suspect
>> that RTCWEB might furnish another good example of this problem before
>> long.
> Do we have evidence as to the (good, bad or neutral) impact
> of the stately pace of the evolution of email standards-
> track  RFCs? I could imagine the net effect being overall
> positive or negative but am unsure which may be the case. I
> suspect it may be more likely that the actual impact is not
> correlated with RFC numbers at all, but that may also be
> wrong.
> 
> Cheers,
> S.
>

[arch-d] Proposed IAB program: Evolvability, Depl… Tommy Pauly
Re: [arch-d] Proposed IAB program: Evolvability, … Toerless Eckert
Re: [arch-d] Proposed IAB program: Evolvability, … Brian E Carpenter
Re: [arch-d] Proposed IAB program: Evolvability, … Toerless Eckert
Re: [arch-d] Proposed IAB program: Evolvability, … Stephen Farrell
Re: [arch-d] Proposed IAB program: Evolvability, … Brian E Carpenter
Re: [arch-d] Proposed IAB program: Evolvability, … Joel M. Halpern
Re: [arch-d] Proposed IAB program: Evolvability, … Brian E Carpenter
[arch-d] Re: Proposed IAB program: Evolvability, … Martin Thomson
Re: [arch-d] Proposed IAB program: Evolvability, … S Moonesamy
Re: [arch-d] Proposed IAB program: Evolvability, … Tommy Pauly
Re: [arch-d] Proposed IAB program: Evolvability, … Tommy Pauly
Re: [arch-d] Proposed IAB program: Evolvability, … Tommy Pauly
Re: [arch-d] Proposed IAB program: Evolvability, … Toerless Eckert
Re: [arch-d] Proposed IAB program: Evolvability, … S Moonesamy
[arch-d] Re: Proposed IAB program: Evolvability, … Christopher Wood
Re: [arch-d] Proposed IAB program: Evolvability, … Spencer Dawkins at IETF
Re: [arch-d] Proposed IAB program: Evolvability, … Mary Barnes
Re: [arch-d] Proposed IAB program: Evolvability, … Spencer Dawkins at IETF
Re: [arch-d] Proposed IAB program: Evolvability, … Brian E Carpenter
Re: [arch-d] clusterpation, was Proposed IAB prog… John Levine
Re: [arch-d] clusterpation, was Proposed IAB prog… Brian E Carpenter
Re: [arch-d] clusterpation, was Proposed IAB prog… John R Levine
Re: [arch-d] clusterpation, was Proposed IAB prog… Toerless Eckert
Re: [arch-d] clusterpation, was Proposed IAB prog… John R Levine
Re: [arch-d] clusterpation, was Proposed IAB prog… tom petch
Re: [arch-d] Proposed IAB program: Evolvability, … John C Klensin
Re: [arch-d] clusterpation, was Proposed IAB prog… Toerless Eckert