RE: Internet Technology Adoption and Transition

S Moonesamy <sm+ietf@elandsys.com> Fri, 18 April 2014 14:43 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 E7FB71A01BB; Fri, 18 Apr 2014 07:43:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.062
X-Spam-Level:
X-Spam-Status: No, score=-2.062 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.272, T_DKIM_INVALID=0.01] 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 plWKq2p6OEUn; Fri, 18 Apr 2014 07:43:46 -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 0BBB41A01B6; Fri, 18 Apr 2014 07:43:46 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.151.248]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3IEhSUJ020157 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 Apr 2014 07:43:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1397832221; bh=fZ9LunEsDF0x30RseqQIy1Iv5b2TRrex+CO5luKAVqk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Xv7yKcDXgd8969ktDjZIjPFEUXLAnvVR6XZeRubNDQK/3fdWUio4kCbdb8ZEP+N09 yWN9rfpRSAtMqfoCGH/0FTwmKVwnyTYRjSMnV7HHxij5sqgS1OomAdxoVUKvPZS+wn rEYFV199IBgFZnRliXsPQp+4FMYKK/hmSRYSIHic=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1397832221; i=@elandsys.com; bh=fZ9LunEsDF0x30RseqQIy1Iv5b2TRrex+CO5luKAVqk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=iuWaxlg3peP6YZ34kr2AOcvr1wHANxqtkrWnS0SMfZdD1h1P3D/5VjJz/F4BlSvO7 +lVUrcyiHt9CcYBshHBzIxUruxvqP+HCDy2hvl6JQCblQLfXN3qUPI/2rsuRCmVTQ+ XaGIGGyep/ea22YPOymWzMtBnnJ/k4+t2COdm40s=
Message-Id: <6.2.5.6.2.20140418054044.0cb13980@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 18 Apr 2014 06:41:13 -0700
To: l.wood@surrey.ac.uk, iab@iab.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: RE: Internet Technology Adoption and Transition
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E9989B8E@EXMB01CMS.surre y.ac.uk>
References: <2D34F9A8-98B9-4FBD-A3CD-B3C4A4EA7CD5@iab.org> <6.2.5.6.2.20140417215305.0dc8c008@resistor.net> <290E20B455C66743BE178C5C84F1240847E9989B8E@EXMB01CMS.surrey.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/q7AI4y18x7uV0kaX41ojAphuEHY
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: Fri, 18 Apr 2014 14:43:51 -0000

Hi Lloyd,
At 00:57 18-04-2014, l.wood@surrey.ac.uk wrote:
>the correct url is
>https://datatracker.ietf.org/doc/draft-iab-itat-report/
>no trailing minus. why cite a broken url?

I should have removed the URL instead of citing it.

>evolution in the smtp space? Um, DMARC?

I am reading "SMTP" narrowly and did not consider DMARC as part of the space.

 From 
<http://www.iab.org/wp-content/IAB-uploads/2013/06/itat-2013_submission_5.docx>http://www.iab.org/wp-content/IAB-uploads/2013/06/itat-2013_submission_5.docx 
examples of DNSSEC-based applications are mentioned and there is the following:

    "The DMARC wg is working on higher-level use of DKIM and SPF."

The technology for those two specifications is mostly related to DNS.

>for thoughts on http as an hourglass waist, see
>http://personal.ee.surrey.ac.uk/Personal/L.Wood/publications/internet-drafts/draft-wood-dtnrg-http-dtn-delivery/lloyd-wood-turning-http-into-a-standalone-layer-ietf-75-tsvarea-slides.pdf
>- it's a little hard to see http as a waist when it's so tightly 
>coupled to tcp. That is unlikely to change, as the benefits of 
>uncoupling are for edge cases.

Thanks for the URL.  I would say yes to the comment about tightly 
coupled.  I'd say that they are seen as the transport and you end up 
with other protocols being designed on top of that.

>many involved in the ietf, myself included, began contributing as 
>grad students. As with academic paper review, it's how the 
>interested/enthusiastic/unpaid learn.

Yes.

Regards,
S. Moonesamy