IETF Logo Mail Archive

Re: [addr-select-dt] next step

Bob Hinden <bob.hinden@gmail.com> Tue, 14 September 2010 20:00 UTC

Return-Path: <bob.hinden@gmail.com>
X-Original-To: addr-select-dt@core3.amsl.com
Delivered-To: addr-select-dt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 475B73A69A1 for <addr-select-dt@core3.amsl.com>; Tue, 14 Sep 2010 13:00:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.654
X-Spam-Level:
X-Spam-Status: No, score=-102.654 tagged_above=-999 required=5 tests=[AWL=-0.055, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PPp0kUkOajDt for <addr-select-dt@core3.amsl.com>; Tue, 14 Sep 2010 13:00:28 -0700 (PDT)
Received: from mail-px0-f172.google.com (mail-px0-f172.google.com [209.85.212.172]) by core3.amsl.com (Postfix) with ESMTP id 5A1B63A69B2 for <addr-select-dt@ietf.org>; Tue, 14 Sep 2010 13:00:28 -0700 (PDT)
Received: by pxi6 with SMTP id 6so3387153pxi.31 for <addr-select-dt@ietf.org>; Tue, 14 Sep 2010 13:00:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=vKOWEWho7dmsc1DH8XZq1SzwFbbP/3K55xnDUf/HuUg=; b=maum17Hyu7a08bL1GFpGIdRUFldVvmoMtySFty44RZx8VFh/nYQpK8xIL4AlI6ULWB MDvmY2rWjOhhD9MiZML1I5s1qk7rdbJVCCROeYVd5Vy5U/E6dvnzAnXVaZNY6UZpqSw1 3+W1sxeFL1NjXV8sF879iSTWV2HBSE1+GUe7g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=Iq11lpavZFq8dNFswZHp/XCIZLtlvG9G3GqEn8+noQk5bqpYOC7tuXNmhJFsjxnEJ+ /NkBzFJhNkU4mjueI8Cctp8BT0QPs97Gso8GrAcRSemtMPlRKUUk3fBHr95rzdtB0Tan zXAKoJS4PyvZEpp6+diB+Psjs8aLiJbXHr0IU=
Received: by 10.114.93.19 with SMTP id q19mr614525wab.15.1284494454227; Tue, 14 Sep 2010 13:00:54 -0700 (PDT)
Received: from [172.16.224.217] ([209.97.127.34]) by mx.google.com with ESMTPS id d2sm896988wam.2.2010.09.14.13.00.45 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 14 Sep 2010 13:00:48 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <4C8FC373.5010404@innovationslab.net>
Date: Tue, 14 Sep 2010 13:00:44 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <6F801459-1B4D-4E83-94A4-51E3FB963A9F@gmail.com>
References: <D6CE49D0-6BF0-488E-B4AD-F28BFE2DEE98@nttv6.net> <4C8FC373.5010404@innovationslab.net>
To: addr-select-dt@ietf.org
X-Mailer: Apple Mail (2.1081)
Subject: Re: [addr-select-dt] next step
X-BeenThere: addr-select-dt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IPv6 Address Selection Design Team <addr-select-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/addr-select-dt>, <mailto:addr-select-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/addr-select-dt>
List-Post: <mailto:addr-select-dt@ietf.org>
List-Help: <mailto:addr-select-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/addr-select-dt>, <mailto:addr-select-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Sep 2010 20:00:29 -0000

Hi,

>> 
>> 
> I believe we have reached a point of completion for the design team with
> the publication of the address selection considerations draft.  What Bob
> & I would like to see now is a draft proposing the actual changes to RFC
> 3484.  This should be driven by the issues raised in
> draft-ietf-6man-rfc3484-revise.  It would be encouraging to see such a
> draft published soon so that it can be discussed on the mailing list and
> possibly revised prior to the Beijing meeting.

I would like to second what Brian said.  This work has been going on for a long time (two years?) and it needs to get to completion.  

I think the DT is completed now that <draft-ietf-6man-rfc3484-revise-00.txt> was published.  As Brian said, now we need an actual specification that proposes specific changes to RFC3484.  I would like to see the first draft at least a month before the Beijing meeting to allow for a discussion and an update prior to the cutoff for drafts.

If you do not think you can make this schedule, please let us know.

Thanks,
Bob

v2.23.0 | Report a Bug | By Email