RFC 5006 status
Fred Baker <fred@cisco.com> Wed, 17 March 2010 15:28 UTC
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C5EC03A6C50 for <ietfarch-v6ops-archive@core3.amsl.com>; Wed, 17 Mar 2010 08:28:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.006
X-Spam-Level:
X-Spam-Status: No, score=-108.006 tagged_above=-999 required=5 tests=[AWL=-1.241, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, RDNS_NONE=0.1, 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 5BJjYgsDSNW4 for <ietfarch-v6ops-archive@core3.amsl.com>; Wed, 17 Mar 2010 08:28:22 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 8A96D3A6C3E for <v6ops-archive@lists.ietf.org>; Wed, 17 Mar 2010 08:27:02 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-v6ops@ops.ietf.org>) id 1Nrv4M-000N1y-Ro for v6ops-data0@psg.com; Wed, 17 Mar 2010 15:22:02 +0000
Received: from [171.68.10.87] (helo=sj-iport-5.cisco.com) by psg.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <fred@cisco.com>) id 1Nrv4J-000N1M-V4 for v6ops@ops.ietf.org; Wed, 17 Mar 2010 15:22:00 +0000
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEADuQoEtAaMHF/2dsb2JhbACbBHOfJZhohHYE
Received: from syd-iport-2.cisco.com ([64.104.193.197]) by sj-iport-5.cisco.com with ESMTP; 17 Mar 2010 15:21:57 +0000
X-IronPort-AV: E=Sophos;i="4.49,657,1262563200"; d="scan'208";a="62342677"
Received: from hkg-core-1.cisco.com ([64.104.123.94]) by syd-iport-2.cisco.com with ESMTP; 17 Mar 2010 15:21:57 +0000
Received: from [10.149.3.219] ([10.21.119.236]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o2HFLiNo001209; Wed, 17 Mar 2010 15:21:49 GMT
Subject: RFC 5006 status
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset="us-ascii"
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4BA0EC66.3010403@piuha.net>
Date: Wed, 17 Mar 2010 11:18:44 -0400
Cc: Lindqvist Kurt Erik <kurtis@kurtis.pp.se>, Ralph Droms <rdroms@cisco.com>, 6man Chairs <6man-chairs@tools.ietf.org>, Dave Thaler <dthaler@windows.microsoft.com>, Jari Arkko <jari.arkko@piuha.net>, jjeong@cs.umn.edu, luc.beloeil@orange-ftgroup.com, smadanapalli@gmail.com, Daniel Park <soohong.park@samsung.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <308C7176-40DF-4F82-AC2D-A4EAC6E2766B@cisco.com>
References: <4B9DFC7D.3070704@piuha.net> <E47F4C05-D53D-4E04-B15F-07752E9D9A7E@cisco.com> <4B9E96E2.10108@piuha.net> <1315FBDA-12A2-4C16-B66F-CBD4802E6766@cisco.com> <4BA089F9.5010006@piuha.net> <65B6B54D-98AD-4772-B2E0-6E2CA8DE76C0@cisco.com> <419DB14D-BFDC-4118-BB3E-F4D9570D927D@kurtis.pp.se> <A5AB4B97-11BA-4D27-860C-3811D075BFC6@cisco.com> <4BA0EC66.3010403@piuha.net>
To: IPv6 Operations <v6ops@ops.ietf.org>
X-Mailer: Apple Mail (2.1077)
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>
This is a structured question for the community. Jari Arkko tells us that he is getting requests from various sources to take RFC 5006 to Proposed Standard. It is now experimental. http://www.ietf.org/rfc/rfc5006.txt 5006 IPv6 Router Advertisement Option for DNS Configuration. J. Jeong, Ed., S. Park, L. Beloeil, S. Madanapalli. September 2007. (Format: TXT=26136 bytes) (Status: EXPERIMENTAL) (1) Please take a look at the document in the next few days; if you have comments on it (eg, you think it should be changed in some way), please comment to v6ops. (2) Vendors, please advise on implementations. Are there any? Has interoperability been demonstrated? (3) Operators, enterprise and/or service provider, please advise on deployment experience. I'm adding a brief discussion to the agenda Monday morning with a view to getting a quick thumbs-up/thumbs-down to advise Jari, who can then take that to 6man later in the week if appropriate. BTW, I have had a flurry of email related to the agenda. The current agenda may be found at http://www.ietf.org/proceedings/10mar/agenda/v6ops.html
- Re: RFC 5006 status Philip Homburg
- RFC 5006 status Fred Baker
- Re: RFC 5006 status Michael Cardell Widerkrantz
- Re: RFC 5006 status Durand, Alain
- Re: RFC 5006 status james woodyatt
- Re: RFC 5006 status Behcet Sarikaya
- Re: RFC 5006 status james woodyatt
- Re: RFC 5006 status Mark Smith
- Re: RFC 5006 status Brian E Carpenter
- Re: RFC 5006 status Mikael Abrahamsson
- Re: RFC 5006 status Antonio Querubin
- Re: RFC 5006 status Marco Hogewoning
- Re: RFC 5006 status Gert Doering
- Re: RFC 5006 status Philip Homburg
- Re: RFC 5006 status Gert Doering
- Re: RFC 5006 status sthaug
- Re: RFC 5006 status Gert Doering
- Re: RFC 5006 status sthaug
- Re: RFC 5006 status Benoit Boissinot
- Re: RFC 5006 status Rémi Després
- Re: RFC 5006 status Philip Homburg
- Re: RFC 5006 status Michael Cardell Widerkrantz
- Re: RFC 5006 status Benoit Boissinot
- Re: RFC 5006 status Mark Smith
- Re: RFC 5006 status Ole Troan
- Re: RFC 5006 status Michael Cardell Widerkrantz
- Re: RFC 5006 status Philip Homburg
- Re: RFC 5006 status Rémi Després
- Re: RFC 5006 status Philip Homburg
- Re: RFC 5006 status Ralph Droms
- Re: RFC 5006 status Ralph Droms
- Re: RFC 5006 status Ralph Droms
- Re: RFC 5006 status Ralph Droms
- Re: RFC 5006 status Gert Doering
- Re: RFC 5006 status Ralph Droms
- Re: RFC 5006 status Gert Doering
- RE: RFC 5006 status Templin, Fred L
- Re: RFC 5006 status Rémi Denis-Courmont
- Re: RFC 5006 status Benoit Boissinot
- Re: RFC 5006 status Gert Doering
- RE: RFC 5006 status Templin, Fred L
- Re: RFC 5006 status james woodyatt
- RE: RFC 5006 status teemu.savolainen
- Re: RFC 5006 status Brian E Carpenter
- Re: RFC 5006 status Mark Smith
- Re: RFC 5006 status Ralph Droms
- Re: RFC 5006 status james woodyatt
- Re: RFC 5006 status Rémi Denis-Courmont
- Overloading RA [Re: RFC 5006 status] Brian E Carpenter
- Re: Overloading RA [Re: RFC 5006 status] Seiichi Kawamura
- Re: Overloading RA [Re: RFC 5006 status] Xing Li
- Re: RFC 5006 status Gert Doering
- Re: RFC 5006 status Rémi Després
- Re: RFC 5006 status Adrian Kennard
- Re: RFC 5006 status Rémi Després
- Re: RFC 5006 status Syam Madanapalli
- Re: RFC 5006 status Hagen Paul Pfeifer
- RE: RFC 5006 status STARK, BARBARA H (ATTLABS)
- Re: RFC 5006 status Mark Smith
- RE: RFC 5006 status STARK, BARBARA H (ATTLABS)
- Re: RFC 5006 status Rémi Després
- Re: RFC 5006 status Rémi Després
- RE: RFC 5006 status STARK, BARBARA H (ATTLABS)
- Re: RFC 5006 status Syam Madanapalli
- Re: RFC 5006 status Rémi Després
- Stateless DHCP options "authorized" in RAs, in a … Rémi Després
- Re: RFC 5006 status Syam Madanapalli
- Re: Overloading RA [Re: RFC 5006 status] Sander Steffann
- Re: RFC 5006 status Behcet Sarikaya
- Re: RFC 5006 status Rémi Després
- Re: RFC 5006 status Nick Hilliard
- Re: RFC 5006 status Philip Homburg
- Re: RFC 5006 status Gert Doering
- Re: RFC 5006 status John Jason Brzozowski
- Re: Overloading RA [Re: RFC 5006 status] Mark Townsley
- Re: RFC 5006 status Mark Townsley
- Re: RFC 5006 status james woodyatt
- Re: RFC 5006 status Mark Smith
- Re: RFC 5006 status Mark Smith
- Re: RFC 5006 status Mark Smith
- Re: RFC 5006 status james woodyatt
- Re: RFC 5006 status Doug Barton
- Re: RFC 5006 status Mark Smith
- Re: Overloading RA [Re: RFC 5006 status] Lindqvist Kurt Erik
- RE: RFC 5006 status Suresh Krishnan
- RE: RFC 5006 status Hemant Singh (shemant)
- Re: RFC 5006 status Gert Doering
- RE: RFC 5006 status Tony Hain
- Re: RFC 5006 status Ole Troan
- Re: RFC 5006 status Lea Roberts
- RE: RFC 5006 status Hemant Singh (shemant)
- Re: RFC 5006 status Gert Doering
- Re: RFC 5006 status Brian E Carpenter
- RE: RFC 5006 status Hemant Singh (shemant)
- Re: RFC 5006 status Antonio Querubin
- RE: RFC 5006 status Mohacsi Janos
- Re: Overloading RA [Re: RFC 5006 status] Marco Hogewoning
- Re: RFC 5006 status Mark Townsley