Re: Internet Technology Adoption and Transition
S Moonesamy <sm+ietf@elandsys.com> Thu, 24 April 2014 15:18 UTC
Return-Path: <sm@elandsys.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 A41851A0397 for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 08:18:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.872
X-Spam-Level:
X-Spam-Status: No, score=-0.872 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272] 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 kdEmiBqHqkS4 for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 08:18:40 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 817F01A02C1 for <ietf@ietf.org>; Thu, 24 Apr 2014 08:18:40 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.235.12]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3OFIMYx005751 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Apr 2014 08:18:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1398352713; bh=GS+c0N4hI19+uBjWaqLzYm5tadhbX5gS65jcviF16OQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=xtQaT/Ljh8XtT1NrHtU+eUNZFS51XghnAopqVah7ll++Dfk16BjF+6jvqhlVxIdFW TSZc1+LYGsPKcX4uZA5qTdkHMvRvTEcdTsHz6alpsY1X03Ss38FoZb4+5DY1yKDNv0 xdYbABbNh5oeAi6dMUakM1PipRtRitT3DPz60p+Q=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1398352713; i=@elandsys.com; bh=GS+c0N4hI19+uBjWaqLzYm5tadhbX5gS65jcviF16OQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=DUkccMteGXXMcZBiqlTxjQciHd6rHfT6tWZi4h2bb03nANBvp5IgdqyfOjAW7dO+V 4PgMFwuEC+CBrGCSIjuQJFvTmcfFsZX/yKZEnsFV0Q3lLShuQvm7Eio7i3IZ2b1CId U9S9zqzcw5k1qorLW8x2ocwP1KVrpCm96WsPIjoM=
Message-Id: <6.2.5.6.2.20140424071559.0b636398@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 24 Apr 2014 08:05:43 -0700
To: Ned Freed <ned.freed@mrochek.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Internet Technology Adoption and Transition
In-Reply-To: <01P6YJTPN8MO000052@mauve.mrochek.com>
References: <2D34F9A8-98B9-4FBD-A3CD-B3C4A4EA7CD5@iab.org> <6.2.5.6.2.20140417215305.0dc8c008@resistor.net> <01P6YJTPN8MO000052@mauve.mrochek.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/aPyO-5lw18xCnYNQa0WxJtCcT8g
Cc: 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: Thu, 24 Apr 2014 15:18:42 -0000
Hi Ned, At 19:53 22-04-2014, Ned Freed wrote: >I'm not sure what the report means by "evolve", but by any reasonable >definition, I believe SMTP continues to evolve. Ok. >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. I was looking at it in terms of what is implemented and what is deployed. There has been standards work; some of examples are mentioned above. I agree that EAI is a pretty major evolution of the protocol. >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. There are different ways to look at usage. As an example, BINARY may be about 25% of what's deployed (please treat that figure as unverified). >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.) The statistics I looked at show a little more of ENHANCEDSTATUSCODES. >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. I haven't look into the STARTTLS statistics recently to be able to compare the figures with the ones before the Snow thing. Regards, S. Moonesamy
- 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