Re: Internet Technology Adoption and Transition
ned+ietf@mauve.mrochek.com Wed, 23 April 2014 03:15 UTC
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC3271A0012 for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 20:15:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level:
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 Noqg6dHwQ1NU for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 20:15:52 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2E7DB1A000C for <ietf@ietf.org>; Tue, 22 Apr 2014 20:15:52 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6YJTR7P400003IB@mauve.mrochek.com> for ietf@ietf.org; Tue, 22 Apr 2014 20:10:46 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET="iso-8859-1"; format="flowed"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6WZAZ2YYO000052@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 22 Apr 2014 20:10:42 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6YJTPN8MO000052@mauve.mrochek.com>
Date: Tue, 22 Apr 2014 19:53:37 -0700
Subject: Re: Internet Technology Adoption and Transition
In-reply-to: "Your message dated Thu, 17 Apr 2014 23:11:31 -0700" <6.2.5.6.2.20140417215305.0dc8c008@resistor.net>
References: <2D34F9A8-98B9-4FBD-A3CD-B3C4A4EA7CD5@iab.org> <6.2.5.6.2.20140417215305.0dc8c008@resistor.net>
To: S Moonesamy <sm+ietf@elandsys.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Vbd7A0n_SokAEMqX6t2XRwAd-3Y
Cc: iab@iab.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Apr 2014 03:15:57 -0000
> Hello, > At 19:11 17-04-2014, IAB Chair wrote: > >This is a call for review of "Report from the IAB workshop on > >Internet Technology Adoption and Transition (ITAT)" prior to > >potential approval as an IAB stream RFC. > > > >The document is available for inspection here: > >https://datatracker.ietf.org/doc/draft-iab-itat-report-/ > I read the report. Section 2 mentions that SMTP and IMAP in the > applications space have continued to evolve. I have not see much > evolution in the SMTP space. I'll leave the relevant people to > comment about IMAP. As a nit, the reference for IPv6 is incorrect. I'm not sure what the report means by "evolve", but by any reasonable definition, I believe SMTP continues to evolve. If you're talking about standards work, the IESG just approved the RRVS document which specifies a new SMTP extension. In recent times we've approved other extensions such as MT-PRIORITY. And let's not forget about EAI, which is a pretty major evolution of the protocol. And this process continues. I rather expect we'll see changes in the STARTTLS space in the not too distant future. If you're talking about implementations, the first thing to note is that given the relatively small number of implementations in wide use, a change to even one or two of them is significant. And while progess is slow, it's pretty constant from my perspective. As for actual deployment, things are even more skewed, which makes them difficult to measure. For example, if a major wireless vendor implements the BINARY extension in both their client and their own server, that can affect a huge swath of traffic without any need for anyone else to change. The deployment of older extensions also changes over time, and it doesn't always increase. I'm fairly sure I'm seeing more of ENHANCEDSTATUSCODES but less of NOTARY. (And yeah, I know given the relationship between the two that's wierd. I'm just reporing what I've observed.) Moreover, there can be evolutionary changes having nothing to do with extensions per se. For example, it seems that not only is use of STARTTLS on the rise, what cipher suites are enabled seems to be changing, probably because a lot of sites are actually paying attention to such details when prior to the Snoden thing they care. Ned
- Call for Review of draft-iab-itat-report, "Report… IAB Chair
- Re: Call for Review of draft-iab-itat-report, "Re… Patrik Fältström
- Internet Technology Adoption and Transition S Moonesamy
- RE: Internet Technology Adoption and Transition l.wood
- RE: Internet Technology Adoption and Transition S Moonesamy
- Re: Internet Technology Adoption and Transition ned+ietf
- Re: Internet Technology Adoption and Transition S Moonesamy