IETF Logo Mail Archive

Re: [arch-d] [IAB] Call for Comment: <draft-iab-protocol-transitions> (Out With the Old and In With the New: Planning for Protocol Transitions)

Ted Hardie <ted.ietf@gmail.com> Wed, 11 January 2017 16:53 UTC

Return-Path: <ted.ietf@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 89C1A12975C for <architecture-discuss@ietfa.amsl.com>; Wed, 11 Jan 2017 08:53:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_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=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 mQrnlj6W9BWN for <architecture-discuss@ietfa.amsl.com>; Wed, 11 Jan 2017 08:53:27 -0800 (PST)
Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (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 0EFE7129681 for <architecture-discuss@ietf.org>; Wed, 11 Jan 2017 08:53:27 -0800 (PST)
Received: by mail-qk0-x232.google.com with SMTP id 11so116219439qkl.3 for <architecture-discuss@ietf.org>; Wed, 11 Jan 2017 08:53:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NPMBrdRS0F49R70etCahxBK4eImO1+YjC8EnoH3YkM4=; b=gvb1uBTYGJvSEjmp+E9VWCs9Ir/NT80i3ppI9asyih9d5ueeTvExSvd5WyIAjYfdL3 9wXqlpmjXctO0o9si9VnBZqJDilLxBFf96slLnJjvd7Ll9PL41iaVn/Il7AwQayVuvuA +bAgiFW7TH07irv73Zszyekf0f9qGsIC9Z0mSeWQEFZIJz4qMQwKhYBbvWid5kWLJ14q atlDYIqOtZfeayzLHCaFDWDltXna14jSqFQUo0Yg1Sr7NMF3Zn+u26pEm4QlQBGBanuT CQ8Vkmdyb8ONpwW19RzrtgaBw8upKqgqTJULhwZ1iFrJmT2K7ZYBGcmhEMCboNdJJXQK E4Tg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NPMBrdRS0F49R70etCahxBK4eImO1+YjC8EnoH3YkM4=; b=qz+AhbWC4/YcKASS+NbSbnXaDahzdvoofb+FmYclqAM/uxfu8oun41udJso8KXkyDk dJLmqPjrcLYc42IG7mIGZpAI1yU18I0+x/3lPfg0t6OfZ/WbOOnk8DPsd45taLYx5++U 7Of8Xj8cD5fg0r49JjNRXYcRgXYdnaDKAf8gv3LgGC1V8yVcmH3cLflaYzAF8Ndn+NB2 M7yF353VygAmtQpskBCwMA1epzCU5d3FLoNzfIETaL0nUwgeGQDOXgMx0cNHNJ3azfsk VLwslccn6ZAD2Kra/2c3DaN988u3QLFombQIQW7RGxdJhX7BiS1C1TZLNzGZwKFlWsdL YO1g==
X-Gm-Message-State: AIkVDXKb6CIFpljsGiLmJq2938o4D1p40vYQ2ad3Q2ukKZIOqSpqWOwsUqVqcQ4xtDjl85FOjGIi61iVfdiBKg==
X-Received: by 10.55.105.70 with SMTP id e67mr2276697qkc.89.1484153606092; Wed, 11 Jan 2017 08:53:26 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.182.66 with HTTP; Wed, 11 Jan 2017 08:52:55 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20170110191336.0e812710@elandnews.com>
References: <148357904166.13056.1797751203596240116.idtracker@ietfa.amsl.com> <d079c169-a60b-21db-a031-7e3658166443@cisco.com> <CABkgnnWrjTe5J0qgr1kjtisKL5q4BR6XDoh7y3p3rjc+G4EQEA@mail.gmail.com> <3f13be22-cf8a-d2b8-6ac3-70f405e2a04b@cisco.com> <CABkgnnUr5DhRDCWgt8ang=smL768bYyrDCCr6TFH0MJAVPNNWg@mail.gmail.com> <6.2.5.6.2.20170110191336.0e812710@elandnews.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 11 Jan 2017 08:52:55 -0800
Message-ID: <CA+9kkMA0pLuxMN6t7+g6_Dc48eiYFVH9VAURs9QOTbOFt7jRTA@mail.gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary="001a114fe7247bbcf60545d470ca"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/yvIsBTWJSiiAzp-5xwee14VZhFs>
Cc: IAB <iab@iab.org>, architecture-discuss@ietf.org
Subject: Re: [arch-d] [IAB] Call for Comment: <draft-iab-protocol-transitions> (Out With the Old and In With the New: Planning for Protocol Transitions)
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.17
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 Jan 2017 16:53:28 -0000

On Tue, Jan 10, 2017 at 9:35 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hi Martin, Eliot,
>
>
> Is the IAB responsible for planning for transition for an IETF protocol?
>
>
The charter of the IAB puts long-range planning in the IAB's set of
responsibilities when that is done as part of its architectural oversight
(see section 2.1 of RFC 2850).  In practice that means that some
transitions are completely outside of the IAB's remit, some the IAB
contributes to (by reviewing charters for proposed work, proposing
workshops on the relevant space, etc.), and some it advocates (the
transition to default-confidential operation for the Internet being the
most recent).  Once the community accepts the advocacy, though, the work
goes on in the IETF.

regards,

Ted


> Regards,
> S. Moonesamy
>
>

v2.23.0 | Report a Bug | By Email